Highlights and Lowlights

I’m still processing my thoughts after CIL, and I’m sure this won’t be my last post on the issue, but I thought I’d just give a quick thumbs up and thumbs down list.

Thumbs down (first so I can get it over with):

  • Arlington doesn’t seem to have a blue sky. I’ve only seen clouds. Does the sun ever shine there?
  • Vendors who clearly haven’t heard what we’ve been saying for years. C’mon people. We aren’t trying to be mean when we question your relevance ranking algorithm or your obsolete file structure. We’re just frustrated. And nothing’s changing in any fundamental way.

Kinda in between:

  • Wireless that doesn’t work. In all fairness, ITI clearly tried very very hard. There was a whole lot more connectivity than there has been at previous conferences. Unfortunately, all of our bandwidth needs have also increased and so we crashed it… regularly and with frequency.
  • And for all the guff people gave for new ideas that didn’t work (you know the ones), I think it’s great that ITI is really working to make sure this conference structure and logistics move forward with the times. It’s regrettable that many of these experiments flopped in a big way, but a track on open source and a track on new user interfaces were two great steps forward.

Thumbs up (to leave you with the good stuff):

  • The people the people the people
  • More accommodations for the laptop laden (a blogger’s row in the front of every room, complete with power strips. Yay for power strips!)
  • Watching the stenographer at work. I had no idea they did that!
  • Pecha Kucha!!!!

And even though nobody else will care, here are the top in-jokes from this year (feel free to comment with those I’ve left out):

  • One-eyed pink bunnies.
  • “Libelous and slanderous”
  • “I’m late for choir practice”
  • “Hookers and blow”
  • “I hate technology”
  • Lobby 2.0

