- Indico style
- Indico style - inline minutes
- Indico style - numbered
- Indico style - numbered + minutes
- Indico Weeks View
2024-12-09 9:02 – 09:40
All stakeholders have been listed to see that there are many interests that SciCat is used at DESY. Also the main reason why we want/need SciCat was reminded. Work highlights were given: Implementation of proposal types to disentangle DESY IDs as well as the advanced work by Tim W was mentioned. Single ingredients, bits and pieces for a successful, performant SciCat service were outlined:
Job of FS-EC: ingestion, using standardised fields (PaNET/TA1 output) for all beamlines
Job of FS-SC: close to the requirements study possible loads and requests
Job of IT-InFa: to setup productive service meaning amongst others
collaborating with FS-SC to derive a performant systems configuration based on real data,
foster communication between different user groups and SciCat developers (collect “frustration”),
get in touch and foster contact to DESY users
Job of IT-RIC: provide this catalogue for open data DAPHNE wide
How will the final SciCat service look like?
Goal: 1 access point for all DESY data from which a user can
mint a DOI according to L criteria (almost DONE for public data)
find and access data → topic of 2025.
RH mentioned a few IT topics of technical nature to be solved/decided upon beforehand.
A question came up concerning workflow on stable releases. Current deployment workflow will be adopted to from latest to known stable.
Feedback loop with users as well as regular interaction of FS and IT working groups is vital for a good user experience and FAIR. User support likely to be better provided with DAPHNE 2.
Participants
Jan K
Stefan D
Igor K
Sabrina S
Jan G
RH