Repository navigation
Keep track of number of attempts, so we can know if student has used their 'herkansing' or not. (to figure out... is each change to an entry simply a new attempt, or should teacher manually have to adjust the attempts). #25
Description
Activity
There is currently a way to keep track of attempts in the database in
student_scores:// Was this a retake? If not, attempt = 1 $table->unsignedInteger('attempt')->default(1);
However the current implementation always overwrites the default attempt (1) in
StudentScore:public static function updateFeedbackForStudents(array $updatedScores) { StudentScore::upsert( $updatedScores, ['student_id', 'module_version_id', 'feedbackmoment_id', 'attempt'], ['score', 'feedback', 'teacher_id'] ); }
To implement attempts I believe the following needs to be taken into account:
- Interface design: how does a teacher indicate that the result they're editting is an edit, or new attempt
- Interface design: how are previous attempts visible to the teacher (and editable) and visible to the student
- The attempt must be changed in the
StudyPointMatrix->studentsproperty.updatedStudentswill then automatically update or insert it in the database - We should double-check if
StudentController->getStudentScoresForBlokdoes in fact get/count the last attempt (or highest?) for each student
Interface design; maybe like a 'stack'... You click a box which has multiple attempts behind it, and it will fold out like a 'stack' of old attempts was behind it?
How to indicate if you want a new attempt.. maybe like it's always a new attempt, but you can hold down a key, or set a global switch to enter edit mode?
Nice idea to use a stack, seems intuitive to me.
Another idea for an interface that's less preferable, but easier to implement:
- User edits the number
- As the focus is lost they get a modal with these options:
- Edit attempt #last
- Add new attempt
The same modal could be used to visualize the stack of attempts if the user wants to see them. Perhaps on mouse over a small stack button could appear for opening that view.
@bartjroos I can probably work out a prototype for this rather quickly now that I'm familiar with the project. I'll whip something up today
- locked and limited conversation to collaborators
on Jan 15, 2024
