1. Umbrella Implementation at the ESRF and affiliation database project
Status
ZURICH - Wednesday 13 June 2012 – D. PORTE – MIS group -

2. TID involved in
TID DAY – “Together Everyone Achieves More” Frday 8 June 2012 – D. PORTE – MIS group -

3. TID involved in
TID DAY – “Together Everyone Achieves More” Frday 8 June 2012 – D. PORTE – MIS group -

4. Overlap PaNdata-ODI IT Work Packages CRISP IT Work Packages
CRISP WP16
PaNdata WP3
PaNdata-ODI
IT Work Packages
CRISP
IT Work Packages
Overlap
CRISP WP17
PaNdata WP4
PaNdata WP7
AAA & Affiliation
Data catalogue
Fast data recording
Stefan Schulze
Julien Savoyet
Benoit Rousselle
Julien Savoyet
Nicola Bessone
A Demonstration Presentation - Version: 0.1 (19/08/03) - Group: Demo Group -

5. AAA & affiliation - Status:
Authentication: Prototype using a VM clone of our current SMIS system
- Affiliation database: Specification - Draft already exists
Implementation of the authentication with the operational SMIS system: should cost a couple of weeks (with the necessary help of PSI)
Implementation of the affiliation database: Long process described later on
ZURICH - Wednesday 13 June 2012 – D. PORTE – MIS group -

6. LAD Facility A Facility B Facility C
Local User/affiliation/proposals … database
User applying to carry out an experiment
LAD
What does an affiliation database mean in the context of a European Virtual User Office?
The affiliation of people (users) using a facility for an experiment corresponds to the laboratory from which they are authorized to carry out experiments. This information gives the facility the “professional” address of the users. It also opens up the possibility make statistics. It is important to notice that users may “work” for several laboratories at any given time same.
April 24th CRISP 1st Annual meeting Dominique PORTE/ESRF

7. EAD LAD Facility A Facility B Facility C
Local User/proposals … database
Common affiliation database
LAD
EAD
Sharing the same affiliation database between facilities will help scientists a lot. The user will no longer have to register the same information several times. In addition, an affiliation record will make sure that the spelling is the same at all facilities.
April 24th CRISP 1st Annual meeting Dominique PORTE/ESRF

8. Affiliation database: - Status
What we still have to do
To complete the specification:
- To meet facilities ready to participate in the very first common affiliation database. Is a workshop could help for that?
- To agree on a common specification
- To agree on a roadmap
And also
- Evaluate the cost and benefits of such a database
A Demonstration Presentation - Version: 0.1 (19/08/03) - Group: Demo Group -

9. Thanks to the pre-study and our experience at the ESRF
Cost
Benefits
We have already updated the database schema and data =>
More than 6 months of work, only half of the database is now up-to-date.
Duplicate entries deleted or merged.
Sharing the management of entries with other facilities.
A Demonstration Presentation - Version: 0.1 (19/08/03) - Group: Demo Group -

10. Needs adoption (at least an information) at the ESRF Executive level
Political aspects:
Needs adoption (at least an information) at the ESRF Executive level
Needs the involvement of the ESRF User Office
Potentially needs the involvement of the ESRF communication unit
A Demonstration Presentation - Version: 0.1 (19/08/03) - Group: Demo Group -

11. Potential difficulties
To agree on a common database schema (same fields, same types, same design)
Having enough resources to do the job
A Demonstration Presentation - Version: 0.1 (19/08/03) - Group: Demo Group -

12. Two progressive and sequential phases implementation
- Phase 1: Setup of an Establishment database
- Phase 2: Addition of general interest fields
- Workshop in September/October
A Demonstration Presentation - Version: 0.1 (19/08/03) - Group: Demo Group -