Category Archives: First Year Academic Librarian Experience

Hack the Stacks: Outreach and Activism in Patron Driven Acquisitions

As many others have said more eloquently than I could, everyday in libraries we make decisions about how to spend our resources: time, space, attention, but perhaps most obviously, money. In 2015, the average library expenditures for collections at doctoral institutions was over 5 million dollars. What we choose to spend that money on is an inherently political act. Recognizing it as a form of activism, students at the University of Virginia used our purchase request system to ask that the library add more materials by underrepresented voices to our collections.  I’ll describe the background, logistics, and outcomes of an event we organized to encourage and facilitate these requests.

As a subject librarian, collection development is a surprisingly small part of my job. A centralized collections team manages our approval plans and once a year subject liaisons review them to make sure they still align with departmental interests and priorities. We also have an automated purchase request system that patrons can use to request items for the library. These requests get sent to the collections team and the subject librarian in the area and we passively approve them (unless there’s a glaring reason not to purchase it, it goes through). Beyond those two responsibilities, my involvement in collection development is minimal.

UVA isn’t alone in changing the way it handles collection development from the selector/bibliographer to an outsourced model. Along with this operational shift, we’ve experienced a more philosophical one: budget and space constraints mean that we can no longer try to collect everything, and have had to refocus our efforts towards providing material as patrons explicitly need them, which is the same paradigm shift of “just-in-time” to “just-in-case” that many libraries are experiencing. We rely upon patron purchase requests to tell us when there’s a gap that needs to be filled, but sometimes students don’t know about that feature of the library website or how to use it.

A few weeks ago, a graduate student in the Music Department approached me about co-organizing an event to teach people how to use the purchase request feature while simultaneously requesting books by marginalized authors and independent presses be added to our collection. (Thank you to Aldona Dye of the UVA Music Department and Matthew Vest of UCLA who came up with this idea.) We decided to call it Hack the Stacks and partnered with the Graduate Student Coalition for Liberation, an interdisciplinary group formed  “with the goal of creating a campus environment where resources  for learning about and combating white supremacy (such as discussion forums; visiting scholar and activist talks; syllabi; direct actions; trainings; and safe and accountable spaces) are readily available.”

Prior to the event, we circulated a Google Doc and asked people to add books and presses they thought should be added to the library’s collections. The day of the event, we gave a presentation covering the library’s current method of collection development, emphasizing that purchase requests are the best way for patrons to influence what they think we should own, how to submit a purchase request, and describing what happens after a request is submitted. From the patron perspective, our collection development process is opaque and this discussion made it a lot more transparent. We posted large print-outs of the list on the wall and asked participants to check off items when they submitted a request. We also brought a blank sheet of paper for participants to add to if they submitted a request for a book that wasn’t on our list. Participants filtered in and out during the two hour event, with some staying and submitting multiple purchase requests and others dropping in to submit one or two. 

Our collections and acquisitions teams helped facilitate this event on the backend. Before the event, we talked about whether our normal purchase request budget would be sufficient to cover an event like this, and I shared the list with them in advance to give them a rough estimate of the number of requests to expect. During the event, I encouraged participants to track down the link to purchase the title they were interested in to make it easier on the acquisitions team and to use the “additional notes” field to justify the purchase, which is a practice our collections management team encourages for requests to be fulfilled more reliably. We also added a designation to each item that was requested so that the acquisitions team could track which requests were coming in as part of the event.

All told, we ended up submitting purchase requests for close to fifty items. Those requests are still being processed, so I can’t yet say how many will be added to our collection, but I’m hopeful that most of them will be purchased. Building diverse collections is, as AJ Robinson pointed out, imperative if we want to be the inclusive and welcoming institutions we strive to be. We need to have books by and about people from historically marginalized groups if we want them to feel as though the library is for them, too.  Having these materials on hand also means that more people will engage with them. We are undergoing the beginning of a renovation right now and through a series of preparatory focus groups and meetings many people have emphasized how essential browsing is to their research processes. Hopefully, by having these books in our catalog and on our shelves, faculty and students will be more likely to use them in their courses and research. This event also revealed gaps in our collection, particularly in disability and indigenous studies. I hope we can use this knowledge to revisit our approval plans to see how we could collect more intentionally in these areas.

