Showing posts with label users. Show all posts
Showing posts with label users. Show all posts

Wednesday, July 26, 2017

This is a story about control

One thing that the Unified Library Scene has always been about is understand the needs of your user community and responding to them. When reading the most recent Ithaka S+R issue brief, Rethinking liaison programs for the humanities, I was once again reminded of how central listening should be to the work we do in libraries.

I was fascinated by the idea that their projects are "scholar centered." The authors describe their centering of researchers by saying:
we do not ask scholars how they engage with library services, collections, or employees but rather in a more open-ended way what their experiences and practices are like as researchers. Our intention is not to evaluate the "efficacy" of liaison services as they are currently organized but rather to determine what services if any may be needed.
This idea of asking scholars about their processes really resonates with me because it centers the user and decenters the library. Instead of asking "how good are we at meeting your needs?" this process asks "what are your needs?" Instead of asking scholars to do the work of figuring out how to structure the services the library should be providing, the work of mapping the efficacy of services happens when trying to reconcile scholar needs with current service offerings.

This methodology is perhaps easier for Ithaka to undertake than many individual academic libraries because one imagines that they don't tie the answer that a respondent gives to the work being done in the organization those respondents represent. If you talked to the libraries that serve those respondents, they may not feel as comfortable with the scholar centered approach because they are invested in making sure that they are doing the best possible job of meeting the needs of the faculty they serve. And in the end, scholar centered approach requires a flexibility of thinking and a willingness to give legacy services up in order to take on new, more useful services.

Later in the issue brief, the authors talk about how because humanists are often working in sub-disciplines, they don't see their liaison librarian as an expert they can include as a collaborator in their research process. The authors explain:
Even if, as appears to be increasingly the case, subject specialists have advanced degrees in the relevant subject area, subject expertise at a discipline level is not what is being sought. Rather, for research support humanists are looking for engagement at the level of their own sub-discipline, which is rarely available through the library.
That was really hard for me to read, and I don't liaise with scholars.

It's dangerous to think of any user community as a monolith, so what happens at any given academic library might not scale. But I still think this is really valuable insight. I think that academic libraries and the workers who staff them spend a lot of time trying to foist services upon scholars who may not need them and then internalizing the failure they feel when they aren't able to build the kind of relationships they wish to have with the scholars in the academic community. It isn't that those scholars don't see the library as valuable--the authors of this issue brief are very clear that they do--it's that they don't see us in the way that we may want to be seen.

We spend a lot of time in academic libraries evaluating the services we provide our users. And I do think it's valuable to measure the efficacy of the work that we're already doing. But I think what this issue brief points out to us, separate from its findings, is how important it is to have a user centered orientation that comes from truly engaging with your user communities, knowing how they work, and identifying ways in which your work intersects with theirs in an authentic way.

Stay positive,
Erin

Tuesday, April 4, 2017

How it feels when we fall, when we fold

The Ithaka S+R US Library Survey for 2016 was published yesterday and if you're a person who works in academic libraries, it is definitely worth a look. What caught my eye was a chart fairly early in the document--Figure 4. Figure 4 compares the responses of library directors and faculty members to the following question: How important to you is it that your college or university library provides each of the functions below or serves in the capacity listed below? 

What emerges when you look at that table is that what library directors see as valuable roles for the library to play don't necessarily converge with what faculty members see as valuable roles for the library to play. I suspect this isn't surprising if you work in an academic library.

I noticed that the categories that received a larger percentage of positive responses from library directors seemed to be centered around they ways in which the library helps develop information literacy skills in undergraduate students how the library supports faculty with teaching and research activities. And the single category that received a larger percentage of positive responses from faculty is centered around the library paying for resources in all formats.

While I am wary of asking charts to do things they are not intended to do, it is interesting to see these different visions of the library juxtaposed.

Academic libraries invest a lot of resources into marketing and outreach in an attempt to sell our campus communities on the library services that I mentioned in the earlier paragraphs. We set up departmental office hours. We print flyers and create digital signage to market the services no one seems to know about no matter how often we remind them. We hold open houses. We have orientation sessions for new students and faculty. We try, through marketing and outreach, to get other people as excited about this version of the academic library as we are.

And we wring out hands when our efforts don't cultivate new relationships or lead to the more widespread adoption of new services.

This is not to suggest that these outreach efforts are misplaced. Teaching faculty aren't a monolith and some of them are as excited about our vision of the academic library as instructor of students and supporter of faculty activities. Some of our teaching faculty colleagues are, indeed, our strongest supporters and our best allies. And it is absolutely true that the best way to establish new relationships with teaching faculty by way of a satisfied faculty customer.

But I do wonder how much of our marketing and outreach efforts could be better spent by listening to our teaching faculty colleagues on our own campus and developing a shared vision of what the library on our campus should be--even when that vision isn't exactly what we think it should be.

Creating conversations between the academic library and its user communities is really challenging because it asks us to stop putting our vision ahead of the needs of our user communities. And when the vision that is reflected back to us by our user communities is not where we think we should be heading, we have to decide whether to chart a new course or not. It's scary, we think, because our user communities don't understand the history of the academic library. It's scary, we imagine, because our user communities couldn't possibly know what they need better than we do.

But in the end, the way to build an academic library that is not only useful on a campus but creates experiences for our user communities that is transformative is to listen far more than we speak.

What is one way that you can listen to your user communities about the library they want and need? Tell me in the comments!

Stay positive,
Erin


Thursday, January 5, 2017

You've seen it all

Earlier in the week Jacob Berg, friend of the Unified Library Scene, made a point about SciHub as a phenomenon.
I chewed on this idea for a couple of days and yesterday I had a tweet storm that I ended up deciding needed to be a blog post.

The thing that I kept turning over in my mind is that libraries implement a lot of solutions and workflows meant to help their users that were created without actual user input. And while I applaud the impulse that librarians have to implement systems, structures, and tools to help library users, I do think that excluding them from the design, development, and testing phases is a little short-sighted. Especially because our best intentions lead us to crate things that require that we create research guides and tutorials in order for them to be useful to our end users.

I feel like this impulse to exclude the user from the design, development, and testing phases of a library resource or service is a holdover from the time when librarians were both literal and figurative gatekeepers within the library. For many years, we've stood at reference desks and in classrooms as the sage on the stage, teaching people how to access the information that we have acquired and described. And while this was probably never a good idea, it definitely isn't how people interact with information anymore. Regardless of how you feel about the document, one of the things that ACRL's Framework for Information Literacy in Higher Education really crystallized for me is that information comes from many places at this point in time--not just the library--and an information literate person knows how to make the most of information in whatever place they find it.

So if being a useful library isn't about being a storehouse full of information kept safe by a gatekeeper, it seems like we should invite our library's users to become co-creators of the systems, structures, and tools meant for their benefit. To do that, though, we have to understand--really understand--what our users need and want. And in order to understand what our users need and want from us, we have to listen to them. And I don't just mean conducting an annual State of the Library survey. Yes, those surveys are good for getting a broad picture of what your user community things you're doing well or doing poorly. But you're wasting your time if you don't use that information as a jumping off point to gather additional, more targeted information.

I think you also have to engage your user communities in more direct ways. Host focus groups with your user communities. Show up at meetings in your community and get to know their actual concerns. Hire an anthropologist to teach you how to conduct effective observational studies to understand the habits of your user communities. And as you engage your user communities, listen more than you talk.

And, yes. When you listen to your user communities they're going to hurt your feelings by telling you about how your tools and processes are hard to use. They're going to tell you that you aren't relevant to their life and you don't meet their needs. You know what? Listen to that feedback and sit with your discomfort, but don't take it personally. Hear what people are telling you about what they actually want, what they actually need.

