Add story of use case to Analytics docs: Teams can use Submission history to help manage / correct mistakes

Description

Docs/Product both mentioned wanting to know how people are using analytics tools.

This is a nice story for MIT's 8.EFTx about why they wanted to know how many attempts each student has made. I've included their request, and what we offer in docs that lets them do that. is the PM for the course.

Brad Goodman: "The 8.EFTx team do have some thoughts on functionality that would make our lives easier (but probably can’t be completed short term). It has been important for us to be able to track student attempts at problems.

For instance, the students spotted small bugs in a few answers (eg. a sign wrong for checking an answer box, and a problem where we switched notation midway through making the solution with one notation incorrect). Because students are completing the course at different paces, many have not attempted this to-be-fixed problem yet. So we did not want to just add attempts to everyone since that would give people who hadn't looked at it yet an advantage. So instead we reset the attempts for everyone after fixing the bug and announcing it on the discussions. We think we had at least one case of someone who claimed their attempts were not reset properly because they used them up getting the problem wrong, but I guess we don’t have access to attempt-timing information that would have allowed us to determine that…"

My response:
"The 8.EFTx team may want to make use of the Submission History feature on a per-student basis. This will give them a record of the interactions a student has made with the problem, including time-stamps and attempt number.
Submission History
http://edx.readthedocs.org/projects/edx-partner-course-staff/en/latest/running_course/course_answers.html#check-a-student-s-answer-submission-and-submission-history

*For background, events are tracked more systematically in the research data package, so this section on Problem Interaction Events may help with understanding the submission history.
http://edx.readthedocs.org/projects/devdata/en/latest/internal_data_formats/tracking_logs.html#problem-interaction-events

Let us know if you have any general questions. You've shared a great use case for why teams would use this feature, and we'd like to know if what's currently available helps!"

Steps to Reproduce

None

Current Behavior

None

Expected Behavior

None

Reason for Variance

None

Release Notes

None

User Impact Summary

None

Assignee

Unassigned

Reporter

Jennifer Akana

Reach

None

Impact

None

Platform Area

None

Customer

None

Partner Manager

None

URL

None

Contributor Name

None

Groups with Read-Only Access

None

Actual Points

None

Category of Work

None

Platform Map Area (Levels 1 & 2)

None

Platform Map Area (Levels 3 & 4)

None

Story Points

5

Epic Link

Priority

CAT-3
Configure