One of the challenges that we face in Labs and Research at Crossref is that, as we prototype various tools, we need the community to be able to test them. Often, this involves asking for deposit to a different endpoint or changing the way that a platform works to incorporate a prototype.
The problem is that our community is hugely varied in its technical capacity and level of ability when it comes to modifying their platform.
When each line of code is written it is surrounded by a sea of context: who in the community this is for, what problem we’re trying to solve, what technical assumptions we’re making, what we already tried but didn’t work, how much coffee we’ve had today. All of these have an effect on the software we write.
By the time the next person looks at that code, some of that context will have evaporated.
It turns out that one of the things that is really difficult at Crossref is checking whether a set of Crossref credentials has permission to act on a specific DOI prefix. This is the result of many legacy systems storing various mappings in various different software components, from our Content System through to our CRM. To this end, I wrote a basic application, credcheck, that will allow you to test a Crossref credential against an API.
Subject classifications have been available via the REST API for many years but have not been complete or reliable from the start and will soon be deprecated. dfdfd
The subject metadata element was born out of a Labs experiment intended to enrich the metadata returned via Crossref Metadata Search with All Subject Journal Classification codes from Scopus. This feature was developed when the REST API was still fairly new, and we now recognize that the initial implementation worked its way into the service prematurely.
Cited-by supports members who display citations, enabling the community to discover connections between research outputs.
Scholars use citations to critique and build on existing research, acknowledging the contributions of others. Members can include references in their metadata deposits which Crossref uses to create links between works that cite each other. The number of citations each work receives is visible to anyone through our public APIs. Through our Cited-by service, members who deposit reference metadata can retrieve everything they need to display citations on their website.
Members who use this service are helping readers to:
easily navigate to related research,
see how the work has been received by the wider community,
explore how ideas evolve over time by highlighting connections between works.
Watch the introductory Cited-by animation in your language:
Cited-by begins with references deposited as part of the metadata records for your content. Learn more about depositing references.
A member registers content for a work, the citing paper. This metadata deposit includes the reference list. Crossref automatically checks these references for matches to other registered content. If this is successful, a relationship between the two works is created. Crossref logs these relationships and updates the citation counts for each work. You can retrieve citation counts through our public APIs.
Members can use the Cited-by service to retrieve the full list of citing works, along with all the bibliographic details needed to display them on their website.
Note that citations from Crossref may differ from those provided by other services because we only look for links between Crossref-registered works and don’t share the same method to find matches.
Obligations and fees for Cited-by
Participation in Cited-by is optional, but encouraged.
There is no charge for Cited-by.
Depositing references is not a requirement, but strongly encouraged if you are using Cited-by.
Best practice for Cited-by
Because citations can happen at any time, Cited-by links must be kept up-to-date. Members should either check regularly for new citations or (if performing XML queries) set the alert attribute to true. This means the search will be saved in the system and you’ll get an alert when there is a new match.
Depositing your own references is strongly encouraged if you use Cited-by. If you don’t, the citations you retrieve will not include those from your own works. This is likely to lead to under-reporting of citations counts by at least 20% and you are missing the opportunity to point readers to other similar works on your platform.
Also in the metadata is the number of citations a work has received, under the tag "is-referenced-by-count".
To retrieve the full list of citations you need be a member using Cited-by. While anyone can use an API query to see the number of citations a work has received, members can retrieve a full list of citing DOIs and callback notifications informing them when one of their works has been cited. Details of the citing works can be displayed on your website alongside the article.
In 2023 we are developing a new API endpoint that will make citations more accessible to the community, for a preview see this announcement.
Page owner: Martyn Rittman | Last updated 2021-February-09