Post on 26-Sep-2020
transcript
SMIS & ICAT & European Affiliation DatabasePresented by D.Porte & J. Savoyet
Slide: 1Umbrella EAD ICAT- Version: 1.0 (15/11/2013) - Group: MIS -
Several projects at the ESRF in the scope of the Umbrella
Where are we now?
Several projects at the ESRF in the scope of the Umbrella
-SMIS in the Umbrella (Stefan Schulze)
-ICAT implementation (Nicola Bessone, Christophe Cleva, Alistair Mills, Julien Savoyet)
- European Affiliation Database (Julien Savoyet, Dominique Porte)
Slide: 2Umbrella EAD ICAT- Version: 1.0 (15/11/2013) - Group: MIS -
SMIS in the Umbrella
Slide: 3Umbrella EAD ICAT- Version: 1.0 (15/11/2013) - Group: MIS -
Umbrella (Stefan Schulze)
Slide: 4Umbrella EAD ICAT- Version: 1.0 (15/11/2013) - Group: MIS -
ICAT
-ICAT is installed
-Nicola Bessone customized ICAT to collect data from a beam line (id19),-Christophe Cleva is continuing the implementation
D i ll d f SMIS & T DB-Data is collected from SMIS & TomoDB
-ESRF is in the “service verification” game
European Affiliation Database (EAD)
es an affiliation database mean in the context of a European Virtual User Office?
The affiliation of a user using a facility for an experiment corresponds to the laboratory from which he is authorized to carry out experiments professional address
User applying to carry out an experiment
Facility A Facility B Facility CLocal ser/affiliation/roposals … database
Local User/affiliation/proposal
s
Local User/affiliation/proposal
sdatabase s … database
s … database
The goal is to share a common affiliation databaseComponent of
Umbrella!!Cloud !!
Ultimate goal
User applying to carry out an experiment
Facility A Facility B Facility CLocal ser/affiliation/roposals … database
Local User/affiliation/proposals …
Local User/affiliation/proposals …
database database database
ages of a common Affiliation database:
e user records his affiliation only once e affiliation is checked and polished only once.p yhen the user moves from a laboratory to another, he changes his affiliation only once hen the affiliation changes, it is automatically replicated to all facilitiese management of the database is shared by several facilities => less work for UO
Common affiliation database
EAD
Facility A Facility B Facility CLocal User/propos
als … database
Local User/proposals … database
Local User/proposals … database
Nevertheless, facilities already have a local affiliation database
or even impossible to replace LAD by a common central EAD in the short term
Common affiliation database
EAD
p p y
database
F ilit A F ilit B F ilit CFacility A Facility B Facility CLocal User/proposa
ls … database
Local User/proposals … database
Local User/proposals … database
LAD LAD LADFacilities want to get sensitive databases under control, in-house
future
he long term, some facilities will replace their LAD by the EAD, when ers will keep their LAD or an hybrid solution
Common affiliation database
EAD
ers will keep their LAD or an hybrid solution
database
F ilit A F ilit B F ilit CFacility A Facility B Facility CLocal User/proposa
s … database
Local User/proposals … database
Local User/proposals … database
LAD LAD LAD
Both databases must coexist in a first period
=> Synchronization mechanism
Common affiliation database
EADdatabase
F ilit A F ilit B F ilit CFacility A Facility B Facility CLocal User/proposa
ls … database
Local User/proposals … database
Local User/proposals … database
LAD LAD LAD
European Affiliation Database
- 2011 - first specification
https://wwws.esrf.fr/ead/preprod/EvuoFront/mockup/login/
- Test period to collect very last feedback
- User Office role
- Content based on ESRF affiliation database
Harmonization MeetingHamburg / 21 January 2013
PaNdata MeetingLund / 12 March 2013
Harmonization MeetingBerlin / June 2013
EAD Database implementation
oject ation
EAD Web Forms Mock‐up
g / y
EAD Database Design
/
EAD “Ergonomic Interface” Mock‐up
/
EAD developments
EAD “Trial Prototype” launch
Umbrella Integration &EAD Maintenance
European Affiliation Database
Still to be done
European Affiliation Database
-demonstration