In the scholarly communications environment, the evolution of a journal article can be traced by the relationships it has with its preprints. Those preprint–journal article relationships are an important component of the research nexus. Some of those relationships are provided by Crossref members (including publishers, universities, research groups, funders, etc.) when they deposit metadata with Crossref, but we know that a significant number of them are missing. To fill this gap, we developed a new automated strategy for discovering relationships between preprints and journal articles and applied it to all the preprints in the Crossref database. We made the resulting dataset, containing both publisher-asserted and automatically discovered relationships, publicly available for anyone to analyse.
The second half of 2023 brought with itself a couple of big life changes for me: not only did I move to the Netherlands from India, I also started a new and exciting job at Crossref as the newest Community Engagement Manager. In this role, I am a part of the Community Engagement and Communications team, and my key responsibility is to engage with the global community of scholarly editors, publishers, and editorial organisations to develop sustained programs that help editors to leverage rich metadata.
STM, DataCite, and Crossref are pleased to announce an updated joint statement on research data.
In 2012, DataCite and STM drafted an initial joint statement on the linkability and citability of research data. With nearly 10 million data citations tracked, thousands of repositories adopting data citation best practices, thousands of journals adopting data policies, data availability statements and establishing persistent links between articles and datasets, and the introduction of data policies by an increasing number of funders, there has been significant progress since.
Have you attended any of our annual meeting sessions this year? Ah, yes – there were many in this conference-style event. I, as many of my colleagues, attended them all because it is so great to connect with our global community, and hear your thoughts on the developments at Crossref, and the stories you share.
Let me offer some highlights from the event and a reflection on some emergent themes of the day.
Crossref allows citation linking using Digital Object Identifiers (DOIs) between research produced by different organizations (without the need for individual agreements between them). This ensures that citation links are persistent - that they work over long periods of time. However, there is no purely technical solution to the problem of broken links on the web; Crossref members have to keep these links updated, along with rich metadata that everyone in the scholarly ecosystem relies on.
At Crossref, every metadata record that our members register for their content needs to have a unique DOI attached to it, both as a container for that record and as a locator for others to use. A DOI does not signify any value or accuracy of the thing it locates; the value lies in the record’s metadata which gives context about the object (such as contributors, funding bodies, abstract/summary) and enables connections with other entities (such as people (e.g. ORCID) or organizations (e.g. ROR)).
DOIs include 3 parts:
Of these three parts of the DOI, members (or their service providers) create the last part, the suffix. Because DOIs must be unique and persistent, members need a reasonable way to create and manage their suffixes, which should be opaque.
Here, we share the rules, guidelines and some examples to help you decide how to approach your suffixes. You can also go straight to our suffix generator.
Suffixes are case insensitive, so 10.1006/abc is the same in the system as 10.1006/ABC. Note that using lowercase is better for accessibility.
Guidelines for creating a DOI suffix
In part because there are few rules, it can be helpful to have some guidance in how to approach suffixes. This advice applies to DOIs at all levels, whether at journal or book level (a title-level DOI), or volume, issue, article, or chapter level.
The most important part of creating your DOIs is to understand that because DOIs are unique, persistent and ‘dumb’, once they are created, they will always work. There is never a need to delete or update existing DOIs.
Best practices for DOI suffixes:
Suffixes are best when they include short strings that are easily displayed and typed but are ‘dumb’ - meaning, the suffixes contains no readable information, including metadata.
Keep suffixes short. This makes them easier to read and to re-type. Remember, DOIs will appear online and in print.
Best practice DOI example:10.3390/s18020479 This example appears to be opaque because it includes no obvious information.
Avoid the following in DOI suffixes:
The function of suffixes is technical in nature so they are most problematic when they are treated as information to be read, interpreted and/or predicted. Remember, DOIs are persistent and not subject to correction or deletion.
While it may be tempting, using a pattern, such as a sequence, can cause problems. Services and tools that use DOIs may, for example, try to predict future DOIs that are not registered and may never be (more on opaque suffixes below).
Don’t include information like journal title (or initials), page number or date. This kind of information should be included in the metadata but can cause problems when included in suffixes for 2 main reasons:
Information in the suffix that conflicts with information in the metadata is confusing.
Information like journal title (or initials) may change or be found to be incorrect, as with dates, but DOIs are persistent, cannot be deleted and are not subject to correction. See more on opaque suffixes below.
Example problematic DOI suffix:10.5555/2014-04-01 This example is not opaque because it includes a date, which should be included in the metadata instead of in the suffix.
Proceed with caution in DOI suffixes:
Determining how to create suffixes and manage the over time can be a challenge. We recognize that some systems have requirements that don’t follow this advice and that human readability is helpful in managing DOIs.
If you must use a suffix with meaning, internal system identifiers can work, with careful management. Because things like ISBNs are themselves metadata, we don’t recommend using them in suffixes.
Just remember that while you and readers may recognize an ISBN, for example, the DOI system itself doesn’t and DOIs are not subject to correction or deletion.
No matter your approach, it’s worth taking some time to understand the emphasis on opaque suffixes.
Once a DOI has been registered with us, it should always be used for the same content. Even if the content moves to a new website or a new owner, the same DOI should continue to be used. Though the DOI never changes, its associated metadata is kept up-to-date by the relevant Crossref member.
What if your content already has a DOI?
Sometimes members may acquire a journal that already has DOIs registered for some articles. It’s important to keep and continue to use the DOIs that have already been registered and not change them - DOIs need to be persistent.
It doesn’t matter if the prefix on the existing DOI is different from the prefix belonging to the acquiring member. As content can move between members, the owner of a DOI is not necessarily the same as the owner of the prefix. Read more about transferring responsibility for DOIs.
The importance of opaque identifiers
What are opaque suffixes & why they are important
Suffixes are ‘dumb numbers.’ They are essentially meaningless on their own and meant to be that way–opaque. One good reason for that is because when something is meaningless, it doesn’t need to be corrected.
DOIs should not include information that can be understood, interpreted or predicted, especially information that may change. Page numbers and dates are examples of information that shouldn’t be included in suffixes. It is particularly problematic if the suffix includes information that conflicts with the metadata associated with the DOI.
We’ve referred to creating ‘suffix patterns’ in the past but information that includes or implies a pattern is also problematic. A sequence of numbers, for example, lends itself to the assumption that future DOIs can be predicted.
Scraping for DOIs - or what appear to be DOIs–is common, as is the likelihood that what is–or appears to be–a pattern will be treated as such. Just as the timing of DOI registration is important, in order to avoid unregistered DOIs, their construction is critical to avoiding interpretation.
More information on creating DOIs
Here are a few other resources that discuss creating DOIs and the importance of using opaque suffixes.