As part of our blog post series on the Crossref REST API, we talked to Silvio Peroni and David Shotton of OpenCitations (OC) about the work they’re doing, and how they’re using the Crossref REST API as part of their workflow.
Rachael Lammey – 2017 July 25
As a follow-up to our blog posts on the Crossref REST API we talked to the Copyright Licensing Agency (CLA) about the work they’re doing, and how they’re using the Crossref REST API as part of their workflow.
Jennifer Kemp – 2017 July 05
We’ve been talking about it at events, blogging about it on our site, living it, breathing it, and even sometimes dreaming about it, and now we are delighted to announce that Crossref Event Data has entered Beta.
Ed Pentz – 2017 March 28
At the end of October 2016, Crossref, DataCite, and ORCID reported on collaboration in the area of organization identifiers. We issued three papers for community comment and after input we subsequently announced the formation of The OI Project, along with a call for expressions of interest from people interested in serving on the working group.
Ed Pentz – 2017 March 15
We have updated our DOI display guidelines as of March 2017, this month! I described the what and the why in my previous blog post New Crossref DOI display guidelines are on the way and in an email I wrote to all our members in September 2016. I’m pleased to say that the updated Crossref DOI display guidelines are available via this fantastic new website and are now active. Here is the URL of the full set of guidelines in case you want to bookmark it (https://www.crossref.org/display-guidelines/) and a shareable image to spread the word on social media.
Geoffrey Bilder – 2017 February 15
Crossref and DataCite are forming a working group to explore conference identifiers and project identifiers. If you are interested in joining this working group and in doing some actual work for it, please contact us at
firstname.lastname@example.org and include the text
conference identifiers WG in the subject heading.
Rachael Lammey – 2016 December 01
Joe Wass – 2016 November 04
As the linking hub for scholarly content, it’s our job to tame URLs and put in their place something better. Why? Most URLs suffer from link rot and can be created, deleted or changed at any time. And that’s a problem if you’re trying to cite them.
Ed Pentz – 2016 October 31
The scholarly communications sector has built and adopted a series of open identifier and metadata infrastructure systems to great success. Content identifiers (through Crossref and DataCite) and contributor identifiers (through ORCID) have become foundational infrastructure to the industry.
Ed Pentz – 2016 September 27
Crossref will be updating its DOI Display Guidelines within the next couple of weeks. This is a big deal. We last made a change in 2011 so it’s not something that happens often or that we take lightly. In short, the changes are to drop “dx” from DOI links and to use “https:” rather than “http:”. An example of the new best practice in displaying a Crossref DOI link is: https://doi.org/10.1629/22161
2018 October 16
2018 October 15
2018 October 10
2018 October 05