Idea I hope will become trends: ask for what you want

In the final installment of my ALA Annual faux-cap, I want to talk about asking for what you want.

The previous installments: user stories, communication, and assessment.

The last session I went to in Anaheim was a panel discussion about how ILS vendors were planning on dealing with the challenges and changes that RDA's implementation would inevitably cause.

When the moderator opened the floor for Q&A, a very different discussion erupted. Basically, the audience called the vendors out on their shenanigans.

Because, while the vendors had, indeed, made provisions for new MARC tags, it didn't seems as if they had really given much consideration to what a post-MARC world might look like. And that's a problem.

The discussion was...lively. Catalogers want tools and mock-ups of what a RDA-driven, post-MARC catalog might look like. ILS vendors don't seem to want to create even a beta version of such a catalog until the landscape is more stable.

What seemed most shocking to the catalogers in the room was that vendors seemed surprised that catalogers were even interested in such mock-ups. And their defense seemed to be that until and unless catalogers make their wishes known, vendors can't create the tools that catalogers want.

It seems to me like ILS vendors and libraries are having a stand-off. It's like they're playing chicken about how metadata will be represented in this post-AACR2, post-MARC world. Libraries are waiting on vendors who are waiting on libraries.

My observation about this stand-off is that if you want to affect real and lasting change when it comes to vendors, convince the people in your organization who sign-off on paying the bills that what you value is worthwhile.

So, my last and final takeaway is to ask for what you want.

At your own institution, talk to your Systems staff and UL about what you want users to be able to do with the metadata you're creating. Find products or dream up solutions to make these dreams a reality. Talk about what makes this metadata so important for users--for searching and retrieving items and for serendipitous discovery--and what would be so devastating for your users about outsourcing cataloging or accepting sub-par vendor-generated MARC records.

At conferences, visit the vendors your library works with. Ask them tough questions about what they're doing to move toward a post-AACR2, post-MARC world. Tell them what you want your users to be able to do with the metadata you're creating and ask them how they plan to make that happen. Talk to them about task forces and committees you know exist where libraries and vendors intersect and ask them what they're contributing to them.

Find your tribe and get involved. Join your state's library association or ALA. Or both. Join a committee or an interest group that's tackling these issues and get to work. Start learning to code and come up with your own solutions to these problems. Use social media to find like-minded folks and start learning about the issues.

To quote Rage Against The Machine:
"It has to start somewhere
It has to start sometime
What better place than here?
What better time than now?"

Be visible. Be proactive. Be awesome.

Ideas I hope will become trends: assessment

This series is, at its core, a recap of my trip to ALA's Annual Conference in Anaheim. But I prefer talking about the practical applications of what I learned to simply recapping programs.

The first installment was about user stories and the second was about communication.

The third installment is about assessment.

I was not planning on attending LITA's Top Tech Trends panel. But, I returned back from an off-campus lunch too late to attend the session I'd hoped to catch and too early for the next round of programs.Having found myself with a few minutes on my hand, I decided to catch a few minutes of the program.

Meredith Farkas was one of the panelists and I found myself nodding in agreement when she talked about how academic libraries can't really stand on the assertion that the library is the center of the academic community anymore. Instead, academic libraries are being asked to justify their impact on those they serve.

Farkas suggested that assessment tracking tools were a good way of managing data that would help libraries build stories of user impact.

But this isn't so much about what Farkas had to say as it is about what people had to say about what she had to say.

It seemed like the Twitter backchannel was musing about how difficult it was to cultivate the kind of organizational culture that breeds an interest in assessment. Basically--nobody teaches this kind of stuff in library school.

The thing is, I couldn't agree more with the notion that academic libraries are being asked to justify their impact on those they serve. It's no longer enough for them to say that they're the center of the academic community. Researchers, both novice and expert, are finding other sources for information than traditional library resources. And many academic libraries grapple with how to stay at the center of the campus community--a completely different challenge.

And I also couldn't agree more with the idea that data helps libraries build stories about their impact on the lives of users.

And, while we're at it, I also couldn't agree more with the idea that creating that kind of organizational culture is really, really hard.

But it's not impossible.

So, how do we do it? How do we create organizational cultures in our libraries that embrace assessment and the data it generates?

I think we start by shifting our focus toward things that are measurable. Which means that every project or program needs to have outcomes built into it during the design phase. How else will we know if the project is successful? And, in the case of programs, how will we know if the audience has learned what we'd like for them to learn?

Academic libraries need to think critically about how adopting this kind of culture could affect them for the better. What would it look like to have data supporting your assertions about how bibliographic instruction sessions have prepared student researchers for upper-level research? It's one thing to consider gate count (which is valuable data, indeed), but it's another to show how you've created good consumers and stewards of information.

I think it's equally important for user-centered back room folks to generate, synthesize, and store data as well. If it's true that academic libraries are being asked to justify their impact on the academic community, it's equally as true that many units performing back-room functions are being asked to do the same. And, when the day comes that you have to advocate for your job, it's much easier to do so using data.

So, try gathering some usage statistics after you finish a cataloging project. Did usage of a hidden collection go up after you added it to the catalog? Did analyzing that serial prompt more people to use it? This kind of data collection can help justify some of the most important work you're doing.

Alternately, though, data of this kind can help you decide what to let go of when budgets are tight and time is fleeting. You can see what your users value most and what they can live without and make decisions about resource allocation accordingly.

So...start with an outcome and measure your success accordingly. And let the data do the talking.

