A presentation given at the Open Repositories conference in 2010. In part, the proposal reads and While repositories provide obvious benefits in hosting and managing content, it is equally clear that there is no “one size fits all” solution to the range of digital asset management needs at a typical institution, much less across institutions. A system that supports the submission, approval and dissemination of electronic theses and dissertations, for example, has demonstrably different requirements than a digitization workflow solution, an e-science data repository, or media preservation and access system. There is a clear need in the repository community to readily develop and deploy content-, domain-, and institution-specific solutions that integrate the flexibility and richness of customized applications and workflows with the underlying power of repositories for content management, access and preservation. This paper will provide an overview of Hydra’s philosophy, architecture, and components, as well as demonstrations of various Hydra installations. The paper will also provide a progress report on Hydra development to date and its overall roadmap, as well as provide observations on the successes and challenges of community-based development of shared repository solutions.
Keyword:
Community, Open Repositories 2010, Architecture, Repository, and Hydra
Subject:
Hydra Project
Creator:
Sadler, Bess, Sigmon, Tim, Mene, Willy, Green, Richard A, Staples, Thornton, McRae, Lynn, Cramer, Tom, and Awre, Christopher L
Contributor:
University of Hull, DuraSpace, University of Virginia, and Stanford University
The Hydra Project started in 2008 through a partnership between the University of Hull, the University of Virginia, Stanford University and Fedora Commons (now DuraSpace) to create tools that support use of the Fedora digital repository. Hull adopted the software outputs from this collaboration for its institutional repository in 2011 and remains an active Partner in the community, serving on the Steering Group and fostering development of the community and software in the UK and mainland Europe and The community now has 35 formal Partners and over 70 known adopters internationally. In June 2017 Hydra changed its name to Samvera, Icelandic for 'being together', to recognize the value gained from multiple institutions working together to create the underlying common basis upon which multiple different repository solutions have been implemented. Samvera can be adopted through a set of tools to develop your own repository (using a package called Hyrax as the starting point) and is also available as a complete repository solution, hosted or local, through the use of Hyku. The community has been at the heart of making Samvera a success, and will continue to underpin its future direction.
This session will be a brief introduction to the Hydra community, and a 35,000ft view of Hydra technically. It is an opportunity for people new to Hydra to get some context around what we are about and, hence, the rest of the conference! and An introductory presentation at Hydra Connect 2016, described thus