A New Line of Librarian Action Figures

I got a catalog in the mail the other day advertising the new deluxe version of the Librarian Action Figure. She comes with a book truck, and some extra books. Nice.

Still, I think there should be a whole line of librarian action figures, including one with the earlier, discarded, exploding bun feature.

Lightning-fast reference is an obvious Librarian Superpower, as well as maybe, oh, I dunno, Willingness to Dedicate One’s Life to the Good of Others. But I don’t know how you would turn that into a pushbutton feature…unless you push the button and she detaches her head and offers it to you.

Overwhelm them with sheer numeric superiority

Me and Dewey at ALAI just checked the frappr map, and dang you Librarian Avengers are so cute! And geographically disparate! All 81 of you. Gulp.

Once I realized there are so many people out there willing to read about my battles with bad librarianship, scary interfaces, and look at photos of my grandma, I had to sit in the closet and rock back and forth for awhile. But I’m back! And do I have news for you.

According to Siva and the ALA, there are more libraries in the U.S. than there are McDonalds. Let’s consider this news. Let’s consider the possibilities it opens up. Let’s consider what, say, 16,220 librarians (that’s one librarian from every U.S. branch) could DO if we all decided to work together. Are you thinking? Let’s make a list. I’ll start.

  • We could swarm the U.S. Senate carrying burning copies of the Patriot Act on pitchforks.
  • We could donate one book each and create a brand new library
  • We could build a search taxonomy for the ALA BY HAND
  • We could build an entire neighborhood for Habitat for Humanity and call it Librarian Land.
  • We could dig up enough dirt on our local censors and anti-library-funding jerks to put them all out of commission.
  • We could start selling yummy hamburgers and make the whole country fat.
  • We could start making people do pushups for books and make the whole country fit.
  • We could have the world’s biggest librarian party! Every year! Twice!

Your turn.

My library helps Harry Potter!

screenshot of Cornell homepage with Macaulay library featured
Take that Voldemort! Several articles have come out in the Cornell press recently about the Macaulay Library’s huge collection of animal sounds. One of the ways we stay afloat is by licensing our sounds to movie studios. Recently, this has included helping give a voice to Buckbeak the Hippogriff in the Harry Potter movies.

Also, today we are being featured on the Cornell homepage. This is all in buildup to the release of our massive, monumental, absolutely nifty, online collection that will make all of our sounds and videos available for free Real Soon Nowtm. Just you wait. You’ll see.

Buckbeak saying Meyow!In other news, it’s snowing here and I’ve got a two-foot high stack of receipts representing three different currencies to sort through from our Euro-trip. We also have that penguin movie sitting in a Netflix envelope at home. And I made matzohball soup last night using this recipe.

Spain update

jamon.gifHi all – a quick update. I don´t want to type much since I´m using a cybercafe machine and the keyboard is greasy, perhaps due to the monumental consumption of pork products in this country. Great XForms tutorial this morning at the conference. I learned a whole lot about XHTML 2.0 as well. This is some damned exciting stuff for libraries and the library-ness of the web. I´ll try to talk some more about XHTML2 when I´m not dizzy from Spanish over-the-counter cold medicine.

Right now I´m going to stay away from the complicated topics and just wish everyone in Los Estados Unidos a happy Thanksgiving. Wish I was with you eating stuffing instead of sitting in a weird cybercafe looking at a pig leg and inhaling secondhand smoke. Good times. I´ll see you all on Saturday back at home.

Liveblogging Fundamentos Web 2005: Part Two

One of the big questions I have about web design for accessibility is, how can I design for one audience without isolating another? Obviously, there are basic things I can do to make our web applications more accessible, by including alt tags, skiplinks, and labeling form fields. But our users have a higher level of disabilities than most due to the nature of our content (birding is of wide interest to the blind and our users are often older, and therefore more likely to have disabilities) and I want to make sure our site is as useful to as many people as possible.

The problem is, if I take steps to make the site accessible to one group, say our partially-sighted users (hi dad), by increasing the text size and contrast, I risk not serving users with cognitive disabilities who respond better to an interface in which only the important elements are emphasized using contrast and the text is not large and overwhelming. Similar arguments apply to designing for young users, who are also one of our main user groups.

The terrible reality is, some solutions can help people with certain disabilities, but exclude others. This puts organizations in a position where they must, often not consciously, choose only certain disabilities to address, such as the charismatic blind man with a dog, and ignore users with different and perhaps competing needs.

I can see why the process of creating web accessibility guidelines is so difficult. The perspectives involved are broad and often divergent. This isn’t like web standards, where you can just close your tags and call it good. Real people will be discriminated against if you screw up. The responsibility is sobering.

At the Macaulay Library, we are proud to provide spectrograms of our bird sounds that are accessible to the hearing-impaired. However, the software to view the spectrograms requires a multimedia plug-in that is annoying to blind users.

What should I do? Do I assume blind users aren’t interested in these spectrograms, and design an interface using Flash and other inaccessible technologies? What if a blind user wants to show a spectrogram, which is a valuable educational tool, to a sighted friend or their child? Even worse, it isn’t possible to even generate spectrograms without using QuickTime and Flash, so the choice has been made for me. Without even making a choice, I’ve created some happy deaf people, and some pissed off blind people. Can I provide an alternative way for the blind to use this feature? Nope. The technology prevents it. Can I provide a larger version of the spectrogram tool for users with manual mobility problems? I could, but it would hold back the entire project while I designed it and no one would be able to use it.

These are dark choices, my friends, and they are often made under pressure of time and money. I’m glad to have the opportunity this week to spend time thinking about them. Thanks to work for sending me here.

Liveblogging Fundamentos Web 2005: Part One

Leader dog imageThe conference is in a combination of English and Spanish, with simultaneous translation headsets, so there’s a strange aural halo of chatter going on in the background. I’m providing my own simultaneous translation by blowing my nose every five minutes or so. Stupid cold.

Right now John Slaton from the University of Texas Accessibility Institute is speaking. I got a chance to speak with him for a few minutes before the presentation and was glad to hear about his work. I wish more Universities would have this kind of focus on making materials available to everyone. Granted, universities are much better at this sort of thing than most institutions. There’s usually an office somewhere, often in the basement of the library, which helps students with disabilities. Still, it’s neat to hear from a school that has taken a national role in developing accessibility standards. Hook ‘em horns.

Much of what we’re hearing right now from the W3C is "real soon now" about their next set of accessibility standards. Which is understandable considering the scope of this project. It sounds like there is a good understanding of the weaknesses of the current standards, especially regarding new and different combinations of technologies. The old standard assumes you are using just HTML, which is actually fairly unusual these days for large dynamic sites. At my library, we’re using Java, JSP, Struts, and some nonessential JavaScript. All of these languages are pretty tangential to the existing guidelines. There might be a new working draft announced tomorrow. Pretty cool. These are good folks, give them a break.