We are very pleased to kick off the New Year with another important schema update and the news that a Grant DOI field is now supported for all record types. This means that Crossref members can explicitly include the Crossref Grant IDs as part of their DOI metadata records for publications and any other output type, accurately linking research outputs to the funding that made it possible, all through metadata. We hope that our members will leverage this to respond to recent calls for stronger funding transparency and best practices for reporting funding sources in research outputs.Â
As we finish celebrating our 25th anniversary, we can look back on a truly transformational year, defined by the successful delivery of several long-planned, foundational projects—as well as updates to our teams, services, and fees—that position Crossref for success over the next quarter century as essential open scholarly infrastructure. In our update at the end of 2024, we highlighted that we had restructured our leadership team and paused some projects. The changes made in 2024 positioned us for a year of getting things done in 2025. We launched cross-functional programs, modernised our systems, strengthened connections with our growing global community, and streamlined a bunch of technical and business operations while continuing to grow our staff, members, content, relationships, and community connections.
Crossref turned twenty-five this year, and our 2025 Annual Meeting became more than a celebration—it was a shared moment to reflect on how far open scholarly infrastructure has come and where we, as a community, are heading next.
Over two days in October, hundreds of participants joined online and in local satellite meetings in Madrid, Nairobi, Medan, Bogotá, Washington D.C., and London––a reminder that our community spans the globe. The meetings offered updates, community highlights, and a look at what’s ahead for our shared metadata network––including plans to connect funders, platforms, and AI tools across the global research ecosystem.
In my latest conversations with research funders, I talked with Hannah Hope, Open Research Lead at Wellcome, and Melissa Harrison, Team Leader of Literature Services at Europe PMC. Wellcome and Europe PMC are working together to realise the potential of funding metadata and the Crossref Grant Linking System for, among other things, programmatic grantee reporting. In this blog, we explore how this partnership works and how the Crossref Grant Linking System is supporting Wellcome in realising their Open Science vision.
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
