URLs (aka web addresses) of any relevant observations: observations/383145794
Screenshots of what you are seeing:
Description of problem:
Step 1:If I upload an observation identified to species, and a subsequent identifier IDs it to subspecies, the observation becomes RG.
Step 2:If I upload an observation identified to subspecies, and a subsequent identifier IDs it to species, the observation remains “needs ID”.
Step 3:Not a bug exactly, and apparently an issue that has been around since 2019 but it would be nice if it cound be fixed. I’m not a coder, so I don’t understand the complexity of the issue.
This is intentional because it honors the observers original ID. If the observer’s ID is species, then a subspecies ID will agree with that so it can be RG at species. If the observer’s ID is subspecies, making it RG after just a species ID would mean displaying species as the observation taxon and not subspecies as originally IDed. This would “override” the observer’s original ID in a sense, and I think some users don’t like that. Another subspecies ID will make the observation RG at subspecies.
The only real alternative is to have two systems, so the species can be needs ID at subspecies but RG at species. This seems excessively complicated and confusing to me, though.
Personally, I think it should go the other way. I think that the system should recognize that there is agreement at the species level, but insufficient support at the subspecies level. The order of the IDs shouldn’t really matter.
But I don’t care that much about the community ID anymore, so I’m not going to argue about it.