Blog

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.  Cynthia Hudson-Vitale from SHARE explains in more detail…

We first met the team from PaperHive at SSP in June, pointed them in the direction of the Crossref Metadata API and let things progress from there. That’s the nice thing about having an API - because it’s a common and easy way for developers to access and use metadata, it makes it possible to use with lots of diverse systems and services.

So how are things going? Alexander Naydenov, PaperHive’s Co-founder gives us an update on how they’re working with the Crossref metadata:

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.

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.

[ Crossref Labs loves to be the last to jump on an internet trend, so what better than than to combine the Doge meme with altmetrics? Note: The API calls below have been superceeded with the development of the Event Data project. See the latest API documentation for equivalent functionality Want to know how many times a Crossref DOI is cited by the Wikipedia? http://0-det-labs-crossref-org.libus.csd.mu.edu/works/doi/10.1371/journal.pone.0086859 Or how many times one has been mentioned in Europe PubMed Central?

The South Park movie , “Bigger, Longer & Uncut” has a DOI: a) http://0-dx-doi-org.libus.csd.mu.edu/10.5240/B1FA-0EEC-C316-3316-3A73-L So does the pornographic movie, “Young Sex Crazed Nurses”: b) http://0-dx-doi-org.libus.csd.mu.edu/10.5240/4CF3-57AB-2481-651D-D53D-Q And the following DOI points to a fake article on a “Google-Based Alien Detector”: c) http://0-dx-doi-org.libus.csd.mu.edu/10.6084/m9.figshare.93964 And the following DOI refers to an infamous fake article on literary theory: d) http://0-dx-doi-org.libus.csd.mu.edu/10.2307/466856 This scholarly article discusses the entirely fictitious Australian “Drop Bear”: e) http://0-dx-doi-org.libus.csd.mu.edu/10.1080/00049182.2012.731307 The following two DOIs point to the same article- the first DOI points to the final author version, and the second DOI points to the final published version:

If you’ve ever thought that scholarly citation practice was antediluvian and perverse- you should check-out patents some day. Over the past year of so Crossref has been working with Cambia and the The Lens to explore how we can better link scholarly literature to and from the patent literature. The first object of our collaboration was to attempt to link patents hosted on the new, beta version of The Lens to the Scholarly literature.

Since I’ve already blogged about this a number of times before here, I thought I ought to include a link to a fuller writeup in this month’s D-Lib Magazine of our nature.com OpenSearch service which serves as a case study in OpenSearch and SRU integration: doi:10.1045/july2010-hammond

We’re pleased to announce that a Crossref working group has released a set of best practice recommendations for scholarly publishers producing RSS feeds. Variations in practice amongst publisher feeds can be irritating for end-users, but they can be insurmountable for automated processes. RSS feeds are increasingly being consumed by knowledge discovery and data mining services. In these cases, variations in date formats, the practice of lumping all authors together in one <dc:creator> element, or generating invalid XML can render the RSS feed useless to the service accessing it.

An Overview of the OAI Object Reuse and Exchange Interoperability Framework View more Microsoft Word documents from hvdsomp. This is a very slick presentation by Herbert Van de Sompel on OAI-ORE which he’s due to give today for a workshop at the INFORUM 2009 15th Conference on Prrofessional Information Resources in Prague. It’s on the long side at 167 slides but even if you just flip though or sample it selectively you’ll be bound to come away with something.