Page 1 of 1

Confirmed (not in wild)

Posted: Thu Mar 08, 2018 2:03 pm
by AndyAmphlett
Tom,

While BSBI has guidelines on where to record, occasionally a record arrives at the DDb that is subsequently found to fall outwith the guidelines. For example this record of Salix lanata:

https://database.bsbi.org/record/2cd4p9h.bpzt8r

Pete Stroh queried it as a new hectad record of a Scarce species. I checked with the recorder, and it turns out that the bush was planted within her garden, and so should not have been recorded. (The record arrived via an unrelated dataset of fungi records via a LRC). The species is correctly identified, and the other details are correct, but the record should not be mapped, and should not really be returned by default queries. The option of rejecting the record seems wrong, as that signifies that the record is erroneous, when it is not. Perhaps there should be a validation category of Confirmed (not in wild) or something similar?

Andy.

Re: Confirmed (not in wild)

Posted: Sat Mar 10, 2018 10:27 am
by jdsh
Status = planted would seem an obvious choice.

Re: Confirmed (not in wild)

Posted: Sat Mar 10, 2018 3:14 pm
by admin
We're planning to add a separate 'do-not-map' flag to cover valid records of occurrences from non-wild situations.

This has some overlap with 'planted' ('deliberate introduction') status but would also cover unintentional presence of aliens in non-wild situations.

Re: Confirmed (not in wild)

Posted: Fri Mar 23, 2018 10:43 am
by AndyAmphlett
See - viewtopic.php?f=4&t=372#p1036 - for details of the new 'Do not map' validation option.