Workshop Goal Statement & Schedule

[PeterKraus]

Goals

The main objective of the workshop is to develop a set of interoperability prototypes for communication of sample information between different RDM tools, with the aim of arriving at a defined standard. Along the way, we have identified the following challenges:

• ontologisation of structured but non-ontologised data, i.e. "how do I use an ontology" as a RDM tool author
• cross-ontology mapping, i.e. "how can I translate between ontologies as a user to construct secondary datasets"
• do we need to enforce a certain ontology for sample management, e.g. should samples be allowed to be stateful or restricted to be immutable? Can these two philosophical viewpoints be unified?
• focusing on interoperability between small tools, i.e. easing the burden for implementing RDF / JSON-LD on RDM tool authors

For this purpose, we'd like you to self-organise into smaller teams, implementing this sample data transfer between two (ideally unaffiliated) RDM tools. The teams should ideally comprise:

• a "data expert", i.e. someone who provides or at least understands the structure of the data
• at least two "RDM tool experts", i.e. someones who are comfortable with the APIs of the two tools to be linked

Organisational

Sample data archive:

We encourage everyone to contribute one or several sample data archives they consider typical in their work and are happy to share openly. Please upload your data here as a zip file, in any of the formats you can export (please include raw data where possible too), accompanied by an .md or .txt readme file with a short description (please consider this format for the readme).

Where possible, we intend to publish the collected data on Zenodo after the workshop using a permissive license (CC-BY or similar).

Code archive:

In order to keep track of the work developed at the workshop, we would like your interoperability prototype to be committed into its own separate GitHub repository under the MADICES organisation. We can furnish people with specific repositories for this purpose, otherwise please just make a branch or fork of MADICES/MADICES-projects. Please include, where appropriate:

• a short README describing:
  • authorship information,
  • what sample data from the above archive is required,
  • any installation instructions,
  • a short usage description,
  • any ideas for future plans or extensions.

Schedule

3rd pre-event meeting - March

• by this meeting, we would like the attendees to tell us what:
  • sample data they make available for the workshop (ideally related to catalysis or electrochemistry, but other areas are also fine)
  • APIs of which RDM tools they are comfortable with
  • classes of RDM tools they are interested for their interoperability case study (to facilitate matching)
• during and after this meeting, we can start defining the teams

Workshop

For the workshop itself, we have 2 rooms at the Zuse Institute:

• a large lecture room, where the "plenary" sessions will be held
• a smaller conference room, where we expect the bulk of the implementation work to happen in "breakout" sessions

The up-to-date dynamic schedule will be maintained on the CECAM site for the workshop.

Below are listed the "plenary" sessions.

"Case study" sessions will involve discussions of particular challenges and solutions relevant to the specific field, and can incoporate some amount of ad hoc show & tell of e.g., exemplar datasets, knowledge graphs, ontologies and data capture platforms.

Workshop Day 1 - Afternoon, 22nd of April

• Plenary:
  • Registration and admin issues (from 12:00)
  • Welcome and introduction (13:30)
  • Recap of the above project goals (14:00)
  • Overview of the gathered sample data (14:15)

Workshop Day 2 - Morning, 23rd of April

• Plenary: Discussion of the above mentioned challenges (09:00)
• Parallel: Team formation (11:00)

Workshop Day 2 - Afternoon, 23rd of April

• Plenary: Case study: Electrochemistry
• Plenary: Case study: Catalysis

For these case study sessions, we'd encourage short ad hoc contributions (~10 minutes) describing any ontologies (BATT-INFO, voc4cat), tailored tools (visualisation dashboards), or demos of existing projects.

Workshop Day 3 - Morning, 24th of April

• Plenary: A short recap of Day 2, followed by:
• Implementation session

Workshop Day 3 - Afternoon, 24th of April

• Implementation session

Hackathon - Evening 24th of April

The evening session is intended as a more free-form, creative hackathon, possibly on topics not covered by the workshop.

Workshop Day 4 - Morning, 25th of April

• Plenary: Demos of interoperability prototypes and any hackathon projects
• Plenary: Summary & Next steps for MADICES
  • Here we will decide e.g., which projects we wish to continue working on as a community through future meetings, and whether we can write a useful paper describing our findings at this workshop (in addition to the mandatory CECAM report).