gbif-pipelines
commented
3 months ago Identifier validation still failing for the dataset Northern Tablelands Koala Habitat Restoration Project:
- Crawler attempt: 56
- Publishing organization: DEPARTMENT OF PLANNING AND ENVIRONMENT - Environment and Heritage
- Publishing country: AUSTRALIA
- Installation: ALA.org.au
- Number of occurrences indexed for this dataset at the time of the issue: 456
- Cause: GBIF ID problems exceed 50% threshold: 60% duplicates; 544 total records; 325 absent records
- Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/3946771/step
New IDs sample:
66b705ab-b4c7-4487-a030-1258e4a0e555
2e45435b-4ce0-4b9b-8e2d-b65112fb016b
a813251c-afbf-4850-b134-44356328cd0d
e5e2b7da-8f5a-4f87-baec-c0900a37aab5
7fd45b3b-410b-42d5-9536-ecfae2b3d1bf
e1072100-54d9-4ef5-b43c-3e8c10cce4a9
cad8bb05-88b5-4435-993b-def2dcc0a139
2079239b-0c95-4b4e-a80b-b5a77e3d4a9d
bd69d4db-7ec8-4076-a4e7-164cb3f807cc
d6cd7017-4437-4d1a-801f-b8338682cabfOld IDs sample:
00c76ef6-3bd0-411d-b7d8-ef8ff00735b2
03aaeb88-3844-4b37-95a8-7d88fd7e453d
08fc991c-57be-43b5-92ca-2a4fc0865e3b
092bb623-2dd1-45f8-b050-f1761807c06b
0bedae5b-973c-40dc-bb2e-5ebfac693895
0c2f1dfe-dc42-42d6-b4fd-56a56e49178b
0c643601-1fcb-4e17-8c01-521b03a3607b
0e13a887-4ccd-4aea-aca0-c76cac67f44d
150291a1-0665-4823-9347-bde094228257
16006dcf-185e-4769-88d8-66f98a1c61fcPublisher email
Hello, I am contacting you from the GBIF Secretariat about a dataset published by the [Northern Tablelands Koala Habitat Restoration Project](https://registry.gbif.org/dataset/1c85c7c0-6343-4be2-9230-03fa16b6dee8) : https://doi.org/10.15468/ushbmp. 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 Northern Tablelands Koala Habitat Restoration Project:
Publisher email
Hello, I am contacting you from the GBIF Secretariat about a dataset published by the [Northern Tablelands Koala Habitat Restoration Project](https://registry.gbif.org/dataset/1c85c7c0-6343-4be2-9230-03fa16b6dee8) : https://doi.org/10.15468/ushbmp. 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.