To date, there are about 100 Crossref members who have made use of our co-access service for one or more of their books. The service was designed to be a last-resort measure when multiple parties - book publishers, aggregators, and other members - had rights to register book content. Unfortunately, the service allowed members to register multiple DOIs for shared books and book chapters, thereby violating our own core tenet of one DOI per content item. We should not have created a service that violated that tenet, resulting in duplicate DOIs. As we are able to offer an alternative in the form of the multiple resolution service, it is time to switch co-access off. Among other benefits – for the publisher and the authors, creation of a single DOI for each item, regardless of where it might be hosted, will result in more accurate citation counts and usage statistics. We’re retiring co-access at the end of 2026.
This month marks one year since the Dutch Research Council (NWO) introduced grant IDs—an important milestone in our journey toward more transparent and trackable research funding. We created over 1,600 Crossref Grant IDs with associated metadata. We are beginning to see them appear in publications. These early examples show the enormous potential Grant IDs have. They also highlight that publishers could extend their efforts to improve the quality of funding metadata of publications.
eLife recently won a Crossref Metadata Award for the completeness of its metadata, showing itself as the clear leader among our medium-sized members. In this post, the eLife team answers our questions about how and why they produce such high-quality open metadata. For eLife, the work of creating and sharing excellent metadata aligns with their mission to foster open science and supports their preprint-centred publication model, but it also lays the groundwork for all kinds of exciting potential uses.
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
