My record is just been questioned as to having ‘plot 7’ (record: 4369 4862) in the Site Name field when clearly on the app this is free-form text to allow users to define their own site name/description. In our case it’s to differentiate between the 8 plots we have so that when the data is extracted that we have a clear defining field from which to extrapolate the data. it still has the grid referencing data attached to it so I’m not sure what the moderator was talking about in this case?
Comments
Re: Site Name
While the app might deal with site names as free-form text, it is probably helpful from a human perspective to be add a little precision. “Plot 7” is on a par with recorders who use “my garden” as a site name, in that both you and the gardening naturalists know where the site is, but the rest of us haven’t a clue.
Something like “Sutton Hams - plot 7” seems reasonable, and is not dissimilar to the names used for other plots in your study area.
Site names should contain a proper location
As well as checking the ID, part of the role of a verifier is to check that all of the other record data is correct, including the location. Data is also usually stored in a database where it can be sorted by location field. Whilst the site name field is indeed freeform, and I understand that for your local site having "plot 7" is useful, from a verifier's point of view it isn't informative (likewise people are asked not to have locations labelled "my house", "my garden" etc). A standard site name would be something that can be found on an Ordnance Survey map, so either the nearest town or village, a nature reserve name, country park etc. By doing that, the verifier can check that the name matches the grid reference and records from similar areas can be grouped together.
The simple answer to this is to include both the site name and your plot number, so the site name would be for example "Sutton Nature Reserve Plot 7" - that keeps the plot number for internal use but allows the verifier to match up the location and grid reference.
As a verifier I prefer to…
As a verifier I prefer to see location names that reflect what is seen on on OS map as this enables verifiers to check the grid ref given is approx correct. I've had a few incorrect grid refs to sort just this morning which were spotted as they didnt match the location name provided (I cross reference all records against the OS map and sometimes county council maps). Also, for someone who may use the data eg the VC recorder, who may be using downloaded data in a spreadsheet, seeing a recognisable site name is really helpful. There's no reason why you cant use your terminology at the start of the site name to aid your work, but still include the known location eg Plot 7, Somerset Wetlands NNR. I use some 'local' names on may mates farm as all his fields are named but still include the farm name and parish not just the field name.
StevenSite names are really…
Steven
Site names are really useful for various reasons. They help verifiers determine that the grid ref is approx correct for a start. Theyre also helpful to people who may use the data eg VC recorders, who may be working from downloaded data in spreadhseet form. I always try to give the name of the geoographical feature eg hill/down/dale/fen/reserve/wood and parish. Sometime though, as per my mates farm, I give the field names that he uses, but still include the farm name. If you gave 'Plot 7, Somerset Wetlands NR' then you can still pull up records by plot but the name also makes sense to other users of the data.
Jim
While the app might deal with site names as free-form text, it is probably helpful from a human perspective to be add a little precision. “Plot 7” is on a par with recorders who use “my garden” as a site name, in that both you and the gardening naturalists know where the site is, but the rest of us haven’t a clue.
Something like “Sutton Hams - plot 7” seems reasonable.