The Avalon Media System: An Open Source Audio/Video System for Libraries and Archives
26
The Avalon Media System An open source audio/video system for libraries and archives Stu Baker Stefan Elnabli CIC Indiana University Media PreservaAon Conference 17 April 2013
-
Upload
avalon-media-system -
Category
Technology
-
view
275 -
download
1
description
This presentation was given by Stu Baker and Stefan Elnabli at a 2013 Media Preservation meeting hosted by the Media Preservation Initiative in Bloomington, Indiana.
Transcript of The Avalon Media System: An Open Source Audio/Video System for Libraries and Archives
The Avalon Media System An open source audio/video system for libraries and archives Stu Baker Stefan Elnabli CIC Indiana University Media PreservaAon Conference 17 April 2013
About Us
• Stu Baker – Associate University Librarian for Library Technologies, Northwestern University
– Co-‐Project Director, Avalon
• Stefan Elnabli – Moving Image and Sound PreservaAon Specialist, Northwestern University
– Audiovisual Media and Metadata Specialist, Avalon
Agenda
• Project background and overview • MoAvators and use cases • Demo • Release 1 pilots • Plans beyond Release 1 • IntegraAon scenarios • Development process and community • QuesAons and discussion
Project ObjecAves
Goal: Create an open source system to enable libraries and archives to provide online access to video and audio collecAons • Digital audio/video management and delivery system,
focused on needs of libraries and archives • Follow an agile, open source development model • Leverage exisAng technologies, where feasible • Communicate and market the project broadly to increase
awareness and grow the community of users and developers
Project Overview
• Funded in part by a NaAonal Leadership Grant from the InsAtute of Museum and Library Services
• Original name: Varia*ons on Video
• Planning grant: – August 2010 – July 2011
• ImplementaAon grant: – September 2011 – October 2014
• Partnership between libraries at Indiana University and Northwestern University
Project Partners and Collaborators
What needs are we trying to serve? • Libraries and archives (and museums?) • Wide variety of audio/video collecAons, uses, and access needs – Licensed educaAonal video collecAons – Video/audio e-‐reserves – Archival collecAons – Open access collecAons
• Research and teaching & learning use • Long-‐term management and access • Tie-‐in with preservaAon
MoAvators
ExisAng SoluAons Incomplete for Libraries and Archives • InsAtuAonal and digital library repositories
– e.g. DSpace, Fedora, Digital Commons, ContentDM • Web video services
– e.g. YouTube, Vimeo • Classroom lecture capture
– e.g. Echo360, Mediasite, Opencast Maberhorn • Online video environments
– e.g. Kaltura, Brightcove • Streaming servers
– e.g. Flash Media Server, Real Helix, Wowza, Red5 • Digital asset management systems
– e.g. OpenText, NetXposure, etc.
Bridging library and academic IT content management
Release 1 (“any day now!”) • Mobile and desktop playback support
• AuthenAcaAon and group-‐based authorizaAon
• Faceted search, using Blacklight
• Manual and batch import
Demo
R1 Pilots
Avalon Architecture
Avalon Media System
Archival Storage
AuthenAc-‐aAon
LMS, websites
ILS Hydrant Rails App
All Users
Desktop, Mobile
Browser, Drop box
Search Browse View
Ingest Describe Manage
Integra*ons
CollecAon Managers
Authoriz-‐aAon
n Avalon code – consists of Hydrant Rails App and the Rubyhorn gem. Other pieces are leveraged.
Users
Fedora Solr Maberhorn Media Server
Media Player (Maberhorn Engage)
Can-‐Can
Ruby-‐ horn
Hydra Head
Black-‐ light
Omni-‐Auth
Beyond R1 (ParAal List, UnprioriAzed) • AuthorizaAon improvements & integraAons • Structural metadata for navigaAon • Technical metadata • Workflow & batch loading improvements • Playlists and clip making • Easy player embedding for other contexts, e.g., course management,
websites, publishing sites • Transcripts • Publishing out to other systems • More opAmizaAon for mobile • Focused accessibility work • Improvements based on pilots, user feedback, usability tesAng Releases every three months
Stu Bakerproject director
Jon Dunnproject director
Chris Colvardlead developer
Phuong Dinhdeveloper
Steve DiDomenicoscrum master
Stefan Elnablimetadata/preservation specialist
Adam Hallettdeveloper
Nathan Rogersdeveloper
Michael Kleinlead developer
Julie Hardestymetadata analyst
Karen Millermetadata analyst
Julie Rudderproduct owner
Claire Stewartproduct owner/director
Mark Notessproduct owner/manager
Andrea Zielkeproject assistant
Brianna Marshallproject assistant
Development Team
Development process
• A single, blended team • Scrum • F2F for scrum training, prioriAzaAon
• Daily standups, IRC
Working towards community
• Lessons learned in development process • Working with Hydra community • Working with OpenCast maberhorn
ParAcipaAon
• Try out R1 (any day now!): hbp://www.avalonmediasystem.org/try-‐out-‐avalon
• Download R1: hbp://www.avalonmediasystem.org/download
• On GitHub: hbps://github.com/avalonmediasystem/avalon
• Read our blog: hbp://www.avalonmediasystem.org/blog
QuesAons?
Learn More About Avalon • Website: hbp://avalonmediasystem.org/ • Listserv: E-‐mail avalon-‐l-‐[email protected] to subscribe • Social media:
@avalonmediasys
facebook.com/avalonmediasys
Or contact:
Jon Dunn: [email protected] Stu Baker: [email protected]
