If the Episode's MediaPackage could be retrieved by episode ID (i.e. workflow id) instead of the mediapackage ID, would this problem go away? The Episode Id already comes across in the schedule event's episode.xml.

On 11/16/2012 11:32 AM, Greg Logan (Commented) (JIRA) wrote:
     [ 
http://opencast.jira.com/browse/MH-9282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=32192#comment-32192
 ]

Greg Logan commented on MH-9282:
--------------------------------

So what's the proposal here?  That we pass the mediapackage ID over in the iCal 
as well as the workflow ID?  I have no problem with this, however this will 
require some changes in both the scheduler side of things as well as the CA's 
logic.  It may also confuse some of the 3rd party CAs.  Candidate for 1.5, 
patches welcome.
Mediapackage Id not set correctly in the CAs
--------------------------------------------

                 Key: MH-9282
                 URL: http://opencast.jira.com/browse/MH-9282
             Project: Matterhorn Project
          Issue Type: Bug
          Components: Architecture & Services, Capture (Devices and Software)
    Affects Versions: 1.4, 1.3
            Reporter: Rubén Pérez Vázquez
            Assignee: Greg Logan


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
http://opencast.jira.com/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn


To unsubscribe please email
[email protected]
_______________________________________________


--

Karen Dolan
Harvard University, DCE
617-998-8439
[email protected]

_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn


To unsubscribe please email
[email protected]
_______________________________________________

Reply via email to