Julien C (Sep 19 2023 at 12:47): Julien C (Sep 19 2023 at 12:47):Hello Dataverse Community,
Is there a way to migrate with the API (version 5.10) some DataFiles with an existing DOIs to a different existing installation ? (I means to a different Dataverse installation). I see in the API Documentation that is possible with the Datasets but the question remains for the DataFiles associated with it.
Thks in advance for advices
Philip Durbin 🚀 (Sep 19 2023 at 13:16):I would suggest digging into these migration scripts from Scholars Portal: https://groups.google.com/g/dataverse-community/c/PfKIZFxFZhE/m/2lC7QLzUBAAJ
Julien C (Sep 19 2023 at 13:19):Thanks for the link Philip, I will give it a try.
Philip Durbin 🚀 (Sep 22 2023 at 14:04):I'm glad you asked on the list: https://groups.google.com/g/dataverse-community/c/NwIFODp4I0A/m/xrH422EuAAAJ . Thanks!
Julien C (Oct 06 2023 at 14:19):Still no answer, is anybody have a clue on that specific point ?
Philip Durbin 🚀 (Oct 06 2023 at 14:56):I forget, did you also email support@dataverse.org about this?
Julien C (Oct 09 2023 at 09:25):Thank you Philip for your reply, i will do that too.
Philip Durbin 🚀 (Oct 12 2023 at 18:10):I'm in a room with @Dimitri Szabo talking about this. Jim Myers isn't sure if DOIs for files are supported or not.
Julien C (Oct 13 2023 at 14:09):Thanks for your reply, Hello to everyone and to my french colleague.
If you can give me confirmation or not on this crucial point it will help me.
Regards
Philip Durbin 🚀 (Oct 13 2023 at 14:12):Sure. For now, would you be able to create an issue about this?
Philip Durbin 🚀 (Oct 13 2023 at 17:22):Thanks for opening this: API Migration for DataFiles DOI how to do this ? (version 5.1x) #10008
Julien C (Nov 03 2023 at 10:50):This is not a necropost because I've not solved the "issue" with DataFiles DOIs.
As an example for the community, maybe someone knows or had already done this.
I can manage, between two same installations with same DOI authority, an update of DOI for a dataset.
But it doesnt work for Datafiles because, when I'm trying to publish it fails: automatically it generates a lock on dataset in a dedicated database table. (I've try to delete the lock, it changes nothing, relocked automatically)
And here its just for the same authority, I'm wondering if it will be different with the French RDG server who has a different provider root authority.
Please look at this simple SQL capture example where i'm trying to update manually a DataFile with ID 8232 it fails when trying to publish after reindexing. (Solr)
Maybe i'm doing this the wrong way, if someone can tell me how to do that with the publication status to succeed it will helps a lot to configure out a scripted version with Datacite provider.
Have a nice day,
Regards
screenshot_db_provider_identifier_DOI_Datafiles.jpg
Philip Durbin 🚀 (Nov 03 2023 at 12:22):Thanks I just linked from #10008 to this update about locks.
Julien C (Nov 06 2023 at 14:26):When i change into SQL the identifier for the dataset and publish without files it works (ok this an update to provider Datacite)
But When I add Datafiles and try to do the same thing, the publication of the Dataset failed and a lock is generated into the DatasetLock table.
How can I bypass this lock to "force" the update of the Datafiles DOIs too ?
@Philip Durbin
Could it be possible to have more details on how the File Validation is performed when a dataset is published please ?
In table Datasetlock I still have "FileValidationFailed" and I think i have tried almost all ideas ...
For each Datafiles the fields: authority, identifier, identifierregistered have been updated and this is not working.
I have tried to change the status of DOI with Datacite: pass to 'findable' to 'registered'... change nothing.
A little help please, i need a Dataverse SQL guru here :-)
Julien C (Nov 08 2023 at 10:00):Hello there,
Atm i'm running some tests in order to figure out to force the DOIs DataFiles to be migrated on target server.
I have done some modifications on the target server in SQL but it doesnt work for DataFiles. When publishing the lock in table 'Datasetlock" appears.
You can remove the lock but nothing changed. The dataset with DOIs Datafiles cannot be published.
2) Using the Migration API: I start migration, update informations with Datafiles but new DOIs are attributed when published. This is not what I want. Keep the existing DOIs is essential here.
3) I have tried to initialize the migration of a Dataset and edit the SQL just for the DataFiles includes with DOIs, but when i try to use the 'releasemigrated' command from the Migration API, i got a similar response to my SQL Tests:
"status":"ERROR","message":"Dataset Version Update failed. Changes are still in the DRAFT version. - edu.harvard.iq.dataverse.engine.command.exception.CommandException: This dataset may not be published due to an error when contacting the <a href=http://status.datacite.org target=\"_blank\"/> DataCite </a> Service. Please try again."}
My question is simple how can integrate the migration of Datafiles to keep the existing DOIs attributed on the target server ?
Philip Durbin 🚀 (Nov 08 2023 at 13:33):It might take some development work. Someone probably needs to work on this issue you opened, I mean: API Migration for DataFiles DOI how to do this ? (version 5.1x) #10008
Julien C (Dec 05 2023 at 16:20):Hello Dataverse community,
Just to give you an update on this.
I am still unable to publish/migrate to RDG installation a dataset with DataFiles with DOI attached.
The migration API gives me this kind of response:
(500, {'status': 'ERROR', 'message': 'Dataset Version Update failed. Changes are still in the DRAFT version. - edu.harvard.iq.dataverse.engine.command.exception.CommandException: This dataset may not be published due to an error when contacting the <a href="http://status.datacite.org" target="_blank"/> DataCite </a> Service. Please try again.'})
The RDG dataverse installation is a little bit more explicite with an email with detailed error:
... could not be published due to a failure to register, or update the Global Identifier for the dataset or one of the files in it. Contact support if this continues to happen.
If dataverse community or support can propose a workaround or valid process to migrate with DataFiles and publish on a target server (including SQL process), I'm listening !
Thanks in advance for help or advice (need "dataverse guru" here please)
Regards
Philip Durbin 🚀 (Dec 05 2023 at 16:36):Right, and way back in September you asked here: https://groups.google.com/g/dataverse-community/c/NwIFODp4I0A/m/xrH422EuAAAJ
Philip Durbin 🚀 (Dec 05 2023 at 16:37):Perhaps you should post again to that thread? I'm not sure what to tell you.
Santiago Florez (Nov 08 2024 at 19:47):Hello everyone, hope you are well
I would like to know if there is any way to migrate datafiles with the same DOI between different Dataverse instances. I have migrated the Datasets keeping the same DOI and I need to do the same with the datafiles. Is there any process, script or module I can use?
Philip Durbin 🚀 (Nov 08 2024 at 19:57):Hmm, that's a good question. I hope it works. :sweat_smile:
Philip Durbin 🚀 (Nov 08 2024 at 19:58):I would suggest asking at https://groups.google.com/g/dataverse-community
There are about five times more people there.
Santiago Florez (Nov 08 2024 at 20:21):Ok, @Philip Durbin 🐉 thanks for answer :grinning_face_with_smiling_eyes: . I'll do. Have a good day.
Last updated: Nov 01 2025 at 14:11 UTC