Created date shown on Engage instead of Start Date

[Jean-François Barthe]

Hi all,

We upgraded to Opencast 16.1.0 this Fall. We are noticing that, on the Engage Media Module, the events show the event’s “Created” date instead of the event’s “Start” date. This confuses students who expect to see class recordings by Start dates.

I would appreciate any direction on how we can have the Start date appear on the media module instead f the creation date.

Here is my etc/org.opencastproject.ui.metadata.CatalogUIAdapterFactory-episode-common.cfg:

# A Start Date property property.startDate.inputID=temporal property.startDate.outputID=startDate property.startDate.label=EVENTS.EVENTS.DETAILS.METADATA.START_DATE property.startDate.type=start_date property.startDate.readOnly=false property.startDate.required=false property.startDate.order=9 # Created property.created.inputID=created property.created.label=EVENTS.EVENTS.DETAILS.METADATA.CREATED property.created.type=date property.created.readOnly=true property.created.required=false property.created.order=15

Thanks,
JF

​

[Greg Logan]

Hi JF,

Your best bet here is going to changing the metadata itself so that the dates are the same.  Otherwise, there are two approaches:

- Modify the media module to add a new sort method, and make that the default.  The data is present in the results, at $event.dc.temporal, probably.  I say probably because it's going to depend on how your metadata is set up.

- Modify the search service itself to put the data you want in the right place(s).  You're looking for [1], which is what dehydrates the java object into something that can be sent to Opensearch.

G

1: https://github.com/opencast/opencast/blob/b4c3f1c0239f84e05beabcaa8ef856c84fee94c8/modules/search-service-api/src/main/java/org/opencastproject/search/api/SearchResult.java#L147

To unsubscribe from this group and stop receiving emails from it, send an email to users+un...@opencast.org.

[Lars Kiesow]

Hi JF,
I had a brief look at this, but cannot reproduce the issue with a
current Opencast 16 (see attached screenshot). Maybe you can check if
the issue persists for you after upgrading to Opencast 16.6?
All the best,
Lars