{"id":1300,"date":"2011-10-06T10:39:27","date_gmt":"2011-10-06T09:39:27","guid":{"rendered":"http:\/\/www.meanboyfriend.com\/overdue_ideas\/2011\/10\/why-we-need-to-adopt-apis-for-digitised-content\/"},"modified":"2011-10-06T11:07:11","modified_gmt":"2011-10-06T10:07:11","slug":"why-we-need-to-adopt-apis-for-digitised-content","status":"publish","type":"post","link":"http:\/\/www.meanboyfriend.com\/overdue_ideas\/2011\/10\/why-we-need-to-adopt-apis-for-digitised-content\/","title":{"rendered":"Why we need to adopt APIs for Digitised Content"},"content":{"rendered":"

Alastair Dunning from JISC (http:\/\/twitter.com\/alastairdunning<\/a>). Slides at\u00a0http:\/\/www.slideshare.net\/xcia0069\/creating-a-hive-of-activity-why-we-need-to-adopt-apis-for-digitised-content<\/a><\/p>\n

Commercial content services – Flickr, Google Books, Twitter – use APIs to all multiple services to access, manipulate and display their content.<\/p>\n

ImageKind – example of commercial service built on Flickr API
\nBulkr – enables functionality (data management) that Flickr doesn’t supply
\nFlickr Stackr – iPad app which uses the Flickr API
\nPicnik – online photo editor, which can use Flickr API – so successful that Flickr have now embedded into their site
\nOskope – visual search of Flickr content – one of many examples (I’ve used http:\/\/compfight.com<\/a> to search Flickr)<\/p>\n

The Flickr API has led to the creation of innovative products and services.<\/p>\n

But cultural and educational resources tend to lock data and interface together. Three examples Alastair showing – all use the ‘SEARCH then LIST’ approach to the interface. This is really useful, but it’s only one way of interacting with the content<\/p>\n

The trouble with current resources is that they demand cerain ways of analysing and representing the resource – and they constitute the creators’ way of seeing the world, not the users’. Diffierent audiences may benefit from different ways of interacting with the resources.<\/p>\n

More importantly an API can help break down the notion of a ‘collection’ and the related sils.<\/p>\n

Alastair now going to give examples of projects that have used APIs to give access to content.<\/p>\n

The NEWTON project – transcribing Isaac Newton’s manuscripts at University of Sussex. A completely separate project at the the University of Cambridge looking at putting scanned images of manuscripts online (I think). JISC funded some work to use APIs to bring content from these two projects together – so you can view both images and transcripts together.<\/p>\n

CERL Thesaurus – bringing together discovery mechanisms from CERL and Europeana<\/p>\n

Old Bailey – transcriptions of almost 200,000 trials – accessible via API. Means e.g. you can download transcriptions of groups of cases and manipulate locally – e.g. do computerised text analysis – example of using Voyeur tool to analyse all trials meeting certain keyword<\/p>\n

Using the API, researchers could test and revise the historical narrative of the evolution of court room practise at the Old Bailey.<\/p>\n

Another e.g. “Locating London’s Past” (coming soon) – API enables data to be brought together from multiple sources and visualised in new ways<\/p>\n

Some short-term wins of adopting APIs – bringing dispersed resources together and interacting with them in new ways.<\/p>\n

But long-term challenges – getting people to build, document and sustain, and explain why they are important. Some publishers suspicious; technical knowledge required to provide and exploit APIs<\/p>\n

Ultimately APIs open the possibility of moving beyond just presenting the information and get to exploiting the information.<\/p>\n","protected":false},"excerpt":{"rendered":"

Alastair Dunning from JISC (http:\/\/twitter.com\/alastairdunning). Slides at\u00a0http:\/\/www.slideshare.net\/xcia0069\/creating-a-hive-of-activity-why-we-need-to-adopt-apis-for-digitised-content Commercial content services – Flickr, Google Books, Twitter – use APIs to all multiple services to access, manipulate and display their content. ImageKind – example of commercial service built on Flickr API Bulkr – enables functionality (data management) that Flickr doesn’t supply Flickr Stackr – iPad app which […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[79,78],"class_list":["post-1300","post","type-post","status-publish","format-standard","hentry","category-uncategorized","tag-libeb11","tag-liber-eblida"],"_links":{"self":[{"href":"http:\/\/www.meanboyfriend.com\/overdue_ideas\/wp-json\/wp\/v2\/posts\/1300","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.meanboyfriend.com\/overdue_ideas\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.meanboyfriend.com\/overdue_ideas\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.meanboyfriend.com\/overdue_ideas\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"http:\/\/www.meanboyfriend.com\/overdue_ideas\/wp-json\/wp\/v2\/comments?post=1300"}],"version-history":[{"count":4,"href":"http:\/\/www.meanboyfriend.com\/overdue_ideas\/wp-json\/wp\/v2\/posts\/1300\/revisions"}],"predecessor-version":[{"id":1305,"href":"http:\/\/www.meanboyfriend.com\/overdue_ideas\/wp-json\/wp\/v2\/posts\/1300\/revisions\/1305"}],"wp:attachment":[{"href":"http:\/\/www.meanboyfriend.com\/overdue_ideas\/wp-json\/wp\/v2\/media?parent=1300"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.meanboyfriend.com\/overdue_ideas\/wp-json\/wp\/v2\/categories?post=1300"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.meanboyfriend.com\/overdue_ideas\/wp-json\/wp\/v2\/tags?post=1300"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}