Sergio & James,
 
I can verify that in MH1.4rc2, each time metadata is updated for a scheduled 
recording, a new dublincore/episode catalog is added to the mediapackage in the 
file system.
Interestingly, recording dublin core in the database is not duplication, it is 
updated. 

The "fix" of choosing the last  mediapackage dublincore/episode in the trim UI 
javascript seems like a good interim solution, since the layout of 
dublincore/episode in the mediapackage goes from earliest to latest. It could 
almost be a UI issue that all of the dublincore/episodes in the mediapackage 
are queried all at once by the trim UI.

>From the Un-conference, I learned that there are three sources of truth for 
>data: the solr index, the database and the file system. The database has the 
>best truth.

(Database)
http://testallinone.usask.ca:8080/recordings/41265.xml
-- Returns just the one recording dublin core from the database

(MediaPackage - reflects actual files in the filesystem)
http://testallinone.usask.ca:8080/workflow/instance/41265.xml
-- Returns links for all the items in the mediapackage including links for all 
the dublincore/episodes found in the media package.

My preference is for one dublincore/episode and one dublincore/series within 
the mediapackage. 

Aside: I noticed that the episode identifier is set immediately after creating 
the mediapackage, in SchedulerServiceImpl.addEvent(final DublinCoreCatalog 
eventCatalog) //lines 435 & 444. This means the first dublincore/episode 
catalog that is in the mediapackage does not include the identifier element. 
All subsequent dublincore/episode catalogs in the mediapackage have the 
identifier set because they get it from the recording dublincore. The recording 
dublincore is persisted to the database immediately after the episode 
identifier is set //line 448. 

- Karen

> In general it would be great if more people could talk about their QA 
> findings when piloting or otherwise test driving 1.4. 
> 
_______________________________________________
Matterhorn mailing list
Matterhorn@opencastproject.org
http://lists.opencastproject.org/mailman/listinfo/matterhorn


To unsubscribe please email
matterhorn-unsubscr...@opencastproject.org
_______________________________________________

Reply via email to