Harvard is issuing a Request for Proposals (RFP) for new digital repository infrastructure supporting both curatorial processing and preservation persistence. The repository system will replace Harvard’s existing Digital Repository System (DRS).
Background
- Harvard Library Digital Repository Service (DRS) has reached the conceptual and operational limits of its current design and implementation after 22 years of successfully managing and preserving more than 10.7 million digital objects, 913 million files, more than 90 formats, and 1.8 PB. The revitalized repository infrastructure must address identified needs, goals, and aspirations regarding function, scale, performance, sustainability, and innovation. The new system must be capable of supporting effective and efficient preservation of all existing, newly emerging, and unanticipated forms of digital scholarship and institutional records. Historically, the DRS has averaged annual growth of 10-15%. Harvard anticipates new initiatives in research data management, electronic records management, and mass audio/video digitization will increase the preserved corpus upwards of five to tenfold over the next several years. As a generational modernization, it is important that the new infrastructure is flexible and innovative enough to remain robust and productive in the face of ever-evolving organizational mission, strategic priorities, stakeholder ambition, and environmental conditions. Consequently, Harvard seeks a new repository system to steward and preserve its deep, broad, rich, and unique digital collections.
Scope
- Harvard has sufficient storage for its current digital collections and is looking for a flexible, extensible repository management system providing the highest functional levels of preservation service, assurance, and productivity through a clean, intuitive user experience. The system will be interoperable with other systems, including metadata providers and discovery gateways, and provide comprehensive support for asset management and digital preservation. Harvard is not seeking to replace its current storage solution but is open to exploring the possibility of a different storage solution if a compelling repository system requires it.
- Harvard would prefer a solution that allows for storage and repository services to function independently, that is, a system in which Harvard is able to change software platforms without migration of data in the storage layer. Harvard requires a system that supports all preservation repository functions while also connecting to existing Harvard systems for cataloging, reporting, access, and delivery to provide a seamless experience to meet the business needs and requirements of our users. The repository system has no responsibility for patron-facing discovery or access; all patron-facing discovery and delivery is the responsibility of other Harvard services. The repository system must provide content and metadata to those separate services as required but is not responsible for performing those roles.
Please see the full Harvard Digital Repository Request for Proposal Announcement document for more information.