some more open source ubuntu help for libraries

School Library Journal this month has a test drive of Edubuntu — the Ubuntu distribution that was created for use in classrooms.

When I installed Edubuntu on three different generations of laptops, each with different wireless cards, I was astounded at how easy it was. In every case, the first thing Edubuntu did was sniff the wireless card, install it, and hop right onto the Net. Plus, every display was configured and sized just right, every touch pad and sound card functioned, hardware just worked.

Jim Mann is the Technology Coordinator at the Greene County Public Library in Xenia Ohio. I met him when I was in Ohio last spring. He has created a series of very professional videos on YouTube on how to use Eudbuntu in libraries to maximize the hardware you have especially with old and outdated computers. These videos are very easy to understand and super clear.

We’re going to show you how to turn a pile of junk into useful inexpensive literally free computers that you can use in your library or that you can use with a public service group or with a school.

wedging open source into your library effectively

It’s great to mess around with open source tools if you’re geeky and techie. However what if, like many small libraries and solo librarians, you’re not? PALINET has been looking at open source tools and I really really like what PALINET is doing to make using an open source ILS a genuine option for their member libraries. Way to actually address the problem PALINET, nice job.

PALINET is aware that not all of our members have the technical support or skills necessary to install or test the open source applications that are currently available. We’re looking at a number of ways to address this issue, but we’ve taken two initial steps already. First, a member Technology Caucus has begun regular discussions of open source software tools in monthly meetings. Yesterday, a group of library developers met at the PALINET offices in Philadelphia to install test copies of Koha and Evergreen for evaluation and comparison. It’s my hope that we’ll be able to put together a couple of really clean, well integrated, model systems, which will demonstrate the kind of functionality that is possible with these open source ILS solutions.

[wilt]

quickie Ubuntu update

printer + internet success!

So it’s been a while since I checked in from the Ubuntu installs at the library. Life intervened in a ton of ways. I went back over to the library today. I spent most of my time helping a Ukranian artist woman wade through the 250 emails in her inbox spanning almost two years. Every time she’d see a lost job opportunity or a note from a friend from eight months ago she’d say "see, this is why I have to know this, I lose work not knowing this…" I had to agree to a point but also mentioned that checking her email — however that needed to happen — more than once every 18 months was probably part of it.

So, I was in prime form when I went downstairs to check on the Ubuntu machines. The handyman had installed the ethernet drop from upstairs and I had limited time. This is what I did in about 20 minutes.

– made basic user accounts on each machine and changed the password on the admin accounts from the one I put on the YouTube video
– Set up the desktop for that account to have Firefox and OpenOffice on it (for now, we’ll move to games and IM once this is established as working)
– Plugged both computers into the switch I got. Hey check that out, they’re on the Internet. That was simple.
– Plugged the printer into one of them (HP 6100 series all on one blah) and went through the install printer routine. Hey look IT JUST WORKS, and prints.

Now one of the machines prints, both of them are on the internet, they’ve got a non-admin account on both of them and a locked down admin account with a new password. Next time I’ll do software updates and get the other printer working via the network, flesh out the desktops some and write some documentation. Woo! (crossposted from Flickr)

Open Source Software in Libraries

Casey Bisson has written a Library Technology Reports issue on Open Source Software in Libraries with a chapter by yours truly. I got to install and run Mac and Windows versions of the more popular desktop open source applications and take screenshots and make recommendations. Of course it’s not hard to recommend something like Firefox with all its sexy add-ons and Greasemonkey scripts, but you might not know that VLC is a pretty good media player, or that for advanced users Gimp can do a lot of what Photoshop does for no cost. Now if we can just get our style guides properly updated to not suggest hyphenating it all the time, we’ll be golden.

accomplishments, small and large

So last week I helped one of the small libraries I worked with get their in-house library catalog actually online, like on the web. They use Follett and had to pay some ungodly amount of money for the “web connector” software to make this happen. The process involves installing a fairly non-standard web server onto whatever your server is and then using it as the interface to your existing Follett install. The manual says you need to have a static IP address to make this work and the cable company they use for Internet won’t give them one. So, we had to do a little haxie magic using DynDNS, a special port redirect in the router, and a little app that lives on the server and broadcasts its current IP address to the DNS server. I had an idea that this would work but wasn’t totally sure, so we tried it. Other than that, my basic approach was “I am not a good cook but I can follow a decent recipe” which is what we did for the install.

When I say “we”, I mean me and my friend Stan who is a local IT guy who comes with me on some of these more complicated projects for the cost of lunch and does all the typing while I answer questions and explain what’s going on. The software install took all of fifteen minutes but the Q and A session took nearly an hour. As it stands they’re probably still going to use the local version of the OPAC in-house just in case the Internet goes down. I’m not sure I understand this reasoning and told them so. I’m as cautious as the next person as far as having a Plan B for most catastrophic situations, but I worry that if you only roll out the most bulletproof solutions, you wind up never trying new things and you live in fear that you haven’t tested everything rigorously enough. This sort of fear, uncertainty and doubt means going with large-scale tried and true solutions and is a definite impediment to getting libraries to work with open source. Additionally, with the perpetual betaness of a lot of 2.0 tools, anyone can muster up a reason to say no to them. I’m still always looking for the angle that will make people say “yes.”