How can we connect equipment data, metadata and repositories?

Use LEAF, or a similar equipment-adapter setup, to extract data and metadata from research equipment and transfer them to the selected endpoint. Depending on the local deployment, this may include MQTT messaging, time-series storage, dashboards or additional processing components. This step should be refined by the team that operates the actual LEAF setup.

Use FAIR Data Station to capture and validate metadata about the investigation, study, observation units, samples, assays and data files. Where relevant, include references to LEAF-captured run information, instrument settings, raw files and processed outputs. The goal is to make the experimental context explicit early and to ensure that equipment data, metadata and derived files can be interpreted together. The concrete metadata profile, template fields, identifiers and controlled vocabularies should be completed by the WUR and IBISBA domain experts.

Use FAIRDOM-SEEK, or an IBISBA Knowledge Hub instance based on FAIRDOM-SEEK, to register the investigation, study, samples, assays, protocols, data files and related outputs. Access permissions, project membership, licences and publication status should be decided according to the project policy. If FAIR Data Station import is used, the exact import behaviour and metadata mappings should be confirmed with the FAIRDOM-SEEK and WUR teams.

The experiment is no longer only a collection of files and instrument exports. The operational data, sample and assay metadata, protocols, derived outputs and access conditions are connected in a platform where collaborators can discover, interpret and reuse them. This final wording should be adapted once WUR and IBISBA confirm the intended user story.