5. The Original Development Partners Library Legacy System # of Item Records Go Live Date Beacon Falls Library Follett Circulation/Web Collection Plus 16,000 March 3, 2010 Douglas Library, Hebron Spectrum 46,000 March 8, 2010 Jonathan Trumbull Library Athena 49,000 May 18, 2010 Slater Library SLIMS ILS 29,025 TBA July 1, 2010 ?? Windham Free Library No ILS 8,000 TBA July 1, 2010 ??
6. Juggling Act SirsiDynix Horizon Evergreen Web services Helpdesk The terrible twos Small Libraries Horizon Informational Portal Remote Patron Authentication Email Backup Logo Redesign Display Design PR Materials Documentation Project Management Meetings More Meetings Still more meetings
10. Go live. Bibliomation staff at library day of go live
11. Managing Transitions Bibliomation Staff Development Partners Vendor ILS Stand alone systems Windows to Linux ILS Migration Communication Communication Fear of change Fear of change Generation gap? Scary cutting edge
22. And then there was 11 Library Legacy System # of Item Records Go Live Date David M. Hunt Library No ILS 24,000 TBA Douglas Library, No. Canaan Follett Circ Plus 19,000 Oct 7, 2010 Lebanon Elementary School Follett 12,736 Aug 30, 2010 Lebanon High School Follett 15,000 Aug 25, 2010 Lebanon Middle School Follett 12,500 Aug 25, 2010 Sprague Library Athena 13,400 June 10, 2010
Bibliomation (in blue) is made up of 50 public libraries and 22 School libraries. Bibliomation is the largest consortium in CT. We are known as the geographically challenged network as we have libraries in all areas of the state.
Dynix logo: http://svn.codehaus.org/jetty/powered/images/dynix.jpg Bibliomation migrated to Dynix in 2004 to later see Sirsi merge (ie buy out) with Dynix. Soon we were told that Horizon would no longer be supported. We have no intention on migrating to Sirsi's Symphony product so we turned our attention to open source. We decided to migrate to Evergreen in 2011. But first we needed a “proof of concept” that open source wasn't scary or immature as some people thought. In enters our BibliOak Project.
In our plan, our BibliOak Project (in green) would be made up of small libraries who were willing to be “beta” testers of Evergreen. None of these libraries would normally have been able to afford our small library module pricing so our CEO, Mike Simonds, made them a deal they couldn't refuse. We got beta testers (guinea pigs) and they became part of our consortium.
First Meeting: basic information gathering session, including number of workstations, barcode formats, total bibs/items/patrons. General overview of process that will happen. Discuss go live dates. Web Demos: using a free online meeting tool called Mikogo www.mikogo.com Second Meeting: profiling meeting lasts anywhere between 2-4 hours where we ask everything about collection, how it behaves, including blocks, fines, loan periods, etc Go Live: 1-2 people from Bibliomation are at the library on go live date to support library and answer any problems/questions.
Not only did I have to manage transitions for Bibliomation staff, our development partners, but also for our member libraries who were feeling anxiety about the upcoming migration of our own. As hard as one tries, emails aren't read, information is forgotten and fear takes over....only if you let it.
early stages include shock and denial (refusing to believe what has happened and instead believing everything will be all right), guilt (at not having done or said more or for not being the decedent), and anger (at the decedent or at God).Later, one passes through the stages of acceptance (acknowledging what has happened) and moving on. Elisabeth Kübler-Ross http://blogs.techrepublic.com.com/10things/?p=257 Listservs, IRC chats, weekly meetings for staff, weekly and then bi-weekly calls with development partners after going live, web demos, blogs, Facebook pages were all of the means of communication we had open for our member libraries, staff, and development partners.
To ease the transition to the new system, we train the libraries about 1-2 weeks before they go live, leave hard copies of all manuals with them at that time, but we also post all documentation in the main entry page of the staff client along with phone numbers, email address, and forms that they will need in order to contact us. We also included instructional videos. One thing we discovered in training was that originally under Documentation heading was just Circulation, Cataloging, etc subheadings that would bring them to that part of the site. However, we discovered that staff were clicking on Circulation thinking it would bring them to Check in and Check out. So we added the word Manual in hopes that would lessen the confusion.
Copy NPSWF32.dll file into the program/plugins folder of Open Office.
When adding ahref tags to the index page, you must also include a <span style> class with color of blue in order for the page to show to the library staff that these things are hyperlinked. Without the span class added the hyperlinks will work but staff will only know when they hover their mouse over the word that it's a hyperlink.
Magic image http://www.whattofix.com/blog/archives/2008/10/livin-the-2040.php Black hole image: http://lgo.mit.edu/blog/drewhill/files/blackhole.gif Point finger image: http://www.weightymatters.ca/2009_10_01_archive.html Question mark image: http://www.yead.dk/conference/ Change image: http://www.mediabistro.com/agencyspy/original/change.jpg
![Melissa Lefebvre Bibliomation, Inc. [email_address]](https://image.slidesharecdn.com/trueconfessionsmelissalefebvre-100426104743-phpapp02/85/True-confessions-melissa-lefebvre-1-320.jpg)
