In late February, twenty-four of DataCite’s twenty-seven members gathered in Amsterdam for our annual Strategy Meeting and General Assembly. DataCite members are the voting body of the organisation and work directly with data centers and the data sharing community. The focus of the meeting was evaluating how DataCite can continue to provide quality services and meet the continuously changing needs of the research community.

With the release of Dataverse 4.3 in mid-March, anyone installing or updating to the most recent version of the Dataverse software will be able to mint DOIs directly through the DataCite Metadata Store API.

As DataCite’s Technical Director I am very excited to announce that DataCite is looking for an application developer to strengthen our technical team. Working for DataCite is an opportunity to work on interesting development work around scholarly infrastructure and data citation. We are a small team, which requires flexibility, but it is a chance to work on a broad range of topics, from frontend development to DevOps work.

I was pleased to present at IDCC16 on a research paper called The location of the citation: Changing practices in how publications cite original data in the Dryad Digital Repository (see preprint: Mayo et al, [-@https://doi.org/10.5281/zenodo.32412]). Recently, organizations including CrossRef and the Digital Curation Center (DCC) have recommended as a best practice that original data citations appear in the works cited sections of the

At DataCite we are incredibly proud of supporting Open Science. Over the past several years, DataCite DOIs have been assigned to millions of research datasets. All of these DOIs are an important step towards making data a first-class citizen in scholarly research – they all deserve a round of applause, but some deserve to be highlighted. Einstein predicted the existence of gravitational waves under his general theory of relativity in 1916.

We are happy to announce a new feature that enables users to more easily suggest corrections and enhancements of information about research data repositories registered in re3data.org.

The DataCite Metadata Working Group has prepared a DataCite to Dublin Core application profile (DC2AP) and would love to hear your comments about it! The profile will help you building Dublin Core compatible DataCite metadata records, using Dublin Core Metadata Initiative (DCMI) metadata terms and other ontologies. Along with the DC2AP, we are also releasing a DataCite Ontology.

We are pleased to announce the publication of version 3.0 of the “Metadata Schema for the Description of Research Data Repositories” [@https://doi.org/10.2312/RE3.008]. This updated version of the re3data.org schema incorporates feedback from users as well as changes in registry policies and structural adjustments to the schema designed to better reflect changes in the landscape of research data repositories.

As a provider of crucial scholarly infrastructure, it is critical that DataCite not only provides a reliable service, but also properly communicates problems. The best way to do this is via a central status page, a best practice used by many organizations from Github and Diqus to Slack.

The DataCite blog has migrated to a new platform, from a hosted version at Ghost to a self-hosted version using Jekyll. The main reason for this change is that it gives us more control over the formatting of blog posts. The migration was easy as both Ghost and Jekyll use markdown to format blog posts, and the blog post URLs haven’t changed.

When I started as DataCite Technical Director four months ago, my first post [@http://datacite.org/data-driven-development] on this blog was about what I called Data-Driven Development . The post included a lot of ideas on how to approach development and technical infrastructure. In this post I want to take a second look.