The Samvera Branch Renaming Working Group formed in August 2020 to create a recommendation, plan, and timeline for our community to stop using long-practiced "master/slave" coding jargon that perpetuates racist systems and language, and instead embrace and implement positive change, leading by example. This presentation will detail the work of this group, A presentation given at Samvera Connect 2020 On-line described thus, and the guiding morals and philosophy for undertaking this work, where and why we prioritized change while some communities are left uncertain how to proceed with similar work, the challenges we have discovered along the way, our immediate future plans, and the forward-to-better model that we hope this group’s deliverables put forth for the Samvera Community and others in the Open Source world. The 'Related URL' below links to a video recording of the session. The video has closed captioning.
Keyword:
Interest and Working Groups, Connect 2020, and Samvera
Subject:
Samvera Community
Creator:
Rayle, E Lynette, Dunn, Alexandra, Brittle, Collin, Lynch, Kate, Friesen, Jeremy, and Colvard, Chris
Contributor:
Ubiquity Press, University of California Santa Barbara, University of Notre Dame, Cornell University, Emory University, and Princeton University
"what are we going to do about the cloud?" If only we had some kind of animal, recently retrofitted with Wings, that could live up there natively. Fear not, Hyraxes do that. This presentation tackles the what, why, and how of cloud native Samvera. What is the community doing and what are solution bundles supporting? Why should you be interested? Why should you contribute? How can you (yes, i'm looking at you developers, operations folks, repository managers, bosses) benefit? How can your repository make its home among the clouds? The 'Related URL' below links to a video recording of the session. The video has closed captioning., I know what you're asking, and A presentation given at Samvera Connect 2020 On-line described thus
This talk will outline the Surfliner code base, describe the GitLab monolithic source repository, and discuss the reasons behind choosing this model of source control management. It will include background on the systems and workflows used by the UC San Diego and UC Santa Barbara teams that make managing and working productively with a single repository feasible, in addition to a psychomachia-style discussion of the advantages and trade-offs of this approach. The 'Related URL' below links to a video recording of the session. The video has closed captioning. and A presentation given at Samvera Connect 2020 On-line described thus
Wings, the project to move Hyrax to Valkyrie, has been underway for most of this year. What does this transition mean for your existing Hyrax application? How should you account for it in your future planning? How can you take advantage of this work today? This presentation will address these questions for a general community audience. and A presentation at Samvera Connect 2019 described thus
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