gbif-pipelines
commented
1 month ago Identifier validation still failing for the dataset HCF - Herbário da Universidade Tecnológica Federal do Paraná Campus Campo Mourão:
- Crawler attempt: 439
- Publishing organization: Universidade Tecnológica Federal do Paraná - Campus Campo Mourão
- Publishing country: BRAZIL
- Installation: speciesLink Network / INCT-HVFF IPT
- Number of occurrences indexed for this dataset at the time of the issue: 38678
- Cause: GBIF ID problems exceed 50% threshold: 100% duplicates; 38786 total records; 38786 absent records
- Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/4193668/step
New IDs sample:
Old IDs sample:
BRA:UTFPR:HCF:38060
BRA:UTFPR:HCF:38061
BRA:UTFPR:HCF:38062
BRA:UTFPR:HCF:38063
BRA:UTFPR:HCF:38064
BRA:UTFPR:HCF:38065
BRA:UTFPR:HCF:38066
BRA:UTFPR:HCF:38067
BRA:UTFPR:HCF:38068
BRA:UTFPR:HCF:38069Publisher email
Hello, I am contacting you from the GBIF Secretariat about a dataset published by the [HCF - Herbário da Universidade Tecnológica Federal do Paraná Campus Campo Mourão](https://registry.gbif.org/dataset/dd31ac22-63d4-4bb4-a987-5eece5ffadb8) : https://doi.org/10.15468/sfdea2. 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 HCF - Herbário da Universidade Tecnológica Federal do Paraná Campus Campo Mourão:
Publisher email
Hello, I am contacting you from the GBIF Secretariat about a dataset published by the [HCF - Herbário da Universidade Tecnológica Federal do Paraná Campus Campo Mourão](https://registry.gbif.org/dataset/dd31ac22-63d4-4bb4-a987-5eece5ffadb8) : https://doi.org/10.15468/sfdea2. 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.