Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Chronological order for the students in the "assess next submitter manually" feature #1110

Closed
markkuriekkinen opened this issue Dec 15, 2022 · 1 comment · Fixed by #1167
Closed

Chronological order for the students in the "assess next submitter manually" feature #1110

markkuriekkinen opened this issue Dec 15, 2022 · 1 comment · Fixed by #1167
Assignees
@EerikSaksi
Labels
area: e-exam Important for electronic exams area: end-of-course Tasks that are done at the end-of-course (e.g. retriecing grades out) area: UX teacher User experience and usability for teachers effort: days Estimated to take less than one week, from the creation of a new branch to the merging experience: beginner required knowledge estimate requester: CS The issue is raised internally by a CS teacher requires: priority Currently using this label to flag issues that need EDIT decision ASAP (even if there was priority) type: feature New feature or change to a feature
Milestone
v1.19

Comments

@markkuriekkinen
Copy link
Collaborator

In the assignment submissions list, there is a button "Start manual assessment" at the top. What is the order of the students when they are traversed through the "Assess next submitter manually" links (at the top of the inspect submission view)? The students could be sorted chronologically based on the submission time stamps (model field Submission.submission_time). The students could then be manually graded starting from the earliest students and progressing towards the latest submitters.

Note that students have multiple submissions and each of those has a different submission time. Should the students be sorted based on their latest submission time stamps or the time stamps of the best submissions?

Chronological order is useful in the grading of the Y1 course exam because the grading may be started before all students have taken the exam. Then, it is best to start from the student who took the exam at the start of the exam period.
@markkuriekkinen markkuriekkinen added type: feature New feature or change to a feature area: UX teacher User experience and usability for teachers area: e-exam Important for electronic exams effort: days Estimated to take less than one week, from the creation of a new branch to the merging experience: beginner required knowledge estimate requester: CS The issue is raised internally by a CS teacher area: end-of-course Tasks that are done at the end-of-course (e.g. retriecing grades out) requires: priority Currently using this label to flag issues that need EDIT decision ASAP (even if there was priority) labels Dec 15, 2022
@markkuriekkinen
Copy link
Collaborator Author

markkuriekkinen commented Dec 16, 2022 •
edited
Loading

Note that students have multiple submissions and each of those has a different submission time. Should the students be sorted based on their latest submission time stamps or the time stamps of the best submissions?

One teaching assistant preferred the latest submission time stamps. It describes best when the student is finishing the exam (when manual assessment is used in exams in particular; manual assessment could be used during the course too). It is then convenient to assess in succession those students who took the exam at the same time. This may also help with spotting cheating in the exam studios.

The chronological sorting helps to avoid this unfortunate scenario:

  1. assistants start manual assessment during the exam period before all students have taken the exam
  2. assistant moves on to the next student using the "Assess next submitter manually" link.
  3. If the students are not sorted, the assistant may start to assess students who are actually taking the exam right at that time. The student could still make new submissions and the student is not supposed to see the feedback during the exam. It is hard for the assistant to spot that the student has submitted on the same day when the assistant is assessing the students.

The problem (3) has already occurred in a real exam.

EerikSaksi added a commit to EerikSaksi/a-plus that referenced this issue Mar 17, 2023
@EerikSaksi
Sort unassessed exercises by most recent submission
99c0ba9 
Fixes apluslms#1110
@EerikSaksi EerikSaksi mentioned this issue Mar 17, 2023
Merged
18 tasks
@PasiSa PasiSa added this to the v1.19 milestone May 9, 2023
EerikSaksi added a commit to EerikSaksi/a-plus that referenced this issue May 9, 2023
@EerikSaksi
Sort unassessed exercises by most recent submission
a6e5972 
Fixes apluslms#1110
markkuriekkinen pushed a commit that referenced this issue May 30, 2023
@EerikSaksi @markkuriekkinen
Sort unassessed exercises by most recent submission
0a5d7f5 
Fixes #1110
@markkuriekkinen markkuriekkinen mentioned this issue Jun 12, 2023
Closed
markkuriekkinen added a commit to markkuriekkinen/a-plus that referenced this issue Jun 18, 2023
@markkuriekkinen
Revert "Sort unassessed exercises by most recent submission"
40cf492 
This reverts commit 0a5d7f5.

The feature for chronological sorting of the submissions in
the `NextUnassessedSubmitterView` is still not working correctly.
Thus, I revert this commit before making a new stable release.

See issues apluslms#1196 and apluslms#1110 and pull requests apluslms#1199 and apluslms#1167.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@EerikSaksi EerikSaksi

Labels
area: e-exam Important for electronic exams area: end-of-course Tasks that are done at the end-of-course (e.g. retriecing grades out) area: UX teacher User experience and usability for teachers effort: days Estimated to take less than one week, from the creation of a new branch to the merging experience: beginner required knowledge estimate requester: CS The issue is raised internally by a CS teacher requires: priority Currently using this label to flag issues that need EDIT decision ASAP (even if there was priority) type: feature New feature or change to a feature
Projects
A+ sprints
Status: Done
Milestone
v1.19
Development

Successfully merging a pull request may close this issue.

Sort unassessed exercises by most recent submission EerikSaksi/a-plus
3 participants
@PasiSa @markkuriekkinen @EerikSaksi