Expertiza_Wiki - User contributions [en]

CSC/ECE 517 Fall 2021 - E2158. Grading audit trail

2021-11-30T16:49:08Z

Hdu5: /* Important Links */

== Problem Definition ==
After an instructor gave a grade to an assignment, there is no way to track who gave the grade. Any instructor can assign/edit a grade freely. There is no way of tracking who did it.

A grading audit trail must be created and the following information needs to be stored:
:1. When a grade is assigned by an instructor, there needs to be an indication of who did it and when it was done.
:2. Comments previously provided by other instructors must also be preserved.

This information needs to be stored every time an instructor edits a grade/comment and clicks the save button.

Currently, there are two places need to add grading audit trail:
:1. '''Review grade''': Log in as instructor -> Manage -> Assignments -> View Review Report
:2. '''Submission grade''': Log in as instructor -> Manage -> Assignments -> View submissions

The grading audit trail can probably be implemented as the submission records history on Expertiza.
The required page can be reached by logging in as instructor -> Manage -> Assignments -> View Submissions -> History

At the minimum, a grading log entry must include the '''instructor id''', '''assignment id''', '''student id''', '''grade''', '''comment''' and '''timestamp'''.

== Previous Implementation ==

=== Links ===
[https://expertiza.csc.ncsu.edu/index.php/E1934_-_Grading_Audit_Trail Previous Wiki Page]

[https://youtu.be/yyxX_kRYxLc Screencast]

=== Review ===

:1. '''Review grade''' part in the previous implementation served well, we only need to fix some UI issues in the current implementation;
:2. But for '''Submission grade''' part, we need to add a table in order to save submission history including the instructor id, assignment id, student id, grade, comment, and timestamp.

=== Issues with Previous Work ===
:1. For review grades, the “Grading History” link must not be in a separate column. It should be in smaller text below in the “Save” button.

:2. In the view grading record page, remove the receiver column and add it to the title.

:3. Restrict the column width on the grading record page.

:4. Add comments on list_submissions.html.erb to indicate that the alignment was changed to fix code climate issues.

:5. Revert changes made to list_review_mapping.html.erb.

:6. Remove the review_report-html.erb file.

== Proposed Solution ==
=== Expected View ===
 
[[File:E2158_Proposed_Solution_1.png|1100px]]
 
 
[[File:E2158_Proposed_Solution_2.png|1100px]]
 
 
[[File:E2158_Proposed_Solution_3.png|1100px]]
 

=== History of Comment and Grade for Reviews ===

In this part, we will modify the current view of review page, to add the link "history" to a proper place as the expected design picture shows.

The related table from databases is [https://expertiza.csc.ncsu.edu/index.php/Review_scores review_scores]. The ER table of review_scores is shown as below.

[[File:Review scores imported.png]]
==== Review History Flow====
[[File:reviewhistory.png]]

=== History of Comment and Grade for Submissions===

In Expertiza, we find the fields related to grade and comment are located in the model '''team''', which is only able to be overwritten. Since there is no table to store the history of the comment and score given by instructors and TAs, we need to do:

:1. Review the related implementation of previous work in order to evaluate and understand the process of adding new models.

:2. Implement the related Model, View and Controller:

:* Model: grading_history.rb

:* Controller: grading_history_controller.rb

:* View: related pages.

Because in Expertiza the team ID will be generated for each given assignment, so the original design of grade / comment of team's submission are the field belongs to '''team'''. So our model uses the foreign key to only the team but not the related assignments or submissions.

The expected class of grading history could be shown as:

[[File:GradingHistory.png]]

==== Team History Flow====
[[File:teamhistory.png]]

== Testing Plan ==
=== Rspec Unit Tests ===
==== For History of the Grade of Reviews ====
The history of the grade and comments are related to this controller app/controllers/review_mapping_controller.rb and this view app/views/reports/_review_report.html.erb.

So the related RSpec tests are planned to be executed:

spec/controllers/review_mapping_controller_spec.rb

==== For History of the Grade of Team Submissions ====
The history of the grade and comments are related to the new model grading_history.rb and the new controller grading_history_controller.rb.

So the related RSpec tests are planned to be executed:

spec/models/grading_history.rb
spec/controllers/grading_history_controller.rb

For the feature part, test if the grading history and instructor can be shown in chronological order:

spec/features/grade_histories_spec.rb
spec/features/helpers/grade_histories_helper.rb

=== Manual UI Tests ===
To start the test, we need to log in as instructor or TA first. These accounts should have access to the assignment. For example: we can use '''intructor6/password''' or '''teaching_assistant8631/password''';

==== Scenario 1: Grading histories of submissions ====
Step 1. Log in as instructor/TA -> Manage -> Assignments -> View submissions
 
[[File:E2158_view_submisson.png|1100px]]
 
 
Step 2. The instructor/TA can assign grades to a team by clicking 'Assign Grade' in the 'Team name' column:
 
[[File:E2158_grading_history_submisson1.png|1100px]]
 
 
Step 3. The instructor/TA can view the grading audit trail by clicking 'Grading History' in the 'History' column, here is the record page:
 
[[File:E2158_grading_history_submisson2.png|1100px]]
 
 
==== Scenario 2: Grading histories of reviews ====
Step 1. Log in as instructor/TA -> Manage -> Assignments -> View Reports
 
[[File:E2158_view_report.png|1100px]]
 
 
Step 2. Select 'Review Report' then click 'View', here is the Review Report page. The instructor/TA can assign grades to a review by inputing 'Grade' and 'Comment' then clicking 'Save' button:
 
[[File:E2158_grading_history_report1.png|1100px]]
 
 
Step 3. The instructor/TA can view the grading audit trail by clicking 'Grading History' as Step 2 figure shows, here is the record page:
 
[[File:E2158_grading_history_report2.png|1100px]]
 
 

== Important Links ==
#[https://github.com/duliwencynthia/expertiza/tree/beta Git Repo]
#[https://github.com/expertiza/expertiza/pull/2164 Pull Request]
#[https://www.youtube.com/watch?v=ad4wF6--5dQ Test1]

== Team ==
'''Mentor:''' Xiao, Kai (yxiao28)

Yao, Kaiyong (kyao)

Hou, Guanyu (ghou3)

Du, Haoze (hdu5)

Du, Liwen (ldu2)

File:GradingHistory.png

2021-11-10T17:17:02Z

Hdu5: Hdu5 uploaded a new version of File:GradingHistory.png

File:GradingHistory.png

2021-11-10T17:16:42Z

Hdu5: Hdu5 uploaded a new version of File:GradingHistory.png

File:GradingHistory.png

2021-11-10T17:09:54Z

Hdu5: Hdu5 uploaded a new version of File:GradingHistory.png

CSC/ECE 517 Fall 2021 - E2158. Grading audit trail

2021-11-09T04:07:55Z

Hdu5: Undo revision 141451 by Hdu5 (talk)

== Problem Definition ==
After an instructor gave a grade to an assignment, there is no way to track who gave the grade. Any instructor can assign/edit a grade freely. There is no way of tracking who did it.

A grading audit trail must be created and the following information needs to be stored:
:1. When a grade is assigned by an instructor, there needs to be an indication of who did it and when it was done.
:2. Comments previously provided by other instructors must also be preserved.

This information needs to be stored every time an instructor edits a grade/comment and clicks the save button.

Currently, there are two places need to add grading audit trail:
:1. '''Review grade''': Log in as instructor -> Manage -> Assignments -> View Review Report
:2. '''Submission grade''': Log in as instructor -> Manage -> Assignments -> View submissions

The grading audit trail can probably be implemented as the submission records history on Expertiza.
The required page can be reached by logging in as instructor -> Manage -> Assignments -> View Submissions -> History

At the minimum, a grading log entry must include the '''instructor id''', '''assignment id''', '''student id''', '''grade''', '''comment''' and '''timestamp'''.

== Previous Implementation ==

=== Links ===
[https://expertiza.csc.ncsu.edu/index.php/E1934_-_Grading_Audit_Trail Previous Wiki Page]

[https://youtu.be/yyxX_kRYxLc Screencast]

=== Review ===

:1. '''Review grade''' part in the previous implementation served well, we only need to fix some UI issues in the current implementation;
:2. But for '''Submission grade''' part, we need to add a table in order to save submission history including the instructor id, assignment id, student id, grade, comment, and timestamp.

=== Issues with Previous Work ===
:1. For review grades, the “Grading History” link must not be in a separate column. It should be in smaller text below in the “Save” button.

:2. In the view grading record page, remove the receiver column and add it to the title.

:3. Restrict the column width on the grading record page.

:4. Add comments on list_submissions.html.erb to indicate that the alignment was changed to fix code climate issues.

:5. Revert changes made to list_review_mapping.html.erb.

:6. Remove the review_report-html.erb file.

== Proposed Solution ==
=== Expected View ===

[[File:E2158_Proposed_Solution_1.png|1100px|center]]
[[File:E2158_Proposed_Solution_2.png|1100px|center]]
[[File:E2158_Proposed_Solution_3.png|1100px|center]]

=== History of Comment and Grade for Reviews ===

In this part, we will modify the current view of review page, to add the link "history" to a proper place as the expected design picture shows.

The related table from databases is [https://expertiza.csc.ncsu.edu/index.php/Review_scores review_scores]. The ER table of review_scores is shown as below.

[[File:Review scores imported.png]]

=== History of Comment and Grade for Submissions===

In Expertiza, we find the fields related to grade and comment are located in the model '''team''', which is only able to be overwritten. Since there is no table to store the history of the comment and score given by instructors and TAs, we need to do:

:1. Review the related implementation of previous work in order to evaluate and understand the process of adding new models.

:2. Implement the related Model, View and Controller:

:* Model: grading_history.rb

:* Controller: grading_history_controller.rb

:* View: related pages.

Because in Expertiza the team ID will be generated for each given assignment, so the original design of grade / comment of team's submission are the field belongs to '''team'''. So our model uses the foreign key to only the team but not the related assignments or submissions.

The expected class of grading history could be shown as:

[[File:GradingHistory.png]]

== Testing Plan ==
=== Rspec Unit Tests ===
==== For History of the Grade of Reviews ====
The history of the grade and comments are related to this controller app/controllers/review_mapping_controller.rb and this view app/views/reports/_review_report.html.erb.

So the related RSpec tests are planned to be executed:

spec/controllers/review_mapping_controller_spec.rb

==== For History of the Grade of Team Submissions ====
The history of the grade and comments are related to the new model grading_history.rb and the new controller grading_history_controller.rb.

So the related RSpec tests are planned to be executed:

spec/models/grading_history.rb
spec/controllers/grading_history_controller.rb

=== Manual UI Tests ===
The new features of recording and showing the history of grades and comments of reviews and submissions will be manually tested after we finished the implementation of those functions.

:1. An assignment and a team will be generated, and at most 3 instructors / TAs will give grades for these situations:
1. 1 submission, 1 review, 1 grade and comment for submission, 1 grade and comment for review.
2. 1 submission, 2 review, 2 grade and comment for submission from different graders, 2 grade and comment for review from different graders.
:2. An assignment and 3 teams will be generated, and at most 3 instructors / TAs will give grades for these situations:
1. For each team: 1 submission, 1 review, 1 grade and comment for submission, 1 grade and comment for review.
2. For each team: 1 submission, 2 review, 2 grade and comment for submission from different graders, 2 grade and comment for review from different graders.
...

We will generate some edge cases to test the robustness of our work.

== Important Links ==
#[https://github.com/duliwencynthia/expertiza/tree/beta Git path]
#[https://github.com/expertiza/expertiza/pull/2130 Pull Request]

== Team ==
'''Mentor:''' Xiao, Kai (yxiao28)

Yao, Kaiyong (kyao)

Hou, Guanyu (ghou3)

Du, Haoze (hdu5)

Du, Liwen (ldu2)

CSC/ECE 517 Fall 2021 - E2158. Grading audit trail

2021-11-09T04:07:26Z

Hdu5: /* Expected View */

== Problem Definition ==
After an instructor gave a grade to an assignment, there is no way to track who gave the grade. Any instructor can assign/edit a grade freely. There is no way of tracking who did it.

A grading audit trail must be created and the following information needs to be stored:
:1. When a grade is assigned by an instructor, there needs to be an indication of who did it and when it was done.
:2. Comments previously provided by other instructors must also be preserved.

This information needs to be stored every time an instructor edits a grade/comment and clicks the save button.

Currently, there are two places need to add grading audit trail:
:1. '''Review grade''': Log in as instructor -> Manage -> Assignments -> View Review Report
:2. '''Submission grade''': Log in as instructor -> Manage -> Assignments -> View submissions

The grading audit trail can probably be implemented as the submission records history on Expertiza.
The required page can be reached by logging in as instructor -> Manage -> Assignments -> View Submissions -> History

At the minimum, a grading log entry must include the '''instructor id''', '''assignment id''', '''student id''', '''grade''', '''comment''' and '''timestamp'''.

== Previous Implementation ==

=== Links ===
[https://expertiza.csc.ncsu.edu/index.php/E1934_-_Grading_Audit_Trail Previous Wiki Page]

[https://youtu.be/yyxX_kRYxLc Screencast]

=== Review ===

:1. '''Review grade''' part in the previous implementation served well, we only need to fix some UI issues in the current implementation;
:2. But for '''Submission grade''' part, we need to add a table in order to save submission history including the instructor id, assignment id, student id, grade, comment, and timestamp.

=== Issues with Previous Work ===
:1. For review grades, the “Grading History” link must not be in a separate column. It should be in smaller text below in the “Save” button.

:2. In the view grading record page, remove the receiver column and add it to the title.

:3. Restrict the column width on the grading record page.

:4. Add comments on list_submissions.html.erb to indicate that the alignment was changed to fix code climate issues.

:5. Revert changes made to list_review_mapping.html.erb.

:6. Remove the review_report-html.erb file.

== Proposed Solution ==
=== Expected View ===

[[File:E2158_Proposed_Solution_1.png|1100px|left]]
[[File:E2158_Proposed_Solution_2.png|1100px|left]]
[[File:E2158_Proposed_Solution_3.png|1100px|left]]

=== History of Comment and Grade for Reviews ===

In this part, we will modify the current view of review page, to add the link "history" to a proper place as the expected design picture shows.

The related table from databases is [https://expertiza.csc.ncsu.edu/index.php/Review_scores review_scores]. The ER table of review_scores is shown as below.

[[File:Review scores imported.png]]

=== History of Comment and Grade for Submissions===

In Expertiza, we find the fields related to grade and comment are located in the model '''team''', which is only able to be overwritten. Since there is no table to store the history of the comment and score given by instructors and TAs, we need to do:

:1. Review the related implementation of previous work in order to evaluate and understand the process of adding new models.

:2. Implement the related Model, View and Controller:

:* Model: grading_history.rb

:* Controller: grading_history_controller.rb

:* View: related pages.

Because in Expertiza the team ID will be generated for each given assignment, so the original design of grade / comment of team's submission are the field belongs to '''team'''. So our model uses the foreign key to only the team but not the related assignments or submissions.

The expected class of grading history could be shown as:

[[File:GradingHistory.png]]

== Testing Plan ==
=== Rspec Unit Tests ===
==== For History of the Grade of Reviews ====
The history of the grade and comments are related to this controller app/controllers/review_mapping_controller.rb and this view app/views/reports/_review_report.html.erb.

So the related RSpec tests are planned to be executed:

spec/controllers/review_mapping_controller_spec.rb

==== For History of the Grade of Team Submissions ====
The history of the grade and comments are related to the new model grading_history.rb and the new controller grading_history_controller.rb.

So the related RSpec tests are planned to be executed:

spec/models/grading_history.rb
spec/controllers/grading_history_controller.rb

=== Manual UI Tests ===
The new features of recording and showing the history of grades and comments of reviews and submissions will be manually tested after we finished the implementation of those functions.

:1. An assignment and a team will be generated, and at most 3 instructors / TAs will give grades for these situations:
1. 1 submission, 1 review, 1 grade and comment for submission, 1 grade and comment for review.
2. 1 submission, 2 review, 2 grade and comment for submission from different graders, 2 grade and comment for review from different graders.
:2. An assignment and 3 teams will be generated, and at most 3 instructors / TAs will give grades for these situations:
1. For each team: 1 submission, 1 review, 1 grade and comment for submission, 1 grade and comment for review.
2. For each team: 1 submission, 2 review, 2 grade and comment for submission from different graders, 2 grade and comment for review from different graders.
...

We will generate some edge cases to test the robustness of our work.

== Important Links ==
#[https://github.com/duliwencynthia/expertiza/tree/beta Git path]
#[https://github.com/expertiza/expertiza/pull/2130 Pull Request]

== Team ==
'''Mentor:''' Xiao, Kai (yxiao28)

Yao, Kaiyong (kyao)

Hou, Guanyu (ghou3)

Du, Haoze (hdu5)

Du, Liwen (ldu2)

CSC/ECE 517 Fall 2021 - E2158. Grading audit trail

2021-11-09T04:06:27Z

Hdu5: /* Manual UI Testing */

== Problem Definition ==
After an instructor gave a grade to an assignment, there is no way to track who gave the grade. Any instructor can assign/edit a grade freely. There is no way of tracking who did it.

A grading audit trail must be created and the following information needs to be stored:
:1. When a grade is assigned by an instructor, there needs to be an indication of who did it and when it was done.
:2. Comments previously provided by other instructors must also be preserved.

This information needs to be stored every time an instructor edits a grade/comment and clicks the save button.

Currently, there are two places need to add grading audit trail:
:1. '''Review grade''': Log in as instructor -> Manage -> Assignments -> View Review Report
:2. '''Submission grade''': Log in as instructor -> Manage -> Assignments -> View submissions

The grading audit trail can probably be implemented as the submission records history on Expertiza.
The required page can be reached by logging in as instructor -> Manage -> Assignments -> View Submissions -> History

At the minimum, a grading log entry must include the '''instructor id''', '''assignment id''', '''student id''', '''grade''', '''comment''' and '''timestamp'''.

== Previous Implementation ==

=== Links ===
[https://expertiza.csc.ncsu.edu/index.php/E1934_-_Grading_Audit_Trail Previous Wiki Page]

[https://youtu.be/yyxX_kRYxLc Screencast]

=== Review ===

:1. '''Review grade''' part in the previous implementation served well, we only need to fix some UI issues in the current implementation;
:2. But for '''Submission grade''' part, we need to add a table in order to save submission history including the instructor id, assignment id, student id, grade, comment, and timestamp.

=== Issues with Previous Work ===
:1. For review grades, the “Grading History” link must not be in a separate column. It should be in smaller text below in the “Save” button.

:2. In the view grading record page, remove the receiver column and add it to the title.

:3. Restrict the column width on the grading record page.

:4. Add comments on list_submissions.html.erb to indicate that the alignment was changed to fix code climate issues.

:5. Revert changes made to list_review_mapping.html.erb.

:6. Remove the review_report-html.erb file.

== Proposed Solution ==
=== Expected View ===

[[File:E2158_Proposed_Solution_1.png|1100px|center]]
[[File:E2158_Proposed_Solution_2.png|1100px|center]]
[[File:E2158_Proposed_Solution_3.png|1100px|center]]

=== History of Comment and Grade for Reviews ===

In this part, we will modify the current view of review page, to add the link "history" to a proper place as the expected design picture shows.

The related table from databases is [https://expertiza.csc.ncsu.edu/index.php/Review_scores review_scores]. The ER table of review_scores is shown as below.

[[File:Review scores imported.png]]

=== History of Comment and Grade for Submissions===

In Expertiza, we find the fields related to grade and comment are located in the model '''team''', which is only able to be overwritten. Since there is no table to store the history of the comment and score given by instructors and TAs, we need to do:

:1. Review the related implementation of previous work in order to evaluate and understand the process of adding new models.

:2. Implement the related Model, View and Controller:

:* Model: grading_history.rb

:* Controller: grading_history_controller.rb

:* View: related pages.

Because in Expertiza the team ID will be generated for each given assignment, so the original design of grade / comment of team's submission are the field belongs to '''team'''. So our model uses the foreign key to only the team but not the related assignments or submissions.

The expected class of grading history could be shown as:

[[File:GradingHistory.png]]

== Testing Plan ==
=== Rspec Unit Tests ===
==== For History of the Grade of Reviews ====
The history of the grade and comments are related to this controller app/controllers/review_mapping_controller.rb and this view app/views/reports/_review_report.html.erb.

So the related RSpec tests are planned to be executed:

spec/controllers/review_mapping_controller_spec.rb

==== For History of the Grade of Team Submissions ====
The history of the grade and comments are related to the new model grading_history.rb and the new controller grading_history_controller.rb.

So the related RSpec tests are planned to be executed:

spec/models/grading_history.rb
spec/controllers/grading_history_controller.rb

=== Manual UI Tests ===
The new features of recording and showing the history of grades and comments of reviews and submissions will be manually tested after we finished the implementation of those functions.

:1. An assignment and a team will be generated, and at most 3 instructors / TAs will give grades for these situations:
1. 1 submission, 1 review, 1 grade and comment for submission, 1 grade and comment for review.
2. 1 submission, 2 review, 2 grade and comment for submission from different graders, 2 grade and comment for review from different graders.
:2. An assignment and 3 teams will be generated, and at most 3 instructors / TAs will give grades for these situations:
1. For each team: 1 submission, 1 review, 1 grade and comment for submission, 1 grade and comment for review.
2. For each team: 1 submission, 2 review, 2 grade and comment for submission from different graders, 2 grade and comment for review from different graders.
...

We will generate some edge cases to test the robustness of our work.

== Important Links ==
#[https://github.com/duliwencynthia/expertiza/tree/beta Git path]
#[https://github.com/expertiza/expertiza/pull/2130 Pull Request]

== Team ==
'''Mentor:''' Xiao, Kai (yxiao28)

Yao, Kaiyong (kyao)

Hou, Guanyu (ghou3)

Du, Haoze (hdu5)

Du, Liwen (ldu2)

CSC/ECE 517 Fall 2021 - E2158. Grading audit trail

2021-11-09T03:56:55Z

Hdu5: /* Rspec Unit Tests */

== Problem Definition ==
After an instructor gave a grade to an assignment, there is no way to track who gave the grade. Any instructor can assign/edit a grade freely. There is no way of tracking who did it.

A grading audit trail must be created and the following information needs to be stored:
:1. When a grade is assigned by an instructor, there needs to be an indication of who did it and when it was done.
:2. Comments previously provided by other instructors must also be preserved.

This information needs to be stored every time an instructor edits a grade/comment and clicks the save button.

Currently, there are two places need to add grading audit trail:
:1. '''Review grade''': Log in as instructor -> Manage -> Assignments -> View Review Report
:2. '''Submission grade''': Log in as instructor -> Manage -> Assignments -> View submissions

The grading audit trail can probably be implemented as the submission records history on Expertiza.
The required page can be reached by logging in as instructor -> Manage -> Assignments -> View Submissions -> History

At the minimum, a grading log entry must include the '''instructor id''', '''assignment id''', '''student id''', '''grade''', '''comment''' and '''timestamp'''.

== Previous Implementation ==

=== Links ===
[https://expertiza.csc.ncsu.edu/index.php/E1934_-_Grading_Audit_Trail Previous Wiki Page]

[https://youtu.be/yyxX_kRYxLc Screencast]

=== Review ===

:1. '''Review grade''' part in the previous implementation served well, we only need to fix some UI issues in the current implementation;
:2. But for '''Submission grade''' part, we need to add a table in order to save submission history including the instructor id, assignment id, student id, grade, comment, and timestamp.

=== Issues with Previous Work ===
:1. For review grades, the “Grading History” link must not be in a separate column. It should be in smaller text below in the “Save” button.

:2. In the view grading record page, remove the receiver column and add it to the title.

:3. Restrict the column width on the grading record page.

:4. Add comments on list_submissions.html.erb to indicate that the alignment was changed to fix code climate issues.

:5. Revert changes made to list_review_mapping.html.erb.

:6. Remove the review_report-html.erb file.

== Proposed Solution ==
=== Expected View ===

[[File:E2158_Proposed_Solution_1.png|1100px|center]]
[[File:E2158_Proposed_Solution_2.png|1100px|center]]
[[File:E2158_Proposed_Solution_3.png|1100px|center]]

=== History of Comment and Grade for Reviews ===

In this part, we will modify the current view of review page, to add the link "history" to a proper place as the expected design picture shows.

The related table from databases is [https://expertiza.csc.ncsu.edu/index.php/Review_scores review_scores]. The ER table of review_scores is shown as below.

[[File:Review scores imported.png]]

=== History of Comment and Grade for Submissions===

In Expertiza, we find the fields related to grade and comment are located in the model '''team''', which is only able to be overwritten. Since there is no table to store the history of the comment and score given by instructors and TAs, we need to do:

:1. Review the related implementation of previous work in order to evaluate and understand the process of adding new models.

:2. Implement the related Model, View and Controller:

:* Model: grading_history.rb

:* Controller: grading_history_controller.rb

:* View: related pages.

Because in Expertiza the team ID will be generated for each given assignment, so the original design of grade / comment of team's submission are the field belongs to '''team'''. So our model uses the foreign key to only the team but not the related assignments or submissions.

The expected class of grading history could be shown as:

[[File:GradingHistory.png]]

== Testing Plan ==
=== Rspec Unit Tests ===
==== For History of the Grade of Reviews ====
The history of the grade and comments are related to this controller app/controllers/review_mapping_controller.rb and this view app/views/reports/_review_report.html.erb.

So the related RSpec tests are planned to be executed:

spec/controllers/review_mapping_controller_spec.rb

==== For History of the Grade of Team Submissions ====
The history of the grade and comments are related to the new model grading_history.rb and the new controller grading_history_controller.rb.

So the related RSpec tests are planned to be executed:

spec/models/grading_history.rb
spec/controllers/grading_history_controller.rb

=== Manual UI Testing ===

== Important Links ==
#[https://github.com/duliwencynthia/expertiza/tree/beta Git path]
#[https://github.com/expertiza/expertiza/pull/2130 Pull Request]

== Team ==
'''Mentor:''' Xiao, Kai (yxiao28)

Yao, Kaiyong (kyao)

Hou, Guanyu (ghou3)

Du, Haoze (hdu5)

Du, Liwen (ldu2)

CSC/ECE 517 Fall 2021 - E2158. Grading audit trail

2021-11-09T03:52:33Z

Hdu5: /* For History of the Grade of Reviews */

CSC/ECE 517 Fall 2021 - E2158. Grading audit trail

2021-11-09T03:52:05Z

Hdu5: /* For History of the Grade of Reviews */

CSC/ECE 517 Fall 2021 - E2158. Grading audit trail

2021-11-09T03:46:38Z

Hdu5: /* History of Comment and Grade for Submissions */

CSC/ECE 517 Fall 2021 - E2158. Grading audit trail

2021-11-09T03:41:23Z

Hdu5: /* Rspec Unit Tests */

CSC/ECE 517 Fall 2021 - E2158. Grading audit trail

2021-11-09T03:39:42Z

Hdu5: /* History of Comment and Grade for Submissions */

CSC/ECE 517 Fall 2021 - E2158. Grading audit trail

2021-11-09T03:39:09Z

Hdu5: /* History of Comment and Grade for Submissions */

File:GradingHistory.png

2021-11-09T03:38:39Z

Hdu5:

File:SubmissionHistoryER.png

2021-11-09T03:38:17Z

Hdu5: Hdu5 uploaded a new version of File:SubmissionHistoryER.png

File:SubmissionHistoryER.png

2021-11-09T03:37:59Z

Hdu5: Hdu5 uploaded a new version of File:SubmissionHistoryER.png

File:SubmissionHistoryER.png

2021-11-09T03:36:29Z

Hdu5: Hdu5 uploaded a new version of File:SubmissionHistoryER.png

File:SubmissionHistoryER.png

2021-11-09T03:35:06Z

Hdu5: Hdu5 uploaded a new version of File:SubmissionHistoryER.png

CSC/ECE 517 Fall 2021 - E2158. Grading audit trail

2021-11-09T03:34:10Z

Hdu5: /* History of Comment and Grade for Submissions */

CSC/ECE 517 Fall 2021 - E2158. Grading audit trail

2021-11-08T18:25:45Z

Hdu5: /* Previous Implementation */

CSC/ECE 517 Fall 2021 - E2158. Grading audit trail

2021-11-08T18:21:26Z

Hdu5: /* History of Comment and Grade for Submissions */

File:SubmissionHistoryER.png

2021-11-08T18:20:54Z

Hdu5:

CSC/ECE 517 Fall 2021 - E2158. Grading audit trail

2021-11-08T18:01:04Z

Hdu5: /* History of Comment and Grade for Submissions */

CSC/ECE 517 Fall 2021 - E2158. Grading audit trail

2021-11-08T17:57:52Z

Hdu5: /* History of Comment and Grade for Reviews */

CSC/ECE 517 Fall 2021 - E2158. Grading audit trail

2021-11-04T02:21:45Z

Hdu5: /* Important Links */

CSC/ECE 517 Fall 2021 - E2158. Grading audit trail

2021-11-04T02:16:18Z

Hdu5: /* History of Comment and Grade for Submissions */

CSC/ECE 517 Fall 2021 - E2158. Grading audit trail

2021-11-04T02:15:57Z

Hdu5: /* History of Comment and Grade for Submissions */

CSC/ECE 517 Fall 2021 - E2158. Grading audit trail

2021-11-04T02:15:39Z

Hdu5: /* History of Comment and Grade for Submissions */

CSC/ECE 517 Fall 2021 - E2158. Grading audit trail

2021-11-04T02:13:24Z

Hdu5: /* History of Comment and Grade for Submissions */

CSC/ECE 517 Fall 2021 - E2158. Grading audit trail

2021-11-04T02:04:01Z

Hdu5: /* Submission Grade */

CSC/ECE 517 Fall 2021 - E2158. Grading audit trail

2021-11-04T02:03:17Z

Hdu5: /* Review Grade */

CSC/ECE 517 Fall 2021 - E2158. Grading audit trail

2021-11-04T01:58:20Z

Hdu5: /* Overview */

CSC/ECE 517 Fall 2021 - E2158. Grading audit trail

2021-11-04T01:58:01Z

Hdu5: /* Previous Implementation */

CSC/ECE 517 Fall 2021 - E2158. Grading audit trail

2021-11-04T01:38:48Z

Hdu5: /* Expected View */

CSC/ECE 517 Fall 2021 - E2158. Grading audit trail

2021-11-04T01:38:10Z

Hdu5: /* Expected View */

CSC/ECE 517 Fall 2021 - E2158. Grading audit trail

2021-11-03T17:07:29Z

Hdu5: /* Proposed Solution */

= Problem Definition =
After an instructor gave a grade to an assignment, there is no way to track who gave the grade. Any instructor can assign/edit a grade freely. There is no way of tracking who did it.

A grading audit trail must be created and the following information needs to be stored:
:1. When a grade is assigned by an instructor, there needs to be an indication of who did it and when it was done.
:2. Comments previously provided by other instructors must also be preserved.

This information needs to be stored every time an instructor edits a grade/comment and clicks the save button.

Currently, there are two places need to add grading audit trail:
:1. '''Review grade''': Log in as instructor -> Manage -> Assignments -> View Review Report
:2. '''Submission grade''': Log in as instructor -> Manage -> Assignments -> View submissions

The grading audit trail can probably be implemented as the submission records history on Expertiza.
The required page can be reached by logging in as instructor -> Manage -> Assignments -> View Submissions -> History

At the minimum, a grading log entry must include the '''instructor id''', '''assignment id''', '''student id''', '''grade''', '''comment''' and '''timestamp'''.

= Previous Implementation =
== Overview ==
== Issues ==

= Proposed Solution =
== Review Grade ==
== Submission Grade ==

= Testing Plan =
= Important Links =
= Team =
'''Mentor:''' Xiao, Kai (yxiao28)

Yao, Kaiyong (kyao)

Hou, Guanyu (ghou3)

Du, Haoze (hdu5)

Du, Liwen (ldu2)

CSC/ECE 517 Fall 2021 - E2158. Grading audit trail

2021-11-03T15:42:06Z

Hdu5: /* Problem Definition */

= Problem Definition =
After an instructor gave a grade to an assignment, there is no way to track who gave the grade. Any instructor can assign/edit a grade freely. There is no way of tracking who did it.

A grading audit trail must be created and the following information needs to be stored:
:1. When a grade is assigned by an instructor, there needs to be an indication of who did it and when it was done.
:2. Comments previously provided by other instructors must also be preserved.

This information needs to be stored every time an instructor edits a grade/comment and clicks the save button.

Currently, there are two places need to add grading audit trail:
:1. '''Review grade''': Log in as instructor -> Manage -> Assignments -> View Review Report
:2. '''Submission grade''': Log in as instructor -> Manage -> Assignments -> View submissions

The grading audit trail can probably be implemented as the submission records history on Expertiza.
The required page can be reached by logging in as instructor -> Manage -> Assignments -> View Submissions -> History

At the minimum, a grading log entry must include the '''instructor id''', '''assignment id''', '''student id''', '''grade''', '''comment''' and '''timestamp'''.

= Previous Implementation =
== Overview ==
== Issues ==

= Proposed Solution =
= Testing Plan =
= Important Links =
= Team =
'''Mentor:''' Xiao, Kai (yxiao28)

Yao, Kaiyong (kyao)

Hou, Guanyu (ghou3)

Du, Haoze (hdu5)

Du, Liwen (ldu2)

CSC/ECE 517 Fall 2021 - E2158. Grading audit trail

2021-11-03T15:35:30Z

Hdu5:

= Problem Definition =
== Basic Task ==
After an instructor gave a grade to an assignment, there is no way to track who gave the grade. Any instructor can assign/edit a grade freely. There is no way of tracking who did it.

A grading audit trail must be created and the following information needs to be stored:
:1. When a grade is assigned by an instructor, there needs to be an indication of who did it and when it was done.
:2. Comments previously provided by other instructors must also be preserved.

This information needs to be stored every time an instructor edits a grade/comment and clicks the save button.

Currently, there are two places need to add grading audit trail:
:1. '''Review grade''': Log in as instructor -> Manage -> Assignments -> View Review Report
:2. '''Submission grade''': Log in as instructor -> Manage -> Assignments -> View submissions

At the minimum, a grading log entry must include the '''instructor id''', '''assignment id''', '''student id''', '''grade''', '''comment''' and '''timestamp'''.

= Previous Implementation =
== Overview ==
== Issues ==

= Proposed Solution =
= Testing Plan =
= Important Links =
= Team =
'''Mentor:''' Xiao, Kai (yxiao28)

Yao, Kaiyong (kyao)

Hou, Guanyu (ghou3)

Du, Haoze (hdu5)

Du, Liwen (ldu2)

CSC/ECE 517 Fall 2021 - E2158. Grading audit trail

2021-11-03T15:26:57Z

Hdu5: /* Team */

'''Bold text'''= Problem Definition =
== Basic Task ==
After an instructor gave a grade to an assignment, there is no way to track who gave the grade. Any instructor can assign/edit a grade freely. There is no way of tracking who did it.

A grading audit trail must be created and the following information needs to be stored:
:1. When a grade is assigned by an instructor, there needs to be an indication of who did it and when it was done.
:2. Comments previously provided by other instructors must also be preserved.

This information needs to be stored every time an instructor edits a grade/comment and clicks the save button.

Currently, there are two places need to add grading audit trail:
:1. '''Review grade''': Log in as instructor -> Manage -> Assignments -> View Review Report
:2. '''Submission grade''': Log in as instructor -> Manage -> Assignments -> View submissions

== Additional Task ==
Additionally, the grading audit trail can probably be a pattern of the submission records history on Expertiza.
The related page can be reached by:
:* '''View Submissions''': Log in as instructor -> Manage -> Assignments -> View Submissions -> History

At the minimum, a grading log entry must include the '''instructor id''', '''assignment id''', '''student id''', '''grade''', '''comment''' and '''timestamp'''.

= Previous Implementation =
== Overview ==
== Issues ==

= Proposed Solution =
= Testing Plan =
= Important Links =
= Team =
'''Mentor:''' Xiao, Kai (yxiao28)

Yao, Kaiyong (kyao)

Hou, Guanyu (ghou3)

Du, Haoze (hdu5)

Du, Liwen (ldu2)

CSC/ECE 517 Fall 2021 - E2158. Grading audit trail

2021-11-03T15:26:36Z

Hdu5: /* Team */

'''Bold text'''= Problem Definition =
== Basic Task ==
After an instructor gave a grade to an assignment, there is no way to track who gave the grade. Any instructor can assign/edit a grade freely. There is no way of tracking who did it.

A grading audit trail must be created and the following information needs to be stored:
:1. When a grade is assigned by an instructor, there needs to be an indication of who did it and when it was done.
:2. Comments previously provided by other instructors must also be preserved.

This information needs to be stored every time an instructor edits a grade/comment and clicks the save button.

Currently, there are two places need to add grading audit trail:
:1. '''Review grade''': Log in as instructor -> Manage -> Assignments -> View Review Report
:2. '''Submission grade''': Log in as instructor -> Manage -> Assignments -> View submissions

== Additional Task ==
Additionally, the grading audit trail can probably be a pattern of the submission records history on Expertiza.
The related page can be reached by:
:* '''View Submissions''': Log in as instructor -> Manage -> Assignments -> View Submissions -> History

At the minimum, a grading log entry must include the '''instructor id''', '''assignment id''', '''student id''', '''grade''', '''comment''' and '''timestamp'''.

= Previous Implementation =
== Overview ==
== Issues ==

= Proposed Solution =
= Testing Plan =
= Important Links =
= Team =
Xiao, Kai (yxiao28)

Yao, Kaiyong (kyao)

Hou, Guanyu (ghou3)

Du, Haoze (hdu5)

Du, Liwen (ldu2)

CSC/ECE 517 Fall 2021 - E2158. Grading audit trail

2021-11-03T15:25:57Z

Hdu5: /* Team */

'''Bold text'''= Problem Definition =
== Basic Task ==
After an instructor gave a grade to an assignment, there is no way to track who gave the grade. Any instructor can assign/edit a grade freely. There is no way of tracking who did it.

A grading audit trail must be created and the following information needs to be stored:
:1. When a grade is assigned by an instructor, there needs to be an indication of who did it and when it was done.
:2. Comments previously provided by other instructors must also be preserved.

This information needs to be stored every time an instructor edits a grade/comment and clicks the save button.

Currently, there are two places need to add grading audit trail:
:1. '''Review grade''': Log in as instructor -> Manage -> Assignments -> View Review Report
:2. '''Submission grade''': Log in as instructor -> Manage -> Assignments -> View submissions

== Additional Task ==
Additionally, the grading audit trail can probably be a pattern of the submission records history on Expertiza.
The related page can be reached by:
:* '''View Submissions''': Log in as instructor -> Manage -> Assignments -> View Submissions -> History

At the minimum, a grading log entry must include the '''instructor id''', '''assignment id''', '''student id''', '''grade''', '''comment''' and '''timestamp'''.

= Previous Implementation =
== Overview ==
== Issues ==

= Proposed Solution =
= Testing Plan =
= Important Links =
= Team =
Yao, Kaiyong (kyao)

Hou, Guanyu (ghou3)

Du, Haoze (hdu5)

Du, Liwen (ldu2)

CSC/ECE 517 Fall 2021 - E2158. Grading audit trail

2021-11-03T15:25:44Z

Hdu5: /* Team */

'''Bold text'''= Problem Definition =
== Basic Task ==
After an instructor gave a grade to an assignment, there is no way to track who gave the grade. Any instructor can assign/edit a grade freely. There is no way of tracking who did it.

A grading audit trail must be created and the following information needs to be stored:
:1. When a grade is assigned by an instructor, there needs to be an indication of who did it and when it was done.
:2. Comments previously provided by other instructors must also be preserved.

This information needs to be stored every time an instructor edits a grade/comment and clicks the save button.

Currently, there are two places need to add grading audit trail:
:1. '''Review grade''': Log in as instructor -> Manage -> Assignments -> View Review Report
:2. '''Submission grade''': Log in as instructor -> Manage -> Assignments -> View submissions

== Additional Task ==
Additionally, the grading audit trail can probably be a pattern of the submission records history on Expertiza.
The related page can be reached by:
:* '''View Submissions''': Log in as instructor -> Manage -> Assignments -> View Submissions -> History

At the minimum, a grading log entry must include the '''instructor id''', '''assignment id''', '''student id''', '''grade''', '''comment''' and '''timestamp'''.

= Previous Implementation =
== Overview ==
== Issues ==

= Proposed Solution =
= Testing Plan =
= Important Links =
= Team =
Yao, Kaiyong (kyao)
Hou, Guanyu (ghou3)
Du, Haoze (hdu5)
Du, Liwen (ldu2)

CSC/ECE 517 Fall 2021 - E2158. Grading audit trail

2021-11-03T15:20:49Z

Hdu5: /* Additional Task */

CSC/ECE 517 Fall 2021 - E2158. Grading audit trail

2021-11-03T15:19:56Z

Hdu5: /* Problem Definition */

'''Bold text'''= Problem Definition =
== Basic Task ==
After an instructor gave a grade to an assignment, there is no way to track who gave the grade. Any instructor can assign/edit a grade freely. There is no way of tracking who did it.

A grading audit trail must be created and the following information needs to be stored:
:1. When a grade is assigned by an instructor, there needs to be an indication of who did it and when it was done.
:2. Comments previously provided by other instructors must also be preserved.

This information needs to be stored every time an instructor edits a grade/comment and clicks the save button.

Currently, there are two places need to add grading audit trail:
:1. '''Review grade''': Log in as instructor -> Manage -> Assignments -> View Review Report
:2. '''Submission grade''': Log in as instructor -> Manage -> Assignments -> View submissions

== Additional Task ==
Additionally, the grading audit trail can probably be a pattern of the submission records history on Expertiza.
The related page can be reached by:
:* '''View Submissions''': Log in as instructor -> Manage -> Assignments -> View Submissions -> History

At the minimum, a grading log entry must include the ''instructor id'', ''assignment id'', ''student id'', ''grade'', ''comment'' and ''timestamp''.

= Previous Implementation =
== Overview ==
== Issues ==

= Proposed Solution =
= Testing Plan =
= Important Links =
= Team =

CSC/ECE 517 Fall 2021 - E2158. Grading audit trail

2021-11-03T15:17:22Z

Hdu5: /* Problem Definition */

= Problem Definition =
== Basic Task ==
After an instructor gave a grade to an assignment, there is no way to track who gave the grade. Any instructor can assign/edit a grade freely. There is no way of tracking who did it.

A grading audit trail must be created and the following information needs to be stored:
:1. When a grade is assigned by an instructor, there needs to be an indication of who did it and when it was done.
:2. Comments previously provided by other instructors must also be preserved.

This information needs to be stored every time an instructor edits a grade/comment and clicks the save button.

Currently, there are two places need to add grading audit trail:
:1. '''Review grade''': Log in as instructor -> Manage -> Assignments -> View Review Report
:2. '''Submission grade''': Log in as instructor -> Manage -> Assignments -> View submissions

== Additional Task ==
Additionally, the grading audit trail can probably be a pattern of the submission records history on Expertiza.
The related page can be reached by logging in as instructor -> Manage -> Assignments -> View Submissions -> History

At the minimum, a grading log entry must include the ''instructor id'', ''assignment id'', ''student id'', ''grade'', ''comment'' and ''timestamp''.

= Previous Implementation =
== Overview ==
== Issues ==

= Proposed Solution =
= Testing Plan =
= Important Links =
= Team =

CSC/ECE 517 Fall 2021 - E2158. Grading audit trail

2021-11-03T15:16:16Z

Hdu5: /* Problem Definition */

= Problem Definition =
After an instructor gave a grade to an assignment, there is no way to track who gave the grade. Any instructor can assign/edit a grade freely. There is no way of tracking who did it.

A grading audit trail must be created and the following information needs to be stored:
:1. When a grade is assigned by an instructor, there needs to be an indication of who did it and when it was done.
:2. Comments previously provided by other instructors must also be preserved.

This information needs to be stored every time an instructor edits a grade/comment and clicks the save button.

Currently, there are two places need to add grading audit trail:
:1. '''Review grade''': Log in as instructor -> Manage -> Assignments -> View Review Report
:2. '''Submission grade''': Log in as instructor -> Manage -> Assignments -> View submissions

Additionally, the grading audit trail can probably be a pattern of the submission records history on Expertiza.
The related page can be reached by logging in as instructor -> Manage -> Assignments -> View Submissions -> History

At the minimum, a grading log entry must include the ''instructor id'', ''assignment id'', ''student id'', ''grade'', ''comment'' and ''timestamp''.

= Previous Implementation =
== Overview ==
== Issues ==

= Proposed Solution =
= Testing Plan =
= Important Links =
= Team =

CSC/ECE 517 Fall 2021 - E2158. Grading audit trail

2021-11-03T15:13:35Z

Hdu5: /* Problem Definition */

= Problem Definition =
After an instructor gave a grade to an assignment, there is no way to track who gave the grade. Any instructor can assign/edit a grade freely. There is no way of tracking who did it.

A grading audit trail must be created and the following information needs to be stored:
:1. When a grade is assigned by an instructor, there needs to be an indication of who did it and when it was done.
:2. Comments previously provided by other instructors must also be preserved.

This information needs to be stored every time an instructor edits a grade/comment and clicks the save button.

Currently, there are two places need to add grading audit trail:
:1. '''Review grade''': Log in as instructor -> Manage -> Assignments -> View Review Report
:2. '''Submission grade''': Log in as instructor -> Manage -> Assignments -> View submissions

Additionally, the grading audit trail can probably pattern off of the submission records history on Expertiza.
The related page can be reached by logging in as instructor -> Manage -> Assignments -> View Submissions -> History

= Previous Implementation =
== Overview ==
== Issues ==

= Proposed Solution =
= Testing Plan =
= Important Links =
= Team =

CSC/ECE 517 Fall 2021 - E2158. Grading audit trail

2021-11-03T15:13:17Z

Hdu5:

= Problem Definition =
After an instructor gave a grade to an assignment, there is no way to track who gave the grade. Any instructor can assign/edit a grade freely. There is no way of tracking who did it.

A grading audit trail must be created and the following information needs to be stored:
:1. When a grade is assigned by an instructor, there needs to be an indication of who did it and when it was done.
:2. Comments previously provided by other instructors must also be preserved.

This information needs to be stored every time an instructor edits a grade/comment and clicks the save button.

Currently, there are two places need to add grading audit trail:
:1. '''Review grade''': Log in as instructor -> Manage -> Assignments -> View Review Report
:2. '''Submission grade''': Log in as instructor -> Manage -> Assignments -> View submissions

Additionally, the grading audit trail can probably pattern off of the submission records history on Expertiza.
The below page can be reached by logging in as instructor -> Manage -> Assignments -> View Submissions -> History

= Previous Implementation =
== Overview ==
== Issues ==

= Proposed Solution =
= Testing Plan =
= Important Links =
= Team =

CSC/ECE 517 Fall 2021

2021-11-03T14:58:39Z

Hdu5:

== OSS Projects ==

* [[CSC/ECE 517 Fall 2021 - E2117. Refactor questionaires_controller.rb]]
* [[CSC/ECE 517 Fall 2021 - E2128. Refactor student_quizzes_controller.rb & late_policies_controller.rb]]
* [[CSC/ECE 517 Fall 2021 - E2129. Refactor auth_controller.rb & password_retrieval_controller.rb]]
* [[CSC/ECE 517 Fall 2021 - E2132. Add tests cases for review mapping helper.rb]]
* [[CSC/ECE 517 Fall 2021 - E2134. Write unit tests for admin_controller.rb and institution_controller.rb]]
* [[CSC/ECE 517 Fall 2021 - E2138. Auto-generate submission directory names based on assignment]]
* [[CSC/ECE 517 Fall 2021 - E2142. Improve e-mail notifications]]
* [[CSC/ECE 517 Fall 2021 - E2133. Write tests for popup_controller.rb]]
* [[CSC/ECE 517 Fall 2021 - E2120. Refactor reputation_web_service_controller.rb]]
* [[CSC/ECE 517 Fall 2021 - E2139. Remove multiple topics at a time]]
* [[CSC/ECE 517 Fall 2021 - E2131. Improve assessment360_controller.rb]]
* [[CSC/ECE 517 Fall 2021 - E2121. Refactor suggestion_controller.rb]]
* [[CSC/ECE 517 Fall 2021 - E2122. Refactor impersonate_controller.rb]]
* [[CSC/ECE 517 Fall 2021 - E2123. Refactor sign_up_sheet_controller.rb]]
* [[CSC/ECE 517 Fall 2021 - E2126. Refactor account_request_controller.rb]]
* [[CSC/ECE 517 Fall 2021 - E2124. Refactor review_mapping_controller.rb]]
* [[CSC/ECE 517 Fall 2021 - E2125. Refactor review_mapping_helper.rb]]
* [[CSC/ECE 517 Fall 2021 - E2127. Refactor teams_controller]]
* [[CSC/ECE 517 Fall 2021 - E2130. Refactor submitted_content_controller.rb]]
* [[CSC/ECE 517 Fall 2021 - E2140. Create new late policy successfully and fix Bank link]]
* [[CSC/ECE 517 Fall 2021 - E2141. OSS project Finklestein: Instructors & Institutions]]
* [[CSC/ECE 517 Fall 2021 - E2144. Refactor delayed mailer and scheduled task]]
* [[CSC/ECE 517 Fall 2021 - E2147. Role-based reviewing]]
* [[CSC/ECE 517 Fall 2021 - E2145. OSS Project Beige]]
* [[CSC/ECE 517 Fall 2021 - E2146. Introduce a Student View for instructors]]
* [[CSC/ECE 517 Fall 2021 - Refactor Evaluation of SQL Queries]]
* [[CSC/ECE 517 Fall 2021 - E2135. Email notification to reviewers and instructors]]
* [[CSC/ECE 517 Fall 2021 - E2168. Testing - Reputations]]
* [[CSC/ECE 517 Fall 2021 - E2166. Testing - Scoring & Grades]]
* [[CSC/ECE 517 Fall 2021 - E2149. Finish Github metrics integration - Reputations]]

== Final Projects ==
* [https://expertiza.csc.ncsu.edu/index.php/CSC/ECE_517_Fall_2021_-_E2150._Integrate_suggestion_detection_algorithm#Description_about_project CSC/ECE 517 Fall 2021 - E2150. Integrate suggestion detection algorithm]
* [https://expertiza.csc.ncsu.edu/index.php/CSC/ECE_517_Fall_2021_-_E2151._Allow_reviewers_to_bid_on_what_to_review CSC/ECE 517 Fall 2021 - E2151. Allow reviewers to bid on what to review]
* [https://expertiza.csc.ncsu.edu/index.php/CSC/ECE_517_Fall_2021_-_E2152._Revision_planning_tool#Description_about_project CSC/ECE 517 Fall 2021 - E2152. Revision_planning_tool]
* [https://expertiza.csc.ncsu.edu/index.php/CSC/ECE_517_Fall_2021_-_E2170._Testing_-_Response_Maps#Description_about_project CSC/ECE 517 Fall 2021 - E2170. Testing - Response Maps]
* [https://expertiza.csc.ncsu.edu/index.php/CSC/ECE_517_Fall_2021_-_E2153._Improving_search_facility_in_Expertiza#Description_about_project CSC/ECE 517 Fall 2021 - E2153. Improving search facility in Expertiza]
* [https://expertiza.csc.ncsu.edu/index.php/CSC/ECE_517_Fall_2021_-_E2162._Further_refactoring_and_improvement_of_review_mapping_helper CSC/ECE 517 Fall 2021 - E2162. Further refactoring and improvement of review mapping helper]
* [https://expertiza.csc.ncsu.edu/index.php/CSC/ECE_517_Fall_2021_-_E2165._Fix_teammate-review_view CSC/ECE 517 Fall 2021 - E2165. Fix teammate review view ]
* [https://expertiza.csc.ncsu.edu/index.php/CSC/ECE_517_Fall_2021_-_E2155._Calibration_submissions_should_be_copied_along_with_calibration_assignments CSC/ECE 517 Fall 2021 - E2155. Calibration submissions should be copied along with calibration assignments]
* [https://expertiza.csc.ncsu.edu/index.php/CSC/ECE_517_Fall_2021_-_E2148._Completion/Progress_View CSC/ECE 517 Fall 2021 - E2148. Completion/Progress view]
* [https://expertiza.csc.ncsu.edu/index.php/CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail CSC/ECE 517 Fall 2021 - E2158. Grading audit trail ]
*[https://expertiza.csc.ncsu.edu/index.php/CSC/ECE_517_Fall_2021_-_E2159._Expertiza_internationalization CSC/ECE 517 Fall 2021 - E2159. Expertiza internationalization]
* [https://expertiza.csc.ncsu.edu/index.php/CSC/ECE_517_Fall_2021_-_E2160._Implementing_and_testing_import_export_controllers#Description_about_project CSC/ECE 517 Fall 2021 - E2160. Implementing and testing import and export controllers]