It takes a Village: Implementing a Homegrown Solution for Streaming Video Resources

  • 621 views
Uploaded on

Slides from the ALA 2012 presentation by ASU Libraries …

Slides from the ALA 2012 presentation by ASU Libraries
with: deg farrelly, Matthew Harp, Jeremy Kurtz, and Tammy Allgood

More in: Education , Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
621
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
9
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. It Takes a VillageImplementing a Homegrown Solution forStreaming Video Resources
  • 2. deg farrelly Media Librarian Matthew Harp Media Development, Repository Jeremy Kurtz Systems Administrator Lead Tammy Allgood Wolf Web Services LibrarianArizona 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 StatementASU Libraries needed local hosting for licensedstreaming video
  • 5. Successful Acquisition ofStreaming ContentFilms on DemandBBC Shakespeare PlaysAlexander Street PressCritical Video Editions
  • 6. Limitations to AcquisitionAcquisitions limited to vendor hosted streaming
  • 7. Local Hosting ProposedMedia librarian requested pilot project• ICS will develop platform• Content from single vendor identified• Content licensed by Acquisitions unit
  • 8. Local Hosting ProposedMedia 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 ASUs central IT unit.
  • 10. Rewind
  • 11. Video Courses
  • 12. Video Courses
  • 13. Digitization 2003 - 2004
  • 14. Fast Forward• 2003 Class Streaming20042007 Request for Flash® streaming server2010 University Technology (UTO) ProposesSolution Libraries commit to enterprise plan
  • 15. Pre AssessmentEvaluate Kaltura software • Licensing permissions • Metadata and cataloging workflow • Usage statistics • Cost of personnel • Cost of long term storage • Continuing cost of project and ScalabilityProject Dependencies • Alt^i/UTO implementation and negotiations • Supporting departments financial support • Collection Development purchasing of content
  • 16. Original TimelineApril 25, 2010 Kaltura proposal as ASU enterprise•systemIf 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
  • 19. Fish or cut bait
  • 20. Choosing a system • Commitment made to “Do it now!” • Other products? o Video Furnace o iTunes U o Vimeo Pro YouTube o Omeka
  • 21. Selecting Kaltura
  • 22. Nuts n Bolts
  • 23. IT @ ASU
  • 24. Sourcing Services
  • 25. Storage
  • 26. Underlying Infrastructure
  • 27. Installing Kaltura
  • 28. Getting Help - Youll need it!
  • 29. System Design
  • 30. Kaltura Logon (Backend)
  • 31. Evolving Standards
  • 32. 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
  • 33. 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
  • 34. 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
  • 35. Using Drupal to meetexpectations• 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
  • 36. Acquire
  • 37. Ingest
  • 38. Ingest
  • 39. Tag
  • 40. Tag
  • 41. User interface expectations
  • 42. User interface expectations
  • 43. User interface expectations
  • 44. Discoverability - Catalog
  • 45. Discoverability - Summon
  • 46. Discoverability
  • 47. complete catalog record
  • 48. Title display
  • 49. Supplemental materials
  • 50. Kaltura Drupal Home Page
  • 51. Discoverability - Browse
  • 52. Series Listing
  • 53. Use Data - Analytics
  • 54. Freezing Development
  • 55. Freezing DevelopmentFurther development ends: Continued maintenance Maintain status quo Not upgrading versionsUnfulfilled: iOS support not available - Drupal module Performance Issues / Red5 crashing Chaptering and captions
  • 56. Developmental Cost
  • 57. Lessons Learned
  • 58. 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
  • 59. Where do we go now?
  • 60. 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