Loris
Loris copied to clipboard
[Conflicts Resolver] Once a selection has been made, there is no way to revert back to 'No selection'
Once a user makes a selection, whether intentionally or by mistake, the user is forced to commit to one of the options and has no way of reverting back to having no selection and having the question remain 'unresolved'. This is not ideal as users can make a selection by mistake, having no way of backing out or reverting from having to select one of the options.
Related to:
- https://github.com/aces/Loris/issues/8563
@SantiagoTG for this issue, it is ok to add a confirm change popup, that will be easy and clear for user to understand?
@kongtiaowang IIRC some people (@cmadjar? @LeighMac? can't recall who exactly) were opposed to a confirmation popup because of the time it takes to resolve multiple things if you need to acknowledge each one. Might be worth bringing up on next Tuesdays LORIS meeting?
I can see the drawback of using a pop-up of an additional confirmation step. However, the main issue here is not whether the user confirms, but that once a selection has been made, there is no way to backtrack or set that selection back to 'Null'. This is a problem if a user mistakenly clicks on a selection (If they even notice the selection being made before changing pages on the table for example).
If the user notices, going back on an erroneous selection would require the user to check the question, form and participant for which the selection was made before refreshing the page (or otherwise going to the 'Resolved Conflicts' tab, where the user can only see the final selection). If the selection is made on a participants the user has access to, perhaps it is not that troublesome, as they can check right away (if they have the original source handy), but if it is another site's participant, this becomes very difficult to trace. All in all, not being able to set a 'Null' response is troublesome, at least without giving the user the chance to review the changes to be made.
I will rethinking this feature.
need a dev meeting to discuss this feature.