And yes. When you listen to your user communities, you're going to have the urge to tell teach them something that it would easier to use a particular service or tool. You're going to want to say, 'using [x] would be easier if you only knew [y].' I get it. You want to make things easier for them. But resist this urge, because your user communities aren't broken. What they're telling you is that if you have to tell them [y] in order to effectively use [x], then it isn't a good solution.

True engagement with user communities is hard. But creating structures, systems, and services intended for their use without their input is a waste of everyone's time and resources.

Stay positive,
Erin




Tuesday, December 13, 2016

You're all alone and so peaceful

So, I want to talk about our tendency as librarians to over-market our services as a substitute for listening to what our users really need from us.

An opinion piece on Forbes' site discusses the how a combination of Big Data and information literacy can create a more informed citizenry--one that can identify fake news when it sees it. It's not an objectively terrible take on the idea of fake news and what can be done about it. There is a part that gave me pause, though. The author begins the closing paragraph of his article by stating "...we see that fake news exists because as a society we have failed to teach our citizens data and information literacy."

I feel like Michael Bluth speaks for all of us here...


Okay, but also yes.

I should start by saying that I believe that librarians have thought a lot about what it takes to create information literate people. I should also say that I believe that those among us who have taken on reference and instruction roles go about the business of creating information literate people in really thoughtful ways. If you want a thoughtful take on information literacy in an age where people believe that truth is relative, I highly recommend that you take a look at what Kevin Seeber has to say about how creating information literate people is more complicated than just teaching people that this source is good and that one is bad. I think that Kevin makes a well-reasoned, thoughtful argument. You should read it.

As a metadata creator, I spend relatively little time thinking about information literacy and about creating information literate people. But I do spend a lot of time thinking about whether (and how) our collections and services resonate with our user communities. I feel like one of the things that librarians do when confronted with a message like the one in the Forbes article I linked to is freak out and double down on their outreach and marketing efforts. If people can't see how hard we're working on [insert a topic here], that's a failure on our part to market our services well. We must not be doing a great job of making people aware of our tools and services, librarians think. so we need to work harder to connect with people. But sometimes the answer isn't another research guide or more table tents. Sometimes people don't notice the work being done by librarians on [insert a topic here] because we believe we know better than our users what they need to be successful.

Librarians talk a lot about The Future of Libraries: how can we invent our collections, services, and tools to maintain our relevance? I would argue that the best way for us to meet the future is to stop acting like gatekeepers of information in both a literal and figurative sense and to start spending more tine in conversation with our user communities learning more about their needs and thinking critically about how we can meet them. Having those conversations means having conversations with the people who are your most regular customers and those that you feel most comfortable around. But having those conversations also means talking to people who never set foot in your doors and those who make you feel the most uncomfortable. And most importantly, listening to your user communities likely means that the decisions you make will go against what you believe as a self-appointed gatekeeper.

I get why it's easier to choose yelling louder and louder over listening. It's easier and more comfortable and it allows us to remain comfortably in this notion that librarians know best. But the louder we yell, the more we become background noise. So let's stop yelling and start listening.

Stay positive,
Erin






Tuesday, November 15, 2016

Mountains grow from just one stone

One of the things that I talk about over and over (and over and over) again on the blog is the idea of imagining what it would be like to center the lived experiences of our user communities when it comes to creating metadata to describe our collections. I was thrilled when a friend, Anna-Sophia, sent me a link to the transcript for a 2015 talk by Sara Wachter-Boettcher called "Everybody hurts: content for kindness."

The talk centers around this idea:
And what I've come to is there's an opportunity that we have to make every decision an act of kindness. Make sure everything we write, everything that we build, come from a place of kindness at its core.
Wachter-Boettcher goes on to talk about how this mission of centering kindness can be lived in when it comes to better understanding both the needs and the triggers of our user communities. While the audience of this talk wasn't those engaged in the work of libraries or librarianship, I can get behind this premise for librarianship in general and metadata creation more specifically. I spend a lot of time wondering how metadata creation would be different if those of us who create metadata saw it as not just an act of service, but also as an act of care for the user communities that we serve and support. And then I wonder why we don't.

I was struck by something that Wachter-Boettcher referenced early in her talk. She made mention of an address given by Paul Ford, in which he states:
If we are going to ask people in the form of our products, in the form of the things we make, to spend their heartbeats--if we are going to ask them to spend their heartbeats on us, on our ideas, how can we be sure, far more sure than we are now, that they spend those heartbeats wisely?
And I think that this quote is at the center of why we don't always see metadata creation as an act of care, and why we should.

I worry that we take for granted that users will spend their  heartbeats using the collections and services that we offer. I especially worry about this in academic libraries where students and faculty require access to scholarly resources in order to conduct research and create scholarly works. As this applies specifically to metadata creation, I worry that we take for granted that user communities will have to use the library catalog in order to access our collections. As many people wiser than I have pointed out to me when I try to reckon with this mindset, it's a direct holdover from the time when our collections were kept in closed stacks and library workers were the gatekeepers to these collections. It's also a significant conflation of the catalog as both the content and the carrier--a thing that I do all the time and which my wise friend, Kyle, regularly holds me accountable for.

So what would it look like for those of us who create metadata to describe collections to choose to put kindness at the center of our work? First and foremost, I think that we should stop taking our user communities for granted and create software systems and rules for description and encoding that respect the lived experiences of our users. While I don't agree with the idea that people in Technical Services are change averse, I do think our public services colleagues have been quicker to see the ways in which the needs of our user communities are changing and then responding. Second, I think it means evaluating our local policies for metadata creation and remediation and amending them in ways that have the biggest impact on our user communities.

I don't think that evaluating our metadata reuse policies means we have to stop reusing metadata. For some materials, records don't need a significant amount of customization. And for smaller libraries, metadata reuse is the only way that their cataloging operations stay afloat. But I do think it's worth considering which types of material and which subjects are important enough to your users to provide the extra care of customization. Especially if the library for which you are describing collections has made diversity, equity, and inclusion a priority.

I think that many people who create metadata would tell you that the work they do is a public services. I think what is important for us to be explicit about is that we have the choice to treat our work as an act of care for the user communities we serve. I think it's time for us to think more about what it would mean for metadata creators if we thought about making sure that our user communities were using our heartbeats wisely when they accessed the metadata we create.

Stay positive,
Erin








Tuesday, November 8, 2016

No firm ground, but we ain't sliding

The Policy and Standards Division of the Library of Congress decided for a second time to reject white privilege as a subject heading. You can read their decision here. The part of their argument that is most salient to this blog post is: Numerous works about white privilege have been assigned the headings Race discrimination and Whites--Race identity, and the meeting wishes to continue that practise.

It is both completely understandable and completely perplexing that the PSD would reject this heading despite the fact that literary warrant exists. On the one hand, if the PSD believes that a combination of existing subject headings is sufficiently describes a concept they can make the argument against adding another subject heading to the thesaurus. On the other, it seems like the combination of subject headings that the PSD points to in their decision misses the mark.

When reading this decision, it seems like the PSD fundamentally misunderstands the concept of white privilege by deferring to the headings already being used. The idea of white privilege implicitly touches on discrimination and race identity to the extent that the privileges extended to white people as a result of their identity further margainalizes people who aren't white. But white privilege is not explicitly about either of those things. April Hathcock wrote a really great blog post about this which I think it well worth your time. In her post she writes " Privilege isn't about discrimination; it's about the automatic benefits and advantages that come from living in a system set up to value the lives, ideas, and expressions of one group over all others. You may be a staunch antiracist, but if you are white, you are steeped in WHITE PRIVILEGE. It is a reality of living in the systemic bias of our society."

