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.
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.
Please visit Crossref’s official Data & Software Citations Deposit Guide for deposit details. Very carefully, one at a time? However you wish. Last year, we introduced linking publication metadata to associated data and software when registering publisher content with Crossref Linking Publications to Data and Software.
TL;DR 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 community@crossref.org and include the text conference identifiers WG in the subject heading.
Recently we announced that we were making some new recommendations in our DOI display guidelines. One of them was to use the secure HTTPS protocol to link Crossref DOIs, instead of the insecure HTTP.
We began accepting preprints as a new record type last month (in a category known as “posted content” in our XML schema). Over 1,000 records have already been registered in the first few weeks since we launched the service.
As a follow-up to our blog posts on the Crossref REST API we talked to SHARE about the work they’re doing, and how they’re employing the Crossref metadata as a piece of the puzzle.
Crossref was founded to enable collaboration between publishers. As our membership has grown and diversified over recent years, it’s becoming even more vital that we take input from a representative cross-section of the membership.
Crossref LIVE16 opened with a Mashup Day on 1st November 2016 in London. Attendees from the scholarly communications world met to chat with Crossref team members in an open house atmosphere.
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.
We’re excited to say that we’ve finished the work on our infrastructure to allow members to register preprints. Want to know why we’re doing this?
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. But there still seems to be one piece of the infrastructure that is missing.