I’ve been writing more and travelling more this year in compensation for not doing teeny library work as much. One of my newer gigs has been as a reviewer for Rachel Singer Gordon’s new project The Tech Static, helping librarians do collection development for tech titles. I did a short review of a DVD/manual for people learning Access 2007. There’s already a lot of good content up there. Add it to your feed reader and check the meta category for more background information.
FreeGovInfo — whose guest blogger this month is none other than Ric Davis, acting Superintendent of Documents and Director of Library Services & Content Management at the U.S. GPO — points to a well-researchd report about vulnerable web browsers and the problems they pose. The article concludes that only 60% of web surfers use current versions of whatever browsing software they choose to use. This isn’t one of those “Hey, get Firefox!” articles, though it does point out that users of the Firefox browser are the most likely to be using a current version of the operating system — IE users are least likely — and part of the reason for this is that browser and plug-in version updating is built in to the system itself and turned ON by default. Read this article and then go make sure your library’s browsers are updated to the latest version. It’s important.
Understanding the nature of the threats against Web browser and their plug-in technologies is important for continued Internet usage. As more users and organizations depend upon these browser technologies to access ever more complex and distributed business applications, any threats to the underlying platform equate to a direct risk to business continuity and integrity.
The incident with the library computers being taken by law enforcement that I mentioned a few weeks back has now made a splash in the big media. Girl’s case had library, cops in privacy standoff. It’s interesting to see how the headline of the same AP article changes depending on who is using it. In another place it’s titled Library confrontation points up privacy dilemma or Kimball Library required warrant to view Brooke Bennett’s record’s
I’ve got one more privacy related post, but this is just a few things I’ve seen, noticed and liked. My goal for the summer was to catch up and stay caught up on RSS feeds, either through thinning my list, developing better habits or deciding to only follow friends and family, or only work people. I did a little of all of those and have been caught up for weeks now, even through ALA.
- Quick privacy-related link: why
- Speaking of Google, does anyone feel, like Sarah does, that they punk’d us?
- Ryan Dechamps tries out an EEE PC thinking about its potential use in a public library setting.
- Laura does some thinking out loud about the 2.0 aesthetic and what matters to us versus what matters to our patrons.
- David Lee King talks about Twitter best practices. Some very sensible suggestions for people who are newly starting out with Twitter, the how and the why.
- An older but good post from Lichen about a session she went to at NELA about library-wise IT proficiencies. That is, what proficiencies should we expect all library staff to have?
I went down to Massachusetts to do a few short talks. They were all very different and most were somewhat reworked versions of talks I’ve done before. I also went to a MetaFilter meetup and had BLTs with Casey. Thanks to everyone who hosted me while I was down in MA. Here are links to the presentations I did.
- Teaching Tech in Libraries for an in-service day at Cambridge Public Library
- OPACs – The Ugly, the Bad, and the Good
for an information technology class at Simmons West that I was a guest at
- Small Libraries and the Digital Divide & why it matters, a lot my contribution to an excellent panel about the Digital Divide that featured me, Pay Oyler a Simmons prof who went to train librarians in Vietnam, and Susan O’Connor who runs the Timothy Smith Network in Roxbury MA which I will post more about in another separate post.
Now I’m back to a week of teaching adult education classes and ripping plastic off the windows which I am sure will bring about a new ice age.
I gave a talk this afternoon for a one day workshop given by the Michigan Library Consortium about teaching technology in libraries. It was a keynote-ish talk so more “big picture” talking and less “this is how we do it.”
To that end, I did a new-from-the-ground-up talk about technology instruction and even wrote out notes for all of my slides so people who weren’t there could maybe follow along later. As anyone who has seen me speak knows, I tend to extemporanize (sp?) quite a bit so while the bones of the talk are in the notes, I also told a lot of stories about the libraries I work in and waved my hands around a lot. You can see the notes and a mov or pdf of the slides here: Teaching Tech in Libraries: what are we doing?
I’m still trying to find a good way to put slideware talks online without having to re-give the talk and toss it into Slideshare. Big thanks to all the folks from Michigan for being such a great audience and Twitterfolks for giving me some good advice. (go be Flickr friends with Kevin to see more (admittedly, not that fascinating) photos of this event)
Karen Coombs explains why web services isn’t just about a better website and also explains what some of the sacred cows are that keep library websites from being better.
[M]eeting your users where they are isn’t about making them come to the library website. In considering our long term virtual presence plans, the library website is a given. People who come to the site know we exist and want to use our services. To truly be successful we have to get our content into the path of the people who wouldn’t walk through our door (physical or virtual).
I like Karen’s talks about her work website specifically because she’s part of a larger team that all needs to work together to roll out new services to their faculty, student and staff population. I feel lucky because I often have carte blanche in the tiny sites for tiny libraries that I design. I also have very little reach with those sites. That’s okay for what I’m trying to do, but if I had to bring together multiple different stakeholders and make them happy with a website — including those designing, for example, for 800 x 600 resolution screens — I’m sure I’d find it very challenging indeed.
I’m en route to Nova Scotia today, speaking at NSLA and at a Learning 2.0 program with Ryan Deschamps, but when I get back I hope to show off my own collaborative project, turning the Vermont Library Association site into a bloggish group-maintained site from a static single-admin site. It’s gotten so that I have enough WordPress admin login pages to keep track of that I’ve shunted them into their own folder on my bookmarks toolbar. Exciting times!
Libraries Connect Communities: Public Library Funding & Technology Access Study 2006-2007 Report is out today. I haven’t looked at it yet and was waiting for it to hit the website. The URL for the actual 6MB file is here
If you bookmark the page the document is linked to it will appear as “ALA | 2006-2007 Report” on your bookmark list. While I continue to make the point that tech/web savviness is going to be an important part of being useful relevant libraries in the 21st century, we still put out documents intended to be widely disseminated in PDF format, not HTML This assures that it will be shallowly linked and quoted, if at all, and those links will be hard to track and learn from.
The one news article that I’ve read referring to this report — an AP wire article that I read in the Las Vegas Sun — “Despite Demand, Libraries Won’t Add PCs” is a weird mess of statistics and odd conclusions (won’t add PCs? how about can’t add PCs. Who did this study again? Oh right The Gates Foundation… gee I wonder what their solution to this involves, it better not be Vista. update: the geeky artist librarian agrees). It discusses how popular technology in libraries has become, but also what the limitations are that libraries are facing. The whole article is tailor-made to support a roll-out of the Gates Foundation’s next round of funding which I’m sure will nicely sew up all the loose ends that this article pinpoints.
Except for the fact that more computers means, or should mean, more staff and more space, neither of which get a lot of lip service from technology grantors who would rather give away last year’s software for a hefty tax writeoff. You’ll note that this article says that libraries are cutting staffing so they can afford more computers. I assume then that this is supposed to imply that getting more computers means more freed up money to hire staff. However, we all know, at least out here in rural noplace, that funding remains fixed as does space and what we could really use is an operating system that doesn’t need a 20MB security update every few weeks and a browser that isn’t out-of-the-box vulnerable to a huge range of exploits that leave our computers barely working. The good news is that we can get both of those things and we don’t have to wait for someone to loan us money to do it. Sorry for the slightly bitter tone, I’ll chime in with some more facts from this study once I’ve gotten a chance to read it.
Michael blogged about this last week I figured I’d add some more information. These are two students of mine that I visit irregularly at the Tunbridge Public Library. They’ve got pretty good computers and sharp minds but don’t know the first thing about how to navigate a file system or compose a message to save for later. We sit down and talk about how to do the things they want to do. The last time I was there, I made a little video and you can see it on YouTube.
I feel like I can just say “blah blah insert digital divide lecture here” but really, the library is doing an invaluable service here, and the job I have isn’t even paid for by the library. I’m an employee of a local technical high school that happens to take its outreach mandate very seriously and sends me to these places that happen to be libraries. If I had any tips for people wanting to do this same sort of thing, here they are.
- Encourage people to get laptops. I’m not a real Dell fanatic, personally, but because of them laptops aren’t as fiendishly expensive as they used to be. I really liked that my students were both using Macs because a) it’s the same kind of computer that I have and b) I find them much easier to use for someone who has never used a computer before. No need to start a flame war, but I’ve been doing this for several years and I’ve observed that my Mac students are happier with their computers. You can save people serious money if they have a laptop and they can use the library’s internet service occasionally and not have to pay to get broadband at home.
- Invest in wifi. If students have their own computers then you can teach them about the internet using their own computers. No matter how awesome our public access computers are, they’re not identical to the computers our patrons have at home, they’re just not. Students can learn things on the computers and then take them home and practice the exact same things.
- Solve problems. I used to teach a basic email class at the public library I worked at. It went great. However I would find that time and time again people would come to the class and sit through it because they had one loosely email-related question to ask. They didn’t even need an email class but there was no other way to get five minutes of dedicated staff time to ask a computer question. Consider being available in a way so that people who want a class get a class and people who just have questions can ask them. Also stress that they should come in with a problem to be solved, not just “I want to learn about computers” People who just want to learn about computers should probably go to a class.
- Larger groups help everyone learn. My two students got along great and it was excellent to have them learn from and teach each other as well as learn from me. Having multiple students (not a ton, maybe just two or three) encourages people to see tech support time as a limited resource, lets people see other people’s computers and their problems in a larger context, and makes computer time more sociable and less like school. Also I think people are less likely to let their technostress get the best of them if they are not in a private session with you.
- Keep it regular and keep it brief. Have set times when you offer tech support help. This keeps people queueing their questions to bring to you, can free up other less-savvy staff to refer people to you appropriately and the time limit means people will ask pressing questions first and prioritize their own concerns.
- Share with staff, create a FAQ. If I solve a problem that I see frequently (for example: how do I print just part of a web page) I’ll often share the solution with the staff so that they can know how to help people who come in with the same problem.
- Know when to say when. Unfortunately, the biggest problem in my area is that people need help at home, figuring out their printer, or their network or their desktop machine. I decided early on that going to people’s houses would not be part of my job. There has been a rare case where a patron got DSL and wasn’t sure how to do the self-install and I’ve traded help for a free dinner or something. Usually I’ll refer people to the professionals when they need help either buying equipment, installing something at home, or fixing a complicated problem with some legacy frankenstein PC. It’s too easy to own all of people’s future problems if you get too involved with some of these situations and I’ve sometimes had to tell people that I won’t be able to keep working with them unless they get a more stable computer or start practicing better computer hygeine.
Those are just some top-of-the-head ideas. My library background doesn’t make me special in this regard. Anyone who is okay dealing with people and knows technical stuff well could be part of an informal tech support program at your library.
I read the web4lib mailing list in RSS format. It’s fascinating because not only is there a lot of good advice, and a lot of familiar faces, but I also learn a lot in terms of what people do and do not know about technology which helps me do my job. There are also some more thought-provoking longer threads sometimes about things like the 2.0 bandwagon, whether Twitter/Facebook type applications are a flash in the pan, or the recent thread about whether libraries innovate.
It all started, I think, with a lita-l mailing list topic that I didn’t see concerning the “ultimate debate” happening at ALA. The event was blogged on the LITA blog and debated a lot on web4lib though the thread is sort of all over the place. And then the topic was picked up by other blogs, which someone on web4lib graciously added to the mailing list as a list of links.
I wonder about the topic myself. The libraries I work with around here are very innovative, but mostly in stretching a super-small [usually five-figure] budget and rarely in technological ways. However, when you’re the only free internet in town, taking a step like offering free wifi when the library is closed, or having a way that people can use your computers to download ebooks checked out from other libraries in other states seems pretty innovative indeed.