Please fill out the following sections to the best of your ability, it will help us investigate bugs if we have this information at the outset. Screenshots are especially helpful, so please provide those if you can.
Platform (Android, iOS, Website): website
Browser, if a website issue (Firefox, Chrome, etc) : Firefox
Description of problem (please provide a set of steps we can use to replicate the issue, and make as many as you need.):
The former planthopper superfamily Fulgoroidea was split into Fulgoroidea s.s. and Cixioidea. Consequently old Fulgoroidea IDs were changed to Fulgoromorpha. In doing so, disagreeing IDs using Fulgoroidea were replaced with nondisagreeing ones of Fulgoromorpha, causing old incorrect species IDs to resurface. One has to manually add an additional disagreeing ID in order to clear them out. This particular species is a problem because it’s an invasive species in several places but the CV keeps incorrectly choosing it for almost any planthopper.
This is a known issue. I don’t know if it qualifies as a bug but at least there’s a workaround that can be used to restore the disagreeing IDs after the fact. The problem can occur as a result of the simplest taxon change, such as name change.
Please fill out the following sections to the best of your ability, it will help us investigate bugs if we have this information at the outset. Screenshots are especially helpful, so please provide those if you can.
Platform (Android, iOS, Website): all
rest not relevant
Description of problem (please provide a set of steps we can use to replicate the issue, and make as many as you need.):
Observations in genus Rubus that had some nonsensical (typically CV-assisted) ID to an unlikely species sometimes received disagreeing ID’s as Rubus fruticosus Complex. After Rubus fruticosus Complex was swapped to Section Rubus https://www.inaturalist.org/taxon_changes/122502, the ID’s are no longer disagreeing and the observations again show up with the incorrect species name.
It is certainly quite vexing. I am currentoy the top identifier of Rubus armeniacus in my country although I have never seen it and never issued it as an ID. It is quite rare but CV insists on IDing every other bramble using this name.
Has there been any progress in dealing with this? I was just about to report the same thing, having found several observations with the same issue (such as https://inaturalist.ala.org.au/observations/7573575). Knowing that the disagreement can be reinstated isn’t really a help when I assume most people don’t realise their disagreement has been removed.
the next ID has to deliberately add back DISagreement. I have learnt to check that CID algorithm is ‘keeping up at the back’ with the intention of my ID. Delete, repeat, till we do agree.
Which is fine if you’re adding an ID, but who would expect a taxon swap to mean that you need to revisit any ID you might have ever given of that taxon and check it was correctly disagreeing?
Workaround for a bug - till iNat resolves the issue. It was still Needs ID, so someone would have picked it up eventually. I anyway sweat blood over untangling the CID algorithm - which is working as intended. But not as expected by the identifier.
