Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Avalon Media System
Jon Dunn
Indiana University Bloomington
Evviva Weinraub
Northwestern University
CNI Spring 2016
April ...
Avalon, A History
What is Avalon?
Open source software system that enables libraries
and archives to provide access to audio and video
colle...
Why Avalon?
• Existing repository systems don’t work well for
time-based media
– Issues: integration with streaming server...
Project Funding
• 2010 – 2011: IMLS Planning Grant
• 2011-2015: National Leadership Grant from
the Institute of Museum and...
Goals of current Mellon grant
1. Develop additional Avalon functionality
2. Conduct studies of use of audio and video
coll...
Features of Avalon
Avalon Architecture
Avalon Media System
Archival
Storage
Authentic-
ation
LMS,
websites
ILS
Hydrant Rails App
All Users
De...
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...
Faceted browse via Blacklight
Desktop/Mobile Player
Navigation by Structure
Embedding
Manage Content
Add item: Upload, Dropbox, or Batch
Descriptive Metadata: MODS
Structural Metadata
Access Control
Avalon Use Cases
Use Case: Archival Film
Use Case: Media Within Archival
Collections
21
Use Case: Online Exhibits
22
Use Case: Online Publishing
23
Use Case: Consortial Licensed Video
Use Case: Video Reserves in
Learning Management System
Use Case: Mass Digitization
Moving Forward
Lessons Learned from Advisory Board
• Clearly define and focus on our core product
• Ensure that Avalon is complementary t...
Future Development Strategies
• Migrating from Fedora 3 to Fedora 4
– Fedora 4 running with our current data model (so dat...
Community Growth
New Adopters:
University of Alberta University of Virginia Washington University,
St. Louis
Questions?
• www.avalonmediasystem.org
• github.com/avalonmediasystem
• jwd@iu.edu
• evviva.weinraub@northwestern.edu
Discussion Questions
• What other use cases do you have for A/V
access?
• What do you look for in adopting or investing
in...
Upcoming SlideShare
Loading in …5
×

CNI 2016: Avalon overview

262 views

Published on

Jon Dunn, Indiana University
Evviva Weinraub, Northwestern University
April 2016 Presentation given to The Coalition for Networked Information (CNI)

Published in: Technology
  • Be the first to comment

  • Be the first to like this

CNI 2016: Avalon overview

  1. 1. Avalon Media System Jon Dunn Indiana University Bloomington Evviva Weinraub Northwestern University CNI Spring 2016 April 4, 2016
  2. 2. Avalon, A History
  3. 3. What is Avalon? Open source 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. 4. Why Avalon? • Existing repository 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. 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. 6. Goals of current Mellon 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. 7. Features of Avalon
  8. 8. Avalon Architecture Avalon Media System 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. 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. 10. Faceted browse via Blacklight
  11. 11. Desktop/Mobile Player
  12. 12. Navigation by Structure
  13. 13. Embedding
  14. 14. Manage Content
  15. 15. Add item: Upload, Dropbox, or Batch
  16. 16. Descriptive Metadata: MODS
  17. 17. Structural Metadata
  18. 18. Access Control
  19. 19. Avalon Use Cases
  20. 20. Use Case: Archival Film
  21. 21. Use Case: Media Within Archival Collections 21
  22. 22. Use Case: Online Exhibits 22
  23. 23. Use Case: Online Publishing 23
  24. 24. Use Case: Consortial Licensed Video
  25. 25. Use Case: Video Reserves in Learning Management System
  26. 26. Use Case: Mass Digitization
  27. 27. Moving Forward
  28. 28. Lessons Learned from Advisory 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. 29. Future Development Strategies • Migrating from Fedora 3 to Fedora 4 – Fedora 4 running with our current data model (so datastreams, etc). – Ensure no features in Avalon become nonfunctional during the upgrade • 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 – Re-factoring Avalon code for paying off technical debt – 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
  30. 30. Community Growth New Adopters: University of Alberta University of Virginia Washington University, St. Louis
  31. 31. Questions? • www.avalonmediasystem.org • github.com/avalonmediasystem • jwd@iu.edu • evviva.weinraub@northwestern.edu
  32. 32. Discussion Questions • What other use cases do you have for A/V access? • What do you look for in adopting or investing in an open source solution? • What barriers do you encounter in adopting or investing in open source? • What factors influence your choice of SaaS vs. on-premise implementations?

×