Thematically related to this discussion of white privilege and systemic bias is Jarrett Drake's keynote address at the Digital Library Federation Liberal Arts Pre-Conference titled "Documenting Dissent in the Contemporary College Archive: Finding our Function within the Liberal Arts." In this address, Drake states
I doubt many of you here know about this history of black college and universities in this country, and I have that doubt for many reasons. The first is that most of you are white and can afford to be ignorant of blackness. The second is that many of our library and archive consortia--this one included--excludes our librarians, libraries, archivists, and archives at black colleges and universities, so even when you think you are immersing yourself within the field of librarianship, you remain blissfully unaware that there is a whole different world out there to which you are functionally illiterate. This unawareness is both a product and a reification of systemic racism, and it doesn't require racists whatsoever.
Both Drake and Hathcock point out that even those of us who believe that we are antiracist still benefit from our whiteness and that white privilege affords us the luxury of being able to be ignorant about aspects of blackness. Further, Hathcock argues that the decision not to name white privilege explicitly and add it to the thesaurus perpetuates systemic racism both in libraries that utilize the thesaurus and in the larger arena of subject cataloging.

Working both inside and outside of a system is important when thinking about how to create a more equitable and inclusive library catalog. While asking the Library of Congress to both change its most problematic subject headings and to add new headings to address issues of importance to our users is a key component of pushing back against the systemic racism inherent in our metadata creation standards, I would also argue that we can work outside of/around the system to add subject headings to records which both reflect the lived experiences of our users and the values to which we claim to adhere.  There are a lot of existing subject thesauri and the MARC standards allows you add a term from a thesaurus other than LCSH in field 650. Library of Congress publishes a list of source codes and has at the bottom of the document an example of how to construct a 650 field using one of these alternative thesauri. Additionally, the MARC standard allows you to utilize fields 69x for locally constructed thesauri that aren't on the source code list. So while LCSH is the (seemingly) most widely used thesaurus for published material, it doesn't have to be the only thesaurus a library uses to describe the about-ness of a resource. A particular community of practise could create its own thesaurus and use that to provide access to headings that the Library of Congress has chosen not to address.

I should note that this isn't a new idea. There's a reason that cataloger's love Sanford Berman.

I know I write a lot about how I think we should think about how much we rely on repurposed metadata and on how we should localize our cataloging practises to better meet the needs of our users. And I think that the use of alternative thesauri is a good place for us to do some thinking. As luck would have it, there are a lot of people in technical services librarianship already thinking hard about these issues. As April notes, Jenna Freedman and Netanel Ganin stand out as people whose efforts in this arena should be acknowledged. I am so, so grateful all of the people who speak so bravely and so boldly about the lived experiences of our users and who hold us accountable for the ways in which we fall short of doing right by them.

Stay positive,
Erin


Tuesday, October 18, 2016

Don't look to me for answers

So, let's talk about content standards. More specifically, let's talk about cataloging codes.

Yesterday I read an article from 1991 titled "The pragmatic basis of cataloging codes: has the user been ignored" that surfaced for me the tension I feel about the work that I do as a cataloger. In this article, Jon R. Hufford argues that while modern cataloging codes (those codes created since 1841) have had at their theoretical center the needs of catalog end users, none of those codes appear to have taken into account actual user needs in the creation or revision of those codes. In the article, Hufford cites Panizzi and his Rules for Compiling the Catalogue of Printed Books, Maps, and Music in the British Museum (aka, the 91 Rules) as the person associated with the beginnings of modern cataloging. The article predates the development and publication of Resources Description and Access (RDA) as it discusses various cataloging codes created from 1841 to the revised printing of the 2nd edition of the Anglo-American Cataloguing Rules (AACR2r) in 1988.

The argument that undergirds Hufford's article is that while many of the codes he discusses state (either implicitly or explicitly) that they are attempting to develop rules which facilitate ease of use for library users, their creation excludes actual experiences for users. Instead, Hufford argues that the codes are based either on the experiences of the single person who uses them or, when the codes are created by a committee of people, the collective wisdom of the cataloging crowd.

Hufford suggests that librarians have agreed (generally speaking) that "the catalog's main function should be to enable a user to determine whether the library has a certain item, which works of a particular author are in the collection, which editions of a particular work the library has, and what materials the library has on a particular subject" (35). If you're playing along at home, those functions share a lot in common with the Functional Requirements for Bibliographic Records (FRBR) tasks: find, identify, select, and obtain.

The author ends his article by stating "The accumulated data derived from catalog use surveys which employ valid and appropriate research techniques should be consulted whenever professional librarians consider revising cataloging codes, public catalog arrangements, and/or the content of bibliographic records" (36).

Historically, library catalogs were not meant to aid the user in finding, identifying, selecting, and obtaining library materials. But it seems like as libraries moved over time from being closed-stacks in need of a gatekeeper to open-stacks where users can browse freely, our ideas of how a cataloging code should be constructed stayed the same. And in a world where access to information is increasingly unmediated, the seeming unwillingness to change how we create our cataloging codes mean that our library catalogs are not in danger of becoming relics of a time--but have already gone their. After all, how many times have you heard, anecdotally, that users don't start their search in the catalog? And yes, our content standards are forever enmeshed with our encoding standards and our local integrated library systems. But it's still worth considering how we've shut our users and their behavior out of all of these things.

Given how recently RDA was created and adopted, one might think that this would've provided an opportunity for those responsible for its creation and adoption to think about user needs and behavior. But in her book, FRBR before and after, Karen Coyle writes "For a study that was purported to be user-centric, the user's absence is notable. There is no analysis of users; no mention of how varied the user base is; no mention of children or elders or the disabled. Instead, to my mind, the FRBR Final report reads as a study by catalogers for catalogers" (106). It is worth noting that the FRBR model serves as the basis for RDA.

So, back to the tension that I mentioned early in the post. The description of library materials is meant to be a public service and many people who do this work see themselves as advocates for library users. But I often how can we serve the public when we create records using a standard that seems to advocate for a monolithic user without considering their needs. I don't want my work to go into the ether, never to be used by my library's user communities. And, as I mentioned earlier, the content standards we use to create metadata that describes our collections are forever tied to the encoding standards we use and the local systems into which we place records created using these content and encoding standards.

I feel badly about getting to the end of this post and leaving with more questions than answers, but sometimes an opening to a conversation is a gift. I don't think I'm advocating for scrapping our current cataloging code and starting over. But I do think I'm advocating for looking at our current catalog more critically--about who created it and who it was meant to serve--and thinking about our local user communities in how those cataloging rules get applied in a local context.

Stay positive,
Erin

Works cited:
Coyle, Karen. FRBR before and after. Chicago: ALA Editions, 2016.

Hufford, Jon R. "The pragmatic basis of catalog codes: has the user been ignored?" Cataloging & Classification Quarterly 14, no. 1 (1991).

Tuesday, October 11, 2016

The spotlight is focused, the audience rapt

I am in the quiet space between a couple of writing projects and I'm thinking about the thread that ties the two together.

In the first writing project, I spent a considerable amount of time thinking about how my lived experience acts as a lens through which I view the material that I catalog. In the early drafts of this project, I tried to argue that catalogers should both identify biases and work to push against them in their work. I even used the phrase "eradicate bias." As I wrote subsequent drafts, however, I became convinced that our job as catalogers shouldn't be to work against bias to create a neutral catalog. As many people smarter than me have said, the catalog is not neutral ground--nor should it be. Instead, I thought more about how catalogers should consider their lived experiences more to identify who they are and what privilege they do (or don't) possess. In much the same way that understanding how I benefit from whiteness changes how I move in the world, understanding how I benefit from whiteness changes how I approach the material I catalog.

The second writing project is going to turn my attention toward the ACRL Framework for Information Literacy for Higher Education. I'm interested in thinking about the six frames can serve as a lens through which catalogers can view what our cataloging priorities should be. I'm interesting in thinking about how cataloging work would change if we brought our practises into closer alignment with what librarians doing information literacy instruction are teaching students. My gut reaction at the outset of this work is that bringing our practises into closer alignment means that we will be less able to reuse records from Ye Olde Bibliographic Utility without making at least some degree of local changes. At the outset of this project, I feel like bringing cataloging practises and information literacy instruction practises into closer alignment will result in more work for catalogers rather than less.

