"Failure to register, or update the Global Identifier"

[Chris Pauls]

Hi everyone,

we have some teething troubles with our dataverse instance and I am hoping that someone here might have an idea what causes it.

That basic problem seems to be that no DOI can be registered for a dataset that we would like to publish. We have double and triple checked the account data we got from Datacite but after pressing the publishing button, Dataverse works for a few seconds or minutes before sending an error message like the one below:

"4th Nurse Care Activity Recognition Challenge Software (view at http://dare.uol.de:8080/dataset.xhtml?persistentId=doi:10.57782/976PGQ ) in Nurse Care Activity Recognition Challenge 2022 (view at http://dare.uol.de:8080/dataverse/ncra_challenge_2022 ) 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."

I am not directly involved with the technical side of things, but my colleagues who are assured me that everything is correctly set-up (to their knowledge).

I am open to any guesses, conjectures or comments!

Best regards from Oldenburg (Germany) 

Chris

[Chris Pauls]

I forgot to mention that we are on Dataverse version 5.10.1 build 907-b844672.

[Donald Sizemore II]

Hello,

It looks like you’re serving over http, but DataCite serves over https (protocol mismatch). Can you set up https for your installation, and try again?

Secondly, be sure your dataverse.siteUrl jvm-option is set correctly, as this is how DataCite will “call back” to your Dataverse.

Let me know if this helps?

Don

painstakingly pecked on my iphone.

On Oct 7, 2022, at 05:43, Chris Pauls <chr....@gmail.com> wrote:



--
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/154c2064-c7a3-4d7d-bb72-8ad8b13a0266n%40googlegroups.com.

[Mariska J.]

Hi Don,

thank you for your reply.

We have set up https now and corrected our siteUrl but we still get this error message:

4th Nurse Care Activity Recognition Challenge Software (view at

https://dare.uol.de/dataset.xhtml?persistentId=doi:10.57782/976PGQ [Titel anhand dieser DOI in Citavi-Projekt übernehmen] ) in Nurse Care

Activity Recognition Challenge 2022 (view at

https://dare.uol.de/dataverse/ncra_challenge_2022 ) 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.

These are our jvm-options:

        <jvm-options>-Ddataverse.fqdn=dare.uol.de</jvm-options>
        <jvm-options>-Ddataverse.siteUrl=https://${dataverse.fqdn}</jvm-options>
        <jvm-options>-Ddoi.baseurlstring=https://mds.datacite.org</jvm-options>
        <jvm-options>-Ddoi.dataciterestapiurlstring=https://api.datacite.org</jvm-options>
        <jvm-options>-Ddoi.username=BISOLD.DAREUOL</jvm-options>
        <jvm-options>-Ddoi.password=...</jvm-options>

Do you have an idea what is going wrong here?

Best regards from Oldenburg

Mariska

[Don Sizemore]

Hello,

Have you tested your DataCite credentials at https://doi.datacite.org/ ?

and you're certain that your Authority setting is correct?

I see you're not using a Shoulder, but I understand shoulders aren't required.

There may be a more helpful error message in the Payara server.log?

Don

To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/fda6254b-f6f5-451b-95c9-c7033d3efcban%40googlegroups.com.

[Mariska J.]

Hi Don,

we have tested our DataCite credentials and we think that our Authority setting ("10.57782") is correct. When we have applied for our DOI namespace, we have not requested a shoulder.

Please find attached our server.log. Thank you for taking a look!

Mariska

[Don Sizemore]

Hello,

It looks like Dataverse is unable to contact DataCite:

https://mds.datacite.org:443: No route to host

Do you have some network control restricting egress, or perhaps a routing problem?

Don

To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/935bfc31-b30c-4dfa-8e19-bb39b689065an%40googlegroups.com.

[Mariska J.]

Thank you so much for this hint, Don.

We will begin with checking our HTTP/HTTPS proxy settings.

Mariska