gbif-pipelines
commented
3 months ago Identifier validation still failing for the dataset Distribución potencial del género Ficus (Moraceae) en México:
- Crawler attempt: 276
- Publishing organization: Comisión nacional para el conocimiento y uso de la biodiversidad
- Publishing country: MEXICO
- Installation: IPTCONABIO
- Number of occurrences indexed for this dataset at the time of the issue: 885
- Cause: GBIF ID problems exceed 50% threshold: 100% duplicates; 880 total records; 880 absent records
- Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/3740992/step
New IDs sample:
Old IDs sample:
c6a8ce7126f1e5f6130d39c462b43bb1
3f7c88c2fb2d7cdfc7424de1cefe201e
0481adbfc79d9faba9d67463c8b06e7a
ba03cb3f97bd47b0ecfebbd88b9790e1
c82520ea0bd6f8bc10ee5aa46bd7e478
070b22de417907e4026f337f5d641724
2bb04522d6bc091c5406dc94d5c739f7
87118d54e7499e41af6765539b7479ac
aeb08473100aa8e18ea7a02db7c64f2f
e77f623c88fd459cfbb6d418cf3e9b56Publisher email
Hello, I am contacting you from the GBIF Secretariat about a dataset published by the [Distribución potencial del género Ficus (Moraceae) en México](https://registry.gbif.org/dataset/afa36eb1-34d3-4acf-bf5b-ace515ea0f74) : https://doi.org/10.15468/kr9an3. 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 Distribución potencial del género Ficus (Moraceae) en México:
Publisher email
Hello, I am contacting you from the GBIF Secretariat about a dataset published by the [Distribución potencial del género Ficus (Moraceae) en México](https://registry.gbif.org/dataset/afa36eb1-34d3-4acf-bf5b-ace515ea0f74) : https://doi.org/10.15468/kr9an3. 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.