2. What is Avalon?
Open source software system that enables
libraries and archives to provide access to audio
and video collections
3. What is Avalon?
• Easily installable and configurable
• Works on the Fedora/Hydra stack
• Serves a variety of use cases and institutions
• Sustainable development
4. Use Cases
• Learning
• Consortium Licensed Video
• Video Reserves in LMS
• Research
• Media within archival collections/exhibits
• Online publishing
• Collection Management
• Archival Film
• Mass Digitization
13. Avalon 5.0 – June 13, 2016
• 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
17. • 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 Architecture
– Re-factoring Avalon code for paying off technical debt
– Modules of core Avalon components
– Making Avalon components easier to install for other institutions
– Building up from CurationConcerns/Hydra Works
• Creating a Robust Open Development Community
– Using other open source projects as a guide
– Potential for Avalon Developers Conference to train and introduce code base
to wider developer audience
– Introduction of community based sprints
Near Future for Avalon
18. Avalon 6.0 (Expected October 2016)
Upgrades
• Fedora 4, Hydra 9, Solr, Ruby upgrades
• New data models for Fedora4
• JS media framework decisions
SAAS Preparation
• Develop AWS infrastructure map
• Running AWS Hosted Pilot
• Pricing Models for SAAS
Additional transcode engine support
• Zencoder/amazon elastic transcode
decision
• Rework AWS Instance when Matterhorn
is removed
Easily Edit/Import Structural Metadata
Documentation & Transparency
• Move JIRA to Waffle/Github
• Server mapping
• Improve manual install and
upgrade instructions
• Fedora 4 upgrade path instructions
• Variations migration path
instructions
• Code style guide and standards
Improvements to Playlists
Contributions to IIIF Framework
Enable codeclimate against a repo
19. Avalon 7.0 (Expected Winter 2017)
Exhibits Via Spotlight
• Spotlight integration and implementation
• How-to Documentation
Strategy for QA
• Staffing and workflow
• Integrated Automated Test environments
Remove RTMP Support
• Drop Flash
• Investigate HLS on all platforms and its
implications
• Create one player view in Avalon
• Re-implement media element customization
against the main branch
• Adjust streaming security model
• Move to standard mediaelement
Better internal permissions setup
Gemification/Break interdependencies
• Streaming gem for another repo app
• Bulk metadata/editing gem
Improve packaging
• Create ansible solution and docker
containers (internal only)
• Better developer install methods
• Better OVA
Structural Metadata Improvements
• granular seeking
• move a master file to a different item
• merge/split items
Avalon Media System is an open source software system, originally developed by the libraries at Indiana University and Northwestern University, for managing and providing online access to large collections of digital audio and video for purposes of teaching, learning and research. Avalon was initially released in 2013, and as of early 2016, there are at least six adopters of Avalon but no consistent pathway for adopters to contribute financial or development resources to the project.
In 2015, we were awarded a grant from the Mellon Foundation to create a long-term sustainability plan that includes better integration with the Hydra community, a strategy to increase adoption, and a pilot of a software-as-a-service (SaaS) offering in addition to its current locally-installed model.
This presentation will provide an outline of Avalon’s path forward and how it corresponds with directions of the Hydra and Fedora communities. We are radically changing our development strategy as we move forward, and we will discuss our strategic initiatives and outline new areas of exploration and development. Additionally, we will talk about the advantages and disadvantages we have seen in our partnership model and how we plan to evolve that model as we move forward with Avalon’s development.
This release is our last Fedora 3 release. It will provide a path for folks to migrate off Variations to Avalon (~11 institutions run Variations). The two major points for this release will be providing an ingest method (IU is currently in the process of ingesting our variations content into our production Avalon, ~10,000 of ~30,000 are currently ingested) and the playlist feature. Variations users will be forced to abandon Variations at some point in the nearish future because the next release of OS X will remove Quicktime's support for certain functions Variations need. These features have been deprecated for some time, but Apple is just now officially removing them. There also is not a supported version of Quicktime for Windows 10. So bad news for Variations but good news for Avalon adoption
Evviva
Evviva
Evviva
Watching Hybox as they go through some of these same issues.
Release 7 (gemification) is too fuzzy at this point to discuss in detail.
The next two releases are primarily architecture/rearchitecture focused, they will have some features, such as exhibits via Spotlight, dropping flash, and implementing an embeddable LTI player, but those features are primarily related to the promises made in our Melon Grant.
We are not basing the next release on PCDM, instead we’re doing a direct port of our current models
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
We are not basing the next release on PCDM, instead we’re doing a direct port of our current models
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