
The DataCite Metadata Schema 4.1 has been released today. If the 4.1 release has a theme, it is support for software citation.
The DataCite Metadata Schema 4.1 has been released today. If the 4.1 release has a theme, it is support for software citation.
Today DataCite is launching DOI Fabrica, the next generation of DataCite’s DOI registration service, replacing the Metadata Store (MDS). This is the biggest and most important product release DataCite has done in many years, and the result of nine months of hard work by the entire DataCite team. DOI registration is the core service that DataCite is providing to its members and the data centers they work with.
Cross-posted from the Make Data Count blog. As a research and scholarly communications community, we value methods to gauge the impact of research outputs, and we do this in the forms of citations and downloads. But, until now this has been limited to traditional journal publications, and scholarly research is much more than an article.
PIDapalooza is back, by popular demand! We’re building on the the best of the inaugural PIDapalooza and organizing two days packed with discussions, demos, informal and interactive sessions, updates, talks by leading PID innovators, and more. There will be lots of opportunities to network – and to learn from and engage with PID enthusiasts from around the world. All in a fun, relaxed, and welcoming atmosphere! We’re looking for your PIDeas!
As DataCite’s Technical Director I am very excited to announce that DataCite is looking for another application developer to strengthen our team. This is an opportunity to work on interesting development work around scholarly infrastructure with a focus on research data. You would join a small technical team of one application developer based in Berlin and me based in Hannover, also in Germany.
The California Digital Library (CDL) and Purdue University are adopting a new strategic direction for their EZID digital object identifier (DOI) services to support DataCite’s long-term sustainability and to improve DOI services for the broader community. Over the course of the next two years, EZID DOI services will be phased out for users outside of the University of California.
New services, APIs, enhanced functions, and even websites can be hard to grasp. At DataCite we understand how difficult it is to get started and stay up-to-date with all the developments in the scholarly communications ecosystem. That is why we decided to pull all DataCite’s information into a single Support Center. Our goal is to present our user community with a complete, up-to-date, easy to read, searchable resource.
Over the next several months DataCite will embark on a new development path focusing on member-facing services. Our goal is to provide easy, understandable, predictable, and robust services to create, manage, find, use and track DataCite DOIs to make data sharing and citation easier. Our activities are not limited to technical development but will include support services that will foster the successful use of all our services.
The Alfred P. Sloan Foundation has made a 2-year, $747K award to the California Digital Library, DataCite and DataONE to support collection of usage and citation metrics for data objects. Building on pilot work, this award will result in the launch of a new service that will collate and expose data level metrics.
As our Technical Director Martin Fenner shared a few days ago, our new Content Resolver service is an ideal interface and information source to build integrations. Today, we want to share with you a few potential (and fancy!) integrations one could build using content negotiation and DOI metadata. Format your references You have probably seen DataCite’s Citation Formatter or the export functionality of DataCite Search.
While it is a best practice for DOIs (expressed as URL) to send the user to the landing page for that resource [@https://doi.org/10.7717/peerj-cs.1; @https://10.1101/097196], sometimes we want something else: metadata , e.g. to generate a citation, or to go to the content itself. The easiest way to do that is to use DOI content negotiation.