A poster given at the 2014 Open Repositories held in Helsinki. This poster will demonstrate the breadth of usage of the Hydra open repository solution within Europe, and highlight how the institutions using it have engaged with the Hydra community to establish their own repositories and fed into ongoing development. Readers will become aware of the use of Hydra within Europe, and how this relates to the Hydra project overall.
Keyword:
Community, Repository, Hydra, Blacklight, and Fedora
Subject:
Hydra Project
Creator:
Conrad, Anders, Wright, Nicola, Awre, Christopher L, Frost, Dermot, and Arambudo, Roger Guash
Contributor:
London School of Economics and Political Science, Trinity College Dublin, Royal Library, Copenhagen, Denmark, Theater Institute of Barcelona, and University of Hull
At the Digital Collections and Archives (DCA) at Tufts University we have designed, built, and integrated our archival collection management system and repository’s administrative interface to facilitate ingesting archival objects into our Fedora based repository. This 24x7 session briefly explores the assumptions and functional requirements we have used to guide this development work. The DCA’s unique position as an archives that is one of the key stakeholders and users of the Tufts institutional repository has enabled us to meet this integration challenge. The session describes how the integration of our archival collection management system and our repository relies on the ability to flexibly move metadata from one system to another. and A lightning talk given at the Open Repositories conference in 2015 held in Indianapolis described thus
Keyword:
Case study, Digital collections, Hydra, Repository, Archives, Open Repositories 2015, Lightning talk, and Metadata
Diving into the Technology of Hydramata". and A presentation to the Fedora Interest Group track at the 2014 Open Repositories held in Helsinki. As in the heading of the proposal, this was originally offered under the title "Extending the Hydra Head to Create a Pluggable, Extensible Architecture
Keyword:
Architecture, Repository, Curate gem, Hydra, Hydramata, Fedora, Import/export, Technology, Research data management, and Open Repositories 2014
Subject:
Hydra Project
Creator:
Johnson, Rick and Newman, Linda
Contributor:
University of Notre Dame and University of Cincinnati
A panel presentation given at the Open Repositories conference in 2015 held in Indianapolis described thus and Partnerships for shared repositories offer the promise of repository services at a decreased cost due to shared infrastructure and staff. In practice, reduced costs for shared repositories often require tradeoffs in security or access for the shared system. Staff working in a shared system may be geographically distributed or may work for different institutions with different priorities and reporting lines. Effective use of shared services requires thoughtful communication and tools that help maintain consistency and prevent conflicts when multiple people work in the same system. In this panel, shared repository service managers for multisite Islandora installations and a Hydra partnership will discuss methods for distributing system access and communicating with staff who work at our parent organizations, partner institutions, and third-party vendors. Each panelist will discuss the methods used so that distributed staff can have the level of access necessary to use the repository’s unique functions, while also ensuring that widely distributed system access doesn’t result in data loss or system failures.
Keyword:
Fedora, Digital collections, Hydra, Vendors, Open Repositories 2015, Islandora, Documentation, Repository, and Training
Subject:
Hydra Project
Creator:
Dean, Robin, Estlund, Karen, and Herbert, John
Contributor:
University of Oregon Libraries, CO Alliance of Research Libraries, and LYRASIS
A presentation given at Hydra Connect #2 described thus and Our first year of developing a Hydra-based institutional repository yielded many surprises, frustrations, and eureka moments. We will tell you what we wish someone had told us about the Hydra community, Rails applications, System/Stack deployment, and Developer collaboration.
Keyword:
Connect #2 (Fall 2014), Architecture, Hydra, and Repository