...

• 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.

0.1 (Github Milestone) - Using the Avalon Media Player Within Hyrax and IIIF 3.0 Generation and Consumption

The Avalon player will be embedded in a Hyrax app and be initialized with a IIIF manifest generated dynamically from item metadata. In addition, the Hyrax generic work type will be extended minimally to allow for a work to contain necessary technical metadata.

• Core media types (audio and video) can be ingested, transcoded, and attached to a Generic Work.

• IIIF Manifest generated for consumption by player

  • IIIF gem used in Hyrax updated to generate IIIF Presentation API 3.0 manifests (possible collaboration with community)

  • Necessary technical metadata added to Generic work for IIIF manifest (upstream)

• Media player consumes IIIF manifest generated by the application from the work's metadata

• Player streams media (basic http streaming or from specific streaming server)
  

• Development, testing and infrastructure needs for Avalon 7 development defined and in place
  

0.2 (Github Milestone)

This preview will further refine the IIIF Player, auto-generate IIIF manifests based on an Avalonish -work type metadata, and begin discussion and sketches for a branded hyrax-based Avalon solution bundle. Structural metadata will be ported over as is for use in a IIIF manifest.

...

work

...

• Order of masterfiles is necessary metadata
• Order of multi-valued pieces of metadata will wait until later

...

• Time can be navigated via structural metadata
• Port Structural metadata (structure within) as current XML 

...

• We intend for the manifest to be a central point of interoperability
• The manifest will be based on the current IIIF-AV 3.0 standard
• Manifests will be generated based on technical and descriptive metadata
• Manifests  should ideally use the same endpoints as Hyku (possibly the same generation tool)
• The manifest contains the structural information, The display should exercise the manifest. 
• Structural metadata will be stored in XML and crosswalked to the manifest
• Metadata experts talk through what metadata (descriptive or any other kind) to include. There is already an issue for the recommended descriptive metadata. Need to take a deeper look for technical metadata. (https://github.com/avalonmediasystem/avalon/issues/1772)(https://gist.github.com/jlhardes/1e3adada7410591f46b170e65dce20af)

...

• Matterhorn gives us the nice interface for monitoring
• Hyrax may suggest a monitoring interface for job queues
• Exploring how from a collection manager/depositor perspective: if there are issues, how does that get resolved?

...

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 Pipeline

...

• 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

...

.

...

...

Structural Metadata Editor (for r6)

• 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 – 9/17 - 11/10/18

...

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?

Transcoding pipeline work — ActiveEncode

Continued metadata work

• Batch ingest using RDF

Model refinement

Docker and Local Install instructions

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

...

• Transcoding 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
• 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.

...

• Create Posters and serialize to IIIF manifest. Player should show them 
• Begin implementing playlist functionality
• Embedded Player
• Permissions WG Check in for work in .6
• UI/ Design - skinning
• Automation scripts - 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).

• BIB Import w/ better Error Handling
• Create Posters and serialize to IIIF manifest. Player should show them 
• 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!