gbif-pipelines
commented
1 month ago Identifier validation still failing for the dataset LifeWatch observatory data: phytoplankton observations by FlowCam imaging in the Belgian Part of the North Sea:
- Crawler attempt: 149
- Publishing organization: Flanders Marine Institute
- Publishing country: BELGIUM
- Installation: European Ocean Biodiversity Information System (EurOBIS)
- Number of occurrences indexed for this dataset at the time of the issue: 52728
- Cause: GBIF ID problems exceed 50% threshold: 100% duplicates; 66599 total records; 66599 absent records
- Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/3948913/step
New IDs sample:
Old IDs sample:
TripNR3733TripStationNR20659MidasTripActionID111959occurenceIDTA_111959_(Pseudo-)pediastrum_130
TripNR3733TripStationNR20659MidasTripActionID111959occurenceIDTA_111959_Actinoptychus senarius_130
TripNR3733TripStationNR20659MidasTripActionID111959occurenceIDTA_111959_Actinoptychus splendens_130
TripNR3733TripStationNR20659MidasTripActionID111959occurenceIDTA_111959_Actinoptychus_130
TripNR3733TripStationNR20659MidasTripActionID111959occurenceIDTA_111959_Akashiwo sanguinea_130
TripNR3733TripStationNR20659MidasTripActionID111959occurenceIDTA_111959_Amphorellopsis_130
TripNR3733TripStationNR20659MidasTripActionID111959occurenceIDTA_111959_Asterionella_130
TripNR3733TripStationNR20659MidasTripActionID111959occurenceIDTA_111959_Aulacodiscus argus_130
TripNR3733TripStationNR20659MidasTripActionID111959occurenceIDTA_111959_Auliscus_130
TripNR3733TripStationNR20659MidasTripActionID111959occurenceIDTA_111959_Bacillaria paxillifer_130Publisher email
Hello, I am contacting you from the GBIF Secretariat about a dataset published by the [LifeWatch observatory data: phytoplankton observations by FlowCam imaging in the Belgian Part of the North Sea](https://registry.gbif.org/dataset/0ba43f1c-9dc7-4d49-ae90-60d47fd290f3) : https://doi.org/10.14284/650. 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 LifeWatch observatory data: phytoplankton observations by imaging flow cytometry (FlowCam) in the Belgian Part of the North Sea:
Publisher email
Hello, I am contacting you from the GBIF Secretariat about a dataset published by the [LifeWatch observatory data: phytoplankton observations by imaging flow cytometry (FlowCam) in the Belgian Part of the North Sea](https://registry.gbif.org/dataset/0ba43f1c-9dc7-4d49-ae90-60d47fd290f3) : https://doi.org/10.14284/650. 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.