We encourage members of the Sussex Botanical Recording Society to use iRecord to submit records.
Members recording in monads that span VC boundaries are upset to find a random number of their records being allocated to the 'wrong' VC when they are doing a survey. They are upset for two reasons:
- The recording was in 'their' VC so want the records logged as such
- The verifier (me) cannot 'see' the records and so cannot verify them. As the neighbouring VC doesn't have anyone verifying plant records, they will remain in limbo indefinitely.
I can't imagine there is an easy solution to this, but could you explain how iRecord deals with records allocated to squares that span VC boundaries?
Also, perhaps it would be possible to alter the way iRecord presents records to verifiers based on VC settings, allowing them access to all records in, say, tetrads, monads and smaller squares which straddle the boundary? This may be a way to get arround this issue: if a verifier had access like this, they could allocate the VC to the record as part of their verification process, based on their local knowledge (or after direct queries to those submitting the records)?
Many thanks
Nevil
Is this because they are only entering records with 4 fig ie monad grid refs or does this happen if they record to much higher resolution eg 10m (8 fig OS grid ref)?