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

If a user provides an annotated dictionary, the app ignores it but keeps the annotations #677

Closed
3 tasks done
surchs opened this issue Jan 16, 2024 · 0 comments · Fixed by #715
Closed
3 tasks done
Assignees
Labels
usability Issue affecting user or developer experience.

Comments

@surchs
Copy link
Contributor

surchs commented Jan 16, 2024

We do not yet support uploading an already annotated data dictionary (see #601). However, if a user regardless uploads an already annotated data dictionary the app will happily take it. This leads to some very confusing states:

  • if I provide a completely annotated data dictionary 🤷 then the visual state of the app will tell me nothing is annotated yet, but my download will include all my existing annotations
  • if I provide an invalid data dictionary then again, the UI looks empty, but when I come to the download page and my data dictionary is validated, the validation will fail. Unless I guess what's going on, I cannot fix that

So in short: the state of the data dictionary in the app and the visual UI do not correspond to each other, and that's quite bad.
We have two options:

  1. Teach the app to load state from a data dictionary ([ENH] Let user upload an already annotated data dictionary #601)
  2. Put a big red warning on the first page that says: you cannot load a data dictionary with neurobagel annotations

I lean towards 2 because we will likely refactor this soon

TODO:

  • when existing data dictionary is loaded, strip away / rest the "Annotations" part
  • big warning on Home page near the "data dictionary" upload button to say "cannot reuse annotations"
  • test that existing annotations do not make it through the tool, e.g. no unintentional annotations
@surchs surchs added usability Issue affecting user or developer experience. type:bug labels Jan 16, 2024
@surchs surchs added the flag:schedule Flag issue that should go on the roadmap or backlog. label Jan 16, 2024
@surchs surchs moved this to Backlog in Neurobagel Jan 16, 2024
@surchs surchs removed the flag:schedule Flag issue that should go on the roadmap or backlog. label Jan 17, 2024
@surchs surchs moved this from Backlog to Specify - Active in Neurobagel Mar 21, 2024
@surchs surchs moved this from Specify - Active to Specify - Done in Neurobagel Mar 22, 2024
@surchs surchs moved this from Specify - Done to Implement - Active in Neurobagel Mar 28, 2024
@surchs surchs self-assigned this Mar 28, 2024
@surchs surchs moved this from Implement - Active to Implement - Track in Neurobagel Apr 9, 2024
@surchs surchs moved this from Implement - Track to Implement - Active in Neurobagel Apr 9, 2024
@surchs surchs moved this from Implement - Active to Implement - Done in Neurobagel Apr 10, 2024
@rmanaem rmanaem moved this from Implement - Done to Review - Active in Neurobagel Apr 12, 2024
@github-project-automation github-project-automation bot moved this from Review - Active to Review - Done in Neurobagel Apr 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
usability Issue affecting user or developer experience.
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

1 participant