How can we include user experience [UX] best practices in Hydra's core development work? How can UX experts contribute effectively to the Hydra project? How can we ensure that decisions around elements that affect the user experience are based on good evidence? Through case studies and facilitated discussion, this panel will seek to demonstrate and explore how to better integrate end-user feedback into the Hydra development stream. Dave McCallum from the University of Oregon explores issues of accessibility and the user experience. Jenn Colt from Cornell University and Sonya Betz from the University of Alberta will facilitate an active discussion around building UX into Hydra development workflows, and will ask participants to suggest strategies for including real users and their feedback in design and development decisions. The second presentation is available at the 'Related URL' below. An audio recording of the session is available for download below. and A presentation given at Hydra Connect 2016 described thus
Keyword:
Connect 2016, Hydra, and User experience
Subject:
Hydra Project
Creator:
Betz, Sonya, Colt, Jenn, and McCallum, David
Contributor:
Cornell University, University of Oregon, and University of Alberta
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
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 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
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 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
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
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
What does it mean to be a Hydra Partner? What does the Hydra community expect of Partners? What should Partners expect of the rest of the community? Join us to discuss expectations, contributions and the advantages of Partnership. and An audio recording (of mixed quality) of a panel session at Hydra Connect 2016 described thus
A partial audio recording (of mixed quality) of a panel session at Hydra Connect 2016 described thus and Regional meetings are a great way to stay connected with your fellow Hydranauts throughout the year. Hear from past organizers about their experiences and tips, and learn about community resources to help get you started. It is also a chance to connect with other individuals in your region who are interested in organizing a future event.
Keyword:
Regional event, Connect 2016, and Hydra
Subject:
Hydra Project
Creator:
Rhoads, Joseph, Rissmeyer, Chrissy, Allinson, Julie, Cariani, Karen, and Newman, Linda
As a manager, one of the biggest challenges when starting any project (Hydra, or otherwise) is feeling comfortable that you’ve asked all the right questions before the first development hour is logged. But what are the right questions? And once you begin, how do you ensure that you, your developers and your stakeholders remain on the same page throughout the course of the engagement? This presentation will explore two processes that DCE employs to tackle these concerns, A partial audio recording of a presentation at Hydra Connect 2016 described thus, and the Scoping Phase and the Inception Deck. We'll explore how these to practices work to consolidate project expectations and fend-off wild assumptions, helping you to feel confident that when everyone says ‘circle,’ no one is picturing a square.
A presentation at Hydra Connect 2016 described thus and Join us for a technical overview of the Hydra-in-a-Box hosted platform where we will detail how we're using Amazon cloud services and how we've evolved Hydra and Fedora to use them effectively. We will discuss how we've architected the traditional Hydra stack to be highly available, scalable, auto-deployed, and cloud friendly. This is an audio recording of the session.
Keyword:
Hydra, Cloud services, Hydra in a Box, and Connect 2016
A panel session at Hydra Connect 2016 described thus, Service management is not just for managers! How managers, developers, librarians, and other team members can all work together to improve Hydra service management. Sharing success stories and best practices, and sharing challenges and potential solutions. This is an audio recording of the session.
Keyword:
Service management, Connect 2016, and Hydra
Subject:
Hydra Project
Creator:
Frost, Hannah, Johnson, Rick, Cane, Debs, Van Tuyl, Steve, and Cameron, Jon
An introduction to IPFS, IPLD and how the decentralized web solves long-standing problems for Libraries, Archives and anyone who uses linked data. This is an audio recording of the session. and A lightning talk presentation at Hydra Connect 2016 described thus
Keyword:
Connect 2016, Hydra, Linked data, and Lightning talk
Sipity, long the envy of the Hydra community, has support for multiple, configurable complex workflows. At it's heart is a state machine, which allows users with certain roles to take actions which trigger notifications, and custom code. I'll demonstrate how we've brought this to CurationConcerns. This is a partial audio recording of the session. and A lightning talk presentation at Hydra Connect 2016 described thus
Keyword:
Connect 2016, Hydra, Curation Concerns, and Lightning talk
Yes! Another Blacklight mapping plugin! This one is super cool with features like performant Solr clustering, indexing multiple types of geometry (bounding boxes and points!) This is an audio recording of the session. and A lightning talk presentation at Hydra Connect 2016 described thus
Keyword:
Blacklight, Connect 2016, Hydra, and Lightning talk
Migrating a Fedora 3-based Hydra repository to Fedora 4 can be a major undertaking. This panel will bring together representatives from multiple institutions that either are planning for, are in the midst of, or have completed such a migration. Depending on where they are in the migration process, panelists will talk about their plans for migration, techniques used or expected to be used, obstacles anticipated or encountered, how problems were addressed, and migration outcomes. It is hoped that the presentations and discussion will be useful to other Hydra sites planning such a migration. A video of this session is available at the 'Related URL' below. and A presentation given at Hydra Connect 2016 described thus
Keyword:
Fedora, Connect 2016, Hydra, and Migration
Subject:
Hydra Project
Creator:
Coble, Jim, Wead, Adam, Hardesty, Juliet L, and Friscia, Mike
Follow-up to last year's presentation about Columbia's Hyacinth editor. Lots of changes / progress since the last presentation. Many TODOs have been TODONE. Hyacinth is a metadata editor, batch Fedora ingest tool and content publishing application that is becoming more and more integrated into our digitization, cataloging and front-end presentation workflows. Built on top of Hydra, but not Blacklight, with a JavaScript-and-AJAX-heavy front-end for many search/editing features. Currently Fedora 3, but hopefully moving toward Fedora 4 early next year. Still under development with additional planned features. I'd love to present and get feedback. A video of this session is available at the 'Related URL' below. and A lightning talk presentation at Hydra Connect 2016 described thus
The Hydra-in-a-Box team in conjunction with Princeton has added IIIF image and presentation API support to Hydra. Come see how we're going farther together with open APIs. A video of this session is available at the 'Related URL' below. and A lightning talk presentation given at Hydra Connect 2016 described thus
Keyword:
International Image Interoperability Framework (IIIF), Connect 2016, Hydra in a Box, Hydra, and Lightning talk
We encountered big performance hurdles with our Sufia6 based application HydraNorth, and this is a quick overview of tools we used to help us monitoring and profiling the performance of our application, and restoring sanity to our team. A video of this session is available at the 'Related URL' below. and A lightning talk presentation given at Hydra Connect 2016 described thus
An overview of the Jisc Research Data Management Shared Service initiative in the UK, looking to establish a set of infrastructural components that academic institutions can combine to provide an overall RDM solution. Hydra has been shortlisted as one of the repository components that an initial group of pilot institutions can use. A video of this session is available at the 'Related URL' below. and A lightning talk presentation at Hydra Connect 2016 described thus
Keyword:
Connect 2016, Research data management, Jisc, Hydra, and Lightning talk
Blacklight, International Image Interoperability Framework (IIIF), Newspapers, Connect 2016, Research data management, and Text Encoding Initiative (TEI)
