Max answer to "the DESY case" (IDs disentanglement)

Monday 1 Jul 2024, 10:00 → 11:00 Europe/Berlin

DESY, building 1, 2nd floor, SR 03a

Regina Hinzmann (IT (IT Information Fabrics))

https://desy.zoom.us/j/6389377212?pwd=a3pJUGZXb1UrNm5rVVJtN3phNC94dz09

 

Link to document attached at indico

2024-06-24 10:00 – 10:37

Frank S described the issue we had with IDs, the suggestions we made and the received solutions from Max. He terminated by commenting that “DESY issues will remain weak without SciCat in production”.

 

Discussion yielded:

• a user (Jörg H) reported elastic search is enabled. One should test if one can find datasets using beamtime ID or proposal ID.

   

We will follow in all what Max suggested:

• Our option 2 will not be considered.

• short term: start_beamtime and stop_beamtime scripts need to be modified to include DOOR proposal ID ahead of the beamtime ID, to be synchronised with Jan K and Florian B who was much in favor wrt to the current solution. RH will follow up with Stefan D.

• long term: we will use solution of fpotier that enables implementation of at least these two types of IDs in the proposal class. RH will deal with it only after DOI prototype, maybe this year.

• very long term solution: make frontend labels configurable (or language model)

  • Create github issue

  • Wait for current release is completed.

  • Seek for resources

  • Plan, design, implement

         to be done.

 

Participants

1. Frank S

2. Paul M

3. Jan K

4. Anton B

5. Florian B

6. Tim W

7. Jan G

8. Dmytro K

9. RH

 

1 Recommended solutions for "the DESY case" by SciCats Project leader

Frank will present what Max suggested after we seeked his advice for our ID disentanglement.

Speaker: Frank Schluenzen (IT (IT Benutzerservice))

scicat-options.pdf