gbif-pipelines
commented
2 weeks ago Identifier validation still failing for the dataset Prospección de náyades y larvas de odonatos en ríos del País Vasco - Sistema de Información de la Naturaleza de Euskadi:
- Crawler attempt: 83
- Publishing organization: Basque Government
- Publishing country: SPAIN
- Installation: Basque Government installation
- Number of occurrences indexed for this dataset at the time of the issue: 51
- Cause: GBIF ID problems exceed 50% threshold: 100% duplicates; 397 total records; 397 absent records
- Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/4284024/step
New IDs sample:
Old IDs sample:
010eb66a-2533-4bfb-a55b-3f46c85b6697
04fb3a4f-ea47-451c-99ca-04cdb60fc380
0d7cac4e-a658-47db-ad72-81605a27c9f4
0f06f4e6-006c-43b1-a3c0-fbe6498807a5
140590a5-7f05-44ed-b490-694c91c3782d
1a4a20c6-6da8-45ac-8c40-2cd3481714a2
2c7adc08-03e6-4ee8-997b-36290de77f91
2d8ff8ea-1ddf-4008-9c27-b9129dd59aac
31acf5cc-8a64-4bff-b2c0-ec488f277132
34b43b7f-0091-4ab5-b314-2cee70ebd70dPublisher email
Hello, I am contacting you from the GBIF Secretariat about a dataset published by the [Prospección de náyades y larvas de odonatos en ríos del País Vasco - Sistema de Información de la Naturaleza de Euskadi](https://registry.gbif.org/dataset/35ad4e15-8230-4f5a-9c1f-c86cf57ec14d) : https://doi.org/10.15468/gjm7mx. 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 Prospección de náyades y larvas de odonatos en ríos del País Vasco - Sistema de Información de la Naturaleza de Euskadi:
Publisher email
Hello, I am contacting you from the GBIF Secretariat about a dataset published by the [Prospección de náyades y larvas de odonatos en ríos del País Vasco - Sistema de Información de la Naturaleza de Euskadi](https://registry.gbif.org/dataset/35ad4e15-8230-4f5a-9c1f-c86cf57ec14d) : https://doi.org/10.15468/gjm7mx. 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.