Understand what Samvera is and how to participate Understand how to use Samvera Understand the value of Samvera Samvera is a community, a set of tools, and a collection of ready-to run and hosted applications to help build a digital repository for your institution. The community drives the specification and development of sustainable open source technology and honing best practices for managing digital content. This workshop will provide an on-boarding and general entrée to the Samvera community and solutions for non-coders. The first part will provide an overview of Samvera solutions, hosting options and the community – what is it, why is it different? It will showcase applications solving a diverse set of needs and organizations, and discuss the how the community at large works to enable these. The second part will give a general technical overview designed for a non-technical audience. The resources needed to maintain and contribute to a hosted or custom Samvera solution will be discussed, resources that exist to get started will be highlighted plus how to contribute to the community technically and non-technically. The final part will discuss value and how to pitch Samvera and get institutional support. It will discuss the advantages of being part of the community and how that strengthens the sustainability of the tools, the applications, and the community overall. and Slides from a workshop given at Samvera Connect 2019 and described thus
Using Git and GitHub for managing metadata (no new data models, we promise)This session is proposed as a two-part workshop, A workshop given at Samvera Connect 2017 described thus, and 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!
Fedora is the flexible, extensible, open source repository platform that commonly underlies Samvera implementations. Fedora provides a number of core services that Samvera already uses, such as CRUD operations, versioning, and fixity, and several new, potentially useful extended services have been introduced within the last year. The API Extension Framework provides a means of binding services to repository objects in order to extend the functionality of Fedora, while the Import/Export Utility makes it easier to get content into and out of Fedora in standardized formats and packages. This workshop will introduce both of these new services and discuss how they might be used in the context of Samvera. Participants will also have an opportunity to try them out via hands-on exercises in combination with a virtual machine. and A workshop given at Samvera Connect 2017 described thus
A workshop given at Samvera Connect 2017 described thus, Managing Samvera-based Projects and Services, and This hands-on workshop will cover tools and techniques to help managers decide whether to spin up a new Samvera repository, manage the process of building that repository, and maintain the repository once it is in production. We’ll cover the project lifecycle for migrating to Hyrax, defining roles within your team, keeping in sync with community development efforts, managing documentation, and managing user expectations and needs.
Fulcrum is in its third year of developing a publishing platform on Samvera (and is now running on Hyrax). Given the recent interest in possible successor solutions to Digital Commons / bepress, I think this could take the form of a workshop with 3 parts, 1. Presentation of the service model that Fulcrum is being built to support, 2. Presentation of the features and architecture of the platform, with an emphasis on Epub support and publishing workflows, A workshop given at Samvera Connect 2017 described thus, and 3. A group discussion of the kinds of publishing-related service requests attendees are hearing from their communities who are concerned about the Elsevier acquisition of Digital Commons / bepress, and what interest is there in a coordinated community effort around support for publishing and fully-encoded texts.
A workshop given at Samvera Connect 2017 described thus and 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.
A workshop given at the 2014 Open Repositories held in Helsinki. The Hydra for Managers workshop will enable repository managers and curators of digital collections to learn about the Hydra Project, encompassing both the community and the technical development. Focusing on the community primarily, topics covered will include an exploration of how Hydra fits local use cases, how to work with Hydra as a repository, and how to engage with the community to serve local needs and the sustainability Hydra going forward. The workshop will run for 90 minutes and will comprise a mixture of presentations and time to discuss questions raised by attendees. The workshop will be led by established Hydra Partners with different perspectives on using Hydra from differently-sized institutions.
Course syllabus for the Hydra Camp held at Princeton University Libraries, 26-29 August, 2014. The goal of Hydra Camp is to introduce new developers to the skills and tools they will need to successfully build Hydra based digital repository solutions. There’s a lot of ground to cover and you won’t walk out at the end of the week a complete expert, but we hope we’ll have provided you enough of a scaffolding to jump-start your own work and keep learning like the rest of us. We hope that the topics covered at Hydra Camp provide enough breadcrumbs that you’ll have a good idea where to start looking once you get home and start digging into problems on your own!
A proposal for a presentation given at the Open Repositories conference in 2015 held in Indianapolis described thus, One of the many successes of the Hydra community is the fundamental notion from which its name is derived—the concept of many interfaces (“heads”) over top of a single repository (the “body”). The recent release of Fedora 4, with its internal RDF-centric model, has spurred efforts for a community-wide model of collections and works, such that the heads can be sure that the body will behave as they expect it to. That model has been designed and vetted by the Hydra community, and its architecture and initial implementations will be presented in this paper. [Note, and the subject of this proposal has since become known as the 'Portland Common Data Model'.]