to consider: edits changing proofread status #1884
Description
When we implemented some of the new proofreading features, we made it so that whenever an editor-level person changes a chant (or perhaps just saves a chant? I'm not sure on this point), they would go back to needing proofreading review.
I'm of two minds about this. In theory, it sounds like it should prevent mistakes from creeping into the site from people who change things without knowing what they are doing.
BUT this week the following happened:
-I (a proofreader) marked many chants as correct
-The student editor--who, I think, cannot see what has already been marked as correct--decided to go back and look at his earlier work (in this case, this has to be done through the edit page, because the melodies have been made invisible on the chant detail page--but I could imagine this scenario happening even if this weren't the case.)
-In some cases he changed a hyphen or two; in other cases, as far as I can tell, he changed nothing and simply saved (or I simply can't figure out what was changed, or disagree with what I had previously, or something.)
-I am now once again left with a bunch of chants to proofread which I had already corrected, and no way of knowing what the changes were and if they mattered.
At the moment, I'm resigned to just fixing the chants (again), and hoping that with better communication this doesn't happen again. But it does make me wonder whether the original idea of flagging the chants after a save is flawed. Maybe we want the editor to know his/her chant is proofread? Maybe it should even be locked to lower-level editors if proofread? Or maybe we can make it easier to work out what has been changed in a chant that's causing it to undergo review again? We have a dearth of proofreaders, so I think we'd like to not cause them to be looking at things they already dealt with...