The Crossref Nominating Committee invites expressions of interest to join the Board of Directors of Crossref for the term starting in January 2026. The committee will gather responses from those interested and create the slate of candidates that our membership will vote on in an election in September.
Expressions of interest will be due Monday, June 9th, 2025
In its March 2025 meeting, the Crossref board unanimously voted to update both the Crossref bylaws and the Crossref membership terms to:
Provide more clarity and alignment between our bylaws and membership terms, where they had become out of sync over the years.
Reflect previous board motions and bring both documents up-to-date with current processes for suspending and revoking membership, and reviewing those decisions.
Work towards being more explicit about what “Member Practices” should look like in terms of preserving the integrity of the scholarly record.
Marking our 25th anniversary, we launch the Crossref Metadata Awards to emphasise our community’s role in stewarding and enriching the scholarly record.
We are pleased to recognise Noyam Publishers, GigaScience Press, eLife, American Society for Microbiology, and Universidad La Salle Arequipa Perú with the Crossref Metadata Excellence Awards, and Instituto Geologico y Minero de España wins the Crossref Metadata Enrichment Award. These inaugural awards highlight the leadership of members who show dedication to the best metadata practices.
We’ve been accelerating our metadata development efforts and recently released version 5.4 of our metadata schema, and are planning to release version 5.5 (including support for multiple contributor roles and the CRediT taxonomy) this summer. We will also extend our grants schema based on the Funders Advisory Group work, and make progress on other changes as set out on our new metadata development roadmap.
As we work towards the vision of the rich and reusable open network of relationships connecting research organizations, people, things, and actions, dubbed the Research Nexus, our schemas need to change to accommodate the evolving landscape of research processes and communications.
This section of our documentation is for Similarity Check account administrators who are integrating iThenticate v2 with their Manuscript Submission System (MTS).
Not sure if you’re using iThenticate v1 or iThenticate v2? More here.
Not sure whether you’re an account administrator? Find out here.
To set up your integration, 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 v2 account with your MTS.
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 organizations 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 v2 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 v2 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 v2 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 v2, please email your API key(s) and your iThenticate v2 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 v2 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 v2 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 owner: Kathleen Luschek | Last updated 2022-July-18