Problems with the DOI-CrossRef automatic registration

#1

Hi
A month ago we installed the DOI-CrossRef automatic registration for our journal, but unfortunately it doesn’t work. It looks as if CrossRef hasn’t received the registration (DOI). Here you can see how we made the setup:

(Sorry, I couldn’t find out how to insert my gif images, but I’m sure our setup is OK)

#2

Hi nef,

I’m happy to give you a few recommendations for where you might want to start out. The plugin has a few dependencies that can be easy to miss. Some of the error reporting is a little obtuse, currently.

I’d recommend reading this bit. It sounds like you’ve already taken a look at these, but Step 1 in the setup lists a few places you’ll need metadata to exist in order for your DOIs to be registered.

That said, if everything appears to be properly configured and you’re still getting registration errors, one pretty common source for this is missing article publication dates. There’s currently a bug where any article uploaded via the QuickSubmit plugin don’t receive a publication date for the article (even if the issue does). You can check the article publication dates by going to:

Editor > Back Issues > Select Issue > click article title > “Editing” Subheading…

Under “schedule for publication”, you’ll probably see no date selected even if the article is currently within a published issue. This would be a good place to look and a common spot for errors.

Let me know if you’re still hitting snags after trying those. Good luck!

#3

Hi
I’ve checked for all the things you mentioned and I can’t find any errors in my settings and nothing is missing. When I check the link ‘Failed’ under status I get the following:
{“status”:“ok”,“message-type”:“deposit”,“message-version”:“1.0.0”,“message”:{“handoff”:{“delay-millis”:2718.2818284590453,“status”:“completed”,“timestamp”:1439719261738,“try-count”:1},“dois”:[“10.7146/ojssb.v6i6.21245”,“10.7146/ojssb.v6i6.21246”,“10.7146/ojssb.v6i6.21248”,“10.7146/ojssb.v6i6.21250”,“10.7146/ojssb.v6i6.21251”],“parent”:null,“filename”:null,“submitted-at”:“Sun Aug 16 12:01:01 CEST 2015”,“status”:“failed”,“length”:7781,“content-type”:“application/vnd.crossref.deposit+xml”,“pingback-url”:null,“submission”:{“submission-id”:“1383280737”,“batch-id”:“48c4e63c-b41e-4646-8fd1-00d6ed4dd03c”,“record-count”:1,“success-count”:0,“warning-count”:0,“failure-count”:1,“messages”:[{“status”:“failure”,“related-doi”:null,“message”:“Error: cvc-pattern-valid: Value ‘https://orcid.org/0000-0002-6281-9981’ is not facet-valid with respect to pattern ‘http://orcid.org/[0-9]{4}-[0-9]{4}-[0-9]{4}-[0-9]{3}[X0-9]{1}|http://orcid.org/[0-9]{15}[X0-9]{1}’ for type ‘orcid_t’. Error: cvc-complex-type.2.2: Element ‘ORCID’ must have no element [children], and the value must be valid.”,“message-types”:[]}]},“test”:false,“owner”:“aaul”,“batch-id”:“48c4e63c-b41e-4646-8fd1-00d6ed4dd03c”}}

Niels Erik Frederiksen
Forskningsbibliotekar, cand. mag. / Research Librarian, MA
Studie- og Forskningsservice
DIRECT +45 8946 2179
MOBILE +45 2167 2417
email: nef@statsbiblioteket.dkmailto:nef@statsbiblioteket.dk

[cid:image001.png@01CDC0B1.6127E000]
VICTOR ALBECKS VEJ 1
8000 AARHUS C

CVR/SE 10100682 - EAN 5798000791084

#4

Hey again, Nef

It looks like the issue might be with the way the plugin is formatting the ORCID ID metadata field. I can flag that as a bug in OJS.

The relevant text seems like it’s this bit:

“Value ‘https://orcid.org/0000-0002-6281-9981’ is not facet-valid with respect to pattern ‘http://orcid.org/[0-9]{4}-[0-9]{4}-[0-9]{4}-[0-9]{3}[X0-9]{1}|http://orcid.org/[0-9]{15}[X0-9]{1}’ for type ‘orcid_t’. Error: cvc-complex-type.2.2: Element ‘ORCID’ must have no element [children], and the value must be valid.”"

I’m not sure what went wrong in this case… It seems like you have a valid ID there. In the short term, if you’re pressed for time, it might be worth while to remove the orcid id from the metadata and try submission again. I’ve submitted this ticket you might want to keep an eye on.

#5

The ID in this example is (incorrectly) prefixed with https instead of http.
http://orcid.org/trademark-and-id-display-guidelines

Our validation should enforce this.

Did this data perhaps get into OJS pre-validation?

#6

See this thread from the old forum:
http://pkp.sfu.ca/support/forum/viewtopic.php?f=8&t=13004

Regards,
Alec Smecher
Public Knowledge Project Team

#7

Hi Alec

I’ve already inserted my ORCID with a http and not a https so that’s not the problem.

Regards

Niels Erik (nef)
Niels Erik Frederiksen
Forskningsbibliotekar, cand. mag. / Research Librarian, MA
Studie- og Forskningsservice
DIRECT +45 8946 2179
MOBILE +45 2167 2417
email: nef@statsbiblioteket.dkmailto:nef@statsbiblioteket.dk

VICTOR ALBECKS VEJ 1
8000 AARHUS C

CVR/SE 1010 0682 - EAN 5798000791084

#8

@nef, do you mean that the problem is resolved, or that the problem reoccurs even after changing the article metadata to reflect a http-prefixed ORCID iD?

If the problem persists, please post the latest error.

#9

I mean, from the very start I used http and not https, so that can’t be the reason. I haven’t changed anything so the error is still the same
Niels Erik Frederiksen
Forskningsbibliotekar, cand. mag. / Research Librarian, MA
Studie- og Forskningsservice
DIRECT +45 8946 2179
MOBILE +45 2167 2417
email: nef@statsbiblioteket.dkmailto:nef@statsbiblioteket.dk

VICTOR ALBECKS VEJ 1
8000 AARHUS C

CVR/SE 1010 0682 - EAN 5798000791084

#10

That would be weird, given that the error message is quoting 'https:\/\/orcid.org\/0000-0002-6281-9981' as the value. Can you confirm this via:
User Home -> Editor -> (select article) -> Editing -> Review Metadata
for each of “10.7146/ojssb.v6i6.21245”,“10.7146/ojssb.v6i6.21246”,“10.7146/ojssb.v6i6.21248”,“10.7146/ojssb.v6i6.21250”, and “10.7146/ojssb.v6i6.21251”?

#11

Here you can see it. It’s in Danish but I hope you can recognise nevertheless

[cid:b5f03c0a-e0ce-4a15-9d42-2ac822e57be2]
Niels Erik Frederiksen
Forskningsbibliotekar, cand. mag. / Research Librarian, MA
Studie- og Forskningsservice
DIRECT +45 8946 2179
MOBILE +45 2167 2417
email: nef@statsbiblioteket.dkmailto:nef@statsbiblioteket.dk

VICTOR ALBECKS VEJ 1
8000 AARHUS C

CVR/SE 1010 0682 - EAN 5798000791084

#12

“URL-adresse” looks like the value for user.url, not user.orcid. We would be looking for a case where the ORCID iD was filled in with https.

#13

Thank you for the answer. I surely made a mistake there. Concerning the other articles in that issue I used the right field (ORCID iD) but they failed too. Is that because I made that one failure?

Regards
Niels Erik

#14

Yes, I believe Crossref accepts a batch as all-or-nothing. I think you can submit the articles in smaller batches or individually for more specific testing.

#15

Now it seems to work except for one thing. It’s still showing the ‘failed’ link:

When I click the link the ‘error’ says:
{“status”:“ok”,“message-type”:“deposit”,“message-version”:“1.0.0”,“message”:{“handoff”:{“delay-millis”:2718.2818284590458,“status”:“completed”,“timestamp”:1440669930924,“try-count”:1},“dois”:[“10.7146/ojssb.v6i6.21245”,“10.7146/ojssb.v6i6.21250”,“10.7146/ojssb.v6i6.21251”],“parent”:null,“filename”:null,“submitted-at”:“Thu Aug 27 12:05:30 CEST 2015”,“status”:“completed”,“length”:4634,“content-type”:“application/vnd.crossref.deposit+xml”,“pingback-url”:null,“submission”:{“submission-id”:“1383736016”,“batch-id”:“16d0728f-dc27-49dc-8949-3158498fbb55”,“record-count”:3,“success-count”:3,“warning-count”:0,“failure-count”:0,“messages”:[{“status”:“success”,“related-doi”:“10.7146/ojssb.v6i6.21245”,“message”:“Successfully updated”,“message-types”:[]},{“status”:“success”,“related-doi”:“10.7146/ojssb.v6i6.21250”,“message”:“Successfully updated”,“message-types”:[]},{“status”:“success”,“related-doi”:“10.7146/ojssb.v6i6.21251”,“message”:“Successfully updated”,“message-types”:[]}]},“test”:false,“owner”:“aaul”,“batch-id”:“16d0728f-dc27-49dc-8949-3158498fbb55”}}

Apparently it is “Successfully updated” so why the ‘failed’ link?
Regards
Niels Erik

#16

Hola, escribo desde Chile.
En mi universidad se ha actualizado la forma de referenciar los DOI en OJS y ahora tenemos problemas con la exportación de datos XML para crossref.(plugin Crossref)
Cómo podemos solucionar este problema?
Saludos Laura

#17

Hola @lnavarro,

Can you provide details about the problem you’re encountering?

Regards,
Alec Smecher
Public Knowledge Project Team

#18

Hi Alec, thank you for your response.
My english is not good : )
The problem is,
A couple month ago, we changed the version OJS, since that moment we can´t generate the crossref file XML. the report said:
"…Exportar Datos
Un prefijo DOI debe ser indicado en las páginas de gestión para poder utilizar este plugin.

##manager.setup.doiPrefixDescription##

…"
We did that and also we upgraded the plugin crossref ; but the error stills.

What can we do?

regards Laura

#19

Hi @lnavarro,

What version of OJS are you using?

Regards,
Alec Smecher
Public Knowledge Project Team

#20

We using version OJS 2.4.5.0