Today we posted a new blog post on the DataCite blog. There are minor changes to the content negotiation service under the hood, but most importantly this is a deprecation of custom content types, i.e. registering a content type for a specific DOI.
- Starting October 1st, 2019 custom content types will no longer be supported via https://doi.org
- Starting January 1st, 2020, custom content types will no longer be supported via https://data.datacite.org
Going forward, there are two alternatives to using custom content types in content negotiation:
- use the REST API, specifically the
/mediaAPI endpoint to access exactly the information currently made available via content negotiation - use content negotiation at the landing page for the resource that the DOI resolves to. DataCite content negotiation is forwarding all requests with unknown content types to the URL registered in the handle system.
Feel free to provide feedback or ask questions here.