Discuss: Event Metadata by LukasKalbertodt · Pull Request #1 · opencast/data-model

LukasKalbertodt · 2025-03-20T09:32:32Z

This discussion PR is for only event metadata.

To add new comments, go into the "files changed" tab and comment on individual lines or sections of lines. Or you can comment on existing discussion threads here. If you feel like you want to start a discussion about a broader topic (than something mainly referencing a few lines), consider open a new discussion here.

docs/event/metadata.md

JamesUoM · 2025-03-21T09:31:20Z

docs/event/metadata.md

+- `endTime: DateTime?`: Like `startTime`, but when the video recording stopped. Due to cutting, recording pauses and etc, the `duration` is not necessarily `end - start`.
+- `duration: Milliseconds` 🟦: duration of the event. As specified in ["assets"](./assets), this needs to always match the duration of all non-internal tracks.
+- `updated: Timestamp` 🟦: Timestamp of when anything about this event was last changed.
+- `created: Timestamp` 🟦: Timestamp of when the event was created in Opencast. It is set once when the event is first stored in Opencast's DB, and never changed again. This also implies that scheduled event's `created` date is when the scheduling took place, _not_ the time it is scheduled for (that would be `startDate`)


available: DateTimeRange : publication period when the event is visible to intended audience. Can be unset or open-ended.

Maybe this should be specific to each publication?

publication

No idea what you are talking about :D

But yeah I guess this available is related to the lifecycle management? Did not consider anything there. Will think about it and also talk to Arne.

mtneug

Is ETHZ still using translated metadata (e.g. metadata with a language code attached to it)? Do we want that?

docs/event/metadata.md

Since `created` and this field talk about the same event in time, they should share similarity in their name. And `ingest` is just wrong for scheduled videos.

Some fields I previously suggested were questionable in widespread usefulness so we decided to introduce them as experimental fields first. To do that, I fleshed out the `extraMetadata` section with more details.

docs/event/metadata.md

Now it doesn't imply that deleting a series with events inside is a supported operation, it just says: if it were, it needs to be updated. See #1 (comment)

Discuss: Event Metadata

6069666