Suggestions for Samvera Connect 2017 Program

Using Git and GitHub for managing metadata (no new data models, we promise)

This session is proposed as a two-part workshop:

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

Intro to Git(Hub) Workshop - Anyone new to Git/GitHub

Git/GitHub and Metadata - All (focus on metadata)

Fedora project and community update

• API specification
• Alternate implementations
• Semantic versioning
• Import/export

Extending Fedora: API-X and Import/Export

• Hands-on with new Fedora extensions and tools

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.

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.

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.

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.

How to Write Module-Based JavaScript with RequireJS and the AMD (Asynchronous Module Definition) Pattern

Tired of worrying about load order for your script includes? Tired of polluting the global namespace? Want to write more re-usable JavaScript code with discrete modules? Maybe RequireJS / the AMD pattern is right for you! This presentation will go through the construction of a simple RequireJS-based JavaScript app with a few modules. A general familiarity with JavaScript is recommended.

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.

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.

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.

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.

Moving to AWS (possibly also include alternatives to AWS? i.e. Google Cloud/Azure).

* Overview/ risks/ concerns (e.g. Moving to the cloud is scary)
* Planning a transition/ find something to move/ test so people don’t get too scared
* Developer Happiness (flexibility/ speed of deployment/ repeatability)
* Managerial happiness (cost transparency, benefit, efficiency)
* Exit strategy (or where to put stuff long term)

Documenting our Metadata Application Profiles (MAPS) Before Migration

As the Samvera Community prepares for migration, can we get a handle on the metadata we have and what we share with the community? Let's sit down together to document what we're saying about our objects, how we're expressing it and learn from others' ideas. Bring your weird and wild worst practices, build together toward better practices.

Session goals would be: to provide a place to sit down and do the work together, talk about similarities or differences, and provide some context for what we do or don't want our MAPS to look like as we migrate to a new system.

Samvera stack in production the DevOps way