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

[ENH] Let user upload an already annotated data dictionary #601

Open
1 of 5 tasks
surchs opened this issue Nov 2, 2023 · 1 comment
Open
1 of 5 tasks

[ENH] Let user upload an already annotated data dictionary #601

surchs opened this issue Nov 2, 2023 · 1 comment
Labels
feat:add The first minimal viable change that implements a new functionality. feedback:feature request Request for a new functionality or for an enhancement. type:feature Effort to deliver new features, feature changes & improvements

Comments

@surchs
Copy link
Contributor

surchs commented Nov 2, 2023

Is there an existing issue for this?

  • I have searched the existing issues

New feature

When I have already used the annotator once to create a neurobagel annotation tool, I would like to be able to use the file I have generated as an input to the annotation tool the next time I use it.

i.e.:

  • data dictionary upload accepts neurobagel data dictionary .json
  • we parse the neurobagel portion of the user supplied data dictionary
  • the app state gets set to reflect the user supplied data dictionary
  • inputs get validated: Validate supplied .tsv and .json files #49

Unclear documentation

No response

@surchs surchs added feedback:feature request Request for a new functionality or for an enhancement. feat:add The first minimal viable change that implements a new functionality. type:feature Effort to deliver new features, feature changes & improvements labels Nov 2, 2023
Copy link

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!

@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 Jan 17, 2024
@alyssadai alyssadai added flag:schedule Flag issue that should go on the roadmap or backlog. and removed flag:schedule Flag issue that should go on the roadmap or backlog. labels Mar 26, 2024
@github-actions github-actions bot removed the _flag:stale [BOT ONLY] Flag issue that hasn't been updated in a while and needs to be triaged again label Mar 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feat:add The first minimal viable change that implements a new functionality. feedback:feature request Request for a new functionality or for an enhancement. type:feature Effort to deliver new features, feature changes & improvements
Projects
Status: No status
Development

No branches or pull requests

2 participants