WP/4a
From Steeple
[edit] 1 WP4: Encoding engine
[edit] 1.1 Configure Processing Engines (6 weeks effort, during months 4-6)
| Workpackage effort | lead | Oxford | Cam | OU | Starts | Ends |
| Total = 6 weeks | Ox | 6 | 0 | 0 | Feb 2009 | Apr 2009 |
Comments: Need to push for pilot activity as soon as possible. In some sense, we have already. So mainly needs documentation. Impact on 7a.
Think we’ve already done 4 at Oxford, not clear on its purpose. Elements of piloting outside of department here, perhaps merge in original WP5 (Program workflows) and define new WP4.
Oxford aim: Integrate Processing/encoding engine with hosting platform and provide a multi-platform easy to use method for submitting podcasts for publishing.
AKA: Prepare to build it
Consider setting up and sharing VMs to test Replay etc edit comments
The server-based encoding engine will be piloted, allowing test material to be sent by remote clients under default XML workflow scripts. Then Oxford will test that the encoded material can be transferred to simple secondary online delivery channels. The test will be conducted under simplified authorization, and will ensure that an RSS feed can be generated automatically on content creation. Oxford will research the integration of encoded material with web portal delivery, process management system and 3rd party services. Further piloting will occur outside of central services, testing the ease of ingest of materials.
The aim is to integrate a processing/encoding engine with the hosting platform and provide a multi-platform easy to use method for submitting podcasts for publishing.
Deliverable:
- Podcast site that shows publicly available test feeds.
Skills required: If we're using replay, this requires Java. If we're using PCP, this requires OSX Server skills.
