All posts by Maura Smale

About Maura Smale

Maura Smale is Chief Librarian at New York City College of Technology, City University of New York.

Crossing the Bridge: Library School to Library Job

Please welcome our new First Year Academic Librarian Experience blogger Nisha Mody, Health & Life Sciences Librarian at the Louise M. Darling Biomedical Library at the University of California, Los Angeles.

In the summer of 2016, I decided to start applying for librarian jobs. I wouldn’t graduate until May 2017 at the earliest, but a Health & Life Sciences Librarian position at UCLA immediately sparked my interest. Before getting my MLIS, I was a speech-language pathologist. And I love the sun. These two experiences convinced me that I was qualified for this position. I figured this would get me to start updating my resume and website (which now needs more updating). And it worked, I got the job! I was shocked and overjoyed.

Since I was applying to jobs on an earlier timeline, I also ended up starting my position before I finished my MLIS. Thankfully, the University of Illinois at Urbana-Champaign has an online learning option to complete an MLIS. So I moved out to La La Land in March 2017 to start my first real librarian job. I have been in my position for a little over 6 months now, and while it took me awhile to understand the myriad of UCLA acronyms, I am finally starting to feel that I have a decent grasp of how things work. However, this grasp has been very (or not very) informed by my experience in my MLIS classes and while working at the Communications Library. I was also able to chronicle several of my experiences and reflections while writing for Hack Library School. Similar to Abby, I took the advice to get as much library experience as possible. I tried my best given that this is my third career, I am in my mid-30s, and I honestly just wanted to get this show on the road.

Now that I have gotten that first library job, I am starting to see what I did learn in library school and working in a library – these lessons have helped me tremendously. However, I realized that there were some learning opportunities I missed. Yet one of the most enlightening aspects of my experience has nothing to do with library school. Rather, I see how the skills I obtained in my previous careers in IT consulting, IT recruiting, and speech-language pathology are transferring to library-land. I’ll outline each of these a bit right here:

What did I learn?

While working at the Communications Library, I gained knowledge about the importance of positive patron interactions (and how to communicate in not-so-positive interactions), outreach, library organization, the integrated library system, interlibrary loan, and the myriad of possibilities to be more critical in all of these areas (and more).

In library classes, I learned the value of intellectual freedom and how this related to control. I learned how various medium of books (print, electronic, and everything in between) are perceived and used. While I don’t ever see myself working in technical services, I gained knowledge about cataloging and metadata which have helped me understand how resources are categorized. My involvement in University of Illinois’ local Progressive Librarian’s Guild chapter allowed me to advocate for issues seemingly outside my immediate library space. I was also able to integrate experiences from library school to my work in a library through an independent study by starting a Human Library chapter.

All of these lessons (and probably more) were essential to how I view the library today. They have given me the framework for my work today and in the future, especially to never remain neutral as a librarian.

What did I miss?

One of the things I loved about my program was that there was a lot of freedom in the classes you could take. However, the downside of this is that I chose to take classes that looked oh so dreamy. As a result, some of the practical classes fell by the wayside. I wish I took classes around collection development and the administration and management of libraries. I never felt the urge to be a collection development librarian, but I do have to start making these decisions within my current role. I know I can learn this on the job, however, having a better foundation would have been helpful.

I am only now really seeing Ranganathan’s fifth law, “The library is a growing organism” in action. But, in my opinion, it is critical to really understand how different functions within a library relate to each other to see this organism in action. After being in less fulfilling careers, I was resolved to take the classes I was passionate about. And while I am happy I was able to do this, I forgot that I am also passionate about the library itself. This required me to have a grounded understanding in all of the different areas of librarianship whether I was to focus upon them or not.

What have I been able to transfer?

While I am thrilled to not directly be working in corporate culture (because, let’s be real, it is always integrated in our work), I did learn valuable skills regarding project management organizational structure, processes, and workflows, that I can infuse into my work today. I also dealt with various stakeholders in these positions; I see how these interpersonal skills have been beneficial when I interact with vendors now. These experiences have also given me critical thinking skills to analyze and navigate through a stakeholder’s motives and desires.

My work as a speech-language pathologist has first and foremost amplified my empathy. Invisible disabilities are real, and I have learned to never assume anything about a colleague and/or patron. While working in the schools, I learned about a lot of economic, family, and social obstacles that many of my students faced. Everyone has a story, and this has been important for me to keep in mind as a librarian. Additionally, being a speech-language pathologist requires one to create tangible goals for patients/students/clients to measure progress. This has easily translated into learning outcomes for library instruction. I realized that I have always been a teacher of sorts, and while the setting is different, the skills are transferable.

I am truly looking forward to contributing to this blog, and I hope that my skills and knowledge are ever-increasing – building upon the past and supporting a growing organism.

On Being a New Liaison

