ELN Consortium meeting 9 - 25th March 2025 3PM CET

[NicolasCARPi]

Open to all interested parties.

Zoom link

[SteffenBrinckmann]

Topic to discuss: #95 (comment)

[NicolasCARPi]

Conclusion: we can use variableMeasured on Files (not only Datasets)

[SteffenBrinckmann]

Topic to discuss: #105

[SteffenBrinckmann]

Topic to discuss: #56 (comment)

[NicolasCARPi]

in half an hour!

[NicolasCARPi]

AI generated crap

Quick recap

The team discussed various aspects of implementing and standardizing Electronic Lab Notebook (ELN) systems, including variable measurements, data signing, and file format specifications. They made decisions on attribute usage, agreed to test compatibility with a new version of the standard, and planned for future documentation and showcasing of different ELNs. The conversation ended with scheduling the next meeting and assigning homework tasks to team members.

Next steps

Simon to define the 5 types for additional_type and create URIs for them

All participants to check if their exported files comply with the RO-Crate 1.2 draft specification before the next meeting

All participants to export and import each other's .eln files and provide screenshots for documentation purposes

Steffen to add the Streamlit app for quick .eln file compliance checking to the project resources

Sydney to share the link for the Elab.ftw community meeting with the group

Summary
Variable Measurements in System Implementation

The team discussed the implementation of variable measurements in their system, with Florian expressing concerns about its validity. They decided to keep it as close to a valid RO crate as possible and allow for the use of different properties from other entities. Mark joined the meeting late due to technical issues with their robot. The team agreed to update their specification to mention that variable measurements can be used but are not required.

Introducing ELN Systems and Workflow Automation

The group introduces themselves, with each participant sharing their name and role in developing various Electronic Lab Notebook (ELN) systems or related platforms. Mark Durr from the University of Greiswald describes his project, Lara suite, which is a comprehensive research data management system with API-first development, focusing on lab workflow automation and potential AI integration. He emphasizes the importance of generating semantics and metadata directly from the workflow to reduce the need for additional user input.

ELN File Format Attribute Changes

The group discusses the use of genre and additional type attributes in the ELN file format. They decide to move the ELN measurement information into the additional type attribute, replacing the current use of genre. Simon agrees to take the lead on defining the five core types and their corresponding URIs. The decision is made to use proposal one, which involves using additional type for more precise semantic information, while genre can remain for general categorization. This change will require those who have already implemented the format to replace "genre" with "additional type" in their code.

Verifiable Credentials for Data Signing

Simon proposed using the verifiable credentials standard for data signing, which is used by data space initiatives like Katina X and Gaia X. He suggested storing the signature in the JSON document and using the MiniSign library. Nicolas clarified that the signature should exist outside of the metadata JSON file. Simon also suggested that each lab could sign its contribution to the whole dataset, creating multiple data sets with signatures. Mark asked if blockchain technology could be used to chain the hashes, creating a unique blockchain of files.

Version 1.2 Compatibility and Transition

The group discusses the potential switch from version 1.1 to the draft version 1.2 of a standard, likely related to blockchain or data management. Florian raises concerns about compatibility and validation issues, while others suggest testing the new version before fully adopting it. They agree to make this a homework assignment for the next meeting, where everyone will check if their exported files comply with the 1.2 specification. The team also considers using internal versioning to manage the transition and potential breaking changes.

Year-End File Import and Streamlit App

The team discussed the documentation and the process of importing each other's year-end files. They also discussed the creation of a small streamlit app for fast checking of Eln files. The idea of showcasing different Elns and their features was proposed, with a suggestion for a public version of the Eln consortium community meeting. The next meeting was scheduled for September 27th.