...

• Enhanced structural metadata editing—edit structure for a section visually (core)
• Import of structure within media files (such as WAV cue points) upon ingest (depending on amount of effort, core or IU)
• Performance improvements for objects and playlists with large numbers of items (investigate to decide whether core or IU)
• IIIF Manifest generation from media objects (IU)

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.

...

Docker and Local Install instructions

0.5 – 11/26/18 - 1/11/19

At the end of this cycle, we will be capable of importing metadata from external services (bibimport), completethe batch ingest functionality started in .4, and begin the implementation of IIIF Auth <https://iiif.io/api/auth/1.0/#introduction> for Avalon's streaming. Other IIIF-related work will involve investigation and possible collaboration with the Universal Viewer developers. In addition, future UI work will be scoped and investigated. A dashboard for ActiveEncode will be designed, as well as mock-ups of how the application itself will be customized from Hyrax defaults.

• Bibliographic import functionality with improved error handling compared to Avalon 6Transcoding pipeline
  • Single item Status Endpoint within ActiveEncode
    
• IIIF Authentication
• Defining the scope for a transcoding dashboard within the application
• Refinement of installation instructions, including Docker and local
• Batch Ingest Functionality FinishedInvestigation of Universal Viewer - Contributing/ adopting parts
• Start UI/UX Work
  • Beginning mockups for homepage, search, etc.

0.6 – 1/28 - 3/22

At the end of this cycle Avalon will provide an endpoint that will deliver an embedded iframe player. Playlists will begin to be implemented, and decisions made about how they are presented and rendered (IIIF). Avalon's transcoding pipeline will also be completed. Avalon's component strategy will be fleshed out and documented. The Samvera PAWG group's work will also be evaluated, and the team will make a call on whether or not we need to add local permissions customization.  The work of skinning Hyrax will also begin, with the goal of delivering an Avalon look and feel to the solution bundle.

...

• BIB Import w/ better Error Handling
• Create Posters and serialize to IIIF manifest. Player should show them 
• Begin implementing playlist functionality
• Embedded playerPlayer
• Permissions working group (Samvera PAWG) check inWG Check in for work in .6
• UI/ Design and - skinning
• Automation scripts (Ansible)- Ansible
• Continued Transcoding pipeline work
  

0.7 – 4/8 - 5/31

At the the end of this cycle, playlists will be completed and Avalon bundle will have a publish/unpublish feature analogous to it's current solution (ideally using core Hyrax features). The bundle will also be deployable using automation tools (TBD).

• Possible Permissions work
• Playlist cont.
• Publish/ Unpublish (save issue)
• Automated deployments Scripts cont'd
• Grant Extension work

...

At the end of this cycle, the Avalon look and feel will continued to be refined. Documentation will be written or expanded upon for use by users and adopters.

• Look and feel refinement
• Instructions - Plugin/ Component Docs
• Bag content for Archivematica
• Avalon Bundle BETA!