Scientific Publishing and Developer APIs

Rafael Sidi loves to quote Bob Dylan’s song ‘The times they are a-changing”… Certainly in the scientific publishing developer APIs world.

For years there were APIs available from the scientific abstracts databases Scopus, WoS, PubMed, etc.

Last year Elsevier launched SciVerse Application Marketplace that provides developers APIs (Application Programming Interface) to build applications that will integrate into the SciVerse suite of products (ScienceDirect, Scopus, Hub). Some examples –

  • SciverNote:  allows you to save ScienceDirect article abstracts and/or references to Evernote®
  • Top Reviews:  find the most relevant review articles in your Scopus search results
  • iSpeech Audio Reader: This one is pretty cool – reads your ScienceDirect articles aloud
Check out the current Applications Gallery.
You may also want to check out what Nature will be launching soon. This appears to be limited to Search APIs, scientific bookmarking tool (Connotea) APIs, and the social networking site (Nature Network) APIs. There’s a nice presentation (embedded below) put together by Chandran Honour that lays out the api landscape in scientific publishing (Oct 25, 2011)
PLoS has already announced their APIs for search and Article Metrics earlier this year. Springer has announced APIs to their Images database, APIs to the metadata for their journal/book content and API to query their OpenAccess content.
There are probably several that I haven’t mentioned here.
These are exciting times and it will be interesting to see if some understanding develops across publishers to standardize APIs. In the end the goal is to enable researchers to create solutions that are specific to their needs and hopefully help advance scientific research.
Advertisements

7 Ways to Make Your API More Successful

This guest post comes from Daniel Jacobson, Director of Application Development for NPR. Daniel leads NPR’s content management solutions, is the creator of the NPR API and is a frequent contributor to the Inside NPR.org blog.

The purpose of a content API is to make the content available to its audience in the most useful and efficient way possible. To be a useful API, it needs to help the developers make their jobs easier. This could mean a wide range of things, including making it easier to dig into the API, allowing for greater flexibility in the responses, improved performance and efficiency for both the API and its consumer. Below are seven development techniques all of which are part of the NPR API that can help content providers improve the usefulness and efficiency of their APIs on both sides of the track. These techniques played a critical role in the success of the API which now delivers over 700 million stories per month to its users more stats on the NPR API coming soon on our Inside NPR.org blog.

via 7 Ways to Make Your API More Successful.

Data is at the heart of new science ecosystem – DATA – Research Information

Open data and open APIs offer huge opportunities for research and innovation, writes Elsevier’s Rafael Sidi

via Data is at the heart of new science ecosystem – DATA – Research Information.