Designing an Enterprise Video Capture System

784 views

Published on

Presentation given at CCUMC Buffalo, 2010.

Published in: Education, Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
784
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
32
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Designing an Enterprise Video Capture System

  1. 1. Designing an Enterprise Video Capture System Andy Wasklewicz TECHNOLOGY ARCHITECT Stanford University School of Medicine
  2. 2. Context
  3. 3. Overview ‣ World leader in medical research and training ‣ Emphasis on multi-disciplinary research ‣ Curriculum that melds the study of basic science and the clinical practice of medicine
  4. 4. Basic Facts ‣ Medical School Students: 400 ‣ Students in 5+ years Graduate Students: 820 ‣ Postdoctoral Scholars & Clinical Fellows: 1418 ‣ Undergraduate & graduate students outside the SoM served by the school: 628 ‣ Faculty: Practicing clinicians and researchers
  5. 5. Culture of Capture ‣ 1980’s - Capture on VHS - available for checkout ‣ 1998 - Streaming REAL media ‣ 2007 - REAL downloadable ‣ 2008 - H.264/.MP4 downloadable
  6. 6. Curriculum Changes ‣ Move to fewer lectures ‣ More small group and team-based learning ‣ More integrated approach - move away from discipline based courses ‣ We still capture a lot!
  7. 7. Internal Drivers
  8. 8. Accreditation ‣ Shift to “measurable outcomes” ‣ Proven skill-based competencies ‣ Curriculum tracking (database)
  9. 9. Off Campus Growth ‣ Moving research departments ‣ Moving clinical departments ‣ Distribute content beyond MD curriculum
  10. 10. Video Beyond Lectures ‣ Public web video increasing ‣ Requests for special video ‣ People creating their own videos (teaching and research) ‣ Students self-capturing for skills documentations
  11. 11. SoM Technology Trends ‣ Mobility ‣ 80% of student population reports regularly using portable media device ‣ 75% have phones capable of playing media ‣ Median time spent on laptop 6-8 hours daily Stanford School of Medicine. January 2009. Student Technology Ownership and Use Survey
  12. 12. Quality & Formats ‣ Student/Faculty expectations ‣ Mobile devices to HD screens Stanford School of Medicine. January 2009. Student Technology Ownership and Use Survey
  13. 13. New Building ‣ Li Ka Shing Center for Learning and Knowledge ‣ Intersection between School of Medicine, Hospitals Computer Science, Engineering
  14. 14. External Drivers
  15. 15. Storage ‣ Cheaper, faster, bigger ‣ Cloud storage
  16. 16. Capture & Encoding Hardware ‣ Cheaper, faster ‣ Efficiency ‣ Video quality
  17. 17. Mobile Capture Hardware ‣ Smaller, cheaper, faster ‣ Mobile consumer hardware ‣ Students can & will capture lecture themselves
  18. 18. Distribution Channels ‣ Home grown solutions ‣ Custom applications ‣ Learning Management Systems ‣ iTunesU ‣ Youtube
  19. 19. ‣ OpenCast ‣ Podcast Producer ‣ MediaCore Open Communities
  20. 20. Policy & Conversations
  21. 21. ‣ Listen to faculty concerns ‣ Engage in OPEN dialogue ‣ Partner with University Council Education and Discussion
  22. 22. Releases and Rights ‣ University media release ‣ Stanford School of Medicine release ‣ Creative Commons Licensing
  23. 23. Student Responsibility ‣ Cover all course materials (electronic and hard copy) ‣ Provide students with more flexibility to access course materials ‣ Clarify policy on student sharing of course materials ‣ Address faculty concerns regarding redistribution of content
  24. 24. Content Access & Appropriate Use Stanford University School of Medicine course materials are intended for curriculum and course related purposes and are copyrighted by the University. Appropriate access to this content is given for personal academic study and review purposes only. Unless otherwise stated in writing, this content may not be shared, distributed, modified, transmitted, reused, sold, or otherwise disseminated.
  25. 25. Content Access & Appropriate Use These materials may also be protected by additional copyright; any further use of this material may be in violation of federal copyright law. Violators of this policy will be referred to the Committee on Professionalism, Performance and Promotion for disciplinary purposes.
  26. 26. ‣ How long to keep? ‣ Who decides? ‣ Retrieval Archiving Policy
  27. 27. MediaFlow
  28. 28. MediaFlow
  29. 29. MediaFlow Goals ‣ Automate the capture of all core classes and events ‣ Consolidate event data ‣ Video from anywhere to anywhere ‣ 5pm same day deadline for delivery of all media ‣ Modular systems design
  30. 30. System Architecture ‣ Anywhere to anywhere ‣ Decoupled systems ‣ Plan for and accept obsolescence
  31. 31. ‣ Two years of design/prototyping ‣ 500+ hardware components ‣ Eight miles AV fiber MediaFlow - Core AV
  32. 32. ‣ 16 Apple XServe cluster ‣ 220Ghz processing power ‣ 44TB SAN storage MediaFlow - Core IT
  33. 33. Custom/Podcast Producer Distribution YouTube Shared Storage Custom/Xgrid iTunesU Primary Master Camera External Fiber Encoders Sakai RSS/ATOM Fiber Channel AV Fiber Internal
  34. 34. MediaFlow - Core IT Preflight Archive Original Text2Speech Add Watermark Generate Bumpers Merge Movies without transitions Encode for iPod Audio Encode for High QualityVideo Encode for iPod Video Encode for High QualityVideo Generate ChaptersGenerate Chapters OCR Chapters Add Chapters Merge Movies with Transitions
  35. 35. ‣ Front-end metadata capture for course administrators ‣ Java, Tomcat, Oracle MediaFlow - Maestro
  36. 36. ‣ Link between Maestro and core systems ‣ Provides data for digital signs ‣ Provides delay/start/stop/extend/flag functionality ‣ Collaboration with Apple ‣ Java, Tomcat, MySQL MediaFlow - MediaFlowProxy
  37. 37. ‣ Interface between MFP and network encoders ‣ Collaboration between Stanford and Telestream ‣ Objective C, C++, C MediaFlow - StreamGrabber
  38. 38. ‣ H.264, MP4 wrapper ‣ Three different video “types” ‣ Playable on computer, mobile devices ‣ Output all Open and proprietary formats simultaneously (WebM, Theora) MediaFlow - Video Output
  39. 39. Content Page
  40. 40. MediaFlow - Media Asset Management ‣ Automated ingestion of assets ‣ Automated tagging of assets ‣ Multiple levels of categorization ‣ All metadata “lives with” asset
  41. 41. Maestro Design Process
  42. 42. Designing Maestro ‣ Use cases ‣ Flow diagrams ‣ UI wireframes (whiteboard, Omnigraffle) ‣ Iterations based on feedback from users
  43. 43. Maestro QA ‣ Team of four student QA Testers ‣ Developed test cases based on specifications ‣ Tested every test case on new features ‣ Fogbugz for case tracking ‣ Google Doc for test cases
  44. 44. ‣ Plan for obsolescence ‣ Decoupled systems ‣ Vibrant lecture capture community ‣ Long term relationship Lessons Learned
  45. 45. What’s Next ‣ Open Source all code/documentation ‣ Provide lessons learned to community ‣ Provide policies ‣ Planning version 2.0

×