Please welcome our new First Year Academic Librarian Experience blogger Abby Flanigan, Research Librarian for Music and Performing Arts at the University of Virginia.

Last January, I joined the University of Virginia Libraries as the Research Librarian for Music and Performing Arts. This is my first professional position after graduating from the University of North Carolina-Chapel Hill with my MSLS in May 2016, and I’ve found myself in an entirely new (to me) area of the profession: liaison librarianship. In graduate school, I heeded the advice I’ve seen echoed in every corner of the Internet about LIS programs, which is to get as much work experience as you can, and cobbled together a variety of internships in preservation, digital scholarship, cataloging, and reference services. Despite this list of jobs on my resume, I remember feeling instantly panicked when the first question in my interview was to describe my past experience as a liaison, because, of course, I didn’t have any. Luckily, I managed to collect myself and describe some other capacities in which I had worked with faculty, and ended up getting the job. Now that I’ve been here a few months I wanted to share some of my observations about what makes being a liaison both challenging and exciting as a new professional.

No two liaison positions look exactly alike. Because each academic department has different needs and histories with the library, each liaison I know works differently with their departments. Some are busy all semester teaching classes or doing research consultations with undergraduate students, while other collaborate on grants or do collection development for foreign-language sources. Similarly, liaisons are organized differently at many libraries, so it can also be difficult to directly compare positions or responsibilities with colleagues at peer institutions. At UVA, subject liaison responsibilities are decoupled from collection development, general reference, and first-year teaching responsibilities, so my day-to-day work looks very different than liaisons at other institutions whose responsibilities are split across a variety of areas. This was challenging when I first started because, not knowing exactly what I was supposed to do, my instinct was to model my strategy for engagement on my colleagues’, but it didn’t always transfer or apply.

This brings me to my second point: it takes time to be an effective liaison. Getting comfortable in any new position takes a while, of course, but the liaison model seems to benefit in particular from institutional knowledge. Part of the job is knowing faculty and students in the departments, including their research interests, information needs, and communication habits. Gathering this information can take many meetings, emails, and chance encounters; much of it is tacit knowledge that is built up over time and not necessarily passed on from a predecessor. Many liaisons also rely on the “ripple effect.” By working with a faculty member one semester, they may have more interest the next semester based on word-of-mouth between colleagues. This means that as a new liaison, I am working on laying groundwork for richer collaborations in the future. Building up relationships and projects is a longer process than I was expecting, but I think that’s a good thing because it means this is a job that I can grow into.

Finally, as I build these relationships, I’ve learned just how important communication skills are to this position. Being a liaison requires reaching out cold to people in your departments, and, more importantly, once you are meeting with them, articulating your role and value. It can be intimidating to present yourself as a resource to experts in their respective fields, especially without an advanced degree in the discipline for which you are a liaison, but over the past nine months, I’ve gotten more comfortable and confident doing so. In the beginning, I struggled to define exactly how I could help, and erred on the side of suggesting every possible way in which they might use the library’s resources. Now I try to reach out when I have a specific idea to suggest or information to communicate. After a few successful collaborations, I also have a clearer idea myself about what I bring to the table, so I’m able to more confidently offer my services.

“Liaison” is term which means very little to anyone outside of libraries (I know this from the blank stares I get from friends and family when I try to explain what I do) but can be a source of anxiety for people in them as we rethink and reorganize subject expertise in academic libraries. Being a good liaison or having a strong liaison program seems to be an ever-moving target. Stepping into a role of this nebulous nature as a new librarian can be stressful — it’s hard to know whether you’re doing it right! — but I’m learning to be more comfortable with figuring it out as I go.

Seeking First Year Academic Librarian Bloggers

With the new academic year coming up soon (or perhaps, for some of you, already begun!), we’re looking to bring on a few new bloggers here at ACRLog. We’d like to thank Dylan Burns and Lily Troia for their terrific posts this past year in our First Year Academic Librarian Experience series. We’d also like to encourage new academic librarians — those who are just beginning in their first position at an academic library — to blog with us during their first year.

If you’re interested in applying to be a FYAL blogger here at ACRLog, please use the ACRLog Tip Page to contact us by September 9. Along with your contact info, please send:

– a sample blog post
– a brief note describing your job and your interest in blogging at ACRLog

Please send any questions to We’re looking forward to hearing from you!

Musing on Maintenance

I’ve been on sabbatical for almost six months, which has temporarily alleviated my need to use the New York City subway system with any regularity. This has come at almost exactly the same time that the subways (and the rail systems that use Penn Station) have experienced a sharply increasing wave of delays and failures. I love the subway, truly — it’s near the top of my list of reasons why I live in NYC — but I’m very grateful that I don’t need to ride it regularly right now. The subway unreliability plus hot summer temperatures are an especially awful combination, which makes this week’s news that the governor plans to allot funds for a fanciful bridge-lighting project on the city’s river crossings seem particularly ill-inspired. The subways are failing for the same reasons many other infrastructures fail: deferred and delayed maintenance. That these failures are happening at a time when the subway has hit a high in popularity and use is no surprise, too. The solution is more funding for maintenance, which the state and the city can’t seem to agree on, an impasse that leaves commuters stuck, too.

