Hi. The last batch of articles on OJS has failed to assign DOIs, even though it was all working fine before and afaik nothing has changed in the interim. Seems that the plugin is sending correctly, but failing to register. Failure notification says:
Submission was not successful! The DOI registration server returned an error: '1 - HTTP/1.1 100 Continue
HTTP/1.1 400 Bad Request
date: Tue, 22 Jun 2021 08:48:20 GMT
What should I do to fix this? Does anyone know what the error is identifying?
Perhaps you could try that and let me know if it works?
And, just a note, that the version of OJS that you’re using (3.0) is no longer supported by PKP. I recommend that you upgrade to the newest version of OJS, as there are some improvements in OJS and the Crossref plugins that you may wish to take advantage of. Along with that, you may wish to upgrade your Crossref plugin.
In an open ticket with Crossref, their support reports that you should still be able to download the XML export from OJS and upload that manually. This should, however, be considered to be a secondary workaround to upgrading to a more recent version of OJS. OJS 220.127.116.11 is extremely old, and is subject to a number of security advisories. [C.f. #3805#3944/#4024#5302#5871]
The API endpoint “https://api.crossref.org/deposits” stopped working a few weeks ago, hence this errors with older version of OJS and (the corresponding CrossRef plugin). But appears to be back online, so everything should be alright now.
Hi all, I’m Bryan Vickery, Director of Product at Crossref. Our analysis of the usage of the v1 deposit suggested that it wasn’t being used, and we didn’t have information on the installs of older versions of OJS. At least now we know it is, by a few of you.
Typically we would not end the life of a service so swiftly, however - we are about to release a new version of our REST API on July 13 and we can’t guarantee that this old v1 deposit API will continue to work after that date.
A change we made on June 10th should not have removed the v1 deposit API from use, but having reverted that change, and noted that users can register content again, we can only assume that it did. We apologise for the inconvenience.
In summary, we will cutover to our new REST API on July 13th. The v1 deposit API is deprecated and unsupported - if, during the REST API roll out, the v1 deposit API breaks, we may not be able to fix it I’m afraid.
If that happens, you can continue to export your xml, and upload it to Crossref’s systems or you could, and probably should, upgrade your OJS instance to a supported version that makes use of the v2 deposit API.
The JSON / REST API is a separate API for metadata retrieval, but because of the way our APIs were organised we couldn’t guarantee that the v1 deposit API would continue to work when we released the latest version of our JSON / REST API.
The v2 deposit API will still continue to function and is our current deposit API. PKP does not need to update.
May we know if the XML files generated with the older version of OJS (like 18.104.22.168) will remain possible?
At the moment it works well and can be used as a valid alternative to register/activate DOIs with Crossref.
Hi again. Our analysis of the usage of our dedicated OJS v1 deposit API (used in older versions of OJS, 3.1.1 and earlier) suggested that it wasn’t being used, and we didn’t have information on the installations of older versions of OJS. It turns out there are still a few of you.
Typically, we would not intentionally remove a service so suddenly, without notifying users, however, in the final stages before we released a new version of our REST API (July 13) we discovered that it might have an impact on this OJS v1 deposit API. The v1 deposit API was deprecated and unsupported, as is the case for the older versions of OJS as notified by PKP. We took the decision to release the new REST API knowing that if the v1 deposit API were to break, we may not be able to fix it, but that there were workarounds for our members:
you can continue to export your xml, and upload it to Crossref’s systems; or
you could—-and probably should—-upgrade your OJS instance to a supported version that makes use of the v2 deposit API (OJS 3.1.2 or higher).
On rolling out our new REST API the v1 deposit API did indeed break, and we’re not able to make it work again. I’m really sorry that we didn’t communicate that this would happen and that it has caused some disruption to a few of our members registering content automatically via OJS. I will ensure we learn lessons from this and update our deprecation plans for the future.