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 Garden Bird Surveys #1421

Open gbif-pipelines opened 3 months ago

gbif-pipelines commented 3 months ago

Identifier validation failed for the dataset Garden Bird Surveys:

New IDs sample:
Old IDs sample:

000a2fe0-592f-4a1a-b84a-a4e52d7c022f
00153148-3344-4ff6-a742-c6f3539bf892
00221634-b017-47fa-a53e-cb2808b527cb
002697f0-317e-4cc6-b87c-f94f34e0c78b
002abb27-232c-4245-b0e7-3cebb6b8db56
003e657b-a298-4aba-951c-c466cb7d0580
003e8ee2-4c1b-4332-a221-9216e44731a3
0046ab9b-88f3-4c6c-9823-c851dd27e85f
004848ef-9621-4a12-ba6a-eddc4fd516e8
004b2d43-4440-47b4-aedd-59bb81a1b451
Publisher email Hello, I am contacting you from the GBIF Secretariat about a dataset published by the [Garden Bird Surveys](https://registry.gbif.org/dataset/ce58b7bb-fed6-46b9-9424-135499c7afdf) : https://doi.org/10.15468/jsjoae. 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.

ManonGros commented 3 months ago

The log is very odd, it says:

absent gbif id count: 2.939.234

But the archive only contains 1.855.916 records. I am not sure why this happened.

gbif-pipelines commented 3 months ago

Identifier validation still failing for the dataset Garden Bird Surveys:

New IDs sample:
Old IDs sample:

000a2fe0-592f-4a1a-b84a-a4e52d7c022f
00153148-3344-4ff6-a742-c6f3539bf892
00221634-b017-47fa-a53e-cb2808b527cb
002697f0-317e-4cc6-b87c-f94f34e0c78b
002abb27-232c-4245-b0e7-3cebb6b8db56
003e657b-a298-4aba-951c-c466cb7d0580
003e8ee2-4c1b-4332-a221-9216e44731a3
0046ab9b-88f3-4c6c-9823-c851dd27e85f
004848ef-9621-4a12-ba6a-eddc4fd516e8
004b2d43-4440-47b4-aedd-59bb81a1b451
Publisher email Hello, I am contacting you from the GBIF Secretariat about a dataset published by the [Garden Bird Surveys](https://registry.gbif.org/dataset/ce58b7bb-fed6-46b9-9424-135499c7afdf) : https://doi.org/10.15468/jsjoae. 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.