Verification status attribute for records

[GoogleCodeExporter]

Each record to have an attribute for verification status based on a controlled 
vocabulary as used in Recorder (Correct, Considered Correct etc).  Needs to be 
standard for use on NBN Gateway as well.  Need consultation and agreement on 
the combination of factors that equate to each status, i.e. recorder certainty, 
ID difficulty, outputs of automated rules (where they exist), verifier's 
decision, whether records were examined individually or bulk verified etc

Original issue reported on code.google.com by PaulaNBN@gmail.com on 26 Sep 2013 at 8:34

[GoogleCodeExporter]

This is open for discussion - we need a thorough way of categorising the state 
of a record which might not be a simple case of 1 attribute. I can think the 
following flags which might operate independently to some extent:

1) Record input in progress vs Record input complete
2) Record has an unfulfilled request for peer review (i.e. blocked from 
verification & reports until reviewed by a friend or group member)
3) Record has an unfulfilled request from a verifier for more information 
(queried).
4) Verifier has marked the record as: incorrect beyond reasonable doubt, likely 
to be incorrect, likely to be correct, correct beyond reasonable doubt
5) Verifier has marked the record as insufficient evidence (similar to 3, 
except we are accepting the record is not likely to get more evidence so this 
is a completion state).
6) Record marked as possibly correct by a non-expert (i.e. peer review passed 
by a group member).
7) Record marked as likely to be correct by the system (maybe common & easy to 
ID species which pass all rules).

You might combine these flags in a way that a single status attribute does not 
allow, e.g. an important record could be "likely to be correct" AND queried, 
since you'd like to make this one "definitely correct".  

Original comment by johnvanb...@gmail.com on 20 Nov 2013 at 8:40

[GoogleCodeExporter]

Agree, this is all still to be discussed as part of the NBN Technical Strategy. 
 Some of the points above are already in the working document on record-level 
quality tags, but 1, 2 and 6 are not, as the 'record in progress' and peer 
review functionality is a recent development. Another new factor which might 
need to be considered is 'grades' of confidence in georeferenced marine data as 
recently suggested. It is up to the steering group but I think that to 
facilitate data use there should be one (main) (simple!) attribute for record 
quality, but the various independent contributing factors should continue to be 
stored separately as part of the record.  

Original comment by PaulaNBN@gmail.com on 20 Nov 2013 at 9:24

[GoogleCodeExporter]

Change to medium priority until agreement on revisions needed

Original comment by dr.david...@gmail.com on 17 Jun 2014 at 12:31

• Added labels: Priority-Medium
• Removed labels: Priority-High