We have encountered a problem where the DOIs assigned to some articles remain in the “submitted” status and are not being properly registered. This issue persists despite the fact that the DOIs for the first two articles we published were successfully registered and are working correctly. The other articles, however, continue to show the “submitted” status without completing the registration process (as indicated in the attached image).
OJS version: 3.4.0.7
DOI registration agency: Crossref
prefix: 10.69998
However, before you try what is suggested there, it might be best if you could share any PHP error log messages - that may provide more clues if you are experiencing the same issue.
Thank you for your response.
This issue doesn’t seem to apply to us, as we are able to download the XML file without any failures.
We have tried downloading the XML file via ‘Bulk Actions’ >> ‘Export DOIs,’ and we are attempting to manually upload this file through the Crossref dashboard (Crossref >> Submissions >> Upload Metadata).
Unfortunately, the problem still persists."
Without seeing your installation, it’s hard to guess what’s happening. Have you tried just re-submitting the ones with the label “submitted”? You should be able to push an update whenever. Depending on when you first tried to register those, it’s possible they failed to deposit due to Crossref downtown. About two=three weeks before the date on your screenshot, Crossref’s deposit API was down for maintenance for a few days. It’s possible they were “sent” to Crossref but that’s it.
Basically, all “submitted” means is that OJS successfully gave the deposit to Crossref and you don’t see “active” until Crossref has processed that deposit.
I’d start there. Just try to redeposit these first and let us know how it goes. If you can check your error logs and share anything there when you click on the deposit button, please do.
However, this does look very much like an issue I’ve talked to @ewhanson about and it would be nice to get to the bottom of it if it’s a bug we can successfully repeat. Please let us know how the re-deposit attempt goes and if you have any errors. If this is the same bug, we’ll need to be able to repeat it to fix it.
