Blog

Using the Crossref REST API. Part 7 (with CHORUS)

Continuing our blog series highlighting the uses of Crossref metadata, we talked to Sara Girard and Howard Ratner at CHORUS about the work they’re doing, and how they’re using our REST API as part of their workflow.

Changes to the 2018 membership agreement for better metadata distribution

We are making a change to section 9b of the standard Crossref membership agreement which will come into effect on January 1, 2018. This will not change how members register content, nor will it affect membership fees in any way. The new 2018 agreement is on our website, and the exact wording changes are highlighted below. The new membership agreement will automatically replace the previous version from January 1, 2018 and members will not need to sign a new agreement.

Using the Crossref REST API. Part 6 (with NLS)

Continuing our blog series highlighting the uses of Crossref metadata, we talked to Ulf Kronman, Bibliometric Analyst at the National Library of Sweden about the work they’re doing, and how they’re using our REST API as part of their workflow.

More metadata for machines-citations, relations, and preprints arrive in the REST API

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.

Using the Crossref REST API. Part 5 (with OpenCitations)

As part of our blog post series on the Crossref REST API, we talked to Silvio Peroni and David Shotton of OpenCitations (OC) about the work they’re doing, and how they’re using the Crossref REST API as part of their workflow.

Using the Crossref REST API. Part 4 (with CLA)

As a follow-up to our blog posts on the Crossref REST API we talked to the Copyright Licensing Agency (CLA) about the work they’re doing, and how they’re using the Crossref REST API as part of their workflow.

How do you deposit data citations?

An exemplary image

Please visit Crossref’s official Data & Software Citations Deposit Guide for deposit details.

Very carefully, one at a time? However you wish.

Last year, we introduced linking publication metadata to associated data and software when registering publisher content with Crossref Linking Publications to Data and Software. This blog post follows the “whats” and “whys” with the all-important “how(s)” for depositing data and software citations. We have made the process simple and fairly straightforward: publishers deposit data & software links by adding them directly into the standard metadata deposit via relation type and/or references. This is part of the **existing Content Registration ** process and requires no new workflows.

Included, registered, available: let the preprint linking commence.

We began accepting preprints as a new record type last month (in a category known as “posted content” in our XML schema). Over 1,000 records have already been registered in the first few weeks since we launched the service.

By extending our existing services to preprints, we want to help make sure that:

  • links to these publications persist over time
  • they are connected to the full history of the shared research
  • the citation record is clear and up-to-date.

Using the Crossref REST API. Part 3 (with SHARE)

As a follow-up to our blog posts on the Crossref REST API we talked to SHARE about the work they’re doing, and how they’re employing the Crossref metadata as a piece of the puzzle.  Cynthia Hudson-Vitale from SHARE explains in more detail…

Using the Crossref Metadata API. Part 2 (with PaperHive)

We first met the team from PaperHive at SSP in June, pointed them in the direction of the Crossref Metadata API and let things progress from there. That’s the nice thing about having an API - because it’s a common and easy way for developers to access and use metadata, it makes it possible to use with lots of diverse systems and services.

So how are things going? Alexander Naydenov, PaperHive’s Co-founder gives us an update on how they’re working with the Crossref metadata: