Sometime in the past week, possibly since the release of v7.10.2, our existing (saved) queries have started returning Taxon ‘Full Names’ where before they returned ‘Names’. For taxa at the Genus rank or higher, this has no effect (Full Name = Name), but for taxa at the Species and Subspecies rank, the Full Name field automatically populates with the binomial or trinomial, respectively. We now have no way to query the specific or subspecific epithet alone and I don’t appear to be able to make the Name field available in queries.
We’ve heard from several users today that this issue persists in their databases after the update. For now, we’re rolling back our North American Specify Cloud deployments (including yours) to version 7.10.1 to resolve this problem in the short term. Other regions have not yet received the update.
The underlying data and queries remain unchanged; only the way the results are displayed on labels and in query results was affected.
We plan to push the update again later this week to provide a permanent solution! It will return to the previous behavior and you will once again see the ‘Names’ instead of ‘Full Names’. I apologize for the interruption, and you should already see the previous behavior when using Specify.
Replying here to request help with a separate issue in case it was introduced in the same update: our Catalog Number field format has begun forcing nine digit numbers. Where before two collection objects had catalog numbers LSUMZ 5 and LSUMZ 12345 they now return catalog numbers LSUMZ 000000005 and LSUMZ 000012345 in query results and invoice/label reports. How do we revert this change?
I can see where the nine digit format is being forced in Schema Config but I can’t identify where to fix it under App Resources > Field Formatters.
Version is still displaying as 7.10.2 although the Full Names error has been resolved. Thanks for any help you can offer,
Dave