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.
Not sure if you’re using iThenticate v1 or iThenticate 2.0? More here.
Not sure whether you’re an account administrator? Find out here.
Private Repository - ScholarOne only
The Submitted Works repository (or Private Repository) is a new feature in iThenticate 2.0. The only MTS that currently integrates with this feature is ScholarOne. This feature allows users to find similarity not just across Turnitin’s extensive Content Database but also across all previous manuscripts submitted to your iThenticate account for all the journals you work on. This would allow you to find collusion between authors or potential cases of duplicate submissions.
How does this work?
You have received a manuscript from Author 1 and have decided to index this manuscript into your Submitted Works repository. At some point later you receive a new manuscript from Author 2. When generating your Similarity Report, you have decided to check against your Submitted Works repository. There is a paragraph in the manuscript from Author 2 which matches a paragraph in the manuscript from Author 1. This would be highlighted within your Similarity Report as a match against your Submitted Works repository.
By clicking on this match you can see the full text of the submission you’ve matched against:
And details about the submission, such as the name and email address of the user who submitted it, the date it was submitted and the title of the submission:
The ability to see the full source text and the details can both be switched off individually.
Setting up the Submitted Works repository
If you are using a third party integration then you should have options inside your MTS when setting up your configuration with iThenticate to decide whether submissions will be indexed to the Submitted Works repository and whether generated Similarity Reports will match against the Submitted Works.
Important: This feature means that sensitive data could be shared between different journals using your iThenticate account
The Submitted Works repository is shared across your entire iThenticate account. This means regardless of whether a submission was made natively from the iThenticate website or through an integration, all Similarity Reports which match against the Submitted Works repository will potentially match against any submissions which were indexed within it. This means that an editor working on one journal may be able to view submissions for another journal. If you are worried about giving your users access to sensitive data, we recommend switching this functionality off.
Submitted Works repository FAQs
Q. How much does this feature cost to use?
This feature comes free with every iThenticate 2.0 account.
Q. How many submissions can I index to my private repository?
There is no limit to the number of submissions you can index.
Q. Can I delete submissions from my private repository?
Yes. An Administrator can find and delete a submission using the Paper Lookup Tool. Go to Turnitin’s help documentation for more information.
Page maintainer: Kathleen Luschek Last updated: 2022-July-15
