Re: Questions: revising collection development policy

Hi, Cynthia --

I wrote a CDP for our (admittedly tiny) library when I first started. It's about 5 pages long and, while I need to update it a bit, it's worked nicely for us.

Some of the issues I've had with CDPs in the past include: excessive length and complexity; bloated, bureaucratic language; confusion between policy (why we do this) and procedure (how we do this); focusing on a conspectus, rather than on the curriculum as it's actually taught.

When I did mine, I made the assumption that the final document would live on our intranet, rather than in a three-ring binder. I kept the top document pretty lean, just a statement of general principles, who has decision-making authority, etc. From there I linked to other documents (also short and lean) written by members of my staff to cover their areas of responsibility. I also linked out to appropriate sections of the ALA web site for the section on intellectual freedom. (And I strongly recommend that you include one.)

Short version: if you keep it short, keep it to general principles, link to appropriate support documents, rather than quoting from them, you'll have a usable CDP that is easier to manage and update and which can actually be read by human beings.

Have a good week,


Sara R. Williams



Sara R. Williams

Library Director

College of Saint Mary

7000 Mercy Road

Omaha, NE 68106

(402) 399-2467

swilliams_at_csm.edu<mailto:swilliams_at_csm.edu>

________________________________
From: colldv-request_at_lists.ala.org <colldv-request_at_lists.ala.org> on behalf of Smothers, Cynthia Diann <smothersd_at_winthrop.edu>
Sent: Monday, November 30, 2020 8:27 AM
To: colldv_at_lists.ala.org <colldv_at_lists.ala.org>
Subject: [ALCTS-colldv] Questions: revising collection development policy


Hi everyone,



I’d like to change our collection development policy away from a Conspectus-based model and toward something that is easier to update and use, perhaps similar to what Helen N. Levenson describes in her article “Nimble Collection Development Policies: An Achievable Goal” (Library Resources & Technical Services, October 2019). In addition to moving away from a Conspectus model, I’m planning to make some major revisions to how it’s written.



If you/your library has done something similar, I’d love to know how the change has worked out for your library since adopting the new policy. For example: Is there something you might do differently in hindsight? Is it working smoothly? Is it actually easier to use and update? What would you say to someone who might be anxious about such a change?



Thanks!



-Diann-





Diann Smothers

Head of Content Services



Winthrop University

Ida Jane Dacus Library

824 Oakland Avenue

Rock Hill, SC 29733



smothersd_at_winthrop.edu<mailto:smothersd_at_winthrop.edu>

www.winthrop.edu/dacus/<http://www.winthrop.edu/dacus/>