lrts: Vol. 52 Issue 4: p. 270
Book Review: Institutional Repositories
Mary Beth Weber

Mary Beth Weber, Rutgers University, New Brunswick, N.J.; mbfecko@rci.rutgers.edu

Institutional Repositories, number 292 in the Association of Research Libraries (ARL) SPEC Kit series, is based on the findings from a survey that was distributed to 123 member libraries of ARL in January 2006. The survey was implemented to collect baseline information regarding ARL members’ activities about institutional repositories. The authors explain that the survey defines “institutional repository” as a “permanent, institution-wide repository of diverse locally produced digital works” (23) for public use that also supports metadata harvesting. Their definition also includes repositories that are shared among institutions.

The SPEC survey was designed by an impressive team of individuals from the University of Houston who represent a wide array of expertise, including electronic resources acquisitions, metadata creation, Web development, and special libraries (law and pharmacy). That team included Charles W. Bailey Jr., who was the Assistant Dean for Digital Library Planning and Development at that time (Bailey left the University of Houston in January 2007), and Jill Emery, director or the Electronic Resources Program, both recognized experts in their respective fields of work.

An examination of the survey responses yields some interesting figures. First, there was a 71 percent response rate (eighty-seven libraries responded), which is quite high. While the responding libraries are primarily American institutions, respondents also included Canadian member libraries.

When the survey was implemented, thirty-seven institutions had an operational institutional repository, another thirty-five had a target date of 2007 to make their repositories fully operational, and nineteen libraries had no immediate plans to develop an institutional repository. The volume was published in 2006, and it would be worth investigating how these libraries are now faring in terms of content (both level of content and success in recruiting it), if their policies have changed in any way and why, and how many of them are still using their original repository software. Additionally, it would be an interesting exercise to determine if any of the responding libraries that have indicated that they had no immediate plans to develop a repository have changed their plans and how.

Institutional Repositories is divided into three broad areas: (1) survey results, which includes an executive summary, the survey questions and responses, and a list of the institutions that responded to the survey; (2) representative documents from various responding libraries, which include institutional repository home pages, usage statistics, deposit policies, deposit agreements, metadata policies, digital preservation policies, institutional repository proposals, and promotion; and (3) the last section, which consists of selected resources, including general works and information specific to DSpace, eScholarship, and Fedora. The documents in the second section, such as deposit policies and agreements, are quite detailed and provide a wealth of information for institutions seeking sample documents for use in formulating their own policies.

The bulk of the volume consists of the full questionnaire, responses, and selected comments from the responses. The survey questions address a range of topics that include planning, implementation, assessment, staffing, units responsible for ongoing operation of the repository, budget, hardware and software, policies and procedures, content recruitment, and assessment. The executive summary examines these topics in detail and provides analysis and percentages.

The questions run the gamut of potential issues an institution needs to consider when planning to launch an institutional repository or when assessing progress and addressing areas of need.

Another notable fact about the survey results is that the predominant repository software used by respondents is DSpace. This is quite logical given that the first version of DSpace was released in November 2002, giving it ample time to capture some share of the market by 2006. In contrast, Fedora repository software was created late in 2003, and libraries would not have as much exposure to this software. A review of the Fedora Commons Community Registry indicates 127 known Fedora projects as of June 2008.1 In comparison, the DSpace Foundation’s Web site indicates that it has the largest community of developers and users worldwide, and reports that over 250 institutions are currently using the DSpace software.2 The last point becomes more significant in light of the fact that in June 2008, DSpace and Fedora actively engaged in conversations regarding a possible collaboration.

The text is well organized, comprehensive in scope, and provides a wide variety of examples that may be consulted for comparison and guidance. Institutional Repositories is appropriate for libraries with an operational institutional repository as well as those institutions that are in the planning or investigation stage. Since repositories are a fairly new development (despite the fact that the executive summary notes that one responding library had an operational repository in 1999) and a culture change for libraries, a follow-up survey and a comparable summary of the results would be very beneficial to the profession.


References
1. Fedora, “Fedora Commons Community Registry,” www.fedora.info/wiki/index.php/Fedora_Commons_Community_Registry (accessed July 11, 2008)
2. DSpace Foundation, “Community,” www.dspace.org/index.hp?option=com_content&task=view&id=305&Itemid=142 (accessed July 11, 2008)

Article Categories:
  • Library and Information Science
    • Book Reviews

Refbacks

  • There are currently no refbacks.


ALA Privacy Policy

© 2024 Core