1) ASU Libraries implemented a local hosting solution for streaming video resources using the Kaltura video platform integrated with Drupal due to limitations of vendor hosted options. 2) The project involved acquiring content from vendors, ingesting videos into Kaltura, developing metadata and a user interface in Drupal, and ensuring discoverability in the library catalog and discovery tools. 3) Challenges included a longer than expected timeline, unfulfilled features like iOS support, and maintenance costs; lessons learned involved gaining Drupal experience and potential future directions like replacing Drupal.

1. It Takes a Village
Implementing a Homegrown Solution for
Streaming Video Resources

2. deg farrelly
Media Librarian
Matthew Harp
Media Development, Repository
Jeremy Kurtz
Systems Administrator Lead
Tammy Allgood Wolf
Web Services Librarian
Arizona State University Libraries

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

4. Problem Statement
ASU Libraries needed local hosting for licensed
streaming video

5. Successful Acquisition of
Streaming Content
Films on Demand
BBC Shakespeare Plays
Alexander Street Press
Critical Video Editions

6. Limitations to Acquisition
Acquisitions limited to vendor hosted streaming

7. Local Hosting Proposed
Media librarian requested pilot project
• ICS will develop platform
• Content from single vendor identified
• Content licensed by Acquisitions unit

8. Local Hosting Proposed
Media librarian requested pilot project
• ICS to develop platform
• Content from single vendor identified
• Content licensed by Acquisitions unit

9. Initial Pilot Charge
• Digital commercial videos
for ASU Libraries' collections
• Seamless workflow
purchase, license, ingest, describe, manage, authenticate
• Discoverability through the ASU Libraries catalog
• Training and usage reports
provided through ASU's central IT unit.

10. Rewind

11. Video Courses

12. Video Courses

13. Digitization
2003 - 2004

14. Fast Forward
• 2003 Class Streaming
2004
2007 Request for Flash® streaming server
2010 University Technology (UTO) Proposes
Solution
Libraries commit to enterprise plan

15. Pre Assessment
Evaluate Kaltura software
• 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

16. Original Timeline
April 25, 2010 Kaltura proposal as ASU enterprise
•
system
If all went as planned....
by mid-September 2010:
Repository branding and
optimized
by late September:
System testing
by October, 2010:
System up and running

17. Actual Timeline

18. ASU Enterprise Hosting

20. Fish or cut bait

21. Choosing a system
• Commitment made to “Do it now!”
• Other products?
o Video Furnace
o iTunes U
o Vimeo Pro YouTube
o Omeka

22. Selecting Kaltura

23. Nuts 'n Bolts

24. IT @ ASU

25. Sourcing Services

26. Storage

27. Underlying Infrastructure

28. Installing Kaltura

30. Getting Help - You'll need it!

31. System Design

32. Kaltura Logon (Backend)

33. Evolving Standards

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

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

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

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

38. Acquire

39. Ingest

40. Ingest

41. Tag

42. Tag

43. User interface expectations

44. User interface expectations

45. User interface expectations

46. Discoverability - Catalog

47. Discoverability - Summon

48. Discoverability

49. complete catalog record

50. Title display

51. Supplemental materials

52. Kaltura Drupal Home Page

53. Discoverability - Browse

54. Series Listing

55. Use Data - Analytics

57. Freezing Development

58. Freezing Development
Further development ends:
Continued maintenance
Maintain status quo
Not upgrading versions
Unfulfilled:
iOS support not available - Drupal module
Performance Issues / Red5 crashing
Chaptering and captions

59. Developmental Cost

60. Lessons Learned

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

62. Where do we go now?

63. Contacts
deg farrelly
deg@asu.edu / 480.965.1403
Matthew Harp
Matthew.Harp@asu.edu / 480.965.1064
Jeremy Kurtz
Jeremy.Kurtz@asu.edu / 480.965.1902
Tammy Allgood-Wolf
Tammy.Allgood@asu.edu / 480.965.1797