CSC/ECE 517 Fall 2020 - E2087. Conflict notification. Improve Search Facility In Expertiza: Difference between revisions
No edit summary |
|||
| Line 13: | Line 13: | ||
== Proposed Solution == | == Proposed Solution == | ||
The previous team implemented new logic to determine if a review is in conflict with another and created a new page to link the instructors to in the email. Because their functionality was good, we will mainly be focused on improving the UI of the conflict reports. Furthermore, there is a lot of logic that lives in the views that can be refactored and moved to controllers. Additionally, there is debug code that can be removed and tests that can be fleshed out. | |||
=== Logic in Views === | |||
File: app/views/reports/_review_conflict_metric.html.erb | |||
The logic to determine if answers are within or outside of the tolerance limits can be moved to functions outside of the .erb file. | |||
== UI Changes == | == UI Changes == | ||
Revision as of 18:56, 22 October 2020
Introduction
Expertiza includes the functionality of notifying instructors when a conflict occurs in review scores for a submission. Currently, when two reviews for the same submission differ significantly, an email is sent to the instructor of the course, but there is no link to the review that caused the conflict. This improvement will allow the professor to have links to the reviews that caused the conflict and will be formatted better to help the instructor understand the conflict.
Issues with previous submission
- The functionality is good but the UI of conflict report needs work.
- The UI needs to be cleaned up a little. When charts have only one or two bars, the chart can be compressed. The reviewer whose scores deviate from the threshold can be displayed in a different colored bar.
- Tests need to be refactored.
- They included their debug code in their pull request.
- They have included a lot of logic in the views.
- Shallow tests: one or more of their test expectations only focus on the return value not being `nil`, `empty` or not equal to `0` without testing the `real` value.
Proposed Solution
The previous team implemented new logic to determine if a review is in conflict with another and created a new page to link the instructors to in the email. Because their functionality was good, we will mainly be focused on improving the UI of the conflict reports. Furthermore, there is a lot of logic that lives in the views that can be refactored and moved to controllers. Additionally, there is debug code that can be removed and tests that can be fleshed out.
Logic in Views
File: app/views/reports/_review_conflict_metric.html.erb
The logic to determine if answers are within or outside of the tolerance limits can be moved to functions outside of the .erb file.
UI Changes
Test
Relevant Links
GitHub - https://github.com/salmonandrew/expertiza
Pull Request -
Team
Mentor: Sanket Pai (sgpai2@ncsu.edu)
- Yen-An Jou (yjou@ncsu.edu)
- Xiwen Chen (xchen33@ncsu.edu)
- Andrew Hirasawa (achirasa@ncsu.edu)
- Derrick Li (xli56@ncsu.edu)