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
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
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
