A presentation given at Samvera Connect 2019 described thus and This presentation will cover the initial work to move the University of Michigan’s Deep Blue Documents repository from DSpace to Hyrax on Samvera and also merge it with the U-M data repository, Deep Blue Data, which is already on Hyrax. Deep Blue contains more than 120,000 items and has been around on DSpace since 2006. The Deep Blue Data repository started in 2016. Presenters will discuss steps taken so far to migrate and merge the repositories, including creating a minimum viable product (MVP) list, testing migration, addressing challenges so far, collaborating between IT and service providers, and determining next steps.
Keyword:
Hyrax, Collaboration, Research data management, Repository, Samvera, and Connect 2019
A presentation given at Samvera Connect 2017 described thus and The Accessibility and Samvera presentation will cover an intro to web accessibility , general accessibility of Samvera applications, tools and resources for evaluation, educating ourselves and making accessibility a part of development from the start.
Keyword:
Connect 2017, Accessibility, and Samvera
Subject:
Samvera Community
Creator:
Tribone, Michael, Lynch, Katherine, and MacMath, Tracy
A presentation given at Samvera Connect 2017 described thus and A presentation that reflects on the learnings and accomplishments of the Hydra-in-a-Box project, the 30-month effort by Stanford Libraries, DuraSpace, and the Digital Public Library of America with funding from the IMLS.
Keyword:
Hydra in a Box, Grants, Samvera, and Connect 2017
Subject:
Samvera Community
Creator:
Frost, Hannah and Giarlo, Michael J
Contributor:
Stanford University Libraries, Digital Public Library of America, Institute of Museum and Library Services, and DuraSpace
A presentation given at Samvera Connect 2017 described thus and In this session we will give a quick background of Hyrax and offer a status update on current Hyrax work including the 2.0.0 release and the new testing process for releases. We will also discuss our early plans for the 2.x series of releases including updates on Collection Extensions work, Valkyrie sprints, plans for new Analytics features, and other potential work in the 2.x series. Last, we’ll talk broadly about roadmapping for Hyrax and what we might expect from Hyrax 3.0.0 and beyond.
Keyword:
Samvera, Connect 2017, and Hyrax
Subject:
Samvera Community
Creator:
Giarlo, Michael J, Rudder, Julie, and Van Tuyl, Steve
Contributor:
Stanford University, University of North Carolina, and Oregon State University
A presentation given at Samvera Connect 2017. A combined slide pack covering brief reports for a number of Interest and Working Groups.
Keyword:
Interest and Working Groups, Lightning talk, Samvera, and Connect 2017
Subject:
Samvera Community
Creator:
Newspapers Working Group, Documentation Working Group, User Experience Interest Group, Data Mapper Working Group, Hyrax Analytics Working Group, Metadata Interest Group, and Geopredicates Working Group
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. and A presentation given at Connect 2017 originally advertised as "Lookup with Context to select metadata values from a controlled vocabulary" and described thus
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 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.
A presentation given at Connect 2017 described thus and In this presentation, we present Fedora 4’s performance in different use cases. These use cases are the most general use cases that were developed by the Fedora 4 performance team. We compare the performance between different versions of Fedora 4 and demonstrate the improvement between these versions. We will also describe the procedures of these performance experiments and demonstrate the software we use (Ansible, AWS, and JMeter). Our performance experiments are conducted in the AWS ecosystem, and we use an R graph tool to visualize the JMeter result. With the AWS grant, we can do many different performance experiments in many scales. Moreover, it is easy to repeat and verify the performance results using AWS. The Fedora 4 performance team wants to know more about the Samvera community’s interests related to the Fedora 4 performance. We plan to gather more use cases from the Samvera community, including middleware such as Solr, Camel, and Fuseki, etc. We can investigate, explore issues, and continue enhancing the future of Fedora 4.