This was my first experience doing outreach to encourage patron driven acquisition and using it as a tool to encourage more inclusive collections. I’m hopeful we can turn it into a larger effort to tap into patron expertise as we make decisions about how to allocate our limited resources and to incorporate what we learn into our long-term collections strategy.

I Liked, I Wished, I Wondered: A One-Year Review

One year ago today I flew one-way from ORD to LAX for my first real librarian job (and obviously for the weather). I’m going to take an assessment nugget I once learned from Jennifer Brown, Emerging Technologies Librarian at Columbia University and reflect upon this time using the following measurements: I Liked, I Wished, I Wondered.

I Liked

I liked plenty thus far as a Health & Life Sciences Librarian at UCLA. Most importantly, I am grateful for my work colleagues. I work with people that truly care about learning and how it is reflected within library practices. I work with inspiring and supportive people of color. I work with people that have more to talk about than libraries (this is so important!). While I didn’t necessarily imagine myself working as a librarian in the sciences, I like working in this domain! While I have health sciences experience from working as a speech-language pathologist,, I didn’t appreciate scientific research, its importance, its limitations, and its possibilities, as much as I do now. The sciences seemed a bit intimidating in the beginning, but I have been pleasantly surprised at how accessible it can be, even if someone doesn’t have a sciences background (or even an interest…I am curious how much these are linked). I also like the new matrixed organizational structure within the UCLA Library. It allows for librarians to do a little bit of everything while focusing on a specific area: Collections, Outreach, Research Assistance, Research Partnerships, or Teaching and Learning. This encourages communication across units. For example, I am on the Teaching and Learning Team with the Visual Arts Librarians. This is not a librarian with whom I would typically interact, however, this allows for collaboration, transparency, and information dissemination in seemingly unrelated functions and subject areas. Did I mention that I also like (LOVE) the weather? UCLA is a gorgeous campus all, come visit!

I Wished

I wished I came into my position having a better grasp of collections and scholarly communication. These are essential parts of my everyday duties, and while I have learned these functions over time, I think I would have hit the ground running a bit faster if I did a better job of taking a collections class or participating in a collections and/or scholarly communication focused internship during my MLIS.

I wished I had more time! There are moments where it’s hard to stay focused. This is likely due to a combination of my slightly average organizational skills and saying yes to opportunities. I do think I have been saying yes for the right reasons. I want to be of service, test my capacity in my role, and see what I liked (see above). The good news is that certain responsibilities do not last forever, and now I do have a better idea about what I would like to keep pursuing, what might make sense to stop in a year or two, and what to say yes/no to next time around. I want to be mindful of librarian burnout, so while I’m happy to try it all out, I don’t want to resent the profession either.

I Wondered

I wondered how things would be different if what I wished and what I liked had worked in concert. I wonder where I would be if I hadn’t come to UCLA. I wonder if I prefer to manage others or work as a subject or functional liaison. Will I stay in health sciences librarianship or would I branch out to other areas? I have truly enjoyed diving into medical librarianship, but I have wondered if a I would be better suited to focus upon a functional area. I enjoy pedagogy, active learning, outreach, and connecting different campus partners – perhaps there is a place for me in these areas? I enjoy wondering about this all at UCLA because the matrixed organization and professional development opportunities allow me to explore. I have also wondered if I will stay at an R1 institution, make the jump to a community college, or even try my hand in public libraries.

What Now?

I have always disliked the idea of having a 5-year or 10-year plan. I believe in intention, serendipitous moments, and blending that with your personal drive and abilities. I did not come to librarianship through a straight path, and, while I don’t want to change my career again, I am open to different possibilities that can harness and enhance my skill set. Writing this out has definitely forced me to reflect upon the past year, see how far I have come and what the future might hold. One year down and many more to go!

What are some different ways you taken assessment of your career path as a librarian?

