Description
Over time, the page for managing a single entity (video, series, playlist) grew in scope. (Note: this issue is only about that, not about the "My *" overview table of multiple entities.) These management areas have some sub-pages, e.g. for events its "Video Details", "Access Policy", and "Technical Details". The last one caused already quite some discussion in #807, which this issue aims to replace with a more general discussion. There is also a suggestion in #946.
So I think it is clear that we still want sub-pages. Putting all features on one page is overkill I assume. To decide how to group the features into sub-pages, I think we should simply first list all features/things we want to have. And also try to think of any future additions. When grouping these into sub-pages, they should be fairly similar between videos, series and playlists. Finally, we might also consider making the grouping/layout of the video manage page similar to the uploader, since that has many of the same features (metadata, access policy). But consistency only as long as it makes sense, of course.
These are all the features (current or future) I can think of:
| Video | Uploader | Series | Playlist | |
|---|---|---|---|---|
| Metadata editor | ✓ | ✓ | ✓ | ✓ |
| Series selector | ✓ | ✓ | ||
| ACL Editor | ✓ | ✓ | ✓ | ✓ |
| Thumbnail Selector | ? | ✓ | ||
| Subtitle editor/selector | ? | ✓ | ||
| Button "Open in Editor" | ✓ | |||
| Button "Delete" | ✓ | ✓ | ✓ | |
| Button "Upload into series" | ✓ | |||
| Video Content editor | ✓ | ✓ | ||
| Some way to share | ✓ | ✓ | ✓ | |
| Link to public page¹ | ✓ | ✓ | ✓ | |
| Show dates (updated & modified) | ✓ | ✓ | ✓ | |
| Show referencing pages | ✓ | ✓ | ✓ | |
| Show whether it's unlisted | ✓ | ✓ | ✓ | |
| Show Opencast ID | ✓ | ✓ | ✓ | |
| Ability to download tracks | ✓ | |||
| Show technical details² | ✓ | ✓ | ✓ | |
| Analytics/statistics³ | ✓ | ? | ? |
¹ For videos, this is the video page (either direct link or in realm context), for series it would be the series page or the realm where the series is included.
² Like synchronization state, is_live, raw extra metadata, caption information, has slide text?, etc. This is rarely used, but sometimes useful for users. I would imagine us hiding this, like in an expandable section.
³ It's still very unclear what data we want to store.
If you can think of anything else, let me know and I will add it to the table.