It is indicated some records have issues, but these cannot be found in occurrence search

18127
Reporter: peterdesmet
Type: Feedback
Summary: It is indicated some records have issues, but these cannot be found in occurrence search
Resolution: Fixed
Status: Closed
Created: 2016-01-06 16:37:55.917
Updated: 2017-10-05 15:57:54.076
Resolved: 2017-10-05 15:11:21.767
        
        
Description: We just published http://www.gbif.org/dataset/3c428404-893c-44da-bb4a-6c19d8fb676a/stats. The indexing has found the following issues with the dataset:

* Country derived from coordinates: 44
* Taxon match higher rank: 167
* Country coordinate mismatch: 150

However, if you click the links for those issues, the occurrence search returns 0 records for all:

* http://www.gbif.org/occurrence/search?dataset_key=3c428404-893c-44da-bb4a-6c19d8fb676a&issue=COUNTRY_DERIVED_FROM_COORDINATES
* http://www.gbif.org/occurrence/search?dataset_key=3c428404-893c-44da-bb4a-6c19d8fb676a&issue=TAXON_MATCH_HIGHERRANK
* http://www.gbif.org/occurrence/search?dataset_key=3c428404-893c-44da-bb4a-6c19d8fb676a&issue=COUNTRY_COORDINATE_MISMATCH

The GBIF dataset metrics extension (which derives issues from the dwca download) also finds those issues, so they are recorded with the occurrence, but why can't they be found with the occurrence search?]]>
    

Author: hoefft
Comment: sounds like a metrics API sync issue
Created: 2017-10-05 15:11:21.785
Updated: 2017-10-05 15:11:21.785

Author: peterdesmet
Comment: A sync issue that has been resolved? The links still return 0 results.
Created: 2017-10-05 15:49:55.122
Updated: 2017-10-05 15:49:55.122

Author: mblissett
Created: 2017-10-05 15:57:54.076
Updated: 2017-10-05 15:57:54.076
        
The records no longer have the issues.

https://www.gbif.org/occurrence/search?dataset_key=3c428404-893c-44da-bb4a-6c19d8fb676a (in the facet on the left, under issues) shows the only issue is some fuzzy taxon matches.

http://www-old.gbif.org/dataset/3c428404-893c-44da-bb4a-6c19d8fb676a/stats now says no issues, presumably a fuzzy match wasn't considered enough of an issue to display it.