2020 wasn’t all bad. In April of last year, we released our first public data file. Though Crossref metadata is always openly available––and our board recently cemented this by voting to adopt the Principles of Open Scholarly Infrastructure (POSI)––we’ve decided to release an updated file. This will provide a more efficient way to get such a large volume of records. The file (JSON records, 102.6GB) is now available, with thanks once again to Academic Torrents.
Our colleague and friend, Kirsty Meddings, passed away peacefully on 10th December at home with her family, after a sudden and aggressive cancer. She was a huge part of Crossref, our culture, and our lives for the last twelve years.
Kirsty Meddings is a name that almost everyone in scholarly publishing knows; she was part of a generation of Oxford women in publishing technology who have progressed through the industry, adapted to its changes, spotted new opportunities, and supported each other throughout.
Crossref has supported depositing metadata for preprints since 2016 and peer reviews since 2018. Now we are putting the two together, in fact we will permit peer reviews to be registered for any content type.
2020 has been a very challenging year, and we can all agree that everyone needs a break. Crossref will be providing very limited technical and membership support from 21st December to 3rd January to allow our staff to rest and recharge. We’ll be back on January 4th raring to answer your questions. Amanda explains more about why we made this decision.
The quickest way to test whether your DOI and its associated metadata have been registered successfully (and your DOI is now active) is to enter your DOI link (DOI displayed as a link, such as https://doi.org/10.13003/5jchdy) into a browser window, and check if it resolves correctly.
If your DOI doesn’t resolve successfully, read on for more information about the process your submission goes through, why there might be a delay, and which messages you’ll receive depending on your submission method.
If you register your content using the web deposit form, your submission is sent to a submission queue. You’ll see a “success” message in the web deposit form confirming that your submission has been successfully sent to our submission queue, but this doesn’t mean that your registration is complete.
As your submission is processed in the queue, we send you two messages:
XML record email, subject line: Crossref WebDeposit - XML. This email includes the XML created by the web deposit form. Do keep this information, as it may be useful in the future. Receiving this email is a confirmation that your file has been received for processing, and entered into our submission queue.
submission log email, subject line: Crossref Submission ID. This email is sent once your XML has made it through the queue, includes your submission ID, tells you if your deposit has been successful, and provides the reason for any failure.
If your submission log email tells you that your submission was successful, your DOI is now live and active (or your update to metadata for an existing DOI has worked).
If your submission failed, please address the errors flagged in the confirmation, and resubmit. Learn more about error messages.
If you don’t receive your submission log email immediately, it’s probably because your submission is still in the queue. It can stay in the queue between several minutes and several hours depending on how large your submission file is, and how busy our submission queue is at that time. Learn more about how to view the submission queue.
Verify your registration - Metadata Manager
Unlike other content registration methods, Metadata Manager registers content in real-time - with no queueing of content. If your submission has been successful, you’ll see a “success” message, which means that your DOI is now live and active (or your update to metadata for an existing DOI has worked).
Your “success” message will also contain a submission ID. If you need to, you can log in to our admin tool and use this submission ID to view your deposit.
If your submission hasn’t been successful, you’ll see a warning symbol - click on this to see the error message explaining the problem.
Verify your registration - direct deposit of XML using our admin tool
Submissions using our admin tool are sent to a submission queue. Once your submission has been accepted into the queue we display a SUCCESS - Your batch submission was successfully received message. This means that your deposit has been submitted to our processing queue, but it has not yet been processed.
Registration of your content only occurs after your submission has worked its way through the queue, when you will receive an email with the subject line Crossref Submission ID, which includes your submission ID, tells you if your deposit has been successful, and provides the reason for any failure.
If your deposit has been successful, then your new DOI is live and active (or your update to metadata for an existing DOI has worked).
If your submission failed, please address the errors flagged in the email, and resubmit. Not sure what the error messages mean and what you need to do? Learn more about error messages.
If you don’t receive your submission log email immediately, it’s probably because your submission is still in the queue. It can stay in the queue between several minutes and several hours depending on how large your submission file is, and how busy our submission queue is at that time. Learn more about how to view the submission queue.
Verify your registration - XML deposit using HTTPS POST
Most items registered with us are submitted via HTTPS POST. When files are POSTed to our system, you’ll receive a 200 status message to confirm that we’ve received it. Your files are then added to a submission queue to await processing, and once your submission has been processed, you’ll receive a submission log (either by email or through the notification callback service if you have that enabled).
If your submission log shows a success, then your DOI is live and active (or your update to metadata for an existing DOI has worked).
If your submission log shows a failure, please address the errors flagged in the email, and resubmit. Not sure what the error messages mean and what you need to do? Learn more about error messages.
There may be a delay between your submission being received by the queue and completing processing. It can stay in the queue between several minutes and several hours depending on how large your submission file is, and how busy our submission queue is at that time. Learn more about how to view the submission queue.
Verify your registration - Crossref XML plugin for OJS
If you are using the Crossref XML plugin for OJS to send your submission to us directly, check the status of your deposit by clicking the Articles tab at the top of the Crossref plugin settings page.
Page owner: Laura J. Wilkinson | Last updated 2020-April-08
