Now, getting Sunday passes involves picking them up at the library on Saturday. We headed over to the library to get the passes. When we got there, the librarian said that someone else had reserved the passes and sorry but that was how it went sometimes. We asked if she was sure that it wasn’t us who had reserved them [she had scanned my boyfriend's card and showed no passes reserved and the passes we wanted weren't available according to her computer] and she said she was. She was sure. I put on my politest voice possible and said that we had called and done this whole routine twenty minutes ago and how unlikely it was that someone else had reserved the passes and would she please check that the passes that she showed as reserved were not, in fact, reserved for us? I probably do not need to tell you how this story ends. The museum was delightful, marred only slightly by the fact that bad software, wonky library policies and erratic customer service nearly stood in the way of us getting them at all.

This is just a big lead up to tell you that Brian Herzog has written a nice post with Rich Boulet reviewing calendaring and room reservations software and you should go take a look at it. Maybe there’s a better alternative to the software that you use?

This short article makes a few points very well. Many novice tech users are experts in other things and get easily frustrated feeling like they’re back at square one. That sort of thing needs to be considered when you’re figuring out the best way to approach teaching topics. Additionally, find ways for people to succeed, whatever their level of skill is. This can be a challenge for people who are really brand new, but just having simple taks like mouse proficency and “send an email to me. Oh look there it is” can give peopel the confidence they need to explore on their own. [thanks barbara]

I work for the Washington State Digital Archives. We have something like 80 million documents, mostly from Washington State counties, online and add millions more per month. After years of resistance the counties are really hopping aboard and have become great fans of our service.

But still we get these complaints and worries. It is even worse with archives than museums because so many county and local archives count on revenues for access to fund their offices. We are about to put up thousands of cases from county courts, some dating back to the late 1800s. But the county insists that we display only the top half of the first page of each record–and charge 25 cents a page for users to even view the records beyond that first half page! It is anti-democratic and eliminates many of the potential advantages of digital history, but there you have it.

Slightly related librarian topic over at AskMetaFilter, a question about questions: What questions do library users most often ask?

Technology has to be supported by brotherhood, sisterhood, understanding and compassion.

And if I can paraphrase, I’d have to say “We’re all in this together and we haven’t all learned until everyone is leaning.” I’ve definitely been guilty of throwing up my hands trying to teach someone something because they had so much emotion wrapped up in why the computer “didn’t like them” that they couldn’t follow steps to do the actions they theoretically wanted to do.

Just like people who choose to live in the frozen north up here do so “for a reason” I think that most people who don’t know how to use a computer in 2009 — similar to people who don’t drive, who don’t have a telephone or who don’t have electricity — don’t know for a reason. For some people that’s an active reason, they’re not interested, they don’t see a need for it, they’re already busy enough, but for some people it’s a passive reason, they’re resistant to change, they’re easily frustrated, they have a disability that makes technology difficult and no one to help them with adaptive tech, they’re poor. As a technology instructor, part of my job is making technology a genuine option for people who have a need for it, not to sell it to people who don’t want to buy it. At the same time I explain what technology actually IS, apart from the television commercials and relentless boosterism about the promise of the Internet. That’s my interpretation of “technology with heart” [ttw]

I went to this page from Nicole’s post (I’m not going to the conference) just to see if it was really true that the page claims it is “best viewed in IE” which is yet another “tech don’t” in the world of 2008 browsers so much so that it calls into question all the rest of the site.

I don’t belong to ALA anymore. I did my time, paid my dues, donated a lot of service time to the organization and tried to be gentle and patient as they steered a big organization through the minefield of technological change. The Event Planner has been an outsourced, broken and insecure tool since they started using it. I’d like to see ALA do better, but my optimism that this will happen is flagging.

I also often feel that one of the reasons we’re in this strange place is because many privacy issues are ones that technology could be solving for us. Yet, at the same time the technology we’re working with doesn’t allow us the granularity of making, for example, patron reading information available in the aggregate while still keeping the patron’s identity completely private. We have many patrons

Patron 1 wants to make sure no one ever knows what they are reading. Tells the OPAC to not keep his reading list. Knows his PIN. Wants to make sure the public access PCs don’t retain records of the sites he’s visited. Is a bit horrified that the library data we do keep isn’t in some way encrypted or otherwise protected.
Patron 2 wants to know every book she has ever checked out. Wants the library to leave the name of the book she has on hold on her answering machine. Wants her friend to be able to pick the book up for her at the library. Doesn’t remember her PIN and finds it vaguely annoying that she needs more than her library card number to use the OPAC.

A privacy solution that works for Patron 1 becomes a usability impediment to Patron 2. While libraries have the responsibility to keep both patrons’ data safe, they also have the responsibility to be usable and accomodating to both patrons. Technology, in my opinion, can address these issues but librarians have to a) embrace it b) request it from their vendors c) be willing to tolerate the learning curve that comes with any new technology.

I’m off to the tiny library today to help them with their slow automation project. In the meantime, these are the articles I have been reading about privacy lately. They’re about the information the mailman has, not the librarian, but it could apply to any of us at our job as well. The blog post is about an NPR story following a mail carrier on her route. She talks about what she knows about the world and the economy based on what people are getting delivered. She is supposed to keep people’s mail private, and she never mentions any names. Yet, there’s a lot of metadata in mail delivery, things the mailman knows. The blog’s author wonders how simple it would be to identify the people getting mail delivered from the information the mail carrier imparts. Feel free to read the rest.

• What Your Mailman Knows
• Abandoning the Envelope Analogy

Technology should enhance our lives, not add to our stress or cause danger through poor design or poor quality. It is our duty to ensure that this technology is effective, efficient, satisfying and reliable, and that it is usable by all people. This is particularly important for people with disabilities, because technology can enhance their lives, letting them fully participate in work, social and civic experiences. Human error is a misnomer. Technology should be developed knowing that human beings have certain limitations. Human error will occur if technology is not both easy-to-use and easy-to-understand. We need to reduce human error that results from bad design.

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.

• Quick privacy-related link: why is was it so hard to find Google’s privacy policy? Also, if you’re not familiar with the Google/Viacom lawsuit, now is a good time to get familiar.
• 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?

• 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.

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)

[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!