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.