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

Feedback #138

Open
rmanaem opened this issue Aug 1, 2023 · 2 comments
Open

Feedback #138

rmanaem opened this issue Aug 1, 2023 · 2 comments
Labels
feedback:user feedback Feedback from our users. Either direct issue submission or conveyed feedback someday Not a priority right now, but we want to keep this around to think or discuss more.

Comments

@rmanaem
Copy link
Collaborator

rmanaem commented Aug 1, 2023

  • Would it be possible to be able to distinguish between resting state and task-based fMRI in the Imaging modality field?
  • Support for vars reflecting sociodemographic characteristics that are important in open/population datasets but are underexplored, to highlight existing datasets that collect these data: race, SES, educational attainment
@rmanaem rmanaem added the feedback:user feedback Feedback from our users. Either direct issue submission or conveyed feedback label Aug 1, 2023
@Remi-Gau
Copy link
Contributor

Remi-Gau commented Aug 1, 2023

  • Would it be possible to be able to distinguish between resting state and task-based fMRI in the Imaging modality field?

you local BIDS maintainer here:

  • this may be hard because even though BIDS recommends to label resting state data as "task-rest" it is not enforced, so you may get false positive and negative

BTW for the cohort creator I have started listing the task name present in each dataset (not for each participant / session though).

see here: https://github.com/neurodatascience/cohort_creator/blob/main/cohort_creator/data/openneuro.tsv

@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 _flag:stale label to indicate that this issue should be reviewed again.
When you review, please reread the spec and then apply one of these three options:

  • prioritize: apply the flag:schedule label to suggest moving this issue into the backlog now
  • close: if the issue is no longer relevant, explain why (give others a chance to reply) and then close.
  • archive: sometimes an issue has important information or ideas but we won't work on it soon. In this case
    apply the someday label to show that this won't be prioritized. The stalebot will ignore issues with this
    label in the future. Use sparingly!

@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 Sep 21, 2023
@surchs surchs 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 Nov 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feedback:user feedback Feedback from our users. Either direct issue submission or conveyed feedback someday Not a priority right now, but we want to keep this around to think or discuss more.
Projects
Status: No status
Development

No branches or pull requests

3 participants