Access2008 Presentation V3


Published on

Presentation on Evergreen/Conifer for Access 2008 in Hamilton, ON.

Published in: Education, Technology
  • Be the first to comment

  • Be the first to like this

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

No notes for slide

Access2008 Presentation V3

  1. 1. Evergreen and Conifer or... How to amaze your friends and astound your enemies by building a union catalogue on the cheap(ish) John Fink Digital Technologies Development Librarian McMaster University
  2. 2. My relationship with the ILS, 1995-2008:
  3. 3. ...
  4. 4. But first, for the uninitiated <ul><li>What is Evergreen? </li></ul><ul><li>It's an ILS that... </li></ul><ul><li>Is scalable... </li></ul><ul><li>Built on open standards... </li></ul><ul><li>Runs on stock hardware... </li></ul><ul><li>And is open source! </li></ul>
  5. 5. <ul><li>That sounds terrific. Why isn't everyone everywhere using this? </li></ul><ul><li>Open Source (again) </li></ul><ul><li>Many many different pieces == many many places to break. </li></ul><ul><li>Install process getting better , but... </li></ul><ul><li>New ways of doing things == learning curve... </li></ul><ul><li>...but... </li></ul>
  6. 6. Break the shell and you'll find magic.
  7. 8. But you knew that already, right? <ul><li>So what's Project Conifer? </li></ul><ul><li>It's a confederation of five institutions: </li></ul><ul><li>McMaster, Laurentian, Windsor (mid-2007) </li></ul><ul><li>Then NOSM and Algoma University (mid-2008) </li></ul><ul><li>...but probably nobody else (yet)... </li></ul><ul><li>With a single ILS install in Guelph. </li></ul><ul><li>...(Guelph?) </li></ul>
  8. 9. What Conifer is NOT: <ul><li>Provincially comprehensive </li></ul><ul><li>Official at any sort of OCUL-type level </li></ul><ul><li>Its own, separate entity </li></ul><ul><li>An OhioLINK-style resource sharing scheme </li></ul><ul><li>or... </li></ul><ul><li>Operational (May 2009!) </li></ul>
  9. 10. Step back, and breathe... <ul><li>Of course, now you're asking yourself... </li></ul><ul><li>...but hey, why would any one of you, let alone five of you, decide to ditch the ILS systems you have now which are working pretty well, or at least decently right now, and jump into something Completely Unknown? </li></ul><ul><li>well... </li></ul>
  10. 11. It's NOT unknown <ul><li>Examples of Evergreen installs: </li></ul><ul><li>Georgia PINES (~280 libraries) </li></ul><ul><li>BC SITKA (18 libraries) </li></ul><ul><li>Michigan Library Consortium (Welcome GRPL!) </li></ul><ul><li>The Indiana Open Source ILS Initiative </li></ul><ul><li>...and UPEI. </li></ul>
  11. 12. So it's proven, but... <ul><li>At the moment, it lacks what we would consider more ”academic” features, like acquistions, serials, reserves, and batch import/export. </li></ul><ul><li>These are due in with version 2.0 later this year. </li></ul><ul><li>And other things, like internationalization, a Z39.50 server, a better admin interface... </li></ul><ul><li>...these come in 1.4 (this month!) </li></ul>
  12. 13. At the risk of sounding like this guy:
  13. 14. Or (maybe) worse yet:
  14. 15. We're doing this because: <ul><li>All of us, in one form or another, have had proprietary software companies fail us; whether it's because the software or hardware is being end-of-lifed, and migration costs are exorbitant . </li></ul><ul><li>And nowadays, we're smart enough to take some measure of responsibility for the operation and development of our own software. </li></ul>
  15. 16. But really, we're afraid: <ul><li>Of being told we can do something but then having it taken from us </li></ul><ul><li>Of being locked into a platform that is dying a slow death due to corporate takeovers or an arbitrary technology shift. </li></ul><ul><li>Of dependencies. </li></ul>
  16. 17. tl;dr If you can't open it, you don't own it.
  17. 18. <ul><ul><li>So really, it's less a ”hey this software is free and we don't have to pay for it woo-hoo” kind of thing and more a ”holy cripes we need to take a little more interest in what, exactly, this piece of software – long the central kernel of the library – is doing.” </li></ul></ul>
  18. 19. Because it's not cheap – there are hardware and opportunity costs involved, and just about any change means at least some modicum of training, and a whole lot of headache.
  19. 20. But we at least have one advantage.. We (McMaster) are not planning on changing our patron interface – Endeca – and any reasonable discovery layer ought to function without too much hacking.
  20. 21. Ten years on?
  21. 22. One year later, they went out of business.
  22. 23. Image credits: Uncle Karl image courtesy of Wikipedia Stallman image courtesy of love/hate photo courtesy of [email_address] @ flickr: Coherent image courtesy of mrbill @ flickr: EG install image courtesy of G. Hill, K. Thornley: