-
Notifications
You must be signed in to change notification settings - Fork 10
Open
Description
Could be for the entire workflow and/or each individual step (for the case of distributed execution)
- Where (and with what term) in the
ro-crate-metadata.jsonmetadata file would we represent this for an entire workflow? - Where (and with what term) in the
ro-crate-metadata.jsonmetadata file would we represent this for a specific step? - How should the provider be credited? Current thinking is to use an ROR + a local identifier (like a cluster name)
- Probably should be a list of identifiers, for layered systems. Example: OpenStack VMs provisioned on the de.NBI cloud, at the Freiburg University instance. (needing to give credit to OpenStack, de.NBI Cloud, and the Freiburg Uni computers)
(@mr-c has heard about instrument identifiers, but knows nothing about that beyond the existence of the concept)
Metadata
Metadata
Assignees
Labels
No labels