Wrong recording date in media package metadata

[Matthias Neugebauer]

Hi,

we noticed that the Engage UI displays a wrong recording date. It is using the creation date of the planed episode. I had a look at the ingest implementation and I'm not sure if this should be considered a bug or not. If I understand it correctly, the date is set at the beginning of the ingest, but is overwritten when the workflow starts. There it simply copies the Dublin Core metadata including the creation date of the episode (see WorkflowServiceImpl.java:1713-1716). I'm not sure if this could be skipped or if maybe the capture agent has to supply a correct value.

Greetings,
Matthias


--
Matthias Neugebauer
e-Lectures
University of Münster
Georgskommende 25 - Room 310 - D 48143 Münster
Tel. + 49 (0) 251 - 83 29295
email: matthias....@uni-muenster.de

[Karen Dolan]

Matthias,

The Episode Dublin Core catalog has (historically) described the "event" of the recording versus the event of the processing the recording. It is not unreasonable for the ingest service to fill in missing values with reasonable defaults.
But I can see that this would lead to misleading data. Do you suggest leaving the creation date blank rather than adding a default date?

- Karen

Karen Dolan
Harvard University DCE

> --
> You received this message because you are subscribed to the Google Groups "Opencast Development" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to dev+uns...@opencast.org.

[Karen Dolan]

Karen Dolan
Harvard University DCE

> On Oct 26, 2016, at 9:34 AM, Karen Dolan <kdo...@dce.harvard.edu> wrote:
>
> Matthias,
>
> The Episode Dublin Core catalog has (historically) described the "event" of the recording versus the event of the processing the recording. It is not unreasonable for the ingest service to fill in missing values with reasonable defaults.
> But I can see that this would lead to misleading data. Do you suggest leaving the creation date blank rather than adding a default date?

For the cases where the capture agent doesn't pass that data in the catalog. Are capture agents not getting episode/event catalogs from the MH scheduling service any more?

[Matthias Neugebauer]

I'm not yet very familiar with the Opencast code base so I may have understood it wrong. But what I can observe is that the recording date is set to the date when the event was created. So for instance we scheduled a series of recordings at 2016-10-11. Now lets say one recording took place at 2016-10-12. But after the ingest the recording date of the created media package is set to 2016-10-11. When debugging this I found the mentioned lines of code where the date is copied from the event (not sure about the terminology; is event = episode). Before that in IngestServiceImpl.java:647 an initial date is set for the new media package which will later be overwritten. There the day will be correct, but not the hour. I simply suggest to set it to the actual recording time.

I hope this could clarify the problem.

Matthias