Valkyrie is a new persistence layer for Samvera, designed to address performance and sustainability problems. It was developed through the existing Samvera Working Group process, showing that the current Samvera community governance structure can be used to tackle big problems. Valkyrie features pluggable persistence options, allowing Samvera applications to use not just the historical combination of Fedora and Solr, but also other options like Fedora or Solr by themselves, PostgreSQL, and local disk. Allowing Samvera applications to use different persistence options refocuses the Samvera community, shifting away from persistence in Fedora as the defining aspect of the community. Instead, the focus shifts to the shared tools built by the community. and A presentation at Samvera Virtual Connect 2018 described thus
Keyword:
Lightning talk, Virtual Connect 2018, Samvera, and Valkyrie
A proposal for a presentation given at the Open Repositories conference in 2015 held in Indianapolis described thus, One of the many successes of the Hydra community is the fundamental notion from which its name is derived—the concept of many interfaces (“heads”) over top of a single repository (the “body”). The recent release of Fedora 4, with its internal RDF-centric model, has spurred efforts for a community-wide model of collections and works, such that the heads can be sure that the body will behave as they expect it to. That model has been designed and vetted by the Hydra community, and its architecture and initial implementations will be presented in this paper. [Note, and the subject of this proposal has since become known as the 'Portland Common Data Model'.]
Keyword:
Community, Data model, Resource Description Framework (RDF), Hydra, Portland Common Data Model (PCDM), Open Repositories 2015, and Fedora
Subject:
Hydra Project
Creator:
Stroop, Jon, Sanderson, Rob, and Cowles, Esmé
Contributor:
University of California San Diego, Princeton University, and Stanford University
A presentation given at Samvera Connect 2020 On-line described thus and Princeton University Library’s digital projects and initiatives were seriously disrupted by COVID-19. Digitization of materials for projects and forthcoming exhibitions came to an unexpected halt at the same time as patrons and staff were separated from physical objects and library spaces. Necessity, however, provided an opportunity to reassess digital projects and how staff members interact with and contribute to our repository (Figgy). We focused on the creation of workflows and documentation for new contributors who would be working in the repository, helping them enhance existing digital objects with OCR, item level organization, structural metadata, page labeling, and IIIF display attributes. We describe how we were able to use Figgy and unexpectedly-available staff time to make more effective research tools and provide a better user experience for patrons and staff working with our digital collections. Such enhancements add immense value to our collections as well as to our applications, and the work can be done effectively by a wide range of staff from different departments with variable skill sets. The 'Related URL' below links to beginning of this presentation in the day's YouTube recording.
Keyword:
Metadata, Workflow, Connect 2020, Digitization, Samvera, Exhibits, and Vendors
Frost, Hannah, Taylor, Stephanie, Cowles, Esmé, Allinson, Julie, Steans, Ryan, Awre, Christopher L, Pendragon, Trey, Van Tuyl, Steve, Dunn, Jon, and Green, Richard A
Contributor:
Headley, Anna, Dunn, Jon, University of Utah, Weise, John, Tampakis, Nikitas, Bussey, Mark, IUPUI University Library, Lynn, Rachel, and University of London
Valkyrie is a new persistence layer for Samvera, supporting multiple backends for storing files and metadata. Currently supported backends include Fedora, PostgreSQL and Solr for metadata, and Fedora and local disk for files. Valkyrie provides an abstraction layer over file and metadata persistence, allowing an application to be configured to use different backends without code changes. This workshop will include, Description, A workshop given at Samvera Connect 2018 described thus, and An overview of Valkyrie's design, including why the Data Mapper pattern was used, and how Valkyrie addresses sustainability issues with ActiveFedora Status updates on current Valkyrie development, including applications built using Valkyrie, and efforts to use Valkyrie in Hyrax Hands-on exercises to give attendees first-hand experience working with Valkyrie and demonstrate how concepts from Samvera applications work with Valkyrie
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
A brief update on the current state of Fedora 4, followed by a high-level feature discussion for managers and a hands-on test drive for developers. and A workshop given at Hydra Connect #2 described thus
Keyword:
Fedora, Connect #2 (Fall 2014), Hydra, and Workshop
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
Keyword:
Fedora, Connect 2016, Hydra, Import/export, and Lightning talk
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
Keyword:
Connect 2016, Workshop, Portland Common Data Model (PCDM), and Hydra