Make "refined" status permanent in the DB
Opened this issue · 1 comments
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.
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.