Recording provenance of workflow runs with RO-Crate

Authors

LEO Simone CRUSOE Michael R RODRÍGUEZ-NAVAS Laura SIRVENT Raül KANITZ Alexander PAUL De Geest WITTNER Rudolf PIREDDU Luca GARIJO Daniel FERNÁNDEZ José M COLONNELLI Iacopo GALLO Matej OHTA Tazro SUETAKE Hirotaka CAPELLA-GUTIERREZ Salvador DE WIT Renske KINOSHITA Bruno P SOILAND-REYES Stian

Year of publication 2024
Type Article in Periodical
Magazine / Source PLOS ONE
MU Faculty or unit

Institute of Computer Science

Citation
web https://doi.org/10.1371/journal.pone.0309210
Doi http://dx.doi.org/10.1371/journal.pone.0309210
Keywords provenance; computational workflows; RO Crate; Common Provenance Model;
Description Recording the provenance of scientific computation results is key to the support of traceability, reproducibility and quality assessment of data products. Several data models have been explored to address this need, providing representations of workflow plans and their executions as well as means of packaging the resulting information for archiving and sharing. However, existing approaches tend to lack interoperable adoption across workflow management systems. In this work we present Workflow Run RO-Crate, an extension of RO-Crate (Research Object Crate) and Schema.org to capture the provenance of the execution of computational workflows at different levels of granularity and bundle together all their associated objects (inputs, outputs, code, etc.). The model is supported by a diverse, open community that runs regular meetings, discussing development, maintenance and adoption aspects. Workflow Run RO-Crate is already implemented by several workflow management systems, allowing interoperable comparisons between workflow runs from heterogeneous systems. We describe the model, its alignment to standards such as W3C PROV, and its implementation in six workflow systems. Finally, we illustrate the application of Workflow Run RO-Crate in two use cases of machine learning in the digital image analysis domain.

You are running an old browser version. We recommend updating your browser to its latest version.

More info