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
This presentation will focus on Northwestern University and Indiana University’s continued work toward a sustainable model for support, maintenance, and development of the Avalon Media System - an open-source, Samvera-based repository for audio and video jointly developed since 2011. Over the last two years, the team has focused on widening engagement with and commitment to the Samvera and IIIF communities as well as developing wider developer interest by re-basing the product on top of Hyrax and developing a modular architecture. and A proposal and presentation given at the Open Repositories conference in Hamburg, Germany, in 2019, described thus
Keyword:
Grants, International Image Interoperability Framework (IIIF), Avalon, Samvera, Open Repositories 2019, Sustainability, and Hyrax
Subject:
Avalon Media System
Creator:
Dunn, Jon, Schober, David, and Steans, Ryan
Contributor:
Andrew W Mellon Foundation, Indiana University, Samvera, Institute of Museum and Library Services, and Northwestern University
A presentation given at the Open Repositories conference in 2015 held in Indianapolis, described thus, Fedora, Hydra, Solr, and Blacklight. Called “Ichabod,” this tool has allowed us to ingest, normalize, and enrich metadata from diverse systems of record and make it consumable by our main discovery tool, which is powered by the Ex-Libris product Primo. We developed Ichabod using the Agile methodology and involving developers from three distinct NYU Libraries groups. The software will lay the groundwork for future innovation in the areas of metadata management and discovery for repository content. The relationships we established have already made it possible for a similar collaboration arrangement on two other projects, with more to come in the future., and From DSpace to Drupal, NYU has a variety of systems to ingest and display curated digital content. To make this content discoverable centrally, we developed a tool for metadata ingest, transformation, and discovery based on a popular open-source software stack
Keyword:
Metadata, Workflow, Architecture, Hydra, Open Repositories 2015, Blacklight, Digital collections, Fedora, and Solr
Subject:
Hydra Project
Creator:
Pechekhonova, Ekaterina, Harper, Corey, Kassel, Carol, and Lovins, Daniel
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
As part of the Mellon-funded AIMS project, the Universities of Virginia, Hull, Stanford and Yale have spent the last two years exploring the ramifications and distinct requirements of born digital archival materials in libraries. This presentation focuses on the partners’ research and prototyping of tools, infrastructure and workflows necessary to provide an end-to-end environment for born digital archival materials.
Keyword:
Grants, DLF Forum 2011, Hydra, and Archives
Subject:
Hydra Project
Creator:
Dushay, Naomi, Meloni, Julie, Cramer, Tom, Olson, Michael, and Daigle, Bradley
Contributor:
Yale University, Andrew W Mellon Foundation, University of Virginia, and Stanford University
A presentation given at the Open Repositories conference in 2010. In part, the proposal reads and While repositories provide obvious benefits in hosting and managing content, it is equally clear that there is no “one size fits all” solution to the range of digital asset management needs at a typical institution, much less across institutions. A system that supports the submission, approval and dissemination of electronic theses and dissertations, for example, has demonstrably different requirements than a digitization workflow solution, an e-science data repository, or media preservation and access system. There is a clear need in the repository community to readily develop and deploy content-, domain-, and institution-specific solutions that integrate the flexibility and richness of customized applications and workflows with the underlying power of repositories for content management, access and preservation. This paper will provide an overview of Hydra’s philosophy, architecture, and components, as well as demonstrations of various Hydra installations. The paper will also provide a progress report on Hydra development to date and its overall roadmap, as well as provide observations on the successes and challenges of community-based development of shared repository solutions.
Keyword:
Community, Open Repositories 2010, Architecture, Repository, and Hydra
Subject:
Hydra Project
Creator:
Sadler, Bess, Sigmon, Tim, Mene, Willy, Green, Richard A, Staples, Thornton, McRae, Lynn, Cramer, Tom, and Awre, Christopher L
Contributor:
University of Hull, DuraSpace, University of Virginia, and Stanford University
A presentation given at the Open Repositories conference in 2009. Part of the proposal reads and Repositories have proven themselves as powerful tools for managing digital content in many different contexts. But experience has also shown that there are real, practical limits in trying to extend a single repository solution to meet the manifold needs of most institutions for their full range of digital content and use cases. Relatively narrow and inflexible application front ends can be used to create single-purpose repository-powered solutions, but they do not lend themselves to being quickly and easily repurposed to meet variations in content type or user interactions. There is a clear business need for a flexible, reusable application framework that can support the rapid development of multiple systems tailored to distinct needs, but powered by a common underlying repository. Recognizing this common need, Stanford University, the University of Hull and the University of Virginia are collaborating on “Project Hydra”, a three-year effort to create an application and middleware framework that, in combination with an underlying Fedora repository, will create a reusable environment for running multifunction, multipurpose repository-powered solutions. This presentation will provide demonstrations of the work done to date, including of the prototype ETD application, as well as the set of content models and disseminators that the project has defined so far. The presentation will also present links to the project’s publicly accessible documentation and open source code, as well as solicit the constructive input from community members who may be interested in the project or its outcomes.
Keyword:
Open Repositories 2009, Collaboration, Repository, and Hydra
Samvera publicity leaflet for use at conferences. Version 1 dated October 2018 in A4 and US Letter formats. This version of the leaflet has been superseded.
Samvera publicity leaflet for use at conferences. Version 2 dated April 2019 in A4 and US Letter formats. This version of the leaflet has been superseded.
Using Git and GitHub for managing metadata (no new data models, we promise)This session is proposed as a two-part workshop, A workshop given at Samvera Connect 2017 described thus, and The first will cover a modified version of the ‘Version Control with Git’ Software Carpentry lesson, tailored for a non-developer audience, with more focus on metadata. This is typically taught as a half-day (3 hour) workshop.The second part will focus on the use of Git and GitHub in the context of the metadata workflow. We will present examples and strategies, taken from recent work by UC Santa Barbara and UC San Diego, of version control, pull requests, and automated hooks and integrations as they relate to moving metadata through a workflow and into our repositories. In addition to these demonstrations, we hope to spend a good percentage of the time available in discussion with other interested institutions and how we might leverage our collective experience to make getting our metadata into our repositories easier, more consistent, and maybe even more fun!
Keyword:
Workshop, Metadata, Connect 2017, and Samvera
Subject:
Samvera Community
Creator:
Rissmeyer, Chrissy, Critchlow, Matthew, and Dunn, Alex
Contributor:
University of California San Diego Library and University of California Santa Barbara 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
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
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
however, all of Rail's most common UI elements and features will be retained. If time permits, we will also add Blacklight as a dependency for search and retrieval., How Valkyrie differs from ActiveRecord How to manage the differences between Valkyrie and Rails while retaining most of Rails' common features In this workshop, participants will learn how to build a simple Rails application using Valkyrie as a dependency. Data will be persisted with Valkyrie's data mapper pattern and not with ActiveRecord, and Slides from a workshop given at Samvera Connect 2019 and described thus
and we often need to make localized adjustment(s) to address either an underlying bug or to extend existing behavior. The code-base has places for configuration, but sometimes that might not be enough. Join me on a foray into how you can make the Ruby/Rails changes you need now and not make things (too much worse) for your future self and others. and The Samvera stack is deep
- Large ingestion of 4 gig tifs with derivates and preservation checks (10k works) in ~ 1 hour - 5k batch metadata updates ~5 minutes - Round trip spreadsheet update (5k records in 5 minutes) - Preservation dashboard / verification - Local authority creation and updates This presentation will discuss the process, what we learned, and how it relates to the Samvera community at large. and On St. Patrick's Day NU went live with our new digital collection repository and asset management tool prioritizing speed of ingestion and metadata updates. We reframed the problem by working with end-users to look closely at workflows and prioritize solutions rather than any specific technology. The resulting application ecosystem is extremely budget friendly and the architecture supports
electronic thesis and dissertation solution] are so new that few training resources are available. This document attempts to provide a resource for training staff in the technology skills necessary for implementing a digital repository. We list the technologies and the problem solving skills required to work effectively with each technology, along with a practical example of how each can be used in the creation and running of a repository., institutional repository, and This was the working document for a Hydra Curriculum circa 2010. Most of this content became part of the HydraCamp curriculum. Why a curriculum? In the effort to create digital repositories, libraries rarely have the luxury of hiring new staff who are both fluent in the necessary technology and cognizant of the particular concerns and responsibilities of libraries. The technology skills required for the implementation of a [digital library
Building and using an open source community-supported system to manage audiovisual materials for a digital archive/library has many advantages and challenges. Being able to dictate the features, have a system speak to specific needs, and have staff on hand that can change or fix problems is certainly appealing. Embarking on this effort with an established open community, such as Samvera, has the advantages of a robust community of developers and service vendors to turn to for help. Managing needed customisations to core code base, keeping track of updates and contributing to the community, however, is challenging. For WGBH, a public television station with a robust 60-year archive, most customisations are due to the use PBCore to structure the metadata of the audio-visual items. This paper focuses on WGBH’s efforts to build a system for its Media Library and Archives based on the Samvera digital repository framework and its Hyrax and Avalon Media System ‘products’. and Abstract
Samvera Connect 2020 was held on-line due to the COVID-19 pandemic. Some 340 people registered for the event. The linked video is a recording of the Day #4 events. The 'Related URL' below links to the start of this presentation in the YouTube recording. This is the full recording of the day's presentations lasting some 3 hours 23 minutes. Shorter recordings of the individual presentations are to be found elsewhere in this repository. Search 'Connect 2020 on-line' and use the facets to select just 'presentations'.
A recording of the opening session of Samvera Connect 2020. Labelled "Welcome and housekeeping" in the program, the session also included a memorial to the late Julie Allinson and a tribute to the Community's retiring Operations Adviser, Richard Green.
Keyword:
Community and Samvera
Subject:
Samvera Community
Creator:
Metz, Rosalyn
Contributor:
McBride, Brian, Awre, Christopher L, and Cramer, Tom
Samvera Connect 2020 was held on-line due to the COVID-19 pandemic. Some 340 people registered for the event. The linked video is a recording of the Day #5 events. The 'Related URL' below links to the start of this presentation in the YouTube recording. This is the full recording of the day's presentations lasting some 2 hours 51 minutes. Shorter recordings of the individual presentations are to be found elsewhere in this repository. Search 'Connect 2020 on-line' and use the facets to select just 'presentations'.
Between 2018 and 2019, Jisc funded an effort to refresh the SWORD repository deposit protocol, with modern repository use cases in mind, especially around data repositories. As a result we produced a draft specification, extensively reviewed by a large number of the repositories community, including those from the Samvera and Fedora communities. In 2019, NII provided funding to produce a reference implementation, and we have been working to prove that the specification is implementable and viable. That work concluded in July 2020 with the release of a client library and a server library in Python. Now the SWORDv3 team is looking outward to the rest of the repositories community, looking to engage them in development for their platforms, and to enable novel integrations. This presentation will introduce the spec for those that are not familiar, and describe the technical and community-building work that is ongoing, and call for engagement by the Samvera technical community in working with SWORDv3. The YouTube 'Related URL' below links to a recording of the presentation with closed captioning. and A presentation at Samvera Connect 2020 On-line described thus
Keyword:
Samvera, SWORD, Protocol, Connect 2020, and Metadata
Ubiquity repositories, which are based on Hyku, are designed to be highly scalable, highly reliable and quick to deploy in the cloud. In this presentation we will outline the technical architecture we have implemented, along with the challenges faced. These include scalability, security, cost-efficiency, performance, reliability, resilience, portability, delivery pipelines for code deployment, error reporting, testing and localization. We will also discuss our approach ensuring we remain on the most recent stable branch of the platform and contributing our code back to the community. The 'Related URL' below links to a video recording of the session. The video has closed captioning. and A presentation given at Samvera Connect 2020 On-line described thus
Keyword:
Collaboration, Architecture, Samvera, API, Customization, Connect 2020, Hyrax, and Hyku
Resource models. This will include information on the major changes that were made, descriptions of gotchas and workarounds, and a look at how close we are to being able to use any Valkyrie storage adapter. I’m hoping to include benchmark data as well to compare the various adapters. The 'Related URL' below links to a video recording of the session. The video has closed captioning., A presentation given at Samvera Connect 2020 On-line described thus, I will talk about the process I went through (and possibly am continuing to go through) to convert our Hyrax application’s ActiveFedora, and Base object models to Valkyrie
Keyword:
Hyrax, Workflow, Connect 2020, Samvera, and Valkyrie
The Emory Libraries implemented a second-generation preservation infrastructure in 2019 utilizing Hyrax 3, Fedora 4 and AWS, following a requirements gathering phase that included developing a preservation policy and a review of preservation community best practices. This presentation describes our solution design including locally-defined entities such as preservation workflows and events and FileSet expansion to support derivative files. We will also address implementation lessons learned while leveraging existing Samvera functionality and building new features to bridge gaps between existing framework components. The 'Related URL' below links to a video recording of the session. The video has closed captioning. and A presentation given at Samvera Connect 2020 On-line described thus
What is it like to dive headlong into Samvera from the outside? Notch8 assigned three interns to work on the Bulkrax community gem in 2020. They were not only new to Samvera, they were brand new developers in training. This talk will address the success of using interns on a Samvera project, the hurdles of taking on Samvera development, and the challenge of understanding the community concepts. You'll have an opportunity to ask these incredible interns about their experiences as they do a brief demo of their work. The 'Related URL' below links to a video recording of the session. The video has closed captioning. and A presentation given at Samvera Connect 2020 On-line described thus
Keyword:
Panel, Samvera, Import/export, User experience, Training, and Connect 2020
Subject:
Samvera Community
Creator:
Gabriel, Jeremy, Ramirez, Ruben, Rieger, April, Kochanski, Kevin, and Stroud, Kiah
Heavily inspired by QA, "Authoritex" is a Hex package for querying any controlled vocabulary or set of authority terms that NUL developed for use within our Elixir ecosystem. We'll go through quick overview of Authoritex and how it fits into our repository ingest application "Meadow" and our broader strategy for handling controlled terms and authorities. The 'Related URL' below links to a video recording of the session. The video has closed captioning. and A lightning talk (seven minute) presentation given at Samvera Connect 2020 On-line described thus
