Steps to reproduce:
1. Upload or schedule a recording
2. Compare the time shown in the overview and in the metadata, the time in the overview should be an hour ahead of the time shown in the metadata.
Workaround (if any):
I'm able to reproduce this with 3.0. Consider we use spanish timezone (and we are in DST!)
Scheduled at 20hrs, shown that way of event list, but metadata displays 19hrs.
May I reopen? What information you need?
PS: We are creating events via REST /recordings. example:
#Capture Agent specific data
#Wed Jun 26 12:05:19 CEST 2017
<?xml version="1.0" encoding="UTF-8" standalone="no"?><dublincore xmlns="http://www.opencastproject.org/xsd/1.0/dublincore/" xmlns:dcterms="http://purl.org/dc/terms/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><dcterms:isPartOf>1234</dcterms:isPartOf><dcterms:temporal xsi:type="dctermseriod">start=2017-06-29T18:10:00Z; end=2017-06-29T18:15:00Z; scheme=W3C-DTF;</dcterms:temporal><dcterms:spatial>agent-1</dcterms:spatial><cterms:title>title</dcterms:title></dublincore>
The problem is fixed for 4.0 in develop (release December 2017), as part of a major refactoring of date and time input, that did not make it in time for 3.x
No idea if somebody is interested in writing an intermediate patch for 3.x.