|
|
| (8 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| == Marking Conflict Prevention ==
| | See [[Assignment/Draft_Features/Marker_Allocation]] |
| | |
| This is a proposal for an additional feature to prevent multiple markers from marking the same student at the same time and overwriting each others grades and feedback.
| |
| | |
| This needs a better name - "Locking" is taken and "check-in/check-out" is a bit unwieldy.
| |
| | |
| == Goals and rationale ==
| |
| | |
| The main goals of this feature are to :
| |
| | |
| * Prevent multiple markers from marking the same student submission at the same time and overwriting each others grades and feedback.
| |
| | |
| == Overview ==
| |
| | |
| Currently in the assignment module, when dealing with large class sizes it is desirable to share the workload of marking among multiple markers. The current methods for doing this rely on process outside of Moodle (e.g. spreadsheet) to allocate students to markers to ensure that multiple markers do not mark the same piece of work.
| |
| | |
| The feature would add an option in the grading interface so that markers can "Check-out for marking" a submission for marking. Once a submission is checked out, only the person who has checked out the submission can provide grades/feedback. When they have finished marking, they can "Check-in marking" the submission which will allow other markers to check the submission out.
| |
| | |
| == Design ==
| |
| === Changes to assignment settings ===
| |
| | |
| No changes to the assignment settings page (this feature would always be available - but there is no requirement to use it)
| |
| | |
| === Changes to the grading table ===
| |
| | |
| An additional action would be available from the submission menu and the batch operations menu "Check-out" for all submissions that are not currently checked out.
| |
| | |
| An additional column would be added to the grading table to show which assignments are checked out and to whom. This column would show either "Not checked out" or "Checked out by XXX".
| |
| | |
| If the current submission is checked out by someone who is not the current user, the grade action would not be displayed and this row would be read only for quick-grading/offline marking.
| |
| | |
| If the current submission is checked out by the current user, or the current user has a special "reset" capability, an additional action would be available in the submission menu and the batch operations menu to "Check-in" a submission.
| |
| | |
| Submissions that are not checked out can be graded by anyone with grade permission - which replicates the existing workflow.
| |
| | |
| === Capabilities ===
| |
| An additional capability would be added to allow a manager/editing teacher to checkin a submission belonging to a different user.
| |
| | |
| === User Interface mockups ===
| |
| To be written
| |
| | |
| === Database changes ===
| |
| To be written
| |
| | |
| == Use cases ==
| |
| '''Small class size, one grader'''
| |
| * Grader can ignore this feature and mark as they did before
| |
| '''Medium class size, multiple markers'''
| |
| * Markers can "Check-out" submissions before they mark them to prevent conflicts
| |
| '''Large class size, one teacher, multiple marking assistants'''
| |
| * Teacher can require marking assistants checkout submissions before marking them to prevent conflicts
| |
| * If a marker has a submission checked out but the marker is sick/non contactable the teacher can "Check-in" that submission to allow someone else to mark it
| |
