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

Track provenance of derived files #548

Closed
tsalo opened this issue Oct 1, 2022 · 3 comments
Closed

Track provenance of derived files #548

tsalo opened this issue Oct 1, 2022 · 3 comments
Assignees
Labels
enhancement New feature or request

Comments

@tsalo
Copy link
Member

tsalo commented Oct 1, 2022

Summary

BIDS Derivatives includes fields to link derived files to earlier ones (e.g., the preprocessed fMRIPrep file) and the originals in the raw dataset. We should attempt to track this information and include it in xcp_d's sidecar files.

@tsalo tsalo added the enhancement New feature or request label Oct 1, 2022
@sattertt
Copy link

sattertt commented Oct 1, 2022 via email

@tsalo
Copy link
Member Author

tsalo commented Oct 9, 2022

I think the best way to handle it is this:

  1. Set the BIDSVersion in dataset_description.json to 1.8.0 (first release after addition of BIDS URIs).
  2. Add DatasetLinks field to dataset_description.json pointing to preprocessed derivatives (e.g., "fmriprep": "relative/path/"). I think we'll need some fancy logic to determine the relative path though...
    • Actually, I think we can just use the relative path from the xcpd_dir.
  3. Use BIDS URIs for Sources field in sidecar files. E.g., bids:fmriprep:sub-01/ses-01/func/sub-01_ses-01_task-rest_desc-preproc_bold.nii.gz.
  4. Retain metadata from source files, when available.

@tsalo
Copy link
Member Author

tsalo commented Jan 19, 2024

I probably should have closed this with #966.

@tsalo tsalo closed this as completed Jan 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants