Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Evergreen - Future of the ILS


Published on

Presentation done by the Evergreen team at the Future of the ILS symposium in Windsor

Published in: Business, Technology
  • thanq its really nice as well as useful to me in thinking about advancement comes together with think of which.... very nice work.... tanq for this.....
    Are you sure you want to  Yes  No
    Your message goes here

Evergreen - Future of the ILS

  1. 2. David Singleton, Deputy State Librarian Julie Walker, PINES Program Director Brad LaJeunesse, Systems Administrator Mike Rylander, Development Consultant
  2. 3. Georgia Systems PINES Systems
  3. 4. PINES Anticipated Growth
  4. 5. PINES Today <ul><li>Y2k project started in 1999 </li></ul><ul><li>44 public library systems </li></ul><ul><li>252 member libraries </li></ul><ul><li>123 counties </li></ul><ul><li>8.8 million items </li></ul><ul><li>1.6 million active cardholders from all 159 Georgia counties. </li></ul>
  5. 6. What Makes PINES Different? <ul><li>The PINES library card is free to any resident of Georgia, and may be obtained from any PINES library. </li></ul><ul><li>The PINES library card can be used at any PINES facility as if at the home library. </li></ul><ul><li>Materials may be returned to any PINES library. </li></ul>
  6. 7. What Makes PINES Different? <ul><li>Users may request materials delivered from any PINES library to local library, at no charge. </li></ul><ul><li>In FY06, over 452,000 loans between PINES libraries. </li></ul><ul><li>PINES libraries agree to a common set of policies, and procedures, with the goal that users have a consistent experience at any PINES library. </li></ul>
  7. 8. <ul><li>Executive Committee: Nine (9) elected representatives (Library Directors) from member library systems. </li></ul><ul><li>Function-specific subcommittees make policy recommendations. </li></ul><ul><li>Executive Committee meets quarterly and as needed. </li></ul>PINES Governance
  8. 9. What are the Benefits? <ul><li>For users: increased access to local library collections </li></ul><ul><li>For libraries: the State of Georgia assumes the costs of the automation system. </li></ul><ul><li>Access, not ownership, is the key. </li></ul><ul><li>Economy of scale: </li></ul><ul><li>PINES annual cost = approximately $1.6 million. </li></ul><ul><li>Individual library automation systems = over $15 million + approximately $5 million per year to maintain those systems. </li></ul>
  9. 10. Services from PINES Central <ul><li>Training for 1,400 PINES staff in libraries across the state. Training is conducted regionally to reduce travel demands on libraries. </li></ul><ul><li>Responsibility for printing and mailing of overdue notices for all PINES libraries </li></ul><ul><li>Helpdesk via phone, email or web, available 24 hours/day. </li></ul>
  10. 11. <ul><li>“ It SIGNIFICANTLY expands the choices of books and other materials available to me. I appreciate this so much because I live in a rural part of the state with a very small local library.” </li></ul><ul><li>“ Allowing books to be checked out from other libraries is WONDERFUL. This way, the Pines System is like one gigantic library making available a tremendous selection of books regardless of where the books are physically housed.” </li></ul>WHAT DO USERS LIKE BEST ABOUT PINES? Comments from the PINES User Survey
  11. 12. The Evergreen Project <ul><li>The 5-year software contract for PINES ended in June 2005. </li></ul><ul><li>2003-2004: PINES staff conducted a comprehensive survey of the library automation marketplace </li></ul><ul><li>At issue: the unique needs of a statewide consortium sharing a centralized database and utilizing a statewide library card. </li></ul><ul><li>Is the software driving the policy/procedure, or is the policy/procedure driving the software? </li></ul>
  12. 13. The Evergreen Project <ul><li>What do PINES libraries need? </li></ul><ul><ul><li>Enterprise-class relational database </li></ul></ul><ul><ul><li>Flexible system administration </li></ul></ul><ul><ul><li>Granular permissions structure </li></ul></ul><ul><ul><li>A complex holds matrix </li></ul></ul><ul><ul><li>Ability to treat member libraries as individual entities </li></ul></ul><ul><ul><li>Reports designed to correspond to annual reporting requirements </li></ul></ul>
  13. 14. The Evergreen Project <ul><li>Evergreen Integrated Library System was developed using Open Source software. </li></ul><ul><li>Released under General Public License (GPL). </li></ul><ul><li>Alpha release (Online public access catalog, Cataloging, Circulation) debuted in July 2005. </li></ul><ul><li>Beta release in early 2006. </li></ul><ul><li>All PINES libraries migrated to Evergreen software on September 5, 2006. </li></ul><ul><li>Transactions, user records, and item records were migrated from the former system. </li></ul>
  14. 15. Cost Comparison 2 4 Local Tech Staff $200,000/yr $0 Software Licensing $200,000/yr (included, 3 years) Hardware Support $1,500,000 $350,000 Server Hardware Vendor ILS Evergreen
  15. 16. Fringe Benefits <ul><li>We’re self-sustaining and control our own destiny. </li></ul><ul><ul><li>We decide on development priorities. </li></ul></ul><ul><ul><li>No more difficulty trying to convince a vendor to develop important features for us (a minority customer in some ways). </li></ul></ul><ul><li>The users of the software have direct access to the developers. </li></ul>
  16. 17. Evergreen Online Catalog Features <ul><li>Streamlined searching from a single search box. </li></ul><ul><li>Google-like spell-checking and search suggestions. </li></ul><ul><li>Ability to select specific material formats from the online catalog’s front page . </li></ul><ul><li>Added content, including book cover images, reviews, and excerpts. </li></ul><ul><li>Randomized holds that include geographic location as a factor. </li></ul><ul><li>Scalability in anticipation of PINES growth. </li></ul>
  17. 18. Evergreen Online Catalog Features <ul><li>In ‘My Account’, patrons can: </li></ul><ul><ul><li>change personal login name; </li></ul></ul><ul><ul><li>change password; </li></ul></ul><ul><ul><li>place, cancel, and view holds; </li></ul></ul><ul><ul><li>modify how they would like to be alerted of available holds; </li></ul></ul><ul><ul><li>view fines; </li></ul></ul><ul><ul><li>view address information; and </li></ul></ul><ul><ul><li>view Bookbags (and share them) </li></ul></ul>
  18. 19. Let’s take a look… <ul><li> </li></ul>
  19. 20. Evergreen Core Technologies <ul><ul><li>Database: PostgreSQL </li></ul></ul><ul><ul><li>Logic/glue languages: C and Perl, Javascript </li></ul></ul><ul><ul><li>Webserver: Apache mod_perl, C modules </li></ul></ul><ul><ul><li>Client side software: XUL </li></ul></ul><ul><ul><li>Server operating system: Linux </li></ul></ul><ul><ul><li>Server hardware: x86-64 </li></ul></ul><ul><ul><li>Messaging core: Jabber (Ejabberd) </li></ul></ul>
  20. 21. Evergreen Design <ul><li>Server-side software is designed to run on inexpensive commodity hardware with Linux as the operating system. </li></ul><ul><li>The software is designed to run in a clustered environment, giving it enterprise-level high availability and failover. </li></ul><ul><li>Evergreen's staff client is cross-platform (Windows, Mac, Linux). </li></ul>
  21. 23. Open Application Plaform <ul><li>The traditional ILS is </li></ul><ul><li>A catalog </li></ul><ul><li>An OPAC </li></ul><ul><li>A circulation system </li></ul><ul><li>Cataloging tools </li></ul><ul><li>We wanted more – we wanted a platform </li></ul>
  22. 24. Open Application Platform <ul><li>We need a framework that </li></ul><ul><li>is easy to cluster </li></ul><ul><li>takes care of all the dirty work </li></ul><ul><li>has very low overhead </li></ul><ul><li>makes writing applications simple </li></ul><ul><li>is built on open, standard protocols </li></ul><ul><li>Given this we can create components as they are needed to provide solutions on demand – we don't need to anticipate every problem! </li></ul>
  23. 25. OpenSRF: Features and Benefits <ul><li>We built a framework that </li></ul><ul><li>can trivially scale from a single server to hundreds in a tiered, redundant fashion </li></ul><ul><li>manages everything but the application logic, abstracting away everything to a consistent set of method calls </li></ul><ul><li>can easily handle hundreds of transactions per second, per server without any administrator tuning of the underlying components </li></ul><ul><li>turns writing applications, including entire ILS modules, into a matter of translating business logic into a set of simple Perl or C routines </li></ul><ul><li>Leverages existing open standards and open source software to avoid both duplication of effort and component lock-in </li></ul>
  24. 26. OpenSRF: The Pieces <ul><li>OpenSRF consists of </li></ul><ul><li>A Jabber server – PINES uses eJabberd, and has tested jabber2d and an in-house custom server </li></ul><ul><li>The OpenSRF Router – provides application load balancing and failover services </li></ul><ul><li>OpenSRF Application Infrastructure – libraries and tools that turn simple business logic functions into seamless applications </li></ul><ul><li>OpenSRF Gateway – an Apache web server plugin that turns URLs into OpenSRF requests, and OpenSRF reponses into web-accesible content </li></ul><ul><li>OpenSRF DocGen – serves API documentation from the OpenSRF Introspection Service </li></ul>
  25. 27. Benefits to Evergreen <ul><li>Dramatically decreased the time to go from service prototypes to production implementations </li></ul><ul><li>Allows developers to focus on core ILS issues </li></ul><ul><li>Increase capacity as needed using any source – no hardware vendor lock-in! </li></ul><ul><li>No single point of failure for any critical system or service </li></ul><ul><li>Rolling Upgrades – no need to take the system offline to upgrade backend services! </li></ul>
  26. 28. Where Do We Go from Here? <ul><li>Migration of the six library systems waiting to become part of PINES. </li></ul><ul><li>Develop the Acquisitions and Serials modules. </li></ul><ul><li>Work with others on a protocol to share information across automation systems (Open NCIP). </li></ul><ul><li>Develop the children's portal for the online catalog. </li></ul>
  27. 29. Where Do We Go from Here? <ul><li>Implement online bill pay for users. </li></ul><ul><li>Enhance social aspects of the catalog: user ratings, reviews, and comments. </li></ul><ul><li>Complete the Spanish translation for the online catalog. </li></ul>
  28. 30. Where do we go from here? <ul><li>Deep links into the GALILEO databases. </li></ul><ul><li>Online catalog that can be used on mobile devices. </li></ul><ul><li>Possible partnerships with other institutions. </li></ul>
  29. 31. PINES online catalog: Evergreen development:
  30. 32. David Singleton [email_address] Julie Walker [email_address] Brad LaJeunesse [email_address] Mike Rylander [email_address]