+ All Categories
Home > Education > Conifer/Evergreen -- OLA 2009

Conifer/Evergreen -- OLA 2009

Date post: 08-Jul-2015
Category:
Upload: john-fink
View: 790 times
Download: 1 times
Share this document with a friend
Description:
Presentation given to OLA 2009 on Conifer and Evergreen
39
Project Conifer: Evergreen Library System for Ontario Universities John Fink Digital Technologies Development Librarian McMaster University
Transcript
Page 1: Conifer/Evergreen -- OLA 2009

Project Conifer: Evergreen Library System for Ontario Universities

John FinkDigital Technologies Development Librarian

McMaster University

Page 2: Conifer/Evergreen -- OLA 2009

My relationship with the ILS, 1995-2009:

Page 3: Conifer/Evergreen -- OLA 2009

Why do I love the ILS?

It helps make our resources ubiquitous and available or......never underestimate the power of being able to do things in your pajamas.

Page 4: Conifer/Evergreen -- OLA 2009

It handles a lot of what we typically get in our heads when we think library, even though the nature of the library – especially in academia – has changed dramatically over the last fifteen

years or so, with the rise of databases, websites, reference services over IM and SMS,

things like that.

Page 5: Conifer/Evergreen -- OLA 2009

But about fifteen years ago, when everything was changing, just around the time I bought a

jar of hot sauce over the Web and thought holy crap, this is the future, libraries pretty much

were their physical collections – those books and magazines – and had been since, well, the

invention of libraries.

Page 6: Conifer/Evergreen -- OLA 2009

And the ILS, then, was a major thing.

Page 7: Conifer/Evergreen -- OLA 2009

It ran on Important Machines:

Page 8: Conifer/Evergreen -- OLA 2009
Page 9: Conifer/Evergreen -- OLA 2009

And it cost a lot of money.

Page 10: Conifer/Evergreen -- OLA 2009

And we paid. We paid because we couldn't do it ourselves, and the benefits that the ILS gave us

over the card catalogue was wonderful.

Page 11: Conifer/Evergreen -- OLA 2009

And even though the money was a lot, the issue isn't really money...

Page 12: Conifer/Evergreen -- OLA 2009

Libraries and librarians like open and free standards and working with other libraries and the public.

That's why we made interchange standards like MARC, Z39.50 and SRU, and, oh yeah, loan all those books out to people with no upfront costs.

Page 13: Conifer/Evergreen -- OLA 2009

But to proprietary companies, interoperability is largely undesireable...

... because it means you have mobility... ...and if you have mobility...

Page 14: Conifer/Evergreen -- OLA 2009

You might go somewhere.

Page 15: Conifer/Evergreen -- OLA 2009

But first, for the uninitiated

What is Evergreen? It's an ILS that... Is scalable... Built on open standards... Runs on cheap-ish hardware... And is open source!

Page 16: Conifer/Evergreen -- OLA 2009

What is Open Source?

Page 17: Conifer/Evergreen -- OLA 2009

Why is Open Source important to us?

It's not because it's free. ...well, not just because it's free... ...because it's open... ...and open means it can't be taken away from

you.

Page 18: Conifer/Evergreen -- OLA 2009

If you can't open it, you don't own it.

Page 19: Conifer/Evergreen -- OLA 2009

That sounds terrific. Why isn't everyone everywhere using this?

Fear of open source Many many different pieces == many many

places to break. Install process getting better, but... New ways of doing things == learning curve...

Page 20: Conifer/Evergreen -- OLA 2009
Page 21: Conifer/Evergreen -- OLA 2009

So what's Project Conifer? It's a confederation of five institutions: Laurentian, Windsor, and McMaster (mid-2007) Then NOSM and Algoma University (mid-2008) ...but probably nobody else (yet)... With a single ILS install in Guelph. ...(Guelph?)

Page 22: Conifer/Evergreen -- OLA 2009

What Conifer is NOT:

Provincially comprehensive Official at any sort of OCUL-type level Its own, separate entity An OhioLINK-style resource sharing scheme or... Operational (May 2009!)

Page 23: Conifer/Evergreen -- OLA 2009

Step back, and breathe...

Of course, now you're asking yourself... ...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?

well...

Page 24: Conifer/Evergreen -- OLA 2009

It's NOT unknown

Examples of Evergreen installs: Georgia PINES (~280 libraries) BC SITKA (18 libraries) Michigan Library Consortium The Indiana Open Source ILS Initiative UPEI

Page 25: Conifer/Evergreen -- OLA 2009

So it's proven, but...

At the moment, it lacks what we would consider more ”academic” features, like acquistions, serials, reserves, and batch import/export.

These are due in with version 2.0 in mid-May, 2009.

Page 26: Conifer/Evergreen -- OLA 2009

We're doing this because:

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.

And nowadays, we're smart enough to take some measure of responsibility for the operation and development of our own software.

Page 27: Conifer/Evergreen -- OLA 2009

But really, we're afraid:

Of being told we can do something but then having it taken from us

Of being locked into a platform that is dying a slow death due to corporate takeovers or an arbitrary technology shift.

Of dependencies.

Page 28: Conifer/Evergreen -- OLA 2009

So really, it's less a ”hey this software is free and we don't have to pay for it” kind of thing and more a ”we need to take a little more interest in what, exactly, this piece of software – long the central

kernel of the library – is doing.”

Page 29: Conifer/Evergreen -- OLA 2009

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.

Page 30: Conifer/Evergreen -- OLA 2009

Headache?

Page 31: Conifer/Evergreen -- OLA 2009

So where's the setback?

McMaster won't, as it turns out, be migrating with Conifer in May 2009.

Page 32: Conifer/Evergreen -- OLA 2009

”But wait...”

”But waitaminit,” I hear you say... ”...He wasted X number of minutes saying how

awesome Evergreen is, and now they're not even migrating?...”

...Well, like Facebook sez...

Page 33: Conifer/Evergreen -- OLA 2009

”It's Complicated.”

Page 34: Conifer/Evergreen -- OLA 2009

We decided in the end that features like recalls, acquisitions, serials, and batch import/export were too important, too necessary for our functionality to go ahead without them in May.

Early adopters – like UPEI – have unusual workarounds that won't scale for us.

We are, in part, a victim of our size and our (comparative) lack of urgency so we're planning on...

Page 35: Conifer/Evergreen -- OLA 2009

...Migrating when our feature requirements are met...

...running a local install that will potentially share records with Guelph...

...still contribute time and resources to Project Conifer.

Page 36: Conifer/Evergreen -- OLA 2009

Our ship is sinking, it's just not sinking quite as fast.

Page 37: Conifer/Evergreen -- OLA 2009

Ten years on?

Page 38: Conifer/Evergreen -- OLA 2009

One year later, they went out of business.

Page 39: Conifer/Evergreen -- OLA 2009

Image credits:

love/hate photo courtesy of fr@ns @ flickr: http://www.flickr.com/photos/fiji_art/2414595461/

Coherent image courtesy of mrbill @ flickr: http://flickr.com/photos/mrbill/29870228/


Recommended