Libr243 Future Trends Ms


Published on

Published in: Business, Technology
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Libr243 Future Trends Ms

  1. 1. Future Trends in Library Systems <ul><ul><li>SLIS LIBR243/Hiles </li></ul></ul>
  2. 2. Future Trends in Library Systems <ul><ul><li>1. “Unbundling” the ILS </li></ul></ul><ul><ul><li>2. Entering the computing mainstream </li></ul></ul><ul><ul><li>3. Being where our patrons are looking </li></ul></ul><ul><ul><li>4. Virtualizing systems/Utility computing </li></ul></ul>
  3. 3. 1. Unbundling the ILS <ul><ul><li>In the beginning was the database… </li></ul></ul>
  4. 4. 1. Unbundling the ILS <ul><li>Part 1. “Bundling” the ILS </li></ul><ul><li>After the first steps towards automating circulation and inventory control, vendors sought to leverage the expensive proprietary systems by adding functionality through new modules </li></ul>
  5. 5. 1. Unbundling the ILS <ul><li>Databases (Bibliographic/Patron)‏ </li></ul><ul><li>Circulation </li></ul><ul><li>Acquisitions </li></ul><ul><li>Serials </li></ul><ul><li>Reserves/Holds </li></ul><ul><li>Cataloging </li></ul><ul><li>OPAC </li></ul><ul><li>ERM </li></ul><ul><li>Discovery Tools </li></ul>
  6. 6. 1. Unbundling the ILS <ul><li>The Result Was Seldom the “Best of Breed”. </li></ul>
  7. 7. 1. Unbundling the ILS <ul><li>Part 2: ”Unbundling” </li></ul><ul><li>Split off OPAC/Discovery Tool: </li></ul><ul><li>NCSU Endeca-based product </li></ul><ul><li>Scriblio WordPress-based product </li></ul><ul><li>VuFind Solr-based product </li></ul><ul><li>WorldCat Local </li></ul>
  8. 8. 1. Unbundling the ILS <ul><li>Split off Serials/ERM </li></ul><ul><li>Verde </li></ul><ul><li>HERMES </li></ul>
  9. 9. 1. Unbundling the ILS <ul><li>Split off Acquisitions </li></ul><ul><li>Peoplesoft </li></ul><ul><li>SAP </li></ul>
  10. 10. 1. Unbundling the ILS <ul><li>Split off Circ? </li></ul><ul><li>Student Management Systems </li></ul>
  11. 11. 1. Unbundling the ILS <ul><li>Split off functions which are duplicated by other software we either are using or could use </li></ul><ul><li>Simplify moving core inventory functions if need to </li></ul>
  12. 12. 1. Unbundling the ILS <ul><li>Systems Issues— </li></ul><ul><li>Sustainability – no single “turn-key” vendor, so integration issues. </li></ul><ul><li>Support companies/consultants – where available </li></ul><ul><li>Open Source community – need to build relationships & skills set </li></ul>
  13. 13. <ul><ul><li>The OPAC becomes just another content management system: </li></ul></ul><ul><ul><li>Endeca-based </li></ul></ul><ul><ul><li>Solr/Lucene-based </li></ul></ul>2. Entering the computing mainstream
  14. 14. <ul><ul><li>Now the “OPAC” can be web-enabled, spiderable, and searchable </li></ul></ul>2. Entering the computing mainstream
  15. 15. <ul><ul><li>More importantly, the “OPAC” can grow and develop at the pace of the rest of the web </li></ul></ul>2. Entering the computing mainstream
  16. 16. <ul><ul><li>Data and metadata standards can go mainstream, too. Libraries can take advantage of the work of the publishing and retailing industries. </li></ul></ul>2. Entering the computing mainstream
  17. 17. <ul><ul><li>Other “unbundled” components can also be “best-of breed”. Ordering, payments, financial matters could be input directly to institutional accounting systems (no error-ridden manual reconciliation steps)‏ </li></ul></ul>2. Entering the computing mainstream
  18. 18. <ul><ul><li>Importantly-- the library will need fewer “peculiar” systems (maybe none at all)‏ </li></ul></ul><ul><ul><li>The server infrastructure could consist of mainstream software on mainstream hardware shared with other parts of our organizations (campus-wide, city-wide, county-wide)‏ </li></ul></ul>2. Entering the computing mainstream
  19. 19. <ul><ul><li>There's a old joke about a cop meeting a drunk who was crawling around under a street light one night. </li></ul></ul><ul><ul><li>“ What are you doing?”, the cop asked. </li></ul></ul><ul><ul><li>“ I'm looking for my car keys”, said the drunk. </li></ul></ul><ul><ul><li>“ You sure you lost them here?”, </li></ul></ul><ul><ul><li>asked the cop. </li></ul></ul><ul><ul><li>“ I don't know, but it's too dark </li></ul></ul><ul><ul><li>to look anywhere else.” </li></ul></ul>3. Being where our patrons are looking
  20. 20. <ul><ul><li>Not that our patrons are drunk, but whole generations are growing up expecting their information needs to be met in specific ways. If libraries (just one of many potential suppliers) are not where they are used to looking, they won't find us. </li></ul></ul>3. Being where our patrons are looking
  21. 21. <ul><ul><li>Good example: </li></ul></ul><ul><ul><li>Miami University creates a Facebook app for it's catalog </li></ul></ul><ul><ul><li> </li></ul></ul>3. Being where our patrons are looking
  22. 22. <ul><ul><li>Bad example (for libraries): </li></ul></ul><ul><ul><li>Amazon's AskKindleNowNow </li></ul></ul><ul><ul><li>The ability to get live answers to reference questions (for a fee) from a hand-held device that also gets you books. Who's business model does that look like? </li></ul></ul>3. Being where our patrons are looking
  23. 23. <ul><ul><li>Virtualization hits the mainstream, allowing: </li></ul></ul><ul><ul><li>Hardware independence/optimization </li></ul></ul><ul><ul><li>Operating system “best of breed” </li></ul></ul><ul><ul><li>Virtual appliances </li></ul></ul>4. Virtualizing systems/Utility computing
  24. 24. <ul><ul><li>Hardware independence/optimization </li></ul></ul><ul><ul><li>A software layer enables multiple virtual systems to share a single physical machine. </li></ul></ul><ul><ul><li>Virtual Servers can be created and moved where needed to optimize server utilization. </li></ul></ul><ul><ul><li>Greater utilization = fewer servers = $$ saved </li></ul></ul>4. Virtualizing systems/Utility computing
  25. 25. <ul><ul><li>Operating system “best of breed” </li></ul></ul><ul><ul><li>Virtual servers can run different operating systems from the host system. </li></ul></ul><ul><ul><li>Linux guest servers can reside on Microsoft host servers, or vice-versa. </li></ul></ul><ul><ul><li>A lot of the new library software is Linux-based, so this is a way out of the Microsoft ghetto many of us have to work in </li></ul></ul>4. Virtualizing systems/Utility computing
  26. 26. <ul><ul><li>Virtual appliances </li></ul></ul><ul><ul><li>Fully pre-installed and pre-configured application and operating system environments </li></ul></ul><ul><ul><li>Simplify deployment of open source ILS systems (no installation hassles or stack maintenence)‏ </li></ul></ul>4. Virtualizing systems/Utility computing
  27. 27. <ul><ul><li>Utility Computing </li></ul></ul><ul><ul><li>Metered computer provisioning (like an electric utility), from a third party provider that can scale up or down with demand </li></ul></ul><ul><ul><li>Customers can plug into the computing grid just as they would plug a power cord into the electric grid </li></ul></ul>4. Virtualizing systems/Utility computing
  28. 28. 4. Virtualizing systems/Utility computing <ul><ul><li>Economies of scale – Large Data Centers being built by: </li></ul></ul><ul><ul><li>Sun </li></ul></ul><ul><ul><li>Amazon </li></ul></ul><ul><ul><li>Google </li></ul></ul><ul><ul><li>Microsoft </li></ul></ul>
  29. 29. <ul><ul><li>Next week: </li></ul></ul><ul><ul><li>What are the career implications of all this? </li></ul></ul>Future Trends in Library Systems
  30. 30. Future Trends in Library Systems <ul><li>Resources: </li></ul><ul><li> feed at: </li></ul>