How vegging out in front of the boob tube improved my professional skills

I’ve been going for the most passive of all passive entertainment the last couple of weeks while my health has been on the fritz. The hard part of my super-passive entertainment regimen is right at the beginning, where you choose a series on Netflix, preferably one with many episodes since the initial choice is the brunt of the work. Man, I wish I liked Mad Men… Anyway, after that initial hard work Netflix does the rest for you — all you have to do is wait for the next episode to cue up for you, and the next, and the next.

So there I was, catatonic in front of the screen on Sunday evening. There may or may not have been drool. I probably hadn’t showered recently. There were probably orange peels scattered around my coffee table (I’ve been on a bit of an orange binge lately). Netflix was serving up endless episodes of one of my favorite genres: BBC mysteries. You know the ones. They have an interesting, complex character for the main detective, and then far more murders than any one tiny country town in the British Isles could possibly sustain without completely depopulating. I love them. Anyway, this particular detective (Inspector George Gently) has an annoying, immature jerk of a second in command (Sergeant Bacchus), Gently has to spend some considerable time explaining to Bacchus just how prejudiced and immature he really is. In this particular episode, Bacchus’ primary vice was “racialism.”

Hold on! Racialism? You mean, in the UK people are Racialists rather than Racists? Or at least it’s a totally accepted term for that form of prejudice?

So, being the librarian that I am, I told my coworkers the next morning about my startling discovery, and we started searching Google Scholar, as one does. Turns out, you get two pretty distinct sets of results if you search for racialism vs racism. So bear that in mind next time you’re searching a free-text database.

Next weekend I intend to continue my vegging… er… RESEARCH. For science.

Good searching really isn’t about searching

I’m a librarian. My brand is Search. And I do a lot of searching every day, and I know a lot of fancy ways of making that search go well for me (much of the time). But today a chance comment underscored something I think I’ve always known: good searching really isn’t about Search, or at least not in the way that people think of Search.

Here’s what happened this morning. I’m part of a grant-funded “iPad Learning Community” on campus. We get iPads (woo!) and we commit to attending learning community sessions several times during fall term to build a better understanding of how iPads work with higher education. So I’ve been doing a lot of experimenting with iPads lately, and one of my favorite things to do on an iPad is read and annotate PDFs (I’ve been using iAnnotate, though I just got Good Reader to play with, too). The thing is, it gets very tiring to write without letting your palm hit the iPad surface, and if your palm hits the iPad surface it can suddenly not tell where the tip of your finger or stylus is and so annotation goes all wonky.

So I fired up my trusty Google, and typed in iPad stylus wrist guard thinking that these were probably terrible search terms but thinking that any page that used all of those terms would probably talk about the problem I was having. Even if all I found was someone else talking about the problem, I might learn better ways to ask the question, or see someone’s answer to the question. Meanwhile, Google suggested as I typed, and thought maybe I should search for iPad stylus wrist protection, which seemed reasonable to me, so I hit “search.”

I don’t remember the next steps very clearly because this was yesterday, and yesterday is a long time ago, and I did it all really fast and without thinking too hard because this is what I do for a living — find stuff when I don’t really know what I’m looking for or how to ask the question. But eventually I learned that there’s a useful term, “palm rejection,” which is the name of a feature that people aim for in tablet applications. So I searched for iPad palm rejection and came up with some pretty useful results, including a site recommending a glove that I’m going to try out.

When I got to the learning community thing this morning, I said I’d found this glove and one of the technologists asked “how did you figure out that it was called palm rejection?” (None of us had heard the term before.) I said, kind of flippantly, “I’m a librarian!”

But then I realized that yes, it was because I had a different goal in mind for searching in the first place. I was first searching for terminology that would help me do a good search. And that’s what I do with students all the time — work with them to figure out what some key terminology might be so that they can make those search boxes work for them.

So I guess good searching, at least in the case of novices looking for information, is often more about learning to look for clues than it is about fancy search strings.

Libraries, IT departments, and complex relationships

We have what I consider to be a really good working relationship with our IT department. When I talk to other people on campus I come away thinking of it as shockingly good, but most of the time I forget what it could be like and just go about the daily business of being in a good working relationship with another department. Their head of public services sits on our Public Services committee. I sit on their Service Points Steering Committee. Their director and ours meet regularly. Their director participates in our leadership team meetings. The people who run their main help desk and I talk nearly daily as we coordinate the running of the public labs (of which the library has 3) and the supervision of the IT student workers who, as a pool, staff both their main help desk and our Research/IT desk.

What’s more, we’re also friends. Most of us, anyway. There are a few people I don’t really know or understand over there and I’m sure the same is true when they think of us. But really, I’m going to movie night at one of their houses tonight and another one and I have swapped books and another and I meet to knit together nearly every Saturday morning. We confide in each other. We’re friends.

