Dear Dataverse community,
we have a problem publishing a dataset with 131 attached files. The publication is aborted because of a 403 response from DataCite after about 25- 89 sucessfully registered DOIs. After three attempts to publish we have now in a bunch of registered DOIs linking to files of a dataset that is still not published. Some of the files have three or four different DOIs pointing to them, some of the files and the main dataset has no registred DOI at all. We already contacted the DataCite-Support for help.
Had anyone of you similar problems (Issue #6562 sounds somewhat similar) or any idea how to rescue this dataset. We could manually map the additional dois if the dataset would be public. But we do not dare to start a new release attempt on the productive system.
On our testsystem connected to the test DOI-service (mds.test.datacite.org), the dataset could be published without problems.
Thanks a lot and kind regards,
Dorothea from Stuttgart
--
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 on the web visit https://groups.google.com/d/msgid/dataverse-community/66c0978f65b24cd6998581850dc74184%40ub.uni-stuttgart.de.
--
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 on the web visit https://groups.google.com/d/msgid/dataverse-community/71a3cd5a-2ed6-46e4-a510-eaaacb79becc%40googlegroups.com.
FWIW: From the code, it looks like all calls are made with the same HttpClient which has the authentication info, so DataCite’s idea that we might be making the GET without credentials doesn’t look to be true. With Phil’s note that the POST call also had a 403, it seems more likely that there was a temporary authentication issue affecting both/all calls.
-- Jim
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/CABbxx8FYr%2BmhnQORJ%2B%2BQL-AynZQqA23K-ZBYNBWws_JC96rndQ%40mail.gmail.com.