DataCite Support

DataCite Support

Welcome to DataCite's support site. Here you will find helpful information about our services. We have included comprehensive technical guides, training materials, and tips to help you successfully use DataCite services.

Get Started    API Reference

DataCite Content Negotiation

Access DataCite content negotiation here: https://data.datacite.org

What is DataCite Content Negotiation?

The DataCite content negotiation allows you to retrieve DOI metadata in different formats. A content negotiated request to a DOI resolver is very similar to a standard HTTP request, but based on the list of acceptable content types.

Custom content types will no longer be supported after January 1st, 2020

Registration of custom content types will be retired on October 1st, 2019 from the content negotiation via https://doi.org and on January 1st, 2020 from content negotiation via https://data.datacite.org. All requests for unknown content types will then be forwarded to the URL registered for the DOI in the handle system. The media API will continue to support registration and retrieval of content with custom content types.

It can be used by an HTTP client by configuring its HTTP Accept headers, or directly through a browser, constructing a URL.

Citation Formatter

The DataCite Citation Formatter is one important example of what can be done with DOI content negotiation. If you want more information, please visit DataCite Citation Formatter Documentation.

Who can use DataCite Content Negotiation?

DataCite content negotiation is open to the whole community and does not require authentication. It is particularly designed to provide direct access to all our DOIs, simplify integrations and avoid format conversions.

How does the DataCite Content Negotiation work?

The DOI proxy at doi.org will normally redirect a user to the resource location URL of a DOI. For example, the DOI "10.5284/1015681" redirects to a landing page describing the dataset, "Excavation of a Romano-British Cemetery...". Content negotiated requests to doi.org that ask for a content type which isn't "text/html" will be redirected to the DataCite content negotiation service.

       GET "Accept: text/html"
https://doi.org/10.5284/1015681

                   |
                   |
                   |
                   V

       Repository landing page
archaeologydataservice.ac.uk/archives/view/greylit/details.cfm?id=13979

Normal browser requests or explicit requests for text/html redirect to the content's landing page.

    GET "Accept: application/rdf+xml"
     https://doi.org/10.5284/1015681
                 |
                 |
                 |
                 V
       DataCite content negotiation service
http://data.datacite.org/10.5284/1015681

Requests for a data type redirect to a registration agency's metadata service.

Content Negotiation

Making a content negotiated request requires the use of the Accept HTTP header. Content types that are acceptable to the client (those that it knows how to parse), each with an optional "quality" value indicating its relative suitability. For example, a client that wishes to receive citeproc JSON if it is available, but which can also handle RDF XML if citeproc JSON is unavailable, would make a request with an Accept header listing both "application/citeproc+json" and "application/rdf+xml":

$ curl -LH "Accept: application/rdf+xml;q=0.5, application/vnd.citationstyles.csl+json;q=1.0" https://doi.org/10.5284/1015681

This request favours citeproc JSON but will accept RDF XML if citeproc is unavailable. The q values are optional. The request could have been written without them. The order of content types then becomes important; more suitable content types should be placed at the front of the Accept header.

$ curl -LH "Accept: application/vnd.citationstyles.csl+json, application/rdf+xml" https://doi.org/10.5284/1015681

DataCite supports different response codes, listed below. If multiple content types specified by the client are supported by a DOI then the content type with the highest "q" value (or, if no "q" values are specified, the one that appears first in the "accept" header) will be returned.

Code
Meaning

200

The request was OK.

204

The request was OK but there was no metadata available.

404

The DOI requested doesn't exist.

Link-based Content Type Requests

DataCite supports link-based content type requests. This method can be used with a regular web browser. In order to get a specific format please construct a URL following this pattern: https://data.datacite.org/MIME_TYPE/DOI.

Extra parameters, e.g. when using the text/x-bliography content type, can be included, e.g.

curl https://data.datacite.org/text/x-bibliography;style=ieee/10.5061/dryad.8515

This method allows DataCite data centres to link additional metadata and data itself using custom URLs, still using the primary URL for the DOI to point to the landing page of a data set.

Supported Content Types

DataCite supports a number of metadata content types:

Format
Content Type

application/rdf+xml

text/turtle

application/vnd.citationstyles.csl+json

application/vnd.schemaorg.ld+json

application/vnd.codemeta.ld+json

text/x-bibliography

application/x-research-info-systems

application/x-bibtex

application/vnd.datacite.datacite+xml

application/vnd.datacite.datacite+json

application/vnd.jats+xml

Would you like to know more?

If you have any questions, requests or ideas please contact us!

DataCite Content Negotiation


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.