We were delighted to engage with over 200 community members in our latest Community update calls. We aimed to present a diverse selection of highlights on our progress and discuss your questions about participating in the Research Nexus. For those who didn’t get a chance to join us, I’ll briefly summarise the content of the sessions here and I invite you to join the conversations on the Community Forum.
You can take a look at the slides here and the recordings of the calls are available here.
We have some exciting news for fans of big batches of metadata: this year’s public data file is now available. Like in years past, we’ve wrapped up all of our metadata records into a single download for those who want to get started using all Crossref metadata records.
We’ve once again made this year’s public data file available via Academic Torrents, and in response to some feedback we’ve received from public data file users, we’ve taken a few additional steps to make accessing this 185 gb file a little easier.
In 2022, we flagged up some changes to Similarity Check, which were taking place in v2 of Turnitin’s iThenticate tool used by members participating in the service. We noted that further enhancements were planned, and want to highlight some changes that are coming very soon. These changes will affect functionality that is used by account administrators, and doesn’t affect the Similarity Reports themselves.
From Wednesday 3 May 2023, administrators of iThenticate v2 accounts will notice some changes to the interface and improvements to the Users, Groups, Integrations, Statistics and Paper Lookup sections.
We’ve been spending some time speaking to the community about our role in research integrity, and particularly the integrity of the scholarly record. In this blog, we’ll be sharing what we’ve discovered, and what we’ve been up to in this area.
We’ve discussed in our previous posts in the “Integrity of the Scholarly Record (ISR)” series that the infrastructure Crossref builds and operates (together with our partners and integrators) captures and preserves the scholarly record, making it openly available for humans and machines through metadata and relationships about all research activity.
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://0-doi-org.lib.rivier.edu/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.
If you don’t receive your submission log email and you can’t see your submission in the queue, it may be that your access to register content has been suspended due to unpaid invoices. If this is the case, please contact us.
Verify your registration - grant deposit form
The grant registration form registers your record in real time, with no queueing or delay. If your submission has been successful, you’ll see a “success” message, which means your DOI is now live and active or your update to an existing DOI has worked.
Your “success” message will also contain a submission ID. If you need to, you can log into our admin tool using your account credentials and use this submission to view your deposit.
If your submission hasn’t been successful, you’ll see an error message explaining the problem.
Verify your registration - if you’re still using the deprecated Metadata Manager
The Metadata Manager tool is in beta and contains many bugs. It’s being deprecated at the end of 2021. We recommend using the web deposit tool as an alternative, or the OJS plugin if your content is hosted on the OJS platform from PKP.
If you’re still using Metadata Manager, here’s how to verify your registration.
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 using your account credentials 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.
If you don’t receive your submission log email and you can’t see your submission in the queue, it may be that your access to register content has been suspended due to unpaid invoices. If this is the case, please contact us.
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 plugin settings page.
Page owner: Isaac Farley | Last updated 2022-July-22
