http://www.flickr.com/photos/bindermichi/3473495065/ For libraries, OS is new and cutting edge and cool.
http://www.flickr.com/photos/90146003@N00/666491202/ New is exciting, but change always brings a little FUD. A little FUD (like a little cheese) is a good thing - it’s how we know what kinds of questions to ask and what people need extra assurance about. A lot of FUD (unlike a lot of cheese) is what we want to avoid.
http://www.flickr.com/photos/dayataglance/2282457985/ So, how we combat FUD and built excitement depends on who we’re working with. We’re a consortium of public and school libraries and we’re working with these four small development partners before we bring up the rest of our libraries.
http://www.flickr.com/photos/sixmilliondollardan/3488012638/sizes/l/ our members range from small public libraries to suburban school libraries to city libraries. their patrons have online accounts and expectations of staff and patrons are high. they want, need and deserve a better ILS.
http://www.flickr.com/photos/zach_manchester/2295839628/ Our dev partners are small and don’t have public OPACs. They’re open to trying something REALLY new. this is a bigger change for them than it is for our members, but it will be a very easy sell to the public (search for books from home is a no brainer and they won’t have any “your account signin has changed to contend with). This will be a huge leap forward.
http://www.flickr.com/photos/practicalowl/392894653/ We’re going to turn them into mad ILS scientists.
The advantage of having tiny libraries as dev partners: beginner’s mind. library technology has been the tail wagging the dog for so long, it’s helpful to have fresh perspective on what an ILS ought to do and how.
http://www.flickr.com/photos/leecullivan/2098453701/ As we work with the dev partners, we’re finding that we need to keep unwinding technology from policy. For small libraries that haven’t had the technology to offer certain services, it can be unclear what’s policy-driven and what’s tech-driven. For libraries that have been enmeshed with an ILS, that distinction is also unclear, so this is good practice for the big migration and can help us shape our development requests.
How's it Going?
An open source puzzle How the pieces all fell into place Front Row (left to right): Ben Shum- Software Coordinator, [email_address] Melissa Lefebvre- Project Manager, [email_address] Kate Sheehan- Implementation Coordinator, [email_address] Back Row (left to right): Amy Terlaga- Assistant Director, [email_address] Mike Simonds- CEO, [email_address]
Reasons to explore open source <ul><li>Open source is more in keeping with the mission of Bibliomation because it is the ultimate resource sharing model since software enhancements are developed collectively by those using the system; </li></ul><ul><li>Open source allows for local control ; open source protects Bibliomation from the unpredictability of vendor-owned commercial systems; </li></ul><ul><li>Open source can facilitate greater cooperation among library networks in Connecticut and allow for improved interfaces; </li></ul><ul><li>Open source would allow Bibliomation to expand other services. </li></ul>