Hello,
We had a draft dataset with a DOI that accidentally got deleted. We have to have this record at that DOI when it's ready to be published. I realize we can't recover the dataset, but is there a way to make a new (draft) dataset with that DOI?
Thanks,
Bethany
Others may have some more ideas, here's mine: maybe use the Migration API to create it? https://guides.dataverse.org/en/6.9/developers/dataset-migration-api.html
Hmm, @Leo Andreev might have a better answer but you could always edit the database directly. The DOI is stored here: https://guides.dataverse.org/en/6.9/schemaspy/tables/dvobject.html
Thanks for the ideas so far. I think we can "migrate" the a new record in.
If we migrate one in, will I have to create the DOI myself in fabrica?
The DOI might already be in fabrica. I'm not sure of the state though, since you deleted the dataset.
Thanks - the migration does seem to work. I had to recreate the draft doi in datacite, then migrate the dataset, then I'll update datacite again with the actual URL. I think that Dataverse will not steward this DOI with Datacite the way it does with others (which makes sense), but I think this will be good enough to solve my issue.
Phew! Should we have an API for this?!? :sweat_smile:
We recently had the same issue. We kept the DOI registered for the deleted draft as "registered", created a new dataset and had the URL of the old DOI point to the new DOI URL.
Would it be an idea to make unintentionally deleting drafts harder? Our user was trying to delete a file and was probably in a hurry. Similar to how GitLab handles this you could have a modal/popup that asks the user to type in the full DOI of the draft dataset to delete.
@Henning Timm interesting idea! We're trying to touch the old UI (JSF) as little as possible, but if you're up for it, please create an issue over here for the new UI (React): https://github.com/IQSS/dataverse-frontend/issues
Thank you! I opened an issue: https://github.com/IQSS/dataverse-frontend/issues/976
Looks great. Thanks!
Last updated: May 30 2026 at 09:11 UTC