Thank you to everyone who responded with feedback on the Op Cit proposal. This post clarifies, defends, and amends the original proposal in light of the responses that have been sent. We have endeavoured to respond to every point that was raised, either here or in the document comments themselves.
We strongly prefer for this to be developed in collaboration with CLOCKSS, LOCKSS, and/or Portico, i.e. through established preservation services that already have existing arrangements in place, are properly funded, and understand the problem space.
I’m pleased to share the 2023 board election slate. Crossref’s Nominating Committee received 87 submissions from members worldwide to fill seven open board seats.
We maintain a balance of eight large member seats and eight small member seats. A member’s size is determined based on the membership fee tier they pay. We look at how our total revenue is generated across the membership tiers and split it down the middle. Like last year, about half of our revenue came from members in the tiers $0 - $1,650, and the other half came from members in tiers $3,900 - $50,000.
https://doi.org/10.13003/c23rw1d9
Crossref acquires Retraction Watch data and opens it for the scientific community Agreement to combine and publicly distribute data about tens of thousands of retracted research papers, and grow the service together
12th September 2023 —– The Center for Scientific Integrity, the organisation behind the Retraction Watch blog and database, and Crossref, the global infrastructure underpinning research communications, both not-for-profits, announced today that the Retraction Watch database has been acquired by Crossref and made a public resource.
Today, we are announcing a long-term plan to deprecate the Open Funder Registry. For some time, we have understood that there is significant overlap between the Funder Registry and the Research Organization Registry (ROR), and funders and publishers have been asking us whether they should use Funder IDs or ROR IDs to identify funders. It has therefore become clear that merging the two registries will make workflows more efficient and less confusing for all concerned.
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