I think the places where these two projects (and the thinking behind them) come together is that we need to spend a lot more time considering our local communities and the values that our local libraries embrace when creating and adapting records for use in our local catalogs. We must consider how we will change every aspect of how we work when we decide that our libraries should be anti-racist, anti-sexist, anti-homophobic, anti-transphobic, anti-ableist, and anti-classist spaces. We cannot create inclusive physical library spaces without also creating inclusive digital spaces--and that includes are our library catalogs. We cannot address signage without also addressing metadata creation content standards. We cannot address loan policies without also addressing controlled vocabulary.

I don't resent people for thinking first about how to create more inclusive physical spaces since changing physical spaces has a visible return on investment for users. But not every person who uses the library does so by coming into our physical spaces. For some of our user groups, the library's digital presence is the only way they will interact with the library, so we also need to put some thought into how we will reflect in those spaces the values we profess in our physical spaces. This might mean changing our website's design or creating a local thesaurus of terms that reflect our values more than any of the existing thesauri. But whatever it means, we have to do it.

Making the changes in local practise that bring information literacy practise and cataloging practise into closer alignment will be neither easy nor cheap. And creating inclusive digital spaces will require both financial resources and staff time. We'll have to decide what we're willing to give up to take on this new work and we'll have to have administrative support to move forward. But if creating inclusive physical spaces is a priority for us, we have to think about how our digital spaces will change too.

Stay positive,
Erin

Tuesday, September 20, 2016

Stop! Take some time to think, figure out what's important to you.

Yesterday, I had mentally prepared a blog post for today about assessment and building a culture of assessment. I'll probably still write that blog post, but something else surfaced between the time I'd decided on assessment as a blog topic and the time I put fingers to keys to write this post that made me decide to change up my topic.

Yesterday, author Tessa Dare tweeted:
I totally agree with Ms. Dare and I retweeted her tweet. I added another tweet after hers:
For whatever else librarianship is, I believe it's customer service work. Our job as librarians is to help connect our users with the resources they need. Whether you work the front lines of the library or the back rooms, we all have a role to play in serving our library's users. And like most kinds of customer service work, helping library patrons can be frustrating. I think we librarians would be living in a perfect world if we weren't honest about the fact that every library has problem patrons and difficult situations. But despite what everyone has told you about how library work is reading books all the time and telling people to "shhhh!," this kind of customer service work is what we signed up for when we decided we want to work in libraries.

Knowing what we signed up for, I think it's ill advised for us as librarians to mock, ridicule, look down on our users for the services they use, the material they check out, or how they conduct themselves while they're in our libraries. It teaches people that libraries aren't a welcoming place and that librarians aren't welcoming people. It teaches people that they have to look a certain way, act a certain way, or read a certain type of materials in order to be invited into the library community. If librarians truly believe that libraries are for everyone in the communities they serve, we shouldn't ask our users to pass a test--implicit or explicit--to be welcome in our spaces. Furthermore, when we choose to mock a particular user group for the choices they're making, I would challenge us (myself included) to think about who we're choosing to mock. I could be wrong, but I would venture to guess that most of the time the users who get our ridicule are not the white, cisgender, middle-class, able-bodied among us. Instead, I would guess that more often than not it's users from marginalized communities--the people who may not have the tools to code switch and become the kind of people think is worthy of using your library's collections and service.

This doesn't mean that we shouldn't set expectations for how our users should behave in our library spaces or to develop collection policies to cover what we will and won't purchase for our users. But even when we make those choices, I think we should agree that we should treat our library users with respect--even when we're holding them accountable for the ways in which they've broken the rules we've established for library use.

But Erin, you're thinking, what about those times when I need to blow off steam or vent about a situation? What about those stories that are too good not to tell?

Look, I get it. It's totally normal to need to have a release valve for those problem patrons or difficult situations. I'm not advocating that you have to be perfect all the time. If you need to talk something through, find a trusted colleague or network of colleagues and talk about those situations in private--in person or by email. If you want to tell a story, tell it in your break room or your staff-only areas where you are certain that a library user can't hear you. The point is: if you air your library's dirty laundry in public, you risk losing the trust and support of your community.

I'm as guilty of this as anyone else, I'll admit. So let's all decide together that this is too important not to work through.

Stay positive,
Erin

Tuesday, August 9, 2016

Oh what a wonder, oh what a waste

Last week, I read an article in the most recent issue of dh+lib that presented the idea that the development of metadata standards for a particular project can, if we let it, be a kind of outreach. Emma Annette Wilson and Mary Alexander write, "DH projects require high-quality metadata in order to thrive, and the bigger the project, the more important that metadata becomes to make data discoverable, navigable, and open to computational analysis." The article goes on to urge that metadata librarians emerge from the back room in order to build relationships with digital humanities scholars. Wilson and Alexander write, "it is time to leave the backroom and partner with faculty and students on the frontiers of DH research, introducing them to metadata best practises and innovations, and sharing with them the creativity required to produce flexible, sustainable, and robust data for their projects."

I like the idea of including metadata librarians in the development of digital humanities projects. As the authors point out, digital projects require well-formed metadata in order to do the things scholars want to do. Inviting metadata creators into the conversation early on in the process will (hopefully) lead to decisions being made that don't end up with a library's metadata creation team remediating a significant amount of metadata later in the project.

I also appreciate the range of projects that Wilson and Alexander discuss in their article, as I think they show the range of digital humanities work and the metadata that supports it. From using a controlled vocabulary to describe fabric swatches in a fashion industry publication to contextualizing marginalia in digitized texts, the authors demonstrate the value of well-formed metadata across a wide variety of digital projects. The projects outlined in this article show what digital scholarship can be when metadata is considered early and often.

One thing that Wilson and Alexander don't explicitly address in their article is how the additional labor of consulting on digital projects from outside the library is accommodated within the existing workload of metadata creators. And, ultimately, this is the part of the situation that I find myself feeling concerned about. I have mixed feelings about asking metadata creators who are already taxed working on homegrown library initiatives to take on the work of instructing digital humanities scholars about well-formed metadata. On one side, I think it it's important to leverage the expertise that librarians have to provide the services that our users need. And if digital humanities scholars need help with metadata in order to create meaningful digital projects, then metadata creators should be in the middle of things helping them. On the other side, I think that we risk having our metadata creators suffer from burnout if we're not providing additional resources to help those metadata creators balance the demands from within, and outside, the library.

When considering how to balance competing interests in the area of metadata creation, two possible solutions come immediately to mind:

1. Allocate positions (or portions of positions) to digital projects that come from outside the library. By including this work in the position description or job duties of a metadata creator, a library acknowledges both the importance of supporting user-created digital projects and the labor necessary to do this work.

2. Embed a metadata creator in the library's digital humanities program. By doing this, you not only address the importance and the labor of supporting user-created digital projects, but you give the metadata creator the space and time necessary to collaborate with both the digital humanities library and the user community. The metadata creator has time to answer question and give their full attention to the project at hand without significantly compromising the progress on in-house digital projects.

In the end, I am not against the idea that metadata creation can be an outreach tool. Digital humanities research provides an opportunity for academic libraries to engage with our users and that opportunity can't be ignored. But I do think that we have to take seriously the question of labor and of workload when we ask metadata creators to add consultation to their already full plates. If well-formed metadata is as important as the authors of this article suggest that it is, we have to ask ourselves at what point the challenge we've placed in front of metadata creators is no longer sustainable. Ultimately, I don't think academic librarianship can support digital humanities work while also applying the 'do less with more' tactic to metadata creation. Our metadata creators, and our users, deserve better.

