sergejzr
commented
1 year ago Update: We tested with ScopusID and that worked, however it does not with ORCIDID
Closed sergejzr closed 1 year ago
sergejzr
commented
1 year ago Update: We tested with ScopusID and that worked, however it does not with ORCIDID
pdurbin
commented
1 year ago @sergejzr sorry for the slow reply. Very strange. Any news? I'm asking in our internal Slack (for my reference).
pdurbin
commented
1 year ago We're having trouble reproducing this. 🤔
sergejzr
commented
1 year ago Dear Phil,
Thanks! Yes, it is quite strange. This problem does not occur on our test system which works with test Datacite account for DOIs. It only occurs on the productive system (though both are exactly the same, actually). Unfortunately, I was not able to produce more detailed logs that could help to understand the cause (for example, it would be interesting to read the original error message from Datacite-API).
At the moment, I am in the middle of my vacations and do not have access to my machines. Maybe we can have a look together when I return to my desk in beginning August? If you in the meanwhile have an idea, how to let Dataverse produce more helpful logs, please tell us, so we can prepare.
Thank you very much, Sergej
pdurbin
commented
1 year ago Sure, feel free to get in touch. You can find me in https://chat.dataverse.org . Enjoy your vacation! 🏖️
As for logging, this line:
String errMsg = "Response from postMetadata: " + response.getStatusLine().getStatusCode() + ", " + data;
Is producing this from your original output in this issue:
Response from postMetadata: 422, DOI 10.60507/fk2/kl6jxk: This element is not expected. Expected is ( {http://datacite.org/schema/kernel-4}creator ). at line 9, column 0
So DataCite is replying with a 422 (Unprocessable Content) with that message, if it helps.
sergejzr
commented
1 year ago Thanks! Is there also a way to display the request message sent from Dataverse?
qqmyers
commented
1 year ago If you turn on fine logging for the DOIDataCiteRegisterService class, it will print the xml sent to DataCite in the log.
cd /usr/local/payara5 bin/asadmin set-log-levels edu.hardvard.iq.dataverse.DOIDataCiteRegisterService=FINE
-- Jim
From: Сергей @.> Sent: Saturday, July 22, 2023 3:21 PM To: IQSS/dataverse @.> Cc: Subscribed @.***> Subject: Re: [IQSS/dataverse] DOI is not created when user has an ORCID ID (Issue #9681)
Thanks! Is there also a way to display the request message sent from Dataverse?
— Reply to this email directly, view it on GitHubhttps://github.com/IQSS/dataverse/issues/9681#issuecomment-1646654428, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABTLRT3TAOAALE4MP5CTTGTXRQRY5ANCNFSM6AAAAAAZVEA4ZA. You are receiving this because you are subscribed to this thread.Message ID: @.**@.>>
sergejzr
commented
1 year ago Thank you so much for all the suggestions! Printing out the outgoing XML did the work. The problem was with implementation of the autocomplete using extended-metadata project, where the variables for ORCID were adjusted. I was able to fix the bug now, using your help, so I guess the issue can be closed here.
I will continue investigating the issue though, but will post in the extended-metadata github-project if the problem persists.
Thanks once again! Sergej
pdurbin
commented
1 year ago @sergejzr sounds good. Closing. Please feel free to open up a fresh issue if you need anything!
Dear Dataverse Developers,
at our installation we discovered a critical issue with the communication between Dataverse and Datacite. We can not draft a DOI when authors supply an ORCID ID. Everything works as expected otherwise. Thank you for your help. Please find the detailed report below
Best regards Sergej
What steps does it take to reproduce the issue?
A user supplies his ORCID ID when adding a dataset. When submitting, no error message is displyed, everything seems alright, however, the DOI request is rejected by DATACITE and the Exception is logged "Response from postMetadata: 422, DOI 10.60507/fk2/uyubh5: This element is not expected. Expected is ( {http://datacite.org/schema/kernel-4}creator ). at line 9, column 0"
Full Stack is posted below in Screenshots. As a consequence, DATACITE does not know the DOI and the dataset can not be published.
Without ORCID ID everything works as expectd
When does this issue occur? When adding a dataset and supplying an ORCID ID of one of the authors.
Which page(s) does it occurs on?
Dataset creation: https://bonndata.uni-bonn.de/dataset.xhtml?ownerId=1
Everything seems to be alright for the user, however an Exception occurs and is logged. Datavers can not draft a DOI
To whom does it occur (all users, curators, superusers)? all users
What did you expect to happen? The DOI should be created or at least, an Error message should be displayed to user, when DATACITE API fails.
Which version of Dataverse are you using?
v. 5.13 build 1244-79d6e57
Any related open or closed issues to this bug report?
Could not find any related issues, there might be some, related to DOI creation at DATACITE
Screenshots: The authors supply their ORCID IDs
After upload, everything seems ok for the user:
However, when publishing the dataset, an error is displayed that the DOI can not be registered.
Also the DOI does not exit at DATACITE.
The log tells that a t upload time the API call to DATACITE failed and DOI could not be created.
Stack Trace:
No matter the issue, screenshots are always welcome.
To add a screenshot, please use one of the following formats and/or methods described here: