samvera an open source solution for building digital repositories Bess Sadler & Mark Bussey 45 minutes = 35 present + 10 Q & A

What we’ll cover Samvera in the wild Hands on feature exploration Hyrax vs. Hyku (custom vs. packaged) Where to go next Q & A

Tufts Digital Library Fedora content pre-dates Hydra / Samvera Multi-app ecosystem (management, discovery, image library, others) Supports multiple content types Live Site: https://dl.tufts.edu

INDIANA UNIVERSITY Media Collections Online Built using the Avalon Media System Rich tool for management and discovery of audio and visual resources Provides gated discovery and streaming authentication Live Site: https://media.dlib.indiana.edu

Alexandria Digital Research Library Fedora 4 + RDF based Broadly focused Institutional Repository hosting multiple content types Includes a mix of born digital and digitized content Live Site: https://www.alexandria.ucsb.edu

Earthworks Heterogeneous GIS Content Search and browse augmented by spatial search functions Includes content harvested from multiple sources Live Site: https://earthworks.stanford.edu

Next Up: Hands-On Any questions so far?

Create an account Visit http://demo.curationexperts.com/ Click the Login link Click on “Sign Up” (just under the Login button) Enter your e-mail, choose a password, and click on “Sign Up”

Deposit a new work Click on the logo in the upper left corner Click on the “Share Your Work” button Select a type of work Add required metadata, attach a file, choose visibility, accept the deposit agreement Save your work

Edit your work Choose “Dashboard” from the menu in the upper right corner Click on Works Use the “Actions” dropdown to choose edit Enter some data in “Additional Fields” Add a file or two, update versions

Browse content Click on the logo in the upper left Click on the search icon to browse the repository Use search and facet to narrow results View some items Log-out - how does your experience differ?

Next Up: Mini Break + Nominate an Admin

Deposit a new work Reminder: Logo, Share, Select Add required metadata, attach a file, choose visibility, accept the deposit agreement Confirm “one step approval” is selected under Relationships Save your work

View your work? Reminder: dashboard, works What do you see? What does your administrator see? Approve some works (Admins) All Works Review Submissions Notifications

Other features to try Gated discovery: Public, DCE, Private Featured works (Admins) Collections Admin dashboard (Group Walkthrough) Background Processing (Group)

Next Up: The big picture Any questions so far?

Some Names Samvera: (formerly Hydra) an ecosystem of ruby-on-rails focused tools for building rich and flexible digital repositories - refers to the community, governance, and the software framework Fedora: a robust, modular, open source repository back-end for the management and dissemination of digital content Solr: a fast, scalable, search index Blacklight: a flexible, configurable ruby-on-rails based discovery layer that can be used as part of Samvera or as a standalone discovery application Hyrax: Fully customizable repository application - requires software development Hyku: Fully configured (i.e. opinionated) Institutional Repository Avalon: Fully configured (i.e. opinionated) Digital A/V repository

Partial, Incomplete, Concept Cloud RDF Resource TDD Exporters Importers CSS Bootstrap MVC Container GeoConcerns IIIF XML Nokogiri PCDM Non- RDF Resource LDP Linked Data RDF Resque Questioning Authority Blacklight Hydra Core Devise Internationalization Redis RabbitMQ FITS Characterization Derivative Hydra-Forms JQuery Background Jobs OpenOffice ImageMagick FFMPEG Ruby JavaScript Rails Camel Versioning Fixity Messaging ActiveFedora RSolr Indexing TripleStore Sparql SQL WebAC

Objects (Resources) in Fedora 4.x Are described using RDF (“linked-data”) Are related using RDF Are controlled using RDF Can contain non-RDF-Resources Think bitstream – i.e. Files

Observation #1 You don’t have to expose your Samvera content as linked data. BUT The Samvera + Fedora framework makes it much easier when you do want to share linked data content.

Next Up: What next? What do I do back home?

Community Structure Steering Group Stewards of the project - individual membership Partners Formally committed institutional membership Working & Interest Groups Topically aligned groups that span organizations & roles Committers Developer community

Community Resources Website - for the managers https://samvera.org Wiki - for the doers https://wiki.duraspace.org/display/samvera/Samvera Github - for the makers https://github.com/samvera https://github.com/samvera-labs https://github.com/samvera-deprecated

Try it out github.com/samvera demo.curationexperts.com ask other partners for demos! Stanford University Univ. of Notre Dame Indiana University Data Curation Experts Yale University Cornell University Tufts University University of Michigan University of York University of Hull Northwestern University London School of Economics WGBH Boston Virginia Tech University of Oregon Duoc UC (Chile) Lafayette College UC San Diego Digital Repository of Ireland University of Virginia Columbia University Boston Public Library University of Cincinnati Oregon State University University of Alberta University of York UC Santa Barbara DuraSpace Penn State University Royal Library of Denmark Duke University Princeton University Library Washington U. in St Louis University of Houston Digital Public Library of America

Questions Thank you samvera-community@googlegroups.com samvera-tech@googlegroups.com bess@curationexperts.com Last resort… mark@curationexperts.com Thank you

Bonus: PCDM Portland Common Data Model In case you’re interested

How Does PCDM Fit? The Portland Common Data Model Describes relationships between objects Defines where (but not what) metadata about things can be found – see diagram Facilitates content interchange between heterogeneous repositories Makes more code reusable

PCDM Benefits Shared Open Standard Promise of richer data interchange Learn from patterns and practices broader than the Samvera / Repository / LAM community Reusable developer skills, fewer snowflakes

Observation #2 Your end-users should not know your application relies on PCDM, LDP, or RDF BUT You can provide your end-users a richer experience because your application relies on PCDM, LDP, and RDF