Responding to Communities in Crisis

Charlottesville and the University of Virginia have been in the news a lot recently. In Summer 2017, a series of white supremacist rallies took place in Charlottesville, culminating in the August 2017 Unite the Right rally which erupted in violence between counter-protestors and the white supremacists. In 2014, UVA was the focal point of a conversation about sexual assault on campuses after an article in Rolling Stone detailed, and later retracted, a story titled “A Rape on Campus.” A few years before, UVA’s president was forced out by the board and later reinstated, resulting in national conversations about the future of higher education centered around the scandal at UVA. While it wasn’t specific to our institution, some also viewed the 2016 presidential election and its aftermath as a community crisis, since it was traumatizing for many people and resulted in local conflicts.

In light of this recent string of traumas, and our lack of clarity about what to do when they occur, my colleagues and I wanted to start a conversation with other academic librarians about how we can respond when our communities are in crisis. A few weeks ago, we had the opportunity to travel to Knoxville, Tennessee for the Library Collective Conference, where we facilitated a roundtable discussion centered on crisis response in libraries informed by our own experiences as librarians at UVA.  I’ve been in Charlottesville for 14 months, so I was only personally present for the events of August 2017. I am very grateful to the colleagues I worked with on this session, Maggie Nunley, Paula Archey, Erin Pappas, and Jeremy Boggs, who were able to speak about their experiences at UVA during each of these events.

While Charlottesville has been the locus of a lot of national attention, campuses all over the country are dealing with crises in their local communities and the impacts of national events. We wanted to make this session an opportunity for people to talk about whatever type of incident they feel most impacted by or worried about, so we organized participants by type of institution and asked each group to choose a type of scenario they wanted to discuss.  We asked participants to consider a series of discussion questions related to their incident, taking into account institutional, personal, and collegial levels of response. After discussing and writing down their ideas, each group arranged their thoughts in an incident response matrix. An example of the matrix, which we filled out using August 12th as an example, is pictured below.

This outlines our imagined ideal response. The actions we actually took are highlighted.

We created this matrix after reflecting on our own response to the rallies in August 2017. Of all the events we discussed, this was the one we felt the most prepared for. The Library, in collaboration with the University, was planning to host a day of reflection and conversation on the day of the rallies, with speakers, discussions, film screenings, and a community potluck. Around noon, the governor called a state of emergency and the events had to be canceled, although the Library was kept open. While we had prepared an institutional pedagogical response, it became clear that we were not prepared on other levels. For example, we weren’t clear on our gun policy and there was confusion about whether or not weapons were allowed inside building on campus. Since then, we’ve clarified our policy, and signs have been posted outside buildings to clarify that guns are not allowed in our libraries. While it’s obviously impossible to prepare for every possibility, in hindsight, it may have been helpful to consider these different levels of response prior to that weekend’s events in order to fill some of the gaps.

We also asked participants to consider the constraints that might prevent them from achieving the ideal scenario outlined in their response matrix.  It will probably be no surprise to hear that participants had a lot of constraints to share, ranging from the constraints most libraries face all the time, like lack of resources, to more complicated problems of emotional labor, legal issues, power imbalances, and fear. Conversations like this one can be hard to have, because constraints vary so widely by institution and individual person, but it was interesting to hear the roadblocks that different people experience in trying to align their personal values with their professional responses. As each group reported out about their chosen scenarios, responses, and constraints, we asked them to also share actionable takeaways their group had generated.  The conversation constellated around a few key needs, which I hope library administrators may take into consideration as they think through these same issues:

  • To feel empowered to respond by administration without fear of retribution or judgement.
  • Proactive policies and procedures for crisis response.
  • Frequent trainings for library staff.
  • Space to reflect on and share experiences.

While there are no right answers to a lot of the questions we discussed, this session made it clear that many of us feel unprepared in the face of crisis and that there’s a lot of interest in starting these types of conversations. I appreciate everyone who shared their insights with us and hope it will be part of an ongoing conversation about how we can support our communities and colleagues while practicing self care during times of crisis.

