|Introduction to RSpec||Devs||Workshop (half-day)|
Using Git and GitHub for managing metadata (no new data models, we promise)
This session is proposed as a two-part workshop:
Intro to Git(Hub) Workshop - Anyone new to Git/GitHub
Git/GitHub and Metadata - All (focus on metadata)
|Workshop (two half-day)|
|Upcoming changes in the architecture of Samvera.||Devs||Presentation|
|Fedora 4 performance: current status and future works||All||Presentation|
|Metadata management and batch ingest automation with Git/GitHub, Jenkins, Ansible, and JIRA||Devs, Metadata||Presentation|
Fedora project and community update
Extending Fedora: API-X and Import/Export
|So how's your migration going? A Panel Discussion or Breakout Session about migrating apps/content to Hyrax/Fedora 4||All||Panel (if others in addition to IU are interested in presenting) or Breakout|
Managing Enterprise Samvera Infrastructure: From Chef-Solo to Chef-Server
|Devs, DevOps, Ops||Workshop (half-day)|
|Lessons Learned From 100 Releases||Dev||Presentation|
|Hydra-in-a-Box - Final Project Update||All||Presentation|
Community models and authorities for Hyrax applications
Presentation on a gem for Hyrax models and authorities, which provides a central place for creating models for different types of works. Each new model draws on a central pot of properties to declare the set of properties needed to fully describe the particular work. The gem already exists and has sample models for journal article, thesis and more. In this presentation we will work through the process of defining a new model and then using that model in a Hyrax application. The idea behind the gem is to make it easier for developers to deploy new models, and provide a place for metadata folks to jointly define re-usable models.
Institution-specific Front-end Implementations of Hyrax
Overview of Hyrax implementations at different institutions showcasing how presentation layers can be extended to fit local needs and use cases.
|Repo Managers, UX, Devs||Presentation|
Dive into Valkyrie
Workshop going over the interface, configuration, patterns, and interaction points for using Valkyrie, a library to enable persisting metadata and files into a variety of different backends with a common interface.
Trey Pendragon, others?
Hyrax for Research Data
Deep Blue Data - Michigan's Research Data Repository has been in production since Feb 2016. Presentation on experiences and challenges of transitioning from Sufia to Hyrax; adding new features and running the service over the past year.
|So you want to migrate from DSpace/CONTENTdm/Digital Commons/Other to Samvera? We've been there are are here to help guide you through your perilous journey!||Devs, Repo Managers||Panel|
Managing Samvera based Projects and Services
90 min workshop: tools and techniques for on-boarding, project management,service management and keeping in line with the community updates
Our Journey from Sufia 7 to Hyrax
The University of Cincinnati recently migrated our Scholar@UC application from Sufia 7.3 to Hyrax 1.0. We will discuss our process and the special circumstances we had to deal with.
|Devs, Managers||Presentation||University of Cincinnati developers|
|APIs, Sharing Work, Specifications and Alternative Data Stores: Continuing Several Talks from the 2016 Meeting||Devs, Managers||Panel/Presentation||A mash-up of Valkyrie, Cavendish, Solution Bundle product owners, and other discontents|
|Devs||Presentation / maybe workshop?||Eric O'Hanlon||Eric O'Hanlon|
Collections Extensions and Admin Sets: Flexible approaches to grouping things in the repository
An introduction to the Hyrax 2.0 Collections which include collections extensions, once known as Display Sets. This implementation adds the ability to define collection types with various settings to meet the many use cases for collections from user collections to exhibits. We'll also look at how these play nicely with Admin Sets.
|Devs, Repo Managers||Presentation + Break out if interest||Lynette Rayle||Lynette Rayle|
Lookup with Context to select metadata values from a controlled vocabulary
Want to move beyond a simple autocomplete field for controlled vocabularies? Want a more accurate selection process? We will look at a Hyrax demo app that uses questioning authority to search linked data authorities and extracts multiple predicate values from search results to provide additional context in a lookup table to help with the selection process from a controlled vocabulary. The presentation will include direct access to OCLC Fast, locally cached access to Library of Congress and GeoNames, as well as others.
|Devs, Metadata, UX||Presentation||Lynette Rayle||Lynette Rayle|
|Lessons Learned from the Collection Extensions development sprint||Devs||Presentation or Lightening Talk||Lynette Rayle|
|Hyrax for Scanned Resources. Connecting Hyrax to larger digitization workflows, including metadata and UX work for publishing from Hyrax into your larger digital collections/discovery interfaces||Devs, Metadata, UX||Panel/Presentation||Jenn Colt|
Performance Metrics with Hyrax and Valkyrie
Looking at how Hyrax and Valkyrie perform with large collections of works, upwards of 300K items. Comparisons will be made across a number of different factors including metadata-only resources, resources with metadata and binary data, storing file on disk versus Fedora, as well as using PCDM-based models and non-PCDM models.
|Developers and managers||Presentation or Lightning talk|
|Distributed Usability Research Team Retrospective (& Planning?)||Devs, UX, Repo managers||Panel|
As part of the Avalon Media System project, we're creating a MediaElement.js video/audio player which can consume a IIIF A/V manifest (based on the 3.0 Presentation Spec). The proof-of-concept application ingests any supplied IIIF manifest, and outputs structured time range navigation links (ie. clicking on different tracks of a CD; or annotated time ranges in a video clip) in addition to rendering and playing the source media (audio or video) file. This demo could be useful to any organization implementing and/or creating IIIF endpoint applications. More info at: http://iiif.io/
|Devs, Front-End Devs, Repo managers, A/V interested parties||Lightning talk||Adam Arling|
Developing a Staff-Only Samvera Application: Struggles and Successes
Princeton University Library has spent the last two years developing Plum as a staff-only ingest platform for books, manuscripts, geo-spatial data, and archived ephemera. This talk would go through a history of the design goals, the successes we've had, the problems we've run into, and a look into the future.