DOI content negotiation is one of the oldest DataCite services, launched in 2012. Content negotiation makes it easy to fetch DataCite metadata in other metadata formats, for example BibTeX or schema.org , or as formatted citation in one of more than 5,000 citation styles.
The connections between scholarly resources generated by persistent identifiers (PIDs) and associated metadata form a graph: the PID Graph [@https://doi.org/10.5438/jwvf-8a66]. We developed this PID Graph concept in the EC-funded FREYA project, and have identified important use cases and technical requirements.
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?
Following the announcement of Trisha Cruse’s retirement, DataCite has started its search for a dynamic, committed, and entrepreneurial Executive Director to build on our exceptional record of providing first-class services to the research community. DataCite was founded in 2009 and celebrates its 10 year anniversary this year. DataCite has seen tremendous growth during these 10 years, in terms of members, services, and staff.
At the end of last year we conducted the first DataCite member survey. And one of the things you told us is that relevant information doesn’t always reach you. This is obviously really important to us, so we immediately put it on our 2019 roadmap. Another development last year was the release of the EU General Data Protection Regulation (GDPR), which specifies how the collection of personal information needs to be handled.
It is with mixed feelings that I announce that our Executive Director, Trisha Cruse, plans to retire later this year. I’m sad that Trisha will be leaving us, grateful for all the work Trisha has done for DataCite, but also happy that our friend and colleague will be able to take on new life adventures. As many of you will know, Trisha has been with DataCite from day one. Trisha was there when on December 1, 2009 DataCite was founded in London.
As some of you may have seen at our last Open Hours, our roadmap has a new look. The previous version was fed directly from our GitHub milestones. This meshed nicely with how we operate at DataCite, but we heard from many of you that GitHub wasn’t so intuitive for providing feedback if it wasn’t already something you use every day.
Two weeks ago DataCite announced the pre-release version of a GraphQL API [@https://doi.org/10.5438/qab1-n315]. GraphQL simplifies complex queries that for example want to retrieve information about the authors, funding and data citations for a dataset with a DataCite DOI.
DataCite DOIs describe resources such as datasets, samples, software and publications with rich metadata.
We’ve previously shared with you our plans to migrate all of our services from Solr to Elasticsearch. (See for example our 2019 preview [@https://doi.org/10.5438/bckb-qy95] or how we’ve used Elasticsearch to make an improved DataCite Search [@https://doi.org/10.5438/vyd9-ty64]. Elasticsearch is already a key component of DOI Fabrica and of DataCite Search, and we’re in the process of bringing it to our other services, too.
When we launched the DOI registration form in DOI Fabrica last year, we purposely kept it pretty basic. We wanted to get the most-used metadata fields in front of the people who needed them as soon as possible. But it’s always been our intention to expand the form and make it more useful for more metadata needs for more people. Today we’re announcing a new and improved DOI Fabrica form that takes a step in that direction. What has changed?