Linked Data - Crossref

Redirecting redirection

Geoffrey Bilder, Jonathan Rees, Henry Thompson – 2018 April 24

In IdentifiersLinked DataMetadataProgrammingStandards

Crossref has decided to change the HTTP redirect code used by our DOIs from 303 back to the more commonly used 302. Our implementation of 303 redirects back in 2010 was based on recommended best practice for supporting linked data identifiers. Unfortunately, very few other parties have adopted this practice.

DOI-like strings and fake DOIs

Geoffrey Bilder – 2016 June 29

In DoisIdentifiersLinked Data

TL;DR Crossref discourages our members from using DOI-like strings or fake DOIs. Details Recently we have seen quite a bit of debate around the use of so-called “fake-DOIs.” We have also been quoted as saying that we discourage the use of “fake DOIs” or “DOI-like strings”. This post outlines some of the cases in which we’ve seen fake DOIs used and why we recommend against doing so. Using DOI-like strings as internal identifiers Some of our members use DOI-like strings as internal identifiers for their manuscript tracking systems.

Clinical trial data and articles linked for the first time

Daniel Shanahan, Kirsty Meddings – 2016 May 17

In Clinical TrialsCrossmarkInteroperabilityLinked Data

It’s here. After years of hard work and with a huge cast of characters involved, I am delighted to announce that you will now be able to instantly link to all published articles related to an individual clinical trial through the Crossmark dialogue box. Linked Clinical Trials are here! In practice, this means that anyone reading an article will be able to pull a list of both clinical trials relating to that article and all other articles related to those clinical trials – be it the protocol, statistical analysis plan, results articles or others – all at the click of a button.

Crossref & the Art of Cartography: an Open Map for Scholarly Communications

Jennifer Lin – 2016 January 08

In Crossref LabsDataEvent DataFundersIdentifiersLinked DataMetadataOrcidXml

In the 2015 Crossref Annual Meeting, I introduced a metaphor for the work that we do at Crossref. I re-present it here for broader discussion as this narrative continues to play a guiding role in the development of products and services this year.

Metadata enable connections

At Crossref, we make research outputs easy to find, cite, link, and assess through DOIs. Publishers register their publications and deposit metadata through a variety of channels (XML, CSV, PDF, manual entry), which we process and transform into Crossref XML for inclusion into our corpus. This data infrastructure which makes possible scholarly communications without restrictions on publisher, subject area, geography, etc. is far more than a reference list, index or directory.

DOI Event Tracker (DET): Pilot progresses and is poised for launch

Jennifer Lin – 2015 September 15

In OrcidCollaborationDataEvent DataFundersIdentifiersInteroperabilityLinked DataMember BriefingNews ReleaseWikipedia

Publishers, researchers, funders, institutions and technology providers are all interested in better understanding how scholarly research is used. Scholarly content has always been discussed by scholars outside the formal literature and by others beyond the academic community. We need a way to monitor and distribute this valuable information.

♫ Researchers just wanna have funds ♫

Geoffrey Bilder – 2014 April 10

In OrcidCrossmarkCrossref LabsFundersIdentifiersLinked DataMetadataOrcid

photo credit Summary You can use a new Crossref API to query all sorts of interesting things about who funded the research behind the content Crossref members publish. Background Back in May 2013 we launched Crossref’s FundRef service. It can be summarized like this: Crossref keeps and manages a canonical list of Funder Names (ephemeral) and associated identifiers (persistent). We encourage our members (or anybody, really- the list is available under A CC-Zero license waiver) to use this list for collecting information on who funded the research behind the content that our members publish.

Turning DOIs into formatted citations

Karl Ward – 2011 November 28

In Citation FormatsCrossref LabsDoisLinked DataMetadata

Today two new content types were added to dx.doi.org resolution for Crossref DOIs. These allow anyone to retrieve DOI bibliographic metadata as formatted bibliographic entries. To perform the formatting we’re using the citation style language processor, citeproc-js which supports a shed load of citation styles and locales. In fact, all the styles and locales found in the CSL repositories, including many common styles such as bibtex, apa, ieee, harvard, vancouver and chicago are supported.

DataCite supporting content negotiation

Geoffrey Bilder – 2011 October 10

In DataDataciteIdentifiersLinked DataStandards

In April In April for its DOIs. At the time I cheekily called-out DataCite to start supporting content negotiation as well. Edward Zukowski (DataCite’s resident propellor-head) took up the challenge with gusto and, as of September 22nd DataCite has also been supporting content negotiation for its DOIs. This means that one million more DOIs are now linked-data friendly. Congratulations to Ed and the rest of the team at DataCite. We hope this is a trend.

Content Negotiation for Crossref DOIs

Geoffrey Bilder – 2011 April 19

In DataciteIdentifiersLinked DataMetadataProgrammingStandards

So does anybody remember the posting DOIs and Linked Data: Some Concrete Proposals? Well, we went with option “D.” From now on, DOIs, expressed as HTTP URIs, can be used with content-negotiation. Let’s get straight to the point. If you have curl installed, you can start playing with content-negotiation and Crossref DOIs right away: curl -D - -L -H “Accept: application/rdf+xml” “http://0-dx.doi.org.lib.rivier.edu/10.1126/science.1157784” curl -D - -L -H “Accept: text/turtle” “http://dx.

DOIs and Linked Data: Some Concrete Proposals

Geoffrey Bilder – 2010 March 25

In IdentifiersLinked Data

Since last month’s threads (here, here, here and here) talking about the issues involved in making the DOI a first-class identifier for linked data applications, I’ve had the chance to actually sit down with some of the thread’s participants (Tony Hammond, Leigh Dodds, Norman Paskin) and we’ve been able sketch-out some possible scenarios for migrating the DOI into a linked data world. I think that several of us were struck by how little actually needs to be done in order to fully address virtually all of the concerns that the linked data community has expressed about DOIs.

RSS Feed

Blog