CSV (comma-separated values) is a popular file format for data. It is popular because it is very simple: CSV is text-based and any application that can open text files can read or write CSV. This makes it a good fit for digital preservation. We don’t know how many of the datasets in DataCite use CSV because the format metadata attribute is not used much (this query gives you some examples), but we know that the number is big.

This is a guest post by Jennifer Lin, project manager for the Making Data Count project, and since last week CrossRef Director of Product Management. Counting is hard. But when it comes to research data, not in the way we thought it was (example 1, example 2, example 3). The Making Data Count (MDC) project aims to go further – measurement.

In the first post of this new blog a few weeks ago I talked about Data-Driven Development, and that service monitoring is an important aspect of this. The main service DataCite is providing is registration of digital object identifiers (DOIs) for scholarly content, in particular research data.

Today I am pleased to announce the launch of a new service, DataCite Labs Search – the service is available immediately at https://search.datacite.org/. This is one of THOR’s first services and is based on work in the earlier EC-funded ODIN Project. The ODIN project launched the DataCite/ORCID claiming tool in June 2013. The DataCite/ORCID claiming tool allows users to add works from the DataCite Metadata Store (MDS) to their ORCID profile.

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.

Today DataCite received an email from a user alerting us that there are some small inconsistencies with our recommended data citation format: Creator (PublicationYear): Title. Publisher. Identifier at https://www.datacite.org/services/cite-your-data.html Creator; (PublicationYear): Title; Publisher.

This week I start as the new DataCite Technical Director. While I get up to speed with existing DataCite services and infrastructure, and we start to launch new services (e.g. this blog), this is also a good time to communicate the overall approach I am taking. I like to call it Data-Driven Development , or DDD as we all love acronyms.