CrossRef XML Export Plugin "not working" or "working"

Hi there; I’m trying to submit dois through OJS 3. I check the articles to export, check the xml, and press “Submit”. A “Success” message is returned. However, the xml doesn’t seem to get to CrossRef. Information: I did give it 24 hours…, does anyone know if this queue for submissions takes longer than that at CrossRef. Also, though it seems to be a non-issue, when I look at the xml in Oxygen the xml schema displays as an error, i.e. the

<?xml version="1.0" encoding="utf-8"?>. In Oxygen, when I backspace and re-enter "?xml" the error disappears. I don't think this has anything to do with anything -- I just noticed it. My submission, as noted above, returns "Success".

I’m hoping I’m just missing something here… but if anyone has been successful and there’s a step I’ve lost I would be thankful for your indulgence.

Cheers,
DM

Hi there! The current plugin for 2.4.x and 3.x runs on an older Crossref API that sometimes doesn’t update submission status after successful registration. This is frustrating for a variety of reasons. My recommendation is to check to see if any of these DOIs have resolved by visiting them as you would if they were linked (ie, https://doi.org/prefix/suffix). It’s pretty common for DOIs to show their status as “submitted” in the crossref plugin but still have successfully registered.

If they aren’t currently registered, it’s possible that one of the submissions themselves was problematic. You can export a whole issue at once by downloading the XML and parsing it using Crossref’s parsing tools to see if you get any errors. crossref.org : metadata quality check

We’re working on releasing a new Crossref plugin for 3.1.2 that uses a different crossref API and ought to resolve these issues for folks. In the meantime, the best way to check is by checking the links and via XML deposit to the Crossref backend (https://doi.crossref.org)

Please let me know if you have any follow-up questions.

Cheers,
Mike

Thanks. That helps. For what we’re doing I have a suspicion the most efficient way around this, at this time, is to download from OJS, parse the xml, then upload directly into CrossRef.
https://forum.pkp.sfu.ca/t/crossref-xml-export-plugin-not-working-or-working/51333
forum.pkp.sfu.ca
crawl=CC-MAIN-2022-49
21739
application/http; msgtype=response
sha1:UXHWUN763DHUS3T6JXWAFBD2UIGRFNQU
<urn:uuid:cff0b30d-756b-43db-9683-639800ca2cdc>
2022-12-05T14:37:59Z
142.58.229.37
text/html
sha1:N4ZV76Z3XINOI6MSICHSP5QLU2QJEETV
<urn:uuid:71cdac42-a572-46a1-a1fc-5db8626ffea4>
https://forum.pkp.sfu.ca/t/crossref-xml-export-plugin-not-working-or-working/51333
response
<urn:uuid:2ffbbdf8-c118-483d-b1f0-18b9b2e5230e>
isPartOf: CC-MAIN-2022-49
publisher: Common Crawl
description: Wide crawl of the web for November/December 2022
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-17
software: Apache Nutch 1.19 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.4-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/