Today DataCite is launching DOI Fabrica, the next generation of DataCite’s DOI registration service, replacing the Metadata Store (MDS). This is the biggest and most important product release DataCite has done in many years, and the result of nine months of hard work by the entire DataCite team. DOI registration is the core service that DataCite is providing to its members and the data centers they work with.

While it is a best practice for DOIs (expressed as URL) to send the user to the landing page for that resource (Starr et al., 2015), sometimes we want something else: metadata , e.g. to generate a citation, or to go to the content itself. The easiest way to do that is to use DOI content negotiation.

Three weeks ago we started assigning DOIs to every post on this blog (Fenner, 2016c). The process we implemented uses a new command line utility and integrates well with our the publishing workflow, with (almost) no extra effort compared to how we published blog posts before. Given that DataCite is a DOI registration agency, we obviously are careful about following best practices for assigning DOIs.

On Tuesday the journal PLOS ONE celebrated its 10th anniversary (see blog post by PLOS ONE Editor-in-Chief Jörg Heber and blog post by PLOS ONE Managing Editor Iratxe Puebla and PLOS Advocacy Director Catriona MacCallum). PLOS ONE (and PLOS) have changed scholarly publishing in many ways, from a DataCite perspective probably most importantly via the data policy updated in February 2014 that states that PLOS ONE was not the first journal with a

Eating your own dog food is a slang term to describe that an organization should itself use the products and services it provides. For DataCite this means that we should use DOIs with appropriate metadata and strategies for long-term preservation for the scholarly outputs we produce.

Geoff Bilder from CrossRef likes to show the following slide at scholarly conferences, and then asks the audience what they see: Most of us probably immediately recognize this document as a scholarly article.

In 1998 Tim Berners-Lee coined the term cool URIs (1998), that is URIs that don’t change. We know that URLs referenced in the scholarly literature are often not cool, leading to link rot (Klein et al., 2014) and making it hard or impossible to find the referenced resource.

Today we are launching a new version of the DataCite API at http://api.datacite.org. This new version includes numerous bug fixes and now includes related resources (e.g. data centers, members or contributors) according to the JSONAPI spec. The changelog can be found here. Current users of the API should watch out for breaking changes in the meta object used for faceting.

The scholarly research community has come to depend on a series of open identifier and metadata infrastructure systems to great success. Content identifiers (through DataCite and Crossref) and contributor identifiers (through ORCID) have become foundational infrastructure for the community.

On July 12, 2016, DataCite invited Andreas Rauber to present the recommendations for dynamic data citation of the RDA Data Citation Working Group in a webinar. Andreas is one of the co-chairs of the RDA working group, and he gave a throughout overview of the recommendations, and the thinking that went into them. The final recommendations are available since last fall, and the current focus of the working group is to help with implementations.

This week we relaunched DataCite Search, providing a more user-friendly search interface for DataCite metadata. We also added functionality that was not available before. The new search uses a single entry box for queries, and filters by resource type, publication year and data center. A new Cite button will generate a citation in several popular citation styles, and in BibTeX and RIS import formats.