Join an online community with more than 350,000 members from 150,000+ organizations, where you can ask questions and get advice.
TechSoup hosts free weekly webinars on a variety of topics, from cloud computing to fundraising to social media and tech strategy.
Thinking about updating software, investing in new computers, or deploying a network or server? Our IT consulting services can help!
Close this window
Our free webinar was held on Thursday, October 21, 2010, 11:00 a.m. Pacific (Noon Mountain / 1pm Central / 2pm Eastern). This webinar covered specific open source tools (some of which you may not have heard of before!) that work well for libraries and the benefits and challenges associated with their use. Meadville Public Library uses open source software on 90% of their public access computers.
Cindy Murdock Ames, IT Services Director and Kyle Hall, the library's on-staff developer, shared recommendations for libraries considering open source software and how to get started successfully. Cindy has been using open source software for over 10 years, which has allowed the library to save licensing costs and have more control over its computing environment. The library uses open source tools for their websites, e-mail, Internet firewall, wireless router, proxying, filtering, and productivity software. They use thin clients for Internet access and Koha for the circulation and public catalogs.
View the archive online.
Top of Thread
Hi - I'm wondering is Kyle the only full-time developer working for the library system? Have you guys hired consultants here and there or was that mostly in the very beginning when you started going to open source? Great information! Thanks a lot for sharing.
Yes, I am the only developer for the library system. Cindy and I represent the entire IT department for our library system. AFAIK, we have only hired one consultant who trained Cindy very early in her IT career.
The following is a follow-up answer to a question asked during the webinar.
A: (Kyle) Each project is different, but Koha has a release manager that decides what gets merged and what doesn't. The release manager changes for each version of Koha, and is usually someone hired by one of the main Koha support vendors.