One part of the issue (https://opencast.jira.com/browse/MH-9438) has been fixed.
Christoph Am 13.02.2013 um 19:11 schrieb Judy Stern <jlst...@berkeley.edu>: > And maybe this is too obvious to mention here (or maybe irrelevant), but we > still have different metadata fields available for editing in the Trim/Review > UI than are in Schedule/Upload/Edit > (http://opencast.jira.com/browse/MH-8776), which are still different from the > Archive editor. Talk about confusing! > Is there an explanation for why we can't have a single editor that is called > in all places in which metadata needs to be edited? > > Judy > > On Feb 11, 2013, at 3:13 PM, Tobias Wunden wrote: > >> Hi Karen, >> >> this analysis is extremely helpful and clearly shows that a lot of work is >> left on the metadata side of things. Thanks as well for opening the >> corresponding ticket. We'll need to check that we get to consistent metadata >> handling in these places: >> >> - scheduling ui >> - mediapackage editor in the archive >> >> Best, >> Tobias >> >> On 10.02.2013, at 21:37, Karen Dolan <kdo...@dce.harvard.edu> wrote: >> >>> >>> On Feb 10, 2013, at 1:23 PM, Karen Dolan <kdo...@dce.harvard.edu> wrote: >>> >>>>> One of the problems that caused us to notice the problem was that some >>>>> recordings had more complete data in our RSS feeds than others. It >>>>> appears that the more recent dc flies contain less data with successive >>>>> edits, for example we found that <dcterms:created> was one of the first >>>>> fields to disappear after an edit. So you might have to start with the >>>>> newest file and then look back across older files for some of the fields, >>>>> something of a pain in the arse. >>>> >>>> It might be data loss from the Edit UI form. >>> >>> Sorry, I meant the oc.scheduler.js file. >>> If data loss is a problem with the UI, using Vaadin here might keep the >>> dublin core model unified with the MH server. To consider for 1.5+ >>> >>> MH oc.scheduler.js >>> --------- -------------------- >>> abstract >>> accessRights >>> available >>> contributor (1.1) key: 'contributor' >>> coverage (1.1) >>> created >>> creator (1.1) key: 'creator' >>> date (1.1) >>> description (1.1) key: 'description' >>> extent >>> format (1.1) >>> identifier (1.1) key: 'identifier' >>> isPartOf key: 'isPartOf', >>> isReferencedBy >>> isReplacedBy >>> language (1.1) key: 'language' >>> license >>> publisher (1.1) >>> relation (1.1) >>> replaces >>> rights (1.1) >>> rightsHolder >>> source (1.1) >>> spatial key: 'spatial', >>> subject (1.1) key: 'subject' >>> temporal key: 'temporal', >>> title (1.1) key: 'title', >>> type (1.1) >>> >>> _______________________________________________ >>> Matterhorn mailing list >>> Matterhorn@opencastproject.org >>> http://lists.opencastproject.org/mailman/listinfo/matterhorn >>> >>> >>> To unsubscribe please email >>> matterhorn-unsubscr...@opencastproject.org >>> _______________________________________________ >> >> _______________________________________________ >> Matterhorn mailing list >> Matterhorn@opencastproject.org >> http://lists.opencastproject.org/mailman/listinfo/matterhorn >> >> >> To unsubscribe please email >> matterhorn-unsubscr...@opencastproject.org >> _______________________________________________ > > _______________________________________________ > Matterhorn mailing list > Matterhorn@opencastproject.org > http://lists.opencastproject.org/mailman/listinfo/matterhorn > > > To unsubscribe please email > matterhorn-unsubscr...@opencastproject.org > _______________________________________________ _______________________________________________ Matterhorn mailing list Matterhorn@opencastproject.org http://lists.opencastproject.org/mailman/listinfo/matterhorn To unsubscribe please email matterhorn-unsubscr...@opencastproject.org _______________________________________________
