Documentation

Upgrade FAQs

Differences between iThenticate v1 and iThenticate 2.0

Q. What are the big differences between iThenticate v1 and 2.0 for all users?

As well as the faster, more user-friendly and responsive interface there are a few new features in iThenticate 2.0 which everyone can benefit from.

The Submitted Works repository (or Private Repository)

The Submitted Works Repository (or Private Repository) is a new feature in iThenticate 2.0 which is now available to Crossref members. 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.

  • Using iThenticate 2.0 in the browser? Find out more about the Submitted Works Repository.
  • Using iThenticate 2.0 through an integration with your MTS? This feature is currently only available to ScholarOne Manuscripts users. Find out more about the Submitted Works Repository.

Better identification of preprints

Identification of hidden text or suspicious character replacement

The new “red flag” feature signals the detection of hidden text such as text/quotation marks in white font, or suspicious character replacement. Find out more about the flags

No need to manually exclude bibliography or citations

In iThenticate 2.0, there is no need to choose to exclude the bibliography or citations in papers written in English, as Turnitin will automatically exclude these from your Similarity Report. For more information, please see Turnitin’s documentation here.

Please note, if you using an MTS integration and you find that the bibliography or citations are not being excluded, please reach out to your MTS, as they will need to adjust the settings on their end to ensure these exclusions are in place.

Q. Are there other differences between v1 and iThenticate 2.0 that those who integrate with an MTS will also notice?

Yes, there are some other big improvements to iThenticate for members who integrate iThenticate with their MTS.

View your Similarity Reports within your MTS

You can now both submit your manuscripts AND view your Similarity Report from within your MTS.

No folders if you integrate with an MTS

If you are using iThenticate through an integration then there is no need to set up any folders within your iThenticate account. Unlike in iThenticate v1, integrations will not send submissions to a folder which is accessible by logging into iThenticate through your browser. Submissions created by your MTS will only be accessible through your MTS.

No individual users in iThenticate if you integrate with an MTS

If you are using iThenticate through an integration with an MTS, then you do not need to set up any new users on your new iThenticate account. This is because all the submissions from your MTS will be made by the API key you’ve set, rather than individual users.

Q. Is AI detection available with iThenticate 2.0 through Similarity Check?

We’re not currently offering the iThenticate AI add-on to Crossref members as part of the Similarity Check service. This is based on feedback from our members who tested its functionality.

We do hope to offer the AI feature in the future though, and we’ll revisit the decision as the service develops. Keep an eye out for announcements on our community forum.

Upgrading from iThenticate v1 to iThenticate 2.0

Q. Can I move my existing users over from iThenticate v1 to iThenticate 2.0 when I upgrade?

Yes. By using Turnitin’s migration tool, you’ll be able to move your users from your iThenticate v1 account to your new iThenticate 2.0 account. This is a good time to review the users on your account and ensure that they are correct.

Q. When I move to iThenticate 2.0, will I immediately lose access to iThenticate v1?

Yes, but you will have a chance to test out iThenticate 2.0 through Turnitin’s migration process with a temporary Migration Setup Account. During this migration process, you will schedule the date for your migration, and you will continue to have access to your historical Similarity reports from your v1 account. For more information about the migration process, please see our documentation here and Turnitin’s documentation here.

Q. Can I still view my previous submissions from iThenticate v1 in iThenticate 2.0?

The submissions you made through iThenticate v1 will not be accessible directly through iThenticate 2.0. However, you will still be able to access your historical reports.

Q. Is there an extra charge for using iThenticate 2.0?

There is no charge to upgrade to iThenticate 2.0, and the costs to check your manuscripts are the same as in iThenticate v1. If you are using iThenticate 2.0 for some of your journals, but continue to use iThenticate v1 for some of your other journals, your volume discounts will apply across both instances.

However, it’s important to note that we can’t tell if you check the same document in both iThenticate v1 and iThenticate 2.0. If you do this, you will be charged twice.

Q. Can I upgrade from v1 to 2.0 if I use the OJS platform from PKP?

Yes, the OJS platform does have an integration with iThenticate 2.0. Please note, you’ll need to be on OJS version 3.3, 3.4, or 3.5 to use the integration. If you need to upgrade your OJS instance, please visit PKP’s website for documentation.

Problems after upgrading from v1 to iThenticate 2.0

Q. I can’t login to my new iThenticate 2.0 account

If you are the main Similarity Check contact on your member account, you should have received an email from Turnitin to set up your administrator password. Have you received the email and set up your new credentials yet? More information here.

If you have already received the email and set up your credentials and are still having problems, please check that you are going to the right place to access your iThenticate 2.0 account. Your old iThenticate v1 account and your new iThenticate 2.0 account are completely different, and you will get to them using a different URL. Some members accidentally try to login to their new 2.0 account on the URL for their old v1 account by mistake. To make sure that you are definitely going to the right place for 2.0, follow these instructions.

This is deliberate - being able to share links to the system was a security risk and this functionality has been deliberately removed by Turnitin. You can however download and email Similarity Reports to others.

Page owner: Amanda Bartell   |   Last updated 2022-July-15