Correct, I made a mistake there. As for what the third identifier can do, they can vote “yes”, which will cancel out identifier 2’s “no” vote".
Just to be clear, I agree the casual thing is a problem and needs to be fixed, but I was also responding to the specific scenarios you mentioned and trying to go through in them in my mind as to what decisions a person might make there.
We just released a fix for this today (totally unrelated to this thread, someone on Github had decided to work on it a few weeks ago). So people will see the community taxon there now.
@loarie and I spent about an hour last night going through some observations on our test server to see how these votes are being used, and playing around with them, just to understand the scope of the problem better how to best mitigate it. For example, if someone votes on the community taxon at family and the community taxon gets moved to genus, that vote doesn’t really make any sense any longer and probably shouldn’t be applied. And yes, making that DQA not votable if the community taxon and obs taxon don’t agree is another potential improvement, although it does come with other consequences. It’s impossible to make a change that doesn’t tug on some other part of the spider web.