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
Samvera circulated a "Season's Greetings" card for the first time in December 2020. It features the Samvera tree festooned with decorative lights and incorporates in the winter scene the logos for Samvera's major software items.
A presentation given at the Open Repositories conference in 2010. In part, the proposal reads and While repositories provide obvious benefits in hosting and managing content, it is equally clear that there is no “one size fits all” solution to the range of digital asset management needs at a typical institution, much less across institutions. A system that supports the submission, approval and dissemination of electronic theses and dissertations, for example, has demonstrably different requirements than a digitization workflow solution, an e-science data repository, or media preservation and access system. There is a clear need in the repository community to readily develop and deploy content-, domain-, and institution-specific solutions that integrate the flexibility and richness of customized applications and workflows with the underlying power of repositories for content management, access and preservation. This paper will provide an overview of Hydra’s philosophy, architecture, and components, as well as demonstrations of various Hydra installations. The paper will also provide a progress report on Hydra development to date and its overall roadmap, as well as provide observations on the successes and challenges of community-based development of shared repository solutions.
• No single institution can resource the development of a full range of digital content management solutions on its own, …yet each needs the flexibility to tailor solutions to local demands and workflows. • No single system can provide the full range of repository‐based solutions for a given institution’s needs, *…yet sustainable solutions require a common repository infrastructure The Hydra project has tested out these assumptions and reports in this presentation the outcomes from applying them to the work undertaken. The paper was delivered as a 'Prezi' presentation which can be found by following the 'Related URL' link below., The proposal for this presentation at the Open Repositories conference in 2011 begins, and The Hydra project is a digital repository initiative started in 2008 that originally brought together three institutions (Stanford University, the University of Virginia and the University of Hull) and DuraSpace, with a common identified need to provide a flexible means for managing and delivering a wide range of digital content types. The project has since investigated and worked towards a reusable framework for multipurpose, multifunction, multi‐institutional repository‐enabled solutions. Two previously identified assumptions have underpinned the work