Avalon 2016 Overview

Avalon 2016 Overview

• 1.
  Avalon Media System JonDunn Indiana University Bloomington Evviva Weinraub Northwestern University Open Repositories, 2016 16, June 2016
• 2.
  Avalon, A History
• 3.
  What is Avalon? Opensource software system that enables libraries and archives to provide access to audio and video collections • Hydra Solution Bundle • Goals: – Easily installable and configurable – Serve a variety of use cases and institutions – Create a basis for sustainable development
• 4.
  Why Avalon? • Existingrepository systems don’t work well for time-based media – Issues: integration with streaming servers; hard to support time-based navigation; difficulties in integrating access control • Existing media systems don’t work well with repositories – Issues: focus on short-term access for teaching and learning; limited metadata and access control capabilities; integration with preservation workflows
• 5.
  Project Funding • 2010– 2011: IMLS Planning Grant • 2011-2015: National Leadership Grant from the Institute of Museum and Library Services • 2015-2016: Andrew W. Mellon Foundation Partnership between libraries at Indiana University and Northwestern University
• 6.
  Goals of currentMellon grant 1. Develop additional Avalon functionality 2. Conduct studies of use of audio and video collections by humanities researchers 3. Develop and implement a community-funded business and governance model 4. Deploy Avalon in a hosted SaaS model for testing/pilot
• 7.
  Features of Avalon
• 8.
  Avalon Architecture Avalon MediaSystem Archival Storage Authentic- ation LMS, websites ILS Hydrant Rails App All Users Desktop, Mobile Browser, Drop box Search Browse View Ingest Describe Manage Integrations Collection Managers Authoriz- ation  Avalon code – consists of Hydrant Rails App and the Rubyhorn gem. Other pieces are leveraged. Users Fedora Solr Matterhorn Media Server Media Player (mediaelement.js) Can- Can Ruby- horn Hydra Head Black- light Omni- Auth
• 9.
  Release History • 0.1– July 2012 • 0.5 – October 2012 • 1.0 – May 2013 • 2.0 – October 2013 • 3.0 – May 2014 • 3.1 – July 2014 • 3.2 – January 2015 • 3.3 – March 2015 • 4.0 – September 2015 • 5.0 – May 2016 • 6.0 – August 2016
• 10.
  Faceted browse viaBlacklight
• 11.
  Desktop/Mobile Player
• 12.
  Navigation by Structure
• 13.
  Embedding
• 14.
  Manage Content
• 15.
  Add item: Upload,Dropbox, or Batch
• 16.
  Descriptive Metadata: MODS
• 17.
  Structural Metadata
• 18.
  Access Control
• 19.
  Avalon Use Cases
• 20.
  Use Case: ArchivalFilm
• 21.
  Use Case: MediaWithin Archival Collections 21
• 22.
  Use Case: OnlineExhibits 22
• 23.
  Use Case: OnlinePublishing 23
• 24.
  Use Case: ConsortialLicensed Video
• 25.
  Use Case: VideoReserves in Learning Management System
• 26.
  Use Case: MassDigitization
• 27.
  Moving Forward
• 28.
  Lessons Learned fromAdvisory Board • Clearly define and focus on our core product • Ensure that Avalon is complementary to, not overlapping with, other solutions in the repository and media space • Keep the product as general purpose as possible to help drive adoption • For many institutions, modularity and ability to integrate with existing repository solutions is a key requirement • Partnerships should be chosen wisely • Reduce technical debt (e.g. keeping up with Fedora 4 and Hydra) is important for local installations • Integration with a variety of research and analysis tools will be important for scholarly uptake
• 29.
  Avalon 5.0 LaunchedJune 13th • Organization and Sharing Features – Create private or shareable Playlists – Add whole audio and video files or clips to playlists • Content Ingest API – A lightweight API for importing metadata and links to existing derivatives into Avalon. • Access control enhancements – IP based access control – “Date digitized” field for master files. – Grant access permission for items for set periods of time • More granular searching – Searching now includes section and structure labels – “Date digitized” provided as admin facet . • Accessibility phase 2 – Support for ingesting/delivering captions in VTT and/or SRT files – Player shows captions when available – End user can toggle captioning on/off via player control - mouse and keyboard. Final Fedora 3 Release
• 30.
  Avalon 6.0 (ExpectedOctober 2016) • Feature parity with R5 but on Fedora 4 • Additional transcode engine support (besides Matterhorn) • Upgrade to Hydra 9 / Fedora 4 • Support HLS Flash and retire RTMP support • LDAP based groups for assigning collection staff roles • Other possible features • Better visibility of access control status for bulk selected items
• 31.
  Future Development Strategies •Avalon as a SaaS – Cloud deployment model – Working to develop partnership with Infrastructure Based Service companies – Interested in sites willing to pilot • “Gemification“ of Avalon Architecure (Expected release Winter 2017) – Re-factoring Avalon code for paying off technical debt – Modularizing core Avalon components – Making Avalon components easier to install for other institutions – Re-architecting for full service and gems for other open source repository solutions – Building up from CurationConcerns • Creating a Robust Open Development Community – Using other open source projects as a guide – Potential introduction of Avalon Developers Conference to train and introduce code base to wider developer audience – Introduction of community based sprints
• 32.
  Community Growth New Adopters: Universityof Alberta University of Virginia Washington University, St. Louis
• 33.
  Questions? • www.avalonmediasystem.org • github.com/avalonmediasystem •jwd@iu.edu • evviva.weinraub@northwestern.edu