A presentation given at Connect 2017 described thus and 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.
Keyword:
Hyrax, Connect 2017, Case study, Samvera, and Sufia
Flexible approaches to grouping things in the repository" and described thus, An introduction to the Hyrax 2.1 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., and A presentation given at Connect 2017 advertiosed under the title "Collections Extensions and Admin Sets
Keyword:
Hyrax, Connect 2017, Samvera, and Collection management
Subject:
Samvera Community
Creator:
Rayle, E Lynette
Contributor:
Cornell University and Collection Extensions Working Groups
A presentation given at Connect 2017 described thus and 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.
Keyword:
Hyrax, Connect 2017, and Samvera
Subject:
Samvera Community
Creator:
Hardesty, Juliet L and Allinson, Julie
Contributor:
CoSector, University of London and Indiana University
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.
Keyword:
Hyrax, Connect 2017, Samvera, and Customization
Subject:
Samvera Community
Creator:
Diaz, Chris, Jaffer, Nabeela, and Arling, Adam
Contributor:
University of Michigan and Northwestern University
A presentation given at Connect 2017 described thus and With so many Samvera metadataists managing similar objects and collections, can we get a handle on the metadata we have and what we share with the community? This session will introduce the idea behind the Documentation Project from the Samvera Metadata Interest Group and will consider what we're saying about our objects, how we're expressing it, and how best to move this work forward to provide suitable context for what we do or don't want our MAPS to look like as we document our work within Samvera.
Keyword:
Interest and Working Groups, Metadata, and Connect 2017
A presentation given at Connect 2017 described thus and 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.
A presentation given at Connect 2017 described thus, it’s not fun to have an ingest fail overnight and spend the morning tracking down why. Programmatically testing and validating digital object metadata prior to ingest helps us avoid these failures. The metadata itself is managed by Git and stored in GitHub, Several years ago UCSB incorporated Git/GitHub and JIRA into our metadata management and batch ingest workflows. Since then we’ve looked at repurposing other development tools to provide lightweight and automated solutions to problems we often face. One is that we rely primarily on batch ingests when adding content to our Samvera repository. As a result it’s especially important for the metadata to be error-free, and this allows us to run automated checks against any changes using Jenkins and some custom libraries we’ve written for validating CSV and MODS metadata. In this session, we will provide an overall of our current ingest preparation workflow and the tools we are using, and will discuss some of the benefits that have come out of this collaborative effort.
Keyword:
Metadata, Connect 2017, Samvera, and Import/export
A presentation given at Connect 2017 described thus, Michigan's Research Data Repository has been in production since Feb 2016. Presentation on experiences and challenges of transitioning from Sufia to Hyrax, and adding new features and running the service over the past year.
Keyword:
Hyrax, Connect 2017, Research data management, Repository, and Samvera
A presentation given at Connect 2017 described thus and Over the past 5 years ScholarSphere has been released 100 times. We will look back at those 100 releases to categorize the releases. I will then share lessons that I have learned through the process of releasing ScholarSphere.