In our previous blog post in this series, we explained why no metadata matching strategy can return perfect results. Thankfully, however, this does not mean that it’s impossible to know anything about the quality of matching. Indeed, we can (and should!) measure how close (or far) we are from achieving perfection with our matching. Read on to learn how this can be done!
How about we start with a quiz? Imagine a database of scholarly metadata that needs to be enriched with identifiers, such as ORCIDs or ROR IDs.
We’re in year two of the Resourcing Crossref for Future Sustainability (RCFS) research. This report provides an update on progress to date, specifically on research we’ve conducted to better understand the impact of our fees and possible changes.
Crossref is in a good financial position with our current fees, which haven’t increased in 20 years. This project is seeking to future-proof our fees by:
Making fees more equitable Simplifying our complex fee schedule Rebalancing revenue sources In order to review all aspects of our fees, we’ve planned five projects to look into specific aspects of our current fees that may need to change to achieve the goals above.
On behalf of the Nominating Committee, I’m pleased to share the slate of candidates for the 2024 board election.
Each year we do an open call for board interest. This year, the Nominating Committee received 53 submissions from members worldwide to fill four open board seats.
We maintain a balanced board of 8 large member seats and 8 small member seats. Size is determined based on the organization’s membership tier (small members fall in the $0-$1,650 tiers and large members in the $3,900 - $50,000 tiers).
In our previous instalments of the blog series about matching (see part 1 and part 2), we explained what metadata matching is, why it is important and described its basic terminology. In this entry, we will discuss a few common beliefs about metadata matching that are often encountered when interacting with users, developers, integrators, and other stakeholders. Spoiler alert: we are calling them myths because these beliefs are not true! Read on to learn why.
The Similarity Check service gives Crossref members reduced rate access to the iThenticate tool from Turnitin, and there’s now a new version of iThenticate available for some subscribers. iThenticate v2 has lots of new and improved features, including:
The ability to identify content on preprint servers more easily
A “red flag” feature that signals the detection of hidden text such as text/quotation marks in white font, or suspicious character replacement
A faster, more user-friendly and responsive Similarity Report interface
For those members who integrate their iThenticate account with a Manuscript Tracking Service (MTS) there are even more benefits - you can now submit your manuscripts and view your Similarity Report from within the MTS, and you can also manage your exclusions from within your MTS too. There are also some important changes in how you manage users.
You can find out more about the benefits of iThenticate v2 on our blog.
Who can upgrade from iThenticate v1 to iThenticate v2?
Most existing subscribers to Similarity Check are currently using iThenticate v1, and over the next year or so we’ll be inviting these members to upgrade to iThenticate v2. Not everyone can upgrade immediately. This is because many members integrate their iThenticate account with their Manuscript Tracking Service (MTS), and not all the MTSs are able to integrate with iThenticate v2 just yet.
An upgrade is currently available to members of Crossref:
Using iThenticate through the browser
Integrating iThenticate with eJournal Press
Integrating iThenticate with ScholarOne Manuscripts
Integrating iThenticate with Scholastica Peer Review
Integrating iThenticate with Editorial Manager
We’ll be letting members know as the other Manuscript Tracking Systems are able to integrate with iThenticate v2. Brand new subscribers who fall into the categories above will be set up directly on iThenticate v2.
Not sure if you’re currently using iThenticate v1 or iThenticate v2? Here’s how to check.
The upgrade process
When you are able to upgrade from iThenticate v1 to iThenticate v2, we will contact the Similarity Check editorial contact on your account and ask you to complete a form. We will then check that you are still eligible for Similarity Check. This means that we will check that you are still providing Similarity Check URLs for at least 90% of the content you have registered with Crossref, and that the team at Turnitin can continue to index this content into the iThenticate database.
Once this is done, the team at Turnitin will send an email to the Similarity Check editorial contact on your account, so they can set up administrator credentials on your new iThenticate v2 account. The email will look like this:
Click on the blue ‘Set up my account’ button at the bottom of the email. This will bring you to a page which looks something like this:
Fill out your username and password, and don’t forget to tick to agree to the terms and conditions. You will then arrive at your new iThenticate v2 account.
Once you have administrator access to your new iThenticate v2 account, you can follow the instructions for getting set up. There are a different set of instructions depending on whether:
You will be using iThenticate directly in the browser - more here.
You will be integrating iThenticate with your Manuscript Tracking System (MTS) - more here.
If you have any follow up questions after your upgrade, do read our upgrade FAQs.
Page owner: Amanda Bartell | Last updated 2022-July-15