BEP028
This repository contains BIDS Extension Proposal 028 : BIDS-prov, a provenance framework for BIDS.
Our goal
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.
Who is building BEP 028 ✨
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!
BIDS-prov in the NIDM project
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.
How to help
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.
Finding information and getting in touch
Google doc
The BEP028 is in a google doc.
Contact BIDS-Prov
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.
Additional resources
Mature building blocks of NIDM:
Run parsers on the SPM, FSL and AFNI data
To obtain data in bids-prov format, you can use the developed parsers.
Code of conduct
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.
1 maintainer
Metadata
1 maintainer
Release files for bids-prov 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| bids_prov-0.1.0.tar.gz | 11.0 kB | Without provenance | Details for bids_prov-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| bids_prov-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for bids_prov-0.1.0-py3-none-any.whl |
Total release size: 22.5 kB
Release files / bids_prov-0.1.0.tar.gz
| Download URL | bids_prov-0.1.0.tar.gz |
|---|---|
| Size | 11.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1aaec81ed9446270710d12485b3efa8167af488e66ce411d878cef2cf83f6df8
|
|
BLAKE2b-256 checksum How to use checksums |
50231543198049958d299e73b0586b6d2f9ec2dc146999e7a228c359d0e7c9e8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.10.11
|
Release files / bids_prov-0.1.0-py3-none-any.whl
| Download URL | bids_prov-0.1.0-py3-none-any.whl |
|---|---|
| Size | 11.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b5e7d3ad198ca66f3c42c4935abe191f00cf758b765044b0e2049dafe3e04cf8
|
|
BLAKE2b-256 checksum How to use checksums |
f0eed678e43924c61901dcf7b119588011784b7a5f91fb4ac26f524219639f48
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.10.11
|
Security for bids-prov 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
