1 Topic by cwdee

  • cwdee
  • Member
  • Offline
  • Registered: 03-06-2015
  • Posts: 48

Topic: How to implement record validation workflow

I have records submission working in Drupal 7 against the test warehouse using an instance of General Purpose Data Entry Forms / Sample with occurences form and am displaying the mostly recently submitted records on a webpage using a custom report to extract data from cache_occurrences (thanks, Jim, for you help with this) and formatted in a custom PHP function.

Now my client wishes to add a moderation workflow, so that records only appear on their website once approved. Is this workflow something that Indicia supports?

The process would need to be something like:
1) anonymous (not logged-in) user enters a record through existing form, where in Default values I assume I set occurrence:record_status to something other than 'C'. What are the valid values of record_status?
2) moderator (logged in to Drupal) views the records and approves or rejects each record, which causes the record_status in the warehouse to be change from [unvalidated_record_status_value] to 'C' or [rejected_record_status_value]. Is there an Indiciai form to do this?   
3) the approved records are displayed on the webpage using the existing custom report extended to include subsetting on record_status='C'.

Thanks in anticipation, Chris

Chris Dee
Garganey Consulting

2 Reply by Jim Bacon

  • Jim Bacon
  • Veteran
  • Offline
  • From: BRC
  • Registered: 03-11-2008
  • Posts: 980

Re: How to implement record validation workflow

Hi Chris,

Yes, verification is a core feature of Indicia.

Values for record_status are
  I - in progress,
  C - completed,
  V - verified,
  R - rejected,
  T - test.

The values of I and C are set from the recorder's perspective so a value of C means that it is released for verification.

The verification process can then set a coarse value of V or R. There is a verification prebuilt form for exactly this purpose.

Because this did not meet the needs of verifiers there is now an additional record_substatus field which the latest verification form (version 5) can also set.

Values for record_substatus are
  1 - accepted as correct,
  2 - accepted as considered correct,
  3 - plausible,
  4 - not accepted as unable to verify,
  5 - not accepted, incorrect.
  Null for unchecked records.

Record_status is set to V for 1 and 2, left as C for 3, and set to R for 4 and 5.

Indicia also has a system for determining which users can verify which species groups but that is beyond my experience.

There are two entirely different ways that you can proceed with this. One is to build the verification form in to your own website and work with your own community of verifiers in an isolated way. The alternative is to share the records gathered through your website with iRecord. That enables the verifiers and verification system built in to iRecord to be applied to your records.

Here are some additional resources.
http://indicia-docs.readthedocs.org/en/ … ments.html
https://www.youtube.com/watch?v=tSVy-zb … e=youtu.be (possibly a bit dated)
http://www.brc.ac.uk/irecord/about

Jim Bacon.