Issue 11295

gbif-parsers: create type status parser to interpret type status

11295
Reporter: kbraak
Assignee: mdoering
Type: Improvement
Summary: gbif-parsers: create type status parser to interpret type status
Priority: Major
Status: Open
Created: 2012-06-06 12:22:13.124
Updated: 2013-12-06 16:50:01.156
        
Description: The type status enum will exist (see blocking issue). The type status will be used as an interpreted enum. A parse will be responsible for the interpretation:

1) The parser will have to interpret from recognised but not enum-identical values to the enum.

2) The parser will also have to check against a blacklist for values that need no re-inspection (obvious non-type vocabulary - see http://code.google.com/p/gbif-indexingtoolkit/source/browse/trunk/synchroniser-gbif/src/main/resources/org/gbif/harvest/portal/synchronise/excludedTypeStatuses.txt)

-----
Outside the scope of the issue, we will need to try and support handling of non-blacklisted but non-enum-mapped values coming in with indexing (add to mapping / add to blacklist)]]>
    


Author: kbraak@gbif.org
Comment: [~mdoering@gbif.org] can you confirm that you have written a type status interpreter as part of the occurrence widening work we began?
Created: 2013-12-06 11:48:19.062
Updated: 2013-12-06 11:48:19.062


Author: mdoering@gbif.org
Created: 2013-12-06 16:49:51.849
Updated: 2013-12-06 16:49:51.849
        
https://code.google.com/p/gbif-common-resources/source/detail?r=1838

this parses the type status, but does not yet extract the typified name. It also does not use any blacklist, but that might not really be needed, does it?