Crash Course in Weeding Library Collections

Adcock, Chris


Goldsmith, F. (2016). Crash course in weeding library collections (Crash course series (Westport, Conn.)).


Crash course in weeding library collections is divided into 8 chapters with sequential and information-dense titles: Introduction to Weed Identification;  The Weeding Process; Library Staff Weeding Responsibilities; Determining Datedness; Creating a Weeding Plan; Weeding as Library Policy; Communication and Publicity about  Weeding, and Models and Tips for Library Administrators.

The chapter that really drew me in the most as a library student was "Introduction to Weed Identification." I think that this is probably the most difficult part of weeding - how can you tell the weeds from useful resources? This becomes very difficult in collections of more than a thousand records where even when weeds are easily identifiable once encountered there are so many items to consider that they become drowned out. A good way to systematize weed identification is a handy acronym used by Goldsmith called "MUSTIE:"
Misleading (dated)
Ugly (in poor condition)
Suspended (No Longer Current)
Trivial (Poor Quality Content)
Irrelevant (Out of Scope for this Library's Community
Elsewhere (would be a better place for this material, including potentially a different and more suitable collection).

In addition to judging collections buy this criteria, weeding becomes additionally complex when one looks at the relationship of the collections to the community which they serve. An extreme example of this would be an advanced scientific paper search engine in a small rural library. The item might be extremely up to date and useful, but not necessarily for the community it is serving. Weeding should also be made as transparent as possible: library patrons should know that weeding is not done to water down/censor collections or reflect the individual tastes of librarians. It is done to remove irrelevant, damaged or out of date material and increase the findability of higher quality resources.

Developing an Outstanding Core Collection

Chase, Matthew
Fall 2016

Citation

Alabaster, C. (2002). Developing an outstanding core collection: A guide for librarians. Chicago, IL: American Library Association.

Summary

Alabaster's book provides a comprehensive step-by-step guide to the collaborative development of a library's core collection. She uses the case study of the Phoenix Public Library system to thoroughly examine the process. The author defines a core collection as one in which each title circulates regularly and reflect the current interests of the local community. She addresses the issues relating to core collection development such as budgetary limitations, lack of communication among library staff, and an inconsistent understanding of what constitutes a core title.

Evaluation

I found the book to be a great resource that sought to clarify the issue of what makes up a well-established core collection. In particular, her definition of a core title resolves the misunderstanding that they only concern the so-called classics of literature. She aimed to expand this narrow criteria to include any materials relevant to the needs and the interests of a library's community. Alabaster also adds the criteria of currency and usage to determine a title's status as part of the core collection. She highlights the importance of maintaining clear communication and goals, emphasizing the need for written collection policy statements and well-organized staff forums to discuss issues. While the book proves very useful, I thought it problematic in some ways. The case study of an entire library system was of particular issue, since they sought to develop a uniform core collection across all library branches, with each library being required to purchase the same core titles no matter budget and other limitations. There were several issues arising from this ambitious endeavor as the smaller branches didn't have the funding or space to match their larger counterparts. It also neglected to recognize that some core titles won't be as relevant to some of the branch communities being served.