Yes, New Yorkers are obsessed with public transit (and I will admit to being more obsessed than many), but what does this have to do with libraries? As I was writing this post I remembered that I’d written about The Maintainers conference last year, thinking a bit about the conference’s discussion of maintenance as the opposite of innovation, and how to make space for both in our libraries. But this week, with cascadingly ridiculous subway news, I’m thinking about maintenance of infrastructure that can be critical and is sometimes too easily ignored.

Any organization or institution needs maintenance, including libraries. Like subways, the more popular we are in libraries, the more maintenance we have (and, I would argue, the more deferred maintenance can snowball). At the beginning of the semester our circulation desk has a rush of students checking out reserve textbooks; with the midterms and finals week rush comes more trash for our custodial staff to clean up; the more pages students print, the more often we need to repair or replace the printers. We try to allocate resources appropriately to accommodate busy times, but that can be tricky given flat or declining budgets. And with increasing popularity also comes a need for not only maintenance but expansion — we are absolutely struggling with that at the college where I work, which has seen nearly a 50% increase in enrollment in the past decade (and with expansion comes a neew for more maintenance, too).

Much of the work that we as librarians do is also about maintenance: continuing to meet the needs of our communities by offering services and resources that they need for their academic work. This work can be invisible, sometimes, because our community may not see the work as it happens (for example, in technical services). Invisibility can also be a result of the tendency of institutions to privilege the additive for planning and reporting. When we pull together our goals and targets each year, the tendency is to focus on what we’re doing that’s new. But the maintenance work for continuing services and resources is important, too, and I try to make sure that doesn’t get left out of our goals and reports.

One form of maintenance that I’ve tried to make time and space for during my sabbatical is for my professional and research self. A few times each year I update my CV and professional website, keeping track of what I’ve worked on both to share it (e.g. links to articles in my institution’s repository) and to make it easier to do my own annual report each year. Research, too, is additive: collecting new data, analyzing and interpreting it, and sharing the results. When time is short it’s easy to dump those files into a folder (bonus points for media files with unintuitive filenames!) to be dealt with later. It’s all too easy to let this kind of maintenance pile up, even for those of us who generally enjoy organizing physical or digital files. I’ve done a fair amount of professional and research file management during my leave. It’s been great to have some time to focus on this kind of maintenance, especially for the research that my colleague and I have been working on for many years.

I’m not sure how to resolve my concerns with maintenance in our libraries and for ourselves as librarians, other than to try to keep the focus on these maintenance tasks when we’re planning and reporting. How have you integrated maintenance into your work in libraries?

Here We Go Again: Net Neutrality

With so much in the news since the new federal administration took office earlier this year it’s easy to be overwhelmed — I certainly have been, especially in recent weeks. So you might have missed the announcement that the Federal Communications Committee has proposed to repeal regulations on commercial internet providers that guarantee net neutrality. Net neutrality is an admittedly somewhat clunky term that requires companies that sell internet access to treat all content equally. As a concept it’s a bit easier to explain using the negative example: if net neutrality ended, companies like Verizon and Comcast could force consumers to pay different rates for different kinds of content, for example, high-bandwidth content like streaming video (think YouTube or Netflix) could be more expensive than content that doesn’t require as much bandwidth. Rolling back net neutrality could make it much more challenging for many of us to access the internet.

The FCC last proposed changing these regulations in 2014, at which point John Jackson wrote a concise overview — Keeping Up With…Net Neutrality — on ACRL’s website, which is a good place to start to learn more. Margaret Heller’s thorough post on the ACRL TechConnect blog is also a great read; in What Should Academic Librarians Know about Net Neutrality? she offers a clear explanation of how content gets from content providers via internet service providers to us as consumers. And how does this affect us as librarians? Content that our communities need could be made more difficult and expensive to access, costs that neither our communities nor our libraries may be able to bear. Even more troubling to consider are possible effects on information freedom and free speech, since as Jackson notes

The loss of net neutrality would add additional layers of economic influence on the structure of the web.

The FCC’s previous efforts to roll back net neutrality were met with a strong campaign from consumers and content providers that was ultimately successful. Both ALA and ACRL issued a statement late last month opposing the FCC’s plans. The FCC was accepting public comments on the proposal, which is scheduled to be reviewed at its open meeting on May 18th, but as of May 12th has entered a “sunshine agenda period” and is not currently accepting comments. But don’t despair — the good folks at the EFF (Electronic Frontier Foundation) are making it easy for you to register your opinions about net neutrality. Visit their Dear FCC site to add your comment, which will be submitted by the EFF when the comment period reopens.