S-D6 Provenance and Change History of (Derived) Data and Models Y4M03

[KZzizzle]

in this sprint:

• agree with DAT- on approach
• plan implementation

A key factor in achieving reproducibility lies in being able to track changes, reproduce previous states, and understand relationships between evolving data/model items. For that purpose, versioning/branching and/or change log concepts are required (on the dataset/data file/model/... level). Robust concepts are also required for frequently evolving items and derived data.

• Tracking of provenance and change
• Robust concept for frequently evolving items; git-based for scripts and models: users can specify an own git repository (with credential) or select a SPARC one. o2S2PARC then makes it easy to push specific versions (milestones) of developing scripts and models. It is possible to specify, when an older such version should be used instead of the newest one.
• Robust concept for derived data (e.g., from computational modeling, or data analyses)

this also demands synchronization with DAT- and K-CORE