Discuss: Event Metadata #1
Open
+112
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
JamesUoM
reviewed
Mar 21, 2025
JamesUoM
reviewed
Mar 21, 2025
JamesUoM
reviewed
Mar 21, 2025
JamesUoM
reviewed
Mar 21, 2025
JamesUoM
reviewed
Mar 21, 2025
docs/event/metadata.md
Outdated
| - `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`) |
There was a problem hiding this comment.
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?
Member
Author
There was a problem hiding this comment.
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
reviewed
Apr 1, 2025
Member
mtneug
left a comment
mtneug
left a comment
There was a problem hiding this comment.
Is ETHZ still using translated metadata (e.g. metadata with a language code attached to it)? Do we want that?
LukasKalbertodt
commented
Apr 2, 2025
snoesberger
reviewed
Apr 4, 2025
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.
mtneug
reviewed
May 15, 2025
This was referenced Feb 4, 2026
Open
Open
LukasKalbertodt
added a commit
that referenced
this pull request
Feb 9, 2026
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)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.