The recommendations of the Contribution Model Working Group were formally adopted by the Samvera Partners in early 2020. This document sets out the requirements for Partners which will be mandatory from spring 2022.
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
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.
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.
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
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.
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
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
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
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
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
Slides from a workshop at Samvera Connect 2019 advertized under the title "Using The Latest Rails Features in Hyrax" and described thus and We'll introduce Rails 6 features and discuss how they might integrate in to Samvera applications. *File uploads with S3 *Action Mailbox *Webpacker (default in Rails 6) *ActionText Another day, another major Rails version. What's been happening in the larger Rails community and how does it affect Samvera development?
Update on recent and upcoming Hyrax releases, progress made by the working group, and the current state of the roadmap. and A presentation at Samvera Connect 2019 described thus
This presentation highlights the tools and documentation created by the Bridge2Hyku team during the 2-year IMLS leadership grant. From the desktop application, CDMBridge, which exports out of contentDM to the import gem, HyBridge, that will be available as a feature within a future release of Hyku. We will also share our project partner migration stories and discuss the knowledge we’ve gleaned through leading 3 migration workshops and spending an inordinate amount of time thinking about migration best practices. and A presentation at Samvera Connect 2019 described thus
Using agile for more accurate proposals - Aaron Collier New Tools for NU, A combined slide pack containing the lightning talks presented at Samvera Connect 2019. Deploying a custom Hyrax on Azure with Terraform and Kubernetes from a standing start - Julie Allinson Controlled Vocabulary Options in Hyrax - Julie Hardesty Scholarsphere is Dead, Long Live Scholarsphere! - Adam Wead Work Estimation Records, and Elixir, Broadway, Phoenix, and GraphQL - Michael B Klein Hyku Open Source Institutional Repository Development partnership awarded $1M Arcadia grant to improve open scholarship infrastructure - Brian Hole Showcasing & Connecting Women in Technology - Robin Ruggaber Iterating on a Hiring Process - Jeremy Friesen
00., The Politics of Memory in a St. Louis Town House (University of Massachusetts Press, 2019), but also recent political events in St. Louis, probing the deeper motives and implications of heritage preservation. The 'related URL' shown is a video recording of the conference's morning proceedings. The keynote address starts at time index 25, A presentation at Samvera Connect 2019 described thus, and Historian Pierre Nora has argued that we are living in an archival age––one in which we seek nothing less than “complete conservation of the present” and “total preservation of the past.” The advent of digital media has aided this project, but also exposed its futility, and in turn compounded our archival obsession, which Nora reminds us is rooted in anxiety about the meaning of the present, a sense of alienation from our collective past, and broader fears of cultural––or human––annihilation. In “Sites of Memory, Acts of Erasure,” Heidi Aronson Kolk will explore the unusual potency of the well-preserved material archive, while challenging us to consider its dark twin––the site of erasure, forgetting and annihilation. Her presentation will engage subjects introduced in her book, Taking Possession
A presentation at Samvera Connect 2019 described thus and Although it feels like we just migrated from CONTENTdm to Hydra/Fedora 3, it's time to adjust course back to Hyrax! Oregon Digital's Metadata Team will talk about strategies and challenges with metadata preparation, remediation before migration begins and mapping updates. The Migration Team will talk about the gem we're building, hyrax-migrator, to allow us to migrate over 465,000 assets (files and metadata). We’ll cover the design and implementation of the gem which supports migrating assets both locally (for dev and testing) and remotely (for production, on AWS S3), and share our progress with a batch of about 1000 ‘seed data’ assets, as well as our goals for scaling up in the coming months.
A recording of a panel presentation at Samvera Connect 2018 described thus and In this panel we will briefly discuss the current landscape of needs and reasons for users to consider moving from an established repository, and the challenges facing users of a variety of platforms, both cultural and technological. We will also consider work currently underway such as "Bridge to Hyku", a grant-sponsored project empowering Content DM users to migrate, successes in DSpace-to-Samvera migration and what's on the horizon for BePress. In discussing these challenges, we hope to present the Samvera Community with an opportunity to grow the portfolio of users and create the potential for standards and teams to assist those who wish to be a part of the Samvera Community. A video recording of this session is available at the 'Related URL' below.
A presentation at Samvera Connect 2019 described thus and Northwestern University Libraries (NUL) became a Hydra Partner in early 2012. Over the past 7+ years, we produced bespoke applications locally using the Hydra/Samvera codebase, worked on many iterations of a stand-alone grant-funded Hydra/Samvera product with another Partner institution, contributed effort to the development of Hyrax, implemented Hyrax as a component in a larger repository ecosystem, and shifted our repository services to the cloud. As we have evolved, we have gone through many changes in our local culture, in our user needs, in our codebase, and with our talent. One of the organizational culture changes is the shift of NUL to a learning organization. This change has made us more risk tolerant than in the past. It has allowed NUL to solve its local need of large-scale fast ingestion and description using novel approaches and technologies (Elixir, AWS services, Lambdas, etc). This presentation will discuss how these organizational changes and approaches to technology projects made us privilege the value of Samvera as a community of shared values and ideas over its shared codebase.
This will be a half-day, hands-on workshop covering data modeling primarily in RDF. We hope to bring a diverse group of Hydra community members together to learn, discuss, and build out examples that will inform Hydra community best practices for data modeling. This modeling work will be taught in the context of helping Hydra and Fedora development, metadata, and interoperability efforts. We will discuss how model uses a number of standards, and demo the different ways to represent models. We will compare and contract data modeling with metadata standards/profiles. We will walk through modeling efforts around PCDM and its place in our work and community - this workshop will not focus on PCDM alone (this is not a PCDM or RDF workshop). We want this workshop to bring together, develop and engage a larger corps of data modelers in the Hydrasphere. and A workshop delivered at Hydra Connect 2016, described thus
A recording of a presentation at Samvera Connect 2018 described thus, prototyping a core component of our new architecture to be horizontally scalable, designing a new architecture for our digital library with a wide ranging set of requirements and users, Stanford University Library has a robust digital library system called the Stanford Digital Repository. This repository holds a little under 500 TB of materials in preservation, and a little less than that for online access, from our cultural heritage digitization efforts and institutional repository outputs. These materials are managed across 90+ codebases serving a variety of functions from self-deposit web applications, to a nearly 10 year old parallel processing framework, to a digital repository assets publication mechanism leading into our Blacklight, Spotlight, and Geoblacklight applications - among other services and needs. At the core of this system is a Fedora 3 store. With Fedora 3 now end-of-lifed, and our system suffering from limited to no horizontal scalability options, we’re revisiting our system and architecture. We are writing it from the start with a goal to have data-forward, distributed microservices and some event-driven processing components. TACO, our new core management API, is the heart of this new architecture, and is currently being developed as a prototype. This talk will walk through the process of analysing our current system via a dataflows analysis, then planning how to create ‘seams’ in our current system to migrate towards our new system in an evolutionary fashion instead of a turn-key migration. A video recording of this session is available at the 'Related URL' below., and seeing where community technologies like Hyrax, Blacklight, and IIIF will connect
Does writing or reviewing code make you stressed, fatigued, or anxious? In this session Glen will share the mindful approach he takes to writing and reviewing code at the University of Cincinnati Libraries. Mindfulness has been used to reduce stress and increase the quality of people's lives and it can be used during software development as well. Learn how being present in the moment, focusing, and empathizing with users can lead to a better product and actually be therapeutic for the developer. and A presentation at Samvera Connect 2019 described thus
A workshop delivered at Hydra Connect 2016, described thus, increasing familiarity with PCDM, contributing back to PCDM from the activities of the participants, and increasing participants’ familiarly and comfort with data models more broadly., and The Portland Common Data Model (PCDM) is a flexible shared, linked data-based domain model for representing complex digital objects. This workshop will review PCDM, its history, technical overview, recent developments, and Hydra-specific implementation considerations. The workshop will also include an interactive modeling session where users will employ use cases from their repositories (or provided samples) to model in PCDM. The goals of the workshop include
A recording of a presentation at Samvera Connect 2018 described thus and Panelists from Duke University, Indiana University, and the University of Michigan will share their experience of developing a Research Data Repository based on Hyrax 2. They will discuss what worked out-of-the-box, what was customized, future directions, lessons learned to date from working together, and contributing back to the Hyrax community. Institutions’ efforts include data migration, accessibility testing, branding, community outreach, curation workflows, and overcoming the challenges associated with large datasets. A video recording of this session is available at the 'Related URL' below.
//wiki.duraspace.org/display/hydra/Applied+Linked+Data+Working+Group, https, A workshop delivered at Hydra Connect 2016, described thus, and This workshop is all about techniques to use linked data within your Hydra based application. For example, autocomplete fields from a controlled vocabulary are nice... but what if you wanted to give more context to what users are selecting via things like alternative labels and broader / narrower concepts? How do you cache triples locally? How do do you publish your own controlled vocabulary for others to use? And what is the best way to make your RDF data harvestable by others? This workshop is based on work done by the Applied Linked Data working group
A panel presentation at Samvera Connect 2019 described thus and As a Hyrax application developer, setting up a development environment is well documented within the community. Simply go through the Github README, install the prerequisites, and the development environment is practically ready to roll. Setting up a Hyrax production environment? Now, that’s a different story. Once an application is ready for production, there are a number of important decision points and configuration options that are less well documented within the community. This session will highlight some of those configuration options and include a discussion about how we can move forward, as a community, in communicating, sharing, and documenting how the characteristics of a repository should be considered before setting up a Hyrax production environment.
At Stanford libraries we've run hundreds of virtual machines to support dozens of applications. We've found the cost and complexity of patching and maintaining these machines to be untenable. We believe that a serverless infrastructure is our future and so we are using AWS Fargate (Elastic Container Services) and Lambda architecture to reduce our maintenance burden. We will explain the AWS offerings in this space, explain how we can set up a simple distributed system, and point out pitfalls that we've experienced. and A video recording of a presentation at Samvera Connect 2018 described thus
For the past few years I've been distributing a survey to gauge usage of Sufia (and, this year, CurationConcerns) and to get a sense of what direction the community wants the components to go in. I'd like to report back to you all on what the latest data says, and share a rough roadmap for 2016-2017. A video of this session is available at the 'Related URL' below. and A lightning talk presentation at Hydra Connect 2016, described thus
This presentation will explore the development of Hyku for Open Educational Resources — openly licensed educational materials such as textbooks, quizzes, classroom activities, etc. — while capitalizing on Hyku's multi-tenancy and sharing of infrastructure across two large groups of libraries. The PALCI and PALNI consortia (representing libraries in Pennsylvania, New York, New Jersey, West Virginia and Indiana) have just received a two year IMLS National Leadership Grant to develop Hyku into a multi-tenant, consortia-based service capable of handling OER in addition to other institutional repository resource types. In addition to leveraging collective expertise through consortia, two new work types are being developed for OER and electronic thesis and dissertations. This presentation will focus on the first work type being developed for OER , describing the features and uses of these resources, how the new work type model is being developed, and examine why Hyku and the Open Source Software community is a great home for this project. and A presentation at Samvera Connect 2019 described thus
Update on the recent work to implement standards-based import/export functionality for Fedora 4, working on importing and exporting Bags for migrating between Fedora repositories, and backing up to and restoring from preservation services such as APTrust, Archivematica, etc. and A lightning talk presentation at Hydra Connect 2016, described thus
A presentation given at Samvera Connect 2018 described thus, Despite widespread interest in Hyrax, Samvera’s new flagship repository solution, there is a dearth of documentation about how to run a production instance. We’ll cover the lessons we’ve learned from a year of building and hosting Hyrax, including our new project checklist, logging and monitoring practices, and data migration paths. DCE has been hosting a Hyrax based ETD repository for Emory University for 12 months. We've made a lot of discoveries and improvements since we launched. We'll be sharing our learnings and best practices for running Samvera Based repositories including, and * Infrastructure as code (esp. ansible for configuration management) * Monitoring using open-source and commercial tools (nagios, ok computer, splunk, pingdom, honeybadger) * Maintenance, Upgrades, and Testing A video recording of this session is available at the 'Related URL' below.
This session will provide an overview of the strategies and tactics being used at Emory University Libraries for planning and management of Samvera based initiatives. An overview of our approaches to project, product, and system management will be presented with a focus on resource strategy related to people, teams and roles. An emphasis on new hires and leadership roles will be presented as well as the challenges faced when implementing new technologies, providing support for legacy systems and managing teams. We intend for the session to be an opportunity for attendees to also share their experiences and challenges in the areas of leadership and management. and A presentation at Samvera Connect 2019 described thus
A lightning talk presentation at Hydra Connect 2016, described thus and Hydra applications can interact with a number of backing services (Fedora, Solr, Redis, job runners, etc). Using Docker to run these services locally can potentially simplify the development environment and reduce on-boarding time. A video of this session is available at the 'Related URL' below.
Minimum Viable Product-Suite and Minimum Viable Preservation features in a new Samvera platform migration., A presentation given at Samvera Connect 2018 described thus, and The Emory Digital Library Program team will share a retrospective of their Discovery and Technical Design process for determining MVP2
As most Hyrax adopters know, Hyrax offers a basic set of metadata properties that it assigns to each new work type. Most adopters will extend that set, to a greater or lesser degree, adding new properties, defining vocabularies and terms lists, and setting other constraints and requirements. Adding new metadata is a complicated process in Hyrax, and there are various ways in which developers have worked to streamline things (eg. scooby snacks, dog biscuits and archetypes). But before we even get to customising a Hyrax application, metadata librarians and developers must collaborate on specifying the metadata requirements. With no community machine-readable approach to defining those requirements, misunderstandings are common, and can be costly. With a machine-readable specification for metadata, metadata librarians could accurately specify requirements and developers could validate and codify those into applications. That’s where the Machine-readable Metadata Modeling Specification (M3) steps in. The specification is the output of the M3 Working Group and is nearing its version 1.0 release. This presentation will provide a walkthrough of the specification, show how to construct and validate a new M3 profile, and illustrate the benefits of M3 for both metadata specialists and developers. and A presentation at Samvera Connect 2019 described thus