-
Notifications
You must be signed in to change notification settings - Fork 231
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Playlist allows multiple entries of the same event #5737
Comments
👍 for specifying that clearly! Thinking about use cases for having a video in a playlist multiple times:
From these, the "home workout" one seems most convincing to me, the others are rather far fetched I feel. Your point of getting an error/warning when adding a video to a playlist twice is good I think: certainly with song playlists, I usually don't want to add a song multiple times, and was happy about my music service telling me "the song is already in the playlist". That service gave me the option to add it anyway though! So I think I'm slightly leaning to "allow multiple times in playlist", because:
|
In our internal discussion, we came to the conclusion that we don't have any specific use case in Stud.IP for multiple entries of the same video. Therefore, we would not provide this function for users, but the restrictions in the database should still be removed and the display should be possible. Related issue: elan-ev/studip-opencast-plugin#965. |
The implemented playlists API allows to add an event multiple times to a playlist. In the Stud.IP Opencast Plugin, multiple occurrences are not yet supported in the existing playlists. I think we should find a common solution to avoid incompatibilities between systems like Stud.IP and Tobira. So we should not allow multiple occurrences if we really do not need them. If I see correctly, youtube videos can only be added to a playlist once. If we have no restriction, users might lose track of large playlists and unintentionally add a video to a playlist multiple times.
In general, we should consider whether there are any use cases.
The text was updated successfully, but these errors were encountered: