This document discusses cloud computing and its potential applications for libraries. It begins by defining cloud computing and providing examples. It then discusses the benefits of cloud computing for enterprises and libraries, including cost savings, scalability, and the ability to focus on core services. The document outlines some ideas for applying cloud computing architecture to library management services. This would include building services around infrastructure, data, and community. It envisions a cooperative platform that allows libraries to develop and share applications. The platform could support collaboration and innovation across libraries.

1. Bibliotheken en cloud computing Annette Dortmund Product Manager OCLC

3. Cloud Computing for Libraries

5. Cloud Computing – What is it? A style of computing in which scalable and elastic IT-enabled capabilities are delivered as a service to external customers using Internet technologies. -Gartner Group Simple: Web-based applications with shared data and services.

6. Cloud Computing - examples A style of computing where scalable and elastic IT-related capabilities are provided 'as a service' to customers using Internet technologies. -Gartner Group Simple: Web-based applications with shared data and services. Infrastructure Platform Applications Services KPMG

8. Why Cloud Computing for enterprises? Subscribe to high quality services when / as long as needed Choose best value, not pieces of technology Save costs on IT infrastructure & management Improve service quality (performance, availability, …) Improve visibility and accessibility of the service Focus on core business, grow, innovate Collaborate, Aggregate & Share Data & Services

9. Challenges connected with Cloud Computing Data security & privacy, data ownership & exit options Scalability, Reliability and Performance of the Service Interoperability with external Services Compliance with legal standards (national, EU & international), lack of appropriate standards … http://blog.marinetelecom.net/2009/10/

12. data integrity and security

13. service availability

14. service interoperability

15. legal issues / contract templates

16. Increase public acceptance of cloud based solutions

19. Libraries and Cloud Computing

20. Changing demand

21. ChangingCollections

23. Libraries are changing rapidly

24. Cost & time requirements are exploding

26. Libraries and Cloud Computing Cloud based library services could bring the power of library cooperation to core library management Libraries will be freed to focus on innovation

27. Why Cloud Computing for enterpriseslibraries? Subscribe to high quality services when / as long as needed Choose best value, not pieces of technology Save costs on IT infrastructure & management Improve service quality (performance, availability, …) Improve visibility and accessibility of the service Focus on core business, grow, innovate Collaborate, Aggregate & Share Data & Services

28. Cloud Computing for Libraries SomeIdeas on Architecture

29. Successful on the web (web-scale) Infrastructure Data Community

30. Libraries and Web-Scale? Infrastructure Data Community

31. Building Web-Scale for / with Libraries Infrastructure Data Community

32. Key principles of a cooperative platform Data richness: Offer data pools and integrated workflows for all purchased, licensed and digital content Collaboration: Share data and services with other libraries & partners in a controlled way Designed for the cloud: Responsive, massive scalable, highly fault tolerant, suitableforpublicconsumption

33. Key principles of a cooperative platform Openness: Support interoperability between cloud based solutions, with library-developed or 3rd party applications / services through APIs, incl. exit options Extensibility: Platform can be extended by applications, provided by supplier, libraries or partners

34. Design for Web-Scale Goals Architecture Features Responsive Service Oriented Architecture Judicious Caching Partition by data and domain Embrace Open Standards Massively Scalable Network savvy APIs “Shared Nothing” Architecture Optimistic Locking Stateless Services Highly Layered Asynch. Transactions Highly Fault Tolerant Versioned APIs Discoverable Services Data Redundancy Replication & Failover Suitable for Public Consumption Avoid Distributed Transactions Temporary data inconsistency

35. Design for Web-Scale Goals Architecture Features Responsive Service Oriented Architecture Judicious Caching Partition by data and domain Embrace Open Standards Massively Scalable Network savvy APIs “Shared Nothing” Architecture Optimistic Locking Stateless Services Highly Layered Asynch. Transactions Highly Fault Tolerant Versioned APIs Discoverable Services Data Redundancy Replication & Failover Suitable for Public Consumption Avoid Distributed Transactions Temporary data inconsistency

36. Public consumptionof WorldCat API WorldCat BasedApps Not necessarilylibraryorientedorgenerated! Example: „shoppingapps“ Top App: RedLaser

38. Compareprices

39. Libraries arelistedin additiontobookshops

40. Check libraryaddress,phonenumbers, openinghours, orgoto online OPAC / website All mobile

41. A Service Platform With such an architecture – discoverable services and a platform concept –, can libraries develop their own custom applications for library management activities. In addition, they can expose and share those applications as Web services on the platform for other libraries to use. They can innovate collectively.

42. The Open Extensible Platform:It’s the Good Stuff in the Middle!

44. A “toolbox” for developers that want to use OCLC services and data to build new or enhance existing applications

45. An “App Gallery”, through which libraries can easily share apps created by the community

46. App Store, plug-ins, etc.

48. “I want to build an app…” Trends from outside of the library realm… Feed into selection and acquisition decision-making… Trends within the library

49. “I begin by…” Searching for documentation and other information necessary to begin writing my app.

50. “Next I…” // build request $listURL = 'http://api.nytimes.com/svc/books/v2/lists/' . $listname . '.xml'; $listURL = $listURL . '?api-key=' . $NYT_API ; // go get the XML $xml = simplexml_load_file($listURL); $bookCount = count($xml->xpath('//results/book')); if ($bookCount > 0) { $list_title = $xml->results->book[0]->list_name; $list_date = $xml->results->book[0]->published_date; Build my app in my local development environment… And upload the app to the Platform.

51. Managing Apps on the Platform

52. Uploading an App to the Platform

53. Uploading an App to the Platform

55. Share innovative solutions with peers

57. Finding an App on the Platform

58. A Sample Platform App Exactly what I want!

59. Using a Shared App in WMS

63. Discovery to Delivery : WorldCat Local

64. Circulation & Acquisitions

65. Knowledge Base Management

67. A Sea Change “For 25 years of library automation, we’ve had a choice of brand, and now we have a choice of kind.” -Marshall Breeding

68. “...companies distinguish themselves through defining different futures for their library customers.” — Marshall BreedingSCELC Colloquium 11 May 2010

69. Thank You! Comments? Questions? Just let me know, now or later. annette.dortmund@oclc.org