Issue 18085

Dataset has locality data but no occurrences are displayed

Reporter: rdmpage
Assignee: jlegind
Type: Feedback
Summary: Dataset has locality data but no occurrences are displayed
Description: Another Biofresh dataset that has lats and longs, and seems to be valid Darwin Core Archive, but does not seem to have been indexed (see also DM-269)
Resolution: Fixed
Status: Closed
Created: 2015-12-14 19:02:48.448
Updated: 2017-10-05 15:00:25.746
Resolved: 2017-10-05 15:00:25.729

Created: 2015-12-14 19:07:21.149
Updated: 2015-12-14 19:07:21.149
Having not investigated other than to check logs:

Finished validating DwC-A for dataset [5221e970-757c-43cb-bdd4-2f085bf36ae4], valid? is [false]. Full report [DwcaValidationReport{datasetKey=5221e970-757c-43cb-bdd4-2f085bf36ae4, invalidationReason=null, occurrenceReport=OccurrenceValidationReport{checkedRecords=1965, uniqueTriplets=0, recordsWithInvalidTriplets=1965, uniqueOccurrenceIds=0, recordsMissingOccurrenceId=1965, allRecordsChecked=true, invalidationReason=Archive invalid because [100% invalid triplets is > than threshold of 25%; 1965 records without an occurrence id (should be 0)], valid=false}, genericReport=null}]

Author: rdmpage
Comment: OK, so the data fails to parse because the occurrences lack unique identifiers. How does the user know this? How does the data provider know that their archive has a problem? As far as BioFresh are concerned it's job done, they've uploaded data to GBIF. Any thoughts on adding flags to datasets like this so people can see the problem and fix it? Would be great if we had a staging area (like GitHub) where we could sort these issues out. Won&it it be nice to have little badges on the GBIF repositories flagging data issues (just like we have for software issues). There's lots of interesting data that GBIF is not making the most of :(
Created: 2015-12-15 00:10:38.928
Updated: 2015-12-15 00:10:38.928

Comment: The publisher has been contacted about this issue.
Created: 2015-12-17 12:17:11.67
Updated: 2015-12-17 12:17:11.67

Comment: And contacted again...
Created: 2017-05-02 10:51:16.981
Updated: 2017-05-02 10:51:16.981