Well... that was not my point. Well, my point is to write down what mediapackage should contain. Right now, it's: 1. episode/dublincore 2. series/dublincore 3. tracks - as many as you want, but at least one.
Other than this - ID's and MD5 sums are optional, and that I will write down a proposal for the commiters to approve by the end of this week (and since this Friday it is the last day of school here, I may be busy - so end of the week includes weekend). I love the proposal of making series/dublincore optional in few cases, and I think server should decide how to enrich / alter mediapackage when it is ingested rather than forcing overwriting the data - however overwriting is one way of handling it. Best Regards -Pawel --- On Wed, 6/20/12, Tobias Wunden <[email protected]> wrote: > > The mediapackage already is completely universal, you can > attach anything to it, including catalogs that contain > YouTube or Videolecture.net specific information. It just > happened that we decided to have our own scheduling system > create dublin core catalogs, but you can easily implement > your own. Just make sure that in this case you implement a > MediapackageMetadataProvider implementation that is able to > provide a subset of metadata to the mediapackage (see that > interface for more details, it's essentially the title, the > series and some other things). > _______________________________________________ Matterhorn mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn To unsubscribe please email [email protected] _______________________________________________
