A workshop given at Samvera Connect 2017 described thus, Managing Samvera-based Projects and Services, and This hands-on workshop will cover tools and techniques to help managers decide whether to spin up a new Samvera repository, manage the process of building that repository, and maintain the repository once it is in production. We’ll cover the project lifecycle for migrating to Hyrax, defining roles within your team, keeping in sync with community development efforts, managing documentation, and managing user expectations and needs.
A presentation given at Connect 2017 described thus and How can presentation layers in Hyrax applications be extended to fit local needs? This session will showcase two front-end implementations of Hyrax for institutional repositories and discuss design decisions we made for specific use-cases.
A lightning talk at Samvera Virtual Connect 2018 described thus and IIIF Presentation 3.0 pushes beyond only images to support time-based media. This presentation will explain the new possibilities and how the Avalon team is helping to bring those to Hyrax.
A lightning talk at Samvera Virtual Connect 2018 described thus and Avalon Media System is working towards a release to integrate with Hyrax in support of time-based media formats. This includes creating a Work type to support the needs of audio and video formats and provide an upgrade path for those who have been using Avalon in it’s previous releases as a standalone Samvera product. Join us for a look at the new Audiovisual Work type, specifically how we’re transitioning descriptive metadata from MODS XML to RDF. A video recording of this session is available at the 'Related URL' below.
Northwestern University Libraries is currently running Samvera applications in production. Three of these are developed, maintained, and managed by the Repository & Digital Curation workgroup, * Arch, an Institutional Repository, based on Hyrax 2.4.1 * AVR, Northwestern's audiovisual repository, based on Avalon 6.3 * DONUT, the staff-facing ingest interface for the digital object repository, based on Hyrax 2.4.1 In developing and deploying these applications, we have encountered (and mostly overcome) numerous stumbling blocks relating to performance, scalability, customization, and assumptions about the deployment environment and infrastructure on which the apps will run. While we have found it possible to shoehorn the Samvera stack (as it exists today) into our Amazon Web Services cloud-based deployment environment, we have also started to investigate the rewards and compromises involved in taking a cloud-first approach to our next generation of tools. We have identified several basic tenets for this approach so far, * If AWS offers a native Software-as-a-Service (SaaS) solution for a particular problem, use it (e.g., choose ElasticSearch/Cloud Search over Solr) * Avoid virtual server instances that run 24x7 waiting for requests/work * Do not assume there is a local filesystem to work with * Optimize startup time so that units of work can be spawned and killed as needed * Constantly assess and reassess every unit of work for scalability, repeatability, and idempotence * Keep data portable and code adaptable, but don't over-stress about vendor lock-in In this presentation, members of the Repository Development & Administration Team will present on lessons learned from 7 years of working with Samvera, Avalon, and Hyrax, what the future holds for our next round of in-house development, and the opportunities & compromises our cloud-first approach creates regarding our use of and contributions to the larger Samvera community., and A presentation at Samvera Virtual Connect 2019 described thus
A lightning talk at Samvera Virtual Connect 2019 described thus and Avalon Media System is upgrading it's UI component for handling structural metadata editing for an audio or visual work. The user can select and organize timespans in an AV work by manually typing bounding times and titles, or by interacting with a visual representation of the waveform. Technologies used are Peak.js and ReactJS.