Librarianship and Project Management Skills

I am almost a year into my tenure as a Health & Life Sciences Librarian at UCLA, so I’m starting to get a hang of things. I have a better understanding of our resources, I am able to dissect a research question more efficiently, and I am figuring out how my library actually works. My guess is that all of these, and more, will become even easier while providing more challenges along the way.

This is also about the time where I reflect on the coulda, woulda, shouldas from library school. While I did work at a library at the University of Illinois at Urbana-Champaign, I didn’t work there enough to truly understand how the library worked as a system and how individuals were serving this system. And while I stick by the benefits of laziness, especially in graduate school, there is one class I wish I took in my program: Administration & Management of Libraries and Information Centers (I especially wish I could have taken it with the amazing instructor Melissa Wong!)

First, I will first explain why I didn’t take it:

  1. I wanted to graduate ASAP. So I took enough classes to meet the minimum credit requirement.
  2. I wasn’t sure if I needed this class given my experience in the corporate world.
  3. I was (and still am) interested in reference and instruction, so I was afraid this would veer away from that focus.
  4. I wasn’t even thinking about being a manager in library school – my brain wasn’t thinking that far ahead. I was just trying to learn as much as I could about my interests as well as the mushy stuff (theory, library history, etc.) that I wouldn’t necessarily learn on the job.

Now, I shall debunk the above (hindsight is always 20/20):

  1. Yes, I did want to graduate ASAP, and I did enjoy all the classes I took, but there are one or two I could have done without.
  2. Experience in the corporate world ? libraries. Also, the individuals working in the corporate world are different than those working in libraries, especially when it comes to project management. I will expand on this more later.
  3. Understanding how libraries are administered and managed is the oxygen to navigating a library system. I didn’t really connect this before, but if I’m going to do reference or instruction or collections or whatever, these functions rely upon a larger structure which is essential to understand and critique.
  4. I did enjoy the mushy stuff. However, I think it would have benefited me to be a little more practical and learn the nuts and bolts about the administration of libraries. After all, if we think about the world and how socioeconomics, identity, and global politics affect us today, our place in the world starts becoming a little more situated as opposed to feeling independent or out of context. My point is, structure matters.

I want to talk about project management and librarians a little here. Keep in mind, this is based upon my less than two years experience working part-time at the University of Illinois at Urbana-Champaign and less than one year at UCLA. These are large academic research libraries. My experience is limited, however, I do think I’m onto something here. And that is: Most people do not initially go into librarianship to lead or manage.

I think many of us have had pretty library fantasies that are indeed wonderful. And I fully support this because this is where we came from. But we need to go back to Ranganathan’s fifth law of library science: a library is a growing organism. Libraries are different today than they were 10 years ago and 10 years before that and so on. Technology has accelerated the capabilities and possibilities for libraries, however, it is difficult to keep up. Because of this, project management skills are necessary. My first foray with project management was when I dove into my first job out of college as an IT consultant. I was slammed with project management methodology and project managers that were successful implementers. While there were, and still are, many things I despised about the corporate world, project management is a great skill for any individual to have within any type of organization.

I have noticed that many librarians (myself included) can get bogged down in the details of tasks instead of zooming out, looking at the landscape of a project, sketching out a timeline, determining project phases, corresponding tasks, and project members. However, those that work in corporations, especially consultancies, go into these fields to be project managers. I don’t think it’s bad that this isn’t the first priority of many librarians, but I do think it’s bad to ignore its importance.

When I go to conferences, I haven’t see many papers or lightning talks about project management specifically, and I wonder how librarianship could evolve if this was a focus. I have seen plenty about specific projects, but not as much about the tools they used to manage and implement them. The Project Management Institute has a Project Management Professional (PMP) certification. This is a certification that helps people make the big bucks and in companies. Is there an equivalent for libraries? Can there be one? Also, how can this be harmonized with leadership institutes and meeting the needs of marginalized populations? Is there a way that library science graduate programs can include this in curriculum?

