DOI configuration on dataverse
Adilia Alves
<jvm-options>-Ddoi.password=[PASSWORD]</jvm-options>
<jvm-options>-Ddoi.baseurlstring=https://mds.datacite.org</jvm-options>
<jvm-options>-Ddoi.dataciterestapiurlstring=https://api.datacite.org</jvm-options>
...
Other Error on ezidService.login(USERNAME, PASSWORD) - not EZIDException ]]
James Myers
I’m not sure what your issue is, but the “Other Error on ezidService.login(USERNAME, PASSWORD) - not EZIDException ]]” isn’t fatal. The DOIEZIdServiceBean tries to login using the credentials you set and, since you’re not using EZId, it fails. The DataCite service bean should also be setting up with those credentials and succeeding (assuming they’re good). (This would be a good case for https://github.com/IQSS/dataverse/issues/7805 - something that shouldn’t be a SEVERE log entry.)
Other than assuring that your username and password are good, for the production DataCite services, e.g. by logging in with them at doi.atacite.org, I can’t think of anything else that could be related just to a change in the doi jvm options.
- 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 on the web visit
https://groups.google.com/d/msgid/dataverse-community/7f8f109b-1f64-40fe-88a4-54b9f84b6846n%40googlegroups.com.
Adilia Alves
Location: https://dados.ipb.pt/dataset.xhtml?persistentId=doi:10.34620/FK2/N0SAHK&version=DRAFT"
James Myers
That doesn’t sound like anything a :Shoulder should cause. In general, if your account can mint DOIs for the whole authority, you can still use a shoulder if you want (might be useful for example if you might someday have a second repository.)
The XML Parsing Error: duplicate attribute error isn’t one I’ve seen before. I’d suggest trying to create a dataset with the same metadata on demo.dataverse.org to see if this is a bug or something to do with your local configuration.
In either case it would probably be good to submit an issue at for https://github.com/IQSS/dataverse/issues - that’s a better place for more complex problems.
-- Jim
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/b86078ff-2203-43a0-abeb-788a8e38faadn%40googlegroups.com.
Adilia Alves
Philip Durbin
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/01bca6cd-d541-47ae-8cb9-ba6514126950n%40googlegroups.com.
--
Software Developer for http://dataverse.org
http://www.iq.harvard.edu/people/philip-durbin
Thomas Jouneau
Hi,
A user here encounters the same error as described below
(Dataverse 5.10).
XML Parsing Error: duplicate attribute
Location:
https://dorel.univ-lorraine.fr/dataset.xhtml?persistentId=doi%3A10.12763%2F5TZTE9&version=DRAFT
Line Number 955, Column 342:
The dataset could not be created. If you
believe this is an error, please contact <a
id="messages:j_idt156:j_idt161" href="#" class="ui-commandlink
ui-widget"
onclick="clickSupportLink();;PrimeFaces.ab({s:"messages:j_idt156:j_idt161",f:"messages:j_idt156",fi:"messagePanel"});return
false;" onclick="clickSupportLink();"
onclick="clickSupportLink();">L'équipe support DOREL</a>
for assistance.<input type="hidden"
name="javax.faces.ViewState" id="j_id1:javax.faces.ViewState:4"
value="1273334235578213818:-1899972390304135016"
autocomplete="off" />
The other users don't seem to have encountered the problem yet.
So might it be linked to the user's entry in Dataverse?
I see that the ticket created by Adilia last september was closed two days later. What solution was found, if any?
Thanks
Thomas
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/CABbxx8HrpJc30-Ub9-y3WUw63wJuGWa5e-fNcF9AbZb0ZHvGOg%40mail.gmail.com.