Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Generalize Pipelinedescription from BEP003 for raw "BIDS" #369

Open
yarikoptic opened this issue Nov 13, 2019 · 0 comments
Open

Generalize Pipelinedescription from BEP003 for raw "BIDS" #369

yarikoptic opened this issue Nov 13, 2019 · 0 comments
Labels
enhancement New feature or request opinions wanted Please read and offer your opinion on this matter

Comments

@yarikoptic
Copy link
Collaborator

Any "raw" BIDS dataset is not given by god or a scanner, it is either result of manual labor, a script under code/ or use of helper tools such as heudiconv. The mere presence of sourcedata/ supports that claim. But nowhere in BIDS (dataset_description.json) we have formalized fields/form to inform provenance for the dataset. Currently it is only BEP003 (common derivatives) and future BEP on provenance #368 which touch upon that topic. As proper provenance tracking is a bigger job todo, we could at least implement in "raw" BIDS Pipelinedescription approach from BEP003.

@yarikoptic yarikoptic added enhancement New feature or request opinions wanted Please read and offer your opinion on this matter labels Nov 13, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request opinions wanted Please read and offer your opinion on this matter
Projects
None yet
Development

No branches or pull requests

1 participant