See also 2 - database procedures >>
Well, the first thing that will happen is that you will be thanked! We are always pleased to receive records, even one sighting of one moth can add to what we know about the county.
We also have a responsibility to check the records to ensure that they are accurate, as far as is humanly possible. We're keen that our records do reflect what is really happening to moths in the county, and records from the database are also shared with other organisations (see our Records Position Statement), including Butterfly Conservation and the Thames Valley Environmental Records Centre. These organisations use wildlife records to inform conservation projects and within the context of planning decisions, so again it is in everyone's interests to make the data as accurate as possible.
Incoming moth records for Berkshire are reviewed by the county verifiers (Martin Harvey and John Thacker), who check them against three main criteria:
We do our best to provide feedback to moth recorders about any interesting or unusual records, and will query anything that seems unlikely - hopefully this is always done in a polite and diplomatic way! The database procedures used to do this are described here for those who want to know the details. For some species photos or specimens may be requested, or confirmation from another recorder may be advisable. The Moth Group and the county recorder can advise on this, and see also our document listing the more difficult species.
The most important thing you can do is make sure you have documented all the relevant evidence. If you have found something unusual it is always best to get as much supporting evidence as you can to confirm the record. Such evidence might include:
If you have found a moth at an unusual time of year it's good to get a photo or keep the specimen, but also please do make a comment about it as part of your record - if someone records a summer moth in March and makes no comment about it being unusual, or having been double-checked, it looks like it could be an identification or data entry error, but if there is a comment along the lines of "this individual was exceptionally early, but it was checked carefully" that makes it clear that the recorder realised it was something out of the ordinary. See figures 1 and 2.
If you want to get help with identification from a photo you can share it via the Upper Thames Moths blog, the Berks Moth Group email group, or add it to the iSpot wildlife identification site.
Everyone makes mistakes sometimes, no matter how 'expert' they are: moths can be difficult to identify, and errors can also occur when writing down records or transcribing them onto a computer. If it is decided that a record is unsafe, it is removed from the county database and archived in a separate spreadsheet, just in case any queries subsequently arise, or further evidence comes to light.
About 1,500 records have been archived off the county database since 2007, which represents just over 1% of the almost 126,000 moth records submitted in that time. The vast majority of these have been as a result of doubt over the correct identification, followed by doubt over the date (i.e. a moth reported at an unusual time of year without supporting evidence), see Figure 3.
Of the 1,000 or so records removed due to identification problems, 618 (60%) resulted from just four common species that mistakenly get recorded at species level when they haven't been dissected:
Other species that are problematic and have to be rejected fairly often include:
and among the micros:
I'm not going to 'name and shame' any particular recorders for submitting dodgy records! Suffice it to say that there is a correlation between the total number of records made by any one person and the number of errors - in other words most people make the occasional error, and if you record more moths you will make more errors, even though the percentage rate of error is tiny. There are some well-known names in the list of people who have had records removed (and one of those people is the county recorder!).
Figure 1. This record of Small Clouded Brindle in April looked questionable, but on checking the record ...
Figure 2. ... the recorder had provided clear evidence that they realised the date was unusual and had taken steps to ensure the identification was correct.
Figure 3: main reasons for removing records from the county database, based on c. 1,500 removals since 2007