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.
A combined slide deck of the short reports from Interest and Working Groups at Hydra Connect 2015. Archivists Interest Group Digital Preservation Interest Group Geospatial Interest Group Hydra GIS Data Modeling Working Group Metadata Working Group Page Turner Interest/Working Group Service Management Interest Group User Experience Interest Group Web Presence Interest Group
A presentation at Hydra Connect 2015 about integrating RDF with Hydra for discoverability and presentation. Trey Pendragon, at the time, was known as Trey Terrell.
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.
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.
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.
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.
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
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.
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 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.
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.
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.
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.
A lightning talk at Samvera Virtual Connect 2016. The talk was in two parts with the second given by Matthew Phillips of Durham University. Unfortunately, his slide deck is missing from the archive.
A presentation at Samvera Virtual Connect 2017. Interest and Working Group Reports and Newspaper IG User Experience IG Repository Management IG Metadata IG Hyrax Analytics WG URI Selection WG Data Mapper WG Applied Linked Data IG Documentation WG Collection Extensions WG CONTENTdm Migration WG Samvera Plugins WG
A lightning talk at Samvera Virtual Connect 2018 described thus and Over the course of the last six months, Duke University Libraries have been engaged in adjusting some of the native features of Hyrax in order to support a research data curation workflow that is heavily mediated and may involve extensive pre-publication alterations to files and their arrangement or description. This presentation will cover how we've adapted a Hyrax application to facilitate research data curation best practices, using the FAIR (findable, accessible, interoperable, and reusable) data guidelines as a framework.
A lightning talk at Samvera Virtual Connect 2018 described thus and At Samvera Connect 2017, we presented a draft roadmap for the Hyrax 2.x-3.x release series. Since then, much work has been done to fulfill the promise of that roadmap, and work continues. In this talk we'll quickly review the roadmap, discuss the current status of work on Hyrax, and call for participation in future development efforts to bring Hyrax to 3.0 as soon as feasible.
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.
Valkyrie is a new persistence layer for Samvera, designed to address performance and sustainability problems. It was developed through the existing Samvera Working Group process, showing that the current Samvera community governance structure can be used to tackle big problems. Valkyrie features pluggable persistence options, allowing Samvera applications to use not just the historical combination of Fedora and Solr, but also other options like Fedora or Solr by themselves, PostgreSQL, and local disk. Allowing Samvera applications to use different persistence options refocuses the Samvera community, shifting away from persistence in Fedora as the defining aspect of the community. Instead, the focus shifts to the shared tools built by the community. and A presentation at Samvera Virtual Connect 2018 described thus
A lightning talk at Samvera Virtual Connect 2018 described thus and Beginning in April, folks from DuraSpace, Stanford University, Digital Curation Experts, CoSector (U. of London), Ubiquity Press, Texas Digital Library and Notch8 have been meeting to discuss their experiences hosting Hyku and develop a roadmap for its future. This presentation will update the Samvera community on the work group members have done to host and implement Hyku, plans for future work, and present several topics for consideration such as a potential governance structure and the feasibility of Hyku going forward.
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.
A presentation at Samvera Virtual Connect 2019 described thus and Samvera Metadata Interest Group Update - Julie Hardesty (Indiana University) Samvera URI Selection Working Group - Ryan Wick (Oregon State University) MODS to RDF Working Group - Eben English (Boston Public Library) Machine-readable Metadata Modeling Specification (M3) Working Group - Arwen Hutt (UC San Diego) Samvera Geospatial Predicates Working Group - James Griffin (Princeton University) Newspapers Interest Group Update - Eben English (Boston Public Library) Repo Managers Interest Group - Nabeela Jaffer (University of Michigan)
A lightning talk at Samvera Virtual Connect 2018 described thus and Bridge2Hyku is an IMLS-funded grant project that is building a migration toolkit to assist institutions interested in migrating their digital content to Hyku. The toolkit contains general guidance for migration planning, documentation for software that enables efficient and effective data migration, and an introduction to the Hyku platform. This presentation will provide an overview of the project goals and timeline, an update on project progress, and information about how to contribute to the Bridge2Hyku migration toolkit.
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 presentation at Samvera Virtual Connect 2019 described thus and We'll go over the Apartment gem, what it means and how it is integrated in the the multi-tenant structure of Hyku.
A lightning talk at Samvera Virtual Connect 2019 described thus and For metadata specialists, creating metadata profiles, system requirements, and accompanying documentation often feels like a game of whack-a-mole. Current practices and technologies also mean comparing your profiles with another institutions’ is an enormous hassle. To address this problem, developers and metadatists came together to create the machine-readable metadata modeling (M3) specification. This presentation will offer some history and use cases for the specification, an update on its current status, and where to learn more.
A presentation at Samvera Virtual Connect 2019 described thus and 6,761,224,773 words. 2,823,957 images. 200+ content sources. And a very long tail of unique metadata fields. This will be a "by the numbers" tour of the digital collections at the University of Michigan Library that highlights some of the challenges of designing and building a new repository and access system for our digital collections that can handle scale, variety, growth, and a rich feature set.
A lightning talk at Samvera Virtual Connect 2019 described thus and A quick look at how WGBH is using the hyrax-batch_ingest gem in their AMS app for multiple shapes and sizes of ingest.
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.
A lightning talk at Samvera Virtual Connect 2019 described thus and The Timeliner is a pedagogical tool that was available in the old Variations application, the Avalon predecessor. It allows for a visual representation of the structure of an audio file or fragment. The tool, which will be made available as a standalone, has been reimplemented using IIIF Presentation API v3 for the presentation layer and the IIIF Auth protocol for the integration with Avalon. We will show the tool and also discuss the technical aspects of the IIIF standards.
A lightning talk at Samvera Virtual Connect 2019 described thus and I'll present the many contexts in which pair programming can be beneficial in different ways, reasons to use pairing as part of the regular practice of your team, the basic mechanics of how pairing works, prompts for staying mindful of power dynamics while pairing, and ideas for introducing the practice to a team that has never really done it before.