Looking back over 2024, we wanted to reflect on where we are in meeting our goals, and report on the progress and plans that affect you - our community of 21,000 organisational members as well as the vast number of research initiatives and scientific bodies that rely on Crossref metadata.
In this post, we will give an update on our roadmap, including what is completed, underway, and up next, and a bit about what’s paused and why.
The Crossref2024 annual meeting gathered our community for a packed agenda of updates, demos, and lively discussions on advancing our shared goals. The day was filled with insights and energy, from practical demos of Crossrefâs latest API features to community reflections on the Research Nexus initiative and the Board elections.
Our Board elections are always the focal point of the Annual Meeting. We want to start reflecting on the day by congratulating our newly elected board members: Katharina Rieck from Austrian Science Fund (FWF), Lisa Schiff from California Digital Library, Aaron Wood from American Psychological Association, and Amanda Ward from Taylor and Francis, who will officially join (and re-join) in January 2025.
Background The Principles of Open Scholarly Infrastructure (POSI) provides a set of guidelines for operating open infrastructure in service to the scholarly community. It sets out 16 points to ensure that the infrastructure on which the scholarly and research communities rely is openly governed, sustainable, and replicable. Each POSI adopter regularly reviews progress, conducts periodic audits, and self-reports how theyâre working towards each of the principles.
In 2020, Crossrefâs board voted to adopt the Principles of Open Scholarly Infrastructure, and we completed our first self-audit.
In June 2022, we wrote a blog post âRethinking staff travel, meetings, and eventsâ outlining our new approach to staff travel, meetings, and events with the goal of not going back to ânormalâ after the pandemic. We took into account three key areas:
The environment and climate change Inclusion Work/life balance We are aware that many of our members are also interested in minimizing their impacts on the environment, and we are overdue for an update on meeting our own commitments, so here goes our summary for the year 2023!
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.libus.csd.mu.edu/10.13003/5jchdy) into a browser window, and check if it resolves correctly. DOI 10.13003/5jchdy has been registered so it is resolving to that DOI’s landing page (or, resolution URL). DOIs that have not been registered will resolve to a DOI NOT FOUND error message on doi.org, such as https://0-doi-org.libus.csd.mu.edu/10.13003/unregisteredDOI.
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 2024-October-07
