This repository contains BIDS Extension Proposal 028 : BIDS-prov, a provenance framework for BIDS.
Interpreting and comparing scientific results and enabling reusable data and analysis output require understanding provenance, i.e. how the data were generated and processed. To be useful, the provenance must be understandable, easily communicated, and captured automatically in machine accessible form. Provenance records are thus used to encode transformations between digital objects.
Camille Maumet (@cmaumet) and Satrajit Ghosh (@satra) are the BEP co-moderators. Here is the list of all contributors (emoji key):
-
Stefan Appelhoff (@sappelhoff)🤔
-
Yaroslav Halchenko (@yarikoptic)🤔
-
Hermann Courteille (@hermann74)💻👀📖 🐛
-
Thomas Betton (@thomasbtnfr)💻👀📖 🐛
-
Cyril Regan (@cyril-data)💻👀📖 🐛
This project follows the all-contributors specification. Contributions of any kind welcome!
The Neuroimaging Data Model (NIDM) is a collection of specification documents that define extensions the W3C PROV standard for the domain of human brain mapping.
BIDS-prov is a BIDS extension that is compatible with NIDM.
Our goal is to extends BIDS to be able to track provenance at every stage of an experiment.
For this purpose we have to propose changes to the BIDS specification.
The BIDS specification is rendered as a webpage at https://bids-specification.readthedocs.io.
The website is built from a GitHub repository that consists of mostly markdown files at https://github.com/bids-standard/bids-specification. If you don't know much about markdown, here's a good intro guide.
The BEP028 is in a google doc.
The group is always open to new contributors interested in neuroimaging data sharing. To participate in discussions or to ask any question, please email us at incf-nidash-nidm@googlegroups.com.
Mature building blocks of NIDM:
To obtain data in bids-prov format, you can use the developed parsers.
We are committed to building a welcoming and harrasement free experience for all our contributors. As a contributor to the BIDS-Prov specification, we ask you to follow our code of conduct
Credits: This README was build based on the BEP001 README.