[Gusdev-gusdev] proposal for ReviewStatus

[Steve F. <sfi...@pc...>]

Folks-

we have been discusing ReviewStatus.

here, as far as i can tell, are the use cases, in order of commoness:
  (a) loading data into a table that expects a review status (eg, 
features),  but where none of the data has been reviewed
  (b) updating data in a table that uses review status, and the logic 
states that rows that have been reviewed should not be updated
  (c) loading data that is tagged with a review status, but using a 
vocabulary determined by the data provider, not by the database
  (d) curating data locally, which would use the review status 
vocabulary stored in the db.

my goals are :
  (1) to remove the requirement that gus installations use ReviewStatus
  (2) to allow sites that want to use it to be responsible for 
developing and loading their own ReviewStatus CV.

Here is my proposal:
  - make ReviewStatus nullable in all tables that use it
  - null is synonymous with "not reviewed"
  - plugins that load data for use case (a) above can just leave 
ReviewStatus null
  - plugins that need to know what review status means "don't update" 
offer a --reviewedCode argument that solicits from the user the name of 
the review status that means "don't update"
  - plugins that need to load ReviewStatus values from a data provider's 
input offer a --reviewStatusMap argument that takes a file specifying 
the mapping from input values to database values
  - curation applications read the review status CV stored in the 
database and offer it in a pulldown to the curator

The immediate action for GUS 3.5 would be:
  - name ReviewStatus nullable
  - upgrade supported plugins to conform to this proposal

comments?

steve