Using Sufia 7 as a reference model, what does the path for depositing a new item into a Hydra/PCDM based repository look like from an end-user, code, console, solr, and fedora perspective, A presentation given at Hydra Connect 2016 described thus, show the upload of new digital content via the Sufia UI and show each step of the data flow in the Browser, rails console, and Fedora. Walk through derivative generation and show the various PCDM relationships being built at each stage. Then add a new user collection, and walk through the same flows as a work is added to a collection, and what gems are in play, what does the data look like from a ruby developer perspective, what is persisted in Fedora and Solr - how does it all relate to PCDM? A video of this session is available at the 'Related URL' below.
Keyword:
Connect 2016, Hydra, Portland Common Data Model (PCDM), and Sufia
For Hydra Connect 2016, the local organizers took the project's basic logo and extended it. It was used on large display screens adjacent to the conference's main auditorium.
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
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 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 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.
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
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
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 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.
