We were delighted to engage with over 200 community members in our latest Community update calls. We aimed to present a diverse selection of highlights on our progress and discuss your questions about participating in the Research Nexus. For those who didn’t get a chance to join us, I’ll briefly summarise the content of the sessions here and I invite you to join the conversations on the Community Forum.
You can take a look at the slides here and the recordings of the calls are available here.
We have some exciting news for fans of big batches of metadata: this year’s public data file is now available. Like in years past, we’ve wrapped up all of our metadata records into a single download for those who want to get started using all Crossref metadata records.
We’ve once again made this year’s public data file available via Academic Torrents, and in response to some feedback we’ve received from public data file users, we’ve taken a few additional steps to make accessing this 185 gb file a little easier.
In 2022, we flagged up some changes to Similarity Check, which were taking place in v2 of Turnitin’s iThenticate tool used by members participating in the service. We noted that further enhancements were planned, and want to highlight some changes that are coming very soon. These changes will affect functionality that is used by account administrators, and doesn’t affect the Similarity Reports themselves.
From Wednesday 3 May 2023, administrators of iThenticate v2 accounts will notice some changes to the interface and improvements to the Users, Groups, Integrations, Statistics and Paper Lookup sections.
We’ve been spending some time speaking to the community about our role in research integrity, and particularly the integrity of the scholarly record. In this blog, we’ll be sharing what we’ve discovered, and what we’ve been up to in this area.
We’ve discussed in our previous posts in the “Integrity of the Scholarly Record (ISR)” series that the infrastructure Crossref builds and operates (together with our partners and integrators) captures and preserves the scholarly record, making it openly available for humans and machines through metadata and relationships about all research activity.
If you plan to set up the plugin to register content with Crossref automatically, you’ll need to add your Crossref account credentials into the username and password field in the plugin.
Depositor name - Name of the organization registering the DOIs (note: this field is not authenticated with Crossref)
Depositor email - email address of the individual responsible for registering content with Crossref (note: this field is not authenticated with Crossref)
Username - the Crossref username that will be passed to us to authenticate your submission(s). This might also be an email address - more on role versus user credentials below.
Password - the password associated with your Crossref credentials
Note: if the combination of username and password is incorrect, OJS will return a 401 unauthorized status code error at the time of registration. This error indicates that the username and password are incorrectly entered. That is, they do not match the username and/or password set with Crossref.
If you are using organization-wide, shared role credentials, you can simply add in your shared username and password.
If you are using personal user credentials that are unique to you, you’ll need to add your email address and your role into the username field, and your personal password into the password field. Here’s an example of what this will look like:
In addition to the Crossref XML plugin for OJS, there are also other important plugins that can be enabled in OJS to enrich your metadata records:
Reference linking and deposit plugin - As of OJS 3.1.2, it is possible to enable a reference linking plugin for Crossref. The plugin will use the Crossref API to check against plain text references and locate possible DOIs for articles. The plugin will also allow the display of reference lists on the article landing page in OJS and deposit them as part of your metadata deposit. Linking references is a requirement of Crossref membership.
Crossmark plugin - OJS 3.2 includes support for Crossmark, which gives readers quick and easy access to the current status of an item of content, including any corrections, retractions, or updates to that record.
Similarity Check plugin - if you are using OJS 3.1.2 or above, you are able to use the Similarity Check plugin. This will enable you to automatically send manuscripts to your iThenticate account to check their similarity to already published content. You will need to be subscribed to Crossref’s Similarity Check service for this to work.
Getting help with OJS plugins
The team at Crossref didn’t create these plugins - they were either created by the team at PKP, or by third party developers. Because of this, we aren’t able to give in-depth help or troubleshooting on problems with these plugins.
If you need more help, you can learn more at PKP’s Crossref OJS Manual, plus there’s a very active PKP Community Forum which has more information on how to modify your OJS instance to submit metadata and register DOIs with Crossref.