Migration - Reproduce latest Datasets version with DOI and DataFiles DOI

46 views
Skip to first unread message

Jules

unread,
Sep 22, 2023, 3:44:39 AM9/22/23
to Dataverse Users Community

Hello Dataverse community,

I've already asked a few questions on ZulipChat, but currently didn't find all the answers we need, so I'm asking again to the Users Community here and hope someone people have done the same as us or maybe can share information on how to achieve this, let me explain:

We're currently trying to figure out how to best use the dataset migration API (https://guides.dataverse.org/en/5.10/developers/dataset-migration-api.html#publish-a-migrated-dataset). 

The use case would be to migrate the datasets currently present in our institutional Dataverse, DOREL (https://dorel.univ-lorraine.fr) to the national French repository (https://entrepot.recherche.data.gouv.fr).

A few questions come along the way, some of them crucial :

- Previous versions : some datasets are in versions > 1.0. We understand that it is better to migrate every version, but how to achieve this? In case this is not possible, and if we had to migrate only the last version (say, 3.1), would it be possible to only have that version, with the right number, in the target repository? What's the best practice, and what's the best technical way to proceed here?

- The migration API allows to create a dataset in the target repository while keeping the current DOI. But what about the files that have already DOIs ?

Thanks in advance, for help or advices,

Daniela Serrano

unread,
Jun 30, 2026, 11:38:40 AM (4 days ago) Jun 30
to Dataverse Users Community
Hello, I know this is super old. Were you able to migrate the version history of your resources? I'm stuck in a similar problem. 

William Hahn

unread,
Jun 30, 2026, 1:29:37 PM (4 days ago) Jun 30
to dataverse...@googlegroups.com
Hi,

I've recently tested out Scholars Portal's dataverse migration scripts for an anticipated migration and can confirm they work well (though I haven't used it in production yet). It covers your case for carrying over all dataset versions, so could be worth trying out: https://github.com/scholarsportal/dataverse-migration-scripts


Best,
William

--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-commu...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/dataverse-community/af2e26e2-f996-4ab5-acf4-3f9579e27d3an%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages