As we have talked about before, the DataCite Metadata Working Group has prepared a DataCite to Dublin Core application profile (DC2AP) and an ontology (DC2RDF) and is currently running a public review to become a DCMI Community Specification. Two weeks ago, DataCite organised a webinar to discuss the first round of feedback received.

This week most of the DataCite staff is attending the Force16 conference in Portland, Oregon. Force16 brings together a large group of people who either already work with DataCite in one way or another, or are doing interesting projects of relevance to DataCite. ImpactStory is a non-profit that helps scientists learn where their research is being cited, shared, saved and more.

The following is a guest post by Daniel S. Katz, cross-posted from his blog. After a number of general discussions in the research communication community, mostly focused on software citation, and then a few separate discussions with Anita Bandrowski and Martin Fenner, it’s become clear to me that we need something like a group (perhaps hierarchical) object identifier (GROUPID), which is somewhat different than a DOI, or at least

In a guest post two weeks ago Elizabeth Hull explained that only 6% of Dryad datasets associated with a journal article are found in the reference list of that article, data she also presented at the IDCC conference in February [@https://doi.org/10.5281/zenodo.32412]. This number has increased from 4% to 8% between 2011-2014, but is still low.

re3data.org has reached a milestone of identifying and listing 1,500 research data repositories, making it the largest and most comprehensive registry of data repositories available on the web. It has grown steadily since its launch four years ago to cover a wide range of disciplines from around the world. In other news, badges are now available for repositories to acknowledge and link to their listings in re3data.org.

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.

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.

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.

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.