From the catalogs of babes











{April 21, 2009}   easy to be hard

Lately there’s been a resurgence on RADCAT, the “radical catalogers” mailing list. It’s good, as that list is generally pretty quiet, and the encouragement of introductions and discussions has stimulated conversation and participation. It’s bad, though, too, as that list is generally pretty quiet, and the encouragement of introductions and discussions has stimulated conversation and participation.

What I meant to say by that: I subscribe to a number of library listservs and mailing lists, as well as blogs, message boards, project wikis, etc. My inbox, my Google Reader, my bookmarks, my LiveJournal friends page, are all full of stuff I want to not only read but comment on and participate in every single day. There’s a wealth of good information, help, and support there, but sometimes I honestly fear opening my inbox after being sick for a day or two. The amount of information overload (a recurring theme in today’s world) makes me wonder which is worse–spending hours and hours sifting through it all, or just simply hitting the delete key and chance missing out on something important?

In an attempt to be more organized and efficient, I choose to subscribe to listservs such as RADCAT, AUTOCAT, etc., in digest form. I’ve had some suggestions on how to read the list on the web, which does seem to satisfy some users, but I personally don’t care for it.  So I get all the day’s messages delivered in one (supposedly) convenient email.  However, it’s not so much that I find it convenient, but rather it’s the least inconvenientof the current options available to me.  It’s long; and repetitive where people don’t delete the entirely of the messages to which they are replying; discussions aren’t threaded; and formatting from all sorts of email clients literally makes reading the emails difficult, as many of them come across garbled with code. There is a vast chasm between “convenient” and “least inconvenient,” between “easy” and “less hard.” I really wish I had a better way of filtering and organizing this information. As part of the recent RADCAT discussion, I mused that I would probably participate more if my participation interface was more user-friendly, even going so far as to say “let me know when I can subscribe to the list in Google Reader.”

Which made me think: why isn’tit? Is there any reason, besides continuity’s sake, that these groups have not moved on to harness a more current–and, in my opinion, a potentially more flexible and powerful–technology?

 For instance, AUTOCAT is peppered with posts containing cataloging questions: questions about using AACR2r, LCSH, MARC, etc. A couple of my previous posts about LCSH subdivisions would not be out of place on AUTOCAT. So why didn’t I post them there? Because to get an answer, I would have had to wade through unorganized and unstructured replies–some to me, some to the list itself, some replies to responses on the list itself…it’s just physically hard for me to read and follow. All I wanted was a quick answer to a quick question–‘can I subdivide “Trade shows” by industry?’ A simple “yes” or “no” was all I wanted. It struck me that a brief, direct question requiring a short, immediate answer, might be better served by a technology that was designed for short bursts of immediate communication. Now, I confess, I haven’t been much of a Twitter fan since it’s inception, but that’s because I never saw much practical use for it. Now I think I might. How great would it be to Tweet “anyone know the 040 for Italian?” and receive a real-time reply, without having to log in to email and scroll through numerous messages to find the answer. I know when I am sitting there with the book in my hand, in the middle of cataloging, I don’t want to put it aside and wait to finish when I might get an answer the next day (if I get one at all). How much more efficient might our cataloging be if we could receive quicker responses like this? Of course, Twitter doesn’t supply the ability for longer, more complex conversations, which are inherently necessary when talking about cataloging, but there are other technologies for that.

Like the recent flurry of activity on RADCAT: all these introductions are nice, but after a week or so, they’ve been archived in the depth of the list with no easy, instant way to refer back to them. What happens when I’m reading a message several months from now and want to revisit the author’s introduction to learn more about where they’re coming from? Gee, wouldn’t it be great if there was some technology out there where a person could have a page about him- or herself, and I could easily click on that person’s name and be taken to a profile, a page that told more about them, their introduction and background, what kinds of libraries they worked in, what other interests they might have? And Facebook has the capability for group pages and discussions, potentially allow people who wanted to participate in a 9/11 conspiracy debate to do so while others could talk about authority control on Ravelry.

The key word here is “easy.” The listservs, in my opinion, are not easy. I almost hate to say it, but Facebook and Twitter are. (Even my 70+ year-old aunt is on Facebook, and she is far from what I would call tech-savvy.) They are designed to be easy to use, because that gets them more users, and therefore more eyes viewing ads, and therefore more $$.  And it works–Facebook has 200 million active users. It’s not that this technology is “new” or “shiny” or “buzzworthy” or “cool.”  It’s that it’s easy to use for what people want to use it for, so they use it. It’s using the right tool for the right job. Technology too succumbs to the survival of the fittest. People will use what they find easy and pass on what they don’t: is anyone out there still running DOS? No, because something better, more powerful, and more user-friendly came along.

Now, everyone’s idea of easy will differ. Some people are not only content with listservs but prefer them. And that’s fine. What’s not fine is the inability for users to choose through which interface they prefer to interact. Wasn’t that part of the whole glory of Web 2.0? That we could make content independent of formatting, so that the user could view it in whatever format they preferred?

Whatever it is, we need to stop locking our content away in these outdated technology platforms. As technology evolves, we need to evolve as well. These listservs are a great concrete example. But I think they’re also a great analogy for libraries in general, and especially for cataloging. Whay are we still using the same difficult tools, rules, workflows, and softwares? Continuity can only carry us so far. Why are we fighting against technology and evolution, instead of using it to improve not only our jobs but our patrons’ experiences? And why do we continue to insist on making cataloging hard?

Advertisements


[…] if the author had read back though my blog, he or she would see that I severely dislike the listerv format utilized by AUTOCAT et. al., and that I rarely actually read or contribute. Since I published that post, I’m excited to […]



Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

et cetera
%d bloggers like this: