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

What should we return to a user for pheno-only subjects #84

Open
surchs opened this issue Feb 14, 2023 · 1 comment
Open

What should we return to a user for pheno-only subjects #84

surchs opened this issue Feb 14, 2023 · 1 comment
Labels
flag:discuss Flag issue that needs to be discussed before it can be implemented. _flag:stale [BOT ONLY] Flag issue that hasn't been updated in a while and needs to be triaged again

Comments

@surchs
Copy link
Contributor

surchs commented Feb 14, 2023

We have decided that we will support datasets where some or even all subjects have only phenotypic data, and no (BIDS) imaging data. In our current data model this means that these subjects won't have acquisition nodes, and that they also won't have file paths to their session nodes. For the API this means that there will be a mismatch between the reported number of matching subjects*sessions, and the number of returned file paths - in an extreme case where none of the matching subjects have imaging data, the list of file paths might be empty even though we are finding subjects that match the criteria.

We should discuss what information we want to return to a user in such a case.

User-facing documentation is also needed to alert the user that (currently) the list of file paths returned for a query only covers subjects with BIDS imaging data.

@surchs surchs added the flag:discuss Flag issue that needs to be discussed before it can be implemented. label Feb 14, 2023
@github-actions
Copy link

We want to keep our issues up to date and active. This issue hasn't seen any activity in the last 30 days.
We have applied the stale-issue label to indicate that this issue should be reviewed again and then either prioritized or closed.

@github-actions 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 Aug 18, 2023
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. _flag:stale [BOT ONLY] Flag issue that hasn't been updated in a while and needs to be triaged again
Projects
None yet
Development

No branches or pull requests

1 participant