DuraCloud

DuraCloud
Name	DuraCloud
Developed by	DuraSpace
Initial release	2010
Latest release	2015
Programming language	Java
License	Open source

DuraCloud is a hosted digital preservation and content storage service originally developed to help libraries, archives, and cultural heritage institutions manage, preserve, and deliver digital content. It provides cloud-based storage, integrity checking, and access mechanisms designed for long-term stewardship of digital collections. Institutions such as Library of Congress, British Library, National Library of Australia, Stanford University, and King's College London have been referenced in related discussions about cloud preservation strategies.

Overview

DuraCloud was created to bridge institutional repositories and cloud storage providers like Amazon Web Services, Google Cloud Platform, and Microsoft Azure using preservation principles advocated by organizations including Digital Preservation Coalition, International Council on Archives, and OCLC. The service integrated with repository platforms such as Fedora Commons, DSpace, Islandora, and Omeka to enable content transfer from systems used by Harvard University, Yale University, University of Oxford, and Columbia University. Funders and partners involved in the project included Andrew W. Mellon Foundation, Jisc, and National Endowment for the Humanities.

Architecture and Components

DuraCloud's architecture combined a web application, storage adapters, checksum and fixity services, and delivery endpoints. The stack relied on components common to enterprise environments like Apache Tomcat, Spring Framework, and Hibernate with development practices influenced by projects at DuraSpace, Mozilla Foundation, and Internet Archive. Storage adapters targeted providers such as Amazon S3, Rackspace Cloud Files, and DreamHost and integration patterns echoed those used by LOCKSS and Archivematica. The system exposed APIs for batch ingest and management compatible with workflows used at institutions like Smithsonian Institution, National Archives and Records Administration, and Bibliothèque nationale de France.

Features and Functionality

Key features included automated fixity checking, content replication, transparent cloud storage abstraction, and public delivery via HTTP endpoints. It supported preservation actions and monitoring comparable to services discussed by PREMIS advocates and metadata frameworks used by Dublin Core proponents. Functional capabilities addressed ingest workflows familiar to practitioners at Princeton University, University of California, Berkeley, and Cornell University including scheduled integrity checks, replication policies, and comprehensive audit logs. The platform interoperated with metadata registries and standards promoted by International Federation of Library Associations and Institutions and Society of American Archivists.

Deployment and Integration

Deployment patterns for DuraCloud ranged from hosted offerings to on-premises adaptations using virtualization and containerization strategies inspired by practices at MIT, Caltech, and Los Alamos National Laboratory. Integration points included content management systems like Drupal, WordPress, and Blacklight-based discovery layers used by Duke University and University of Michigan. Automation and batch transfer methods paralleled techniques used in projects supported by Digital Library Federation and orchestration approaches discussed by CERN and National Institutes of Health.

History and Development

The project was initiated in the early 2010s by DuraSpace with community collaboration from repositories and cultural heritage institutions across North America, Europe, and Australasia. Development milestones referenced models from the Open Archives Initiative and received attention in conferences such as International Conference on Dublin Core and Metadata Applications, IASSIST, and Society of American Archivists Annual Meeting. Contributors included engineers and librarians from New York Public Library, Library and Archives Canada, Australian National University, and Princeton Plasma Physics Laboratory who adapted preservation workflows and service models influenced by LOCKSS and CLOCKSS.

Use Cases and Adoption

Typical use cases encompassed digital preservation for institutional repositories, web archiving complements to Internet Archive activities, research data stewardship for projects funded by National Science Foundation, and dissemination of cultural heritage digitization projects similar to collaborations with Getty Research Institute and Smithsonian Institution Libraries. Adoption scenarios involved consortia efforts at regional organizations such as Jisc and national programs run by bodies like National Library of Scotland and Portuguese National Library which explored cloud-based redundancy and access replication.

Security and Preservation Practices

Security and preservation practices implemented encryption-at-rest and in-transit strategies aligned with guidelines from National Institute of Standards and Technology, audit logging approaches used by European Union Agency for Cybersecurity, and access controls compatible with institutional identity providers like Shibboleth and CAS. Preservation policies emphasized fixity verification, replication across multiple storage endpoints, and provenance tracking consistent with standards promoted by PREMIS, OAIS Reference Model, and community recommendations from Digital Preservation Coalition and OCLC.

Category:Digital preservation