v7.10.2.2
I noticed something strange in query results yesterday. Lots identified as a taxon which had its Preferred Taxon updated in our Taxon Tree a few months ago are still bearing the previous Preferred Taxon. Both taxa occur in query results as the Preferred Taxon for the same determined Taxon.
This is incorrect behavior. It appears that the user can force the update to the new Preferred Taxon by updating the current determination record (in any way, even saving a version with no change committed) for an affected lot, but this should be done automatically when the Taxon Tree is updated.
Not sure exactly how long it’s been like this, but I just noticed it. I can see that I changed the synonymy on 2024-11-09, and all records created or modified since then have the correct Preferred Taxon, whereas all records with determinations created or modified before that date have an incorrect Preferred Taxon. I’ve found records with this issue as far back as August, so it has nothing to do with 7.10.2, and has likely been the behavior since I have started using specify, I just hadn’t noticed until now.
See below: a query performed today, showing the same Taxon ID having two different Preferred Taxon IDs in the same result set.
Determination record with incorrect Preferred Taxon, unedited since synonymy was changed:
Upon committing an edit (entering a space in “Verbatim Determination” field, immediately deleting it, and hitting save), the Preferred Taxon is correct:
