We are delighted to announce the launch of IGSN ID registration using DataCite services. This is the culmination of almost one year of work after the signing of a partnership agreement between DataCite and the IGSN e.V. in October 2021. The ability to register material samples with IGSN IDs is now available to all DataCite Members and Consortium Organizations.
This blog post is cross-posted from the Research Organization Registry blog with a preceding introductory paragraph from DataCite. DataCite together with California Digital Library and Crossref sustain the Research Organization Registry (ROR) operations through expertise in developing open, sustainable, community-driven infrastructure for scholarly communications.
In a blog post four weeks ago DataCite Executive Director Matt Buys talked about the DataCite strategic priorities for 2020 [@https://doi.org/10.5438/9j86-bv91]. In this post we want to talk a bit more about the strategic priorities for this year we have regarding services and infrastructure work: a) consolidation of our services and infrastructure, and b) stronger emphasis on member-driven product development.
Our OAI-PMH service is one of the common ways we offer to harvest our public metadata, and we are launching a new version this Wednesday. This technology refresh allows us to continue supporting the OAI-PMH service. For the most part, there is no functional change, we adhere to the OAI-PMH standards and have attempted to keep the service as backward compatible as possible.
DataCite is excited to announce that Sarala Wimalaratne will join our team in the new role ’Head of Infrastructure Services’ on September 1st. Sarala brings a wealth of experience in the Open Science and PID communities and will be a great addition to our team. Get to know her better via this interview. 1. Can you tell us a little bit about what you did before you will start working for DataCite?
We frequently receive questions from our members and clients about our current approach to testing. Some of you have accounts in our test system, some of you have the “demo” accounts introduced earlier this year, and all of you have access to the test prefix 10.5072 as part of your regular production account. What’s the difference? Which one are you supposed to use for what?
We are happy to announce the relaunch of our DOI Citation Formatting service, available at http://citation.crosscite.org. The service uses the citeproc.js library by Frank Bennett together with the more than 5,000 citation styles made available by the citationstyles.org project. The service works with DOIs from Crossref, mEDRA and ISTIC in addition to DataCite DOIs.
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.
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.
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.
