Events with dcterms:created field can't have start date/time edited

Steps to reproduce

Create an event/recording which has the dcterm:created element using the rest endpoint POST /recordings/

<?xml version="1.0" encoding="UTF-8"?>
<dublincore xmlns="http://www.opencastproject.org/xsd/1.0/dublincore/" xmlns:dcterms="http://purl.org/dc/terms/">
<dcterms:temporal>start=2016-05-13T15:00:00Z; end=2016-05-13T15:55:00Z; scheme=W3C-DTF;</dcterms:temporal>
<dcterms:title>MATH1234</dcterms:title>
<dcterms:created>2016-05-12T15:00:00Z</dcterms:created>
<dcterms:spatial>dummy</dcterms:spatial>
</dublincore>

#Capture Agent specific data
event.title=MATH1234
event.location=dummy
capture.device.id=dummy

In the Admin UI edit the start date/time and update the recording.
In the recordings the start date/time is unchanged.

Inspect workflow:

  • the workflow start/end datetime are correct

  • but the mediapackage start datetime is not updated

Check the recording:

  • GET /recordings/{id}.xml shows that the recordings itself has been updated.

For some reason the mediapackages start datetime is not being updated if the recordings has a created field set.

Activity

Show:
James Perrin
March 1, 2016, 3:50 PM

Added tests.

Just need to check whether this needs applying to 2.x

James Perrin
March 23, 2016, 2:55 PM

Looks like in 2.x that schedule's created field is actually used to represent the time that the schedule(event) was made. As there is no corresponding workflow (and embrionic mediapackage) to update. I don't believe this issue exists in 2.x

James Perrin
March 23, 2016, 2:56 PM

Occurs only in 1.6.x which has been reviewed and merged, therefore resolving this ticket

Former user
March 23, 2016, 2:59 PM
Edited

James, do you mean the "temporal" field is not referenced when scheduling/updating a recording request via the Scheduling endpoint in 2.x? Ah, I just re-read your post. The catalog exists, but no workflow/mp update step. (Hoping people can still modify the created date or some other date to represent the symbolic "starting time". i.e. instructors re-post past recordings to fill in future class times, so the republish's "start time" is the future class time. That's a use case to manipulate the "Presentation" layer metadata.)

James Perrin
March 23, 2016, 4:07 PM

Only the scheduled event exists, no workflow stub and therefore no MP and no episode catalog. So I believe the original issue has gone away.

When you edit the event's start/duration only the event's dc:temporal is changed, the dc:created field remains the same. So dc:created the schedule in 2.x means when the "booking" was made and not the event started. I don't know how dc:created is/should be treated within the episode catalog after the event has occurred.

When you upload an event (via the UI) you can't specify an event start time, it takes the upload time initially. After the wf has run you can then edit the start time (and duration). This appears to add/change the episode's dc:temporal but the dc:created remains the upload date, so again not longer the symbolic "starting time".

Assignee

James Perrin

Reporter

James Perrin

Severity

Non Functioning

Tags (folksonomy)

Fix versions

Affects versions

Priority

Major
Configure