Building a Digital Repository Program with Limited Resources

Citation

MacDonald, R. (2011), "Building a Digital Repository Program with Limited Resources", The Electronic Library, Vol. 29 No. 6, pp. 854-855. https://doi.org/10.1108/02640471111188097

Battle‐scars are a good sign in authors of “how to” books; judging by this book Abby Clobridge's background in LIS work and experience in establishing an institutional repository at Bucknell University have left her with plenty. Early on she establishes a series of guiding principles then builds upon them with more detailed advice in later chapters, providing a consistent approach to much of her subject matter.

Clobridge first tackles how to get started on an institutional repository project in an orderly way. She begins with strategic planning: how to identify core constituencies and their needs; aligning a repository project with an institution's broader strategic goals. A fairly general overview of the technological issues involved in digital repositories is provided, before a chapter on staffing, including the value, and function of a steering group, and descriptions of various roles sure to be required, e.g. program coordinator or metadata librarian.

The second part of the book addresses the actual development of the repository. Metadata looms large; Clobridge describes the use of data dictionaries, metadata schemes (particularly Dublin Core), plus metadata production and harvesting. There are more guidelines (e.g. “focus on progress over perfection”), and an “introduction to metadata workshop” is included as an appendix. A wide‐ranging chapter on the initial phase of collection building covers the writing of project proposals (including a sample template), project planning, practical tips on processing large numbers of digital objects, and legal issues. Marketing and content recruitment is treated together, reflecting the relationship between the library and the institution it is a part of: while the library may be managing and implementing a repository project, it is likely to be other parts of the institution that will provide the content. Here Clobridge's principle of “don't make it about the library” stresses that involvement of other members of the institution in the repository's creation will help them see how it will serve their needs, and enhance their willingness to use and contribute to it. A chapter on open access examines what it means for online repositories, correcting several misconceptions, such as the relationship between open access and copyright. The long‐term preservation role of a repository is considered, including strategies for ensuring the survival of a coherent repository team as members come and go. A last chapter discusses assessment of the repository and its services, using Web site‐ and collection‐usage statistics, gathering feedback from users, and a timely reminder to “make decisions based on data”.

Practical advice is often in keeping with Clobridge's “limited resources” theme: audit to identify already available resources to avoid unnecessary purchases; seek input from institutional IT staff; involve (unpaid) LIS interns in the project. Similarity of subject matter invites comparison with Nabe's book Starting, Strengthening, and Managing Institutional Repositories, and the differing treatments complement each other well. Although Nabe provides a more rigorous framework for assessing the technologies associated with institutional repositories, Clobridge's emphasis on other aspects of such a project may well give her book a longer shelf‐life.