Hi Pawel, > BTW (off topic): > Talking to people, how they use MH is very interesting, and it is a > different topic, but: haven't you thought about performing operations > on already ingested Media Package? I can understand it's just publish > & forget, but - how about retracting if something needs to be > altered, or licensed? Trimming recording after publishing? How it is
We would like to use the episode service I think. We don't have high demand for it right now (once the media goes in and gets processed once we're pretty much done with it), but we did run into a few issues where we wanted to export media. We wrote some methods to do this (a gstreamer workflow operation), and tying that into the episode service should be fairly easy. Akm: It seems that instead of reingesting the media package into an inbox that had "hold for export", we could potentially just go to the episode service and run it there, right? The only rub in this case is that we don't keep CA media packages on disk, since we would need several terabytes of high speed disk space sitting around to do this. > Other than this, we have come up with some workflows like: > "Delete episode from the hard drive", > "Fix the episode", > "Split episode into presenter & presentation", > "Combine into one stream" - reverse to the previous one. > > Well, and they all appear there on upload page. Your discussion of what workflows an instructor might want to start is really interesting, and it brings in the issue of access control. Just to probe further, has anyone started to consider how workflows could be tied to access control lists? It would be great to give instructors the ability to run a limited set of workflows, or workflows with a limited set of parameters (e.g. you can distribute media, but the distribution endpoint is set, or you can edit metadata, but only certain keys). Outside of the scope of what you're talking about I think, but related. > > 3. What is the data type of <tags>? Is it > > NMTOKEN? (A space separated > > list of values?) Or multiple <tag> > > children? I would like to see how > > the tags "pre-conference" and "unconference streams" would > > be handled > > by the back end. > > NMTOKEN. > First of all, those tags will not be visible to end user, so there > will be no special characters. I do not see a need for multiple <tag> > children. Ok, this means that workflow ids MUST NOT have spaces in them, or they won't work here. An important side effect of this method of implementation. (So the workflow with id "unconference streams" wouldn't work). Otherwise this looks fine to me, I'd be +0 since I support it but can't add development towards it, Chris -- Christopher Brooks, BSc, MSc ARIES Laboratory, University of Saskatchewan Web: http://www.cs.usask.ca/~cab938 Phone: 1.306.966.1442 Mail: Advanced Research in Intelligent Educational Systems Laboratory Department of Computer Science University of Saskatchewan 176 Thorvaldson Building 110 Science Place Saskatoon, SK S7N 5C9 _______________________________________________ Matterhorn mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn To unsubscribe please email [email protected] _______________________________________________
