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

Make "refined" status permanent in the DB #83

Open
mzur opened this issue Oct 25, 2021 · 1 comment
Open

Make "refined" status permanent in the DB #83

mzur opened this issue Oct 25, 2021 · 1 comment

Comments

@mzur
Copy link
Member

mzur commented Oct 25, 2021

In the refine steps for proposals/candidates the counter of the "seen" proposals/candidates is reset on page reload. If a refine tasks takes very long, this can be annoying as you need to cycle through many proposals/candidates that you have already refined. Store the "refined" state permanently in the DB. Refined proposals/candidates are automatically skipped in the refine steps. Maybe implement a switch (in a new options tab) to disable this behavior.

Also visually distinguish refined proposals/candidates from the not yet refined ones.

A proposal/candidate is set as refined when it is focussed in the refine view and the user either changes the size/position or navigates on to the next proposal/candidate.

@mzur
Copy link
Member Author

mzur commented Oct 25, 2021

This idea can be extended for the refinement of annotation candidates. Here, a "progress bar" could be displayed in the sidebar above the label trees, that shows the progress (similar to the "x of y seen" message for the training proposals). Maybe replace the message for the training proposals with the progress bar, too.

@mzur mzur moved this to High Priority in BIIGLE Roadmap Oct 25, 2021
@mzur mzur moved this from High Priority to Medium Priority in BIIGLE Roadmap Oct 25, 2021
@mzur mzur removed the student label Oct 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Medium Priority
Development

No branches or pull requests

1 participant