In January 2026, our new annual membership fee tier takes effect. The new tier is US$200 for member organisations that operate on publishing revenue or expenses (whichever is higher) of up to US$1,000 annually. We announced the Board’s decision, making it possible in July, and––as you can infer from Amanda’s latest blog––this is the first such change to the annual membership fee tiers in close to 20 years!
The new fee tier resulted from the consultation process and fees review undertaken as part of the Resourcing Crossref for Future Sustainability program, carried out with the help of our Membership and Fees Committee (made up of representatives from member organisations and community partners). The program is ongoing, and the new fee tier, intended to make Crossref membership more accessible, is one of the first changes it helped us determine.
It has been 18 (!) years since Crossref last deprecated a metadata schema. In that time, we’ve released numerous schema versions, some major updates, and some interim releases that never saw wide adoption. Now, with 27 different schemas to support, we believe it’s time to streamline and move forward.
Starting next year, we plan to begin the process of deprecating lightly-used schemas, with the understanding that this will be a multi-year effort involving careful planning and plenty of communication.
Scholarly metadata, deposited by thousands of our members and made openly available can act as “trust signals” for the publications. It provides information that helps others in the community to verify and assess the integrity of the work. Despite having a central responsibility in ensuring the integrity of the work that they publish, editorial teams tend not be fully aware of the value of metadata for integrity of the scholarly record. How can we change that?
Crossref was created back in 2000 by 12 forward-thinking scholarly publishers from North America and Europe, and by 2002, these members had registered 4 million DOI records. At the time of writing, we have over 23,600 members in 164 different countries. Half of our members are based in Asia, and 35% are universities or scholar-led. These members have registered over 176 million open metadata records with DOIs (as of today). What a difference 25 years makes!
In our 25th anniversary year, I thought it would be time to take a look at how we got here. And so—hold tight—we’re going to go on an adventure through space and time1, stopping every 5 years through Crossref history to check in on our members. And we’re going to see some really interesting changes over the years.
Registering your DOI records using the OJS platform
In order to register DOI records with Crossref, you need to set up your OJS (Open Journal Systems) platform to create DOIs on your Crossref DOI prefix, and also set up your OJS platform to send your records to Crossref. You do this in a different way depending on whether you are using OJS 3.4 or OJS 3.3:
You can download the newest versions of OJS in the Public Knowledge Project’s (PKP) documentation.
Additional OJS plugins for Crossref
There are also other important plugins that can be enabled in OJS to enrich your metadata records:
Funding Metadata plugin - as of OJS 3.1.2, it is possible to enable a funder registry plugin for submitting funding information to Crossref. The plugin will use the Open Funder Registry to check against existing funding agencies. The plugin will include funding information in your Crossref DOI deposits.
Similarity Check plugin - if you are using OJS 3.1.2 or above, you are able to use the Similarity Check plugin. This will enable you to automatically send manuscripts to your iThenticate account to check their similarity to already published content. You will need to be subscribed to Crossref’s Similarity Check service for this to work.
ROR plugin - the ROR Plugin for OJS enables authors to add the ROR ID for the organization they are affiliated with.
Getting help with OJS plugins
The team at Crossref didn’t create these plugins - they were either created by the team at PKP, or by third-party developers. Because of this, we aren’t able to give in-depth help or troubleshooting on problems with these plugins.
