Reset "can the Community Taxon still be confirmed or improved?" after taxon swap

As a result of taxon swap 42539, observation 4176663 went from the genus level to the family level (“Some or all of the identifications affected by this split may have been replaced with identifications of Picidae. This happens when we can’t automatically assign an identification to one of the output taxa.”)

Because the observation had a “No, it’s as good as it can be” vote for the “Based on the evidence, can the Community Taxon still be confirmed or improved?” DQA question and such observations are marked casual when the community ID is family-level or higher, the observation was thus made casual, which seems like an unintended consequence. Perhaps it would be more appropriate to, in such cases, reset any existing votes for that DQA question and notify the previous voters that their votes need to be re-evaluated and potentially recast.

Another idea was to remove all votes whenever the community taxon changes.

8 Likes

Seems like that could make it pretty easy for anyone with an agenda to wipe out the previous votes, by adding (and then maybe deleting again) an ID, at least on observations where one ID can still change the CID.

4 Likes

Or at the very least do some kind of a “refresh” of the records. It’s been discussed in at least one other thread how opted-out folks’ taxon-swapped species will fall into Casual even without any votes either way. (I recently found and fixed a number of snakes, but there’s still a pile of decent woodpecker observations in the “gray hole”.)

2 Likes