Apparently invalid dates are tossed without setting the issue

15993
Reporter: mdoering
Assignee: cgendreau
Type: Bug
Summary: Apparently invalid dates are tossed without setting the issue
Description: http://www.gbif.org/occurrence/search?ISSUE=RECORDED_DATE_INVALID yields no results, very unlikely
Priority: Critical
Status: Open
Created: 2014-06-24 14:58:03.755
Updated: 2016-08-11 09:14:47.391
        
    

Author: trobertson@gbif.org
Created: 2016-03-30 14:02:53.745
Updated: 2016-03-30 14:02:53.745
        
It seems flagging prefers unlikely, not invalid:
  http://www.gbif.org/occurrence/search?DATASET_KEY=c779b049-28f3-4daf-bbf4-0a40830819b6&ISSUE=RECORDED_DATE_UNLIKELY
    

Author: cgendreau
Created: 2016-08-11 09:14:47.391
Updated: 2016-08-11 09:14:47.391
        
I resused RECORDED_DATE_UNLIKELY in the new date parser which is probably a mistake.
The comments in OccurrenceIssue are clear, I think I should change the parser to match the comments:
{code}
/**
   * A (partial) invalid date is given, such as a non existing date, invalid zero month, etc.
   */
  RECORDED_DATE_INVALID,

  /**
   * The recording date is highly unlikely, falling either into the future
   * or represents a very old date before 1600 that predates modern taxonomy.
   */
  RECORDED_DATE_UNLIKELY,
{code}