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 plantas vasculares del Herbario Reinaldo Espinosa (Herbario LOJA) de la Universidad Nacional de Loja #973

Closed gbif-pipelines closed 10 months ago

gbif-pipelines commented 10 months ago

Identifier validation failed for the dataset Colección plantas vasculares del Herbario Reinaldo Espinosa (Herbario LOJA) de la Universidad Nacional de Loja:

New IDs sample:
Old IDs sample:

HLOJA-UNL:43357
HLOJA-UNL:43358
HLOJA-UNL:43359
HLOJA-UNL:43360
HLOJA-UNL:43361
HLOJA-UNL:43362
HLOJA-UNL:43363
HLOJA-UNL:43364
HLOJA-UNL:43365
HLOJA-UNL:43366
Publisher email Hello, I am contacting you from the GBIF Secretariat about a dataset published by the [Colección plantas vasculares del Herbario Reinaldo Espinosa (Herbario LOJA) de la Universidad Nacional de Loja](https://registry.gbif.org/dataset/b5a8e29d-cd8c-4e04-90b2-422d900caab6) : https://doi.org/10.60545/u5ji5y. 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 10 months ago

@vechocho I don't have the time to check this today but I am tagging you so you are aware that the dataset ingestion was stopped again. It looks like all the identifiers are new to our system this time. I am not sure why.

gbif-pipelines commented 10 months ago

Identifier validation still failing for the dataset Colección plantas vasculares del Herbario Reinaldo Espinosa (Herbario LOJA) de la Universidad Nacional de Loja:

New IDs sample:
Old IDs sample:

HLOJA-UNL:43357
HLOJA-UNL:43358
HLOJA-UNL:43359
HLOJA-UNL:43360
HLOJA-UNL:43361
HLOJA-UNL:43362
HLOJA-UNL:43363
HLOJA-UNL:43364
HLOJA-UNL:43365
HLOJA-UNL:43366
Publisher email Hello, I am contacting you from the GBIF Secretariat about a dataset published by the [Colección plantas vasculares del Herbario Reinaldo Espinosa (Herbario LOJA) de la Universidad Nacional de Loja](https://registry.gbif.org/dataset/b5a8e29d-cd8c-4e04-90b2-422d900caab6) : https://doi.org/10.60545/u5ji5y. 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.

vechocho commented 10 months ago

@ManonGros

Thank you

We had a talk with the herbarium people and there is a very small risk that they change the occurrences and we don't realize this chage as they would use the same code (occurrenceID) for other specimens.

So, following the recommendations of the blog https://data-blog.gbif.org/post/improve-identifier-stability/ we changed the IDs.

The list of the old and new ids is in this link https://docs.google.com/spreadsheets/d/e/2PACX-1vQDog4ge-9IrD0PP3gqYPLKI7Wn7kiwAFGPmpr6aOezKX5QWp8aT-HqNHc_7ydQEA/pub?gid=447312645&single=true&output=tsv

image

ManonGros commented 10 months ago

Thanks @vechocho I have migrated the identifiers and reinvested the dataset. The data went trough.