Stay positive,
Erin




Tuesday, August 2, 2016

The time to rise had been engaged

I am always a little bit cheered when someone outside of the metadata creation universe champions a metadata or metadata-adjacent cause. A lot of what I write about is about the value of well-formed metadata in the larger library ecosystem--especially as it relates to a user's ability to discover things in a digital environment.

So given my soapbox feelings about well-formed metadata and its role in discovery, I was interested to Chris Bourg's blog post about the role of serendipity in the research process and browsing in the online environment. I was even more interested to know that Chris gave this talk to members of the IviesPlus group as part of IviesPlus Discovery Day, because I feel like those are the people and institutions with the resources to really dig into these issues.

The part of Chris' blog post that really caught my attention was this:
What we are hearing are scholars who want us to build tools, or facilitate the building or deployment of tools, that will allow them to see connections to their work and their teaching and their interests that they cannot see now. They want to discover articles and books and data and images and maps and primary sources and teaching objects and people on the fringes of their own areas of focus, but that are otherwise kind of in their blindspots. They want to make happy & unexpected discoveries; and they want it not to be by accident, but to be because the library has provided the tools, the data, and the metadata to make it so.
What I appreciate about this statement is the acknowledgement of the fact that creating this kind of world, this kind of future, requires well-formed metadata. Researchers want to be able to discover the things they didn't know that they wanted to discover and I believe that library would love to make that experience available to users. But, as Chris points out, that requires a different set of tools than are currently available to users. It also requires a commitment to understanding what metadata those tools require to provide the kind of experience that users want and, once those needs are assessed, the commitment to developing that kind of metadata.

Creating the descriptive and subject access to library materials that will facilitate the kind of user experience Chris describes is costly. Yes, metadata from other parts of the supply chain can (and should) be used. And yes, linking to authoritative source outside of the current authority ecosystem will help cut down one cost. But at some point, libraries will have to take on the task of creating and remediating metadata in order to make it useable by the tools that are necessary to facilitate true, serendipitous discovery. And that creation and remediation is timely in terms of time and in terms of personpower.

I am grateful that Chris put forth this vision for the future of discovery. And I'm doubly grateful that metadata was mentioned in the same breath with tools and data. It isn't enough for metadata creators to talk ceaselessly about the value of well-formed metadata in the discovery process. We need for administrators to talk about it, too. I am inspired by the ideas that Chris put forth in the talk that lead to the blog post. And I hope that we, as metadata creators, have the resources we need to create the well-formed metadata that will lead to those ideas becoming reality.

Stay positive,
Erin


Thursday, May 26, 2016

The secret to a happy ending is knowing when to roll the credits

I mentioned in my last blog post that I'm writing a book chapter. I'd had "Naming and reframing: a taxonomy of attacks on knowledge organization" by Tina Gross on my to-read list for a while. And this chapter I'm writing provided me a great opportunity to read it.

To say that I have some Capital-F feelings about this article would be a pretty significant understatement.

In the article, Gross identifies 10 types of attacks of knowledge organization and then goes on to define and give examples for each of these attacks. Gross doesn't offer any solutions to the problem of attacks on knowledge organization and states pretty plainly that the point of the article is not to solve the problem, but to establish language through which we can describe it.

There are two attacks that I think have a symbiotic relationship: disregarding quality and distorting user behavior.

When describing disregarding quality, Gross writes:
There is such a thing as metadata being good enough without being comprehensive, and there's also such a thing as declaring hopeless garbage to be good enough without considering the implications for users. Doing the latter is self-defeating--when metadata fails to facilitate the level of searching needed by users, they have a less satisfactory experience. Usage is likely to go down resulting in even less justification to support and pay for the creation or acquisition of quality metadata. (p. 266)


via GIPHY


This particular attack leads to the library infrastructure version of chasing one's tail. For whatever reason, the metadata creation standards at a library decline. Because the metadata is incomplete, incorrect, or both, users can't find what they're looking for and usage of key resources that are powered off of the shoddy metadata goes down. Administrators look at the decline of usage of the key resources and decide that the because the usage is going down that the resources devoted to creating metadata that powers those key resources can be reallocated.

While a metadata creator might be able to draw an immediate connection between the change in metadata quality and usage of key resources, an administrator might not necessarily be able to do the same if they don't have an understanding of how metadata informs search results and all they have to go on is the usage data of key resources.

While we're on the subject of what users do or don't use, let's look at distorting user behavior. Gross describes it as "asserting that users don't use certain types of metadata, even though major search functions are powered by them" (p. 267)

This attack has as much to do with the narrative constructed by outside forces as it does with what libraries know to be true of their users based on actual evidence. There are a not-insignificant number of studies which suggest that users don't start their research in the library catalog, so administrators decide that resources used to create metadata can be reallocated to other library services. There are two things that strike me about this:

1. What seems to be missing from these studies, though, is how many library users interact with the catalog at some point during the research process. Just because a user doesn't start their search in the catalog doesn't mean they don't go there at some point in the process.

2. Our users are not a monolith. What is true about the research process of one user group may not be true of all user groups.

So which comes first--disregarding quality or user behavior? And, perhaps more importantly, where do metadata creators go from here?

I don't have the answer, but I have a couple of ideas.

First, metadata creators should be gathering as much information as we can about user behavior and using that information to guide the decisions we make. We should know what our users find most useful in catalog records and be focusing our attention on that. This differs from library to library and user group to user group. So while you can probably use those reports that construct a narrative as a starting point, you're going to have to interact with actual users to understand the context at our own library.

Second, our public services colleagues have to help us gather data about when users can't find what they're looking for because of poorly-formed metadata. This data can help metadata creators make the case for the re-reallocation of resources back to metadata creation. Nothing says 'hey, we need more resources in the cataloging department' like evidence of where users have walked away empty handed. To the extent that it's practical (and legal), I would advocate share reference interview transcripts or notes as well as catalog search logs.

Finally, I want to say that I picked on administrators a lot in this post, but I do so affectionately and with the understanding that our administrators have a lot to think about and decide on any given day. And, ultimately, they work with the information we give them to make the best decisions they can to allocate resources to library services. It's our job to give them the information and tools to make the best decision possible.

Stay positive,
Erin


Monday, May 9, 2016

The right notion in the meantime

Last week I attended the Program for Cooperative Cataloging's Joint Operations Committee Meeting. This is, essentially, the business meeting of the various groups that form the PCC. This year's OpCo meeting included a lot of discussion on BIBFRAME and what a world after MARC might look like. In the midst of this conversation, I sent out a couple of tweets:




There is much about BIBFRAME and the post-MARC world that I don't understand. And until I attended this meeting, I was pretty sure I wouldn't wade into this discussion because I had nothing smart to add.

But now I do.

Building a new encoding standard is really amazing. I doubt many people really think of it that way because it's such nuanced work. Honestly, I don't think about how amazing it is most of the time. I mean, I quit the BIBFRAME list because it was so far over my head as to be useful to me. So the wonder of standards creation is lost on me most of the time.

The part about building an encoding standard that excites me most is that it gives us the opportunity to radically reconsider our current practises. What parts of our current practices are so important that we want to preserve it and what parts no longer serve us? What new practices could we incorporate to better serve our user communities?

I hope that as the metadata creation community builds out and implements BIBFRAME that we don't just try to map MARC fields into BIBFRAME elements and create what might essentially be considered MARC2.0. I hope that the community takes the time to consider what MARC fields are essential in helping users complete the tasks that brought them to the online catalog in the first place.

This evaluation and decision-making process requires the metadata creation community to think about who it considers its users and what they might require in order to successfully navigate the online catalog. I desperately hope this means consulting with actual library users in order to devise user tasks and use cases based on actual user needs as opposed to talking about a monolithic user.

