The document discusses the University of Virginia's plans to implement the Avalon digital asset management system to provide access to audiovisual materials. Key points include: - Avalon will be rolled out in July 2014 to allow access by 39 colleges and universities. Content will steadily increase through Fall 2014. - Implementation will require half an FTE AV conservator, a quarter FTE software engineer, and other technical resources over a 6 month period. - The initial production setup will use a virtual machine for Avalon and related software like Fedora and Solr. Additional features are needed like time-based access restrictions and custom thumbnails. - Ongoing involvement with the Avalon community is important to promptly

1. AVALON at the
University Of Virginia

2. Use Cases
●Current
oAccess to licensed AV resources
oPreservation/Access to rare/unique AV materials
oAccess to recordings of lecture series’
●Impending
oConcert Recordings
●Considered
oElectronic Reserves

3. Current Media “Solutions”
●Hosted solutions
oKaltura
oShared Shelf
●Local “systems”
ofiles somewhere
oMARC in SIRSI
oSolr records presented in blacklight

4. Implementation Timeframe
●July 2014 Production roll-out for VIVA consortium
oshibboleth access to up to 39 colleges and universities at 55 campuses
●Fall 2014 Avalon → Blacklight pipeline
●Fall 2014 steady increase in content
●Fall 2014 Master File Integration with Fedora 4
●Spring 2015 AP Trust integration
●Spring 2015 Course Reserves (maybe)

5. Implementation Resources
½ FTE AV Conservator with project manager hat
¼ FTE Software Engineer
Sprinkling of UX engineers
Dash of emerging technologies consultation
Healthy heaping of Dev-Ops heavy lifting
Bake for 6 months

6. Production Setup
Avalon VM
Rails (RVM)
Fedora
Solr Transcoding
Hardware
Matterhorn
F5 Load
Balancer
Firewall
Hardware
Streaming
Red5
Hardware
Streaming
Red5

7. Ideal Production Setup
Avalon VM
Rails (RVM)
Transcoding
Hardware
Matterhorn
F5 Load
Balancer
Firewall
Hardware
Streaming
Red5
Hardware
Streaming
Red5
Shared
Fedora
Box
Shared
Solr
Box
Second
Matterhorn
Worker Box

8. Needed features
●Time-based access restrictions
●Custom thumbnails
●Collection-specific handling of master files
●Specification of offset in URLs
●EBU-Core RDF metadata

9. Future of the Community
Want Need to stay in sync with the community
●prompt upgrades
●push changes upstream