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?
A presentation at Hydra Connect 2016 described thus and This case study will address the initial decisions and reasons for switching to Hydra, prototyping for launch of Hydra head, metadata cleanup and asset migration, final quality review, and lessons learned. An audio recording of the session is available for download below.
Fedora, the flexible, extensible, open source repository platform for managing, preserving, and providing access to digital content, is a key component of most Samvera implementations. Fedora 4.x, the latest version of Fedora, has been in production since 2015, and since then the real-world experience of the community’s use cases has clarified Fedora’s role in supporting preservation and access in the context of large collections and performance at scale. This understanding led to an effort to formally specify the Fedora application programming interface (API) that provides a stable layer of abstraction between clients and repository instances. In this way, alternate back-end implementations suited for specific user cases can all expose the same core services to repository clients. This initiative will allow the Fedora project to adapt to technological change more easily over time while insulating clients from changes in the underlying implementation. This presentation will provide an overview of the the API specification effort, including current status, motivations, and benefits, with a particular focus on the relevance to Samvera. A brief survey of alternate implementations will provide context for the different use cases that will be enabled by the specification. This will be of interest to current and future Fedora implementers looking for an update on the current status and technical roadmap of the project. A video recording of this session is available at the 'Related URL' below. and A presentation given at Samvera Connect 2018 described thus
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
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
Participants will leave with ideas and methods for how to receive, prioritize, and plan multiple concurrent Library IT projects by taking into consideration the complexity, cost, and impact This half-day hands-on workshop will introduce participants to Michigan’s “Front Door” request intake and cycle planning process. At Michigan, we have designed a cycle planning process to gather requests of all kinds, rate and review, and finally, assign resources as appropriate. The workshop is intended to be a simulation of the cycle planning process from intake to resource planning exercise. The participants will get a feel of how requests are rated and reviewed for cost, complexity, and impact. We will be sharing the tools and templates used at Michigan for reviewing the requests, planning the cycle, and assessing the works’ progress throughout the cycle. and Slides from a workshop given at Samvera Connect 2019 and described thus