This evaluation and decision-making process also requires the metadata creation community to have a difficult conversation about administrative metadata and about the extent to which the metadata community itself is a user. What I think we need to wrestle with as a community is the fact that while the metadata community is a user, we are not the primary user. We should not put our needs first and we definitely shouldn't cling to old ways of doing things because they suit our needs. Instead, I would argue that the metadata creation community should identify the minimum amount of administrative metadata required to successfully complete our work.

As we build this new encoding standard, I hope that we decide to use this opportunity to radically reconsider our metadata creation process. And when we do, I hope our benchmark for which practises to continue and which to stop are based entirely on end user needs and not on our own.

Stay positive,
Erin






Tuesday, April 19, 2016

And when I start to feel it making sense for me

So...let's talk about this story that circulated last week about the Representative from Tennessee who wants to introduce legislation to force the Library of Congress to reverse its decision to cancel the heading Illegal aliens and, in its place, use the headings Noncitizen and Unauthorized immigration. It seems likely that this proposed piece of legislation is little more than a push for attention by a person who is up for reelection. After all, what better way to make a name for oneself than taking on the bastion of political correctness that is Library of Congress.

I think this story surfaces, again, an issue that I've written about before: the Library of Congress is not the U.S. national library even though we in the U.S. library community treat it as if it were. We use the Library of Congress' thesaurus and classification scheme for subject cataloging even though many in the U.S. cataloging community have been talking for many years about its flaws and working for many years to try to correct "-ist" headings and class numbers.

And while it would be fun to talk more about the problematic nature of treating the Library of Congress as de facto U.S. National Library, I think that there is a more important issue that this story surfaces: cataloging is not a neutral act.

While it's true that catalogers are taught to be objective in how they are taught to describe the objects they're tasked with cataloging, this feels impossible. One could argue that it feels less impossible in descriptive cataloging, because it is easier to be object about, say, the publisher of a book than the subject of that book. But this feeling of impossibility is even baked into our content standards, which leave room for "cataloger's judgment." In some cases, the standards reason, a cataloger will have to interpret a rule and apply it in a way that makes the most sense to them. Which means that even descriptive cataloging --the part of cataloging that is meant to have the greatest chance of objectivity--isn't actually all that objective.

And while it feels like a challenge to talk about objectivity in descriptive cataloging, it feels wholly impossible to talk about objectivity in subject cataloging. If the language itself isn't neutral, how can we be expected to be objective in our application of that language?

I have long thought that in addition to talking about cataloger's judgment, we should also talk about cataloger's bias. So, let's do that. One of the definitions Merriam-Webster gives for bias is "an inclination of temperament or outlook, especially: a personal and sometimes unreasoned judgment." And when we talk about cataloging--especially subject cataloging--that makes sense to me.

Catalogers bring to bear on the works they catalog a lifetime of lived experience. It is impossible to put away that lived experience in order to describe works in an objective fashion. And it is both disingenuous to library users and unfair to catalogers to continue to perpetuate this....lie. As a middle-class, white, cisgender woman, I can't put away my lived experience in order to describe the things I catalog--nor should I. And I shouldn't expect that my colleagues from marginalized groups to do the same.

So how do we reckon with this? How do we acknowledge cataloger's bias and then move through a flawed system in order to order the objects we are tasked with describing? I think we do it in two ways.

1. Appreciate the lived experiences of your colleagues and your users and think about how this is reflected in your metadata.
My experience with the heading Illegal aliens is different than someone who has lived that experience, which means I should believe them when they say that this terminology is dehumanizing. The same goes with any number of "-ist" subject headings. If someone tells you that the words you're using in your metadata to describe them invalidates their lived experiences, take that seriously. Don't dismiss it because their lived experience is not the same as yours.

2. Educate yourself and your users.
If you are unclear about your place in creating and maintaining oppressive systems, you have some work to do. I wrote before about how you have to understand your place in an oppressive system before you can dismantle it. Read everything you can and have hard conversations with you friends and your colleagues about white privilege and oppression. If you need a starting point for educating yourself, April Hathcock's blog has a lot of great posts on intersectionality and on doing the work.

If you have a relationship with library users, you should use every appropriate opportunity to talk about catalog records and bias and how the material you retrieve when you search is based on biased algorithms. It seems likely that making the catalog as transparent as possible for users will help them find the material they seek while navigating the biased language of subject headings. Emily Drabinski's article, "Queering the Catalog," is a great read when thinking about how to bring users into the conversation about metadata. And anything you can read by Safiya Noble is great for thinking about algorithmic bias.

There are a wealth of tools out there to help you get started in thinking about how to educate yourself and your users. If you have other ideas, feel free to drop them in the comments!

While coming to terms with cataloger's bias is both challenging and uncomfortable, it's unbelievably necessary. We cannot continue to believe that cataloging is a neutral act. And the quicker we move on from that point, the quicker we can help our users identify how to get the best information they need to complete the task at hand.

Stay positive,
Erin






Thursday, March 31, 2016

They pale before the monolith that towers over me

Yesterday I wondered aloud on Twitter why cataloging and catalog records are always held up as signs of the Library of the Past.


I'd just read this Ithaka S+R Issue Brief and was left with mixed feelings about what the Digital Future means for the creation of well-formed metadata.

I actually agreed with much of what Ms. Marcum has to say in this brief. Libraries absolutely do need to understand the needs and desires of users when it comes to library use and then act accordingly. Marcum writes:
Our users, or customers, are in control. Instead of settling for what we have to offer, they can now readily determine who can meet their information needs. Some information resources are freely available through the Internet; some sources provide information for a fee. The user can decide what is important to him or her, and also decide how much that service is worth.
I agree with that 100%. We can't dictate to our users how they should use our resources or what services we provide should be valuable to them. But I would stop to say that I think we should be careful about describing users in monolithic ways. I've written before about how user needs are contextual. While all user groups have some habits in common, I think it's potentially damaging to think about users as a single type of person and change our workflows to match that single type of user.

In this world where users can access a wealth of information from a variety of sources, Marcum suggests that digital resources become even more important. She suggests that libraries need to shift their foci from acquiring and describing print resources to providing access in greater numbers to digital resources. Marcum writes:
In the print world, librarians have been concerned about cataloging books and journals so that faculty and students could discover the resources in the library. In the digital environment, our users are more likely to find digital resources through a Google search than they are through searching the library's catalog. Access to information resources is what users care about--not what the library owns.
Okay, so Ms. Marcum and I are more or less still on the same page here. I think it's fair to suggest that some users prefer instant access to information resources. And the needs of some users require us to think more broadly about how we describe our resources and where we make them available.

But here's where Ms. Marcum loses me:
In the digital era, instead of preparing detailed cataloging records to enter into our online catalogs, we are far more likely to invest in services that our users really want--specialized and individualized help when they can't find what they want in a Google search, access to more electronic journals and databases, on-line reference services, and access to new types of scholarly information--data sets, blog posts, and multimedia resources.
Maybe I'm wrong, but it seems like at least some of these things that Marcum suggests that users want hinge on well-formed metadata in local library catalogs. Where are the people providing specialized and individualized help directing people when Google searches fail? How do users gain access to more electronic journals and databases? Maybe not always the local library catalog, but sometimes.

Library administrators must survey their communities and adjust priorities to meet changing user needs. I get that. But I also think that as long as users need to find library resources--physical or digital--well formed metadata will be an integral part of that task. In fact, I think well-formed metadata is especially important for digital resources because in a digital world we lose the capacity to browse the shelves to find all of the things we missed in our catalog search.

About a year ago, I wrote a post about the importance of having an elevator pitch about the value of well-formed metadata ready for those times when people suggest that perhaps cataloging isn't as important as it once was. In some ways it's disheartening to see that we're at the same place we were a year ago.  And while advocacy is important, I think that if enough people are suggesting that cataloging has extended beyond its usefulness, maybe it's time to evaluate our practises to live in the digital age. I think this means learning more about how users actually acquire information and adjusting our local and national practises accordingly.

