Welcome back to our series of case studies of research funders using the Grant Linking System. In this interview, I talk with CĂĄtia Laranjeira, PTCRIS Program Manager at FCCN|FCT, Portugalâs main public funding agency, about the agencyâs approach to metadata, persistent identifiers, Open Science and Open Infrastructure.
With a holistic approach to the management, production and access to information on science, FCCN|FCT’s decision to implement the Grant Linking System within their processes was not simply a technical upgrade, but a coordinated effort to continue building a strong culture of openness. With the mantra âregister once, reuse alwaysâ, FCCN|FCT efforts to embrace open funding metadata was only logical.
Repositories are home to a wide range of scholarly content; they often archive theses, dissertations, preprints, datasets, and other valuable outputs. These records are an important part of the research ecosystem and should be connected to the broader scholarly record. But to truly serve their purpose, repository records need to be connected to each other, to the broader research ecosystem, and to the people behind the research. Metadata is what makes that possible. Enhancing metadata is a way to tell a fuller, more accurate story of research. It helps surface relationships between works, people, funders, and institutions, and allows us as a community to build and use a more connected, more useful network of knowledge - what Crossref calls the âResearch Nexusâ.
The Crossref Grant Linking System (GLS) has been facilitating the registration, sharing and re-use of open funding metadata for six years now, and we have reached some important milestones recently! What started as an interest in identifying funders through the Open Funder Registry evolved to a more nuanced and comprehensive way to share and re-use open funding data systematically. Thatâs how, in collaboration with the funding community, the Crossref Grant Linking System was developed. Open funding metadata is fundamental for the transparency and integrity of the research endeavour, so we are happy to see them included in the Research Nexus.
This section of our documentation is for Similarity Check account administrators who plan to access iThenticate 2.0 through their Manuscript Submission System (MTS).
Not sure if you’re using iThenticate v1 or iThenticate 2.0? More here.
Not sure whether you’re an account administrator? Find out here.
To set up your integration with your MTS, you need to create an API key by logging into iThenticate through the browser. You will then share this API key and the URL of your iThenticate 2.0 account with your MTS.
Please note: If you are sponsored by Biteca, please contact your sponsor who will help you with this.
Step One: Decide how many API scopes and API keys you need
Within iThenticate, you can set up different API Scopes, and within that, different API keys. Most members will just need one API Scope and one API key. However, some members may need more than one.
If you need to integrate with more than one Manuscript Tracking System (MTS), you will need a different API Scope for each MTS.
If you publish on behalf of societies or work with other organisations who want to keep their activities separate from each other, you will need a different API Scope and API key for each society.
If at some point in the future, you need to change your API key for an existing MTS integration, you must generate a new API key under the same scope that you originally used for this integration.
Step Two: Create your API Scope and API key(s)
Click on âIntegrationsâ in the menu.
This will bring you to the Integrations section. Click on the âGenerate API Scopeâ key.
You will then give your API Scope a name.
For example, this may be the name of a particular MTS, or of a particular society.
Under your new API Scope, you can then set up your first API key.
Once you add the key name, you will be able to click on the âCreate and viewâ button. The system will then generate your key.
Step three: Add your API key into your Manuscript Tracking System (MTS)
In order to integrate your new iThenticate 2.0 account and your Manuscript Tracking system(s), your MTS will require from you:
At least one API key
Your unique iThenticate URL containing your Crossref membership number using the following format: https://crossref-xxx.turnitin.com. (For example, if your Crossref Membership number is 1234, your URL will be: https://crossref-1234.turnitin.com. If you are not sure what your Crossref Membership number is, please ask us.
Follow the instructions below for the relevant MTS:
OJS
Follow the instructions found on PKP’s website. You’ll need to ensure that you’re on OJS version 3.3, 3.4, or 3.5. For instructions on how to upgrade your OJS instance, please visit PKP’s documentation here or here, depending on which version you’re currently running.
Editorial Manager
Enter your iThenticate API key(s) and your iThenticate 2.0 account URL into the iThenticate configuration page in Editorial Manager. There are instructions available from Aries Systems here.
eJournal Press
Email your API key(s) and your iThenticate 2.0 account URL to support@ejpress.com and the team at eJournal Press will set up the integration for you.
ScholarOne
If you are already using iThenticate with ScholarOne and are upgrading from iThenticate v1 to iThenticate 2.0, please email your API key(s) and your iThenticate 2.0 account URL to s1help@clarivate.com, and the team at ScholarOne will make the change for you. Please put âProduct Managementâ in the subject line of your email.
If you are a new subscriber to Similarity Check and you havenât used iThenticate before, you don’t need to email the team at ScholarOne. Just enter your iThenticate API key(s) and your iThenticate 2.0 account URL into the iThenticate configuration page in ScholarOne.
Scholastica
The team at Scholastica will set up the integration for you. Give them your API key(s) and your iThenticate 2.0 account URL by filling out this form.
The team at Scholastica will also set up any exclusions for you, so in the form they’ll ask you which sort of content you want to exclude from displaying as a match.
Page maintainer: Kathleen Luschek Last updated: 2022-July-18