Be visible. Be proactive. Be awesome.

Ideas that I hope will become trends: communication

If you missed the first post in this short series, you can catch up here. The first post was about user stories and focused on a presentation that I saw at the Heads of Technical Services IG meeting.

The second idea that I hope becomes a trend is open dialogue between catalogers and, well, everyone else. The genesis of this was a bullet point from the presentation that Scott Piepenburg gave at the Competencies and Education for a Career in Cataloging IG meeting.Piepenburg's presentation was about what Catalogers would need to be able to do in a post-AACR2, post-MARC world. One thing that he suggested is a must is that Catalogers need to not only understand what their ILS can (and cannot) do, but they must also be able to communicate these limitations to others.

It took everything I had not to jump for joy or to stand on my chair and cheer. I didn't, though. It was a small room and kind of crowded.

I think that catalogers do a pretty decent job of understanding the limitations of our ILSs. We spend a lot of time working with them and, as a general rule, get what they do both well and poorly. Where it breaks down, sometimes, is communicating this information to our colleagues. Whether it's our colleagues in IT or our colleagues staffing the front lines, it is our job to communicate well with them.

Having a basic knowledge of coding can help us communicate more effectively with IT staff. We don't have to be coding wizards, but we should be able to talk about how our systems do parse out data in MARC records and, perhaps more importantly, how we wish they did.

Having a basic understanding of how users search for information can help us communicate more effectively with front line staff. We don't have to spend a lot of time on the Reference Desk (though it wouldn't hurt), but we should be able to talk about how users can do more effective searching.

So, how do we become better at communication with others? I have a couple of ideas:

• If you want to learn the basics of coding, Codeacademy can help. They even have a program called Code Year which will walk you through the basics of languages like Javascript. And if you're looking for support, there's a CatCode wiki whose function is to support dialogue between coders and catalogers. In this case, I suspect it's a lot like learning the language when you visit another country. You don't have to be proficient in it, but the natives appreciate that you're trying to speak their language.

• Attend (open) meetings in departments other than your own. At my former place of work, there was a monthly meeting of subject librarians that was open to all interested staff. I didn't go every month, but I tried to go fairly regularly. Attending this meeting helped me understand the challenges that subject specialists faced when helping users which, in turn, helped me think differently about the work I was doing. This meeting was also sometimes the only way that I learned about issues that I could help solve but that nobody thought to tell me about--not because they were trying to leave me out of the loop, but because they didn't realize that the problem could be solved.

• Get your hands dirty in projects that involve other departments. Though the bulk of my job duties involved cataloging, I taught in my former place of work's Freshman Writing Seminar. I also worked with our Digital Library Services unit and our Web 2.0 initiatives. I made valuable contacts and learned a lot about what other people the organization do. 

I think the moral of the story is that it's all about relationships and empathy. Learn to speak the language of the people you work with. Be friendly and empathetic and take the time to answer questions that your colleagues have about the work that you do. 

What are your suggestions about developing rapport with other units? How have you opened the lines of communication?

Be visible. Be proactive. Be awesome.

Ideas that I hope will become trends: User stories

One thing I have learned after attending ALA's midwinter and annual conferences is that, if you pay attention, you can spot the beginning of trends. Is there more than one program on a particular topic? Consider it a trend. Is it an idea you've heard at multiple programs? Consider it a trend.

And one thing I've preached is that after you spot a trend, you have to figure out how your library is going to deal with this trend. Maybe you find a way to implement a trend into your library's operations. Or, maybe you consider a trend and decide it's not for you. But either way, you have to consider it.

At ALA's Annual Conference, I noticed a few interesting trends that are worth considering. Over the next couple of days, I'll write about these trends--starting with the idea of user stories.

Okay, so let's talk about user stories.

If you're familiar with software development, you're probably familiar with user stories. Essentially, you interview users to find out what they need a piece of software to do. These stories inform the software's design process. It's an opposite way of thinking than the usual business of most libraries which is to offer solutions that they think will meet a user's needs.

I attended the Head of Technical Services IG and heard about how the University of Chicago used user stories to inform the catalog design they worked on. They conducted 20 interviews and, from those interviews, they identified 200 unique stories. These stories fell into categories like browsing, composition of full records, and integration with other tools.

I like the idea of integrating user stories into any major design or redesign of a library resource. Libraries often believe that they know what their users want a piece of technology to do. Whether it's a citation manager or the library catalog, we think that we know how users work. And many times, we can bring anecdotal evidence to support that. Sometimes we even do usability testing to choose between options we've identified. But none of these things give users a voice during the initial phase of designing a resource or deciding which resource to purchase. Often, by the time we ask our users for their $0.02, the decision has already been made. And we try to do our best to help users live with the decisions we made by training them on how to use the resource we've purchased. But how many times have you taught a class on a piece of technology and had to tell someone that it doesn't do what they really want it to do?

How would things be different if we let the users tell their own stories and then found ways to solve those problems for them?

We might make different choices about the technology we decide to purchase and we might find open source solutions that meet our users' needs better than vendor-supplied solutions. 

We also might start asking for more from our vendors in the way of flexible implementations. Rather than purchasing the solution that comes the closest to doing what we think our users need it to do, we can approach vendors with evidence that we need them to provide implementations of solutions that do what our users actually need them to do.

So...now that you know what a user story is and have heard about someone doing it well, how will you integrate this trend into your library? 

Be visible. Be proactive. Be awesome.