You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.json metadata file would we represent this for an entire workflow?
Where (and with what term) in the ro-crate-metadata.json metadata 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)
Could be for the entire workflow and/or each individual step (for the case of distributed execution)
ro-crate-metadata.jsonmetadata file would we represent this for an entire workflow?ro-crate-metadata.jsonmetadata file would we represent this for a specific step?(@mr-c has heard about instrument identifiers, but knows nothing about that beyond the existence of the concept)