At least that way when people suggest that well-formed metadata isn't as useful as it once was, we can say we did our homework as we advocate for ourselves.

Stay positive,
Erin


Tuesday, March 1, 2016

This ain't no acrobatics

So, lately I've been writing about catalog records and the contextual needs of users. It's been fun to play with ideas about how we could change the ways in which we catalog our collections in order to meet the needs of users. The part about writing this blog that's enjoyable is that I can put ideas into the world without also having to assign dollar values or staff time to these ideas. Essentially, I can put the in an incubator and see how they grow over time.

But over where ideas meet reality, libraries often don't have the money or the staff to treat resources description in the way that we might want them to. And, in the absence of those resources, they are forced to make choices about how items in their collections are described. But how do we decide--how should we decide?

In 2007, David Banush and Jim LeBlanc wrote an article titled "Utility, library priorities, and cataloging policy" that applied utilitarian principles to cataloging backlogs--specifically liberal utilitarianism. The authors worked at an institution where shifting institutional priorities meant that fewer resources were available for the cataloging of library resources. And in that environment of changing priorities and fewer resources, the Cataloging Department was tasked with reducing their significant backlog.The article discusses the ways in which their institution decided how they could process their backlog to do the greatest amount of good for the largest number of patrons. The institution changed the extent to which humans would intervene in the cases of both original and copy cataloging. The result was accepting more records as-is and creating less detailed records in cases where records didn't exist while also utilizing an automated process to search the bibliographic utility on an ongoing basis for fuller-level records to replace those less detailed records. And while they acknowledge that the long-term effects of the decision's they've made on user access won't be immediately discernible, they were able to share some statistics for 2005/2006 that made it seem like, in the short term, the decisions they made weren't disastrous for user access.

The article makes a good point about how resources in an organization are finite and that when we make one thing a priority over another thing, we decide how to allocate the resources. Banush and LeBlanc write:
If library administrations agree with Mann and others that more resources should be devoted to cataloging as it has been traditionally conceived and practiced, the additional funding and staffing will almost certainly come at the expense of other initiatives (107).
I think that libraries have to provide users with the collections and services they the need to be successful researchers. I also think that Banush and LeBlanc are probably correct when they assert that allocating resources to the emerging collections and services that users need to be successful researchers means that other areas will lose resources in the form of funding or staff positions. And in a world where many information seekers bypass the library's catalog to find information resources, metadata creation and remediation may seem like an easy target for reductions in both funds and staffing.

But I would argue that there is room in this 'do more with less' world for libraries to consider their priorities and how metadata creation and remediation might be embedded in those priorities. Users want access to more digitized and electronic collections? How will you represent those in your catalog and/or on your website? Users tell you on your satisfaction surveys that they can't find what they're looking for in the catalog? How can catalog records be improved to help users succeed in finding what they need?

It's likely that not every item that comes through a library's cataloging department needs hands-on intervention. But whether it's unique collections or specialized areas of collection interest, I suspect that are items that come through the library's cataloging department that need hands-on treatment that don't get it because of financial constraints. And, in that case, library users suffer.

While it's nice to have an incubator space for ideas to grow, I don't think we can write all of them off as wishful thinking or as too expensive. I feel strongly about how well-formed metadata can improve the experience of our users--especially in the realm of subject access. But I also acknowledge that we have to find the places where we're willing to give something to get something. So how do we choose?

Stay positive,
Erin

Works cited:
Banush, David and Jim LeBlanc. "Utility, library priorities, and cataloging policies." Library Collections, Acquisitions & Technical Services 31 (2007) 96-109.




Tuesday, February 23, 2016

We were perfect when we started, I've been wondering where we've gone

I finally finished Hope Olson's The Power to Name last week. And while I was sad to see it end, I really appreciated the forward-thinking ways in which Olson proposed potential solutions to the problems she identified in the preceding chapters. Though the book was published in 2002, Olson's solutions to the subject analysis problem still seem...controversial.

And can we talk about how much I love them? Because I do--love them.

Olson's solutions are based on the idea that catalogers can apply controlled vocabularies and classification schemes radically in order to center the Other who is most often marginalized in a conventional application of these systems. Her solutions are also based on the idea that while change is possible at a macro-level, change is most effectively achieved on a micro-level. Olson writes "Ameliorative change needs to come from both LC and individual libraries because universal solutions are not viable options" (234). Olson later writes "Our techniques must have the local context as the primary motivator. The far-reaching principles and the standards that have grown from them must be at the service of local, contemporary needs" (239).

I appreciate that while Olson criticizes controlled vocabulary and classification systems as broad concepts, she does not let individual libraries (and the catalogers they employ) off the hook. She notes that individual catalogers have as much responsibility for the subject analysis of the items in their collection as the de facto U.S. National Library.

Although, maybe instead of responsibility we should say agency.

I think that catalogers don't often have "the local context" as their primary motivator. This isn't always our fault, as sometimes resources aren't on our side. Libraries have begun purchasing more metadata from vendors in an effort to move material more quickly to the shelves or to make online resources more accessible on a scale not possible with item-by-item cataloging. But it's worth considering what we lose in terms of local user needs when we gain efficiency.

One of the solutions that Olson proposes is for people within individual libraries to decide what matters most to their users and set subject analysis priorities based on that. Olson writes "Local libraries could privilege different differences: gathering by race or ethnic origin is likely to be of more use in some libraries than by age" (235). Olson's argument is that while controlled vocabulary and classification systems are often inflexible, local applications don't have to be. Libraries can decide in which way they want to pull together books on a particular topic or about a particular group of people.

I think we might dismiss Olson's idea out of hand because it seems time consuming and we can't imagine devoting that much of our time to changing our cataloging workflows. Olson's proposition isn't a cheap or easy solution to the problem of subject analysis, but it does put a library's user community squarely in the middle of the discussion about how priorities for analysis are set. Imagine what it would be like if a subject specialist and a cataloger sat down and talked about what was most important when it comes to describing items in a particular subject specialty. What is most important to users in that discipline--what should I (the cataloger) look out for? Are there particular terms that are triggering to the people you work with with--what language should I avoid?

We often give our rare and unique collections this kind of treatment, but we rarely extend it to materials that are widely held in libraries. And maybe that's okay. Maybe part of considering the "local context" is deciding that not every item is worth the kind of attention to detail Olson's proposed technique would require. Maybe part of considering the "local context" is deciding that what really matters is focusing our attention on the material that only our libraries hold and hoping that the copy we find in our bibliographic utility of choice is good enough to help users get what they need.

The point, I think, is that a cataloger doesn't have to lavish significant attention on every item their library requires. But that cataloger shouldn't shy away from lavishing attention on the items that require it either. We shouldn't shy away from editing a catalog record from our bibliographic utility of choice because it's good enough. We should decide, instead, that that record does not require editing because it suits the needs of our users.

Stay positive,
Erin

Works cited:
Olson, Hope. The power to name: locating the limits of subject representation in libraries. Dordrecht: Kluwer Academic Publishers, 2002. Print.

Tuesday, February 16, 2016

You can get with this, or your can get with that

I read Karen Coyle's FRBR, before and after recently and I was really enamored with how often, and to what degree, the author asks us to consider users and their needs. And the point she returns to over and over again is that librarians design standards and systems without including the user in the design process. Instead, we ask users to make use of systems we design without their input. Coyle writes in the introduction:
"...making any general statement about the structure or data elements needed to describe all resources for all users of a library catalog is going to be difficult if not impossible. And yet this is what we do on a routine basis: we create records that treat all resource types the same, and for only one definition of 'user.' We also ignore or downplay many of the characteristics that are important for users (xiii)
Coyle's quote led me to consider the why of metadata creation and this is where I landed: catalog records serve two distinct purposes.

