@Elizabeth Fellendorf From what I was told, the only near term solution is either to have users log out/back in or run a script to delete some stuff in the user profile. For the latter, my understanding is that they are working on something, but it's not ready yet. My ticket number is 00977785 in case it is helpful. For the former, we've got this guidance out for our campus and it's been super helpful: https://teach.its.uiowa.edu/uicapture-faq#accordion-item-4636-10

We've implemented an archive policy recently and are now looking at possible options for deletion. We will only be deleting content that has been archived. It would be fantastic and much smoother for all involved if staff were able to easily flag if they wish a recording to be excluded from a deletion policy.

I would envisage a button displayed for each archived recording similar to the publish button for on-demand recordings. Labelled something like "Retain". Setting this option would ensure archived recordings were not processed by delete policies even if they matched all other criteria.

Having an email to creators stating that a recording is due for deletion would allow them time to check and apply retain flags where needed.

This would require that an audit process was re-run prior to the deletion task to make sure that any changes to retain status were included in the retention run. This second audit process could likely be a smaller task which just re-checks all archived recordings scheduled for deletion and whether there has been a change to the retain flag.

I just had an instructor ask if she could limit the number of retakes to a specific number.

Her other suggestion is related:

-If you allow multiple retakes, can they deduct some percentage for a correct answer, if the student doesn't get it on the first try. This avoids rewarding guesses.