We have some rather unusual news to share: Crossref fees are going down again. At its meeting in Paris earlier this month, the Crossref Board approved two further recommendations from the Resourcing Crossref for Future Sustainability (RCFS) project: effective 1st January 2027, we will reduce the majority of Content Registration fees for all 25,000 members, and remove fees for back-year records altogether.
Content Registration fees haven’t increased in around 20 years, and this is the first significant change to them in that time—downwards. Since these fees account for the largest share of Crossref’s revenue (around 60%), and since every member registers DOI records, these changes reach further than anything we’ve announced under the RCFS project so far.
The infrastructure that registers and distributes Crossref metadata has been running and growing for more than two decades. It now does considerably more than it was built to do, and it shows: two large, tightly coupled monoliths (Content System and REST API), where a change in one place risks breaking something in another.
In December 2026, we plan to publish new Crossref Member Practices which will set out the standards we expect all Crossref members to meet. From August to October 2026 we are consulting with our members on a draft of these Member Practices. This blog provides the background to this, and explains how you can share your views.
The Crossref community in India is as diverse as the region that it represents, comprising 1605 members, 11 sponsoring organisations, and 5 ambassadors, who between them cover the length and breadth of this country. Between November 2025 and March 2026, we organised three webinars focused on supporting this community with best metadata and publishing practices. We collaborated with the Directory of Open Access Journals (DOAJ) and the Committee on Publication Ethics (COPE) to embed understanding of metadata’s role in the greater context of publishing integrity.
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