[Edited to get the right things into the right categories. Thanks, Greg, for the heads-up. Advice to all: never blog when this sleep-deprived, no matter how much you think it'll be fun and easy.]

Technorati technorati tags:

Identity, Community, and My Not-So-Virtual-Friends

Without a doubt, the best part of this last week has been meeting all those friends which up until now, I’ve called “eFriends.” I’ve known some of these people for 3 years, but never yet laid eyes on them. In many ways, this has been like what I always imagined a really good class reunion would be like. We already knew what everyone had been doing recently. We knew each other’s interests, fears, and aspirations. We’ve been there for highs and lows. And now, at long last, we know each other’s in-person mannerisms.

Now I wonder, will things go back to the way they were online or will they change? And if they change, what will that change look like? Will we be even more comfortable with each other, or will we become shy now that the subtle protection we’ve enjoyed so far, that cloak of safety in the knowledge that our companions know us but don’t know us? Of course, I hope things will be even more rich and wonderful, but I was surprised to look around one night and wonder if I was becoming shy now that people knew my mannerisms and expressions. “Will they still like me?” I couldn’t help wondering.

But all of this made me wonder again about these online personalities we have. We all bridled a bit when somebody expressed concern during the LSW presentation about the anonymity of screen names and wondered how true community could form in an environment that depends on screen names. And I firmly believe that communities do form in these environments. I’ve felt it. I’ve lived it. But I haven’t decided yet if that kind of community can be the same as a face-to-face community.

I can’t wait to see what does change, and what stays the same. But whatever happens, I’m confirmed in my opinion that these are amazing people. They make me proud to be a librarian and excited for the possibilities that can become reality with people like this put their minds to it. And I’m already pining just a little and wishing I could pop down to the lobby to hang out with the gang.

Technorati technorati tags:

The Story of My Profession

Well, this is a first. I fully intended to blog, twitter, upload pictures to Flickr, and do all the other things I’ve done at every other conference I’ve attended in the last 3 years. But a combination of technical and social factors have gotten in the way. Lack of reliable internet is a perennial problem at CIL. (This year they seemed to have made a concerted effort to improve… but the wireless routers kept failing and kicking whole rooms full of people off the network.) And this year I discovered that if you know a lot of fun, cool, engaged, and social people, you might not get a whole lot of one-on-one time with your laptop. This I take as a wonderful thing, and I had the best time meeting the majority of my until-now-only-virtual friends (more on this in another post). So the upshot is, I’ve spent every moment so far either fighting with wireless connectivity or actually talking with people, not blogging… not uploading photos (or even really taking photos… sorry), not even twittering a whole lot (my phone doesn’t do the whole web connectivity thing, either, and I just don’t want to pay for a conference full of twitterers’s ideas 10 cents at a time). Does this mean I have to hand in my 2.0 credentials?

Ironically, this lack of communication directly contradicts what I think has become the unofficial theme of this conference: telling stories. A few sessions have mentioned this theme explicitly (I’m thinking particularly of the Day 2 Keynote, presented by a trio known affectionately in these parts as “the Dutch Boys”). But even when presenters didn’t actually talk directly about story telling,they’d stir our interest by invoking stories of their own. Who wasn’t captivated by the clip from Mary Poppins in the Day 3 keynote? Who didn’t love Greg Schwartz’s fairy-tale-turned-Pecha-Kucha talk?

I found this underlying focus on Story compelling. At its heart, Story requires interaction, communication, and therefore community. I’ve also found that narrative stirs some deep and vital part of people. We’ll believe a narrative that hangs together even without the “evidence” that we train ourselves from school onward to interrogate. And we’ll often remember evidence-based narratives but forget all the actual evidence itself. On the flip side of that, facts without a narrative to tie them together are just about the epitome of “boring” and “forgettable” for me. And what’s more, Story is fun! It taps into the not-work-but-fun part of my psyche and sets my default mode to trust and enjoyment rather than skepticism. (Why do you think it takes so long to teach students to read fiction critically?… because it’s made up of good stories.)

All this talk of Story has inspired me to be on the lookout for the narratives we present and narratives we could present to our communities. I know we do, and we often even do it intentionally. I’m just interested in being mindful, myself, of the power of Story for my library.

But I actually think it should be more than just an inspiration. I think this idea of Story should be a great comfort to those who feel forced to think that the only way forward is to obliterate everything on which libraries are built. Quite the contrary. Our history of service and of meeting our community’s needs is fundamentally part of our story. It’s the part that’s implied when we start in medias res. It’s the part that sets the stage when we begin “once upon a time.” It’s the part that, if forgotten, renders the rest of the narrative stilted, limp, and ultimately boring. Moving forward is the rising action of the story, not a new story.

Technorati technorati tags:

Getting ready for CIL

I spent the morning tweaking my twitter account to be useful while I’m at CIL. I won’t be publishing my tweets here, but if for whatever reason you want to keep up with what I’m doing (whenever the notoriously spotty conference wifi will allow me onto the network, that is) you have two options: follow me on twitter or subscribe to my twitter feed.

Of course, I’ll be blogging as usual. I usually write a post or two each day pointing out the highlights of what I saw and learned. I don’t usually blog conference session notes, but plenty of other people do, so search Technorati for the tag cil2008 and I’m sure you’ll find all the session notes you need. (By the way, that same tag will work for Flickr and del.icio.us and a whole host of other tag-searchable things.)

Technorati technorati tags:

Becoming a Librarian for Languages

When I first started this job, I knew there was a lot I didn’t know about the unique needs of the different departments I’d be serving. I knew that typical research needs varied by discipline, and that I’d be serving three broad disciplines: languages, literature, and music. But I’d never done research in language or music courses, so I didn’t know what that kind of research looked like, or what it would need from me. So I made a plan. (I’m a planner, what can I say.) My first year, I’d just keep my head above water. I’d learn to teach, learn to work at a reference desk that actually got real reference questions (not the case at the two placed I’d worked during library school), and concentrate on not making a fool of myself. The next year, I’d figure out what it means to serve language departments. And the next year I’d figure out what it means to serve the Music department.

Needless to say, my plan didn’t go quite that tidily. But in general, I did concentrate on peering under the hood of a different discipline each year. I’ve already written about some of the things I’ve learned about being a Music librarian, so I thought I’d share a bit about what I’ve learned so far about serving language departments.

Time is of the essence:

I spent at least a year being frustrated when professors of languages would ask me to please come teach everything there is to know about the library, and please keep it to 15 minutes. At first, I thought I needed to practice those skills you learn about in library school and at ACRL’s Immersion program and say, “That won’t be possible. If you give me 45 minutes here’s what I can cover.” It turns out, though, that in this particular instance that is not always the best strategy. Sometimes, sure, if the project facing students is a major research paper, or if the class is not (as they often are) focused on language and simply using a research paper as another way to gain facility with that language. But if the course’s primary goal is to move students toward language fluency, then the teachers are under a massive time crunch. They know that they’re racing the clock to expose their students to the number of hours of instruction it takes to achieve fluency in a language. And yes, it’s measured in hours.

Here is the chart that a group of language faculty presented this fall as part of their ongoing discussions about curriculum review. Notice that for the Category I languages (like French) it takes 575-600 class hours to achieve basic fluency. For the Category III languages (like Cantonese) it takes 2200 class hours to achieve fluency. (Source, the National Virtual Translation Center which takes some information from the Foreign Service Institute.)

With time to fluency ticking away, an hour of library instruction (delivered in English) is just too costly. So the faculty and I have started coming up with solutions that don’t involve me jeopardizing their instructional goals. I sometimes come and give a 15 minute overview and a handout that prompts students to ask me questions. Then they come to visit me in my office, singly or in groups.

Sometimes that option would eat up all of my time, so I ask for two or three 15-minute chunks of time with the class spread out over several class periods. The end result is that I’ve taken more of their precious class minutes, but this way students don’t go for an entire session without hearing their foreign language of choice so it doesn’t seem to derail instruction as much. It’s always a balancing act: the relative worth of my time balanced against precious classroom minutes.

What Language Students Need from Me:

Depending on the assignment, this changes, but language students need a couple of tips that no other students need. For example, when searching in a given database, should you search in English or in the foreign language? If searching in the foreign language, does it matter if you use accent marks or other non-standard-for-American-writing characters, or will the system understand that e may mean é? Since search is basically character matching, these questions can make the difference between relevant results and no results at all, so I’ve started including them in the research guides I build for those students (example).

At a library the size of Carleton’s (good sized, but not like a large research university’s library), language students also need to know how to interlibrary loan materials. I always tell them that in these classes, they MUST search and order ILL items early. Once that’s done, then they can procrastinate as much as they like. Every term a few students don’t realize how very serious I am about this point and end up having no good sources to work with.

So that’s the big stuff

Other than that, I’ve learned from working with my language students how to give up the mouse and keyboard while doing searches. There’s nothing like trying to scan through a result list in German, or brainstorming for Chinese search terms to encourage me to say, “Here, you take over and tell me what you see. … Now, do you see anything on the page that looks like….”

I used to be completely intimidated when contemplating my work with language classes. I felt uncomfortable standing in front of a class and knowing full well I couldn’t speak the language or even pronounce the example search terms we were using. But after a couple of years, I think these experiences have taught me to be more comfortable with the idea that I can contribute to student learning without any grounding in the subjects their studying.