gbif / ingestion-management

Tracking of data issues seen during data ingestion processes
Apache License 2.0
1 stars 0 forks source link

Identifiers validation failed for dataset Colección Ornitológica de la Universidad Industrial de Santander #1592

Closed gbif-pipelines closed 4 weeks ago

gbif-pipelines commented 1 month ago

Identifier validation failed for the dataset Colección Ornitológica de la Universidad Industrial de Santander:

New IDs sample:
Old IDs sample:

UIS:UIS-O-1476
UIS:UIS-O-1474
UIS:UIS-O-1475
UIS:UIS-O-1477
UIS:UIS-O-1478
UIS:UIS-O-1479
UIS:UIS-O-1480
UIS:UIS-O-1481
UIS:UIS-O-1482
UIS:UIS-O-1483
Publisher email Hello, I am contacting you from the GBIF Secretariat about a dataset published by the [Colección Ornitológica de la Universidad Industrial de Santander](https://registry.gbif.org/dataset/34ca7b9c-6a2f-465e-9cac-7d71c792c670) : https://doi.org/10.15472/w2sefh. 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.

EstebanMH-SiB commented 1 month ago

The publisher told us that it is not possible to connect old occurrenceIDs with the new ones, so we can proceed indexing this one

gbif-pipelines commented 1 month ago

Identifier validation still failing for the dataset Colección Ornitológica de la Universidad Industrial de Santander:

New IDs sample:
Old IDs sample:

UIS:UIS-O-1476
UIS:UIS-O-1474
UIS:UIS-O-1475
UIS:UIS-O-1477
UIS:UIS-O-1478
UIS:UIS-O-1479
UIS:UIS-O-1480
UIS:UIS-O-1481
UIS:UIS-O-1482
UIS:UIS-O-1483
Publisher email Hello, I am contacting you from the GBIF Secretariat about a dataset published by the [Colección Ornitológica de la Universidad Industrial de Santander](https://registry.gbif.org/dataset/34ca7b9c-6a2f-465e-9cac-7d71c792c670) : https://doi.org/10.15472/w2sefh. 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.