Upcoming 6.x Releases

• Enhanced structural metadata editing—edit structure for a section visually
• Import of structure within media files (such as WAV cue points) upon ingest
• Performance improvements for objects and playlists with large numbers of items
• IIIF Manifest generation from media objects

Release 7

Our goal with Avalon 7.0 is to offer a full-featured media streaming application based on the modern Samvera stack. To this end, Avalon 7 will be built using Hyrax as a base, offering developers an environment they know and understand, and offering administrators the flexibility to run stand-alone streaming solutions or integrate scalable streaming into existing Hyrax-based applications. As we work toward full-feature parity with Avalon 6, we will continue development and support. Each dot release milestone is estimated to be an 8-week work cycle.

0.3

The goal of this cycle is to continue refinement of our media work type while developing our streaming/derivative generation pipeline. UI/UX work will begin, and we will deliver initial mockups. Work on the standalone player will continue. 6.4.3 will be cut as a bug fix.

Descriptive Metadata

• Continued refinement of descriptive metadata and the Audiovisual work type
• Descriptive Metadata continues / Version .2 of spec is implemented in WorkType

Ingest/Streaming Pipline

• Discuss matterhorn replacement (sidekiq + ffmpeg?)
  • Derivative parameters can be set by administrators (ex: ffmpeg flags)
  • Derivatives files pushed to streaming location and stream URL info saved in record
  • Basic job information on status of processing relayed to user
• Masterfile management configurable in Avalon (move, delete etc.)
• Files uploaded into Avalon have streaming derivatives created in local and cloud environments (AWS)
• Player can stream using cloudfront or wowza

Structural Metadata Editor

• Get sign off from stakeholders
• Refine mockups
• Implement structural editor in code, based on mockups and any other design/requirements documents
  

Player Work/ IIIF Manifest work

• Store caption files and display them on the player
  • Deciding how this information will be stored in the manifest—reference to a captions file (inline comes later)
• Storing structural metadata XML and generating that as part of the IIIF manifest
• Finalizing how that structure is represented in the manifest

6.4.3

• Cut bug fix from current 6.x branch

0.4

The goal of this cycle is to build out critical feature endpoints. We will initially focus on building out playlist endpoints as a decoupled service (create, read, update, delete). The service will return an IIIF compliant manifest that can be consumed by Avalon's Standalone Player. The team will also work on an initial POC of our batch ingestion. The team will also take an initial pass at UI/UX designs for Avalon on Hyrax.

Core Feature work

• Re-evaluating IIIF 3 manifest generation as the spec nears completion
• Expanded streaming server support

Batch Ingest

• Possible Hyrax import gem (or generic base with per-app modifications)
• Developing in collaboration with WGBH/AVP using Donut work
• Ensure batch ingest spreadsheet and documentation are updated

UI/UX work - mockups / Initial design work

• Create designs for Home/list/item and playlist pages
• Structural metadata rendering
• Avalon look and feel defined, with mockups for evaluation
• Start of style guide
• Wireframes generated
• Hi-fidelity (HTML) mockups?

Critical Feature work

• Playlist Endpoint (No UI)Can create a playlist
  • Can create an item in playlist with a stop / start
  • Can read a playlist and playlist items
• Playlists have an endpoint that returns IIIF manifest(s)
• Standalone player can play playlist manifest (basic functionality)
• Avalon needs

Strategy Development

• Ingest API
• Player API