a week in the life, august edition

I have a month pretty free of travel and speaking stuff so I’ve been doing more little library work in August. Here are a few things I’ve done this week both here and online.

  • Stopped by the Tunbridge library in Monday to help a woman who is re-entering the workforce brush up on her Excel chops. I had to tell her that while Excel hasn’t changed much, the amount Excel tries to help the user has. That is, there are all these wizards and auto-widgets that try to make Excel easier but have the end result for novice users of making Excel harder. The main problem my student was having, however, was trying to figure out where her missing Word toolbar went and no matter how many times I said I pretty much couldn’t troubleshoot a personal computer problem remotely (and offered alternatives like a good manual or the help files) she sort of couldn’t stop talking about it. I see this fairly often. I suggested that she buy a USB drive so that I could give her homework assignments that she could take home.
  • I talked to the Tunbridge librarian about a Photoshop problem she was having which was actually a much more complicated problem. She has taken photos of flowers for the library’s flower sale, but the way they show up on the screen and the way they print doesn’t reproduce the colors accurately. I showed her how to do some color adjustment in Photoshop but said that tweaking the printer to get things just right was likely overkill for what she was suggesting. Explained how color calibration works. Sometimes good tech support involves telling people that what they want to do is going to take significantly more time than they have budgeted, and suggesting an alternate plan. This sort of time estimate thing is fairly easy for me and seems to be a big difference between someone who is really comfy with computers and someone who is still in the early stages of getting to know how they work.
  • The lady who lived next door to the library brought her laptop over to see if it had any “network card” in it so that she could use the library’s wifi instead of her dial-up. Answer: no, but I explained to her how she could buy one if she wanted to.
  • Visited the Royalton Library to help the librarian figure out why the computer keeps asking for some sort of HP Setup CD when it starts and pops up a zillion messages, sometimes freezing the computer. Figured out how to turn off the thing that requires it. The staff computer also has some sort of virus file (according to AVG) that throws up random pop-ups but we couldn’t remove it even following Symantec’s instructions. Switching to Firefox at least made the pop-up problem go away and bought us some time.
  • No one came to my Tuesday drop-in time. The network was down anyhow, for unknown reasons. The IT company who has the school contract wasn’t sure what the problem was and could give no firm ETA so I went to donate blood instead of waiting to see if anyone would show up just to tell them that our Internet was down. Even though my drop-in time is just “computer time” 90% of the people who come in use the Internet in some form or another.
  • Wednesday I went with my friend Stan to the Tunbridge World’s Fair office. They are using some sort of Fair Management software that doesn’t play nice with the network. I knew I was in over my head so I brought my pal Stan in for a consult. He mostly hammered the software into shape while I cleaned up the office, organized things, and hung up a few years’ worth of ribbons. One of the library trustees who also works part time for the fair bought us lunch and offered us free tickets when the fair starts next month.
  • I stopped by the Kimball Library in Randolph before drop-in time on Thursday. I’ve been working with the librarian who works on the website, helping make the site more functional for the staff as well as for patrons. I showed her how to get her web log files and run them through Webalizer and we looked at he traffic the site has been getting since we added the online catalog a few months back. I also helped her get a Kid’s Page started in the hopes that it will inspire the (very busy) kid/ya librarian to give us suggestions of what to put there.
  • Thursday I had one student at drop-in time, a teacher from the high school who was trying to make a list of donors for the Crafts Center Restoration project in town. Someone had typed the list up originally and she needed to know how to add a name to the list she has on the disk. She wanted to use her computer at the school but it didn’t have a disk drive. So we muddled through that and I asked if she had any other questions and showed her how to make a mailing list using her ISP’s webmail program and also how to attach a photo to an email message.

Meanwhile this week, I’ve been going back and forth with some folks from VLA about changes we’re planning for the VLA website, bought tickets to Nova Scotia for a few talks I’ll be giving there in September, accepted an invitation to join the Steering Committee of the MaintainIT Project, made plans to do some work with Casey and the Scriblio project, firmed up plans for a talk in Rhode Island, passed on a talk in Delaware that conflicted with a talk I’m giving in Kansas, and started making plans for my next week of library visits and my next month of travel/talks. I have a friend who is another local librarian who is working possibly switching her library to an open source OPAC and we’ve been scheming about that. I got my inbox down to single digits by replying to almost everyone who had written me after the NYT/WSJ articles. If I haven’t replied to you yet, I swear I will this week.

That’s the report for now. Today is a day for guests and swimming in the pool and maybe some grilling in the backyard if the weather holds.

