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
The Boston Public Library has long been a Fedora 3 Commons system and we are heavily invested in that backend. After waiting to see how Fedora 4 Commons develops and with some recent internal debate, our "next gen" repository solution is going in a different direction. This will be a (perhaps) controversial talk as to why and how we came to this conclusion. A video of this session is available at the 'Related URL' below. and A lightning talk presentation at Hydra Connect 2016, described thus
A presentation given at Samvera Connect 2018 described thus, An overview of modern front-end UI component architecture and patterns. Will showcase case studies in development and implementation decisions in Avalon Media System (platform, React/Redux application built on top of Hyrax in AWS). Will make a case for why UI component architecture is important in community-driven, open-source development, how it can directly benefit the Samvera community moving forward. A video recording of this session is available at the 'Related URL' below., and Hyrax/Webpacker/React) and Northwestern University's Digital Collections application (platform
Quick overview of the implementation of Handle System (https, // www.handle.net) support into a Curation Concerns / Sufia application. A video of this session is available at the 'Related URL' below., and A lightning talk presentation at Hydra Connect 2016, described thus
Since 2014, partners from Indiana University Bloomington (IUB) and Indiana University Purdue University Indianapolis (IUPUI) Libraries have been collaboratively developing new Samvera-based software to manage and deliver page turning digital objects. In 2018, conversations with Enterprise Scholarly Systems (ESS), a partnership between IUB Libraries, IUPUI Libraries, and University Information Technology Services (UITS), expanded our project's scope. This presentation will highlight our development efforts, now known as the ESS Images project or ESSI. In the past year, the ESSI team has developed numerous improvements to the Hyrax digital repository software. These improvements include the ability to order, structure, and label pages within an item, replicating features available in the Pages Online service launched in 2017. Additionally, the project has implemented optical character recognition search in a community-accepted way, building upon components of the IMLS-funded Samvera Newspaper Works application. We will also discuss upcoming improvements for our existing image collections. In these collections, images often have wildly different metadata profiles from each other. Our recent work has aimed to incorporate a model for flexible metadata developed by the Samvera Machine-readable Metadata Modeling Specification (M3) Working Group within Hyrax. We will be discussing the output of this work as well. and A presentation at Samvera Connect 2019 described thus
When the Library of Congress was recently attacked, we noticed an important part of our workflow ground to a halt - XML schema validation had failed. We've developed a gem that allows for schema mirroring and offline validation/rspec testing, which we hope might be of use to others. A video of this session is available at the 'Related URL' below. and A lightning talk presentation at Hydra Connect 2016, described thus
The One-to-Many (OtM) Grant, funded by the Mellon Foundation, is working to provide a model for how local repositories, like Hyrax, interact with Distributed Digital Preservation (DDP) services (i.e., Chronopolis, AP Trust, LOCKSS, etc). This presentation will offer an overview of the grant's goals, an update on the specifications under development, and a call to action for implementation. and A presentation at Samvera Connect 2019 described thus
Over the past two years, Northwestern University Libraries has moved its repository infrastructure and applications to Amazon Web Services. Our initial solution, presented at Samvera Connect 2017, involved AWS CloudFormation, several different deployment platforms, and a lot of manual intervention. In our second phase, we have adopted a fully automated build/configure/deploy system to stand up Fedora, Solr, PostgreSQL, Redis, a Cantaloupe IIIF server, an Avalon Media System instance, a secure CloudFront streaming media distribution, and two Hyrax applications using Terraform, Docker, AWS Elastic Beanstalk, and a whole bunch of homegrown tools and hacks. This presentation will provide an overview of our current system, and hopefully jumpstart some discussions of how these tools can be adopted, standardized, and reused among other members of the Samvera community. A video recording of this session is available at the 'Related URL' below., A presentation given at Samvera Connect 2018, originally titled "My Life in Ops, and Docker, Terraform, AWS, and Learning As We Go", described thus
A brief walk through on concerns related to monitoring and alerting a production Hydra stack. An recording of this session is available at the 'Related URL' below. Unfortunately, although it is technically a video, the slides do not show on the recording. and A lightning talk presentation at Hydra Connect 2016, described thus
Many institutions need to import, export, and migrate data in bulk, and the ability to do this easily should be a fundamental service offered by any repository. For Hyrax, there are a range of home-grown and community solutions focused on specific use cases but there are no easily reusable community solutions. That’s starting to change and we’d like to talk about our specific experience building ‘Bulkrax’ and ‘Zizia’, two bulk import-export engines for Hyrax. This talk will outline the current status of our two projects, covering the design and approach taken, alongside features such as OAI-PMH import, and CSV import and export. We'll also talk about where Bulkrax and Zizia are going in the near future. We’ll show how each can be adopted, configured, and extended to meet local use cases, and how these projects are meeting the requirements set out by 2018’s ‘Batch Import-Export Working Group’. We’ll also discuss how best to move forward as a community around this issue, This will mean developing not only software but also shared community practice for managing the flow of bulk metadata from legacy systems and digitization projects into Samvera repositories., and A presentation at Samvera Connect 2019 described thus
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
//github.com/upenn-libraries/guardian) * A report on the reusability of these components to quickly develop Ruby-based integrations with Amazon Glacier in other applications * Challenges faced while integrating asynchronous storage with our Samvera repository * Considerations for developing a disaster recovery plan dealing with large-scale data loss and recovery A video recording of this session is available at the 'Related URL' below., A presentation given at Samvera Connect 2018 described thus, * Fundamental concepts of managing repository objects as Glacier archives * Best practices followed at Penn Libraries for efficient, affordable transfer and retrieval interactions with Glacier * A dive into the stronghold gem, developed at Penn Libraries, which provides a simple interface for interacting with Glacier (https, //github.com/upenn-libraries/stronghold) * Demonstration of Penn's workflow for running synchronous transfer of objects to Glacier using guardian, a set of Ruby scripts serving as the orchestration layer (https, and This session details work done at the University of Pennsylvania to incorporate Amazon Glacier as a third-copy backup storage location for objects in our repository using a series of components that were developed as generalized tools that can be integrated into any Ruby-based application to manage object copies in Glacier. This session will cover
Wings, the project to move Hyrax to Valkyrie, has been underway for most of this year. What does this transition mean for your existing Hyrax application? How should you account for it in your future planning? How can you take advantage of this work today? This presentation will address these questions for a general community audience. and A presentation at Samvera Connect 2019 described thus
This presentation aims to explore the possible integration of Samvera digital object repositories with additional web services using message brokers. There have been cases in which it is necessary to synchronize content updates between repositories and additional library systems such as library catalogs or digital exhibit publishing software. Within this context, developers may benefit by exploring architectural pattern in which a dedicated message broker receives asynchronous notifications of repository content updates, new ingestions, and deletions. In response to having received these messages, the broker may then broadcast these events to other listening library systems. The library systems then may reindex or update their own content accordingly. A conceptual overview of this architectural pattern shall be provided, followed by an overview of an implementation local to the systems within the Princeton University Library (synchronizing content between implementations of Valkyrie and Spotlight using RabbitMQ). The outcome of this presentation would be to identify other Samvera adopters who may also be utilizing message brokers, with the ultimate aim of determining whether or not this approach would be beneficial to a larger number of community members. A video recording of this session is available at the 'Related URL' below. and A presentation given at Samvera Connect 2018 described thus