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.

Last Monday, DataCite organized the first in a series of t webinars were we will be sharing our latest developments, new services, collaborations with different organizations and best practices to get the most out of persistent identifiers and data publication. Our hope is to connect with the DataCite community to bring everyone up to date and gather feedback on our work.

The inaugural meeting of the DataCite re3data Working Group was convened in Paris on September 20th at the offices of the International Council for Science (ICSU). Co-chairs Michael Witt and Frank Scholze gave the background and history of Databib, which was initially funded by the IMLS in the United States, and re3data.org, which has been funded by DFG in Germany.

DataCite Labs today is launching the DataCite Profiles service, a central place for users to sign in with DataCite, using their ORCID credentials. The first version of DataCite Profiles focusses on integration with ORCID via the Search & Link and Auto-Update services, described in a previous blog post.

Recently I was at a conference and a fellow conference-goer saw on my name badge that that I worked for DataCite and they stepped back and said, “ Wow, DataCite must be a very exciting place to be right now. ” I agree. It is very exciting and I am thrilled to be DataCite’s new Executive Director. Over the past year DataCite has seen an enormous uptake in the use of our services.

This Monday ORCID, CrossRef and DataCite announced (ORCID post, CrossRef post, DataCite post) the new auto-update service that automatically pushes metadata to ORCID when an ORCID identifier is found in newly registered DOI names. This is the first joint announcement by the three organizations, and shows the close collaboration between ORCID, CrossRef and DataCite.