Migrating from figshare to Dataverse

[Philipp Conzett]

We are planning the onboarding of a new partner institution in DataverseNO. They are currently using figshare and would like to migrate from there to DataverseNO. This includes migration of datasets (files, metadata, DOIs), user accounts and possibly other items.

Dataverse supports this kind of migration through the Dataset Migration API and Dataverse migration scripts.

We wonder whether anyone in the community has experiences migrating from figshare (or another platform) to Dataverse and would be willing to share some insight.

Best,
Philipp

[Steven McEachern]

Hi Philipp,

The Australian Data Archive did a migration of around 60 datasets out of Figshare to DV a couple of years back.

If you contact Janet McDougall at ADA, she could give you some insight here.

Cheers,

Steve

[Philipp Conzett]

Thanks, Steve! I'll definitely reach out to Janet.

Best, Philipp

[MM - ADA]

Hi Philipp - I am the Technical Manager at the Australian Data Archive (Janet is my colleague and Steve is the former Director) and was the team member that migrated a collection of datasets from Figshare to ADA's production dataverse.

I will see if I can find the details of how I did this as it was several years ago. The biggest issue, if I recall correctly, was mapping what metadata is available in figshare to dataverse metadata fields.

If you email me, I will share what details I can find.

Kind regards,

Marina

[MM - ADA]

Apologies Philip - I meant to say if you email me as well as Janet, I can provide feedback on the technical issues while Janet can provide details on the doi- and archiving-related issues.

Cheers - Marina

[Philipp Conzett]

Thanks, Marina! I'll contact you and Janet by email.

Best, Philipp

[Philipp Conzett]

We are now preparing the data migration mentioned above from figshare to DataverseNO. Our current approach is to create new datasets with the metadata and files from figshare. This means that the migrated datasets will get new primary PIDs, which are the DataverseNO DOI (10.18710/…). The old figshare DOIs will be added to the metadata field "Previous Dataset Persistent ID", which corresponds to the DataCite metadata field alternateIdentifier. This is how we did it with the Handle IDs that we used before we switched to DOI.

Now, DataCite is asking us whether it would be possible to update the URL landing pages with existing figshare DOIs, rather than creating new duplicates.

Is this possible in Dataverse? I know in Zenodo, depositors are asked if the content they are uploading already has a PID. Maybe that's related to my question.

Best,
Philipp

[James Myers]

The Dataset Migration API supports this: https://guides.dataverse.org/en/latest/developers/dataset-migration-api.html#dataset-migration-api

 

-- Jim

--
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/8f977e86-009e-4f79-a31e-5ce3b0a3ff4fn%40googlegroups.com.

[James Myers]

I should add that updating the DOIs at DataCite requires that they be manageable by some configured PID Provider. If DataCite will transfer the specific PIDs to an account, they can be added to the managed list of that provider. (If you have access to the account currently managing the migrating DOIs, you can just add that as a second provider.).

 

-- Jim

To view this discussion visit https://groups.google.com/d/msgid/dataverse-community/DM6PR07MB6252848EF8E758C806EAB0C4BFD0A%40DM6PR07MB6252.namprd07.prod.outlook.com.

[Philipp Conzett]

Thanks for this information, Jim!

Can we use that second provider just for the migrated datasets? For new datasets, we need to use our usual DOI prefix and setup.

I also wonder whether the solution we're currently discussing is desired. From a DataverseNO point of view it seems odd that we should host "old" figshare DOIs. Why not just create new DataverseNO DOIs for these migrated datasets and add the figshare DOI as Previous Dataset Persistent ID?

Philipp