gbif-pipelines
commented
6 months ago Identifier validation still failing for the dataset SORO - Herbário do Centro de Ciências e Tecnologias para a Sustentabilidade:
- Crawler attempt: 429
- Publishing organization: Universidade Federal de São Carlos
- Publishing country: BRAZIL
- Installation: speciesLink Network / INCT-HVFF IPT
- Number of occurrences indexed for this dataset at the time of the issue: 8680
- Cause: GBIF ID problems exceed 50% threshold: 100% duplicates; 9402 total records; 9402 absent records
- Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/3680568/step
New IDs sample:
Old IDs sample:
BRA:UFSCAR:SORO:9049
BRA:UFSCAR:SORO:9050
BRA:UFSCAR:SORO:9051
BRA:UFSCAR:SORO:9052
BRA:UFSCAR:SORO:9053
BRA:UFSCAR:SORO:9054
BRA:UFSCAR:SORO:8411
BRA:UFSCAR:SORO:8753
BRA:UFSCAR:SORO:8028
BRA:UFSCAR:SORO:8084Publisher email
Hello, I am contacting you from the GBIF Secretariat about a dataset published by the [SORO - Herbário do Centro de Ciências e Tecnologias para a Sustentabilidade](https://registry.gbif.org/dataset/e1278068-7d2d-44e0-8274-a46ae6ebf957) : https://doi.org/10.15468/8catgj. We noticed that the occurrenceIDs were changed. We have temporarily paused the ingestions of this dataset. As you might already know, when an occurrence record has a new occurrenceID for a given dataset, our system considers it to be a new occurrence. This means that it will be given a new gbifid and a new occurrence URL (like this one: https://www.gbif.org/occurrence/1252968762) and the old gbifid and URL will be deprecated. In this case, this means that the occurrence URLs would be deprecated when ingesting the newest versions of these datasets. We would like to check with you if those changes were intentional. Do you know if this is the case? Please let us know, thanks! We are happy to resume the dataset ingestion. Note that some users rely on those occurrence URLs and gbifids (like https://bionomia.net for example). In an attempt to improve the stability of the occurrence URLs and gbifids, we have implemented a warning system to detect these type of changes in datasets (see this news item). If the data publisher can provide us with a list of old and new occurrenceIDs per record, we can avoid the identifier and URL changes. Could that be an option? Please let us know if you have any question. Thanks! All the best,You can skip/fix identifier validation using the registry UI.
Identifier validation failed for the dataset SORO - Herbário do Centro de Ciências e Tecnologias para a Sustentabilidade:
Publisher email
Hello, I am contacting you from the GBIF Secretariat about a dataset published by the [SORO - Herbário do Centro de Ciências e Tecnologias para a Sustentabilidade](https://registry.gbif.org/dataset/e1278068-7d2d-44e0-8274-a46ae6ebf957) : https://doi.org/10.15468/8catgj. We noticed that the occurrenceIDs were changed. We have temporarily paused the ingestions of this dataset. As you might already know, when an occurrence record has a new occurrenceID for a given dataset, our system considers it to be a new occurrence. This means that it will be given a new gbifid and a new occurrence URL (like this one: https://www.gbif.org/occurrence/1252968762) and the old gbifid and URL will be deprecated. In this case, this means that the occurrence URLs would be deprecated when ingesting the newest versions of these datasets. We would like to check with you if those changes were intentional. Do you know if this is the case? Please let us know, thanks! We are happy to resume the dataset ingestion. Note that some users rely on those occurrence URLs and gbifids (like https://bionomia.net for example). In an attempt to improve the stability of the occurrence URLs and gbifids, we have implemented a warning system to detect these type of changes in datasets (see this news item). If the data publisher can provide us with a list of old and new occurrenceIDs per record, we can avoid the identifier and URL changes. Could that be an option? Please let us know if you have any question. Thanks! All the best,You can skip/fix identifier validation using the registry UI.