gbif-pipelines
commented
1 month ago Identifier validation still failing for the dataset ESA - Herbário da Escola Superior de Agricultura Luiz de Queiroz:
- Crawler attempt: 399
- Publishing organization: Escola Superior de Agricultura Luiz de Queiroz
- Publishing country: BRAZIL
- Installation: speciesLink Network / INCT-HVFF IPT
- Number of occurrences indexed for this dataset at the time of the issue: 154911
- Cause: GBIF ID problems exceed 50% threshold: 100% duplicates; 154911 total records; 154911 absent records
- Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/4165311/step
New IDs sample:
Old IDs sample:
BRA:ESALQ:ESA:151013
BRA:ESALQ:ESA:151020
BRA:ESALQ:ESA:151028
BRA:ESALQ:ESA:151032
BRA:ESALQ:ESA:151037
BRA:ESALQ:ESA:151038
BRA:ESALQ:ESA:151044
BRA:ESALQ:ESA:151053
BRA:ESALQ:ESA:151057
BRA:ESALQ:ESA:151060Publisher email
Hello, I am contacting you from the GBIF Secretariat about a dataset published by the [ESA - Herbário da Escola Superior de Agricultura Luiz de Queiroz](https://registry.gbif.org/dataset/cbf8c968-37d6-45be-bf5c-e22914a384dc) : https://doi.org/10.15468/6e9ry8. 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 ESA - Herbário da Escola Superior de Agricultura Luiz de Queiroz:
Publisher email
Hello, I am contacting you from the GBIF Secretariat about a dataset published by the [ESA - Herbário da Escola Superior de Agricultura Luiz de Queiroz](https://registry.gbif.org/dataset/cbf8c968-37d6-45be-bf5c-e22914a384dc) : https://doi.org/10.15468/6e9ry8. 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.