By Meredith Farkas | November 23, 2005
I’ve talked a lot in the past about the gulf that is growing between libraries that are change agents and libraries that are change averse. Lately, I’ve been seeing a new gulf growing in libraries, that has less to do with one’s attitude towards change and more to do with the skills of one’s staff. I see it happening in my library, and my Director is an enthusiastic proponent of change. The problem is that many libraries simply don’t have people capable of creating significant changes in our library middleware. Our systems librarian can get our OPAC to work (in the sense that people can search it and maybe even find our materials if they know how to search it) but that’s it. More often, he’s fixing printers or calling vendors because their products stopped working with our off-campus students. There is no one who knows how to code, and this includes most of the people in IT (not that we have that sort of relationship anyways). I’ve been lobbying to get a coder — or better yet, a librarian who can code — as we have one more funded position that we can create. I want someone who can hack into the catalog and find ways to make it easier for us to search it. I want someone who can not only talk about Library 2.0 and Web Services, but who can actually create things that move us towards 2.0 (whatever that means). I want Norwich to have an OPAC that is easy to use, online journals that are easier to find, and databases that are easier to search.
I guess there are a few ways for libraries to actually get coders:
- contract out for specific services if there aren’t a lot of things you need done
- work closely with folks in IT to get things done (this is only possible if you have a good relationship with the IT folks and if they themselves have the skills to do what you’d like them to do)
- Hire a coder with an IT background
- Hire a librarian with a coding background
- Grow your own coder-librarian through continuing education and training
Some libraries have been smart enough to hire AMAZING librarians and/or coders to help with this stuff. Here are some of the folks I’ve been keeping an eye on who really blow my mind:
The stuff that Casey Bisson is doing at Plymouth State University in NH is so exciting! Why doesn’t every library have someone like him?!?!? Casey has two blogs, both terrific: Maison Bisson and LIBDEV (which is a collaborative blog). Last week, he spoke at the NEASIST Conference Buy, Hack or Build, where he discussed what we can do to improve the OPAC beyond the superficial “lipstick on a pig” sort of stuff. You can hear a podcast of his talk here. Check out the insanely cool prototype he created to make it easier for people to search the catalog by subject. It reminds me of what Red Light Green does with related subjects, but it’s even better because it shows the user the results and the subjects side-by-side. It is really hard to search most library catalogs, and the sort of stuff he’s thinking about will make it much more usable.
John Blyberg is the Network Administrator and Lead Developer at the Ann Arbor District Library. Yes, that library. The library with the most exciting Web site I’ve ever seen. The library that is implementing RSS feeds for keyword searches in the catalog. His blog blyberg.net offers many behind-the-scenes peeks at AADL and their Web site. If smoke comes out of your ears every time you think about the usability of your ILS, you should check out John’s ILS Customer Bill-of-Rights.
I dutifully read Dan Chudnov‘s work log in my aggregator, and though I don’t understand a good 80% of what I read, I am thrilled that developments like this are coming from a librarian! Dan Chudnov worked on the project team that developed DSpace and has been doing really cutting-edge stuff in the library world ever since. He created Unalog which is a social bookmarking application. I have used it a great deal in my book research to see what librarians in-the-know are bookmarking. He is also working on COinS and COinS-PMH (Making Links’ COinS-PMH for Better Links has a great explanation of COinS and COinS-PMH).
I don’t know a lot about what Roy Tennant is working on at the California Digital Library since he doesn’t have a blog (and we all wish he did). What is extraordinary about Roy is that he’s a coder who can explain technical things in plain English to regular folks who don’t even know what XML stands for. And he makes you actually want to know more about XML. He also can inspire people to think critically, to push for change, and to look at their own OPAC with a more critical eye. I was blown away when I was talking to one of the librarians at work about how unusable I think our OPAC is and she said “I agree. I went to a talk last year where this man from the California Digital Library talked about how our catalog should work more like Google…” I nearly fell out of my chair when she said that. Thank you, Roy, for getting the ball rolling for me at work before I even got there.
Ryan Eby‘s blog has a lot of terrific insights about OPACs, social software, and search. Ryan works at Michigan State University and also writes terrific tech-related stuff at LIBDEV.
Why? Why stop your users from using new tools? Is your job of stifling their creativity and innovation that satisfying? Are you afraid that you won’t have a job if they have these tools?
Is it security? Ok, lets argue that. If you are worried about security, do not, let me bold this, DO NOT put your computers/servers on the internet. So there is your security solution.
OMG, this man is so cool! Chris is the “IT Guy” at the Lewis and Clark Library System and I’m sure he spends lots of time empowering his patrons and the librarians he works with. He even started another blog, the LCLS Webborotory to highlight the stuff he’s doing there, prompting a wistful “rant” from Jenny Levine. I would love to have someone like him in my library too!
Dorothea Salo of Caveat Lector is one of those brilliant and independent people who, when faced with a problem, just learns what she needs to know to fix the problem herself. She may not know a ton of programming languages yet, but you can be sure she will learn them as soon as she feels she might need them to do better work at her job. Recently she started learning Java, which I can attest is no mean feat. Her gutsiness and moxie makes her a definite role model for me.
In response to a post of mine a few months back, Dorothea wrote:
I do think there’s something to be said for acquiring the necessary expertise ourselves. I do like to see experts working on our stuff, but honestly, if we took the trouble to get a clue (much of this stuff isn’t rocket science), we wouldn’t be in such sad straits as we are.
I am totally in agreement with all of the folks who think that librarians should try and learn to code. I really do want to be that person for my library. However, there are two things standing in my way. The first is time. Obviously, with the book my free time is gone. Even then, I brought my PHP and MySQL book with me to work back in September with the best intentions of learning while at work. But there are the constant e-mails and reference desk shifts and projects that need to get done. Maybe during the summer I’ll have more time at work to sit down and learn, but with the amount of time I have to learn programming languages, I don’t think I’ll be hacking the ILS anytime soon. The other problem, much more difficult to defeat, is the difficulty I have learning programming languages. I’ve noticed that some people (like my husband) really have a facility for learning this stuff. Maybe it’s because he’s been programming since he was 10 and I’ve only become interested in the past 2 years. For one of my classes in grad school, we had to learn some Java to create some algorithms. I read the book and read the book and read the book. I did the exercises the book suggested I to do for every chapter. But I just couldn’t get it. I’m not accustomed to “not getting things” and I’m certainly not a person who would ever give up easily. My husband would explain things to me (having never learned Java himself, it was frightening to me how quickly he picked it up based on his knowledge of other programming languages), but none of it made sense to me. I feel the same way with PHP (which I know is supposed to be EASY) and I wonder whether I’ll ever be able to get beyond just using it to create web forms.
I have the desire. I want to be able to do this stuff. I just question whether everyone has the ability to learn programming languages well. Just like some people can’t design a good-looking Web site to save their lives and some people lack the ability to write well. We all have our strengths and for some of us, learning programming languages may not be one of them. Maybe I’m wrong. I am just speaking from my own experience. But I sincerely doubt I’ll ever be doing the sort of stuff that Dan Chudnov or Casey Bisson do. I hope that I can make a contribution to the library world as someone who is always willing and eager to try out the latest software, someone who is always happy to teach other people how to use technology, and someone who is always a vocal proponent of online communities, social software, user-centered Web site design, and usable library middleware.
Maybe we need the motivators just as much as we need the coders.