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 talk will present a project at the University of Hull, working with CoSector and Cottage Labs, to create a permanent digital archive of the Hull City of Culture. Hull was awarded UK City of Culture for 2017 and, throughout the year, generated a wealth of digital material documenting the events and activities celebrating the city, as well as archives from the organization and evaluation of the event. The University of Hull, already an active user of Samvera technologies, wanted to build on the work done for the Jisc ‘Filling the Digital Preservation Gap’ by using Archivematica for the digital archives preservation pipeline and Hyrax as a showcase for the City of Culture. We will also talk about how the project was originally conceived, and how that has changed through active and engaged project meetings to reflect ongoing service needs for the management of digital archives, of which the City of Culture archive forms a part. Integration with CALM (archives management solution ) and the existing Hull History Centre Blacklight catalogue (developed by DCE) is being explored to create a fully integrated digital archiving solution. A video recording of this session is available at the 'Related URL' below. and A presentation given at Samvera Connect 2018 described thus
Keyword:
Hyrax, Preservation, Connect 2018, and Samvera
Subject:
Samvera Community
Creator:
Awre, Christopher L and Allinson, Julie
Contributor:
University of Utah, University of Hull, and CoSector, University of London
This presentation will provide an overview of the needs of the American Archive of Public Broadcasting, challenges and successes of building a custom application based on Hyrax and Avalon, features developed both within the application and as re-usable components, and how to represent PBCore metadata in a Samvera application. The American Archive of Public Broadcasting (AAPB), founded by the Corporation for Public Broadcasting, is currently a joint venture between WGBH and the Library of Congress. It is a collection of digital audiovisual content created for public media distribution, requiring an adaptable technical infrastructure that can support close collaborations with organizations of varying technical and institutional capacity. The critical component for this is the Archival Management System (AMS), the entry point through which contributors’ descriptive, technical, and preservation metadata is ingested into the AAPB collection and where all metadata is managed and improved through cataloging by AAPB staff and interns. With plans of moving to a new system, hopefully one with a more active opensource community around it, the AAPB determined that the best path forward was to build the tool on Avalon and within the Samvera community. In 2017, the AAPB was awarded a grant by the Mellon Foundation to do just this, and the AMS 2.0 development project began in December of 2017 and is slated for completion by the beginning of 2019. AAPB is working with AVP and Indiana University as part of the development team. At the same time the project was starting, Avalon made the decision to move to Hyrax for Avalon 7. That changed the starting point and scope for the AMS 2.0 development plan, which is now to build a custom application on a Hyrax base creating features in tandem with the Avalon team. A video recording of this session is available at the 'Related URL' below. and A presentation given at Samvera Connect 2018 described thus
Keyword:
Avalon, Connect 2018, Samvera, and Hyrax
Subject:
Samvera Community
Creator:
Myers, Andrew, Roosa, Sadie, Davis Kaufman, Casey, and Corum, Jason
Contributor:
WGBH Media Library and Archives and University of Utah
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
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.
Keyword:
Hyrax, Production, Samvera, Development, and Connect 2019
Subject:
Samvera Community
Creator:
Corum, Jason, Myers, Andrew, Neels, Henry, and Roosa, Sadie
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