Slides presented during the Avalon Media System Version 1.0 Community Webinar on May 29, 2013. Presenters: Jon Dunn, Mark Notess, Claire Stewart.

1. Avalon
Media
System
Version
1.0
Jon
Dunn
Mark
Notess
Claire
Stewart
Community
Webinar
29
May
2013

2. About
Us
• Jon
Dunn
– Interim
Assistant
Dean
for
Library
Technologies,
Indiana
University
Bloomington
Libraries
– Project
Director,
Avalon
• Claire
Stewart
– Head,
Digital
CollecOons
and
Scholarly
CommunicaOon
Services,
Northwestern
University
Library
– Co-­‐Product
Owner/Director,
Avalon
• Mark
Notess
– Head,
Teaching
&
Learning
Systems
Development
IU
Bloomington
Library
Technologies
– Co-­‐Product
Owner,
Avalon

3. Agenda
• Overview
of
version
1.0
funcOonality
and
the
download/tryout
opOons
• Demo
of
version
1.0
• Roadmap
and
schedule
for
planned
future
releases
• QuesOons
and
discussion

4. 1.0
Release
FuncOonality
• Secure
delivery
of
video
and
audio
to
desktop
browsers
and
iOS
(iPad/iPhone)
devices
• IntegraOon
with
a
variety
of
authenOcaOon
systems
are
supported,
along
with
management
of
group-­‐based
authorizaOon
• Content
can
be
added
using
manual
upload
and
descripOon,
or
using
the
batch
import
facility
(dropbox
+
spreadsheet)
• For
fast
and
easy
discovery,
faceted
search
is
based
on
the
Blacklight
discovery
tool
using
MODS
metadata
• Ingest,
management,
and
search
funcOonality
are
built
using
Hydra,
an
open
source
repository
framework
including
Fedora,
Solr
and
Blacklight
• Support
for
both
Adobe
Media
Server
and
the
Red5
open
source
media
server
for
audio
and
video
streaming

5. 1.0
Demo
Server
On
the
demo
server
you
can
– Search
for
audio
and
video
items
– Play
back
items
in
your
browser
or
on
your
iOS
device
If
you
request
collecOon
manager
access,
you
can
– Upload
audio
or
video
files
– Add/edit
descripOve
metadata
– Publish
items
to
make
them
available
– Restrict
access
rights
to
public
(no
restricOon),
collecOon
managers
only,
all
logged-­‐in
users,
or
specified
users
or
groups
– Delete
a
resource
See
h`p://www.avalonmediasystem.org/try-­‐out-­‐avalon

6. Avalon
1.0
InstallaOon
OpOons
Approach
#1:
Downloading
a
Virtual
Machine
Image
An
easy
way
to
try
out
your
own
instance
of
Avalon
is
to
use
a
virtual
machine
image.
There
are
two
opOons
for
accomplishing
this.
1. Install
an
Avalon
Virtual
Machine
image
as
a
portable
.ova
file
that
can
be
opened
and
run
within
a
virtual
machine
environment
such
as
VirtualBox
or
VMware.
The
image
is
based
on
CentOS
Linux
and
includes
sample
content
and
an
interacOve
interface
for
configuring
Avalon
that
runs
on
first
boot.
2. Install
a
Vagrant/VirtualBox-­‐based
image.
This
opOon
uses
the
command-­‐
line
Vagrant
tool
along
with
VirtualBox
to
build
a
CentOS
Linux-­‐based
virtual
machine
running
Avalon.
See
h`p://www.avalonmediasystem.org/download

7. Avalon
1.0
InstallaOon
OpOons
Approach
#2:
Manual
Install
To
set
up
Avalon
manually,
whether
within
a
VM
environment
or
on
hardware,
choose
one
of
the
opOons
below.
1. Follow
the
instrucOons
for
a
Puppet-­‐assisted
manual
install.
Puppet
automates
part
of
the
process
but
is
a
"black
box.”
2. Follow
the
step-­‐by-­‐step
manual
instrucOons
to
see
all
the
pieces
and
all
the
steps.
See
h`p://www.avalonmediasystem.org/download
In
addiOon,
Avalon
source
code
is
available
on
Github:
h`ps://github.com/avalonmediasystem

8. Support
• Join
the
Avalon
discussion
list
– E-­‐mail
avalon-­‐discuss-­‐l-­‐subscribe@indiana.edu
to
subscribe
– The
primary
mailing
list
for
discussion
among
those
evaluaOng,
piloOng,
or
implemenOng
Avalon.
Discussion
may
be
technical-­‐
or
feature-­‐oriented.

9. Demo
of
Version
1.0

10. Future
Avalon
Releases
–
2.0
Releases
planned
every
3
months
• Release
2
(late
summer
2013)
–
key
improvements
planned
– Permissions
can
be
restricted
and
defaults
set
for
units
and
collecOons
– Tracking
and
management
of
master
and
derivaOve
files
in
Fedora
– IniOal
support
for
automated
authorizaOon
groups
(e.g.,
class
rosters
from
LDAP
or
other
external
source)
– AutomaOc
import
of
MARC
bib
data
via
SRU/SRW
– Media
player
improvements
– Improved
workflow
and
opOons
for
batch
and
manual
ingest
– Basic
monitoring
and
troubleshooOng
support
– Other
changes
based
on
community
feedback

11. Future
Avalon
Releases
–
3.0
• Release
3
(end
of
2013)
–
key
improvements
planned
– NavigaOon
by
structural
metadata
(chapters,
acts,
scenes,
tracks,
etc.)
– Import
of
previously
transcoded
derivaOves
– Batch
updaOng
of
exisOng
records
– AddiOonal
authorizaOon
improvements
– Logging
(usage,
errors)
and
usage
staOsOcs
– MigraOon
and
assignment
of
persistent
URLs
– Video
transcoding
improvements
(profiles?
speed-­‐up?)
– Other
changes
based
on
community
feedback
Track
the
roadmap:
h`ps://wiki.dlib.indiana.edu/display/VarVideo/Road+Map+Post+R1

12. QuesOons?
Please
type
any
quesOons
you
have
in
the
chat
window.

13. Take
our
Survey
• h`p://goo.gl/6cXCt

14. Development
Team
Northwestern
University
• Stu
Baker,
project
director
• Steve
DiDomenico,
scrum
master
• Stefan
Elnabli,
metadata/preservaOon
specialist
• Adam
Halle`,
developer
• Michael
Klein,
lead
developer
• Karen
Miller,
metadata
analyst
• Julie
Rudder,
product
owner
• Claire
Stewart,
product
owner/director
• Andrea
Zielke,
project
assistant
Indiana
University
• Jon
Dunn,
project
director
• Chris
Colvard,
lead
developer
• Phuong
Dinh,
developer
• Julie
Hardesty,
metadata
analyst
• Brianna
Marshall,
project
assistant
• Mark
Notess,
product
owner/manager
• Nathan
Rogers,
developer

15. Learn
More
About
Avalon
• Website:
h`p://avalonmediasystem.org/
• Listserv:
E-­‐mail
avalon-­‐discuss-­‐l-­‐subscribe@indiana.edu
to
subscribe
• Social
media:
@avalonmediasys
facebook.com/avalonmediasys
• Or
contact:
Jon
Dunn:
jwd@iu.edu
Claire
Stewart:
claire-­‐stewart@northwestern.edu
Mark
Notess:
mnotess@iu.edu
Avalon
is
funded
in
part
by
a
NaOonal
Leadership
Grant
from
the
InsOtute
of
Museum
and
Library
Services.