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.
We’ve just released an update to our participation report, which provides a view for our members into how they are each working towards best practices in open metadata. Prompted by some of the signatories and organizers of the Barcelona Declaration, which Crossref supports, and with the help of our friends at CWTS Leiden, we have fast-tracked the work to include an updated set of metadata best practices in participation reports for our members.
It’s been a while, here’s a metadata update and request for feedback In Spring 2023 we sent out a survey to our community with a goal of assessing what our priorities for metadata development should be - what projects are our community ready to support? Where is the greatest need? What are the roadblocks?
The intention was to help prioritize our metadata development work. There’s a lot we want to do, a lot our community needs from us, but we really want to make sure we’re focusing on the projects that will have the most immediate impact for now.
In the first half of this year we’ve been talking to our community about post-publication changes and Crossmark. When a piece of research is published it isn’t the end of the journey—it is read, reused, and sometimes modified. That’s why we run Crossmark, as a way to provide notifications of important changes to research made after publication. Readers can see if the research they are looking at has updates by clicking the Crossmark logo.
Setting up your iThenticate v1 account (admins only)
Documentation Menu
Setting up your iThenticate v1 account (admins only)
This section is for Similarity Check account administrators using iThenticate v1. You need to follow the steps in this section before you start to set up your users and share the account with your colleagues.
If you are using iThenticate v2 rather than iThenticate v1, there are separate instructions for you.
Not sure if you’re using iThenticate v1 or iThenticate v2? More here.
Your personal administrator account in iThenticate v1
Once Turnitin has enabled iThenticate v1 for your organization, the main editorial contact provided on your application form will become the iThenticate account administrator. As an administrator, you create and manage the users on your account, and you decide how your organization uses the iThenticate tool.
To start with, you need to login to iThenticate and set your password.
Log in to your administrator account (v1)
Start from the link in the invitation email from noreply@ithenticate.com with the subject line “Account Created” and click Login
Enter your username and single-use password
Click to agree to the terms of the end-user license agreement. These terms govern your personal use of the service. They’re separate from the central Similarity Check service agreement that your organization has agreed to.
You will be prompted to choose a new password
Click ​Change Password​ to save.
How do you know if you’re an account administrator?
Once you’ve logged in, you will only be able to see the Manage Users tab if you’re an account administrator.
So if you can’t see Manage Users or Users, you’re not an account administrator, and you can skip ahead to the user instructions for iThenticate v1.
Updating your personal email address or password
Changing your email address or updating your password is the same for admins and other users. There’s more information in the user instructions for iThenticate v1.
Page owner: Kathleen Luschek | Last updated 2022-July-15
