"ORCID error" exporting xml from crossref exportation plugin

Software Support
1

  • Application Version:OJS 3.2.1-1

  • Description of issue:

XML ERROR:

<?xml version="1.0" encoding="UTF-8"?>

<doi_batch_diagnostic status=“completed” sp=“ds3.crossref.org”>
<submission_id>1472987551</submission_id>
<batch_id>_1593807235</batch_id>
<record_diagnostic status=“Failure”>

Error: cvc-complex-type.2.4.d: Invalid content was found starting with element ‘ORCID’. No child element is expected at this point.

</record_diagnostic>
<batch_data>
<record_count>1</record_count>
<success_count>0</success_count>
<warning_count>0</warning_count>
<failure_count>1</failure_count>
</batch_data>
</doi_batch_diagnostic>

At first I thought the profile link to ORCID was wrong. But you can check that the link works correctly: El género Phytophthora (Peronosporales) en Argentina | Boletín de la Sociedad Argentina de Botánica

Does anyone have any idea what might be going wrong?

1 Like
2

I have the same error.
Have no idea why it happened (

3

Hi @Oleksandr_Radkevych, @didoemilio,

Can you please attach the XML file here to investigate it?

Regards, Primož

4

Hi
I attach the XML!
XML

Ty

5

Hi @Oleksandr_Radkevych,

Hm, sorry, I don’t find the error. Why don’t you try to send the XML and the error to the CrossRef support and ask for help?

Regards, Primož

6

From now I wait answer from them )
Ty

7

Some news from crossref?

8

Hi, Felix

from crossref nothing useful
I was reinstall ojs 3.2.0
Everything works well

9

This issue is resolved in OJS master branch on 19.10.2020 by the following PR.

10

Hi,

I’m getting same error on OJS 3.2.1-4 (not sure if it also happens with last stable).

The fix was published here but I think it was not included in 3.2 branch. If it fixes the issue, would be great if it can be included in last 3.2 stable.

For others falling know in this same issue (while it was added to 3.2 or if you don’t know how to apply the patch), notice it only happens when authors have an orcid AND multilang names. So an obvious workaround is… removing name and givenname in all langs and keep it in ONLY primary language. And in the few cases where this is not possible, you can download the xml, edit (as explained in gitHub) and upload to CrossRef manually.

Cheers,
m.

1 Like