It Takes a VillageImplementing a Homegrown Solution for Streaming Video Resources

Arizona State University Libraries

deg farrellyMedia Librarian

Matthew HarpMedia Development, Repository

Jeremy KurtzSystems Administrator Lead

Tammy Allgood WolfWeb Services Librarian

Presentation Outline

• Problem leading to the project proposal

• Technology discussion

• Use of Drupal for the project

• Overview of user interface

• Costs, lessons learned, and future directions

Problem Statement

ASU Libraries needed local hosting for licensed streaming video

Successful Acquisition of Streaming Content

Films on Demand

BBC Shakespeare Plays

Alexander Street Press

Critical Video Editions

Limitations to AcquisitionAcquisitions limited to vendor hosted streaming

Local Hosting ProposedMedia librarian requested pilot project

• ICS will develop platform

• Content from single vendor identified

• Content licensed by Acquisitions unit

Local Hosting ProposedMedia librarian requested pilot project

• ICS to develop platform

• Content from single vendor identified

• Content licensed by Acquisitions unit

Initial Pilot Charge• Digital commercial videos

for ASU Libraries' collections

• Seamless workflowpurchase, license, ingest, describe, manage, authenticate

• Discoverability through the ASU Libraries catalog

• Training and usage reportsprovided through ASU's central IT unit.

Rewind

Video Courses

Video Courses

Digitization

2003 - 2004

Fast Forward

• 2003 Class Streaming

2004

2007 Request for Flash® streaming server

2010 University Technology (UTO) Proposes Solution

Libraries commit to enterprise plan

Pre Assessment

• Licensing permissions• Metadata and cataloging workflow• Usage statistics• Cost of personnel• Cost of long term storage• Continuing cost of project and Scalability

Project Dependencies• Alt^i/UTO implementation and negotiations

• Supporting departments financial support

• Collection Development purchasing of content

Evaluate Kaltura software

Original Timeline•April 25, 2010 Kaltura proposal as ASU enterprise system

by mid-September 2010: Repository branding and optimized

by late September: System testing

by October, 2010: System up and running

If all went as planned....

Actual Timeline

ASU Enterprise Hosting

Fish or cut bait

Choosing a system• Commitment made to “Do it now!” • Other products?

o Video Furnaceo iTunes Uo Vimeo Pro YouTubeo Omeka

Selecting Kaltura

Nuts 'n Bolts

IT @ ASU

Sourcing Services

Storage

Underlying Infrastructure

Installing Kaltura

Getting Help - You'll need it!

System Design

Kaltura Logon (Backend)

Evolving Standards

Why Drupal

• Flexible front-end CMS which allowed administration and viewing of Kaltura Content

• Easy to maintain look and feel of main library site

• In-house expertise

• Already had Arizona State University account authentication module for Drupal

Kaltura Module for Drupal

• http://drupal.org/project/kaltura

• Drupal permission integration

• Upload video in any format

• Metadata stored locally

• CCK field representation of media

• Full integration with Drupal Views

• Video Comments

Interface Expectations

• ASU header and footer

• ASU authentication

• Title and subtitle fields

• Description field with wysiwyg editor

• File uploading options for support materials

• Persistent url path

Using Drupal to meet expectations

• ASU header and footer - Used ASU Drupal theme from library web site

• ASU authentication - ASU created module for "webauth" authentication

• Title and subtitle fields - CCK fields

• Description field with wysiwyg editor - WYSIWYG module with TinyMCE editor

• File uploading options for support materials - Filefield module

• Persistent url path - Path (core) module

Acquire

Ingest

Ingest

Tag

Tag

User interface expectations

User interface expectations

User interface expectations

Discoverability - Catalog

Discoverability - Summon

Discoverability

complete catalog record

Title display

Supplemental materials

Kaltura Drupal Home Page

Discoverability - Browse

Series Listing

Use Data - Analytics

Freezing Development

Freezing DevelopmentFurther development ends:

Continued maintenance

Maintain status quo

Not upgrading versions

Unfulfilled:

iOS support not available - Drupal module

Performance Issues / Red5 crashing

Chaptering and captions

Developmental Cost

Lessons Learned

Drupal Lessons

• Need previous experience with Drupal

• Unable to enable HTML5 streaming in order to provide access to iOS (Apple) mobile devices

• Drupal Module officially in "beta"

• Deleting items in Drupal did not delete them in Kaltura

Where do we go now?

Contacts

deg farrellydeg@asu.edu / 480.965.1403

Matthew HarpMatthew.Harp@asu.edu / 480.965.1064

Jeremy KurtzJeremy.Kurtz@asu.edu / 480.965.1902

Tammy Allgood-WolfTammy.Allgood@asu.edu / 480.965.1797