Hi Rubén, thanks for pointing out that there is now a working patch that is adding adding functionality also covered by the media package converter. As you know, that patch had been rolled back a couple of times because it broke ingest for regular mediapackages and it was unclear whether it would make it into 1.4 or not.
Regardless of that patch, the media package converter solves a couple of other issues and most importantly provides the ability to create a mediapackage from scratch, just given the track and catalog files, so I am sure some community members may still find it helpful. Tobias On 14.12.2012, at 19:02, Rubén Pérez <[email protected]> wrote: > I'm repeating the answer I wrote for the "community" list. (sorry about that, > but I consider that the fact that MH 1.4 is compatible with 1.3 Mediapackages > is important to point out). > > Hello, > > I just wanted to clarify that Matterhorn 1.4 does understand pre-1.4 > MediaPackages. The relevant JIRA task is: MH-9256, and the fix was committed > to the 1.4.x branch on November 29 (already 15 days ago). This fix comes from > the decision made by the developers that Matterhorn should keep backwards > compatibility within reasonable, both between interfaces and between data > structures, from one version to the following(s). Since many adopters are > already using Matterhorn in large scale deployments, this commitment to keep > compatibility between versions helps to smooth the upgrading process, which > has traditionally been one of Matterhorn biggest issues. > > Therefore, the statement "Because of this a media package from a previous > release can’t be ingested directly into 1.4 without fixing the manifest." (in > both the email and Entwine's blog) is no longer accurate. You can rest > assured that 1.3 (and before) mediapackages get correctly ingested in the > system. > > That being said, I'd also like to take the opportunity to congratulate > Entwine for this useful tool. Even though the manifest incompatibility is > already sorted out, this MpConverter offers an very easy and intuitive way of > creating a new MediaPackage, in addition of fixing date formats in the > DublinCore catalogs. > > Best regards > Rubén > > Rubén Pérez > TELTEK Video Research > www.teltek.es > > > > 2012/12/14 Jeff Austin <[email protected]> > Hello, > > Apologies for the cross post. I want to make sure everyone sees this. > > The soon to be released Matterhorn 1.4.x fixes a major bug with namespaces in > XML documents. See Opencast ticket MH-8958 for details. > > Because of this a media package from a previous release can’t be ingested > directly into 1.4 without fixing the manifest. The MpConverter remedies this > situation and in addition allows for building 1.4 compliant media packages > from scratch, i.e. from media files, metadata catalogs and attachments. It is > a command line tool that runs without interaction when applied to packages > with a manifest and provides an interactive editing shell when building a new > package from content files. > > Read more about the Matterhorn MediaPackage Converter here: > http://entwinemedia.com/2012/matterhorn-mediapackage-converter/ > > Feel free to comment if you have questions about the tool or would like to > learn more about the work that Entwine is doing. > > Thanks for reading, > > Jeff Austin > Project Manager > Entwine > +1 612.803.7330 > > > _______________________________________________ > Matterhorn-users mailing list > [email protected] > http://lists.opencastproject.org/mailman/listinfo/matterhorn-users > > > _______________________________________________ > Matterhorn-users mailing list > [email protected] > http://lists.opencastproject.org/mailman/listinfo/matterhorn-users _______________________________________________ Matterhorn-users mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