Purpose the first: inventory control--
Libraries need to have some back-end inventory control system to manage the material in their collection. It is helpful to know, at any given moment, which items in your physical collection are on the shelves and which items are not. And it's also helpful to know where (or, I suppose, with whom) the items that are not on the shelves have gone. Finally, it's useful libraries to be able to tie purchase or subscription information to the items on the physical or virtual shelves.

Metadata elements required for the purposes of inventory control of  any given physical or virtual item are fairly small and might vary depending on the library and the material type of the item.

Purpose the second: discovery of resources--
Users search our catalogs to find material in our collection. Sometimes the user knows what they want and sometimes they don't. The elements we record in our records govern how users can find the material we describe. While our systems have evolved to the point that we can keyword search entire records or drill down through results sets using facets, we are generally able to query metadata that describes our collections the basis of title, author, or subject.

Okay, yeah. So what?
I think that we conflate these two purposes more often than not. And that in doing so, we do the user a significant disservice.

Metadata reuse seems to be underlying goal of any attempt to implement standardization in catalogs. And the underlying goal of metadata reuse seems to be a reduction in the cost of cataloging. Putting metadata we purchase from vendors aside, if we put our records into a shared bibliographic utility, other libraries can download them and original cataloging of an item happens only once.

But user needs are contextual and what users require when discovering resources can vary depending on any number of factors. Reuse of metadata without human intervention is fine if what you require is a placeholder for inventory control, but what happens on the 'discovery of resources side' when the record you download doesn't have the data elements your user group needs?

This is not an argument against a shared bibliographic utility or against the reuse of metadata created by other libraries. This is also not an argument in favor of every library should catalog every item in their collection from scratch. Original cataloging on that large of a scale is financially unsustainable and, for much of any given collection, a waste of time.

Where do we go from here?
On a micro-level, we should identify and document the ways in which downloaded records can be enhanced to help users discovery our library's holdings. Chances are, you have a written procedure that your copy catalogers use when making local edits to downloaded records. Have the data elements that your copy catalogers edit been identified by users as significant for access? If not, have you at least run your document past one of your public services colleagues?

On a macro-level, we need to incorporate end users in the development phase of our cataloging and library technology standards. We should identify user tasks based on the actual needs of users. And we should get feedback from our user communities on the models we build before devoting significant resources to implementing them. By doing this, we save our precious time and build infrastructure that better serves the needs of users.

Stay positive,
Erin

Works cited:
Coyle, Karen. FRBR, before and after. Chicago: ALA Editions, 2016. Print.


Thursday, September 3, 2015

It's Best To Make the Most Of This

It's not about you. Well it is. It is about you providing the best services to the most people. I truly believe this is what we are interested in doing, and that's why I talk about relationships all of the time, even on other blogs. Because we want to do our jobs well, we often focus on our jobs, which can work against our interests. As a service organization, the depth of our specific knowledge and the breadth of our professional knowledge and services is often invisible. We want to make it apparent, to show everyone what we know and what we can do for them. However, "marketing" our services can happen in a way that is unhelpful or even belligerent and off-putting.

I am thinking about how we listen. How often do we run into or engage in the kind of interaction I described in this tweet?
Now, I am a person who hates being told what to do, so when this happens to me, I feel like my input isn't valued, and wasn't even wanted in the first place.  I understand the impulse to respond to input with the array of services available or avenues for action, but this impulse is wrong. We need to work on shutting it down. Erin wrote about developing relationships with faculty based, saying
And when we ask faculty what their ideal relationship with a librarian looks like, let's ask because we really want to know and not because we want faculty to take us seriously or see as as equals.
To really listen, to be interested and want to know, our impulse has to shift from "marketing" our services to understanding our users and their needs. The brief conversation in my tweet should read something like
1: Please, we welcome your input!
2: Here is my input.
1: Wow, okay. I hear that. Can you tell me more about what has led you to that position and what you would like to see happen to address this issue? Where do you want to be in that process?
or:
1: Please, we welcome your input!
2: Here is my input.
1: I can definitely help you with that.
This should be the response even when you already offer a service that addresses the concern. Maybe there is something you can improve, maybe you can address a past wrong, maybe you will learn something. There is never a situation where a constructive answer is "oh, you know, we offer that service" or "if you would volunteer for a committee you will be able to address that concern," even when those things are true. Those responses do not encourage the actions that either party would like to see, they do not cultivate relationships. Every interaction is an opportunity to go deeper, as well. By shifting from a focus on what we do to a focus on our users, we can turn "our tech desk checks out several types of camera" to "wow that assignment sounds really interesting, what are you hoping your students learn from it? how else do you incorporate technology into your teaching? when you have some time, I'd love to show you some of the things our technology desk offers for checkout and introduce you to our technology staff."

When we ask for input, we need to be ready to hear input, because when people give input, they want to be heard. Of course, that sounds great and we can all agree that it's best and that my example is what we try to do. I think we need to practice turning off our "let me tell you what we already do" defenses more and harder to make sure we're always ready to listen and engage on a personal level.

What can you say to tell the person you're interacting with that they're being heard? What can you personally do, in that moment or in the short term future, to address their input constructively? How can you connect with their broader concerns?

And every time, after every interaction: how could I have done that better?

Keep Rockin'
Rachel


Tuesday, September 1, 2015

Everything is fine, fine, fine

Library Journal and Gale/Cengage produced a report called "Bridging the Librarian-Faculty Gap in the Academic Library" which documents the results of a survey sent to a pool of academic faculty and academic librarians. The purpose of the survey was to identify where faculty and librarians are in agreement with regard to what constitutes an essential library service and what can be done to increase communication and understanding. An executive summary can be found here.

The most interesting part of the summary is the set of bar graphs in the middle of the document. The first bar graph notes the percentage of faculty respondents and librarian respondents who considered a particular service essential in academic libraries. The second bar graph indicates the percentage of faculty respondents and librarian respondents who rated their library "excellent" when it came to providing the services referenced in the first bar graph.

There are a handful of services on the first graph that a higher percentage of faculty consider essential than librarians: supporting faculty research, coordinating research data services, adding faculty articles to the digital repository,  text and data mining, parceling course materials from separate texts, and managing research grants. Interestingly, faculty also gave librarians higher marks on providing those services than the librarians gave themselves.

It is worth noting that the faculty respondents came from private, college or universities and that many of the respondents came from the sciences and the humanities. It is also worth noting that every individual library operates in a different context. So what this report says on a macro-level might not scale down to your individual library.

On Thursday, Rachel wrote about how the best way to understand our undergraduate users is to engage with them and then provide them with the services they want. She wrote:
There is a simple solution, you know. We can get comfortably uncomfortable and ask students what they want out of interactions with librarians and libraries. We can ask students what their ideal relationship with a librarian looks like throughout their college career. We can listen seriously to what they say, and try to be exactly who and what they need and want.
The report from Library Journal and Gale/Cengage gives us a place from which to start the conversation. Asking what we can do to support faculty research is a good place to start the conversation about what their ideal relationship with a librarian looks like. But let's not stop there, assuming that's all they want. And when we ask faculty what their ideal relationship with a librarian looks like, let's ask because we really want to know and not because we want faculty to take us seriously or see as as equals.

Ultimately, I think that coming into agreement about which services are essential for each of our user groups is the most important thing we can do to succeed. There are some library services we will never be able to jettison, and that's not a bad thing. But there are some services we offer our users that made sense at the time, but which have been rendered obsolete by the passage of time. It isn't that those services never had value--they did. But now they don't, and those services (and the people who provide them) can be transformed into something new and even more useful for users. We just have to be open to having the conversation and open to accepting the feedback even when it makes us uncomfortable.

Stay positive,
Erin