-
Notifications
You must be signed in to change notification settings - Fork 5
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
Support multiple participant ID columns in tabular data #286
Labels
flag:discuss
Flag issue that needs to be discussed before it can be implemented.
someday
Not a priority right now, but we want to keep this around to think or discuss more.
Comments
alyssadai
added
flag:discuss
Flag issue that needs to be discussed before it can be implemented.
flag:schedule
Flag issue that should go on the roadmap or backlog.
labels
Mar 26, 2024
We need to think about the scenario where some subjects in the tabular file have BIDS data, but not all. |
alyssadai
changed the title
Support non-BIDS participant IDs in tabular data?
Support multiple participant ID columns in tabular data
Mar 27, 2024
alyssadai
removed
the
flag:schedule
Flag issue that should go on the roadmap or backlog.
label
Mar 27, 2024
We want to keep our issues up to date and active. This issue hasn't seen any activity in the last 75 days.
|
github-actions
bot
added
the
_flag:stale
[BOT ONLY] Flag issue that hasn't been updated in a while and needs to be triaged again
label
Jun 11, 2024
alyssadai
added
someday
Not a priority right now, but we want to keep this around to think or discuss more.
and removed
_flag:stale
[BOT ONLY] Flag issue that hasn't been updated in a while and needs to be triaged again
labels
Sep 28, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
flag:discuss
Flag issue that needs to be discussed before it can be implemented.
someday
Not a priority right now, but we want to keep this around to think or discuss more.
We keep encountering TSVs that have a participant ID column without the
sub-
prefix required for BIDS subdirectories.This makes sense, as most likely the phenotypic/tabular data will have preceded the BIDS conversion step for most datasets.
Right now, the only option for these kinds of tabular data to work with the Neurobagel CLI is if the data owner adds another column for the BIDS participant IDs, or modifies their existing participant ID column. This is probably not ideal, and also means that we are sometimes creating extra work for data owners only if they have imaging data in addition to phenotypic data.
We should consider having the CLI handle this work by automatically prepending
sub-
onto a given participant ID column if the prefixes don't already exist, before doing the imaging-tabular subject matching check.The text was updated successfully, but these errors were encountered: