MoodleDocs - User contributions [en]

https://docs.moodle.org/dev/api.php?action=feedcontributions&feedformat=atom&user=Fern MoodleDocs - User contributions [en] 2026-09-16T12:50:28Z User contributions MediaWiki 1.43.5 https://docs.moodle.org/dev/index.php?title=Assignment_Resubmission_History_Proposal&diff=36676 Assignment Resubmission History Proposal 2012-11-28T04:41:47Z

<p>Fern: /* Interface changes */</p> <hr /> <div>{{Infobox Project<br /> |name = Assignment Resubmission History<br /> |state = Proposed<br /> |tracker = MDL-36804<br /> |discussion = https://moodle.org/mod/forum/discuss.php?d=205060<br /> }}<br /> <br /> ='''Assignment Resubmission History'''=<br /> <br /> This is a proposal for an additional feature for the Assignment module to retain a history of the submission by a student to the assignment.<br /> <br /> ='''Goals and rationale'''=<br /> The main goals of this feature are to :<br /> <br /> * Provide a better history of the student interactions with an assignment. <br /> * Make it easier for students to resubmit an assignment (without having to delete their original files first)<br /> * Provide an audit trail for internal and external verification of marked work<br /> <br /> * Allow student to view past submissions (along with grade and feedback) when preparing new submission.<br /> * Allow teacher to view past submissions (along with grade and feedback) when grading latest submission.<br /> * Allow teachers to limit the number of resubmissions so that students may resubmit only until they receive a passing grade<br /> <br /> ='''Overview'''=<br /> <br /> This is a feature request from the community to retain the list of submissions by a student instead of overwriting the previous submission.<br /> <br /> ----<br /> other thoughts: <br /> <br /> Currently, when a student RESUBMITS an assignment, the original submission, grade and feedback are all lost. This inhibits the ability of both the teacher and student to LEARN FROM and BUILD ON previous efforts and feedback. <br /> <br /> Is the student’s understanding of the assignment getting better or worse? How can the teacher tell without seeing the student’s progression over time? <br /> <br /> '''Example 1:''' An assignment has tasks A, B and C. The student submits A and B but not C, which the student does not understand. Teacher feedback informs student to resubmit since she “forgot” task C. Again, the student resubmits parts A and B, but not C. Since a RESUBMISSION looks just like a FIRST SUBMISSION, this could happen many times without the teacher realizing that the student has repeatedly skipped task C (especially if the teacher has many students/classes). <br /> <br /> '''Example 2:''' An assignment asks students to write a clear and concise paragraph that expresses an opinion about a controversial issue. A student submits a paragraph that contains some good but obvious arguments as well as a few other points that are original but undeveloped. The teacher’s feedback challenges the student to explore her original thoughts. The student’s resubmission expands on the obvious arguments but completely omits the more original ideas. When the teacher sees the resubmission, all traces of the original ideas (as well as the feedback) are gone. The teacher, who has over 100 students, does not recall that this student had expressed some unique but unexplored views. A grade is given but an opportunity for real learning/teaching is lost.<br /> <br /> ='''New settings'''=<br /> * "Submission history" Yes|No - If enabled, each student submission to the assignment will be recorded at submission time and a teacher will be able to see each submission by an individual student.<br /> <br /> <br /> ----<br /> other thoughts:<br /> <br /> - When a student is required to RESUBMIT an assignment, all previous submission (including the grade, feedback, timestamp, and any other relevant info.) should be shown in a chronological order. <br /> <br /> - Similarly, when a teacher is marking/grading an assignment, all previous submission (including the grade, feedback, timestamp, and any other relevant info.) should be shown in a chronological order. <br /> <br /> - On a separate note, since the assignment module contains a “grade-to-pass’ feature that allows teachers to specify an acceptable grade, there should be a corresponding setting that allows for resubmission IF the grade-to-pass is not met.<br /> <br /> ='''Interface changes'''=<br /> A new entry will be put in the drop down menu on the grading table for each submission to view the submission history for that student. This will go to a new page in the assignment that displays the student details, as well of a list of the submissions by that student. For each submission it will contain the time and date, any files, online text or custom submission data. (Question: Does it need grades/feedback?)<br /> <br /> Although feedback for each historical submission can be collectively held in the Feedback comments text area (perhaps under headings "First attempt Feedback" or similar) or by file upload a better solution might be to archive feedback linked to each submission. This is more suited to evidence requirements in most organisations as feedback cannot then be altered. On the assumption that this would require a lot more work this should be dropped rather than holding up the main feature of allowing resubmissions properly. (Question answered?)<br /> <br /> ='''Use Cases'''=<br /> ''' A teacher wants to give feedback and let a student upload a new file submission to the assignment '''<br /> * Create an assignment with file submissions enabled, "Submission history" enabled and "Require students click submit" disabled<br /> * Wait until a student uploads a file submision<br /> * Grade the submission and give some feedback<br /> * Revert the submission to draft to allow the student to upload a new file<br /> * The student should see a readonly version of their original submission plus any feedback from the teacher<br /> * They should now be able to upload a new file without being able to delete their first submission<br /> <br /> ='''User Interface'''=<br /> Some screenshot mockups will help the community visualise this feature.</div>

Fern https://docs.moodle.org/dev/index.php?title=Assignment_Resubmission_History_Proposal&diff=36675 Assignment Resubmission History Proposal 2012-11-28T04:40:58Z

<p>Fern: /* Use Cases */</p> <hr /> <div>{{Infobox Project<br /> |name = Assignment Resubmission History<br /> |state = Proposed<br /> |tracker = MDL-36804<br /> |discussion = https://moodle.org/mod/forum/discuss.php?d=205060<br /> }}<br /> <br /> ='''Assignment Resubmission History'''=<br /> <br /> This is a proposal for an additional feature for the Assignment module to retain a history of the submission by a student to the assignment.<br /> <br /> ='''Goals and rationale'''=<br /> The main goals of this feature are to :<br /> <br /> * Provide a better history of the student interactions with an assignment. <br /> * Make it easier for students to resubmit an assignment (without having to delete their original files first)<br /> * Provide an audit trail for internal and external verification of marked work<br /> <br /> * Allow student to view past submissions (along with grade and feedback) when preparing new submission.<br /> * Allow teacher to view past submissions (along with grade and feedback) when grading latest submission.<br /> * Allow teachers to limit the number of resubmissions so that students may resubmit only until they receive a passing grade<br /> <br /> ='''Overview'''=<br /> <br /> This is a feature request from the community to retain the list of submissions by a student instead of overwriting the previous submission.<br /> <br /> ----<br /> other thoughts: <br /> <br /> Currently, when a student RESUBMITS an assignment, the original submission, grade and feedback are all lost. This inhibits the ability of both the teacher and student to LEARN FROM and BUILD ON previous efforts and feedback. <br /> <br /> Is the student’s understanding of the assignment getting better or worse? How can the teacher tell without seeing the student’s progression over time? <br /> <br /> '''Example 1:''' An assignment has tasks A, B and C. The student submits A and B but not C, which the student does not understand. Teacher feedback informs student to resubmit since she “forgot” task C. Again, the student resubmits parts A and B, but not C. Since a RESUBMISSION looks just like a FIRST SUBMISSION, this could happen many times without the teacher realizing that the student has repeatedly skipped task C (especially if the teacher has many students/classes). <br /> <br /> '''Example 2:''' An assignment asks students to write a clear and concise paragraph that expresses an opinion about a controversial issue. A student submits a paragraph that contains some good but obvious arguments as well as a few other points that are original but undeveloped. The teacher’s feedback challenges the student to explore her original thoughts. The student’s resubmission expands on the obvious arguments but completely omits the more original ideas. When the teacher sees the resubmission, all traces of the original ideas (as well as the feedback) are gone. The teacher, who has over 100 students, does not recall that this student had expressed some unique but unexplored views. A grade is given but an opportunity for real learning/teaching is lost.<br /> <br /> ='''New settings'''=<br /> * "Submission history" Yes|No - If enabled, each student submission to the assignment will be recorded at submission time and a teacher will be able to see each submission by an individual student.<br /> <br /> <br /> ----<br /> other thoughts:<br /> <br /> - When a student is required to RESUBMIT an assignment, all previous submission (including the grade, feedback, timestamp, and any other relevant info.) should be shown in a chronological order. <br /> <br /> - Similarly, when a teacher is marking/grading an assignment, all previous submission (including the grade, feedback, timestamp, and any other relevant info.) should be shown in a chronological order. <br /> <br /> - On a separate note, since the assignment module contains a “grade-to-pass’ feature that allows teachers to specify an acceptable grade, there should be a corresponding setting that allows for resubmission IF the grade-to-pass is not met.<br /> <br /> ='''Interface changes'''=<br /> A new entry will be put in the drop down menu on the grading table for each submission to view the submission history for that student. This will go to a new page in the assignment that displays the student details, as well of a list of the submissions by that student. For each submission it will contain the time and date, any files, online text or custom submission data. (Question: Does it need grades/feedback?)<br /> <br /> Although feedback for each historical submission can be collectively held in the Feedback comments text area (perhaps under headings "First attempt Feedback" or similar) or by file upload a better solution might be to archive feedback linked to each submission. This is more suited to evidence requirements in most organisations as feedback cannot then be altered. On the assumption that this would require a lot more work this should be dropped rather than holding up the main feature of allowing resubmissions properly. (Question answered?) -I'm not sure what you mean here. Can you explain? Are you suggestion we drop the feedback from the history? If so, I would suggest that we keep it since it is a crucial part of the process.<br /> <br /> -----<br /> Other thoughts:<br /> <br /> Something to consider: Implementing this feature may require that we rethink the “revert to draft” function that’s currently in place. <br /> The current “revert to draft” feature asks students to CHANGE / REPLACE their answer. If I understand this feature correctly, when a submission is reverted to draft, it is NOT graded – it is as if the student NEVER SUBMITTED it in the first place. The new feature that is being proposed here is more like a traditional “Request Resubmission” feature, where the submission is still graded but the student is allowed BUILD ON / LEARN FROM their previous attempts and resubmit for a new (hopefully better) grade. Whether we continue to use term “revert to draft” or adopt “request resubmission”, the goal here is to move from the current method of “undo” to one of “redo”. <br /> <br /> Interface suggestion:<br /> <br /> - Controlling the resubmission option: Bring back the "allow resubmission" option in the Assignment settings and add a "conditional resubmission" (based on "grade-to-pass") setting, like this: http://screencast.com/t/172nIJmiWLS. To make the conditional resubmission option easier to manage, the grade-to-pass value (which is buried in the gradebook) should also be added to the Assignment settings, like this: http://screencast.com/t/a9zUxjDP2w. In effect, if a student is able to resubmit an assignment, she would see a "Resubmit this Assignment" button. Clicking on this button would "revert the assignment to draft" but also save the past submission (along with grade, teacher feedback, etc.) <br /> <br /> - For students - Showing current and past submission: Keep a running list of all submissions at the bottom of the assignment, like this: http://screencast.com/t/tROSTGirFqf (alternatively, you could have a "Show past submissions" button").<br /> <br /> - For teachers - Showing current and past submission: Same idea as the student view, except that it would show up in the marking interface. Also, for quick identification, the "submission status" could show the submission number (attempt), like this: http://screencast.com/t/sU1d7qC4gU.<br /> <br /> ='''Use Cases'''=<br /> ''' A teacher wants to give feedback and let a student upload a new file submission to the assignment '''<br /> * Create an assignment with file submissions enabled, "Submission history" enabled and "Require students click submit" disabled<br /> * Wait until a student uploads a file submision<br /> * Grade the submission and give some feedback<br /> * Revert the submission to draft to allow the student to upload a new file<br /> * The student should see a readonly version of their original submission plus any feedback from the teacher<br /> * They should now be able to upload a new file without being able to delete their first submission<br /> <br /> ='''User Interface'''=<br /> Some screenshot mockups will help the community visualise this feature.</div>

Fern https://docs.moodle.org/dev/index.php?title=Assignment_Resubmission_History_Proposal&diff=36662 Assignment Resubmission History Proposal 2012-11-27T18:56:57Z

<p>Fern: /* Goals and rationale */</p> <hr /> <div>{{Infobox Project<br /> |name = Assignment Resubmission History<br /> |state = Proposed<br /> |tracker = MDL-36804<br /> |discussion = https://moodle.org/mod/forum/discuss.php?d=205060<br /> }}<br /> <br /> ='''Assignment Resubmission History'''=<br /> <br /> This is a proposal for an additional feature for the Assignment module to retain a history of the submission by a student to the assignment.<br /> <br /> ='''Goals and rationale'''=<br /> The main goals of this feature are to :<br /> <br /> * Provide a better history of the student interactions with an assignment. <br /> * Make it easier for students to resubmit an assignment (without having to delete their original files first)<br /> * Provide an audit trail for internal and external verification of marked work<br /> <br /> * Allow student to view past submissions (along with grade and feedback) when preparing new submission.<br /> * Allow teacher to view past submissions (along with grade and feedback) when grading latest submission.<br /> * Allow teachers to limit the number of resubmissions so that students may resubmit only until they receive a passing grade<br /> <br /> ='''Overview'''=<br /> <br /> This is a feature request from the community to retain the list of submissions by a student instead of overwriting the previous submission.<br /> <br /> ----<br /> other thoughts: <br /> <br /> Currently, when a student RESUBMITS an assignment, the original submission, grade and feedback are all lost. This inhibits the ability of both the teacher and student to LEARN FROM and BUILD ON previous efforts and feedback. <br /> <br /> Is the student’s understanding of the assignment getting better or worse? How can the teacher tell without seeing the student’s progression over time? <br /> <br /> '''Example 1:''' An assignment has tasks A, B and C. The student submits A and B but not C, which the student does not understand. Teacher feedback informs student to resubmit since she “forgot” task C. Again, the student resubmits parts A and B, but not C. Since a RESUBMISSION looks just like a FIRST SUBMISSION, this could happen many times without the teacher realizing that the student has repeatedly skipped task C (especially if the teacher has many students/classes). <br /> <br /> '''Example 2:''' An assignment asks students to write a clear and concise paragraph that expresses an opinion about a controversial issue. A student submits a paragraph that contains some good but obvious arguments as well as a few other points that are original but undeveloped. The teacher’s feedback challenges the student to explore her original thoughts. The student’s resubmission expands on the obvious arguments but completely omits the more original ideas. When the teacher sees the resubmission, all traces of the original ideas (as well as the feedback) are gone. The teacher, who has over 100 students, does not recall that this student had expressed some unique but unexplored views. A grade is given but an opportunity for real learning/teaching is lost.<br /> <br /> ='''New settings'''=<br /> * "Submission history" Yes|No - If enabled, each student submission to the assignment will be recorded at submission time and a teacher will be able to see each submission by an individual student.<br /> <br /> <br /> ----<br /> other thoughts:<br /> <br /> - When a student is required to RESUBMIT an assignment, all previous submission (including the grade, feedback, timestamp, and any other relevant info.) should be shown in a chronological order. <br /> <br /> - Similarly, when a teacher is marking/grading an assignment, all previous submission (including the grade, feedback, timestamp, and any other relevant info.) should be shown in a chronological order. <br /> <br /> - On a separate note, since the assignment module contains a “grade-to-pass’ feature that allows teachers to specify an acceptable grade, there should be a corresponding setting that allows for resubmission IF the grade-to-pass is not met.<br /> <br /> ='''Interface changes'''=<br /> A new entry will be put in the drop down menu on the grading table for each submission to view the submission history for that student. This will go to a new page in the assignment that displays the student details, as well of a list of the submissions by that student. For each submission it will contain the time and date, any files, online text or custom submission data. (Question: Does it need grades/feedback?)<br /> <br /> Although feedback for each historical submission can be collectively held in the Feedback comments text area (perhaps under headings "First attempt Feedback" or similar) or by file upload a better solution might be to archive feedback linked to each submission. This is more suited to evidence requirements in most organisations as feedback cannot then be altered. On the assumption that this would require a lot more work this should be dropped rather than holding up the main feature of allowing resubmissions properly. (Question answered?) -I'm not sure what you mean here. Can you explain? Are you suggestion we drop the feedback from the history? If so, I would suggest that we keep it since it is a crucial part of the process.<br /> <br /> -----<br /> Other thoughts:<br /> <br /> Something to consider: Implementing this feature may require that we rethink the “revert to draft” function that’s currently in place. <br /> The current “revert to draft” feature asks students to CHANGE / REPLACE their answer. If I understand this feature correctly, when a submission is reverted to draft, it is NOT graded – it is as if the student NEVER SUBMITTED it in the first place. The new feature that is being proposed here is more like a traditional “Request Resubmission” feature, where the submission is still graded but the student is allowed BUILD ON / LEARN FROM their previous attempts and resubmit for a new (hopefully better) grade. Whether we continue to use term “revert to draft” or adopt “request resubmission”, the goal here is to move from the current method of “undo” to one of “redo”. <br /> <br /> Interface suggestion:<br /> <br /> - Controlling the resubmission option: Bring back the "allow resubmission" option in the Assignment settings and add a "conditional resubmission" (based on "grade-to-pass") setting, like this: http://screencast.com/t/172nIJmiWLS. To make the conditional resubmission option easier to manage, the grade-to-pass value (which is buried in the gradebook) should also be added to the Assignment settings, like this: http://screencast.com/t/a9zUxjDP2w. In effect, if a student is able to resubmit an assignment, she would see a "Resubmit this Assignment" button. Clicking on this button would "revert the assignment to draft" but also save the past submission (along with grade, teacher feedback, etc.) <br /> <br /> - For students - Showing current and past submission: Keep a running list of all submissions at the bottom of the assignment, like this: http://screencast.com/t/tROSTGirFqf (alternatively, you could have a "Show past submissions" button").<br /> <br /> - For teachers - Showing current and past submission: Same idea as the student view, except that it would show up in the marking interface. Also, for quick identification, the "submission status" could show the submission number (attempt), like this: http://screencast.com/t/sU1d7qC4gU.<br /> <br /> ='''Use Cases'''=<br /> ''' A teacher wants to give feedback and let a student upload a new file submission to the assignment '''<br /> * Create an assignment with file submissions enabled, "Submission history" enabled and "Require students click submit" disabled<br /> * Wait until a student uploads a file submision<br /> * Grade the submission and give some feedback<br /> * Revert the submission to draft to allow the student to upload a new file<br /> * The student should see a readonly version of their original submission plus any feedback from the teacher<br /> * They should now be able to upload a new file without being able to delete their first submission<br /> <br /> <br /> ----<br /> <br /> Other thoughts:<br /> <br /> Example 1: A teacher creates an assignment with a conditional resubmission, which means that students are allowed to resubmit until they get a passing grade. To do this, the teacher sets these two additional options within the assignment settings page:<br /> <br /> * Allow resubmissions: Yes, if grade-to-pass is not met<br /> * Grade to Pass: X (teacher selects grade here)<br /> <br /> <br /> Example 2: A teacher want to create an assignment that allows for an unlimited number of submissions regardless of the grade. To do this, the teacher sets this option:<br /> <br /> * Allow resubmissions: Yes, always<br /> <br /> <br /> Example 3: A teacher does not want to allow any resubmissions. To to this, the teacher would set this option:<br /> <br /> * Allow resubmissions: No<br /> <br /> ='''User Interface'''=<br /> Some screenshot mockups will help the community visualise this feature.</div>

Fern https://docs.moodle.org/dev/index.php?title=Assignment_Resubmission_History_Proposal&diff=36661 Assignment Resubmission History Proposal 2012-11-27T17:54:03Z

<p>Fern: /* Use Cases */</p> <hr /> <div>{{Infobox Project<br /> |name = Assignment Resubmission History<br /> |state = Proposed<br /> |tracker = MDL-36804<br /> |discussion = https://moodle.org/mod/forum/discuss.php?d=205060<br /> }}<br /> <br /> ='''Assignment Resubmission History'''=<br /> <br /> This is a proposal for an additional feature for the Assignment module to retain a history of the submission by a student to the assignment.<br /> <br /> ='''Goals and rationale'''=<br /> The main goals of this feature are to :<br /> <br /> * Provide a better history of the student interactions with an assignment. <br /> * Make it easier for students to upload files to an assignment (without having to delete their original files first)<br /> * Provide an audit trail for internal and external verification of marked work<br /> <br /> ='''Overview'''=<br /> <br /> This is a feature request from the community to retain the list of submissions by a student instead of overwriting the previous submission.<br /> <br /> ----<br /> other thoughts: <br /> <br /> Currently, when a student RESUBMITS an assignment, the original submission, grade and feedback are all lost. This inhibits the ability of both the teacher and student to LEARN FROM and BUILD ON previous efforts and feedback. <br /> <br /> Is the student’s understanding of the assignment getting better or worse? How can the teacher tell without seeing the student’s progression over time? <br /> <br /> '''Example 1:''' An assignment has tasks A, B and C. The student submits A and B but not C, which the student does not understand. Teacher feedback informs student to resubmit since she “forgot” task C. Again, the student resubmits parts A and B, but not C. Since a RESUBMISSION looks just like a FIRST SUBMISSION, this could happen many times without the teacher realizing that the student has repeatedly skipped task C (especially if the teacher has many students/classes). <br /> <br /> '''Example 2:''' An assignment asks students to write a clear and concise paragraph that expresses an opinion about a controversial issue. A student submits a paragraph that contains some good but obvious arguments as well as a few other points that are original but undeveloped. The teacher’s feedback challenges the student to explore her original thoughts. The student’s resubmission expands on the obvious arguments but completely omits the more original ideas. When the teacher sees the resubmission, all traces of the original ideas (as well as the feedback) are gone. The teacher, who has over 100 students, does not recall that this student had expressed some unique but unexplored views. A grade is given but an opportunity for real learning/teaching is lost.<br /> <br /> ='''New settings'''=<br /> * "Submission history" Yes|No - If enabled, each student submission to the assignment will be recorded at submission time and a teacher will be able to see each submission by an individual student.<br /> <br /> <br /> ----<br /> other thoughts:<br /> <br /> - When a student is required to RESUBMIT an assignment, all previous submission (including the grade, feedback, timestamp, and any other relevant info.) should be shown in a chronological order. <br /> <br /> - Similarly, when a teacher is marking/grading an assignment, all previous submission (including the grade, feedback, timestamp, and any other relevant info.) should be shown in a chronological order. <br /> <br /> - On a separate note, since the assignment module contains a “grade-to-pass’ feature that allows teachers to specify an acceptable grade, there should be a corresponding setting that allows for resubmission IF the grade-to-pass is not met.<br /> <br /> ='''Interface changes'''=<br /> A new entry will be put in the drop down menu on the grading table for each submission to view the submission history for that student. This will go to a new page in the assignment that displays the student details, as well of a list of the submissions by that student. For each submission it will contain the time and date, any files, online text or custom submission data. (Question: Does it need grades/feedback?)<br /> <br /> Although feedback for each historical submission can be collectively held in the Feedback comments text area (perhaps under headings "First attempt Feedback" or similar) or by file upload a better solution might be to archive feedback linked to each submission. This is more suited to evidence requirements in most organisations as feedback cannot then be altered. On the assumption that this would require a lot more work this should be dropped rather than holding up the main feature of allowing resubmissions properly. (Question answered?) -I'm not sure what you mean here. Can you explain? Are you suggestion we drop the feedback from the history? If so, I would suggest that we keep it since it is a crucial part of the process.<br /> <br /> -----<br /> Other thoughts:<br /> <br /> Something to consider: Implementing this feature may require that we rethink the “revert to draft” function that’s currently in place. <br /> The current “revert to draft” feature asks students to CHANGE / REPLACE their answer. If I understand this feature correctly, when a submission is reverted to draft, it is NOT graded – it is as if the student NEVER SUBMITTED it in the first place. The new feature that is being proposed here is more like a traditional “Request Resubmission” feature, where the submission is still graded but the student is allowed BUILD ON / LEARN FROM their previous attempts and resubmit for a new (hopefully better) grade. Whether we continue to use term “revert to draft” or adopt “request resubmission”, the goal here is to move from the current method of “undo” to one of “redo”. <br /> <br /> Interface suggestion:<br /> <br /> - Controlling the resubmission option: Bring back the "allow resubmission" option in the Assignment settings and add a "conditional resubmission" (based on "grade-to-pass") setting, like this: http://screencast.com/t/172nIJmiWLS. To make the conditional resubmission option easier to manage, the grade-to-pass value (which is buried in the gradebook) should also be added to the Assignment settings, like this: http://screencast.com/t/a9zUxjDP2w. In effect, if a student is able to resubmit an assignment, she would see a "Resubmit this Assignment" button. Clicking on this button would "revert the assignment to draft" but also save the past submission (along with grade, teacher feedback, etc.) <br /> <br /> - For students - Showing current and past submission: Keep a running list of all submissions at the bottom of the assignment, like this: http://screencast.com/t/tROSTGirFqf (alternatively, you could have a "Show past submissions" button").<br /> <br /> - For teachers - Showing current and past submission: Same idea as the student view, except that it would show up in the marking interface. Also, for quick identification, the "submission status" could show the submission number (attempt), like this: http://screencast.com/t/sU1d7qC4gU.<br /> <br /> ='''Use Cases'''=<br /> ''' A teacher wants to give feedback and let a student upload a new file submission to the assignment '''<br /> * Create an assignment with file submissions enabled, "Submission history" enabled and "Require students click submit" disabled<br /> * Wait until a student uploads a file submision<br /> * Grade the submission and give some feedback<br /> * Revert the submission to draft to allow the student to upload a new file<br /> * The student should see a readonly version of their original submission plus any feedback from the teacher<br /> * They should now be able to upload a new file without being able to delete their first submission<br /> <br /> <br /> ----<br /> <br /> Other thoughts:<br /> <br /> Example 1: A teacher creates an assignment with a conditional resubmission, which means that students are allowed to resubmit until they get a passing grade. To do this, the teacher sets these two additional options within the assignment settings page:<br /> <br /> * Allow resubmissions: Yes, if grade-to-pass is not met<br /> * Grade to Pass: X (teacher selects grade here)<br /> <br /> <br /> Example 2: A teacher want to create an assignment that allows for an unlimited number of submissions regardless of the grade. To do this, the teacher sets this option:<br /> <br /> * Allow resubmissions: Yes, always<br /> <br /> <br /> Example 3: A teacher does not want to allow any resubmissions. To to this, the teacher would set this option:<br /> <br /> * Allow resubmissions: No<br /> <br /> ='''User Interface'''=<br /> Some screenshot mockups will help the community visualise this feature.</div>

Fern https://docs.moodle.org/dev/index.php?title=Assignment_Resubmission_History_Proposal&diff=36660 Assignment Resubmission History Proposal 2012-11-27T17:53:20Z

<p>Fern: /* Use Cases */</p> <hr /> <div>{{Infobox Project<br /> |name = Assignment Resubmission History<br /> |state = Proposed<br /> |tracker = MDL-36804<br /> |discussion = https://moodle.org/mod/forum/discuss.php?d=205060<br /> }}<br /> <br /> ='''Assignment Resubmission History'''=<br /> <br /> This is a proposal for an additional feature for the Assignment module to retain a history of the submission by a student to the assignment.<br /> <br /> ='''Goals and rationale'''=<br /> The main goals of this feature are to :<br /> <br /> * Provide a better history of the student interactions with an assignment. <br /> * Make it easier for students to upload files to an assignment (without having to delete their original files first)<br /> * Provide an audit trail for internal and external verification of marked work<br /> <br /> ='''Overview'''=<br /> <br /> This is a feature request from the community to retain the list of submissions by a student instead of overwriting the previous submission.<br /> <br /> ----<br /> other thoughts: <br /> <br /> Currently, when a student RESUBMITS an assignment, the original submission, grade and feedback are all lost. This inhibits the ability of both the teacher and student to LEARN FROM and BUILD ON previous efforts and feedback. <br /> <br /> Is the student’s understanding of the assignment getting better or worse? How can the teacher tell without seeing the student’s progression over time? <br /> <br /> '''Example 1:''' An assignment has tasks A, B and C. The student submits A and B but not C, which the student does not understand. Teacher feedback informs student to resubmit since she “forgot” task C. Again, the student resubmits parts A and B, but not C. Since a RESUBMISSION looks just like a FIRST SUBMISSION, this could happen many times without the teacher realizing that the student has repeatedly skipped task C (especially if the teacher has many students/classes). <br /> <br /> '''Example 2:''' An assignment asks students to write a clear and concise paragraph that expresses an opinion about a controversial issue. A student submits a paragraph that contains some good but obvious arguments as well as a few other points that are original but undeveloped. The teacher’s feedback challenges the student to explore her original thoughts. The student’s resubmission expands on the obvious arguments but completely omits the more original ideas. When the teacher sees the resubmission, all traces of the original ideas (as well as the feedback) are gone. The teacher, who has over 100 students, does not recall that this student had expressed some unique but unexplored views. A grade is given but an opportunity for real learning/teaching is lost.<br /> <br /> ='''New settings'''=<br /> * "Submission history" Yes|No - If enabled, each student submission to the assignment will be recorded at submission time and a teacher will be able to see each submission by an individual student.<br /> <br /> <br /> ----<br /> other thoughts:<br /> <br /> - When a student is required to RESUBMIT an assignment, all previous submission (including the grade, feedback, timestamp, and any other relevant info.) should be shown in a chronological order. <br /> <br /> - Similarly, when a teacher is marking/grading an assignment, all previous submission (including the grade, feedback, timestamp, and any other relevant info.) should be shown in a chronological order. <br /> <br /> - On a separate note, since the assignment module contains a “grade-to-pass’ feature that allows teachers to specify an acceptable grade, there should be a corresponding setting that allows for resubmission IF the grade-to-pass is not met.<br /> <br /> ='''Interface changes'''=<br /> A new entry will be put in the drop down menu on the grading table for each submission to view the submission history for that student. This will go to a new page in the assignment that displays the student details, as well of a list of the submissions by that student. For each submission it will contain the time and date, any files, online text or custom submission data. (Question: Does it need grades/feedback?)<br /> <br /> Although feedback for each historical submission can be collectively held in the Feedback comments text area (perhaps under headings "First attempt Feedback" or similar) or by file upload a better solution might be to archive feedback linked to each submission. This is more suited to evidence requirements in most organisations as feedback cannot then be altered. On the assumption that this would require a lot more work this should be dropped rather than holding up the main feature of allowing resubmissions properly. (Question answered?) -I'm not sure what you mean here. Can you explain? Are you suggestion we drop the feedback from the history? If so, I would suggest that we keep it since it is a crucial part of the process.<br /> <br /> -----<br /> Other thoughts:<br /> <br /> Something to consider: Implementing this feature may require that we rethink the “revert to draft” function that’s currently in place. <br /> The current “revert to draft” feature asks students to CHANGE / REPLACE their answer. If I understand this feature correctly, when a submission is reverted to draft, it is NOT graded – it is as if the student NEVER SUBMITTED it in the first place. The new feature that is being proposed here is more like a traditional “Request Resubmission” feature, where the submission is still graded but the student is allowed BUILD ON / LEARN FROM their previous attempts and resubmit for a new (hopefully better) grade. Whether we continue to use term “revert to draft” or adopt “request resubmission”, the goal here is to move from the current method of “undo” to one of “redo”. <br /> <br /> Interface suggestion:<br /> <br /> - Controlling the resubmission option: Bring back the "allow resubmission" option in the Assignment settings and add a "conditional resubmission" (based on "grade-to-pass") setting, like this: http://screencast.com/t/172nIJmiWLS. To make the conditional resubmission option easier to manage, the grade-to-pass value (which is buried in the gradebook) should also be added to the Assignment settings, like this: http://screencast.com/t/a9zUxjDP2w. In effect, if a student is able to resubmit an assignment, she would see a "Resubmit this Assignment" button. Clicking on this button would "revert the assignment to draft" but also save the past submission (along with grade, teacher feedback, etc.) <br /> <br /> - For students - Showing current and past submission: Keep a running list of all submissions at the bottom of the assignment, like this: http://screencast.com/t/tROSTGirFqf (alternatively, you could have a "Show past submissions" button").<br /> <br /> - For teachers - Showing current and past submission: Same idea as the student view, except that it would show up in the marking interface. Also, for quick identification, the "submission status" could show the submission number (attempt), like this: http://screencast.com/t/sU1d7qC4gU.<br /> <br /> ='''Use Cases'''=<br /> ''' A teacher wants to give feedback and let a student upload a new file submission to the assignment '''<br /> * Create an assignment with file submissions enabled, "Submission history" enabled and "Require students click submit" disabled<br /> * Wait until a student uploads a file submision<br /> * Grade the submission and give some feedback<br /> * Revert the submission to draft to allow the student to upload a new file<br /> * The student should see a readonly version of their original submission plus any feedback from the teacher<br /> * They should now be able to upload a new file without being able to delete their first submission<br /> <br /> <br /> ----<br /> <br /> Other thoughts:<br /> <br /> Example 1: A teacher creates an assignment with a conditional resubmission, which means that students are allowed to resubmit until they get a passing mark. To do this, the teacher sets these two additional options within the assignment settings page:<br /> <br /> * Allow resubmissions: Yes, if grade-to-pass is not met<br /> * Grade to Pass: X (teacher selects grade here)<br /> <br /> <br /> Example 2: A teacher want to create an assignment that allows for an unlimited number of submissions regardless of the grade. To do this, the teacher sets this option:<br /> <br /> * Allow resubmissions: Yes, always<br /> <br /> <br /> Example 3: A teacher does not want to allow any resubmissions. To to this, the teacher would set this option:<br /> <br /> * Allow resubmissions: No<br /> <br /> ='''User Interface'''=<br /> Some screenshot mockups will help the community visualise this feature.</div>

Fern https://docs.moodle.org/dev/index.php?title=Assignment_Resubmission_History_Proposal&diff=36659 Assignment Resubmission History Proposal 2012-11-27T17:52:46Z

<p>Fern: /* Use Cases */</p> <hr /> <div>{{Infobox Project<br /> |name = Assignment Resubmission History<br /> |state = Proposed<br /> |tracker = MDL-36804<br /> |discussion = https://moodle.org/mod/forum/discuss.php?d=205060<br /> }}<br /> <br /> ='''Assignment Resubmission History'''=<br /> <br /> This is a proposal for an additional feature for the Assignment module to retain a history of the submission by a student to the assignment.<br /> <br /> ='''Goals and rationale'''=<br /> The main goals of this feature are to :<br /> <br /> * Provide a better history of the student interactions with an assignment. <br /> * Make it easier for students to upload files to an assignment (without having to delete their original files first)<br /> * Provide an audit trail for internal and external verification of marked work<br /> <br /> ='''Overview'''=<br /> <br /> This is a feature request from the community to retain the list of submissions by a student instead of overwriting the previous submission.<br /> <br /> ----<br /> other thoughts: <br /> <br /> Currently, when a student RESUBMITS an assignment, the original submission, grade and feedback are all lost. This inhibits the ability of both the teacher and student to LEARN FROM and BUILD ON previous efforts and feedback. <br /> <br /> Is the student’s understanding of the assignment getting better or worse? How can the teacher tell without seeing the student’s progression over time? <br /> <br /> '''Example 1:''' An assignment has tasks A, B and C. The student submits A and B but not C, which the student does not understand. Teacher feedback informs student to resubmit since she “forgot” task C. Again, the student resubmits parts A and B, but not C. Since a RESUBMISSION looks just like a FIRST SUBMISSION, this could happen many times without the teacher realizing that the student has repeatedly skipped task C (especially if the teacher has many students/classes). <br /> <br /> '''Example 2:''' An assignment asks students to write a clear and concise paragraph that expresses an opinion about a controversial issue. A student submits a paragraph that contains some good but obvious arguments as well as a few other points that are original but undeveloped. The teacher’s feedback challenges the student to explore her original thoughts. The student’s resubmission expands on the obvious arguments but completely omits the more original ideas. When the teacher sees the resubmission, all traces of the original ideas (as well as the feedback) are gone. The teacher, who has over 100 students, does not recall that this student had expressed some unique but unexplored views. A grade is given but an opportunity for real learning/teaching is lost.<br /> <br /> ='''New settings'''=<br /> * "Submission history" Yes|No - If enabled, each student submission to the assignment will be recorded at submission time and a teacher will be able to see each submission by an individual student.<br /> <br /> <br /> ----<br /> other thoughts:<br /> <br /> - When a student is required to RESUBMIT an assignment, all previous submission (including the grade, feedback, timestamp, and any other relevant info.) should be shown in a chronological order. <br /> <br /> - Similarly, when a teacher is marking/grading an assignment, all previous submission (including the grade, feedback, timestamp, and any other relevant info.) should be shown in a chronological order. <br /> <br /> - On a separate note, since the assignment module contains a “grade-to-pass’ feature that allows teachers to specify an acceptable grade, there should be a corresponding setting that allows for resubmission IF the grade-to-pass is not met.<br /> <br /> ='''Interface changes'''=<br /> A new entry will be put in the drop down menu on the grading table for each submission to view the submission history for that student. This will go to a new page in the assignment that displays the student details, as well of a list of the submissions by that student. For each submission it will contain the time and date, any files, online text or custom submission data. (Question: Does it need grades/feedback?)<br /> <br /> Although feedback for each historical submission can be collectively held in the Feedback comments text area (perhaps under headings "First attempt Feedback" or similar) or by file upload a better solution might be to archive feedback linked to each submission. This is more suited to evidence requirements in most organisations as feedback cannot then be altered. On the assumption that this would require a lot more work this should be dropped rather than holding up the main feature of allowing resubmissions properly. (Question answered?) -I'm not sure what you mean here. Can you explain? Are you suggestion we drop the feedback from the history? If so, I would suggest that we keep it since it is a crucial part of the process.<br /> <br /> -----<br /> Other thoughts:<br /> <br /> Something to consider: Implementing this feature may require that we rethink the “revert to draft” function that’s currently in place. <br /> The current “revert to draft” feature asks students to CHANGE / REPLACE their answer. If I understand this feature correctly, when a submission is reverted to draft, it is NOT graded – it is as if the student NEVER SUBMITTED it in the first place. The new feature that is being proposed here is more like a traditional “Request Resubmission” feature, where the submission is still graded but the student is allowed BUILD ON / LEARN FROM their previous attempts and resubmit for a new (hopefully better) grade. Whether we continue to use term “revert to draft” or adopt “request resubmission”, the goal here is to move from the current method of “undo” to one of “redo”. <br /> <br /> Interface suggestion:<br /> <br /> - Controlling the resubmission option: Bring back the "allow resubmission" option in the Assignment settings and add a "conditional resubmission" (based on "grade-to-pass") setting, like this: http://screencast.com/t/172nIJmiWLS. To make the conditional resubmission option easier to manage, the grade-to-pass value (which is buried in the gradebook) should also be added to the Assignment settings, like this: http://screencast.com/t/a9zUxjDP2w. In effect, if a student is able to resubmit an assignment, she would see a "Resubmit this Assignment" button. Clicking on this button would "revert the assignment to draft" but also save the past submission (along with grade, teacher feedback, etc.) <br /> <br /> - For students - Showing current and past submission: Keep a running list of all submissions at the bottom of the assignment, like this: http://screencast.com/t/tROSTGirFqf (alternatively, you could have a "Show past submissions" button").<br /> <br /> - For teachers - Showing current and past submission: Same idea as the student view, except that it would show up in the marking interface. Also, for quick identification, the "submission status" could show the submission number (attempt), like this: http://screencast.com/t/sU1d7qC4gU.<br /> <br /> ='''Use Cases'''=<br /> ''' A teacher wants to give feedback and let a student upload a new file submission to the assignment '''<br /> * Create an assignment with file submissions enabled, "Submission history" enabled and "Require students click submit" disabled<br /> * Wait until a student uploads a file submision<br /> * Grade the submission and give some feedback<br /> * Revert the submission to draft to allow the student to upload a new file<br /> * The student should see a readonly version of their original submission plus any feedback from the teacher<br /> * They should now be able to upload a new file without being able to delete their first submission<br /> <br /> <br /> ----<br /> <br /> Other thoughts:<br /> <br /> * Example 1: A teacher creates an assignment with a conditional resubmission, which means that students are allowed to resubmit until they get a passing mark. To do this, the teacher sets these two additional options within the assignment settings page:<br /> <br /> Allow resubmissions: Yes, if grade-to-pass is not met<br /> <br /> Grade to Pass: X (teacher selects grade here)<br /> <br /> <br /> * Example 2: A teacher want to create an assignment that allows for an unlimited number of submissions regardless of the grade. To do this, the teacher sets this option:<br /> <br /> Allow resubmissions: Yes, always<br /> <br /> <br /> * Example 3: A teacher does not want to allow any resubmissions. To to this, the teacher would set this option:<br /> <br /> Allow resubmissions: No<br /> <br /> ='''User Interface'''=<br /> Some screenshot mockups will help the community visualise this feature.</div>

Fern https://docs.moodle.org/dev/index.php?title=Assignment_Resubmission_History_Proposal&diff=36658 Assignment Resubmission History Proposal 2012-11-27T17:52:23Z

<p>Fern: /* Use Cases */</p> <hr /> <div>{{Infobox Project<br /> |name = Assignment Resubmission History<br /> |state = Proposed<br /> |tracker = MDL-36804<br /> |discussion = https://moodle.org/mod/forum/discuss.php?d=205060<br /> }}<br /> <br /> ='''Assignment Resubmission History'''=<br /> <br /> This is a proposal for an additional feature for the Assignment module to retain a history of the submission by a student to the assignment.<br /> <br /> ='''Goals and rationale'''=<br /> The main goals of this feature are to :<br /> <br /> * Provide a better history of the student interactions with an assignment. <br /> * Make it easier for students to upload files to an assignment (without having to delete their original files first)<br /> * Provide an audit trail for internal and external verification of marked work<br /> <br /> ='''Overview'''=<br /> <br /> This is a feature request from the community to retain the list of submissions by a student instead of overwriting the previous submission.<br /> <br /> ----<br /> other thoughts: <br /> <br /> Currently, when a student RESUBMITS an assignment, the original submission, grade and feedback are all lost. This inhibits the ability of both the teacher and student to LEARN FROM and BUILD ON previous efforts and feedback. <br /> <br /> Is the student’s understanding of the assignment getting better or worse? How can the teacher tell without seeing the student’s progression over time? <br /> <br /> '''Example 1:''' An assignment has tasks A, B and C. The student submits A and B but not C, which the student does not understand. Teacher feedback informs student to resubmit since she “forgot” task C. Again, the student resubmits parts A and B, but not C. Since a RESUBMISSION looks just like a FIRST SUBMISSION, this could happen many times without the teacher realizing that the student has repeatedly skipped task C (especially if the teacher has many students/classes). <br /> <br /> '''Example 2:''' An assignment asks students to write a clear and concise paragraph that expresses an opinion about a controversial issue. A student submits a paragraph that contains some good but obvious arguments as well as a few other points that are original but undeveloped. The teacher’s feedback challenges the student to explore her original thoughts. The student’s resubmission expands on the obvious arguments but completely omits the more original ideas. When the teacher sees the resubmission, all traces of the original ideas (as well as the feedback) are gone. The teacher, who has over 100 students, does not recall that this student had expressed some unique but unexplored views. A grade is given but an opportunity for real learning/teaching is lost.<br /> <br /> ='''New settings'''=<br /> * "Submission history" Yes|No - If enabled, each student submission to the assignment will be recorded at submission time and a teacher will be able to see each submission by an individual student.<br /> <br /> <br /> ----<br /> other thoughts:<br /> <br /> - When a student is required to RESUBMIT an assignment, all previous submission (including the grade, feedback, timestamp, and any other relevant info.) should be shown in a chronological order. <br /> <br /> - Similarly, when a teacher is marking/grading an assignment, all previous submission (including the grade, feedback, timestamp, and any other relevant info.) should be shown in a chronological order. <br /> <br /> - On a separate note, since the assignment module contains a “grade-to-pass’ feature that allows teachers to specify an acceptable grade, there should be a corresponding setting that allows for resubmission IF the grade-to-pass is not met.<br /> <br /> ='''Interface changes'''=<br /> A new entry will be put in the drop down menu on the grading table for each submission to view the submission history for that student. This will go to a new page in the assignment that displays the student details, as well of a list of the submissions by that student. For each submission it will contain the time and date, any files, online text or custom submission data. (Question: Does it need grades/feedback?)<br /> <br /> Although feedback for each historical submission can be collectively held in the Feedback comments text area (perhaps under headings "First attempt Feedback" or similar) or by file upload a better solution might be to archive feedback linked to each submission. This is more suited to evidence requirements in most organisations as feedback cannot then be altered. On the assumption that this would require a lot more work this should be dropped rather than holding up the main feature of allowing resubmissions properly. (Question answered?) -I'm not sure what you mean here. Can you explain? Are you suggestion we drop the feedback from the history? If so, I would suggest that we keep it since it is a crucial part of the process.<br /> <br /> -----<br /> Other thoughts:<br /> <br /> Something to consider: Implementing this feature may require that we rethink the “revert to draft” function that’s currently in place. <br /> The current “revert to draft” feature asks students to CHANGE / REPLACE their answer. If I understand this feature correctly, when a submission is reverted to draft, it is NOT graded – it is as if the student NEVER SUBMITTED it in the first place. The new feature that is being proposed here is more like a traditional “Request Resubmission” feature, where the submission is still graded but the student is allowed BUILD ON / LEARN FROM their previous attempts and resubmit for a new (hopefully better) grade. Whether we continue to use term “revert to draft” or adopt “request resubmission”, the goal here is to move from the current method of “undo” to one of “redo”. <br /> <br /> Interface suggestion:<br /> <br /> - Controlling the resubmission option: Bring back the "allow resubmission" option in the Assignment settings and add a "conditional resubmission" (based on "grade-to-pass") setting, like this: http://screencast.com/t/172nIJmiWLS. To make the conditional resubmission option easier to manage, the grade-to-pass value (which is buried in the gradebook) should also be added to the Assignment settings, like this: http://screencast.com/t/a9zUxjDP2w. In effect, if a student is able to resubmit an assignment, she would see a "Resubmit this Assignment" button. Clicking on this button would "revert the assignment to draft" but also save the past submission (along with grade, teacher feedback, etc.) <br /> <br /> - For students - Showing current and past submission: Keep a running list of all submissions at the bottom of the assignment, like this: http://screencast.com/t/tROSTGirFqf (alternatively, you could have a "Show past submissions" button").<br /> <br /> - For teachers - Showing current and past submission: Same idea as the student view, except that it would show up in the marking interface. Also, for quick identification, the "submission status" could show the submission number (attempt), like this: http://screencast.com/t/sU1d7qC4gU.<br /> <br /> ='''Use Cases'''=<br /> ''' A teacher wants to give feedback and let a student upload a new file submission to the assignment '''<br /> * Create an assignment with file submissions enabled, "Submission history" enabled and "Require students click submit" disabled<br /> * Wait until a student uploads a file submision<br /> * Grade the submission and give some feedback<br /> * Revert the submission to draft to allow the student to upload a new file<br /> * The student should see a readonly version of their original submission plus any feedback from the teacher<br /> * They should now be able to upload a new file without being able to delete their first submission<br /> <br /> <br /> ----<br /> <br /> Other thoughts:<br /> <br /> * Example 1: A teacher creates an assignment with a conditional resubmission, which means that students are allowed to resubmit until they get a passing mark.<br /> To do this, the teacher sets these two additional options within the assignment settings page:<br /> <br /> Allow resubmissions: Yes, if grade-to-pass is not met<br /> <br /> Grade to Pass: X (teacher selects grade here)<br /> <br /> * Example 2: A teacher want to create an assignment that allows for an unlimited number of submissions regardless of the grade. To do this, the teacher sets this option:<br /> <br /> Allow resubmissions: Yes, always<br /> <br /> * Example 3: A teacher does not want to allow any resubmissions. To to this, the teacher would set this option:<br /> <br /> Allow resubmissions: No<br /> <br /> ='''User Interface'''=<br /> Some screenshot mockups will help the community visualise this feature.</div>

Fern https://docs.moodle.org/dev/index.php?title=Assignment_Resubmission_History_Proposal&diff=36657 Assignment Resubmission History Proposal 2012-11-27T17:51:12Z

<p>Fern: /* Use Cases */</p> <hr /> <div>{{Infobox Project<br /> |name = Assignment Resubmission History<br /> |state = Proposed<br /> |tracker = MDL-36804<br /> |discussion = https://moodle.org/mod/forum/discuss.php?d=205060<br /> }}<br /> <br /> ='''Assignment Resubmission History'''=<br /> <br /> This is a proposal for an additional feature for the Assignment module to retain a history of the submission by a student to the assignment.<br /> <br /> ='''Goals and rationale'''=<br /> The main goals of this feature are to :<br /> <br /> * Provide a better history of the student interactions with an assignment. <br /> * Make it easier for students to upload files to an assignment (without having to delete their original files first)<br /> * Provide an audit trail for internal and external verification of marked work<br /> <br /> ='''Overview'''=<br /> <br /> This is a feature request from the community to retain the list of submissions by a student instead of overwriting the previous submission.<br /> <br /> ----<br /> other thoughts: <br /> <br /> Currently, when a student RESUBMITS an assignment, the original submission, grade and feedback are all lost. This inhibits the ability of both the teacher and student to LEARN FROM and BUILD ON previous efforts and feedback. <br /> <br /> Is the student’s understanding of the assignment getting better or worse? How can the teacher tell without seeing the student’s progression over time? <br /> <br /> '''Example 1:''' An assignment has tasks A, B and C. The student submits A and B but not C, which the student does not understand. Teacher feedback informs student to resubmit since she “forgot” task C. Again, the student resubmits parts A and B, but not C. Since a RESUBMISSION looks just like a FIRST SUBMISSION, this could happen many times without the teacher realizing that the student has repeatedly skipped task C (especially if the teacher has many students/classes). <br /> <br /> '''Example 2:''' An assignment asks students to write a clear and concise paragraph that expresses an opinion about a controversial issue. A student submits a paragraph that contains some good but obvious arguments as well as a few other points that are original but undeveloped. The teacher’s feedback challenges the student to explore her original thoughts. The student’s resubmission expands on the obvious arguments but completely omits the more original ideas. When the teacher sees the resubmission, all traces of the original ideas (as well as the feedback) are gone. The teacher, who has over 100 students, does not recall that this student had expressed some unique but unexplored views. A grade is given but an opportunity for real learning/teaching is lost.<br /> <br /> ='''New settings'''=<br /> * "Submission history" Yes|No - If enabled, each student submission to the assignment will be recorded at submission time and a teacher will be able to see each submission by an individual student.<br /> <br /> <br /> ----<br /> other thoughts:<br /> <br /> - When a student is required to RESUBMIT an assignment, all previous submission (including the grade, feedback, timestamp, and any other relevant info.) should be shown in a chronological order. <br /> <br /> - Similarly, when a teacher is marking/grading an assignment, all previous submission (including the grade, feedback, timestamp, and any other relevant info.) should be shown in a chronological order. <br /> <br /> - On a separate note, since the assignment module contains a “grade-to-pass’ feature that allows teachers to specify an acceptable grade, there should be a corresponding setting that allows for resubmission IF the grade-to-pass is not met.<br /> <br /> ='''Interface changes'''=<br /> A new entry will be put in the drop down menu on the grading table for each submission to view the submission history for that student. This will go to a new page in the assignment that displays the student details, as well of a list of the submissions by that student. For each submission it will contain the time and date, any files, online text or custom submission data. (Question: Does it need grades/feedback?)<br /> <br /> Although feedback for each historical submission can be collectively held in the Feedback comments text area (perhaps under headings "First attempt Feedback" or similar) or by file upload a better solution might be to archive feedback linked to each submission. This is more suited to evidence requirements in most organisations as feedback cannot then be altered. On the assumption that this would require a lot more work this should be dropped rather than holding up the main feature of allowing resubmissions properly. (Question answered?) -I'm not sure what you mean here. Can you explain? Are you suggestion we drop the feedback from the history? If so, I would suggest that we keep it since it is a crucial part of the process.<br /> <br /> -----<br /> Other thoughts:<br /> <br /> Something to consider: Implementing this feature may require that we rethink the “revert to draft” function that’s currently in place. <br /> The current “revert to draft” feature asks students to CHANGE / REPLACE their answer. If I understand this feature correctly, when a submission is reverted to draft, it is NOT graded – it is as if the student NEVER SUBMITTED it in the first place. The new feature that is being proposed here is more like a traditional “Request Resubmission” feature, where the submission is still graded but the student is allowed BUILD ON / LEARN FROM their previous attempts and resubmit for a new (hopefully better) grade. Whether we continue to use term “revert to draft” or adopt “request resubmission”, the goal here is to move from the current method of “undo” to one of “redo”. <br /> <br /> Interface suggestion:<br /> <br /> - Controlling the resubmission option: Bring back the "allow resubmission" option in the Assignment settings and add a "conditional resubmission" (based on "grade-to-pass") setting, like this: http://screencast.com/t/172nIJmiWLS. To make the conditional resubmission option easier to manage, the grade-to-pass value (which is buried in the gradebook) should also be added to the Assignment settings, like this: http://screencast.com/t/a9zUxjDP2w. In effect, if a student is able to resubmit an assignment, she would see a "Resubmit this Assignment" button. Clicking on this button would "revert the assignment to draft" but also save the past submission (along with grade, teacher feedback, etc.) <br /> <br /> - For students - Showing current and past submission: Keep a running list of all submissions at the bottom of the assignment, like this: http://screencast.com/t/tROSTGirFqf (alternatively, you could have a "Show past submissions" button").<br /> <br /> - For teachers - Showing current and past submission: Same idea as the student view, except that it would show up in the marking interface. Also, for quick identification, the "submission status" could show the submission number (attempt), like this: http://screencast.com/t/sU1d7qC4gU.<br /> <br /> ='''Use Cases'''=<br /> ''' A teacher wants to give feedback and let a student upload a new file submission to the assignment '''<br /> * Create an assignment with file submissions enabled, "Submission history" enabled and "Require students click submit" disabled<br /> * Wait until a student uploads a file submision<br /> * Grade the submission and give some feedback<br /> * Revert the submission to draft to allow the student to upload a new file<br /> * The student should see a readonly version of their original submission plus any feedback from the teacher<br /> * They should now be able to upload a new file without being able to delete their first submission<br /> <br /> <br /> ----<br /> <br /> Other thoughts:<br /> <br /> * Example 1: A teacher creates an assignment with a conditional resubmission, which means that students are allowed to resubmit until they get a passing mark.<br /> To do this, the teacher sets these two additional options within the assignment settings page:<br /> <br /> Allow resubmissions: Yes, if grade-to-pass is not met<br /> <br /> Grade to Pass: X<br /> <br /> * Example 2: A teacher want to create an assignment that allows for an unlimited number of submissions regardless of the grade. To do this, the teacher sets this option:<br /> <br /> Allow resubmissions: Yes, always<br /> <br /> * Example 3: A teacher does not want to allow any resubmissions. To to this, the teacher would set this option:<br /> <br /> Allow resubmissions: No<br /> <br /> ='''User Interface'''=<br /> Some screenshot mockups will help the community visualise this feature.</div>

Fern https://docs.moodle.org/dev/index.php?title=Assignment_Resubmission_History_Proposal&diff=36656 Assignment Resubmission History Proposal 2012-11-27T17:49:55Z

<p>Fern: /* Interface changes */</p> <hr /> <div>{{Infobox Project<br /> |name = Assignment Resubmission History<br /> |state = Proposed<br /> |tracker = MDL-36804<br /> |discussion = https://moodle.org/mod/forum/discuss.php?d=205060<br /> }}<br /> <br /> ='''Assignment Resubmission History'''=<br /> <br /> This is a proposal for an additional feature for the Assignment module to retain a history of the submission by a student to the assignment.<br /> <br /> ='''Goals and rationale'''=<br /> The main goals of this feature are to :<br /> <br /> * Provide a better history of the student interactions with an assignment. <br /> * Make it easier for students to upload files to an assignment (without having to delete their original files first)<br /> * Provide an audit trail for internal and external verification of marked work<br /> <br /> ='''Overview'''=<br /> <br /> This is a feature request from the community to retain the list of submissions by a student instead of overwriting the previous submission.<br /> <br /> ----<br /> other thoughts: <br /> <br /> Currently, when a student RESUBMITS an assignment, the original submission, grade and feedback are all lost. This inhibits the ability of both the teacher and student to LEARN FROM and BUILD ON previous efforts and feedback. <br /> <br /> Is the student’s understanding of the assignment getting better or worse? How can the teacher tell without seeing the student’s progression over time? <br /> <br /> '''Example 1:''' An assignment has tasks A, B and C. The student submits A and B but not C, which the student does not understand. Teacher feedback informs student to resubmit since she “forgot” task C. Again, the student resubmits parts A and B, but not C. Since a RESUBMISSION looks just like a FIRST SUBMISSION, this could happen many times without the teacher realizing that the student has repeatedly skipped task C (especially if the teacher has many students/classes). <br /> <br /> '''Example 2:''' An assignment asks students to write a clear and concise paragraph that expresses an opinion about a controversial issue. A student submits a paragraph that contains some good but obvious arguments as well as a few other points that are original but undeveloped. The teacher’s feedback challenges the student to explore her original thoughts. The student’s resubmission expands on the obvious arguments but completely omits the more original ideas. When the teacher sees the resubmission, all traces of the original ideas (as well as the feedback) are gone. The teacher, who has over 100 students, does not recall that this student had expressed some unique but unexplored views. A grade is given but an opportunity for real learning/teaching is lost.<br /> <br /> ='''New settings'''=<br /> * "Submission history" Yes|No - If enabled, each student submission to the assignment will be recorded at submission time and a teacher will be able to see each submission by an individual student.<br /> <br /> <br /> ----<br /> other thoughts:<br /> <br /> - When a student is required to RESUBMIT an assignment, all previous submission (including the grade, feedback, timestamp, and any other relevant info.) should be shown in a chronological order. <br /> <br /> - Similarly, when a teacher is marking/grading an assignment, all previous submission (including the grade, feedback, timestamp, and any other relevant info.) should be shown in a chronological order. <br /> <br /> - On a separate note, since the assignment module contains a “grade-to-pass’ feature that allows teachers to specify an acceptable grade, there should be a corresponding setting that allows for resubmission IF the grade-to-pass is not met.<br /> <br /> ='''Interface changes'''=<br /> A new entry will be put in the drop down menu on the grading table for each submission to view the submission history for that student. This will go to a new page in the assignment that displays the student details, as well of a list of the submissions by that student. For each submission it will contain the time and date, any files, online text or custom submission data. (Question: Does it need grades/feedback?)<br /> <br /> Although feedback for each historical submission can be collectively held in the Feedback comments text area (perhaps under headings "First attempt Feedback" or similar) or by file upload a better solution might be to archive feedback linked to each submission. This is more suited to evidence requirements in most organisations as feedback cannot then be altered. On the assumption that this would require a lot more work this should be dropped rather than holding up the main feature of allowing resubmissions properly. (Question answered?) -I'm not sure what you mean here. Can you explain? Are you suggestion we drop the feedback from the history? If so, I would suggest that we keep it since it is a crucial part of the process.<br /> <br /> -----<br /> Other thoughts:<br /> <br /> Something to consider: Implementing this feature may require that we rethink the “revert to draft” function that’s currently in place. <br /> The current “revert to draft” feature asks students to CHANGE / REPLACE their answer. If I understand this feature correctly, when a submission is reverted to draft, it is NOT graded – it is as if the student NEVER SUBMITTED it in the first place. The new feature that is being proposed here is more like a traditional “Request Resubmission” feature, where the submission is still graded but the student is allowed BUILD ON / LEARN FROM their previous attempts and resubmit for a new (hopefully better) grade. Whether we continue to use term “revert to draft” or adopt “request resubmission”, the goal here is to move from the current method of “undo” to one of “redo”. <br /> <br /> Interface suggestion:<br /> <br /> - Controlling the resubmission option: Bring back the "allow resubmission" option in the Assignment settings and add a "conditional resubmission" (based on "grade-to-pass") setting, like this: http://screencast.com/t/172nIJmiWLS. To make the conditional resubmission option easier to manage, the grade-to-pass value (which is buried in the gradebook) should also be added to the Assignment settings, like this: http://screencast.com/t/a9zUxjDP2w. In effect, if a student is able to resubmit an assignment, she would see a "Resubmit this Assignment" button. Clicking on this button would "revert the assignment to draft" but also save the past submission (along with grade, teacher feedback, etc.) <br /> <br /> - For students - Showing current and past submission: Keep a running list of all submissions at the bottom of the assignment, like this: http://screencast.com/t/tROSTGirFqf (alternatively, you could have a "Show past submissions" button").<br /> <br /> - For teachers - Showing current and past submission: Same idea as the student view, except that it would show up in the marking interface. Also, for quick identification, the "submission status" could show the submission number (attempt), like this: http://screencast.com/t/sU1d7qC4gU.<br /> <br /> ='''Use Cases'''=<br /> ''' A teacher wants to give feedback and let a student upload a new file submission to the assignment '''<br /> * Create an assignment with file submissions enabled, "Submission history" enabled and "Require students click submit" disabled<br /> * Wait until a student uploads a file submision<br /> * Grade the submission and give some feedback<br /> * Revert the submission to draft to allow the student to upload a new file<br /> * The student should see a readonly version of their original submission plus any feedback from the teacher<br /> * They should now be able to upload a new file without being able to delete their first submission<br /> <br /> <br /> ----<br /> <br /> Other thoughts:<br /> <br /> * Example 1: A teacher creates an assignment with a conditional resubmission, which means that students are allowed to resubmit until they get a passing mark.<br /> To do this, the teacher sets these two additional options within the assignment settings page:<br /> Allow resubmissions: Yes, if grade-to-pass is not met<br /> Grade to Pass: X<br /> <br /> * Example 2: A teacher want to create an assignment that allows for an unlimited number of submissions regardless of the grade. To do this, the teacher sets this option:<br /> Allow resubmissions: Yes, always<br /> <br /> * Example 3: A teacher does not want to allow any resubmissions. To to this, the teacher would set this option:<br /> Allow resubmissions: No<br /> <br /> ='''User Interface'''=<br /> Some screenshot mockups will help the community visualise this feature.</div>

Fern https://docs.moodle.org/dev/index.php?title=Assignment_Resubmission_History_Proposal&diff=36655 Assignment Resubmission History Proposal 2012-11-27T17:30:15Z

<p>Fern: /* Use Cases */</p> <hr /> <div>{{Infobox Project<br /> |name = Assignment Resubmission History<br /> |state = Proposed<br /> |tracker = MDL-36804<br /> |discussion = https://moodle.org/mod/forum/discuss.php?d=205060<br /> }}<br /> <br /> ='''Assignment Resubmission History'''=<br /> <br /> This is a proposal for an additional feature for the Assignment module to retain a history of the submission by a student to the assignment.<br /> <br /> ='''Goals and rationale'''=<br /> The main goals of this feature are to :<br /> <br /> * Provide a better history of the student interactions with an assignment. <br /> * Make it easier for students to upload files to an assignment (without having to delete their original files first)<br /> * Provide an audit trail for internal and external verification of marked work<br /> <br /> ='''Overview'''=<br /> <br /> This is a feature request from the community to retain the list of submissions by a student instead of overwriting the previous submission.<br /> <br /> ----<br /> other thoughts: <br /> <br /> Currently, when a student RESUBMITS an assignment, the original submission, grade and feedback are all lost. This inhibits the ability of both the teacher and student to LEARN FROM and BUILD ON previous efforts and feedback. <br /> <br /> Is the student’s understanding of the assignment getting better or worse? How can the teacher tell without seeing the student’s progression over time? <br /> <br /> '''Example 1:''' An assignment has tasks A, B and C. The student submits A and B but not C, which the student does not understand. Teacher feedback informs student to resubmit since she “forgot” task C. Again, the student resubmits parts A and B, but not C. Since a RESUBMISSION looks just like a FIRST SUBMISSION, this could happen many times without the teacher realizing that the student has repeatedly skipped task C (especially if the teacher has many students/classes). <br /> <br /> '''Example 2:''' An assignment asks students to write a clear and concise paragraph that expresses an opinion about a controversial issue. A student submits a paragraph that contains some good but obvious arguments as well as a few other points that are original but undeveloped. The teacher’s feedback challenges the student to explore her original thoughts. The student’s resubmission expands on the obvious arguments but completely omits the more original ideas. When the teacher sees the resubmission, all traces of the original ideas (as well as the feedback) are gone. The teacher, who has over 100 students, does not recall that this student had expressed some unique but unexplored views. A grade is given but an opportunity for real learning/teaching is lost.<br /> <br /> ='''New settings'''=<br /> * "Submission history" Yes|No - If enabled, each student submission to the assignment will be recorded at submission time and a teacher will be able to see each submission by an individual student.<br /> <br /> <br /> ----<br /> other thoughts:<br /> <br /> - When a student is required to RESUBMIT an assignment, all previous submission (including the grade, feedback, timestamp, and any other relevant info.) should be shown in a chronological order. <br /> <br /> - Similarly, when a teacher is marking/grading an assignment, all previous submission (including the grade, feedback, timestamp, and any other relevant info.) should be shown in a chronological order. <br /> <br /> - On a separate note, since the assignment module contains a “grade-to-pass’ feature that allows teachers to specify an acceptable grade, there should be a corresponding setting that allows for resubmission IF the grade-to-pass is not met.<br /> <br /> ='''Interface changes'''=<br /> A new entry will be put in the drop down menu on the grading table for each submission to view the submission history for that student. This will go to a new page in the assignment that displays the student details, as well of a list of the submissions by that student. For each submission it will contain the time and date, any files, online text or custom submission data. (Question: Does it need grades/feedback?)<br /> <br /> Although feedback for each historical submission can be collectively held in the Feedback comments text area (perhaps under headings "First attempt Feedback" or similar) or by file upload a better solution might be to archive feedback linked to each submission. This is more suited to evidence requirements in most organisations as feedback cannot then be altered. On the assumption that this would require a lot more work this should be dropped rather than holding up the main feature of allowing resubmissions properly. (Question answered?) -I'm not sure what you mean here. Can you explain? Are you suggestion we drop the feedback from the history? If so, I would suggest that we keep it since it is a crucial part of the process.<br /> <br /> -----<br /> Other thoughts:<br /> <br /> Something to consider: Implementing this feature may require that we rethink the “revert to draft” function that’s currently in place. <br /> The current “revert to draft” feature asks students to CHANGE / REPLACE their answer. If I understand this feature correctly, when a submission is reverted to draft, it is NOT graded – it is as if the student NEVER SUBMITTED it in the first place. The new feature that is being proposed here is more like a traditional “Request Resubmission” feature, which asks the students to BUILD ON / LEARN FROM their previous submissions.<br /> Whether we continue to use term “revert to draft” or adopt “request resubmission”, the goal here is to move from the current method of “undo” to one of “redo”. <br /> <br /> Interface suggestion:<br /> <br /> - Controlling the resubmission option: Bring back the "allow resubmission" option in the Assignment settings and add a "conditional resubmission" (based on "grade-to-pass") setting, like this: http://screencast.com/t/172nIJmiWLS. To make the conditional resubmission option easier to manage, the grade-to-pass value (which is buried in the gradebook) should also be added to the Assignment settings, like this: http://screencast.com/t/a9zUxjDP2w. In effect, if a student is able to resubmit an assignment, she would see a "Resubmit this Assignment" button. Clicking on this button would "revert the assignment to draft" but also save the past submission (along with grade, teacher feedback, etc.) <br /> <br /> - For students - Showing current and past submission: Keep a running list of all submissions at the bottom of the assignment, like this: http://screencast.com/t/tROSTGirFqf (alternatively, you could have a "Show past submissions" button").<br /> <br /> - For teachers - Showing current and past submission: Same idea as the student view, except that it would show up in the marking interface. Also, for quick identification, the "submission status" could show the submission number (attempt), like this: http://screencast.com/t/sU1d7qC4gU.<br /> <br /> ='''Use Cases'''=<br /> ''' A teacher wants to give feedback and let a student upload a new file submission to the assignment '''<br /> * Create an assignment with file submissions enabled, "Submission history" enabled and "Require students click submit" disabled<br /> * Wait until a student uploads a file submision<br /> * Grade the submission and give some feedback<br /> * Revert the submission to draft to allow the student to upload a new file<br /> * The student should see a readonly version of their original submission plus any feedback from the teacher<br /> * They should now be able to upload a new file without being able to delete their first submission<br /> <br /> <br /> ----<br /> <br /> Other thoughts:<br /> <br /> * Example 1: A teacher creates an assignment with a conditional resubmission, which means that students are allowed to resubmit until they get a passing mark.<br /> To do this, the teacher sets these two additional options within the assignment settings page:<br /> Allow resubmissions: Yes, if grade-to-pass is not met<br /> Grade to Pass: X<br /> <br /> * Example 2: A teacher want to create an assignment that allows for an unlimited number of submissions regardless of the grade. To do this, the teacher sets this option:<br /> Allow resubmissions: Yes, always<br /> <br /> * Example 3: A teacher does not want to allow any resubmissions. To to this, the teacher would set this option:<br /> Allow resubmissions: No<br /> <br /> ='''User Interface'''=<br /> Some screenshot mockups will help the community visualise this feature.</div>

Fern https://docs.moodle.org/dev/index.php?title=Assignment_Resubmission_History_Proposal&diff=36654 Assignment Resubmission History Proposal 2012-11-27T17:20:38Z

<p>Fern: /* Interface changes */</p> <hr /> <div>{{Infobox Project<br /> |name = Assignment Resubmission History<br /> |state = Proposed<br /> |tracker = MDL-36804<br /> |discussion = https://moodle.org/mod/forum/discuss.php?d=205060<br /> }}<br /> <br /> ='''Assignment Resubmission History'''=<br /> <br /> This is a proposal for an additional feature for the Assignment module to retain a history of the submission by a student to the assignment.<br /> <br /> ='''Goals and rationale'''=<br /> The main goals of this feature are to :<br /> <br /> * Provide a better history of the student interactions with an assignment. <br /> * Make it easier for students to upload files to an assignment (without having to delete their original files first)<br /> * Provide an audit trail for internal and external verification of marked work<br /> <br /> ='''Overview'''=<br /> <br /> This is a feature request from the community to retain the list of submissions by a student instead of overwriting the previous submission.<br /> <br /> ----<br /> other thoughts: <br /> <br /> Currently, when a student RESUBMITS an assignment, the original submission, grade and feedback are all lost. This inhibits the ability of both the teacher and student to LEARN FROM and BUILD ON previous efforts and feedback. <br /> <br /> Is the student’s understanding of the assignment getting better or worse? How can the teacher tell without seeing the student’s progression over time? <br /> <br /> '''Example 1:''' An assignment has tasks A, B and C. The student submits A and B but not C, which the student does not understand. Teacher feedback informs student to resubmit since she “forgot” task C. Again, the student resubmits parts A and B, but not C. Since a RESUBMISSION looks just like a FIRST SUBMISSION, this could happen many times without the teacher realizing that the student has repeatedly skipped task C (especially if the teacher has many students/classes). <br /> <br /> '''Example 2:''' An assignment asks students to write a clear and concise paragraph that expresses an opinion about a controversial issue. A student submits a paragraph that contains some good but obvious arguments as well as a few other points that are original but undeveloped. The teacher’s feedback challenges the student to explore her original thoughts. The student’s resubmission expands on the obvious arguments but completely omits the more original ideas. When the teacher sees the resubmission, all traces of the original ideas (as well as the feedback) are gone. The teacher, who has over 100 students, does not recall that this student had expressed some unique but unexplored views. A grade is given but an opportunity for real learning/teaching is lost.<br /> <br /> ='''New settings'''=<br /> * "Submission history" Yes|No - If enabled, each student submission to the assignment will be recorded at submission time and a teacher will be able to see each submission by an individual student.<br /> <br /> <br /> ----<br /> other thoughts:<br /> <br /> - When a student is required to RESUBMIT an assignment, all previous submission (including the grade, feedback, timestamp, and any other relevant info.) should be shown in a chronological order. <br /> <br /> - Similarly, when a teacher is marking/grading an assignment, all previous submission (including the grade, feedback, timestamp, and any other relevant info.) should be shown in a chronological order. <br /> <br /> - On a separate note, since the assignment module contains a “grade-to-pass’ feature that allows teachers to specify an acceptable grade, there should be a corresponding setting that allows for resubmission IF the grade-to-pass is not met.<br /> <br /> ='''Interface changes'''=<br /> A new entry will be put in the drop down menu on the grading table for each submission to view the submission history for that student. This will go to a new page in the assignment that displays the student details, as well of a list of the submissions by that student. For each submission it will contain the time and date, any files, online text or custom submission data. (Question: Does it need grades/feedback?)<br /> <br /> Although feedback for each historical submission can be collectively held in the Feedback comments text area (perhaps under headings "First attempt Feedback" or similar) or by file upload a better solution might be to archive feedback linked to each submission. This is more suited to evidence requirements in most organisations as feedback cannot then be altered. On the assumption that this would require a lot more work this should be dropped rather than holding up the main feature of allowing resubmissions properly. (Question answered?) -I'm not sure what you mean here. Can you explain? Are you suggestion we drop the feedback from the history? If so, I would suggest that we keep it since it is a crucial part of the process.<br /> <br /> -----<br /> Other thoughts:<br /> <br /> Something to consider: Implementing this feature may require that we rethink the “revert to draft” function that’s currently in place. <br /> The current “revert to draft” feature asks students to CHANGE / REPLACE their answer. If I understand this feature correctly, when a submission is reverted to draft, it is NOT graded – it is as if the student NEVER SUBMITTED it in the first place. The new feature that is being proposed here is more like a traditional “Request Resubmission” feature, which asks the students to BUILD ON / LEARN FROM their previous submissions.<br /> Whether we continue to use term “revert to draft” or adopt “request resubmission”, the goal here is to move from the current method of “undo” to one of “redo”. <br /> <br /> Interface suggestion:<br /> <br /> - Controlling the resubmission option: Bring back the "allow resubmission" option in the Assignment settings and add a "conditional resubmission" (based on "grade-to-pass") setting, like this: http://screencast.com/t/172nIJmiWLS. To make the conditional resubmission option easier to manage, the grade-to-pass value (which is buried in the gradebook) should also be added to the Assignment settings, like this: http://screencast.com/t/a9zUxjDP2w. In effect, if a student is able to resubmit an assignment, she would see a "Resubmit this Assignment" button. Clicking on this button would "revert the assignment to draft" but also save the past submission (along with grade, teacher feedback, etc.) <br /> <br /> - For students - Showing current and past submission: Keep a running list of all submissions at the bottom of the assignment, like this: http://screencast.com/t/tROSTGirFqf (alternatively, you could have a "Show past submissions" button").<br /> <br /> - For teachers - Showing current and past submission: Same idea as the student view, except that it would show up in the marking interface. Also, for quick identification, the "submission status" could show the submission number (attempt), like this: http://screencast.com/t/sU1d7qC4gU.<br /> <br /> ='''Use Cases'''=<br /> ''' A teacher wants to give feedback and let a student upload a new file submission to the assignment '''<br /> * Create an assignment with file submissions enabled, "Submission history" enabled and "Require students click submit" disabled<br /> * Wait until a student uploads a file submision<br /> * Grade the submission and give some feedback<br /> * Revert the submission to draft to allow the student to upload a new file<br /> * The student should see a readonly version of their original submission plus any feedback from the teacher<br /> * They should now be able to upload a new file without being able to delete their first submission<br /> <br /> ='''User Interface'''=<br /> Some screenshot mockups will help the community visualise this feature.</div>

Fern https://docs.moodle.org/dev/index.php?title=Assignment_Resubmission_History_Proposal&diff=36653 Assignment Resubmission History Proposal 2012-11-27T17:18:28Z

<p>Fern: /* Interface changes */</p> <hr /> <div>{{Infobox Project<br /> |name = Assignment Resubmission History<br /> |state = Proposed<br /> |tracker = MDL-36804<br /> |discussion = https://moodle.org/mod/forum/discuss.php?d=205060<br /> }}<br /> <br /> ='''Assignment Resubmission History'''=<br /> <br /> This is a proposal for an additional feature for the Assignment module to retain a history of the submission by a student to the assignment.<br /> <br /> ='''Goals and rationale'''=<br /> The main goals of this feature are to :<br /> <br /> * Provide a better history of the student interactions with an assignment. <br /> * Make it easier for students to upload files to an assignment (without having to delete their original files first)<br /> * Provide an audit trail for internal and external verification of marked work<br /> <br /> ='''Overview'''=<br /> <br /> This is a feature request from the community to retain the list of submissions by a student instead of overwriting the previous submission.<br /> <br /> ----<br /> other thoughts: <br /> <br /> Currently, when a student RESUBMITS an assignment, the original submission, grade and feedback are all lost. This inhibits the ability of both the teacher and student to LEARN FROM and BUILD ON previous efforts and feedback. <br /> <br /> Is the student’s understanding of the assignment getting better or worse? How can the teacher tell without seeing the student’s progression over time? <br /> <br /> '''Example 1:''' An assignment has tasks A, B and C. The student submits A and B but not C, which the student does not understand. Teacher feedback informs student to resubmit since she “forgot” task C. Again, the student resubmits parts A and B, but not C. Since a RESUBMISSION looks just like a FIRST SUBMISSION, this could happen many times without the teacher realizing that the student has repeatedly skipped task C (especially if the teacher has many students/classes). <br /> <br /> '''Example 2:''' An assignment asks students to write a clear and concise paragraph that expresses an opinion about a controversial issue. A student submits a paragraph that contains some good but obvious arguments as well as a few other points that are original but undeveloped. The teacher’s feedback challenges the student to explore her original thoughts. The student’s resubmission expands on the obvious arguments but completely omits the more original ideas. When the teacher sees the resubmission, all traces of the original ideas (as well as the feedback) are gone. The teacher, who has over 100 students, does not recall that this student had expressed some unique but unexplored views. A grade is given but an opportunity for real learning/teaching is lost.<br /> <br /> ='''New settings'''=<br /> * "Submission history" Yes|No - If enabled, each student submission to the assignment will be recorded at submission time and a teacher will be able to see each submission by an individual student.<br /> <br /> <br /> ----<br /> other thoughts:<br /> <br /> - When a student is required to RESUBMIT an assignment, all previous submission (including the grade, feedback, timestamp, and any other relevant info.) should be shown in a chronological order. <br /> <br /> - Similarly, when a teacher is marking/grading an assignment, all previous submission (including the grade, feedback, timestamp, and any other relevant info.) should be shown in a chronological order. <br /> <br /> - On a separate note, since the assignment module contains a “grade-to-pass’ feature that allows teachers to specify an acceptable grade, there should be a corresponding setting that allows for resubmission IF the grade-to-pass is not met.<br /> <br /> ='''Interface changes'''=<br /> A new entry will be put in the drop down menu on the grading table for each submission to view the submission history for that student. This will go to a new page in the assignment that displays the student details, as well of a list of the submissions by that student. For each submission it will contain the time and date, any files, online text or custom submission data. (Question: Does it need grades/feedback?)<br /> <br /> Although feedback for each historical submission can be collectively held in the Feedback comments text area (perhaps under headings "First attempt Feedback" or similar) or by file upload a better solution might be to archive feedback linked to each submission. This is more suited to evidence requirements in most organisations as feedback cannot then be altered. On the assumption that this would require a lot more work this should be dropped rather than holding up the main feature of allowing resubmissions properly. (Question answered?) -I'm not sure what you mean here. Can you explain? Are you suggestion we drop the feedback from the history? If so, I would suggest that we keep it since it is a crucial part of the process.<br /> <br /> -----<br /> Other thoughts:<br /> <br /> Something to consider: Implementing this feature may require that we rethink the “revert to draft” function that’s currently in place. <br /> The current “revert to draft” feature asks students to CHANGE / REPLACE their answer. If I understand this feature correctly, when a submission is reverted to draft, it is NOT graded – it is as if the student NEVER SUBMITTED it in the first place. The new feature that is being proposed here is more like a “Request Resubmission” feature, which ARCHIVES all previous attempts are then asks the students to BUILD ON / LEARN FROM their previous submissions.<br /> Whether we continue to use term “revert to draft” or adopt “request resubmission”, the goal in this proposal is to move from the current method of “undo” to one of “redo”. '''<br /> <br /> Interface suggestion:<br /> <br /> - Controlling the resubmission option: Bring back the "allow resubmission" option in the Assignment settings and add a "conditional resubmission" (based on "grade-to-pass") setting, like this: http://screencast.com/t/172nIJmiWLS. To make the conditional resubmission option easier to manage, the grade-to-pass value (which is buried in the gradebook) should also be added to the Assignment settings, like this: http://screencast.com/t/a9zUxjDP2w. In effect, if a student is able to resubmit an assignment, she would see a "Resubmit this Assignment" button. Clicking on this button would "revert the assignment to draft" but also save the past submission (along with grade, teacher feedback, etc.) <br /> <br /> - For students - Showing current and past submission: Keep a running list of all submissions at the bottom of the assignment, like this: http://screencast.com/t/tROSTGirFqf (alternatively, you could have a "Show past submissions" button").<br /> <br /> - For teachers - Showing current and past submission: Same idea as the student view, except that it would show up in the marking interface. Also, for quick identification, the "submission status" could show the submission number (attempt), like this: http://screencast.com/t/sU1d7qC4gU.<br /> <br /> ='''Use Cases'''=<br /> ''' A teacher wants to give feedback and let a student upload a new file submission to the assignment '''<br /> * Create an assignment with file submissions enabled, "Submission history" enabled and "Require students click submit" disabled<br /> * Wait until a student uploads a file submision<br /> * Grade the submission and give some feedback<br /> * Revert the submission to draft to allow the student to upload a new file<br /> * The student should see a readonly version of their original submission plus any feedback from the teacher<br /> * They should now be able to upload a new file without being able to delete their first submission<br /> <br /> ='''User Interface'''=<br /> Some screenshot mockups will help the community visualise this feature.</div>

Fern https://docs.moodle.org/dev/index.php?title=Assignment_Resubmission_History_Proposal&diff=36652 Assignment Resubmission History Proposal 2012-11-27T17:15:24Z

<p>Fern: /* Overview */</p> <hr /> <div>{{Infobox Project<br /> |name = Assignment Resubmission History<br /> |state = Proposed<br /> |tracker = MDL-36804<br /> |discussion = https://moodle.org/mod/forum/discuss.php?d=205060<br /> }}<br /> <br /> ='''Assignment Resubmission History'''=<br /> <br /> This is a proposal for an additional feature for the Assignment module to retain a history of the submission by a student to the assignment.<br /> <br /> ='''Goals and rationale'''=<br /> The main goals of this feature are to :<br /> <br /> * Provide a better history of the student interactions with an assignment. <br /> * Make it easier for students to upload files to an assignment (without having to delete their original files first)<br /> * Provide an audit trail for internal and external verification of marked work<br /> <br /> ='''Overview'''=<br /> <br /> This is a feature request from the community to retain the list of submissions by a student instead of overwriting the previous submission.<br /> <br /> ----<br /> other thoughts: <br /> <br /> Currently, when a student RESUBMITS an assignment, the original submission, grade and feedback are all lost. This inhibits the ability of both the teacher and student to LEARN FROM and BUILD ON previous efforts and feedback. <br /> <br /> Is the student’s understanding of the assignment getting better or worse? How can the teacher tell without seeing the student’s progression over time? <br /> <br /> '''Example 1:''' An assignment has tasks A, B and C. The student submits A and B but not C, which the student does not understand. Teacher feedback informs student to resubmit since she “forgot” task C. Again, the student resubmits parts A and B, but not C. Since a RESUBMISSION looks just like a FIRST SUBMISSION, this could happen many times without the teacher realizing that the student has repeatedly skipped task C (especially if the teacher has many students/classes). <br /> <br /> '''Example 2:''' An assignment asks students to write a clear and concise paragraph that expresses an opinion about a controversial issue. A student submits a paragraph that contains some good but obvious arguments as well as a few other points that are original but undeveloped. The teacher’s feedback challenges the student to explore her original thoughts. The student’s resubmission expands on the obvious arguments but completely omits the more original ideas. When the teacher sees the resubmission, all traces of the original ideas (as well as the feedback) are gone. The teacher, who has over 100 students, does not recall that this student had expressed some unique but unexplored views. A grade is given but an opportunity for real learning/teaching is lost.<br /> <br /> ='''New settings'''=<br /> * "Submission history" Yes|No - If enabled, each student submission to the assignment will be recorded at submission time and a teacher will be able to see each submission by an individual student.<br /> <br /> <br /> ----<br /> other thoughts:<br /> <br /> - When a student is required to RESUBMIT an assignment, all previous submission (including the grade, feedback, timestamp, and any other relevant info.) should be shown in a chronological order. <br /> <br /> - Similarly, when a teacher is marking/grading an assignment, all previous submission (including the grade, feedback, timestamp, and any other relevant info.) should be shown in a chronological order. <br /> <br /> - On a separate note, since the assignment module contains a “grade-to-pass’ feature that allows teachers to specify an acceptable grade, there should be a corresponding setting that allows for resubmission IF the grade-to-pass is not met.<br /> <br /> ='''Interface changes'''=<br /> A new entry will be put in the drop down menu on the grading table for each submission to view the submission history for that student. This will go to a new page in the assignment that displays the student details, as well of a list of the submissions by that student. For each submission it will contain the time and date, any files, online text or custom submission data. (Question: Does it need grades/feedback?)<br /> <br /> Although feedback for each historical submission can be collectively held in the Feedback comments text area (perhaps under headings "First attempt Feedback" or similar) or by file upload a better solution might be to archive feedback linked to each submission. This is more suited to evidence requirements in most organisations as feedback cannot then be altered. On the assumption that this would require a lot more work this should be dropped rather than holding up the main feature of allowing resubmissions properly. (Question answered?) -I'm not sure what you mean here. Can you explain? Are you suggestion we drop the feedback from the history? If so, I would suggest that we keep it since it is a crucial part of the process.<br /> <br /> -----<br /> Other thoughts:<br /> <br /> '''Implementing this feature may require that we rethink the “revert to draft” function that’s currently in place.<br /> <br /> The current “revert to draft” feature asks students to CHANGE / REPLACE their answer. If I understand this feature correctly, when a submission is reverted to draft, it is NOT graded – it is as if the student NEVER SUBMITTED it in the first place. <br /> <br /> The new feature that is being proposed here is more like a “Request Resubmission” feature, which ARCHIVES all previous attempts are then asks the students to BUILD ON / LEARN FROM their previous submissions. <br /> <br /> Whether we continue to use term “revert to draft” or adopt “request resubmission”, the goal in this proposal is to move from the current method of “undo” to one of “redo”. '''<br /> <br /> ='''Use Cases'''=<br /> ''' A teacher wants to give feedback and let a student upload a new file submission to the assignment '''<br /> * Create an assignment with file submissions enabled, "Submission history" enabled and "Require students click submit" disabled<br /> * Wait until a student uploads a file submision<br /> * Grade the submission and give some feedback<br /> * Revert the submission to draft to allow the student to upload a new file<br /> * The student should see a readonly version of their original submission plus any feedback from the teacher<br /> * They should now be able to upload a new file without being able to delete their first submission<br /> <br /> ='''User Interface'''=<br /> Some screenshot mockups will help the community visualise this feature.</div>

Fern https://docs.moodle.org/dev/index.php?title=Assignment_Resubmission_History_Proposal&diff=36651 Assignment Resubmission History Proposal 2012-11-27T17:15:01Z

<p>Fern: /* New settings */</p> <hr /> <div>{{Infobox Project<br /> |name = Assignment Resubmission History<br /> |state = Proposed<br /> |tracker = MDL-36804<br /> |discussion = https://moodle.org/mod/forum/discuss.php?d=205060<br /> }}<br /> <br /> ='''Assignment Resubmission History'''=<br /> <br /> This is a proposal for an additional feature for the Assignment module to retain a history of the submission by a student to the assignment.<br /> <br /> ='''Goals and rationale'''=<br /> The main goals of this feature are to :<br /> <br /> * Provide a better history of the student interactions with an assignment. <br /> * Make it easier for students to upload files to an assignment (without having to delete their original files first)<br /> * Provide an audit trail for internal and external verification of marked work<br /> <br /> ='''Overview'''=<br /> <br /> This is a feature request from the community to retain the list of submissions by a student instead of overwriting the previous submission.<br /> <br /> ----<br /> Currently, when a student RESUBMITS an assignment, the original submission, grade and feedback are all lost. This inhibits the ability of both the teacher and student to LEARN FROM and BUILD ON previous efforts and feedback. <br /> <br /> Is the student’s understanding of the assignment getting better or worse? How can the teacher tell without seeing the student’s progression over time? <br /> <br /> '''Example 1:''' An assignment has tasks A, B and C. The student submits A and B but not C, which the student does not understand. Teacher feedback informs student to resubmit since she “forgot” task C. Again, the student resubmits parts A and B, but not C. Since a RESUBMISSION looks just like a FIRST SUBMISSION, this could happen many times without the teacher realizing that the student has repeatedly skipped task C (especially if the teacher has many students/classes). <br /> <br /> '''Example 2:''' An assignment asks students to write a clear and concise paragraph that expresses an opinion about a controversial issue. A student submits a paragraph that contains some good but obvious arguments as well as a few other points that are original but undeveloped. The teacher’s feedback challenges the student to explore her original thoughts. The student’s resubmission expands on the obvious arguments but completely omits the more original ideas. When the teacher sees the resubmission, all traces of the original ideas (as well as the feedback) are gone. The teacher, who has over 100 students, does not recall that this student had expressed some unique but unexplored views. A grade is given but an opportunity for real learning/teaching is lost.<br /> <br /> ='''New settings'''=<br /> * "Submission history" Yes|No - If enabled, each student submission to the assignment will be recorded at submission time and a teacher will be able to see each submission by an individual student.<br /> <br /> <br /> ----<br /> other thoughts:<br /> <br /> - When a student is required to RESUBMIT an assignment, all previous submission (including the grade, feedback, timestamp, and any other relevant info.) should be shown in a chronological order. <br /> <br /> - Similarly, when a teacher is marking/grading an assignment, all previous submission (including the grade, feedback, timestamp, and any other relevant info.) should be shown in a chronological order. <br /> <br /> - On a separate note, since the assignment module contains a “grade-to-pass’ feature that allows teachers to specify an acceptable grade, there should be a corresponding setting that allows for resubmission IF the grade-to-pass is not met.<br /> <br /> ='''Interface changes'''=<br /> A new entry will be put in the drop down menu on the grading table for each submission to view the submission history for that student. This will go to a new page in the assignment that displays the student details, as well of a list of the submissions by that student. For each submission it will contain the time and date, any files, online text or custom submission data. (Question: Does it need grades/feedback?)<br /> <br /> Although feedback for each historical submission can be collectively held in the Feedback comments text area (perhaps under headings "First attempt Feedback" or similar) or by file upload a better solution might be to archive feedback linked to each submission. This is more suited to evidence requirements in most organisations as feedback cannot then be altered. On the assumption that this would require a lot more work this should be dropped rather than holding up the main feature of allowing resubmissions properly. (Question answered?) -I'm not sure what you mean here. Can you explain? Are you suggestion we drop the feedback from the history? If so, I would suggest that we keep it since it is a crucial part of the process.<br /> <br /> -----<br /> Other thoughts:<br /> <br /> '''Implementing this feature may require that we rethink the “revert to draft” function that’s currently in place.<br /> <br /> The current “revert to draft” feature asks students to CHANGE / REPLACE their answer. If I understand this feature correctly, when a submission is reverted to draft, it is NOT graded – it is as if the student NEVER SUBMITTED it in the first place. <br /> <br /> The new feature that is being proposed here is more like a “Request Resubmission” feature, which ARCHIVES all previous attempts are then asks the students to BUILD ON / LEARN FROM their previous submissions. <br /> <br /> Whether we continue to use term “revert to draft” or adopt “request resubmission”, the goal in this proposal is to move from the current method of “undo” to one of “redo”. '''<br /> <br /> ='''Use Cases'''=<br /> ''' A teacher wants to give feedback and let a student upload a new file submission to the assignment '''<br /> * Create an assignment with file submissions enabled, "Submission history" enabled and "Require students click submit" disabled<br /> * Wait until a student uploads a file submision<br /> * Grade the submission and give some feedback<br /> * Revert the submission to draft to allow the student to upload a new file<br /> * The student should see a readonly version of their original submission plus any feedback from the teacher<br /> * They should now be able to upload a new file without being able to delete their first submission<br /> <br /> ='''User Interface'''=<br /> Some screenshot mockups will help the community visualise this feature.</div>

Fern https://docs.moodle.org/dev/index.php?title=Assignment_Resubmission_History_Proposal&diff=36650 Assignment Resubmission History Proposal 2012-11-27T17:14:28Z

<p>Fern: /* New settings */</p> <hr /> <div>{{Infobox Project<br /> |name = Assignment Resubmission History<br /> |state = Proposed<br /> |tracker = MDL-36804<br /> |discussion = https://moodle.org/mod/forum/discuss.php?d=205060<br /> }}<br /> <br /> ='''Assignment Resubmission History'''=<br /> <br /> This is a proposal for an additional feature for the Assignment module to retain a history of the submission by a student to the assignment.<br /> <br /> ='''Goals and rationale'''=<br /> The main goals of this feature are to :<br /> <br /> * Provide a better history of the student interactions with an assignment. <br /> * Make it easier for students to upload files to an assignment (without having to delete their original files first)<br /> * Provide an audit trail for internal and external verification of marked work<br /> <br /> ='''Overview'''=<br /> <br /> This is a feature request from the community to retain the list of submissions by a student instead of overwriting the previous submission.<br /> <br /> ----<br /> Currently, when a student RESUBMITS an assignment, the original submission, grade and feedback are all lost. This inhibits the ability of both the teacher and student to LEARN FROM and BUILD ON previous efforts and feedback. <br /> <br /> Is the student’s understanding of the assignment getting better or worse? How can the teacher tell without seeing the student’s progression over time? <br /> <br /> '''Example 1:''' An assignment has tasks A, B and C. The student submits A and B but not C, which the student does not understand. Teacher feedback informs student to resubmit since she “forgot” task C. Again, the student resubmits parts A and B, but not C. Since a RESUBMISSION looks just like a FIRST SUBMISSION, this could happen many times without the teacher realizing that the student has repeatedly skipped task C (especially if the teacher has many students/classes). <br /> <br /> '''Example 2:''' An assignment asks students to write a clear and concise paragraph that expresses an opinion about a controversial issue. A student submits a paragraph that contains some good but obvious arguments as well as a few other points that are original but undeveloped. The teacher’s feedback challenges the student to explore her original thoughts. The student’s resubmission expands on the obvious arguments but completely omits the more original ideas. When the teacher sees the resubmission, all traces of the original ideas (as well as the feedback) are gone. The teacher, who has over 100 students, does not recall that this student had expressed some unique but unexplored views. A grade is given but an opportunity for real learning/teaching is lost.<br /> <br /> ='''New settings'''=<br /> * "Submission history" Yes|No - If enabled, each student submission to the assignment will be recorded at submission time and a teacher will be able to see each submission by an individual student.<br /> <br /> <br /> ----<br /> <br /> - When a student is required to RESUBMIT an assignment, all previous submission (including the grade, feedback, timestamp, and any other relevant info.) should be shown in a chronological order. <br /> <br /> - Similarly, when a teacher is marking/grading an assignment, all previous submission (including the grade, feedback, timestamp, and any other relevant info.) should be shown in a chronological order. <br /> <br /> - On a separate note, since the assignment module contains a “grade-to-pass’ feature that allows teachers to specify an acceptable grade, there should be a corresponding setting that allows for resubmission IF the grade-to-pass is not met.<br /> <br /> ='''Interface changes'''=<br /> A new entry will be put in the drop down menu on the grading table for each submission to view the submission history for that student. This will go to a new page in the assignment that displays the student details, as well of a list of the submissions by that student. For each submission it will contain the time and date, any files, online text or custom submission data. (Question: Does it need grades/feedback?)<br /> <br /> Although feedback for each historical submission can be collectively held in the Feedback comments text area (perhaps under headings "First attempt Feedback" or similar) or by file upload a better solution might be to archive feedback linked to each submission. This is more suited to evidence requirements in most organisations as feedback cannot then be altered. On the assumption that this would require a lot more work this should be dropped rather than holding up the main feature of allowing resubmissions properly. (Question answered?) -I'm not sure what you mean here. Can you explain? Are you suggestion we drop the feedback from the history? If so, I would suggest that we keep it since it is a crucial part of the process.<br /> <br /> -----<br /> Other thoughts:<br /> <br /> '''Implementing this feature may require that we rethink the “revert to draft” function that’s currently in place.<br /> <br /> The current “revert to draft” feature asks students to CHANGE / REPLACE their answer. If I understand this feature correctly, when a submission is reverted to draft, it is NOT graded – it is as if the student NEVER SUBMITTED it in the first place. <br /> <br /> The new feature that is being proposed here is more like a “Request Resubmission” feature, which ARCHIVES all previous attempts are then asks the students to BUILD ON / LEARN FROM their previous submissions. <br /> <br /> Whether we continue to use term “revert to draft” or adopt “request resubmission”, the goal in this proposal is to move from the current method of “undo” to one of “redo”. '''<br /> <br /> ='''Use Cases'''=<br /> ''' A teacher wants to give feedback and let a student upload a new file submission to the assignment '''<br /> * Create an assignment with file submissions enabled, "Submission history" enabled and "Require students click submit" disabled<br /> * Wait until a student uploads a file submision<br /> * Grade the submission and give some feedback<br /> * Revert the submission to draft to allow the student to upload a new file<br /> * The student should see a readonly version of their original submission plus any feedback from the teacher<br /> * They should now be able to upload a new file without being able to delete their first submission<br /> <br /> ='''User Interface'''=<br /> Some screenshot mockups will help the community visualise this feature.</div>

Fern https://docs.moodle.org/dev/index.php?title=Assignment_Resubmission_History_Proposal&diff=36649 Assignment Resubmission History Proposal 2012-11-27T17:13:58Z

<p>Fern: /* New settings */</p> <hr /> <div>{{Infobox Project<br /> |name = Assignment Resubmission History<br /> |state = Proposed<br /> |tracker = MDL-36804<br /> |discussion = https://moodle.org/mod/forum/discuss.php?d=205060<br /> }}<br /> <br /> ='''Assignment Resubmission History'''=<br /> <br /> This is a proposal for an additional feature for the Assignment module to retain a history of the submission by a student to the assignment.<br /> <br /> ='''Goals and rationale'''=<br /> The main goals of this feature are to :<br /> <br /> * Provide a better history of the student interactions with an assignment. <br /> * Make it easier for students to upload files to an assignment (without having to delete their original files first)<br /> * Provide an audit trail for internal and external verification of marked work<br /> <br /> ='''Overview'''=<br /> <br /> This is a feature request from the community to retain the list of submissions by a student instead of overwriting the previous submission.<br /> <br /> ----<br /> Currently, when a student RESUBMITS an assignment, the original submission, grade and feedback are all lost. This inhibits the ability of both the teacher and student to LEARN FROM and BUILD ON previous efforts and feedback. <br /> <br /> Is the student’s understanding of the assignment getting better or worse? How can the teacher tell without seeing the student’s progression over time? <br /> <br /> '''Example 1:''' An assignment has tasks A, B and C. The student submits A and B but not C, which the student does not understand. Teacher feedback informs student to resubmit since she “forgot” task C. Again, the student resubmits parts A and B, but not C. Since a RESUBMISSION looks just like a FIRST SUBMISSION, this could happen many times without the teacher realizing that the student has repeatedly skipped task C (especially if the teacher has many students/classes). <br /> <br /> '''Example 2:''' An assignment asks students to write a clear and concise paragraph that expresses an opinion about a controversial issue. A student submits a paragraph that contains some good but obvious arguments as well as a few other points that are original but undeveloped. The teacher’s feedback challenges the student to explore her original thoughts. The student’s resubmission expands on the obvious arguments but completely omits the more original ideas. When the teacher sees the resubmission, all traces of the original ideas (as well as the feedback) are gone. The teacher, who has over 100 students, does not recall that this student had expressed some unique but unexplored views. A grade is given but an opportunity for real learning/teaching is lost.<br /> <br /> ='''New settings'''=<br /> * "Submission history" Yes|No - If enabled, each student submission to the assignment will be recorded at submission time and a teacher will be able to see each submission by an individual student.<br /> <br /> <br /> ----<br /> <br /> • When a student is required to RESUBMIT an assignment, all previous submission (including the grade, feedback, timestamp, and any other relevant info.) should be shown in a chronological order. <br /> • Similarly, when a teacher is marking/grading an assignment, all previous submission (including the grade, feedback, timestamp, and any other relevant info.) should be shown in a chronological order. <br /> • On a separate note, since the assignment module contains a “grade-to-pass’ feature that allows teachers to specify an acceptable grade, there should be a corresponding setting that allows for resubmission IF the grade-to-pass is not met.<br /> <br /> ='''Interface changes'''=<br /> A new entry will be put in the drop down menu on the grading table for each submission to view the submission history for that student. This will go to a new page in the assignment that displays the student details, as well of a list of the submissions by that student. For each submission it will contain the time and date, any files, online text or custom submission data. (Question: Does it need grades/feedback?)<br /> <br /> Although feedback for each historical submission can be collectively held in the Feedback comments text area (perhaps under headings "First attempt Feedback" or similar) or by file upload a better solution might be to archive feedback linked to each submission. This is more suited to evidence requirements in most organisations as feedback cannot then be altered. On the assumption that this would require a lot more work this should be dropped rather than holding up the main feature of allowing resubmissions properly. (Question answered?) -I'm not sure what you mean here. Can you explain? Are you suggestion we drop the feedback from the history? If so, I would suggest that we keep it since it is a crucial part of the process.<br /> <br /> -----<br /> Other thoughts:<br /> <br /> '''Implementing this feature may require that we rethink the “revert to draft” function that’s currently in place.<br /> <br /> The current “revert to draft” feature asks students to CHANGE / REPLACE their answer. If I understand this feature correctly, when a submission is reverted to draft, it is NOT graded – it is as if the student NEVER SUBMITTED it in the first place. <br /> <br /> The new feature that is being proposed here is more like a “Request Resubmission” feature, which ARCHIVES all previous attempts are then asks the students to BUILD ON / LEARN FROM their previous submissions. <br /> <br /> Whether we continue to use term “revert to draft” or adopt “request resubmission”, the goal in this proposal is to move from the current method of “undo” to one of “redo”. '''<br /> <br /> ='''Use Cases'''=<br /> ''' A teacher wants to give feedback and let a student upload a new file submission to the assignment '''<br /> * Create an assignment with file submissions enabled, "Submission history" enabled and "Require students click submit" disabled<br /> * Wait until a student uploads a file submision<br /> * Grade the submission and give some feedback<br /> * Revert the submission to draft to allow the student to upload a new file<br /> * The student should see a readonly version of their original submission plus any feedback from the teacher<br /> * They should now be able to upload a new file without being able to delete their first submission<br /> <br /> ='''User Interface'''=<br /> Some screenshot mockups will help the community visualise this feature.</div>

Fern https://docs.moodle.org/dev/index.php?title=Assignment_Resubmission_History_Proposal&diff=36648 Assignment Resubmission History Proposal 2012-11-27T17:12:50Z

<p>Fern: /* Interface changes */</p> <hr /> <div>{{Infobox Project<br /> |name = Assignment Resubmission History<br /> |state = Proposed<br /> |tracker = MDL-36804<br /> |discussion = https://moodle.org/mod/forum/discuss.php?d=205060<br /> }}<br /> <br /> ='''Assignment Resubmission History'''=<br /> <br /> This is a proposal for an additional feature for the Assignment module to retain a history of the submission by a student to the assignment.<br /> <br /> ='''Goals and rationale'''=<br /> The main goals of this feature are to :<br /> <br /> * Provide a better history of the student interactions with an assignment. <br /> * Make it easier for students to upload files to an assignment (without having to delete their original files first)<br /> * Provide an audit trail for internal and external verification of marked work<br /> <br /> ='''Overview'''=<br /> <br /> This is a feature request from the community to retain the list of submissions by a student instead of overwriting the previous submission.<br /> <br /> ----<br /> Currently, when a student RESUBMITS an assignment, the original submission, grade and feedback are all lost. This inhibits the ability of both the teacher and student to LEARN FROM and BUILD ON previous efforts and feedback. <br /> <br /> Is the student’s understanding of the assignment getting better or worse? How can the teacher tell without seeing the student’s progression over time? <br /> <br /> '''Example 1:''' An assignment has tasks A, B and C. The student submits A and B but not C, which the student does not understand. Teacher feedback informs student to resubmit since she “forgot” task C. Again, the student resubmits parts A and B, but not C. Since a RESUBMISSION looks just like a FIRST SUBMISSION, this could happen many times without the teacher realizing that the student has repeatedly skipped task C (especially if the teacher has many students/classes). <br /> <br /> '''Example 2:''' An assignment asks students to write a clear and concise paragraph that expresses an opinion about a controversial issue. A student submits a paragraph that contains some good but obvious arguments as well as a few other points that are original but undeveloped. The teacher’s feedback challenges the student to explore her original thoughts. The student’s resubmission expands on the obvious arguments but completely omits the more original ideas. When the teacher sees the resubmission, all traces of the original ideas (as well as the feedback) are gone. The teacher, who has over 100 students, does not recall that this student had expressed some unique but unexplored views. A grade is given but an opportunity for real learning/teaching is lost.<br /> <br /> ='''New settings'''=<br /> * "Submission history" Yes|No - If enabled, each student submission to the assignment will be recorded at submission time and a teacher will be able to see each submission by an individual student.<br /> <br /> ='''Interface changes'''=<br /> A new entry will be put in the drop down menu on the grading table for each submission to view the submission history for that student. This will go to a new page in the assignment that displays the student details, as well of a list of the submissions by that student. For each submission it will contain the time and date, any files, online text or custom submission data. (Question: Does it need grades/feedback?)<br /> <br /> Although feedback for each historical submission can be collectively held in the Feedback comments text area (perhaps under headings "First attempt Feedback" or similar) or by file upload a better solution might be to archive feedback linked to each submission. This is more suited to evidence requirements in most organisations as feedback cannot then be altered. On the assumption that this would require a lot more work this should be dropped rather than holding up the main feature of allowing resubmissions properly. (Question answered?) -I'm not sure what you mean here. Can you explain? Are you suggestion we drop the feedback from the history? If so, I would suggest that we keep it since it is a crucial part of the process.<br /> <br /> -----<br /> Other thoughts:<br /> <br /> '''Implementing this feature may require that we rethink the “revert to draft” function that’s currently in place.<br /> <br /> The current “revert to draft” feature asks students to CHANGE / REPLACE their answer. If I understand this feature correctly, when a submission is reverted to draft, it is NOT graded – it is as if the student NEVER SUBMITTED it in the first place. <br /> <br /> The new feature that is being proposed here is more like a “Request Resubmission” feature, which ARCHIVES all previous attempts are then asks the students to BUILD ON / LEARN FROM their previous submissions. <br /> <br /> Whether we continue to use term “revert to draft” or adopt “request resubmission”, the goal in this proposal is to move from the current method of “undo” to one of “redo”. '''<br /> <br /> ='''Use Cases'''=<br /> ''' A teacher wants to give feedback and let a student upload a new file submission to the assignment '''<br /> * Create an assignment with file submissions enabled, "Submission history" enabled and "Require students click submit" disabled<br /> * Wait until a student uploads a file submision<br /> * Grade the submission and give some feedback<br /> * Revert the submission to draft to allow the student to upload a new file<br /> * The student should see a readonly version of their original submission plus any feedback from the teacher<br /> * They should now be able to upload a new file without being able to delete their first submission<br /> <br /> ='''User Interface'''=<br /> Some screenshot mockups will help the community visualise this feature.</div>

Fern https://docs.moodle.org/dev/index.php?title=Assignment_Resubmission_History_Proposal&diff=36647 Assignment Resubmission History Proposal 2012-11-27T17:06:19Z

<p>Fern: /* Interface changes */</p> <hr /> <div>{{Infobox Project<br /> |name = Assignment Resubmission History<br /> |state = Proposed<br /> |tracker = MDL-36804<br /> |discussion = https://moodle.org/mod/forum/discuss.php?d=205060<br /> }}<br /> <br /> ='''Assignment Resubmission History'''=<br /> <br /> This is a proposal for an additional feature for the Assignment module to retain a history of the submission by a student to the assignment.<br /> <br /> ='''Goals and rationale'''=<br /> The main goals of this feature are to :<br /> <br /> * Provide a better history of the student interactions with an assignment. <br /> * Make it easier for students to upload files to an assignment (without having to delete their original files first)<br /> * Provide an audit trail for internal and external verification of marked work<br /> <br /> ='''Overview'''=<br /> <br /> This is a feature request from the community to retain the list of submissions by a student instead of overwriting the previous submission.<br /> <br /> ----<br /> Currently, when a student RESUBMITS an assignment, the original submission, grade and feedback are all lost. This inhibits the ability of both the teacher and student to LEARN FROM and BUILD ON previous efforts and feedback. <br /> <br /> Is the student’s understanding of the assignment getting better or worse? How can the teacher tell without seeing the student’s progression over time? <br /> <br /> '''Example 1:''' An assignment has tasks A, B and C. The student submits A and B but not C, which the student does not understand. Teacher feedback informs student to resubmit since she “forgot” task C. Again, the student resubmits parts A and B, but not C. Since a RESUBMISSION looks just like a FIRST SUBMISSION, this could happen many times without the teacher realizing that the student has repeatedly skipped task C (especially if the teacher has many students/classes). <br /> <br /> '''Example 2:''' An assignment asks students to write a clear and concise paragraph that expresses an opinion about a controversial issue. A student submits a paragraph that contains some good but obvious arguments as well as a few other points that are original but undeveloped. The teacher’s feedback challenges the student to explore her original thoughts. The student’s resubmission expands on the obvious arguments but completely omits the more original ideas. When the teacher sees the resubmission, all traces of the original ideas (as well as the feedback) are gone. The teacher, who has over 100 students, does not recall that this student had expressed some unique but unexplored views. A grade is given but an opportunity for real learning/teaching is lost.<br /> <br /> ='''New settings'''=<br /> * "Submission history" Yes|No - If enabled, each student submission to the assignment will be recorded at submission time and a teacher will be able to see each submission by an individual student.<br /> <br /> ='''Interface changes'''=<br /> A new entry will be put in the drop down menu on the grading table for each submission to view the submission history for that student. This will go to a new page in the assignment that displays the student details, as well of a list of the submissions by that student. For each submission it will contain the time and date, any files, online text or custom submission data. (Question: Does it need grades/feedback?)<br /> <br /> Although feedback for each historical submission can be collectively held in the Feedback comments text area (perhaps under headings "First attempt Feedback" or similar) or by file upload a better solution might be to archive feedback linked to each submission. This is more suited to evidence requirements in most organisations as feedback cannot then be altered. On the assumption that this would require a lot more work this should be dropped rather than holding up the main feature of allowing resubmissions properly. (Question answered?)<br /> <br /> -----<br /> <br /> '''Implementing this feature may require that we rethink the “revert to draft” function that’s currently in place.<br /> <br /> The current “revert to draft” feature asks students to CHANGE / REPLACE their answer. If I understand this feature correctly, when a submission is reverted to draft, it is NOT graded – it is as if the student NEVER SUBMITTED it in the first place. <br /> <br /> The new feature that is being proposed here is more like a “Request Resubmission” feature, which ARCHIVES all previous attempts are then asks the students to BUILD ON / LEARN FROM their previous submissions. <br /> <br /> Whether we continue to use term “revert to draft” or adopt “request resubmission”, the goal in this proposal is to move from the current method of “undo” to one of “redo”.'''<br /> <br /> ='''Use Cases'''=<br /> ''' A teacher wants to give feedback and let a student upload a new file submission to the assignment '''<br /> * Create an assignment with file submissions enabled, "Submission history" enabled and "Require students click submit" disabled<br /> * Wait until a student uploads a file submision<br /> * Grade the submission and give some feedback<br /> * Revert the submission to draft to allow the student to upload a new file<br /> * The student should see a readonly version of their original submission plus any feedback from the teacher<br /> * They should now be able to upload a new file without being able to delete their first submission<br /> <br /> ='''User Interface'''=<br /> Some screenshot mockups will help the community visualise this feature.</div>

Fern https://docs.moodle.org/dev/index.php?title=Assignment_Resubmission_History_Proposal&diff=36646 Assignment Resubmission History Proposal 2012-11-27T17:04:56Z

<p>Fern: /* Interface changes */</p> <hr /> <div>{{Infobox Project<br /> |name = Assignment Resubmission History<br /> |state = Proposed<br /> |tracker = MDL-36804<br /> |discussion = https://moodle.org/mod/forum/discuss.php?d=205060<br /> }}<br /> <br /> ='''Assignment Resubmission History'''=<br /> <br /> This is a proposal for an additional feature for the Assignment module to retain a history of the submission by a student to the assignment.<br /> <br /> ='''Goals and rationale'''=<br /> The main goals of this feature are to :<br /> <br /> * Provide a better history of the student interactions with an assignment. <br /> * Make it easier for students to upload files to an assignment (without having to delete their original files first)<br /> * Provide an audit trail for internal and external verification of marked work<br /> <br /> ='''Overview'''=<br /> <br /> This is a feature request from the community to retain the list of submissions by a student instead of overwriting the previous submission.<br /> <br /> ----<br /> Currently, when a student RESUBMITS an assignment, the original submission, grade and feedback are all lost. This inhibits the ability of both the teacher and student to LEARN FROM and BUILD ON previous efforts and feedback. <br /> <br /> Is the student’s understanding of the assignment getting better or worse? How can the teacher tell without seeing the student’s progression over time? <br /> <br /> '''Example 1:''' An assignment has tasks A, B and C. The student submits A and B but not C, which the student does not understand. Teacher feedback informs student to resubmit since she “forgot” task C. Again, the student resubmits parts A and B, but not C. Since a RESUBMISSION looks just like a FIRST SUBMISSION, this could happen many times without the teacher realizing that the student has repeatedly skipped task C (especially if the teacher has many students/classes). <br /> <br /> '''Example 2:''' An assignment asks students to write a clear and concise paragraph that expresses an opinion about a controversial issue. A student submits a paragraph that contains some good but obvious arguments as well as a few other points that are original but undeveloped. The teacher’s feedback challenges the student to explore her original thoughts. The student’s resubmission expands on the obvious arguments but completely omits the more original ideas. When the teacher sees the resubmission, all traces of the original ideas (as well as the feedback) are gone. The teacher, who has over 100 students, does not recall that this student had expressed some unique but unexplored views. A grade is given but an opportunity for real learning/teaching is lost.<br /> <br /> ='''New settings'''=<br /> * "Submission history" Yes|No - If enabled, each student submission to the assignment will be recorded at submission time and a teacher will be able to see each submission by an individual student.<br /> <br /> ='''Interface changes'''=<br /> A new entry will be put in the drop down menu on the grading table for each submission to view the submission history for that student. This will go to a new page in the assignment that displays the student details, as well of a list of the submissions by that student. For each submission it will contain the time and date, any files, online text or custom submission data. (Question: Does it need grades/feedback?)<br /> <br /> Although feedback for each historical submission can be collectively held in the Feedback comments text area (perhaps under headings "First attempt Feedback" or similar) or by file upload a better solution might be to archive feedback linked to each submission. This is more suited to evidence requirements in most organisations as feedback cannot then be altered. On the assumption that this would require a lot more work this should be dropped rather than holding up the main feature of allowing resubmissions properly. (Question answered?)<br /> <br /> -----<br /> <br /> '''Implementing this feature may require that we rethink the “revert to draft” function that’s currently in place.<br /> <br /> The current “revert to draft” feature asks students to CHANGE / REPLACE their answer. If I understand this feature correctly, when a submission is reverted to draft, it is NOT graded – it is as if the student NEVER SUBMITTED it in the first place. <br /> <br /> The new feature that is being proposed here is more like a “Request Resubmission” feature, which ARCHIVES all previous attempts are then asks the students to BUILD ON / LEARN FROM their previous submissions. <br /> <br /> Whether we continue to use “revert to draft” or adopt “request resubmission”, the goal is this proposal is to move from the current method of “undo” to one of “redo”.'''<br /> <br /> ='''Use Cases'''=<br /> ''' A teacher wants to give feedback and let a student upload a new file submission to the assignment '''<br /> * Create an assignment with file submissions enabled, "Submission history" enabled and "Require students click submit" disabled<br /> * Wait until a student uploads a file submision<br /> * Grade the submission and give some feedback<br /> * Revert the submission to draft to allow the student to upload a new file<br /> * The student should see a readonly version of their original submission plus any feedback from the teacher<br /> * They should now be able to upload a new file without being able to delete their first submission<br /> <br /> ='''User Interface'''=<br /> Some screenshot mockups will help the community visualise this feature.</div>

Fern https://docs.moodle.org/dev/index.php?title=Assignment_Resubmission_History_Proposal&diff=36645 Assignment Resubmission History Proposal 2012-11-27T17:04:00Z

<p>Fern: /* Interface changes */</p> <hr /> <div>{{Infobox Project<br /> |name = Assignment Resubmission History<br /> |state = Proposed<br /> |tracker = MDL-36804<br /> |discussion = https://moodle.org/mod/forum/discuss.php?d=205060<br /> }}<br /> <br /> ='''Assignment Resubmission History'''=<br /> <br /> This is a proposal for an additional feature for the Assignment module to retain a history of the submission by a student to the assignment.<br /> <br /> ='''Goals and rationale'''=<br /> The main goals of this feature are to :<br /> <br /> * Provide a better history of the student interactions with an assignment. <br /> * Make it easier for students to upload files to an assignment (without having to delete their original files first)<br /> * Provide an audit trail for internal and external verification of marked work<br /> <br /> ='''Overview'''=<br /> <br /> This is a feature request from the community to retain the list of submissions by a student instead of overwriting the previous submission.<br /> <br /> ----<br /> Currently, when a student RESUBMITS an assignment, the original submission, grade and feedback are all lost. This inhibits the ability of both the teacher and student to LEARN FROM and BUILD ON previous efforts and feedback. <br /> <br /> Is the student’s understanding of the assignment getting better or worse? How can the teacher tell without seeing the student’s progression over time? <br /> <br /> '''Example 1:''' An assignment has tasks A, B and C. The student submits A and B but not C, which the student does not understand. Teacher feedback informs student to resubmit since she “forgot” task C. Again, the student resubmits parts A and B, but not C. Since a RESUBMISSION looks just like a FIRST SUBMISSION, this could happen many times without the teacher realizing that the student has repeatedly skipped task C (especially if the teacher has many students/classes). <br /> <br /> '''Example 2:''' An assignment asks students to write a clear and concise paragraph that expresses an opinion about a controversial issue. A student submits a paragraph that contains some good but obvious arguments as well as a few other points that are original but undeveloped. The teacher’s feedback challenges the student to explore her original thoughts. The student’s resubmission expands on the obvious arguments but completely omits the more original ideas. When the teacher sees the resubmission, all traces of the original ideas (as well as the feedback) are gone. The teacher, who has over 100 students, does not recall that this student had expressed some unique but unexplored views. A grade is given but an opportunity for real learning/teaching is lost.<br /> <br /> ='''New settings'''=<br /> * "Submission history" Yes|No - If enabled, each student submission to the assignment will be recorded at submission time and a teacher will be able to see each submission by an individual student.<br /> <br /> ='''Interface changes'''=<br /> A new entry will be put in the drop down menu on the grading table for each submission to view the submission history for that student. This will go to a new page in the assignment that displays the student details, as well of a list of the submissions by that student. For each submission it will contain the time and date, any files, online text or custom submission data. (Question: Does it need grades/feedback?)<br /> <br /> Although feedback for each historical submission can be collectively held in the Feedback comments text area (perhaps under headings "First attempt Feedback" or similar) or by file upload a better solution might be to archive feedback linked to each submission. This is more suited to evidence requirements in most organisations as feedback cannot then be altered. On the assumption that this would require a lot more work this should be dropped rather than holding up the main feature of allowing resubmissions properly. (Question answered?)<br /> <br /> -----<br /> ''<br /> Implementing this feature may require that we rethink the “revert to draft” function that’s currently in place.<br /> <br /> The current “revert to draft” feature asks students to CHANGE / REPLACE their answer. If I understand this feature correctly, when a submission is reverted to draft, it is NOT graded – it is as if the student NEVER SUBMITTED it in the first place. <br /> <br /> The new feature that is being proposed here is more like a “Request Resubmission” feature, which ARCHIVES all previous attempts are then asks the students to BUILD ON / LEARN FROM their previous submissions. <br /> <br /> Whether we continue to use “revert to draft” or adopt “request resubmission”, the goal is this proposal is to move from the current method of “undo” to one of “redo”.<br /> ''<br /> <br /> ='''Use Cases'''=<br /> ''' A teacher wants to give feedback and let a student upload a new file submission to the assignment '''<br /> * Create an assignment with file submissions enabled, "Submission history" enabled and "Require students click submit" disabled<br /> * Wait until a student uploads a file submision<br /> * Grade the submission and give some feedback<br /> * Revert the submission to draft to allow the student to upload a new file<br /> * The student should see a readonly version of their original submission plus any feedback from the teacher<br /> * They should now be able to upload a new file without being able to delete their first submission<br /> <br /> ='''User Interface'''=<br /> Some screenshot mockups will help the community visualise this feature.</div>

Fern https://docs.moodle.org/dev/index.php?title=Assignment_Resubmission_History_Proposal&diff=36644 Assignment Resubmission History Proposal 2012-11-27T17:01:16Z

<p>Fern: /* Overview */</p> <hr /> <div>{{Infobox Project<br /> |name = Assignment Resubmission History<br /> |state = Proposed<br /> |tracker = MDL-36804<br /> |discussion = https://moodle.org/mod/forum/discuss.php?d=205060<br /> }}<br /> <br /> ='''Assignment Resubmission History'''=<br /> <br /> This is a proposal for an additional feature for the Assignment module to retain a history of the submission by a student to the assignment.<br /> <br /> ='''Goals and rationale'''=<br /> The main goals of this feature are to :<br /> <br /> * Provide a better history of the student interactions with an assignment. <br /> * Make it easier for students to upload files to an assignment (without having to delete their original files first)<br /> * Provide an audit trail for internal and external verification of marked work<br /> <br /> ='''Overview'''=<br /> <br /> This is a feature request from the community to retain the list of submissions by a student instead of overwriting the previous submission.<br /> <br /> ----<br /> Currently, when a student RESUBMITS an assignment, the original submission, grade and feedback are all lost. This inhibits the ability of both the teacher and student to LEARN FROM and BUILD ON previous efforts and feedback. <br /> <br /> Is the student’s understanding of the assignment getting better or worse? How can the teacher tell without seeing the student’s progression over time? <br /> <br /> '''Example 1:''' An assignment has tasks A, B and C. The student submits A and B but not C, which the student does not understand. Teacher feedback informs student to resubmit since she “forgot” task C. Again, the student resubmits parts A and B, but not C. Since a RESUBMISSION looks just like a FIRST SUBMISSION, this could happen many times without the teacher realizing that the student has repeatedly skipped task C (especially if the teacher has many students/classes). <br /> <br /> '''Example 2:''' An assignment asks students to write a clear and concise paragraph that expresses an opinion about a controversial issue. A student submits a paragraph that contains some good but obvious arguments as well as a few other points that are original but undeveloped. The teacher’s feedback challenges the student to explore her original thoughts. The student’s resubmission expands on the obvious arguments but completely omits the more original ideas. When the teacher sees the resubmission, all traces of the original ideas (as well as the feedback) are gone. The teacher, who has over 100 students, does not recall that this student had expressed some unique but unexplored views. A grade is given but an opportunity for real learning/teaching is lost.<br /> <br /> ='''New settings'''=<br /> * "Submission history" Yes|No - If enabled, each student submission to the assignment will be recorded at submission time and a teacher will be able to see each submission by an individual student.<br /> <br /> ='''Interface changes'''=<br /> A new entry will be put in the drop down menu on the grading table for each submission to view the submission history for that student. This will go to a new page in the assignment that displays the student details, as well of a list of the submissions by that student. For each submission it will contain the time and date, any files, online text or custom submission data. (Question: Does it need grades/feedback?)<br /> <br /> Although feedback for each historical submission can be collectively held in the Feedback comments text area (perhaps under headings "First attempt Feedback" or similar) or by file upload a better solution might be to archive feedback linked to each submission. This is more suited to evidence requirements in most organisations as feedback cannot then be altered. On the assumption that this would require a lot more work this should be dropped rather than holding up the main feature of allowing resubmissions properly. (Question answered?)<br /> <br /> ='''Use Cases'''=<br /> ''' A teacher wants to give feedback and let a student upload a new file submission to the assignment '''<br /> * Create an assignment with file submissions enabled, "Submission history" enabled and "Require students click submit" disabled<br /> * Wait until a student uploads a file submision<br /> * Grade the submission and give some feedback<br /> * Revert the submission to draft to allow the student to upload a new file<br /> * The student should see a readonly version of their original submission plus any feedback from the teacher<br /> * They should now be able to upload a new file without being able to delete their first submission<br /> <br /> ='''User Interface'''=<br /> Some screenshot mockups will help the community visualise this feature.</div>

Fern https://docs.moodle.org/dev/index.php?title=Talk:Cohorts&diff=28364 Talk:Cohorts 2010-06-21T17:46:10Z

<p>Fern: Mock-up for Cohorts/Global Groups</p> <hr /> <div>The goals specified seem to cover exactly what I think the use case for 'global groups' are :) --[[User:Dan Poltawski|Dan Poltawski]] 23:50, 8 March 2010 (UTC)<br /> <br /> It would be useful to expand the comments about replacing category enrolments. Assignment to a role for a category e.g. as course Creator is a method used extensively to provide delegated permissions by department, school etc. It would be a shame for this to be lost in 2.0.<br /> <br /> Will cohorts be role agnostic in the same way as course groups?<br /> <br /> The following is a frequently asked for use case that doesn't seem to be catered for in specification here:<br /> <br /> Site administrator (or others with relevant permissions) can allocate to a cohort e.g. cohort a, cohort b.<br /> <br /> The site administrator wants to hand over responsibility for allocating users to cohort a to a user in cohort a who has the necessary permissions. This user should not be able to access any other cohort or allocate users to them. Are the new capabilities granualar enough to facilitate this? --[[User:Ray Lawrence|Ray Lawrence]] 09:53, 31 March 2010 (UTC)<br /> <br /> --------<br /> This mock-up (shown here: http://dev1.moodlefn.com/moodle-global-groups.pdf )contains a handful of features that (I think) are an important part of the Cohorts/Global Groups design at the site level. In particular..<br /> <br /> 1. Ability to control Global Groups membership and course enrolment at the site level<br /> 2. Ability to perform manual course enrolment (not synched) with Global Groups view<br /> 3. Ability to set up synched course enrolment based on Global Groups<br /> 4. Ability to sync group members (without groups) or group members and thier associated groups<br /> 5. Prevent synched groups from being edited at the course level<br /> 6. Allow Group Managers (role) to be assigned to Global Groups and Cohorts<br /> 7. Allow Global Groups have profiles (avatar + description + custom fields)<br /> <br /> Please feel free to lift ideas or elements from the provided mock-up.<br /> [User: Fernando Oliveira June 21, 2010)<br /> ---------</div>

Fern