I've spent some time looking at how to extend the our dublin core catalog with metadata that is needed by the scheduler to create recurring events. Following the guide Josh made (http://opencast.jira.com/wiki/display/MH/Customizing+Dublin+Core+Catalogs) lets the document be parsed correctly but these new fields are invisible to the scheduler service where they are needed.
What is the best way to extend our implementation so that these values are available to other services that handle the DublinCoreCatalog object? Right now I'm considering just extending the DublinCore interface with the desired fields. Micah _______________________________________________ Matterhorn mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn To unsubscribe please email [email protected] _______________________________________________
