Automatically add DQA 'Yes' vote when adding more specific ID to RG observation at higher rank

Platform(s), Website:

URLs Derived from my comment which was approved as solution to the following thread https://forum.inaturalist.org/t/remove-no-votes-from-the-can-the-id-be-improved-dqa-when-the-observation-taxon-improves/86440:

Description of need:
Since the most recent alteration to the system, a more specific ID added to a RG observation at a higher rank (i.e. with ‘No the CID cannot be improved’), makes that observation casual. Inexperienced users are frequently caught out by this counter-intuitive result, and indeed often do not notice the effect of their action. Many perfectly verifiable observations are inadvertantly ‘casualled’ this way, and it is widely agreed to be problematic.

Feature request details:

  1. The key element of the proposal is that if an observation has been DQA’d to RG at a high rank, adding an ID more specific than that rank should automatically add a ‘Yes, the CID can be improved’ vote in the name of the refining identifier. This would have the effect of returning *most* such observations to the NeedsID pile for further consideration, which is probably what the identifier actually wants, whilst maintaining the record of other identifiers’ ‘no’ votes. Whilst a more comprehensive solution may be possible, this relatively simple change would resolve the issue except in the relatively unusual cases where more than one person has already voted ‘no’.

  2. The implementation of this proposal would be improved if adding such an ID was accompanied with an explanatory pop-up. It is difficult to word such a pop-up in a way that is brief, but if it simply demonstrates to a user that their ID will have an implication they have not understood - that would still be of benefit! I suggest a wording similar to the below:

[In the Data Quality Assessment (hyperlink to explanation) part of this observation, [list of ‘no’ voters] have/has voted that the ID [current ID] cannot be improved upon with the evidence provided. Since your ID is more specific than this, by adding this ID you will also add a vote for ‘yes the community taxon can be improved’.]

Then either…

[As a result, this observation will cease to be Research Grade, and be returned to the community for further identification. Do you still wish to add this ID?]

or

[The ‘no’ votes will still outweigh the ‘yes’ votes, therefore this observation will cease to be Research Grade and become a Casual observation because the Observation ID will disagree with the community consensus. Do you still wish to add this ID?]

  1. A bit of an aside, but perhaps the wording of the ID being ‘improved’ would be improved… if it were made a little more neutral, e.g. Can the CID be made more specific Yes/No? The wording of the above would then need to be changed to “[list of ‘no’ voters] have voted that the ID [current ID] cannot be made more specific with the evidence provided.”

In my opinion if this is implemented the wording on the popup warning should be made in a way that it is clear that by adding the id you are explicitly disagreeing with the person who said the id can’t be improved. If it’s not too complicated it could even be nice to add the disagreement in the identification itself similar to how taxon disagreements are listed saying “x-user disagrees that the id cannot be improved”

I think disagreements are very valuable in this application because you can see that there are different opinions and can reevaluate to make sure you are sure and that you aren’t missing something that the other person saw. I think it is great to be able to disagree and fix mistakes and it is best to do that with intention.

This kind of explicit text can hopefully also ward off well meaning users who are just trying to help something get to species without knowing that that particular observation/taxon may not be identifiable to species.

One of the things that makes the DQA tricky is that it is not linked with a particular ID, but with the observation; the person who ticks the DQA does not even have to add an ID themselves.

There was some text added to indicate the current community taxon beside the DQA, but it isn’t necessarily the case that this was the same at the time when the DQA vote was added. At present, the DQA votes are erased if the community taxon changes, but if the idea of this feature request is that countervotes would be added instead of erasing votes, it would no longer be possible to reconstruct what taxon the DQA originally referred to.

Another disadvantage of DQA instead of ID / comment is that there is no date attached to the DQA. No way to tell where (when) that opinion fits in the sequence.