Hello Wall Street Journal readers!

Or, if you don’t know what I’m taking about, go read this story: Discord Over Dewey. It’s loosely about the Arizona library that decided to get rid of Dewey and make the shelves more bookstore-like, you know the one, but it gets bigger. To quote the article

[T]he debate, say many librarians, is about more than one branch’s organizational system. It feeds into a broader, increasingly urgent discussion about libraries, where a growing number of patrons, used to Google and Yahoo, simply don’t look for books and information the way they used to. Some are drawing on cues from the Internet in proposals for overhauls of cataloging systems, but others are more hesitant, saying that the Web’s tendency to provide thousands of somewhat-relevant results flies in the face of the carefully tailored research libraries pride themselves on.

And if the Wall Street Journal can end a sentence with a preposition, we know the times are changing, right? I’m quoted a little in the article. I had a nice long chat with the writer — as with the NYT piece — and just a tiny bit of it got quoted which I think confuses a few issues, but hey it links here so I can spell them out now in more detail.

  1. The difference between research and looking for information for other purposes. There are much stricter requirements for research — what’s citeable, what’s a good source, what’s authoritative — and a lot of the agitation has been about less-authoritative sites being used more and more not just for people looking up things that interest them, but also for research or attempted research. Is it okay to cite Wikipedia as long as you can prove that you understand that it’s not authoritative? Isn’t there research value to saying that some fact is in Wikipedia, even if it’s not necessarily the same value as that thing being true?
  2. The age gap. People not raised with Google are often more okay with their searches being iterative processes that take longer. Some aren’t. Similarly, younger users are often impatient with iterative searching or the very familiar “try these sources and let me know if they’re okay and if not we can find some others” approach.
  3. Google slicing. I was making a point that because Google is so popular, people forget that information can be indexed by different things than Google decides to index it under. So, searching for content by filesize, by “most recently added to the catalog”, by date added, these are all things Google could do but doesn’t. The problem is that we are forgetting that there are other ways to determine relevance, or relevance to US.

In any case, I liked the article and it had good quotes from a lot of people, some you will recognize and a few you may not. They end the bit with a good line from Michael Casey “Librarians like to think that we’re indispensable,” he said. “While I think that is true to a point, I don’t think we should continue to propagate the idea that we’re indispensable by keeping a complicated cataloging system.”

Me at work, seniors learning computers

Me at Work

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.

  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. 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.
  6. 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.
  7. 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.

Hello New York Times/Sun readers and other “hip shushers”

The fashion section of the New York Times has an article titled A Hipper Crowd of Shushers which, despite the title is less annoying than the usual “librarians, they’re not as lame as you think!” articles that we see about the profession. I’m quoted in it, there’s a great picture of Peter Welsch DJing, a quote from Sarah Mercure and a bunch of other fun pictures and quips. The New York Sun has its own article on a very similar topic.

Jessamyn West, 38, an editor of “Revolting Librarians Redux: Radical Librarians Speak Out” a book that promotes social responsibility in librarianship, and the librarian behind the Web site librarian.net (its tagline is “putting the rarin’ back in librarian since 1999”) agreed that many new librarians are attracted to what they call the “Library 2.0” phenomenon. “It’s become a techie profession,” she said. In a typical day, Ms. West might send instant and e-mail messages to patrons, many of who do their research online rather than in the library. She might also check Twitter, MySpace and other social networking sites, post to her various blogs and keep current through MetaFilter and RSS feeds. Some librarians also create Wikis or podcasts.

Socially Portable, my contribution to the BIGWIG showcase

I decided to do something for the BIGWIG Social Software showcase even though I wasn’t going to be at ALA. I think I missed out on most of the awesome parts of this excellent idea/event, but I was still happy to put a little something together. Then I went to NYC for a long weekend, and ALA happend in DC and I sort of forgot about it until now.

I have to say, a wiki with the exhortation “Please note that all contributions to Social Software Showcase may be edited, altered, or removed by other contributors. If you don’t want your writing to be edited mercilessly, then don’t submit it here.” (as all mediawiki wikis have) seems like an odd place to put presentations that you’d sort of hope wouldn’t be mercilessly edited, but that’s a small gripe in an otherwise enjoyable exercise. My presentation is called Socially Portable and is a short and hopefully amusing look at portable applications (for Mac and Windows) for people interested in having identities that are not just flexible but actually mobile. I hope you enjoy it. Thanks very much to Michelle, Jason and Karen for putting this together.