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

Enable parsing of BIDS dataset with data dictionary #27

Closed
7 tasks done
surchs opened this issue Jan 3, 2023 · 2 comments
Closed
7 tasks done

Enable parsing of BIDS dataset with data dictionary #27

surchs opened this issue Jan 3, 2023 · 2 comments
Assignees
Labels
Epic A collection of issues that are related by topic and can be addressed together.
Milestone

Comments

@surchs
Copy link
Contributor

surchs commented Jan 3, 2023

This tracks the work to create a bagel add-bids subcommand that does this:

Inputs:
(1) pheno.jsonld generated by bagel pheno
(2) BIDS dataset directory path
(3) maybe: the path on the host computer of the BIDS dataset
Output: pheno_bids.jsonld

A user who has already run bagel pheno (#32) successfully to create a pheno.jsonld file should be able to use this subcommand to add imaging metadata (BIDS) to the existing pheno.jsonld file. The imaging metadata to add are:

  • the type of imaging acquired during a session as Acquisition
  • the absolute file system path of a session directory in the BIDS dataset

Expectations (for now):

  • subject IDs in the pheno.tsv and the corresponding BIDS directory will be the same.
  • there may be subjects in the pheno.tsv file that do not exist in the BIDS directory (i.e. pheno only)
  • if a subject does not exist in the BIDS dir, it will remain in the .jsonld with only the existing phenotypic metadata
  • if a subject has multiple acquisitions of the same type in the same session (e.g. several T1s), then they should be added as separate acquisitions to the session (i.e. you can have more than one T1 in a session)

Things to do:

@surchs surchs added this to Neurobagel Jan 3, 2023
@surchs surchs converted this from a draft issue Jan 3, 2023
@surchs surchs added this to the v0.1.0 milestone Jan 9, 2023
@surchs surchs added the Epic A collection of issues that are related by topic and can be addressed together. label Jan 9, 2023
@surchs surchs moved this from Inbox to Backlog in Neurobagel Jan 10, 2023
@surchs surchs moved this from Backlog to Ready in Neurobagel Jan 10, 2023
@surchs surchs pinned this issue Feb 17, 2023
@alyssadai alyssadai self-assigned this Feb 20, 2023
@alyssadai alyssadai moved this from Ready to Blocked in Neurobagel Feb 20, 2023
@alyssadai alyssadai moved this from Blocked to Doing in Neurobagel Feb 20, 2023
@alyssadai
Copy link
Contributor

@surchs I think this one can be closed as well, but want a second pair of eyes before doing so.

@surchs
Copy link
Contributor Author

surchs commented Mar 15, 2023

@alyssadai agreed! Let's close 🎉

@github-project-automation github-project-automation bot moved this from Doing to Done in Neurobagel Mar 15, 2023
@alyssadai alyssadai unpinned this issue Mar 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Epic A collection of issues that are related by topic and can be addressed together.
Projects
Archived in project
Development

No branches or pull requests

2 participants