Kirsty Meddings – 2017 September 11
Over the past few months we have been adding to the metadata and functionality of our REST API, Crossref’s public machine interface for the metadata of all 90 million+ registered content items. Much of the work focused on a review and upgrade of the API’s code and architecture in order to better support its rapidly growing usage. But we have also extended the types of metadata that the API can deliver.
One of the biggest changes is that references are now available if the publisher has made them public (a simple email instruction to us). Currently 45% of all publications with deposited references are now accessible. For example:
We recently announced that we would be accepting preprints, and the metadata for 15,000 preprints registered to date is now in the API, labelled as
posted-content. Over 4,000 have been subsequently published in a journal, and the Crossref metadata now links these preprints to their respective articles (and vice versa). For example this article in Biorxiv has since been published in a journal, and this relationship is recorded in its metadata as
Cited-by counts - the number of times each work has been referenced by other content registered with us. Look for
is-referenced-by-count within a record.
This article from 1953 about a fairly notable discovery has been cited 4832 times, but the two most cited articles both have over 100,000 citations and thousands have been cited more than Watson and Crick.
Abstracts for over 1 million works.
Similarity Check URLs–the ones that Turnitin crawl to add content to the database–are now showing so that participating publishers can check that they are including them in their metadata deposits.
Subject categories have been added for an additional 7000 journal titles, taking the total number of classified titles to ~45,000.
Are you already using our Metadata APIs for your system or project? We’re always keen to hear new use cases and happy to answer any questions.
You may need to install a JSON viewer extension in your browser to render API queries in a human-friendly way.
2018 January 31
2018 January 30
2018 January 23