search

google / wikiloop-doublecheck

WikiLoop DoubleCheck: a web tool to help review Wikipedia edits easily and collaboratively.
http://doublecheck.wikiloop.org
Apache License 2.0
79 stars 53 forks source link

FR: Make clicking "Next" automatic and optional #229

Open xinbenlv opened 4 years ago

xinbenlv commented 4 years ago

The processing of diffs is much too slow. Stiki design is much better at that. I mean, after you press "Looks good", "Not sure", "Should revert", etc., WikiLoop Battlefield should just do the action and proceed to the next diff, instead of asking you to press "Next", "Revert now", etc. There is no time for that during rush hours, especially on a mobile device. Yes, sometimes it is good to have an option to see the article history and revise the revert comment, but this should be just an option, not the main algorithm. - suggested by User:Materialscientist

bhavyakaria commented 4 years ago

@xinbenlv How should it be designed? Like on pressing "Looks good" or "Not Sure", automatically proceed to the next diff but on pressing "Should revert", show the user options, "Revert Now", "Undo" & "Next". So, in the second case, no automatic movement?

xinbenlv commented 4 years ago

In fact I personally think it makes sense to stay for a little, to avoid keyboard mistakes. I have a few other ideas related to this feature:

  1. for LooksGood, show a button of "thank the author for this edit", or skip to next one. 2 for NotSure, allow reviewer to flag the revision for a second pair of eyes or if it is a fact checking issue, ask for editors with domain expertise.
  2. for ShouldRevert, allow direct revert ro jump to url. Also allow warn the user, etc.

It probably takes a bit of UX design work. I don't think my design is so far sufficient, and the design for this level of complexity is non-trivial, so we might want to have some wireframe on Figma or something similar.