We noticed this a couple of days ago too. I can confirm that we have seen Otters appearing with a common name of Dotterel in versions of R6. I think it was version 6.7 with the dictionary patch Steve release, but I can't be sure. However, the version of the dictionary we have does not exhibit this problem. Steve supplied us with an updated version of the dictionary to fix a problem with Bitterns mentioned in another post, so I can only assume this is an issue that has been fixed.

I'll post a heads-up to this thread in the species dictionary forum in case the folk from the NHM can shed any light.

Charles

Further to the earlier message, checking last week's data-entry has thrown up a few more anomalies. Essentially, I encourage use of the Rec.3 checklist & then more specialised lists the species is not present, however this approach is now under review after some odd examples.

Volunteers are generally non-specialists, so they will type in the common name, press return, choose from list & go from there. So we now get

• Cormorant-shows up as “Double-crested Cormorant” -Phalacrocorax carbo. This is most likely to be Great Cormorant, however what’s really odd is that “Double-crested Cormorant” doesn’t exist on the Rec.3.3 list, although that is what is displayed as the checklist in the report. Double-crested Cormorant -Phalacrocorax auritus is on the BIRDS NHM/BOU checklist, which has not been chosen.
• Curlew- shows up as “Stone-Curlew”- Numenius arquata. This is a different family. Stone-Curlew is Burhinus oedicnemus.
• Red Grouse- shows up as “Willow Ptarmigan”- Lagopus lagopus. This is not the preferred name.

The way I'm finding these errors is running a site speciifc report which has 3 columns: Taxon_Common_Name, Taxon_Latin_Name and Taxon_name, then visually comparing differences. My worry is that if these errors are more systematic, then they will be harder to identify like this.

We are using Version 6.7.2.77 of 16 March 2006. It was installed directly onto the server without being upgraded from a previous version. Is there a dictionary update around that will cover these anomalies? Has anyone else found other quirks outwith the Charles’ Bittern  or nameserver errors?