Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Occurrence count incorrect in dataset search TSV export #4468

Open
gbif-portal opened this issue Dec 13, 2022 · 3 comments
Open

Occurrence count incorrect in dataset search TSV export #4468

gbif-portal opened this issue Dec 13, 2022 · 3 comments

Comments

@gbif-portal
Copy link
Collaborator

Occurrence count incorrect in dataset search TSV export

This is an issue originally reported on helplesk. It looks like the CSV file downloadable by clicking on "DOWNLOAD as TSV" has incorrect occurrence counts. The number of occurrences indicated in the CSV is twice the amount of occurrences shown on the website.

One of our users

found 5237 occurrences for the "Type Collection of the National Herbarium of Uzbekistan (TASH)" dataset in the TSV file. But according to the web-page this dataset contains only 3955 occurrences.
There are same errors: "Phenology of Iridaceae" - 1771 occurences in the TSV file, and 1061 in the dataset web-page, also 'Phenology of Crocus' - 888 and 444 respectively, 'Phenology of Liliace' - 514 and 297, 'Chronicle of Nature - Phenology of Mammals of Surhanskiy State Nature Reserve' - 216 and 108.


Github user: @ManonGros
User: See in registry - Send email
System: Safari 16.1.0 / Mac OS X 10.15.7
Referer: https://www.gbif.org/dataset/search?publishing_country=UZ
Window size: width 1349 - height 878
API log
Site log
System health at time of feedback: OPERATIONAL

@ManonGros
Copy link

@fmendezh

@MortenHofft
Copy link
Member

MortenHofft commented Dec 13, 2022

The API recordCount says the same. https://api.gbif.org/v1/dataset/search?publishing_country=UZ if that is of help @fmendezh

@CecSve
Copy link

CecSve commented Dec 14, 2022

Not sure this is relevant, but it might be so putting it here #3187

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants