gbif-pipelines
commented
1 month ago Identifier validation still failing for the dataset MCP-Repteis - Coleção de Répteis:
- Crawler attempt: 296
- Publishing organization: Museu de Ciências e Tecnologia - PUCRS
- Publishing country: BRAZIL
- Installation: speciesLink Network / INCT-HVFF IPT
- Number of occurrences indexed for this dataset at the time of the issue: 19868
- Cause: GBIF ID problems exceed 50% threshold: 100% duplicates; 19868 total records; 19868 absent records
- Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/4199485/step
New IDs sample:
Old IDs sample:
https://specieslink.net/guid/291/19754
https://specieslink.net/guid/291/19752
https://specieslink.net/guid/291/19753
https://specieslink.net/guid/291/19563
https://specieslink.net/guid/291/19564
https://specieslink.net/guid/291/19565
https://specieslink.net/guid/291/19566
https://specieslink.net/guid/291/19567
https://specieslink.net/guid/291/19568
https://specieslink.net/guid/291/19569Publisher email
Hello, I am contacting you from the GBIF Secretariat about a dataset published by the [MCP-Repteis - Coleção de Répteis](https://registry.gbif.org/dataset/dd760e14-7304-40a3-8d53-8aba23f569ce) : https://doi.org/10.15468/2lm0qf. 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 MCP-Repteis - Coleção de Répteis:
Publisher email
Hello, I am contacting you from the GBIF Secretariat about a dataset published by the [MCP-Repteis - Coleção de Répteis](https://registry.gbif.org/dataset/dd760e14-7304-40a3-8d53-8aba23f569ce) : https://doi.org/10.15468/2lm0qf. 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.