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
Indiana University and Northwestern University, in collaboration with nine partner institutions, recently completed the last year of a three-year IMLS-funded effort to build the Avalon Media System, an open source solution for managing and providing access to digital audio and video collections, based on Fedora and the Hydra repository software development framework. As the Avalon platform reaches maturity, several institutions are in the process of implementing Avalon both to replace current time-based media access solutions and to support new use cases. In addition, new funding from the Andrew W. Mellon Foundation will support continued work to develop new features, grow and provide support for the community of adopters, and move Avalon towards organizational and financial sustainability. This panel will bring together project leaders from Indiana and Northwestern, along with Avalon community members at the University of Virginia and Stanford University, to share experiences of implementing Avalon at their institutions, integrating Avalon with other local systems, and supporting Avalon to enable a variety of use cases in research, teaching, and learning. Panel members will also discuss future development plans and provide a preview of how the project intends to transition from a grant-supported endeavor to a community-sustained solution. and Slides for a panel presentation given at the Open Repositories conference in 2015 held in Indianapolis described thus
Keyword:
Fedora, Avalon, Digital collections, Hydra, Repository, Sustainability, Open Repositories 2015, Community, Digitization, Preservation, Workflow, and Archives
Subject:
Avalon Media System
Creator:
Frost, Hannah, Grants, Dunn, Jon, Rudder, Julie, Cane, Debs, and Durbin, Mike
Contributor:
Andrew W Mellon Foundation, University of Virginia, Stanford University, Northwestern University, and Indiana University
A proposal for a presentation given at the Open Repositories conference in 2015 held in Indianapolis described thus, One of the many successes of the Hydra community is the fundamental notion from which its name is derived—the concept of many interfaces (“heads”) over top of a single repository (the “body”). The recent release of Fedora 4, with its internal RDF-centric model, has spurred efforts for a community-wide model of collections and works, such that the heads can be sure that the body will behave as they expect it to. That model has been designed and vetted by the Hydra community, and its architecture and initial implementations will be presented in this paper. [Note, and the subject of this proposal has since become known as the 'Portland Common Data Model'.]
Keyword:
Community, Data model, Resource Description Framework (RDF), Hydra, Portland Common Data Model (PCDM), Open Repositories 2015, and Fedora
Subject:
Hydra Project
Creator:
Stroop, Jon, Sanderson, Rob, and Cowles, Esmé
Contributor:
University of California San Diego, Princeton University, and Stanford University
Open source software isn’t really free. This might seem obvious to some, but there are many members of open source communities that consume rather than contribute, Slides from a panel session given at the Open Repositories conference in 2015 held in Indianapolis described thus, and they use the software but are either unwilling or unable to engage with the community to write code, submit use cases, create documentation, or do any of the other things that make an open source project a success. Fortunately, things don't have to be this way. Over the past two years, the Fedora project has undertaken a great effort to revitalize not only the software but the community itself. By maintaining open, transparent communication, soliciting use cases, development, and testing from community members, and establishing a clear project governance structure, we have laid the groundwork for a successful community source project. At the same time, the Islandora and Hydra communities have pursued similar strategies to build and sustain their own communities and the broader Fedora community. This panel will feature a discussion on the recent successes of the Fedora community and future plans to continue raising the level of community engagement and project ownership.
Keyword:
Community, Collaboration, Islandora, Hydra, Open Repositories 2015, and Fedora
Subject:
Hydra Project
Creator:
Ruest, Nick, Wilcox, David, and Cramer, Tom
Contributor:
York University, DuraSpace, and Stanford University