I did a webinar with Kaltura yesterday where I spoke about lessons learned from our (“successful”) deployment of Kaltura at OSU. I put “successful” in quotes only because it took some time to get to the point where we are today. We’ve been with Kaltura for 6 years and we’re very satisfied with the product today, but in the earliest days, it was certainly a difficult implementation. Both Kaltura and OSU grew in those intervening years, though, and Kaltura today is not what Kaltura was 6 years ago. The product’s implementation is turn-key and simple. I keep coming back to the words “integral”, “transparent”, and “ubiquitous” when I talk about Kaltura. Oftentimes, Kaltura is going exist invisibly behind the scenes. If it does its job, your interaction with Kaltura should be minimal. It’s job is to gobble up video and spit out video, and it does both those things wonderfully.

Recently when meeting with faculty and staff at OSU, and with people outside of OSU, I’ve refrained from going into the weeds when talking about Kaltura. If I try to touch on all the functionality, I’ll be talking for hours and I’ll surely lose my audience. Someone who wants to know about lecture capture doesn’t want to know about live streaming, for instance. Instead, what I often do when I walk into a room is go immediately to the whiteboard and draw a big cloud (“Kaltura”) and put a bunch of arrows going into that cloud on one side, and a bunch of arrows coming out of that cloud on the other side. That’s translated more recently into this Prezi I’ve made that I shared during yesterday’s webinar and you can see here.

ecosystem

Print Friendly, PDF & Email

Leave a reply

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong> 

required

*