-
Notifications
You must be signed in to change notification settings - Fork 0
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
The "Next" button on the annotation page should send me to the next category, not the download page #28
Comments
We want to keep our issues up to date and active. This issue hasn't seen any activity in the last 30 days. |
Makes sense as it doesn't break the tool's 'next' paradigm so much as it slightly alters is it for this multi-step page. This would involved page jump (up) functionality, something we have yet to attempt. |
We want to keep our issues up to date and active. This issue hasn't seen any activity in the last 30 days. |
+1 for this issue - my intuition is still to click "Next" when I use the annotation tool. |
How about a "Previous" button for when you have made a mistake in the annotation? |
Hey @emiledangremont, that's a good idea! We are going to implement a lot of these older issues in a new version of the annotation tool that @rmanaem is working on here https://github.com/neurobagel/annotation-tool. I'll transfer this issue over to the new tool and we'll ping you for feedback when the first version is online |
When I click "Next" during the Annotation workflow, I should jump to the next unannotated category so that I can continue annotating. If all categories have already been annotated, then the "Next" button can transport me to the next page (e.g. the Download page).
The main goal here is to make it easier to navigate through the Annotation workflow. At the moment, the annotation workflow involves scrolling (and annotating) from top to bottom. So when you're done, you are probably near the bottom of the page and can't see the list of categories anymore (but see #33). Because the "Next" button is near the bottom of the page, it would be a natural UI element to allow the user to continue the process.
The text was updated successfully, but these errors were encountered: