gbif-pipelines
commented
4 months ago Identifier validation still failing for the dataset Phenology and biological traits of migrating trout and sea trout (Salmo trutta) sampled by trapping in the survey in the Bresle river (France):
- Crawler attempt: 92
- Publishing organization: Institut national de recherche pour l’agriculture, l’alimentation et l’environnement (INRAE)
- Publishing country: FRANCE
- Installation: IPT GBIF France
- Number of occurrences indexed for this dataset at the time of the issue: 39132
- Cause: GBIF ID problems exceed 50% threshold: 92% duplicates; 260264 total records; 238715 absent records
- Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/3860193/step
New IDs sample:
20200522_EU_PGM_100748_25
20190221_LD_PGD_093347
20190726_EU_PGM_101827
20180722_EU_PGM_081418
20210422_EU_PGD_112100_24
20180418_LD_PGD_105953
20180407_LD_PGD_101038
20210430_LD_PGD_092532_36
20190330_LD_PGD_082852
20190531_EU_PGM_102734Old IDs sample:
20220103_LD_PGD_PGD_084300-Brown trout
20220103_LD_PGD_PGD_084300-sea trout
20220104_LD_PGD_091443_10
20220104_LD_PGD_091940_12
20220104_LD_PGD_092114_13
20220104_LD_PGD_092450_14
20220104_LD_PGD_092802_15
20220104_LD_PGD_093910_22
20220104_LD_PGD_094049_23
20220104_LD_PGD_094422_24Publisher email
Hello, I am contacting you from the GBIF Secretariat about a dataset published by the [Phenology and biological traits of migrating trout and sea trout (Salmo trutta) sampled by trapping in the survey in the Bresle river (France)](https://registry.gbif.org/dataset/1632788f-d8ec-4cfa-acfb-baf7da8e5e74) : https://doi.org/10.15468/jkpya8. 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.
Identifier validation failed for the dataset Phenology and biological traits of migrating trout and sea trout (Salmo trutta) sampled by trapping in the survey in the Bresle river (France):
Publisher email
Hello, I am contacting you from the GBIF Secretariat about a dataset published by the [Phenology and biological traits of migrating trout and sea trout (Salmo trutta) sampled by trapping in the survey in the Bresle river (France)](https://registry.gbif.org/dataset/1632788f-d8ec-4cfa-acfb-baf7da8e5e74) : https://doi.org/10.15468/jkpya8. 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.