It’s very possible that taking Administration & Management in Libraries and Information Centers would not have given me project management expertise. However, I do think it would have led me there earlier if I did take the course. Either way, I am glad I have been able to process and integrate my different career experiences to my work today. So far, my career in librarianship has been very rewarding, and I am confident that learning and building upon project management skills will make me a stronger librarian.

Have you had experience with project management programs? What are your thoughts about integrating these concepts with librarianship?

 

Developing a Peer Support Group

There’s been a lot written here on ACRLog about the importance of mentorship, and I echo what many others have said: there is enormous value in learning from and being supporting by experienced librarians. There’s a separate kind of mentorship, one that doesn’t necessarily fall under the traditional mentor-mentee model, that has also been hugely beneficial to me as a first-year librarian: peer support. Quetzalli wrote a few weeks ago about the value of peer-to-peer relationships, and it inspired me to reflect on my own experience as a member of a newly formed Early to Mid-Career Librarian Support Group at my library.  

Last semester, a few of my colleagues at the University of Virginia convened a group for early- to mid-career librarians to share advice, ideas, and support. The group operates autonomously and informally. We meet every few weeks for a discussion, and anyone can contribute to the agenda or propose a project.  Our first meeting was a chance to introduce ourselves and discuss our career trajectory and what we wanted to get out of the group. While some people were looking simply for camaraderie and support, others were looking for more concrete advice on how to do to do things like pursue a research agenda or how to more purposefully develop their career. These early conversations have informed the direction the group has since gone. We’ve surveyed group members about their research interests, invited senior administrators to discuss professional development, and coalesced around some bigger documentation projects that I will discuss below.

While plenty of opportunities for collaboration and support arise naturally throughout the course of my daily work, having a more formalized avenue for this kind of peer support is especially valuable. Because of the size of my organization, there are people I still haven’t met yet, particularly in departments that I don’t work with closely. This group allowed me to connect with people across areas of the library that I wouldn’t normally encounter in the course of my workday. It’s also a great way for me to avoid some of the isolation that I can sometimes experience in a small branch library. Because meetings are kept collegial and informal, I’m able to start building some of the relationships that happen more easily if you see someone in an office every day.

Finally, conversations in this group have led to projects that would be overwhelming undertakings without the support of many people. For example, one of the most consistent themes that came from our early conversations was a desire for more robust documentation, especially among newer employees of the library. As we compared our on-boarding experiences, it became clear that we had all experienced some version of the same thing: not feeling sure how to do something and asking around until being directed to email a certain person or pointed towards documentation somewhere we never would have thought to look. As a group, we decided to pool our collective knowledge and document everything we wish we had known for future new employees. Working together, we compiled information about the University, the Library, digital spaces, physical spaces, money, time, and travel, for future employees to reference during the on-boarding process. The resulting document lists basic information like where to find forms or how to get access to certain pieces of software, but it also explicitly outlines some of the library’s conventions, like when to use which communication tool, that are not immediately obvious to people who are new to the organization.

While this type of documentation is often compiled by supervisors or administrators, it was actually really useful for it to be generated by people so close to the experience of being new, because we were able to remember what we had to figure out on our own. It’s easy to forget how overwhelming it is to be brand new to an organization, and easy to forget all the things we expect people to know without explicitly telling them.  The group dynamic also really helped us flesh out this document, since we all had overlapping but not quite identical lists of things we thought needed to go into it. Whether or not documentation like this already exists at your institution, I think there is value in asking newer employees what they wish had been spelled out for them when they started and sharing it with new hires. Having a pre-formed group that you can consult with will make this process that much easier.

Creating space in your organization for peer support groups can lead to collaborative projects, like this one, that might not have happened without all of us getting together and talking through some of the challenges we’ve experienced as early career librarians. It can also make employees who work in isolation, physical or otherwise, feel less alone, and open up space for us to ask questions and bounce ideas off each that we might not yet feel comfortable discussing with mentors who are more experienced. I imagine it could also be a useful concept to apply at all levels of experience, such as first-time managers or administrators, as they navigate new challenges. Do you have a peer support group, formal or informal, at your institution?