Hi Pawel, > Tobias idea that server should relay on workflow instance id - is of course > good. I also think that series metadata in mediapackage should be optional. > How do you image export of videos from other systems like > http://videolectures.net/ -- they have episodes, but Series? Their series may > not match my series on my server. > And I can imagine an option on youtube or videolectures.net - export to > Matterhorn - and you download a zip file that can be ingested directly into > Matterhorn - and MAtterhorn will enrich metadata by assinging ID and default > series for the mediapackage. > > As you can see, I would define mediapackage as something much more universal. > Hope you see my point :-) in looking at mediapackage as something more than a > part of Matterhorn (lets make it a universal standard for storing videos).
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). Tobias _______________________________________________ Matterhorn mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn To unsubscribe please email [email protected] _______________________________________________
