FEDS M2.3.1: Define the minimum metadata set for projects, access decisions and federation operations

[alexhambley]

Goal

TBD

Outputs

• Draft minimum metadata set

[douglowe]

Background reading (FOCUS-5): https://zenodo.org/records/19366020

DataSHIELD - is a notebook style tool, but doesn't currently output metadata suitable for populating a 5-Safes RO-Crate.

DataSHIELD produced metadata relevant to their governance lifecycle.

[douglowe]

Tasks:

• look at DataSHIELDS metadata, and decide how useful this is for us
• Investigate real-world access pdf documents, determine what is machine actionable (or, at least, ro-crate capturable data)

Questions:

• Are 'projects' useful for real-world TRE usage? How do we deal with sequential projects, which operate on the same data within a TRE (without moving the data out of the TRE in-between projects)?
• How are 'access decisions' made in real-world TREs? Can we move away from human-readable (only) data stored in pdfs?
• Federation operations - how do we capture this considering governance, TRE boundaries. What about the output crate - one output crate per TRE or per project, or built from multiple output crates?

[douglowe]

Excel to ro-crate material:

• https://www.ldaca.edu.au/resources/user-guides/crate-o/convert-spreadsheet/#template
• https://github.com/language-Research-Technology/ro-crate-excel

[douglowe]

5-Safes summary: https://ukdataservice.ac.uk/help/secure-lab/what-is-the-five-safes-framework/

[douglowe]

https://github.com/eScienceLab/Five-Safes-RO-Crate/blob/main/Five%20Safes%20RO-Crate%20v0.5.md