Page tree
Skip to end of metadata
Go to start of metadata

For information on current and previous versions of Avalon, please see the Releases page on Github.

Release 6.x

Summer 2017 — Migration tools, Player API, and AWS support
  • Fedora 3—Fedora 4 Migration tool with reporting features 
  • Player API  
  • Easily Edit/Import Structural Metadata 
  • Continued work on AWS integration/support 
  • Simplification of Development environment (e.g. nginx, ffmpeg transcoding)
  •  SaaS Pilot—Avalon hosted in the cloud

Release 7

Moving to Hyrax/ Modern Hydra Stack   

For more information on Release 7, please see our standalone road map: Avalon 7 Roadmap

Below are features originally planned for release 7; some of these will be edited or removed as Avalon is written to use Hyrax as its base.
  • PCDM support
  • 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
  •  Structural Metadata Improvements
  • granular seeking
  • move a master file to a different item
  • merge/split items
  • Better local transcode support
  • Descriptive metadata stored as RDF

Release 8 

Full feature list yet to be determined.

  • Publishing Out to External Media Sites 
  • Dynamic Adaptive Streaming 
  • Deeper integration with Hyrax Community 
  • Further gemification/shredding of core components

Technical work yet to be scheduled:

  • Improve unit testing 
  • SAAS solution 
  • RDF
  •  ImplemenPCDM
  •  Packaging/deployment, e.g. use of Docker. Improving installation experience.  
  • Scalability issues that may arise  
  • Automated functional testing

Unscheduled Features

  • Facebook integration 
  • Reporting and metrics 
  • Collections based group management 
  • Collections based master file handling 
  • Internationalization 
  • Administrative metadata (owner, digitizer)
  • Provenance metadata 
  • PBCore/DublinCore crosswalks 
  • Controlled Vocabularies 
  • Import media from other sources 
  • Image content/auxiliary items (how does Avalon fit with other initiatives?)
  • Integration with oral history tools



  • No labels