DOI content negotiation is one of the oldest DataCite services, launched in 2012. Content negotiation makes it easy to fetch DataCite metadata in other metadata formats, for example BibTeX or schema.org, or as formatted citation in one of more than 5,000 citation styles. For example:
curl -LH "Accept: application/x-bibtex" https://doi.org/10.5438/0000-0C2G
In 2017 we updated the service, both adding new content types (e.g. schema.org), and improving the support for existing content types (Fenner, 2017).
In 2018 we launched a new version of the REST API (Dasler, 2018) that complements content negotiation: you can now submit metadata in most of the metadata formats supported by content negotiation to register a DOI.
With this blog post we want to announce an important upcoming change to DataCite DOI content negotiation that addresses a long-standing issue. Content negotiation is used to provide different representations of the same resource in different formats. What content negotiation is not is a protocol to return the content itself described by the DOI instead of the metadata describing the content, e.g. a PDF or CSV file. The initial implementation of DataCite DOI content negotiation didn't make that clear distinction and allows registration of custom content types, including those that typically are associated with content rather than metadata, e.g.
application/pdf. Registration of custom content types is still possible with the current version of the service, but we are today announcing that we will retire this functionality on January 1st, 2020.
We know that many organizations make heavy use of custom content types for DataCite DOIs, so we provide both a long transition period and alternative approaches to achieve the same.
On October 1st, 2019 we will retire support for custom content types via the DOI resolver
https://doi.org. You can continue to use custom content types by using the DataCite content negotiation service at data.datacite.org directly, e.g.
curl -LH "Accept: application/x-bibtex" https://data.datacite.org/10.5438/0000-0C2G
Starting January 1st, 2020 custom content types will no longer be supported.
There are two alternatives to using custom content types in content negotiation:
/mediaAPI endpoint to access exactly the information currently made available via content negotiation
Going forward, the upcoming changes will lead to improvements in two areas:
Please read our support documentation for content negotiation for more details, or reach out to DataCite support if you need help transitioning from custom content types you have registered in the past.
This blog post was originally published on the DataCite Blog.
Dasler, R. (2018). Create dois with the rest api. https://doi.org/10.5438/S8RT-ZV48
Fenner, M. (2017). A content negotiation update. https://doi.org/10.5438/0000-01QJ
Using Jupyter Notebooks with GraphQL and the PID Graph
Two weeks ago DataCite announced the pre-release version of a GraphQL API [Fenner (2019)]. GraphQL simplifies complex queries that for example want to retrieve information about the authors, funding and data citations for a dataset with a DataCite DOI. ...
Introducing the PID Graph
Persistent identifiers (PIDs) are not only important to uniquely identify a publication, dataset, or person, but the metadata for these persistent identifiers can provide unambiguous linking between persistent identifiers of the same type, e.g. ...