search

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 CM Vertebrate Paleontology Collection #822

Closed gbif-pipelines closed 9 months ago

gbif-pipelines commented 1 year ago

Identifier validation failed for the dataset CM Vertebrate Paleontology Collection:

Hello,

I am contacting you from the GBIF Secretariat about a dataset published by the CM Vertebrate Paleontology Collection : https://doi.org/10.15468/hw4khc. 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.

dbloom commented 11 months ago

@ktotsum FYI - still working through the ID lists with the folks at the CM. Close to resolution.

gbif-pipelines commented 9 months ago

Identifier validation still failing for the dataset CM Vertebrate Paleontology Collection:

New IDs sample:

Old IDs sample:

urn:catalog:CM:VertPaleo:089587
urn:catalog:CM:VertPaleo:089579
urn:catalog:CM:VertPaleo:089577
urn:catalog:CM:VertPaleo:089578
urn:catalog:CM:VertPaleo:089586
urn:catalog:CM:VertPaleo:089585
urn:catalog:CM:VertPaleo:089581
urn:catalog:CM:VertPaleo:089582
urn:catalog:CM:VertPaleo:089580
urn:catalog:CM:VertPaleo:089726
Publisher email Hello, I am contacting you from the GBIF Secretariat about a dataset published by the [CM Vertebrate Paleontology Collection](https://registry.gbif.org/dataset/6720aee6-2aad-446d-bb97-ba009d1b5666) : https://doi.org/10.15468/hw4khc. 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.