Two or so years into the Hydra project, around 2010, an on-line demonstrator was produced for the emerging software. The product was called Hydrangea. It proved difficult to keep up to date at a time of rapid development and was soon dropped - but it was in use long enough to get its own logo.
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
The team that founded the Hydra Project met several times in the fall of 2008 at the University of Virginia. At their meeting in December of that year the name 'Hydra' was coined. Later that same day, a hydra toy was spotted, and subsequently purchased, in a local shop - this became part of the first design used on the project's documents and presentations.
The keynote address at the Hydra Connect 2016 conference advertised thus and This presentation aims to present opportunities for collaboration between current Hydra members and The Daniel Cosío Villegas library at El Colegio de México (COLMEX) as well as other Mexican institutions that are interested in making a Mexican-based Hydra users group. COLMEX has been actively planning the implementation of a Hydra-based repository. Given that COLMEX has a significant presence in various digital libraries and repositories interest groups in Mexico, we have taken the opportunity promote Hydra as an alternative, not only with the hopes of promoting the project but to find local partners that might be interested in collaborating. We hope that we might find international partners who will help to spur initiatives through various means of evangelizing, helping support efforts, and perhaps coming down to Mexico to visit. In this manner we can help Hydra become a truly global initiative and one which considers north-south collaborations especially those outside the English-speaking world.
Keyword:
Collaboration, Connect 2016, and Hydra
Subject:
Hydra Project
Creator:
Martinez, Alberto
Contributor:
El Colegio de México, Daniel Cosío Villegas Library
A presentation given at Hydra Connect #2, advertised as "is Fedora 4 a good option for my needs?" and described thus and This session will discuss some of the features that are new in Fedora 4 that will undoubtedly send dazzles up the Hydra stack.
Keyword:
Fedora, Connect #2 (Fall 2014), Architecture, and Hydra
A plenary presentation at Hydra Connect 2016 advertised thus and An update on recent progress on the Hydra in a Box project, including work related to product development for the repository and metadata aggregation components, development of the hosted service, development and infrastructural decisions, and community engagement. A video of this session is available at the 'Related URL' below.
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
This annual report on the Hydra Project will provide a synopsis of the project’s current state from a high level perspective, including recent developments and important trends in adoption and activiity, the technical framework, the community framework, major projects and milestones, and where we may be going in the near future. With so much activity in so many different parts of the project, this session is a chance to take a step back from the many trees to survey the whole forest of the HydraSphere. A video of this session is available at the 'Related URL' below. (Very Low Audio for half of this and then just regular Low Audio - max out volume with headphones to hear) and The 'State of the HydraSphere' address given at Hydra Connect 2016, advertised thus
Do you ever wonder what working groups exist in the Hydra community or what topics are being discussed or how to spark a discussion or a working group? We are proposing a framework for interest groups and working groups which has proven effective in other successful communities toward raising awareness, connecting members with common interests, spawning action oriented working groups and making time at face to face meetings in support of both "percolating" ideas and heads down work. Join us to explore how this framework can further empower our community. and A presentation at Hydra Connect #2 described thus
Keyword:
Connect #2 (Fall 2014), Governance, Interest and Working Groups, Hydra, and Community
Subject:
Hydra Project
Creator:
Ruggaber, Robin and Sanderson, Rob
Contributor:
University of Virginia and Stanford University Libraries
A presentation given at Hydra Connect 2016, described thus and 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.
Keyword:
Fedora, Connect 2016, Workflow, Hydra, and Archives
how to add project and how to promote project to Project-Hydra. In addition we will examine a few nominated projects to see if we can promote them., We will examine Hydra-Labs and the processes we should adopt for it including, and A workshop given at Hydra Connect #2 described thus
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
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.
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
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
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.
In the last few years, as the Hydra partnership has grown to encompass twenty-five institutions, management of services for Hydra heads in production has become a topic of recurring interest and concern. What are the basic goals and requirements for successful service management of Hydra-based technologies? What roles need to be in place? How should user services be fostered and assessed? This panel session, conducted by three service managers from three different institutions, will address some common approaches to inform the start of a community toolbox for service management of a production Hydra head. and A panel session at Hydra Connect #2 described thus
Keyword:
Service management, Connect #2 (Fall 2014), Panel, and Hydra
Subject:
Hydra Project
Creator:
Frost, Hannah, Stewart, Claire, and Hswe, Particia
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 brief update on the current state of Fedora 4, followed by a high-level feature discussion for managers and a hands-on test drive for developers. and A workshop given at Hydra Connect #2 described thus
Keyword:
Fedora, Connect #2 (Fall 2014), Hydra, and Workshop
A presentation at Hydra Connect 2016 described thus and A follow-up to our presentation at Hydra Virtual Connect to show the progress we've made on Opaquenamespace.org. We'll discuss how we are using Git and github as our master-copy for RDF graphs, and using Blazegraph and the triplestore-adapter gem for our operational datastore. An audio recording of the session is available for download below.
Keyword:
Resource Description Framework (RDF), Connect 2016, and Hydra
Subject:
Hydra Project
Creator:
Wick, Ryan, Gum, Josh, and Sato, Linda
Contributor:
University of Oregon Libraries and Oregon State University Libraries and Press
A presentation at Hydra Connect 2016 described thus and A review of available APIs and services for identifying, and either manually or automatically loading, open source online content into a local IR. Grey areas, policy questions, challenges and opportunities. A video of this session is available at the 'Related URL' below.
Keyword:
Open access, Connect 2016, and Hydra
Subject:
Hydra Project
Creator:
Newman, Linda
Contributor:
Horton, Glen, Konecny, Mark, University of Cincinnati, and Van Mil, James
A presentation at Hydra Connect 2016, described thus and The Hydra stack is large and complex, getting a handle on what's causing a specific slowdown can be difficult. This session would recommend some tools, strategies, and places to look for improving the performance of your application. An audio recording of the session is available for download below.
A recap of the group's recommendations for the upcoming (now released) Sufia 7 – thoughts on the diverse needs of the community and the result, What worked, what didn't work, how to approach it next time. An audio recording of the session is available for download below. and A presentation at Hydra Connect 2016, described thus
Keyword:
Interest and Working Groups, Connect 2016, Hydra, User experience, and Sufia
I will show the data model migration from Sufia 6 to Sufia PCDM we used for ScholarSphere. In addition I will the outline major design decisions we made along the way. Then we will look at the tools in Sufia for migration of data from Sufia 6 to Sufia PCDM. I will include examples of extending the functionality for people who have extended the basic Sufia 6 model. An audio recording of the session is available for download below. and A presentation at Hydra Connect 2016, described thus
Keyword:
Connect 2016, Hydra, Portland Common Data Model (PCDM), and Sufia
A report of Michigan's early-stage investigation into building a Hydra publihing platform, which will eventually include support for fully-encoded text with an eye towards migrating level-4 TEI texts from DLXS and possibly including EPUB 3. and A lightning talk presentation at Hydra Connect 2016, described thus
Keyword:
Connect 2016, Hydra, and Lightning talk
Subject:
Hydra Project
Creator:
Morse, Jeremy
Contributor:
Andrew W Mellon Foundation, Penn State University Press, Northwestern University Press, Indiana University Press, and Michigan Publishing, University of Michigan Library
Generalizing from discussions within the GIS Data Modeling Working Group, this talk aims to address the potential benefits and risks involved in attempting to integrate Vagrant Boxes (virtual machine images) into software development and service deployment life cycles. An audio recording of the session is available for download below. and A lightning talk presentation at Hydra Connect 2016, described thus
Keyword:
Deployment, Connect 2016, Hydra, and Lightning talk
Subject:
Hydra Project
Creator:
Griffin, James
Contributor:
Lafayette College Libraries and GIS Data Modeling Working Group
The session focuses on open approaches to sharing geospatial metadata. We will discuss issues around standard requirements, appropriate linked data predicates, using linked data for placenames and gazetteers, participating in organizations and networks for sharing like OpenGeoMetadata, and identifying available tools and resources. An audio recording of the session is available for download below. and A panel presentation at Hydra Connect 2016, described thus
Keyword:
Geodata, Connect 2016, Hydra, and Linked data
Subject:
Hydra Project
Creator:
Durante, Kim, Battista, Andrew, Hardy, Darren, Griffin, James, Reed, Jack, and Barnett, Chris
Blacklight, Fedora, Collaboration, Connect #2 (Fall 2014), Hydra, and Community
Subject:
Hydra Project
Creator:
Arambudo, Roger Guash, Awre, Christopher L, Conrad, Anders, Frost, Dermot, and Wright, Nicola
Contributor:
Trinity College, Dublin, Ireland, Theatre Institute of Barcelona, Royal Library, Copenhagen, Denmark, London School of Economics and Political Science, and University of Hull
A lightning fast overview of free or cheap, cool and useful Ruby and Rails web sites, blogs, podcasts, videos, and users groups for new and not-so-new Hydra developers. I'll talk fast, but don't worry, I'll post the links on-line before the talk. A video of this session is available at the 'Related URL' below. and A lightning talk presentation at Hydra Connect 2016, described thus
