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 Insekten Sachsen #1567

Closed gbif-pipelines closed 1 month ago

gbif-pipelines commented 1 month ago

Identifier validation failed for the dataset Insekten Sachsen:

New IDs sample:
Old IDs sample:
Publisher email Hello, I am contacting you from the GBIF Secretariat about a dataset published by the [Insekten Sachsen](https://registry.gbif.org/dataset/77ecd330-b09e-11e2-a01d-00145eb45e9a) : https://doi.org/10.15468/ops3q2. 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.

gbif-pipelines commented 1 month ago

Identifier validation still failing for the dataset Insekten Sachsen:

New IDs sample:
Old IDs sample:
Publisher email Hello, I am contacting you from the GBIF Secretariat about a dataset published by the [Insekten Sachsen](https://registry.gbif.org/dataset/77ecd330-b09e-11e2-a01d-00145eb45e9a) : https://doi.org/10.15468/ops3q2. 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.

gbif-pipelines commented 1 month ago

Identifier validation still failing for the dataset Insekten Sachsen:

New IDs sample:

e2484450-c8f6-49ba-a298-29b760d307cf
d1128b50-d2ad-40b9-a18c-d9917dc8b76c
b2814de9-33f1-4f99-afc9-83c5ac230746
3e55013e-3c8d-4537-8379-d74487ded00c
01a89fd0-9d24-478c-9fb1-0aa2e8279f50
f9ab52ab-0375-4103-a902-938bcb72787a
f572affb-81ba-4099-849a-9378cd7ff7c2
9c032db9-181a-4140-a276-19b59c99f593
78f950e9-6bfe-4b99-bd45-9388df70d904
253b6ba3-5de8-4a29-8559-beb9abc1809d
Old IDs sample:
Publisher email Hello, I am contacting you from the GBIF Secretariat about a dataset published by the [Insekten Sachsen](https://registry.gbif.org/dataset/77ecd330-b09e-11e2-a01d-00145eb45e9a) : https://doi.org/10.15468/ops3q2. 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.