So yes, things are good. But as with any relationship, things are also complex.

We had a joint retreat recently, and one of the questions several of us raised in our breakout groups — the question that’s kicked around in my head since then — is how to have a truly collaborative relationship when the library is about 90% customer of IT and 10% collaborator with IT. We have complex systems that they support. We have weird old fashioned printers (i.e. label printers) that we really need but that don’t work most of the time. Our web presence is complicated. Our need for public technology infrastructure (and bandwidth) just keeps increasing. Some of us want to tinker with all kinds of geeky stuff, and some of us need help copying and pasting. I don’t know if we’re their most complicated customers on campus, but we’re probably right up there.

So there’s a weird power dynamic there, and potential for either side to get resentful: us if we think they’re not helping us enough and them if they think we’re demanding too much time or resources. And we wondered how to even out that power differential a bit in hopes of keeping a good thing going and making it even better and more sustainable. What is it that we offer them?

Currently, we’re one of the best places on campus to test equipment and software. We’re a high traffic building and one of the few on campus that’s frequented by faculty, staff, and students. And we’re also pretty good at soliciting and communicating feedback. So when the college was deciding on a campus-wide printer/scanner/copier model, we were the main test site. When they institute new software or interfaces, we can usually tell them how it’s being received by our students.

We also offer a space where IT can have direct contact with students who are in the midst of doing their work. The main lab in the library is the reference room, with the joint Research/IT service desk and the two busiest printers on campus. One thing that our IT department doesn’t have much of right now is very direct connections to the curriculum and student engagement with their academic work on campus, and since that’s really the core of the campus’ mission and ethos, figuring out how to engage with that enterprise would be a great step. (There is a group of academic technologists that consults with faculty and students about curricular matters, but for the most part they are separate from the main help desk.)

Right now, they’ve come through several years of several iterations of major reorganizations, so I suppose we can offer a sense of stability if we’re in collaborations with them and other departments or individuals.

But what else? Surely there are ways to offer more tangible support for colleagues that we value and that make our work possible. What are some of the things that you offer your IT departments?

The evolving face of shelves and desks

Harvard Library Reading Room

Libraries have always been many things, but one thing they’ve generally focused on is providing materials and places to read and engage with those materials. Shelves and desks.

With more and more of our collections moving online, an internet connection is now the equivalent of a shelf for our electronic collections, browsers and computer desktops are now the places to read and engage with those materials.

This hit home for us in a big way when our wifi infrastructure crumbled under the ever-increasing demands on its resources (thank heavens for smart and dedicated IT folks!) and when “use one of the library computers” wasn’t an alternative any more because they were all in use. All three labs of them.

I used to think of wifi and computer access in libraries more as amenities. People come here to do their academic work, so isn’t it great that they can stay here and actually do their work. But over the last few years I’ve decided that our collections and the assignments that our faculty require have evolved such that it’s no longer useful to think of these and things like them as “extras.” These are our shelves. These are our desks. These are part of our core mission. We provide materials and ways of engaging with those materials, just as we have always done.

Last Week in OSes Connecting to our Campus Network

Here is a list of OSes that connected to the campus wireless network last week, and the number of each of those OSes that connected. Dorm rooms don’t have wireless, only wired, so they don’t show up here, and lab machines are all wired, so they don’t show up here. Also, we don’t currently have guest access to the wireless network, so this is Carleton folks connecting.

  • 944 Mac OS X
  • 915 Apple iPod, iPhone or iPad
  • 640 Microsoft Windows Vista/7 or Server 2008
  • 340 Mac OS X Lion
  • 133 Generic Android
  • 69 Microsoft Windows XP
  • 26 OEMed Wireless Router
  • 11 Slingbox
  • 11 DD-WRT Router
  • 9 Ubuntu 11.04
  • 9 HP Printer
  • 8 LaCie NAS
  • 7 Samsung Android
  • 7 Playstation 2
  • 5 Nokia Internet Tablet (udhcpc client)
  • 5 Android Tablet
  • 3 Ubuntu/Debian 5/Knoppix 6
  • 3 Motorola Android
  • 3 Debian-based Linux
  • 2 Xbox 360
  • 2 OS/2 Warp (actually BlackBerry, I think)
  • 2 Microsoft Windows 8
  • 2 Gentoo Linux
  • 2 Epson Projectors
  • 1 Symbian OS
  • 1 Fedora 15 or 16 based distro
  • 1 Chrome OS
  • 1 Brother Printer

Coming after the recent Chronicle of Higher Ed article on how Tablet Ownership Triples Among College Students (apologies for the pay wall), it’s very interesting to see iOS connections outnumber all Windows connections.