You can now register rich metadata for a variety of record types in Metadata Manager using simple, guided workflows. The tool is used by many in our community to register grant and journal article records, and it has now been expanded to support books and chapters, reports, dissertations, and post-publication updates for journal content.
Metadata Manager makes it easier to capture identifiers for contributors and their affiliations, funding information, references, and more. Thanks to automated reference matching by Crossref, this offers greater visibility for the works, while the affiliations and funding information can serve as important trust signals for the community.
This year’s edition of the FORCE11 conference was hosted in June by Singapore Management University. Its title, âTo Go Far, Go Together: Advancing Scholarly Communication Across Boundaries and Disruptionsâ truly resonates with Crossrefâs truths; it takes a village! Crossref only works as long as the scholarly research community wants to work together globally, across all disciplines, for integrity and openness of the scientific record. The conversations were influenced by a genuinely diverse mix of librarians, researchers, open infrastructures, and service providers, and that mix shaped almost every interaction we had at the conference.
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 its July meeting, the Crossref board approved the use of Crossref surplus funds for a three-year project to accelerate the redesign of the Crossref system. Our plan is to use $1.6 million a year for three years (~USD $4.9M in total) from our surplus funds, which will help us set up a modern infrastructure consisting of separate services for the different functionalities that the Crossref system offers.
This section of our documentation is for Similarity Check account administrators who plan to access iThenticate 2.0 through their Manuscript Submission System (MTS).
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.
To set up your integration with your MTS, you need to create an API key by logging into iThenticate through the browser. You will then share this API key and the URL of your iThenticate 2.0 account with your MTS.
Please note: If you are sponsored by Biteca, please contact your sponsor who will help you with this.
Step One: Decide how many API scopes and API keys you need
Within iThenticate, you can set up different API Scopes, and within that, different API keys. Most members will just need one API Scope and one API key. However, some members may need more than one.
If you need to integrate with more than one Manuscript Tracking System (MTS), you will need a different API Scope for each MTS.
If you publish on behalf of societies or work with other organisations who want to keep their activities separate from each other, you will need a different API Scope and API key for each society.
If at some point in the future, you need to change your API key for an existing MTS integration, you must generate a new API key under the same scope that you originally used for this integration.
Step Two: Create your API Scope and API key(s)
Click on âIntegrationsâ in the menu.
This will bring you to the Integrations section. Click on the âGenerate API Scopeâ key.
You will then give your API Scope a name.
For example, this may be the name of a particular MTS, or of a particular society.
Under your new API Scope, you can then set up your first API key.
Once you add the key name, you will be able to click on the âCreate and viewâ button. The system will then generate your key.
Step three: Add your API key into your Manuscript Tracking System (MTS)
In order to integrate your new iThenticate 2.0 account and your Manuscript Tracking system(s), your MTS will require from you:
At least one API key
Your unique iThenticate URL containing your Crossref membership number using the following format: https://crossref-xxx.turnitin.com. (For example, if your Crossref Membership number is 1234, your URL will be: https://crossref-1234.turnitin.com. If you are not sure what your Crossref Membership number is, please ask us.
Follow the instructions below for the relevant MTS:
OJS
Follow the instructions found on PKP’s website. You’ll need to ensure that you’re on OJS version 3.3, 3.4, or 3.5. For instructions on how to upgrade your OJS instance, please visit PKP’s documentation here or here, depending on which version you’re currently running.
Editorial Manager
Enter your iThenticate API key(s) and your iThenticate 2.0 account URL into the iThenticate configuration page in Editorial Manager. There are instructions available from Aries Systems here.
eJournal Press
Email your API key(s) and your iThenticate 2.0 account URL to support@ejpress.com and the team at eJournal Press will set up the integration for you.
ScholarOne
If you are already using iThenticate with ScholarOne and are upgrading from iThenticate v1 to iThenticate 2.0, please email your API key(s) and your iThenticate 2.0 account URL to s1help@clarivate.com, and the team at ScholarOne will make the change for you. Please put âProduct Managementâ in the subject line of your email.
If you are a new subscriber to Similarity Check and you havenât used iThenticate before, you don’t need to email the team at ScholarOne. Just enter your iThenticate API key(s) and your iThenticate 2.0 account URL into the iThenticate configuration page in ScholarOne.
Scholastica
The team at Scholastica will set up the integration for you. Give them your API key(s) and your iThenticate 2.0 account URL by filling out this form.
The team at Scholastica will also set up any exclusions for you, so in the form they’ll ask you which sort of content you want to exclude from displaying as a match.
Page maintainer: Kathleen Luschek Last updated: 2022-July-18
