A quot;lofiAPIquot;: Using open source
applications and simple XML to
build a library web service

Jason A. Clark
Head of ...
A quick look ahead…
Discussion of the benefits of web services for
libraries
Demo and walkthrough of the code that makes i...
Photo by Phil Gyford
Provide Web Services?
You have a service that benefits your users
best if they can get to their data from
outside the appl...
Demos and Downloads
Demo: A quot;lofiAPIquot; for Library Data
http://www.lib.montana.edu/%7Ejason/files/api/lofi/

Downlo...
Available Web Services
 Google
 Yahoo!
 Amazon
 eBay
 Flickr
 del.icio.us
 Google App Engine http://code.google.
 com/appe...
Web Services in Libraries
 Plymouth State: Scriblio
 Repository66: mash-up of OpenDOAR data with
 Google Maps and reposito...
How to...
 Components
 1. Database Engine
 2. Scripting Language

 Specifics
 1. Apache
 2. MySQL
 3. PHP
Why?
 Single Source, Multiple Endpoints
 1. Feed Readers
 2. Google Sitemap
 3. Remixed HTML
 4. A9 OpenSearch

 Allow for...
Last thoughts...
 This stuff is just beginning…
 Worldcat API
 Digital Library Federation API recommendation
 Library mash...
Questions?
Getting Started
Play in the sandbox – pick a service, study it
Yahoo Developer Central
http://developer.yahoo.com/
Amazon ...
Web Services - Sources
   AllCDCovers.com http://www.allcdcovers.com/api
   ISBNdb.com http://isbndb.com/docs/api/index.ht...
Terms: API
What is an API?

An application programming interface (or API) is a way for
developers to access parts of a rem...
Terms: Web Service
What is a Web Service?
  Broader term
  Public interface (API)
  Provides access to data and/or procedu...
Terms: Structured Data
Structured data = XML and JSON
   Extensible Mark-up Language and Javascript Object
   Notation
   ...
Contact Information
Jason A. Clark
Head of Digital Access and Web Services
Montana State University Libraries
jaclark@mont...
Upcoming SlideShare
Loading in …5
×

A "lofiAPI": Using open source applications and simple XML to build a library web service

1,173 views
1,113 views

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,173
On SlideShare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
11
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

A "lofiAPI": Using open source applications and simple XML to build a library web service

  1. 1. A quot;lofiAPIquot;: Using open source applications and simple XML to build a library web service Jason A. Clark Head of Digital Access and Web Services Montana State University Libraries
  2. 2. A quick look ahead… Discussion of the benefits of web services for libraries Demo and walkthrough of the code that makes it happen
  3. 3. Photo by Phil Gyford
  4. 4. Provide Web Services? You have a service that benefits your users best if they can get to their data from outside the application You want others to use your data store in their applications
  5. 5. Demos and Downloads Demo: A quot;lofiAPIquot; for Library Data http://www.lib.montana.edu/%7Ejason/files/api/lofi/ Download: A quot;lofiAPIquot; for Library Data http://www.lib.montana.edu/%7Ejason/files/api-lofi. zip
  6. 6. Available Web Services Google Yahoo! Amazon eBay Flickr del.icio.us Google App Engine http://code.google. com/appengine/ Amazon s3 Many more...
  7. 7. Web Services in Libraries Plymouth State: Scriblio Repository66: mash-up of OpenDOAR data with Google Maps and repository growth charts from ROAR, developed by Stuart Lewis of the University of Aberystwyth, Wales http://maps.repository66.org/ LibraryThing lofiAPI: MSU Libraries (ETD, RMT) MSU Library Lifestream: RSS services (Twitter, del. icio.us, last.fm, MSU Library Blog) TERRApod Youtube admin Google Booksearch Samples from the crowd...
  8. 8. How to... Components 1. Database Engine 2. Scripting Language Specifics 1. Apache 2. MySQL 3. PHP
  9. 9. Why? Single Source, Multiple Endpoints 1. Feed Readers 2. Google Sitemap 3. Remixed HTML 4. A9 OpenSearch Allow for the Remix 1. Share data 2. Repurpose for new applications 3. Make library data part of info flow
  10. 10. Last thoughts... This stuff is just beginning… Worldcat API Digital Library Federation API recommendation Library mashups are coming - there's just too much good data out there
  11. 11. Questions?
  12. 12. Getting Started Play in the sandbox – pick a service, study it Yahoo Developer Central http://developer.yahoo.com/ Amazon Web Services Developer Connection http: //developer.amazonwebservices.com/connect/ Google Code http://code.google.com/
  13. 13. Web Services - Sources AllCDCovers.com http://www.allcdcovers.com/api ISBNdb.com http://isbndb.com/docs/api/index.html OpenDOAR http://www.opendoar.org/tools/api.html arXiv.org http://export.arxiv.org/api_help/ * See ProgrammableWeb http://www.programmableweb.com/apis/directory
  14. 14. Terms: API What is an API? An application programming interface (or API) is a way for developers to access parts of a remote web site and integrate it with their own site. MSU Libraries Resources Example http://www.lib.montana.edu/resources/read.php?form=json&limit=25
  15. 15. Terms: Web Service What is a Web Service? Broader term Public interface (API) Provides access to data and/or procedures On a remote/external system (usually) Use structured data for data exchange (often XML)
  16. 16. Terms: Structured Data Structured data = XML and JSON Extensible Mark-up Language and Javascript Object Notation Flexible mark-up languages Lightweight and easy to parse Allow communication between disparate systems
  17. 17. Contact Information Jason A. Clark Head of Digital Access and Web Services Montana State University Libraries jaclark@montana.edu www.jasonclark.info 406-994-6801

×