T6: Execution details

[RenskeW]

Additional information about the workflow execution itself.

• EX1 Timestamps: When the workflow was executed, at step-granularity. The timestamps can be helpful when files were downloaded during workflow execution, especially from a database without clear versions. In addition, the duration of the execution may be important during workflow development (test different settings) and when reproducing the workflow.
• EX2 Consumed resources: The resources used during execution, at step-granularity. This is different from what was described in T5, because there we only described what was available, not what was actually used.
• EX3 Workflow engine: Software, therefore with the same metadata as general software entities (T3).
• EX4 Human agent: At a minimum, a PID such as ORCID should be included, or name and email of the person who ran the workflow. These details may be important for attribution (U2), and can also be used by third parties to ask further questions about the research.

[RenskeW]

What is represented in CWLProv RO in RDF:

EX1 Timestamps:

• Step execution start and end timestamps
• Workflow execution start and end timestamps

EX3 Workflow engine:

• Name
• Version

EX4 Human agent:

• Name
• ORCID

[RenskeW]

Results of analysis of RO-Crates converted by runcrate from CWLProv RO Bundles:

• EX1 - Timestamps: Timestamps are included at workflow and step granularity, see Scenario 1.
• EX3 - Workflow engine: Defined with name and version, see Scenario 1
• EX4 - Human agent: Included with name and ORCID, if present in CWLProv RO Bundle. See Scenario 1.

[RenskeW]

Suggested enhancement 1:

Include the persistent identifier of the workflow engine, if it exists.