Mesibov
commented
7 months ago (Please note that I am not responding as a GBIF staff member, because I have no association with GBIF.)
The dataset from which the occurrence record is derived (Natuurmuseum Brabant, Tilburg - Observations, https://www.gbif.org/dataset/8487c83f-4022-44f3-a93d-9c3e1ba10997) has 41076 records, all with valid "eventDate" entries with the format YYYY-MM. Furthermore, all "year" and "month" entries agree with "eventDate" entries.
However, apart from the one record with "occurrenceID" NMB993900157361, the "day" field has a valid entry (1-31). For example, in the record you cite, "year" is 2016, "month" is 1 and "day" is 6.
Why, then, is "eventDate" "2016-01" instead of "2016-01-06"? Why is "eventDate" YYYY-MM for 41076 records, when for 41075 records it could be YYYY-MM-DD? I would interpret "2016-01" as meaning "some day in January 2016" (see here), but it was not "some day", it was 6 January.
Recorded date mismatch
Please indicate why an accurate date, including day of recording, results in a recorded date mismatch. This apllies to all days in all records. GBIF empties the field day entry, replaces/interprets it with an empty field and calls it a mismatch.
Github user: @slieker User: See in registry - Send email System: Firefox 124.0.0 / Windows 10.0.0 Referer: https://www.gbif.org/occurrence/4089224985 Window size: width 1760 - height 850 API log&_a=(columns:!(_source),filters:!(),index:'3390a910-fcda-11ea-a9ab-4375f2a9d11c',interval:auto,query:(language:kuery,query:''),sort:!())) Site log&_a=(columns:!(_source),filters:!(),index:'5c73f360-fce3-11ea-a9ab-4375f2a9d11c',interval:auto,query:(language:kuery,query:''),sort:!())) System health at time of feedback: OPERATIONAL datasetKey: 8487c83f-4022-44f3-a93d-9c3e1ba10997 publishingOrgKey: 84834ee7-dc9f-4085-abee-13fa7bb47c7d