Hi everyone,
I have a question regarding PID management in Dataverse. Is it possible to migrate existing PIDs that were originally generated as permalinks (Handles) to DOIs using DataCite for datasets that are already published?
Could this process be handled using a similar approach to the existing API endpoint for minting DOIs on datasets with Handles, as mentioned in the docs:
https://guides.dataverse.org/en/6.3/admin/dataverses-datasets.html#mint-a-new-doi-for-a-dataset-with-a-handle ?
Any guidance or best practices would be greatly appreciated.
Thanks
Juan
Hi Juan, yes, that looks like the right API endpoint. It should work. If it doesn't, please let us know!
Hi Philip, thanks for your response.
Just to clarify I meant to say "permalinks to DOIs". I'll go ahead and try the endpoint and let you know how it goes!
Thanks again for the help.
Oh, sorry, I thought you meant handles
You're on version 6.3?
Yes, we're currently on 6.3 but we're planning on upgrading to 6.8 next week
I'm looking at https://github.com/IQSS/dataverse/blob/v6.3/src/main/java/edu/harvard/iq/dataverse/api/Admin.java#L1496 and it only works for Handles.
I seem to remember @Johannes D or @Vera Clemens asking about "promoting" PermaLinks to DOIs.
@Juan L贸pez please take a look at this: Feature Request/Idea: migrate published datasets from Permalink/FAKE PID provider to another provider聽#10497
Is that what you're asking for?
Yes Sir, that鈥檚 exactly what we need
Ha, well, I recommend leaving a comment on that issue and joining the discussion at #dev > changing collection PID provider
Or maybe @Johannes D or @Vera Clemens will join us here. :smile:
Did you see that @Johannes D already did some work in #10567 that landed in 6.7? Over at https://github.com/IQSS/dataverse/releases/tag/v6.7 we wrote it up as "API for switching Datasets to DOIs, for example"
I'm looking at it right now, but it seems to only work for unpublished datasets that have permalinks
In this case, we鈥檙e referring to published datasets. Since this is a new Dataverse instance still under development, we still have the opportunity to deploy a new instance and start publishing datasets with the DataCite account properly configured from the beginning
Yeah, that sounds right. I don't think published datasets are supported
Or maybe, since this is still in development, would it be possible (and safe) to manipulate the database to revert all published dataset to an unpublished state and then mint the DOIs?
I don鈥檛 think this is a good idea, but I鈥檓 trying to find a way to avoid having the team re-upload all datasets again.
Oh, interesting.
Can you simply create new datasets that are equivalent to the published ones?
Yes, we could just set a new installation from scratch and start uploading all the datasets again.
Or...
But whatever is easier, obviously!
Interesting! I'll talk about it with the team, thank you very much Philip!
Philip Durbin 馃殌 said:
Did you see that Johannes D already did some work in #10567 that landed in 6.7? Over at https://github.com/IQSS/dataverse/releases/tag/v6.7 we wrote it up as "API for switching Datasets to DOIs, for example"
Hi, yes, I can confirm that we are regularly using that API (https://guides.dataverse.org/en/latest/api/native-api.html#reconcile-the-pid-of-a-dataset-if-multiple-pid-providers-are-enabled) to switch datasets from Permalinks to DOIs. But yes, it only works for unpublished datasets (at the moment). Maybe it could be extended to work for published datasets as well, if you're superuser, or something like that? We'd be open to creating a PR for that.
Yeah, as a short term solution you could comment the safeguards in the method, compile your own version of dataverse, deploy it to production, conduct the migration and redeploy the official version. (We've also done that ;))
interesting :smile:
sure, we'd love a PR!
Last updated: Apr 03 2026 at 06:08 UTC