When a user chooses to save a video somewhere, they expect to find it there. I for one definitely don't want the expected functionality be to place it somewhere to start, it moves somewhere else at some point in the process, then I have to go copy it back to the original location if I want to retain access to it (which the Panopto guide for this in other LMSs suggests).

Taking a step back, it also just objectively isn't what I was asking for in the feature request. I was specifically asking for the LTI 1.3 "homework_submission" placement so it was an end-to-end solution, not this roundabout thing repurposing the RCE placement. If there is a better and more controlled way of handling the user interaction…why not start moving in that direction? When we had Kaltura, we had issues with their homework submission workflow. It copied things around behind the scenes and orphaned media like this does and it just ended up confusing people. If the process was structured and purpose built for just submitting homework and the "where" was out of the user's control/view (if they were never given the option to save the video somewhere specific), I would have no real issues here.

My last major problem with this solution is that it saves everything into a single folder for the course. We have some courses that have hundreds of students which would be submitting videos for multiple different assignments. This just isn't going to work for them, and if I turn this option on for our site, there is no way to keep it from merging things together if I'm reading the documentation correctly.

Most users will be fine with how this works, sure, but that was true of what we had before. If I turn this on, workflows that worked well for users previously will no longer function if I'm reading things correctly.

I am not sure who the correct person to take this up at Panopto would be, but this shouldn't have been marked as completed. The feature that was rolled out with v.15 did not accomplish the goal of making the submission process any easier, in fact, I think it made it made the whole process a lot less clear for the students and for the instructors.

As always, I am happy to chat more about this if there is someone at Panopto that wants to hear the feedback.

The Canvas Assignment Tool workflow for submitting a Panopto video should be smoother. When an instructor creates their first Panopto (give me a video) type Assignment, that action should create the Assignment Folder in the course if it does not already exist. Additionally all students who submit videos to this assignment should never have to search for where to save their video submissions. It should be saved into the assignment folder where the teachers can view it, but other students cannot automatically view it.  If every time a student in Canvas submitted a WORD or PDF file assignment, they had to also use pulldown menus and find a specific folder to save it to, it would be a support nightmare. A Panopto Video submission Assignment in Canvas should work as seamlessly as a Canvas File submission Assignment.

This is a really good idea. I believe in MS Teams there is a way to view a slide deck like this: a presenter can be on a certain slide, and a participant can click through slides as well at their own pace.

When I saw this on my own windows PC I assumed it was a fluke. I am very sorry that we've deployed this to SCCM. This is huge fail; I hope they can fix it before things ramp up for Fall semester.

At a minimum, it seems like this should be settable via the API.

I am also interested in this feature as we are considering moving a large amount of sessions from archive to regular storage and, unless I'm missing something, there's no programmatic way to do so.

Just realised that this feature request has over 700 views.
Could be lots of people checking to see if oEmbed is getting added as a feature

Currently, academics must manually close the video assignment folders when the assignment deadline passes to prevent students from making changes or adding new submissions. This requires academics to be available at the exact deadline time, which can be challenging if they are teaching, in meetings, or otherwise engaged.

I would like to propose introducing a feature that allows academics to schedule the closure of assignment folders in advance. This would enable them to set a specific date and time for the folder to automatically close. This feature would ensure a seamless and consistent process for managing assignment deadlines, reduce administrative burden, and mitigate the risk of students modifying submissions after the deadline.