Hi Ruben, > Fair enough, Tobias. You have just convinced me. A technical question, > though: with the episode service in place, would it still be needed to put > the recording "on hold"? Doesn't it appear in the list just because it has > been put into the media repository?
It will only appear in the episode service if the "archive" operation has been added to the workflow. After that you are right that you could from there on start the mediapackage with any given workflow. > The discussion here becomes, then, changing the default workflow from one > that does the full processing to another that just puts the mediapackage in > the repository. I don't see many reasons to changing it or leaving it like it > is, giving the fact that it is so easy to change the workflow triggered. > Well, supposing the inbox service is now working correctly, because the last > time I was messing with it (a while back), creating alternative inboxes with > alternative workflows didn't work, but I'm assuming this is not the case > anymore. I was always envisioning a workflow that would go on hold and then make use of the workflow's "append" method to append a selected workflow. But doing it this way seems to be a valid approach as well. Tobias _______________________________________________ Matterhorn mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn To unsubscribe please email [email protected] _______________________________________________
