In 2020 we released our first public data file, something we’ve turned into an annual affair supporting our commitment to the Principles of Open Scholarly Infrastructure (POSI). We’ve just posted the 2022 file, which can now be downloaded via torrent like in years past.
We aim to publish these in the first quarter of each year, though as you may notice, we’re a little behind our intended schedule. The reason for this delay was that we wanted to make critical new metadata fields available, including resource URLs and titles with markup.
Unfortunately, Bryan Vickery has moved onto pastures new. I would like to thank him for his many contributions at Crossref and we all wish him well.
I’m now pleased to announce that Rachael Lammey will be Crossref’s new Director of Product starting on Monday, May 16th.
Rachael’s skills and experience are perfectly suited for this role. She has been at Crossref since 2012 and has deep knowledge and experience of all things Crossref: our mission; our members; our culture; and our services.
Since we announced last September the launch of a new version of iThenticate, a number of you have upgraded and become familiar with iThenticate v2 and its new and improved features which include:
A faster, more user-friendly and responsive interface A preprint exclusion filter, giving users the ability to identify content on preprint servers more easily A new “red flag” feature that signals the detection of hidden text such as text/quotation marks in white font, or suspicious character replacement A private repository available for browser users, allowing them to compare against their previous submissions to identify duplicate submissions within your organisation A content portal, helping users check how much of their own published content has been successfully indexed, self-diagnose and fix the content that has failed to be indexed in iThenticate.
A re-cap We kicked off our Ambassador Program in 2018 after consultation with our members, who told us they wanted greater support and representation in their local regions, time zones, and languages.
We also recognized that our membership has grown and changed dramatically over recent years and that it is likely to continue to do so. We now have over 16,000 members across 140 countries. As we work to understand what’s to come and ensure that we are meeting the needs of such an expansive community, having trusted local contacts we can work closely with is key to ensuring we are more proactive in engaging with new audiences and supporting existing members.
It’s really important for consistency and usability that all members follow these guidelines. We rarely have to change them and usually only do so for very good reasons. Please note that this is for display of Crossref DOIs, not anyone else’s DOIs, as not all DOIs are made equal.
The goals of the guidelines are to:
Make it as easy as possible for users without technical knowledge to cut and paste or click to share Crossref DOIs (for example, using right-click to copy a URL).
Get users to recognize a Crossref DOI as both a persistent link as well as a persistent identifier, even if they don’t know what a DOI is.
Enable points 1 and 2 above by having all Crossref members display DOIs in a consistent way.
Enable robots and crawlers to recognize Crossref DOIs as URLs.
When linking to a research work, use its DOI rather than its URL. If the URL changes, the publisher will update the metadata in Crossref with the new URL, so that the DOI will always take you to the correct location of the work.
How to display a Crossref DOI
When displaying DOIs, it’s important to follow these display guidelines. Crossref DOIs should:
These guidelines introduce two important changes that differ from the previous guidelines:
we have dropped the dx from the domain name portion of DOI links
we recommend you use the secure HTTPS rather than HTTP
Note this change is backwards compatible, so DOIs such as http://dx.doi.org/ and http://doi.org/ which conform to older guidelines will continue to work indefinitely.
Where to apply the display guidelines
Crossref DOIs should be displayed as the full URL link wherever the bibliographic information about the content is displayed.
An obligation of membership is that Crossref DOIs must be displayed on members’ landing pages. We recommend that Crossref DOIs also be displayed or distributed in the following contexts:
Tables of contents
Full-text HTML and PDF articles, and other scholarly documents
Citation downloads to reference management systems
Metadata feeds to third parties
“How to Cite This” instructions on content pages
Social network links
Anywhere users are directed to a permanent, stable, or persistent link to the content.
Crossref members should not use proprietary, internal, or other non-DOI URLs in citation downloads, metadata feeds to third parties, nor in instructions to researchers on how to cite a document.
Crossref DOIs in reference lists and bibliographies
Linking references in journal articles using Crossref DOIs is a condition of membership. This means including the DOI for each item in your reference list. We strongly encourage members to link references for other content types too. Because there are space constraints even in online references lists, Crossref DOIs can be displayed in several ways, depending on the publisher’s preference and publication style. We recommend the following options:
use the Crossref DOI URL as the permanent link. Example: Soleimani N, Mohabati Mobarez A, Farhangi B. Cloning, expression and purification flagellar sheath adhesion of Helicobacter pylori in Escherichia coli host as a vaccination target. Clin Exp Vaccine Res. 2016 Jan;5(1):19-25. https://doi.org/10.7774/cevr.2016.5.1.19
display the text Crossref with a permanent DOI link behind the text. Example: Galli, S.J., and M. Tsai. 2010. Mast cells in allergy and infection: versatile effector and regulatory cells in innate and adaptive immunity. Eur. J. Immunol. 40:1843–1851. Crossref.
The International DOI Foundation created the ShortDOI service as an open system that creates shortcuts to DOIs. DOIs can be long, so this service aimed to to the same thing as URL shortening services. For example, for the DOI https://doi.org/10.7774/cevr.2016.5.1.1, the short form is https://doi.org/bwfc. Only one ShortDOI is created for each DOI, and the ShortDOI returns exactly the same results as the DOI. ShortDOIs are not widely used and are not really actual DOIs themselves, which is confusing. We recommend simply creating shorter DOIs in the first place. Learn more about constructing your DOIs.
Frequently Asked Questions (FAQs) about the March 2017 changes
Do we need to change how DOIs are displayed in already-published content and existing PDFs?
No - you can make the change for new content going forward and do not need to update existing PDF files. You can update existing content if you want to, but this is optional. The current form, for DOI links using http://dx.doi.org, will continue to work as long as Crossref and the DOI system exist.
Can we make the display changes now or do we need to wait?
These guidelines are now in effect. We set the date as March 2017, after giving our members six months’ notice to make the changes.
Why does the DOI have to be displayed as a link on the page that the DOI links to?
Some members have reported resistance from colleagues to displaying the Crossref DOI on the landing page as a link (they say the DOI link in that location appears superfluous as it appears to link to itself). The Crossref DOI must be displayed as a link, because it is both an identifier and a persistent link. It is easier for users when members display the DOI as a full link as they can copy it easily. Also, many users don’t know what a DOI is, but they know what a link is. We want to encourage the DOI to be used as a persistent link, and to be shared and used in other applications (such as reference management tools). A fully linked DOI enables this, wherever it appears.
Do we need to redeposit our metadata to update the DOI display?
No - there is no need to redeposit metadata. These guidelines cover how you display DOIs on your website, not how to register them with us.
Why not use doi: or DOI:?
When Crossref was founded in 2000, we recommended that DOIs be displayed in the format doi:10.NNNN/doisuffix and many members still use doi:[space][doinumber], DOI: [space][doinumber], or DOI[space][doinumber]. At the time that the DOI system was launched in the late 1990s it was thought that doi: would become native to browsers and automatically resolve DOIs, like http:. This did not happen, and so doc:/DOI: is not a valid way of displaying or linking DOIs.
Advantages to changing the display to a resolvable URL (even on the page the DOI itself resolves to) include:
A DOI is both a link and an identifier. Users will more easily recognize Crossref DOIs as an actionable link, regardless of whether they know about DOIs
Users who do not know how to right-click on the link and choose Copy link will still be able to easily copy the DOI URL
Machines and programs (such as bots) will recognize the DOI as a link, thereby increasing discoverability and usage.
What about reference formats in style guides (such as APA, Chicago) that use doi: [doinumber]?
A number of style guides recommend including a DOI in the reference as an unlinked string. We are contacting the main style guides to request that they update their recommendations for DOIs to use the full-URL form.
Why not use dx as in http://dx.doi.org/?
Originally the dx separated the DOI resolver from the International DOI Foundation (IDF) website but this changed a few years ago and the IDF recommends http://doi.org as the preferred form for the domain name in DOI URLs.
Why should we use HTTPS?
Providing the central linking infrastructure for scholarly publishing is something we take seriously. Because we form the connections between publisher content all over the web, it’s important that we do our bit to enable secure browsing from start to finish. In addition, HTTPS is now a ranking signal for Google, which gives sites using HTTPS a small ranking boost.
The process of enabling HTTPS on publisher sites will be a long one, and given the number of members we have, it may take a while before everyone’s made the transition. But by using HTTPS we are future-proofing scholarly linking on the web.
Some years ago we started the process of making our new services available exclusively over HTTPS. The Crossref Metadata API is HTTPS enabled, and Crossmark and our Assets CDN use HTTPS exclusively. In 2015 we collaborated with Wikipedia to make all of their DOI links HTTPS. We hope that we’ll start to see more of the scholarly publishing industry doing the same.
Page owner: Ginny Hendricks | Last updated 2021-April-21