OpenNeuro feedback

[rmanaem]

Hi folks, the query tool is up and running here.
We would like for you to give us feedback on the tool from the perspective
of an openneuro user, who would use it to search for sample level cohorts of openneuro data (see roadmap: OpenNeuroOrg/openneuro#2807).

In its current state the query tool:

• has access to some but not all open neuro datasets (~170 datasets)
• has up-to-date options for diagnosis, imaging modality, etc
• has two output tsv files available for download
  • dataset-level contains: dataset portal uri, dataset file path, dataset name, number of matching subjects, and available imaging modalities
  • participant level contains: dataset file path, subject id, age, sex, diagnosis, session id, session file path, number of sessions, and imaging modality
• doesn't have options for assessment

We'd love to get your feedback on:

• overall functionality
• content and format of the output tsv files
• UI experience
• anything else you notice or have thoughts on

Please add your feedback as comments on this issue or if it is very extensive, a GDoc/Hackpad could also work.

[kimsin98]

A small list of observations:

• More info about result datasets in general
  • Long dataset names are cut off (ellipses) without any way to view the full name
  • Dataset names could link to corresponding URI
  • How many total subjects are in the dataset?
  • (fluff) Distribution of age/diagnosis/etc.
• Need ability to select multiple diagnosis/assessments/modalities ([ENH] Enabled pheno level session for response and query #112)
• Purple feedback button obscures dataset results download button
• Several neurobagel URLs are dead links (documentation, dataset ID)

[rmanaem]

@kimsin98 Thanks for the feedback!

[github-actions]

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]

We want to keep our issues up to date and active. This issue hasn't seen any activity in the last 75 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!