This past year has been a captivating journey of immersion within the Crossref community, a mix of online interactions and meaningful in-person experiences. From the engaging Sustainability Research and Innovation Conference in Port Elizabeth, South Africa, to the impactful webinars conducted globally, this has been more than just a professional endeavour; it has been a personal exploration of collaboration, insights, and a shared commitment to pushing the boundaries of scholarly communication.
One of the challenges that we face in Labs and Research at Crossref is that, as we prototype various tools, we need the community to be able to test them. Often, this involves asking for deposit to a different endpoint or changing the way that a platform works to incorporate a prototype.
The problem is that our community is hugely varied in its technical capacity and level of ability when it comes to modifying their platform.
When each line of code is written it is surrounded by a sea of context: who in the community this is for, what problem we’re trying to solve, what technical assumptions we’re making, what we already tried but didn’t work, how much coffee we’ve had today. All of these have an effect on the software we write.
By the time the next person looks at that code, some of that context will have evaporated.
It turns out that one of the things that is really difficult at Crossref is checking whether a set of Crossref credentials has permission to act on a specific DOI prefix. This is the result of many legacy systems storing various mappings in various different software components, from our Content System through to our CRM. To this end, I wrote a basic application, credcheck, that will allow you to test a Crossref credential against an API.
Pending publication is a way of creating a DOI and depositing metadata for a content item any time after a manuscript has been accepted but before it is published online. This is possible for all standard record types (such as articles, books, conference proceedings).
Because a pending publication has not yet been published, its DOI will resolve to a publicly-available Crossref-hosted landing page. Once the work is published online, this same DOI will resolve to the URL for that content.
The pending publication record type serves as a temporary placeholder for your content - like a “coming soon” or preview of the great work to come. For a pending publication, you register basic metadata for your content item before registering all the formal metadata that comes with a version of record. Take care not to share a DOI before it has been deposited with us, or it will not resolve for your readers, and will lead to a failed resolution in your resolution report. Learn more about the pending publication consultation.
Use cases for pending publication
Before the pending publication record type existed, we recommended you to register DOIs at the time content was published online, or shortly after. As the communication needs of our members (researchers, funders, institutions, and publishers) evolve, we have created this new solution to aid you and your work, and allow you to register DOIs before content is published online. With pending publication:
Members can:
address timing issues related to press embargos
publicly establish scholarly precedence for their articles
meet the conditions in full for new funder policies and mandates, which focus on acceptance as a key event to report on
ensure that institutional repositories use the DOI to link to the member-stewarded copy
Researchers can provide formal evidence of all publications in employment and grant applications
Funders can fully track all publications funded by their research grants
Institutions can fully track the scholarly output of their faculty members
Technology vendors that support scholarly research management can account for all outputs
How does pending publication work?
When registering your publication as pending there are two things you need to do:
Register a subset of the metadata (as a minimum: member name, journal title, and accepted date) under the Pending Publication record type.
After you do this, the DOI will resolve to a Crossref-hosted landing page displaying your logo, a banner showing the manuscript has been accepted for publication, and the metadata you’ve provided. As with all registered content, pending publication metadata will be publicly available in our APIs (and updated as you update your metadata records).
Once your work is published, you need to register the full metadata for the work - this is not an automatic process. You must update the metadata for each pending publication DOI, so that each DOI will resolve directly to the content (and not the pending publication landing page).
Pending publication workflow diagram
Crossmark participants please note that you can deposit Crossmark metadata at any point, but during the Beta version of the pending publication rollout, the Crossmark badge will not be displayed to readers.
Fees for pending publications
Content Registration (metadata deposit) fees still apply, but there are no additional fees for using pending publication. So, you’ll be charged once when you register the pending publication, but any subsequent updates, including the update on publication, are not charged.
History
Pending publication has been supported since 2019 and was designed in response to community feedback: