search

gbif / portal-feedback

User feedback for the GBIF API, website and published data. You can ask questions here. 🗨❓
30 stars 16 forks source link

Duplicated ukraine datasets #4492

Closed rukayaj closed 1 year ago

rukayaj commented 1 year ago

This dataset https://www.gbif.org/dataset/0c5b3d27-e175-4441-9a14-76d7cdd10446 was somehow removed from the Ukraine IPT. Possibly accidentally deleted, I am not sure what happened.

The data provider recreated this dataset on the IPT from a backup, published it, and unfortunately now we have a duplicate dataset: https://www.gbif.org/dataset/4a56feac-b26d-4490-b7c6-dd0d7a10382a . I added the old DOI (https://doi.org/10.15468/2qgsta) + old dataset key (0c5b3d27-e175-4441-9a14-76d7cdd10446 ) to the alternative identifiers in the EML in the new recreated dataset. I see on the registry it's possible to specify if one dataset is a duplicate of another, so I did that too. Is there any way they can get merged?

CecSve commented 1 year ago

It seems the duplicate registration in the registry did not go through. Should I go ahead and try to mark the first one as a duplicate of the new? The datasets would not get merged, but the one that was accidentally deleted on the Ukranian IPT would be registered as 'deleted' + 'duplicate of' the other dataset, the occurrence would be removed and any citations (no citations in this case) would not be automatically transferred to the new dataset.

rukayaj commented 1 year ago

Hi @CecSve yes that sounds good. Thanks :)

CecSve commented 1 year ago

I duplicated the dataset again and deleted the old dataset, and the dataset now appears as deleted + duplicated of the GBIF Norway IPT one