Adam, > I thought mediapackages can be extracted from the workflow and engage search > service (and searchable by mp id)? If so, how is this different?
the mediapackage is indeed accessible from workflow, but not the actual elements (catalogs, tracks) which are being stored in the working fil repository and will get "cleaned" up sooner or later. In addition, there can be multiple workflows working on the same mediapackage. Which one will you use? This is why the episode service will not only keep the mediapackage but also provide a simple api for storing the mediapackage elements, along with an intial filesystem based implementation of that "archive" api. > Since the medata is stored in a variety of services, how does the episode > service ensure that the metadata is up to date? In the current designs, metadata is only updated through workflow, and the episode service is no different. If you want to change metadata, you run a workflow. As long as there is no communication channel being established between the various services, it is up to the author of the workflows to make sure that metadata changes are being propagated as needed. > Do you have any screen shots of UI's taking advantage of this service? Not yet, the capabilities of the ui is still being discussed. It will most probably offer search capabilities similar to the current recordings screen and allow for the selection of one or more mediapackages, which can then be submitted for processing. I will post mockups or screenshots as we are making progress. Tobias _______________________________________________ Matterhorn mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn To unsubscribe please email [email protected] _______________________________________________
