Note: creating this thread on behalf of OpenCraft.
One of our clients is having issues where users are consistently forgetting to submit ORA2 assessments. They upload their files and/or save their progress in the text response, but never come back to submit before the due date. We suspect it is because it’s not clear enough that their response will not be recorded unless they click “Submit”.
We would be interested to know if others have had this experience, and if there are any existing proposed changes to the ORA2 UX to help with this? Alternately, what research or changes would edX be interested in pursuing in this direction?
Ideas that we have had so far include:
- automatically marking an in-progress response as submitted once the due date passes
- allowing multiple submissions, effectively making every saved response and/or uploaded file event become the latest submission. (we researched this and the previous point and determined that these would be very complex to implement correctly)
- modifying the UI layout to make the steps required clearer (simple but would require some research to work well)
- adding behaviour to alert users that they have unsubmitted in-progress responses and that they will not be recorded until manually submitted. This could be an alert course-wide, or popup after uploading a file or saving a text response. (simplest method, possibly tricky to implement in a non-annoying manner)
- add a button for staff to trigger a submit for all students with in-progress responses (unresearched; similar to auto-submitting but takes out the complexities required for auto-launching jobs at certain times)
- automatically send email alerts to students when due-dates draw near warning about un-submitted responses (also still in idea phase)