Conference & Editorial Board

Minutes of Editorial Board Meeting

Date: October 1, 2025
Location: zoom

1. Distribution of Tasks within the Board

• Responsibilities for reviewing abstracts, conference talks, proceedings, and speaker selection were assigned and extended (apart from ex-officio members & Technical Coordination) through nomination of new members:
• Mariana Petris → TRD
• Andrey Kugler → FSD
• Christian Müntz → MVD
• Karl-Heinz Kampert → RICH
• Norbert Hermann (excused) → TOF
• Lokesh Kumar → MUCH

+

• Rudi Schmidt → STS
• Anton Andronic → PWG
• Volker Friese → Computing

2. Procedure for Abstract and Talk Handling

• Current process remains for the time being based on existing Wiki and INDICO:
• Announcements via conference mailing list.
• Upload of abstracts, talks, proceedings handled manually.
• Board members assign themselves for the review if the topics fall under their expertise

3. Editorial Board Section on CBM Web Page

• Planned content:
• Board Members list.
• Wiki documentation migrated to web page
• Link to archives (publications, theses, talks).
• Publication Policy.
• Question raised on creation & maintenance: whether handled by CBM department or CBM collaboration

4. Archiving of Publications, Theses, Talks

• Options under discussion:
• GSI repository (host-lab-based solution).
• CBM-owned solution (similar to ALICE, requires a dedicated group and long-term support).

5. Workflow for Publication Process

• Presently defined in Publication Policy and handled manually via INDICO.
• Reference cases discussed:
• STS paper (example of current workflow).
• Talks with Jerome Lauret (STAR) and Udo Kurilla (PANDA) in January 2025 on respective solutions
• Both use DRUPAL, which seems to be outdated
• FAIR Data Management talk by Andrew Mistry in March 2025.
• seems not suitable or adaptable for our purpose
• Ongoing internal discussions with GSI Research Director on host-lab-based solution

Karl-Heinz showed the system used by Auger, which would pretty much suit our needs. He will inquire with the collaboration on the framework used.

6. Decisions Taken

• For the time being, both solutions will be pursued in parallel:
• GSI host-lab-based repository.
• CBM’s own development of archives and publication workflows.
• An intermediate solution (e.g., based on Redmine or GSI forum) may be considered, but carries the risk of becoming a permanent fix rather than temporary.
• At the upcoming coll. meeting a contribution will be made in the Collaboration Board outlining the needs and requirements, seeking groups to take over this effort (not excluding direct contacts)

7. Outlook

• Long-term solutions will depend on sustainability of support and integration with host-lab data management systems
• Further input expected from ongoing discussions with GSI and FAIR management.
• Similarly, any CBM proprietary solution needs the long-term support of a CBM group