We’ve just added to our input schema the ability to include affiliation information using ROR identifiers. Members who register content using XML can now include ROR IDs, and we’ll add the capability to our manual content registration tools, participation dashboards, and metadata retrieval APIs in the near future. And we are inviting members to a Crossref/ROR webinar on 29th September at 3pm UTC.
The background We’ve been working on the Research Organization Registry (ROR) as a community initiative for the last few years.
We’re excited (and a little nervous) to launch a new research project designed to assess the effects of metadata on research communications. We’re expecting this effort to be a significant contribution to the existing research on the topic and we’re really looking forward to getting started. We’re also a little nervous because of course we don’t know what the conclusions will be (after all, if we did, we wouldn’t be starting this project).
UPDATE, 13 July 2021: The first stage of the cutover is complete, so requests to the public pool are now being served by the new REST API. We took a slightly different approach to performing the cutover, so the “Documentation” and “Temporary domain” sections below have been updated.
Our REST API is the primary interface for anybody to fetch the metadata of content registered with us, and we’ve been working hard on a more robust REST API service that’s about to go live.
22 June 2021, London, UK and Boston, MA, USA — The future of global open access publishing received a boost today with the signing of a Memorandum of Understanding between the Directory of Open Access Journals (DOAJ) and Crossref. The MOU formalizes an already strong partnership between the two organisations and furthers their shared pursuit of an open scholarly communications ecosystem that is inclusive of emerging publishing communities.
Both organisations aim to encourage the dissemination and use of scholarly research using open infrastructure, online technologies, regional and international networks, and community partners - all supporting local institutional capacity and sustainability around the world.
This section is for Similarity Check account administrators only. It explains how administrators need to set up the iThenticate account for their organizations before starting to add other users. It walks administrators through the parts of iThenticate that only account administrators can see, so if you aren’t an account administrator, you can ignore this section and skip to using your iThenticate account.
Not sure if you’re an account administrator? When you receive your email with your login details for iThenticate, log in and check if you can see the Manage Users tab. You can only see this tab if you’re an account administrator.
If you can’t see this tab, you’re not an account administrator, and you can skip ahead to using your iThenticate account for information on how to actually use the service to check your manuscripts.
Similarity Check administrator checklist - questions to answer before you begin
As a Similarity Check service user, your organization gets reduced-rate access to the iThenticate tool from Turnitin. You and your team are able to upload your manuscript submissions and receive a Similarity Report which shows areas of overlap between the manuscript and other published works.
As an administrator, you create and manage the users on your account, and you decide how your organization uses the iThenticate tool. You’ll find the system easier to use if you set it up correctly to start with. Do consider the following questions carefully and set up your account accordingly before inviting any users to your account:
Exclusions allow you to set iThenticate to ignore particular phrases, document sections, common words, and URLs, so that they are not flagged in your account’s Similarity Reports.
We recommend starting without any exclusions to avoid excluding anything important. Once your users are experienced enough to identify words and phrases that appear frequently but are not potentially problematic matches (and can therefore be ignored) in a Similarity Report, you can start carefully making use of this feature.
Set clear guidelines for your users so they understand the settings you have already applied, and can make skilful use of the options they can choose for themselves at report level.
4. Which iThenticate repositories will you want to check your manuscripts against?
iThenticate has a number of content repositories, grouped by the type of content they contain, including: Crossref, Crossref posted content, Internet, Publications, Your Indexed Documents.
You can choose which of iThenticate’s repositories you’re checking your manuscripts against. We recommend including them all to start with.
The person (whether an administrator or a user) who sets up a folder selects the repositories to check against for that folder. When the folder is shared, other users cannot adjust the repositories selected.
5. How will you budget for your document checking fees?
There’s a charge for each document checked, and you’ll receive an invoice in January each year for the documents you’ve checked in the previous year. If you’re a member of Crossref through a Sponsor, your Sponsor will receive this invoice.
As well as setting a Similarity Check document fees budget for your account each year, it’s useful to monitor document checking and see if you’re on track. You can monitor your usage in the reports section of the iThenticate platform. Ask yourself:
How many documents do you plan to check?
How often do you want to monitor usage? Set yourself a reminder to check your usage reports periodically.
How do you want to segment your report? You can report separately by groups of users, so think about what types of groups would make sense for your circumstances.
Learn more about how usage reports can help you monitor the number of documents checked on your account.
It’s a good idea to come back to these questions periodically, consider how your use of the tool is evolving, and make changes accordingly.