Using Hydra to manage and present cultural heritage resources raises a set of interesting challenges that are beyond the scope of the traditional institutional repository. These include more complex data models, elaborate and varied workflows, richer descriptive metadata, support for more and varied controlled vocabularies, the requirement to manage larger objects comprised of larger files and multiple derivatives, support for IIIF, and a desire for richer viewing environments in general. In this presentation we will discuss these challenges and highlight examples and implementations that have gone ‘beyond the repository’. An audio recording of the session is available for download below. and A presentation at Hydra Connect 2016 described thus
Keyword:
International Image Interoperability Framework (IIIF), Connect 2016, Workflow, Hydra, and Metadata
Subject:
Hydra Project
Creator:
Allinson, Julie and Stroop, Jon
Contributor:
Princeton University Library and University of York
Highlight the contributions many Hydra institutions are making towards Fedora as a way to advance their Hydra environments, as exemplars of how the two projects are symbiotic. An audio recording of the session is available for download below., A presentation at Hydra Connect 2016 described thus, Advance a Hydra platform statement on the importance of supporting Fedora in general, Generate awareness of the role client platforms play in shaping Fedora development, Generate awareness of the role Fedora plays in the Hydra stack, Fedora provides an essential foundational layer to the Hydra Stack that may seem opaque to many in the Hydra Community. Recent community discussions have highlighted the technical and community relationship between Hydra and Fedora, the value proposition of Fedora, and Fedora's role in an institution's broader preservation strategy. As the Hydra Community continues to thrive, the intersection of the larger repository community and role with these technologies is an important community rallying area. This session is intended to, and Discuss methods for approaching development of features along the Hydra and Fedora stack continuum
Keyword:
Fedora, Connect 2016, and Hydra
Subject:
Hydra Project
Creator:
Cramer, Tom, Estlund, Karen, and Armintor, Benjamin
A presentation at Hydra Connect 2016 described thus and This case study will address the initial decisions and reasons for switching to Hydra, prototyping for launch of Hydra head, metadata cleanup and asset migration, final quality review, and lessons learned. An audio recording of the session is available for download below.
Keyword:
Case study, Connect 2016, Hydra, and Migration
Subject:
Hydra Project
Creator:
Simic, Julia, Wick, Ryan, Mellinger, Margaret, and Sato, Linda
Contributor:
University of Oregon Libraries and Oregon State University Libraries
GeoConcerns is a plugin to CurationConcerns for managing geospatial resources in a repository (http, A presentation at Hydra Connect 2016 described thus, and //geoconcerns.github.io). This presentation will give an overview and demonstration of GeoConcerns’ features and PCDM-based data model. In addition, we will discuss the code base and future development work such as integration with Sufia. An audio recording of the session is available for download below.
Keyword:
Geodata, Connect 2016, Hydra, and Portland Common Data Model (PCDM)
A presentation at Hydra Connect 2016 described thus, In this presentation, we will present a software development and deployment process that we have developed at Virginia Tech. We have used this procedure to develop several Hydra projects for University Libraries services at Virginia Tech and have also used it to conduct interviews for Ruby and Rails developers. We implemented a central vagrant box to facilitate the development and deployment processes. Using this vagrant box gives us many benefits, and 1. Code immediately. Our software engineers can focus on coding without worrying about software installation. 2. Unified development environment. All developers do their work in the same, consistent development environment. 3. Development of multiple projects simultaneously. Developers can work on multiple projects in parallel, switching between project environments in just a few minutes. 4. Minimal differences between development environments and production environment. After we finish implementation, we can quickly deploy our applications into a cloud environment (e.g. AWS and OpenStack) that is highly consistent with our development environments. We will present and demonstrate our hands-on experience on how we use a single vagrant box with different GitHub repositories to develop multiple Hydra applications in detail, including Sufia, GeoBlacklight, Fedora, Solr, Vagrant, AWS, and OpenStack. An audio recording of the session is available for download below.
Archiving Research Data into Hydra through the Open Science Framework (OSF) - A look at initial work of Notre Dame and Johns Hopkins to archive research projects from the OSF into Fedora and Hydra repositories, and first implementation of a Fedora Research Object Model. This plugs into a service offering of the Center for for Open Science, OSF for Institutions (OSF4I). ND/JHU version will be initial support for OSF Fedora Archiving Add-on in the OSF as part of OSF4I offering. We hope to start discussion around next steps for other Hydra institutions to use this along with OSF4I to allow them support to archive research data from the OSF into their own Hydra/Fedora repository. An audio recording of the session is available for download below. and A presentation given at Hydra Connect 2016 described thus
A workshop given at Hydra Connect #2 described thus and This workshop will offer three detailed demos and case studies of mature production systems from the Hydra community. The contrasting case studies are Hydra@Hull from the University of Hull, Avalon Media Systems from Indiana University and Northwestern University, and ScholarSphere from Penn State University
Keyword:
Connect #2 (Fall 2014), Case study, Hydra, Avalon, and Workshop
Subject:
Hydra Project
Creator:
Klein, Michael B, Cole, Carolyn, and Green, Richard A
Contributor:
Avalon Media System, Penn State University, and University of Hull
Slides from a workshop given at Hydra Connect #2 described thus and Agile is based on self-organizing cross-functional teams addressing evolving requirements and delivering solutions incrementally. Adaptive planning and continuous improvement make Agile teams highly flexible and able to rapidly respond to change. Participants in this workshop will learn about the principles and benefits of Agile and will engage in core Agile activities that they can take back to their own teams.
In the UK, the Universities of York and Hull are looking at Archivematica's place in a research data pipeline. The two universities have slightly different use cases but share the desire to put research (and likely other) content through Archivematica on its way to the repository thus giving us a solid base for long-term preservation. We are both now in the third phase of a joint project to build proof-of-concepts to illustrate how Hydra and Archivematica can work together to manage and preserve research data. Since our project began, Jisc have launched an ambitious UK national research data shared service where a range of suppliers offer systems in different lots. Both Hydra / Fedora and Islandora / Fedora are part of the the ‘research repository’ lot of the service and the work of York and Hull has heavily informed the ‘preservation’ lot, with Archivematica one of the systems on offer. This presentation will describe the proof-of-concept work done by Hull and York, and will provide an overview of the new Jisc service. An audio recording of the session is available for download below. and A presentation at Hydra Connect 2016 described thus
Keyword:
Connect 2016, Archivematica, Workflow, Hydra, and Preservation
