Commit 09adf446 authored by Timm Schoening's avatar Timm Schoening
Browse files

Add new file

parent cfcc8aa3
## Provenance documentation:
Provenance documentation of (automated) SOP steps is required to enable reusability of data and validity checks. Provenance information needs to document the agent, entities and activities and should facilitate reproducibility but mainly document execution steps rather than enable the fully-automated re-execution which would further require the automated setup of the software environment (e.g. through Docker). Provenance of individual SOP steps should be recorded in a machine-readable fashion (i.e. a **yaml** file) like so:
```
provenance:
- action:
executable:
name: <executable name>
version: <version string of executable>
parameter:
- name: <param-x_name>
value: <param-x_value>
[hash: <md5 hash of file at <param-x_value> (optional, only for files)>]
- name: <param-y_name>
value: <param-y_value>
hash: null
time: <time of execution: in utc, human-readable, with milliseconds (%Y%m%d %H:%M:%S.%f%z)>
- action:
executable:
...
parameter:
...
hash: <sha256 hash of previous provenance file>
time: ...
```
In case an additional processing step applied to a entity, the additional provenance information shall be appended to the provenance file of the entities' creation. Together with the SHA256 hash of the previous provenance file, a blockchain-like behaviour is enabled.
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment