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.
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