Technology Scan MediaMosa – Matterhorn Connecting Matterhorn and MediaMosa
•Transferir como KEY, PDF•
1 gostou•383 visualizações
Technology Scan MediaMosa – Matterhorn Connecting Matterhorn and MediaMosa. Presentation by Frans Ward and Wladimir Mufty, SURFnet Event: March 29-31, 2011: MediaMosa and TF-Media conference 'MediaMosa, weblectures & open video'.
Recomendados
Recomendados
Mais conteúdo relacionado
Destaque
Semelhante a Technology Scan MediaMosa – Matterhorn Connecting Matterhorn and MediaMosa
Semelhante a Technology Scan MediaMosa – Matterhorn Connecting Matterhorn and MediaMosa (20)
Mais de MediaMosa
Mais de MediaMosa (20)
Último
Último (20)
Technology Scan MediaMosa – Matterhorn Connecting Matterhorn and MediaMosa
- 1. Frans Ward Wladimir Mufty Technical Product Manager SURFnet Advanced Services Frans.Ward@surfnet.nl Technology Scan MediaMosa – Matterhorn Connecting Matterhorn and MediaMosa 4th TF-Media meeting - March 30, 2011 Utrecht, Netherlands - SURFnet. We make innovation work `
- 2. OVERVIEW 15 min. (Frans) MediaMosa and Opencast Matterhorn. How do they compare? And can they co-act? 15 min. (Wladimir) Technology Scouting project MediaMosa - Matterhorn and Demo. 15 min. Questions 4th TF-Media meeting - March 30, 2011 Utrecht, Netherlands - SURFnet. We make innovation work
- 3. MEDIAMOSA TECHNOLOGY SCOUTING PROJECTS 4th TF-Media meeting - March 30, 2011 Utrecht, Netherlands - SURFnet. We make innovation work
- 4. MEDIAMOSA TECHNOLOGY SCOUTING PROJECTS 4th TF-Media meeting - March 30, 2011 Utrecht, Netherlands - SURFnet. We make innovation work
- 5. THIS TECHNOLOGY SCAN ANSWERS THE QUESTION “Can Matterhorn be used to record lectures in such a way that these web lecture recordings are saved in MediaMosa automatically so that they can be accessed via an end-user application such as SURFmedia?” 4th TF-Media meeting - March 30, 2011 Utrecht, Netherlands - SURFnet. We make innovation work
- 6. THIS TECHNOLOGY SCAN ANSWERS THE QUESTION “What changes would need to be made to MediaMosa so that Matterhorn can be used with MediaMosa in this way?” 4th TF-Media meeting - March 30, 2011 Utrecht, Netherlands - SURFnet. We make innovation work
- 7. THE IDEA 4th TF-Media meeting - March 30, 2011 Utrecht, Netherlands - SURFnet. We make innovation work
- 8. THE TECHNOLOGY SCOUTING PROJECT ! 4th TF-Media meeting - March 30, 2011 Utrecht, Netherlands - SURFnet. We make innovation work
- 9. THE BIG PICTURE 4th TF-Media meeting - March 30, 2011 Utrecht, Netherlands - SURFnet. We make innovation work
- 10. THE BIG PICTURE In order to connect Opencast to MediaMosa, Opencast provides two delivery methods: 1. Delivery workflow; 2. Search API. 4th TF-Media meeting - March 30, 2011 Utrecht, Netherlands - SURFnet. We make innovation work
- 11. MediaMosa has three receiving THE BIG PICTURE methods: 1. REST interface with DBUS authentication; 2. FTP bulk upload; 3. AtomPub API. 4th TF-Media meeting - March 30, 2011 Utrecht, Netherlands - SURFnet. We make innovation work
- 12. SETUP MATTERHORN RECORDING @SURFNET 4th TF-Media meeting - March 30, 2011 Utrecht, Netherlands - SURFnet. We make innovation work
- 13. SETUP MATTERHORN RECORDING @SURFNET 4th TF-Media meeting - March 30, 2011 Utrecht, Netherlands - SURFnet. We make innovation work
- 14. FACTS & FIGURES Opencast Matterhorn MediaMosa Version 1.0 July 2008 Version 1.0 July 2010 Version 1.6 July 2009 Version 1.1 April 2011 (Start Open Source Community) Version 2.0 July 2011/2012 Version 2.3.8 March 2011 Annual: 2 major releases - 3.0 June 2011 - 3.1 december 2011 Community first, Product first, product later Community later Educational Community GPLv2 License, Version 2.0 4th TF-Media meeting - March 30, 2011 Utrecht, Netherlands - SURFnet. We make innovation work
- 15. OPEN SOURCE LICENCES Opencast Matterhorn MediaMosa Educational Community GPLv2 License, Version 2.0 4th TF-Media meeting - March 30, 2011 Utrecht, Netherlands - SURFnet. We make innovation work
- 16. OPEN SOURCE LICENCES Opencast Matterhorn MediaMosa Educational Community GPLv2 License, Version 2.0 Philosophy To allow the maximum use of our software for any purpose and by all people. 4th TF-Media meeting - March 30, 2011 Utrecht, Netherlands - SURFnet. We make innovation work
- 17. OPEN SOURCE LICENCES Opencast Matterhorn MediaMosa Educational Community GPLv2 License, Version 2.0 Philosophy All direct development is To allow the maximum contributed back and use of our software for remain under the same any purpose and by all license. people. This limits commercial adoption 4th TF-Media meeting - March 30, 2011 Utrecht, Netherlands - SURFnet. We make innovation work
- 18. OPEN SOURCE LICENCES Opencast Matterhorn MediaMosa Educational Community GPLv2 License, Version 2.0 Philosophy All direct development is To allow the maximum contributed back and use of our software for remain under the same any purpose and by all COMPATIBLE NOT license. people. This limits commercial adoption 4th TF-Media meeting - March 30, 2011 Utrecht, Netherlands - SURFnet. We make innovation work
- 19. TECHNOLOGY Opencast Matterhorn MediaMosa JAVA MediaMosa 1.x: Drupal 6 OSGi MediaMosa 2.x: Drupal 7 Linux/Debian/Ubuntu/Redhat PHP MySQL FFMpeg FFMpeg REST services REST communication between frond-end and back-end system 4th TF-Media meeting - March 30, 2011 Utrecht, Netherlands - SURFnet. We make innovation work
- 20. 4th TF-Media meeting - March 30, 2011 Utrecht, Netherlands - SURFnet. We make innovation work
- 21. 4th TF-Media meeting - March 30, 2011 Utrecht, Netherlands - SURFnet. We make innovation work
- 22. 4th TF-Media meeting - March 30, 2011 Utrecht, Netherlands - SURFnet. We make innovation work
- 23. 4th TF-Media meeting - March 30, 2011 Utrecht, Netherlands - SURFnet. We make innovation work
- 24. MEDIAMOSA INNOVATION PROJECT 4th TF-Media meeting - March 30, 2011 Utrecht, Netherlands - SURFnet. We make innovation work
- 25. CONCLUSIONS Various steps need to be taken in order to get Matterhorn to operate in conjunction with MediaMosa in the desired manner, with Matterhorn utilising the delivery workflow and MediaMosa utilising the AtomPub API 4th TF-Media meeting - March 30, 2011 Utrecht, Netherlands - SURFnet. We make innovation work
- 26. CONCLUSIONS The necessary steps for Matterhorn are: 1. Programming a delivery workflow in Java; 2. Uploading to MediaMosa by means of the extended AtomPub specification. POST /media Items/USER-ID/@self; 3. Authenticating Matterhorn users with oAuth. 4th TF-Media meeting - March 30, 2011 Utrecht, Netherlands - SURFnet. We make innovation work
- 27. CONCLUSIONS For MediaMosa, the steps are: 1. Creating a REST interface for the AtomPub specification; 2. Making it possible to authenticate users with oAuth. MediaMosa 3.0 release will incorporate these recommendations 4th TF-Media meeting - March 30, 2011 Utrecht, Netherlands - SURFnet. We make innovation work
- 28. MEDIAMOSA INNOVATION PROJECTS IN 2011 Weblecturing pilot with the University of Groningen (RUG) 4th TF-Media meeting - March 30, 2011 Utrecht, Netherlands - SURFnet. We make innovation work
Notas do Editor
- \n
- \n
- \n
- \n
- \n
- \n
- Phase 1: Investigation of Matterhorn and definition of use cases.\nInstallation of a Matterhorn platform consisting of a “Capture Agent” (component:\nMatterhorn Lecture Capture and Administration) and a “Matterhorn Server”\n(components: Matterhorn Ingest and Processing, Matterhorn Distribution Management,\nand Matterhorn Engage Tools).\nThis phase involved investigating how Matterhorn operates. Test recordings were made,\nand this phase formed the basis for the other two phases. During this phase,\nMatterhorn was standalone and not connected to MediaMosa.\n\nPhase 2: Connecting Matterhorn to MediaMosa (partial functionality).\nThis phase involved determining the extent to which the Matterhorn workflows could be\nadapted so as to upload the recordings to MediaMosa. Two MediaMosa inputs were\nexamined: the FTP bulk upload and the direct REST interface.\n9\nThe basic principle for this set-up was that existing Matterhorn functionality should be\nused and that no changes needed to be made for this connection (apart from the\nadapted workflows). Changes were expected to be necessary for MediaMosa, however.\nThis has to do with the authentication process between an EGA and the MediaMosa\nbackend. At the moment, a “trust relationship” is necessary on the basis of the DBUS\nprotocol, but that is unnecessary for open, non-protected content. Another change was\nexpected to be necessary to the mechanism for the play tickets when retrieving (or\nplaying) content. The use of open, non-protected content would be easier if static URLs\ncould be used for this rather than a play proxy and temporary URLs.\n\nPhase 3: Connecting Matterhorn to MediaMosa (full functionality).\nContinuing on from phase 2, it is possible in phase 3 to deploy the entire functionality\nof Matterhorn in combination with MediaMosa. In fact, the backend of Matterhorn is\nreplaced here by MediaMosa. This has the advantages of greater flexibility and the fact\nthat one is not dependent on SURFmedia to play the content. In order to achieve this,\nchanges need to be made to MediaMosa. This is because authentication now takes place\nvia a DBUS trust relationship with an EGA that utilises a ticket mechanism to determine\nwhether a user is authorised to view the media. In this set-up with Matterhorn, there is\nno question of a trust relationship with MediaMosa and authentication will need to take\nplace entirely at web service level.\n\n
- In order to connect Opencast to MediaMosa, Opencast provides two delivery methods:\n1. Delivery workflow;\n2. Search API.\n\nMediaMosa has three receiving methods:\n1. REST interface with DBUS authentication;\n2. FTP bulk upload;\n3. AtomPub API.\n
- \n\nMediaMosa has three receiving methods:\n1. REST interface with DBUS authentication;\n2. FTP bulk upload;\n3. AtomPub API.\n
- \n
- \n
- \n
- \n
- VirtPresenter: Universität Osnabrück (http://www.virtpresenter.org/)\nReplay: ETH Zurich (https://www1.ethz.ch/replay/)\nRe-Collect: University of Saskatchewan, Canada ()\nPuMuKit: Universidad de Vigo. Spain (http://wiki.media.uvigo.es/display/PuMuKIT/PuMuKIT+Project+Home)\n
- \n
- \n
- \n
- \n
- Apache License Philosophy:\nTo allow the maximum use of our software for any purpose and by all people\n\nGPL Philosophy:\nDerivative works remain under the license. Linked works may also remain under the license. Ensures all ‘down stream’ have the same rights GPL. All direct development is contributed back. Contributors assured code remains open source. Encourages a full free software economy. Copyright holder retains much control. Limits commercial adoption. Dual-license business strategy\n\n
- Apache License Philosophy:\nTo allow the maximum use of our software for any purpose and by all people\n\nGPL Philosophy:\nDerivative works remain under the license. Linked works may also remain under the license. Ensures all ‘down stream’ have the same rights GPL. All direct development is contributed back. Contributors assured code remains open source. Encourages a full free software economy. Copyright holder retains much control. Limits commercial adoption. Dual-license business strategy\n\n
- Apache License Philosophy:\nTo allow the maximum use of our software for any purpose and by all people\n\nGPL Philosophy:\nDerivative works remain under the license. Linked works may also remain under the license. Ensures all ‘down stream’ have the same rights GPL. All direct development is contributed back. Contributors assured code remains open source. Encourages a full free software economy. Copyright holder retains much control. Limits commercial adoption. Dual-license business strategy\n\n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- Conclusion\nVarious steps need to be taken in order to get Matterhorn to operate in conjunction with\nMediaMosa in the desired manner, with Matterhorn utilising the delivery workflow and\nMediaMosa utilising the AtomPub API.\n6\nThe necessary steps for Matterhorn are:\n1. Programming a delivery workflow in Java;\n2. Uploading to MediaMosa by means of the extended AtomPub specification.\na. POST /media Items/USER-ID/@self;\n3. Authenticating Matterhorn users with oAuth.\nFor MediaMosa, the steps are:\n1. Creating a REST interface for the AtomPub specification;\n2. Making it possible to authenticate users with oAuth.\n
- Conclusion\nVarious steps need to be taken in order to get Matterhorn to operate in conjunction with\nMediaMosa in the desired manner, with Matterhorn utilising the delivery workflow and\nMediaMosa utilising the AtomPub API.\n6\nThe necessary steps for Matterhorn are:\n1. Programming a delivery workflow in Java;\n2. Uploading to MediaMosa by means of the extended AtomPub specification.\na. POST /media Items/USER-ID/@self;\n3. Authenticating Matterhorn users with oAuth.\nFor MediaMosa, the steps are:\n1. Creating a REST interface for the AtomPub specification;\n2. Making it possible to authenticate users with oAuth.\n
- Conclusion\nVarious steps need to be taken in order to get Matterhorn to operate in conjunction with\nMediaMosa in the desired manner, with Matterhorn utilising the delivery workflow and\nMediaMosa utilising the AtomPub API.\n6\nThe necessary steps for Matterhorn are:\n1. Programming a delivery workflow in Java;\n2. Uploading to MediaMosa by means of the extended AtomPub specification.\na. POST /media Items/USER-ID/@self;\n3. Authenticating Matterhorn users with oAuth.\nFor MediaMosa, the steps are:\n1. Creating a REST interface for the AtomPub specification;\n2. Making it possible to authenticate users with oAuth.\n
- Conclusion\nVarious steps need to be taken in order to get Matterhorn to operate in conjunction with\nMediaMosa in the desired manner, with Matterhorn utilising the delivery workflow and\nMediaMosa utilising the AtomPub API.\n6\nThe necessary steps for Matterhorn are:\n1. Programming a delivery workflow in Java;\n2. Uploading to MediaMosa by means of the extended AtomPub specification.\na. POST /media Items/USER-ID/@self;\n3. Authenticating Matterhorn users with oAuth.\nFor MediaMosa, the steps are:\n1. Creating a REST interface for the AtomPub specification;\n2. Making it possible to authenticate users with oAuth.\n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n