Interpret identification date in the same way as event date

12808
Reporter: mdoering
Type: Story
Summary: Interpret identification date in the same way as event date
Priority: Major
Status: Open
Created: 2013-02-22 22:33:40.297
Updated: 2016-02-15 13:45:38.633
DueDate: 2013-03-08 00:00:00.0
        
Description: In downloads I see quite a lot of broken identification dates with values like this coming from the details webservice:
{code}identificationDate: "0002-11-29T23:00:00.000+0000"{code}
http://staging.gbif.org:8080/occurrence-ws/occurrence/19692445]]>
    

Author: omeyn@gbif.org
Comment: The identificationDate is currently not interpreted, so what you're seeing is a verbatim string from the publisher. We can add interpretation, using the same parsing as for the "occurrence date", for example. What would you rather see if we have something unparseable, like the example?
Created: 2013-03-04 10:13:33.847
Updated: 2013-03-04 10:13:33.847

Author: mdoering@gbif.org
Comment: An interpreted field just as we do with collection date should exist, yes. We should revisit how we represent dates though, as we need to be able to deal with various accuracy (year,month,day,hour,minute) and be able to do range queries on date/timestamps
Created: 2013-03-04 10:43:49.271
Updated: 2013-03-04 10:43:49.271

Author: omeyn@gbif.org
Comment: After further discussion: we'll interpret identificationDate into a ms-since-epoch long, and leave it null if interpretation fails. If all we can get is year we'll set to jan 1 of that year, if we have year and month we set to the start of that month.
Created: 2013-03-04 21:40:25.855
Updated: 2013-03-04 21:40:25.855