Hi Rute, > We need to be able to distribute media for streaming and we need to be > able to archive and retract if needed. So you are saying that there is no > solution for this currently?
Fortunately there is one. If you set tags the right way everything's fine. An example: Place the tagging workflow operation handler as first operation and tag everything in the freshly ingested media package with "archive". Then tag only the results of the download encodings as "archive" but not the streaming ones. Then configure the archive operation to archive everything tagged "archive". > A question related to this: is it required that > getDistributedUri(mediaPackageId, element) and element.getURI() be always > the same? Why can't an element have an URI that is known by Matterhorn (local > path or http://) and another known by the distribution server (i.e. media > server, rtmp://), assuming they both refer to the same location on disk, so > that when an element is archived or retracted, the first one is used and when > that element is served, the second one is used? Quite a while ago it has been proposed to introduce a new element type that describes distributions. But I don't know the status of this. The current situation definitely needs a solution and your suggestion should be considered. -c > > Thanks, > > Rute Santos > > > > _______________________________________________ > Matterhorn mailing list > [email protected] > http://lists.opencastproject.org/mailman/listinfo/matterhorn > > > To unsubscribe please email > [email protected] > _______________________________________________ _______________________________________________ Matterhorn mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn To unsubscribe please email [email protected] _______________________________________________
