Expertiza_Wiki - User contributions [en]

CSC/ECE 517 Fall 2018- Project E1865. Conflict Notification

2018-12-08T03:29:12Z

Pddalwad:

== '''Introduction''' ==

This project aims to enhance the review mapping of the two conflicting reviews which causes an email to be sent to the instructor when there is a considerable disparity in the grading between two reviews. The goal is to help the instructors by making the process of grading reviews easier and more accurate.

== '''Problem Statement''' ==

===Issue===

Currently, when a new review is submitted and the difference between the score of the new review and (average of the) scores of all previous reviews differ by more than a set threshold, an email is triggered to notify the instructor for such disparity. The email consists of an URL only for the new review.

== '''Application Flow''' ==

[[File:studentflowchart.png|frame|center]]

[[File:image_flow_2.jpeg|frame|center]]

== '''UML DIAGRAM''' ==

[[File:uml.gif|frame|center]]

== '''Implemented Solution''' ==

===Issue: Resolving the Conflict Notification===
Current scenario: The function 'significant_difference?' in the model response.rb takes on the average scores of all the existing reviews (by looping through each review to calculate the average) and compares it with the score of the recent response. If the difference is greater than the limit specified(notification_limit), it triggers an email to the instructor with the new response’s (conflicting response) URL.

Implemented changes: Instead of taking on the average scores for existing reviews, we will loop through each review not for calculating the average but to compare the new review score with each review score (a new function will be called to compare with existing responses once a new review is in system). If for any response the notification_limit is exceeded, the review URL of that iteration will be stored and at the end of the function once all the reviews are looped an email will be triggered comprising of the URL of a new page "conflict_view.html.erb" which displays the new review and all the previous conflicting reviews..

Files created/changed:
1. response_controller.rb

Added a function "conflict_view" which returns all the IDs of the conflicting reviews.

[[File:controller.JPG|frame|center]]

2. response.rb

Added a function "scores_and_count_for_prev_reviews" which checks the difference between the score of the new review and the score of each of the previous reviews and returns the response IDs of all the reviews whose difference is greater than a set threshold to an function named "significant difference?" which in turn triggers an email to notify the instructor.

[[File:model.JPG|frame|center]]

3. conflict_view.html.erb

Created a new view to display the new review and all the previous conflicting reviews to the instructor. (File on the github repo: https://github.com/cshinde57/expertiza)

4. routes.rb

Added a route for a newly created "conflict_view" page.

[[File:routes.JPG|frame|center]]

Snapshot for notification email triggered before implementing our changes.

[[File:beforeemail.JPG|frame|center]]

Snapshot for notification email triggered after implementing our changes.

[[File:afteremail.JPG|frame|center]]

Snapshot for the view which the instructor receives (before implementing our changes)

[[File:beforefix.PNG|frame|center]]

Snapshot for the view which the instructor receives (after implementing our changes)

[[File:afterfix.PNG|frame|center]]

Please watch the video provided to have a look on our implementation. Link: https://drive.google.com/drive/folders/1Z8rqRxdmXJYbOZzoptmBLP0kM7Bdul2Q?usp=sharing

== '''Test Plan''' ==

1. Rspec file "conflicting_response_spec.rb" is created to check if there is the function significant difference is working and an email is triggered or not.

[[File:spec.JPG|frame|center]]

== '''References''' ==

Expertiza
* https://expertiza.ncsu.edu/

Expertiza Github
* https://github.com/expertiza/expertiza

Github repo
* https://github.com/cshinde57/expertiza

Expertiza Documentation
* http://wiki.expertiza.ncsu.edu/index.php/Expertiza_documentation

CSC/ECE 517 Fall 2018- Project E1865. Conflict Notification

2018-12-08T03:26:36Z

Pddalwad:

== '''Introduction''' ==

This project aims to enhance the review mapping of the two conflicting reviews which causes an email to be sent to the instructor when there is a considerable disparity in the grading between two reviews. The goal is to help the instructors by making the process of grading reviews easier and more accurate.

== '''Problem Statement''' ==

===Issue===

Currently, when a new review is submitted and the difference between the score of the new review and (average of the) scores of all previous reviews differ by more than a set threshold, an email is triggered to notify the instructor for such disparity. The email consists of an URL only for the new review.

== '''Application Flow''' ==

[[File:studentflowchart.png|frame|center]]

[[File:image_flow_2.jpeg|frame|center]]

== '''UML DIAGRAM''' ==

[[File:uml.gif|frame|center]]

== '''Implemented Solution''' ==

===Issue: Resolving the Conflict Notification===
Current scenario: The function 'significant_difference?' in the model response.rb takes on the average scores of all the existing reviews (by looping through each review to calculate the average) and compares it with the score of the recent response. If the difference is greater than the limit specified(notification_limit), it triggers an email to the instructor with the new response’s (conflicting response) URL.

Implemented changes: Instead of taking on the average scores for existing reviews, we will loop through each review not for calculating the average but to compare the new review score with each review score (a new function will be called to compare with existing responses once a new review is in system). If for any response the notification_limit is exceeded, the review URL of that iteration will be stored and at the end of the function once all the reviews are looped an email will be triggered comprising of the URL of a new page "conflict_view.html.erb" which displays the new review and all the previous conflicting reviews..

Files created/changed:
1. response_controller.rb

Added a function "conflict_view" which returns all the IDs of the conflicting reviews.

[[File:controller.JPG|frame|center]]

2. response.rb

Added a function "scores_and_count_for_prev_reviews" which checks the difference between the score of the new review and the score of each of the previous reviews and returns the response IDs of all the reviews whose difference is greater than a set threshold to an function named "significant difference?" which in turn triggers an email to notify the instructor.

[[File:model.JPG|frame|center]]

3. conflict_view.html.erb

Created a new view to display the new review and all the previous conflicting reviews to the instructor. (File on the github repo: https://github.com/cshinde57/expertiza)

4. routes.rb

Added a route for a newly created "conflict_view" page.

[[File:routes.JPG|frame|center]]

Snapshot for notification email triggered before implementing our changes.

[[File:beforeemail.JPG|frame|center]]

Snapshot for notification email triggered after implementing our changes.

[[File:afteremail.JPG|frame|center]]

Snapshot for the view which the instructor receives (before implementing our changes)

[[File:beforefix.PNG|frame|center]]

Snapshot for the view which the instructor receives (after implementing our changes)

[[File:afterfix.PNG|frame|center]]

Please watch the video provided to have a look on our implementation. Link: https://drive.google.com/drive/folders/1Z8rqRxdmXJYbOZzoptmBLP0kM7Bdul2Q?usp=sharing

== '''Test Plan''' ==

1. Rspec file "response_spec.rb" is created to check if there is the function significant difference is working and an email is triggered or not.

[[File:spec.JPG|frame|center]]

== '''References''' ==

Expertiza
* https://expertiza.ncsu.edu/

Expertiza Github
* https://github.com/expertiza/expertiza

Github repo
* https://github.com/cshinde57/expertiza

Expertiza Documentation
* http://wiki.expertiza.ncsu.edu/index.php/Expertiza_documentation

File:Spec.JPG

2018-12-08T03:22:50Z

Pddalwad:

CSC/ECE 517 Fall 2018- Project E1865. Conflict Notification

2018-12-08T03:22:42Z

Pddalwad:

== '''Introduction''' ==

This project aims to enhance the review mapping of the two conflicting reviews which causes an email to be sent to the instructor when there is a considerable disparity in the grading between two reviews. The goal is to help the instructors by making the process of grading reviews easier and more accurate.

== '''Problem Statement''' ==

===Issue===

Currently, when a new review is submitted and the difference between the score of the new review and (average of the) scores of all previous reviews differ by more than a set threshold, an email is triggered to notify the instructor for such disparity. The email consists of an URL only for the new review.

== '''Application Flow''' ==

[[File:studentflowchart.png|frame|center]]

[[File:image_flow_2.jpeg|frame|center]]

== '''UML DIAGRAM''' ==

[[File:uml.gif|frame|center]]

== '''Implemented Solution''' ==

===Issue: Resolving the Conflict Notification===
Current scenario: The function 'significant_difference?' in the model response.rb takes on the average scores of all the existing reviews (by looping through each review to calculate the average) and compares it with the score of the recent response. If the difference is greater than the limit specified(notification_limit), it triggers an email to the instructor with the new response’s (conflicting response) URL.

Implemented changes: Instead of taking on the average scores for existing reviews, we will loop through each review not for calculating the average but to compare the new review score with each review score (a new function will be called to compare with existing responses once a new review is in system). If for any response the notification_limit is exceeded, the review URL of that iteration will be stored and at the end of the function once all the reviews are looped an email will be triggered comprising of the URL of a new page "conflict_view.html.erb" which displays the new review and all the previous conflicting reviews..

Files created/changed:
1. response_controller.rb

Added a function "conflict_view" which returns all the IDs of the conflicting reviews.

[[File:controller.JPG|frame|center]]

2. response.rb

Added a function "scores_and_count_for_prev_reviews" which checks the difference between the score of the new review and the score of each of the previous reviews and returns the response IDs of all the reviews whose difference is greater than a set threshold to an function named "significant difference?" which in turn triggers an email to notify the instructor.

[[File:model.JPG|frame|center]]

3. conflict_view.html.erb

Created a new view to display the new review and all the previous conflicting reviews to the instructor. (File on the github repo: https://github.com/cshinde57/expertiza)

4. routes.rb

Added a route for a newly created "conflict_view" page.

[[File:routes.JPG|frame|center]]

Snapshot for notification email triggered before implementing our changes.

[[File:beforeemail.JPG|frame|center]]

Snapshot for notification email triggered after implementing our changes.

[[File:afteremail.JPG|frame|center]]

Snapshot for the view which the instructor receives (before implementing our changes)

[[File:beforefix.PNG|frame|center]]

Snapshot for the view which the instructor receives (after implementing our changes)

[[File:afterfix.PNG|frame|center]]

Please watch the video provided to have a look on our implementation. Link:

== '''Test Plan''' ==

1. Rspec file "response_spec.rb" is created to check if there is the function significant difference is working and an email is triggered or not.

[[File:spec.JPG|frame|center]]

== '''References''' ==

Expertiza
* https://expertiza.ncsu.edu/

Expertiza Github
* https://github.com/expertiza/expertiza

Github repo
* https://github.com/cshinde57/expertiza

Expertiza Documentation
* http://wiki.expertiza.ncsu.edu/index.php/Expertiza_documentation

CSC/ECE 517 Fall 2018- Project E1865. Conflict Notification

2018-12-08T03:15:51Z

Pddalwad:

== '''Introduction''' ==

This project aims to enhance the review mapping of the two conflicting reviews which causes an email to be sent to the instructor when there is a considerable disparity in the grading between two reviews. The goal is to help the instructors by making the process of grading reviews easier and more accurate.

== '''Problem Statement''' ==

===Issue===

Currently, when a new review is submitted and the difference between the score of the new review and (average of the) scores of all previous reviews differ by more than a set threshold, an email is triggered to notify the instructor for such disparity. The email consists of an URL only for the new review.

== '''Application Flow''' ==

[[File:studentflowchart.png|frame|center]]

[[File:image_flow_2.jpeg|frame|center]]

== '''UML DIAGRAM''' ==

[[File:uml.gif|frame|center]]

== '''Implemented Solution''' ==

===Issue: Resolving the Conflict Notification===
Current scenario: The function 'significant_difference?' in the model response.rb takes on the average scores of all the existing reviews (by looping through each review to calculate the average) and compares it with the score of the recent response. If the difference is greater than the limit specified(notification_limit), it triggers an email to the instructor with the new response’s (conflicting response) URL.

Implemented changes: Instead of taking on the average scores for existing reviews, we will loop through each review not for calculating the average but to compare the new review score with each review score (a new function will be called to compare with existing responses once a new review is in system). If for any response the notification_limit is exceeded, the review URL of that iteration will be stored and at the end of the function once all the reviews are looped an email will be triggered comprising of the URL of a new page "conflict_view.html.erb" which displays the new review and all the previous conflicting reviews..

Files created/changed:
1. response_controller.rb

Added a function "conflict_view" which returns all the IDs of the conflicting reviews.

[[File:controller.JPG|frame|center]]

2. response.rb

Added a function "scores_and_count_for_prev_reviews" which checks the difference between the score of the new review and the score of each of the previous reviews and returns the response IDs of all the reviews whose difference is greater than a set threshold to an function named "significant difference?" which in turn triggers an email to notify the instructor.

[[File:model.JPG|frame|center]]

3. conflict_view.html.erb

Created a new view to display the new review and all the previous conflicting reviews to the instructor. (File on the github repo: https://github.com/cshinde57/expertiza)

4. routes.rb

Added a route for a newly created "conflict_view" page.

[[File:routes.JPG|frame|center]]

Snapshot for notification email triggered before implementing our changes.

[[File:beforeemail.JPG|frame|center]]

Snapshot for notification email triggered after implementing our changes.

[[File:afteremail.JPG|frame|center]]

Snapshot for the view which the instructor receives (before implementing our changes)

[[File:beforefix.PNG|frame|center]]

Snapshot for the view which the instructor receives (after implementing our changes)

[[File:afterfix.PNG|frame|center]]

Please watch the video provided to have a look on our implementation. Link:

== '''Test Plan''' ==

== '''References''' ==

Expertiza
* https://expertiza.ncsu.edu/

Expertiza Github
* https://github.com/expertiza/expertiza

Github repo
* https://github.com/cshinde57/expertiza

Expertiza Documentation
* http://wiki.expertiza.ncsu.edu/index.php/Expertiza_documentation

CSC/ECE 517 Fall 2018- Project E1865. Conflict Notification

2018-12-08T03:12:20Z

Pddalwad:

== '''Introduction''' ==

This project aims to enhance the review mapping of the two conflicting reviews which causes an email to be sent to the instructor when there is a considerable disparity in the grading between two reviews. The goal is to help the instructors by making the process of grading reviews easier and more accurate.

== '''Problem Statement''' ==

===Issue===

Currently, when a new review is submitted and the difference between the score of the new review and (average of the) scores of all previous reviews differ by more than a set threshold, an email is triggered to notify the instructor for such disparity. The email consists of an URL only for the new review.

== '''Application Flow''' ==

[[File:studentflowchart.png|frame|center]]

[[File:image_flow_2.jpeg|frame|center]]

== '''UML DIAGRAM''' ==

[[File:uml.gif|frame|center]]

== '''Implemented Solution''' ==

===Issue: Resolving the Conflict Notification===
Current scenario: The function 'significant_difference?' in the model response.rb takes on the average scores of all the existing reviews (by looping through each review to calculate the average) and compares it with the score of the recent response. If the difference is greater than the limit specified(notification_limit), it triggers an email to the instructor with the new response’s (conflicting response) URL.

Implemented changes: Instead of taking on the average scores for existing reviews, we will loop through each review not for calculating the average but to compare the new review score with each review score (a new function will be called to compare with existing responses once a new review is in system). If for any response the notification_limit is exceeded, the review URL of that iteration will be stored and at the end of the function once all the reviews are looped an email will be triggered comprising of the URL of a new page "conflict_view.html.erb" which displays the new review and all the previous conflicting reviews..

Files created/changed:
1. response_controller.rb

Added a function "conflict_view" which returns all the IDs of the conflicting reviews.

[[File:controller.JPG|frame|center]]

2. response.rb

Added a function "scores_and_count_for_prev_reviews" which checks the difference between the score of the new review and the score of each of the previous reviews and returns the response IDs of all the reviews whose difference is greater than a set threshold to an function named "significant difference?" which in turn triggers an email to notify the instructor.

[[File:model.JPG|frame|center]]

3. conflict_view.html.erb

Created a new view to display the new review and all the previous conflicting reviews to the instructor. (File on the github repo: https://github.com/cshinde57/expertiza)

4. routes.rb

Added a route for a newly created "conflict_view" page.

[[File:routes.JPG|frame|center]]

Snapshot for notification email triggered before implementing our changes.

[[File:beforeemail.JPG|frame|center]]

Snapshot for notification email triggered after implementing our changes.

[[File:afteremail.JPG|frame|center]]

Snapshot for the view which the instructor receives (before implementing our changes)

[[File:beforefix.PNG|frame|center]]

Snapshot for the view which the instructor receives (after implementing our changes)

[[File:afterfix.PNG|frame|center]]

Please watch the video provided to have a look on our implementation. Link:

== '''Test Plan''' ==

== '''References''' ==

Expertiza
* https://expertiza.ncsu.edu/

Expertiza Github
* https://github.com/expertiza/expertiza

Expertiza Documentation
* http://wiki.expertiza.ncsu.edu/index.php/Expertiza_documentation

CSC/ECE 517 Fall 2018- Project E1865. Conflict Notification

2018-12-08T03:10:32Z

Pddalwad:

== '''Introduction''' ==

This project aims to enhance the review mapping of the two conflicting reviews which causes an email to be sent to the instructor when there is a considerable disparity in the grading between two reviews. The goal is to help the instructors by making the process of grading reviews easier and more accurate.

== '''Problem Statement''' ==

===Issue===

Currently, when a new review is submitted and the difference between the score of the new review and (average of the) scores of all previous reviews differ by more than a set threshold, an email is triggered to notify the instructor for such disparity. The email consists of an URL only for the new review.

== '''Application Flow''' ==

[[File:studentflowchart.png|frame|center]]

[[File:image_flow_2.jpeg|frame|center]]

== '''UML DIAGRAM''' ==

[[File:uml.gif|frame|center]]

== '''Implemented Solution''' ==

===Issue: Resolving the Conflict Notification===
Current scenario: The function 'significant_difference?' in the model response.rb takes on the average scores of all the existing reviews (by looping through each review to calculate the average) and compares it with the score of the recent response. If the difference is greater than the limit specified(notification_limit), it triggers an email to the instructor with the new response’s (conflicting response) URL.

Implemented changes: Instead of taking on the average scores for existing reviews, we will loop through each review not for calculating the average but to compare the new review score with each review score (a new function will be called to compare with existing responses once a new review is in system). If for any response the notification_limit is exceeded, the review URL of that iteration will be stored and at the end of the function once all the reviews are looped an email will be triggered comprising of the URL of a new page "conflict_view.html.erb" which displays the new review and all the previous conflicting reviews..

Files created/changed:
1. response_controller.rb

Added a function "conflict_view" which returns all the IDs of the conflicting reviews.

[[File:controller.JPG|frame|center]]

2. response.rb

Added a function "scores_and_count_for_prev_reviews" which checks the difference between the score of the new review and the score of each of the previous reviews and returns the response IDs of all the reviews whose difference is greater than a set threshold to an function named "significant difference?" which in turn triggers an email to notify the instructor.

[[File:model.JPG|frame|center]]

3. conflict_view.html.erb

Created a new view to display the new review and all the previous conflicting reviews to the instructor.

4. routes.rb

Added a route for a newly created "conflict_view" page.

[[File:routes.JPG|frame|center]]

Snapshot for notification email triggered before implementing our changes.

[[File:beforeemail.JPG|frame|center]]

Snapshot for notification email triggered after implementing our changes.

[[File:afteremail.JPG|frame|center]]

Snapshot for the view which the instructor receives (before implementing our changes)

[[File:beforefix.PNG|frame|center]]

Snapshot for the view which the instructor receives (after implementing our changes)

[[File:afterfix.PNG|frame|center]]

== '''Test Plan''' ==

== '''References''' ==

Expertiza
* https://expertiza.ncsu.edu/

Expertiza Github
* https://github.com/expertiza/expertiza

Expertiza Documentation
* http://wiki.expertiza.ncsu.edu/index.php/Expertiza_documentation

CSC/ECE 517 Fall 2018- Project E1865. Conflict Notification

2018-12-08T03:09:47Z

Pddalwad:

== '''Introduction''' ==

This project aims to enhance the review mapping of the two conflicting reviews which causes an email to be sent to the instructor when there is a considerable disparity in the grading between two reviews. The goal is to help the instructors by making the process of grading reviews easier and more accurate.

== '''Problem Statement''' ==

===Issue===

Currently, when a new review is submitted and the difference between the score of the new review and (average of the) scores of all previous reviews differ by more than a set threshold, an email is triggered to notify the instructor for such disparity. The email consists of an URL only for the new review.

== '''Application Flow''' ==

[[File:studentflowchart.png|frame|center]]

[[File:image_flow_2.jpeg|frame|center]]

== '''UML DIAGRAM''' ==

[[File:uml.gif|frame|center]]

== '''Implemented Solution''' ==

===Issue: Resolving the Conflict Notification===
Current scenario: The function 'significant_difference?' in the model response.rb takes on the average scores of all the existing reviews (by looping through each review to calculate the average) and compares it with the score of the recent response. If the difference is greater than the limit specified(notification_limit), it triggers an email to the instructor with the new response’s (conflicting response) URL.

Implemented changes: Instead of taking on the average scores for existing reviews, we will loop through each review not for calculating the average but to compare the new review score with each review score (a new function will be called to compare with existing responses once a new review is in system). If for any response the notification_limit is exceeded, the review URL of that iteration will be stored and at the end of the function once all the reviews are looped an email will be triggered comprising of the URL of a new page "conflict_view.html.erb" which displays the new review and all the previous conflicting reviews..

Files created/changed:
1. response_controller.rb

Added a function "conflict_view" which returns all the IDs of the conflicting reviews.

[[File:controller.JPG|frame|center]]

2. response.rb

Added a function "scores_and_count_for_prev_reviews" which checks the difference between the score of the new review and the score of each of the previous reviews and returns the response IDs of all the reviews whose difference is greater than a set threshold to an function named "significant difference?" which in turn triggers an email to notify the instructor.

[[File:model.JPG|frame|center]]

3. conflict_view.html.erb

Created a new view to display the new review and all the previous conflicting reviews to the instructor.

[[File:view.JPG|frame|center]]

4. routes.rb

Added a route for a newly created "conflict_view" page.

[[File:routes.JPG|frame|center]]

Snapshot for notification email triggered before implementing our changes.

[[File:beforeemail.JPG|frame|center]]

Snapshot for notification email triggered after implementing our changes.

[[File:afteremail.JPG|frame|center]]

Snapshot for the view which the instructor receives (before implementing our changes)

[[File:beforefix.PNG|frame|center]]

Snapshot for the view which the instructor receives (after implementing our changes)

[[File:afterfix.PNG.JPG|frame|center]]

== '''Test Plan''' ==

== '''References''' ==

Expertiza
* https://expertiza.ncsu.edu/

Expertiza Github
* https://github.com/expertiza/expertiza

Expertiza Documentation
* http://wiki.expertiza.ncsu.edu/index.php/Expertiza_documentation

File:Beforefix.PNG

2018-12-08T03:08:38Z

Pddalwad:

File:Afterfix.PNG

2018-12-08T03:08:29Z

Pddalwad:

File:Beforeemail.JPG

2018-12-08T03:08:17Z

Pddalwad:

File:Afteremail.JPG

2018-12-08T03:08:07Z

Pddalwad:

File:Routes.JPG

2018-12-08T03:07:58Z

Pddalwad:

CSC/ECE 517 Fall 2018- Project E1865. Conflict Notification

2018-12-08T02:47:30Z

Pddalwad:

== '''Introduction''' ==

This project aims to enhance the review mapping of the two conflicting reviews which causes an email to be sent to the instructor when there is a considerable disparity in the grading between two reviews. The goal is to help the instructors by making the process of grading reviews easier and more accurate.

== '''Problem Statement''' ==

===Issue===

Currently, when a new review is submitted and the difference between the score of the new review and (average of the) scores of all previous reviews differ by more than a set threshold, an email is triggered to notify the instructor for such disparity. The email consists of an URL only for the new review.

== '''Application Flow''' ==

[[File:studentflowchart.png|frame|center]]

[[File:image_flow_2.jpeg|frame|center]]

== '''UML DIAGRAM''' ==

[[File:uml.gif|frame|center]]

== '''Implemented Solution''' ==

===Issue: Resolving the Conflict Notification===
Current scenario: The function 'significant_difference?' in the model response.rb takes on the average scores of all the existing reviews (by looping through each review to calculate the average) and compares it with the score of the recent response. If the difference is greater than the limit specified(notification_limit), it triggers an email to the instructor with the new response’s (conflicting response) URL.

Implemented changes: Instead of taking on the average scores for existing reviews, we will loop through each review not for calculating the average but to compare the new review score with each review score (a new function will be called to compare with existing responses once a new review is in system). If for any response the notification_limit is exceeded, the review URL of that iteration will be stored and at the end of the function once all the reviews are looped an email will be triggered comprising of the URL of a new page "conflict_view.html.erb" which displays the new review and all the previous conflicting reviews..

Files created/changed:
1. response_controller.rb

Added a function "conflict_view" which returns all the IDs of the conflicting reviews.

[[File:controller.JPG|frame|center]]

2. response.rb

Added a function "scores_and_count_for_prev_reviews" which checks the difference between the score of the new review and the score of each of the previous reviews and returns the response IDs of all the reviews whose difference is greater than a set threshold to an function named "significant difference?" which in turn triggers an email to notify the instructor.

[[File:model.JPG|frame|center]]

3. conflict_view.html.erb

Created a new view to display the new review and all the previous conflicting reviews to the instructor.

[[File:view.JPG|frame|center]]

4. routes.rb

Added a route for a newly created "conflict_view" page.

[[File:route.JPG|frame|center]]

Snapshot for notification email triggered before implementing our changes.

[[File:email1.JPG|frame|center]]

Snapshot for notification email triggered after implementing our changes.

[[File:email2.JPG|frame|center]]

Snapshot for the view which the instructor receives (before implementing our changes)

[[File:view1.JPG|frame|center]]

Snapshot for the view which the instructor receives (after implementing our changes)

[[File:view2.JPG|frame|center]]

== '''Test Plan''' ==

== '''References''' ==

Expertiza
* https://expertiza.ncsu.edu/

Expertiza Github
* https://github.com/expertiza/expertiza

Expertiza Documentation
* http://wiki.expertiza.ncsu.edu/index.php/Expertiza_documentation

CSC/ECE 517 Fall 2018- Project E1865. Conflict Notification

2018-12-08T02:03:43Z

Pddalwad:

== '''Introduction''' ==

This project aims to enhance the review mapping of the two conflicting reviews which causes an email to be sent to the instructor when there is a considerable disparity in the grading between two reviews. The goal is to help the instructors by making the process of grading reviews easier and more accurate.

== '''Problem Statement''' ==

===Issue===

Currently, when a new review is submitted and the difference between the score of the new review and (average of the) scores of all previous reviews differ by more than a set threshold, an email is triggered to notify the instructor for such disparity. The email consists of an URL only for the new review.

== '''Application Flow''' ==

[[File:studentflowchart.png|frame|center]]

[[File:image_flow_2.jpeg|frame|center]]

== '''UML DIAGRAM''' ==

[[File:uml.gif|frame|center]]

== '''Proposed Solutions''' ==

===Issue: Resolving the Conflict Notification===
Current scenario: The function 'significant_difference?' in the model response.rb takes on the average scores of all the existing reviews (by looping through each review to calculate the average) and compares it with the score of the recent response. If the difference is greater than the limit specified(notification_limit), it triggers an email to the instructor with the new response’s (conflicting response) URL.

Implemented changes: Instead of taking on the average scores for existing reviews, we will loop through each review not for calculating the average but to compare the new review score with each review score (a new function will be called to compare with existing responses once a new review is in system). If for any response the notification_limit is exceeded, the review URL of that iteration will be stored and at the end of the function once all the reviews are looped an email will be triggered comprising of the new review and stored reviews URLs.

Implemented solution:

Files created/changed:
1. response_controller.rb

Added a function "conflict_view" which returns all the IDs of the conflicting reviews.

[[File:controller.JPG|frame|center]]

2. response.rb

Added a function "scores_and_count_for_prev_reviews" which checks the difference between the score of the new review and the score of each of the previous reviews and returns the response IDs of all the reviews whose difference is greater than a set threshold to an function named "significant difference?" which in turn triggers an email to notify the instructor.

[[File:model.JPG|frame|center]]

3. conflict_view.html.erb

Created a new view to display the new review and all the previous conflicting reviews to the instructor.

[[File:view.JPG|frame|center]]

4. routes.rb

Added a route for a newly created "conflict_view" page.

[[File:route.JPG|frame|center]]

== '''Test Plan''' ==

1) Login.

2) Click on ‘Assignments’ tab.

3) Click on the assignment which has to be reviewed.

4) Navigate to ‘Other’s Work’ section to open the reviews summary.

5) Select a team’s assignment and review it.

6) Give a review score (make one user to give all 0’s and other reviewer to give all 5’s for the same assignment) which in turn exceeds the threshold and submit.

7) Logout and check whether the instructor received an email for conflicting reviews.

== '''References''' ==

Expertiza
* https://expertiza.ncsu.edu/

Expertiza Github
* https://github.com/expertiza/expertiza

Expertiza Documentation
* http://wiki.expertiza.ncsu.edu/index.php/Expertiza_documentation

File:Studentflowchart.png

2018-12-08T02:02:47Z

Pddalwad:

CSC/ECE 517 Fall 2018- Project E1865. Conflict Notification

2018-12-08T02:02:35Z

Pddalwad:

== '''Introduction''' ==

This project aims to enhance the review mapping of the two conflicting reviews which causes an email to be sent to the instructor when there is a considerable disparity in the grading between two reviews. The goal is to help the instructors by making the process of grading reviews easier and more accurate.

== '''Problem Statement''' ==

===Issue===

Currently, when a new review is submitted and the difference between the score of the new review and (average of the) scores of all previous reviews differ by more than a set threshold, an email is triggered to notify the instructor for such disparity. The email consists of an URL only for the new review.

== '''Application Flow''' ==

[[File:image_flow_1.jpeg|frame|center]]

[[File:studentflowchart.png|frame|center]]

[[File:image_flow_2.jpeg|frame|center]]

== '''UML DIAGRAM''' ==

[[File:uml.gif|frame|center]]

== '''Proposed Solutions''' ==

===Issue: Resolving the Conflict Notification===
Current scenario: The function 'significant_difference?' in the model response.rb takes on the average scores of all the existing reviews (by looping through each review to calculate the average) and compares it with the score of the recent response. If the difference is greater than the limit specified(notification_limit), it triggers an email to the instructor with the new response’s (conflicting response) URL.

Implemented changes: Instead of taking on the average scores for existing reviews, we will loop through each review not for calculating the average but to compare the new review score with each review score (a new function will be called to compare with existing responses once a new review is in system). If for any response the notification_limit is exceeded, the review URL of that iteration will be stored and at the end of the function once all the reviews are looped an email will be triggered comprising of the new review and stored reviews URLs.

Implemented solution:

Files created/changed:
1. response_controller.rb

Added a function "conflict_view" which returns all the IDs of the conflicting reviews.

[[File:controller.JPG|frame|center]]

2. response.rb

Added a function "scores_and_count_for_prev_reviews" which checks the difference between the score of the new review and the score of each of the previous reviews and returns the response IDs of all the reviews whose difference is greater than a set threshold to an function named "significant difference?" which in turn triggers an email to notify the instructor.

[[File:model.JPG|frame|center]]

3. conflict_view.html.erb

Created a new view to display the new review and all the previous conflicting reviews to the instructor.

[[File:view.JPG|frame|center]]

4. routes.rb

Added a route for a newly created "conflict_view" page.

[[File:route.JPG|frame|center]]

== '''Test Plan''' ==

1) Login.

2) Click on ‘Assignments’ tab.

3) Click on the assignment which has to be reviewed.

4) Navigate to ‘Other’s Work’ section to open the reviews summary.

5) Select a team’s assignment and review it.

6) Give a review score (make one user to give all 0’s and other reviewer to give all 5’s for the same assignment) which in turn exceeds the threshold and submit.

7) Logout and check whether the instructor received an email for conflicting reviews.

== '''References''' ==

Expertiza
* https://expertiza.ncsu.edu/

Expertiza Github
* https://github.com/expertiza/expertiza

Expertiza Documentation
* http://wiki.expertiza.ncsu.edu/index.php/Expertiza_documentation

CSC/ECE 517 Fall 2018- Project E1865. Conflict Notification

2018-12-08T02:00:30Z

Pddalwad:

== '''Introduction''' ==

This project aims to enhance the review mapping of the two conflicting reviews which causes an email to be sent to the instructor when there is a considerable disparity in the grading between two reviews. The goal is to help the instructors by making the process of grading reviews easier and more accurate.

== '''Problem Statement''' ==

===Issue===

Currently, when a new review is submitted and the difference between the score of the new review and (average of the) scores of all previous reviews differ by more than a set threshold, an email is triggered to notify the instructor for such disparity. The email consists of an URL only for the new review.

== '''Application Flow''' ==

[[File:image_flow_1.jpeg|frame|center]]

[[File:image_flow_2.jpeg|frame|center]]

== '''UML DIAGRAM''' ==

[[File:uml.gif|frame|center]]

== '''Proposed Solutions''' ==

===Issue: Resolving the Conflict Notification===
Current scenario: The function 'significant_difference?' in the model response.rb takes on the average scores of all the existing reviews (by looping through each review to calculate the average) and compares it with the score of the recent response. If the difference is greater than the limit specified(notification_limit), it triggers an email to the instructor with the new response’s (conflicting response) URL.

Implemented changes: Instead of taking on the average scores for existing reviews, we will loop through each review not for calculating the average but to compare the new review score with each review score (a new function will be called to compare with existing responses once a new review is in system). If for any response the notification_limit is exceeded, the review URL of that iteration will be stored and at the end of the function once all the reviews are looped an email will be triggered comprising of the new review and stored reviews URLs.

Implemented solution:

Files created/changed:
1. response_controller.rb

Added a function "conflict_view" which returns all the IDs of the conflicting reviews.

[[File:controller.JPG|frame|center]]

2. response.rb

Added a function "scores_and_count_for_prev_reviews" which checks the difference between the score of the new review and the score of each of the previous reviews and returns the response IDs of all the reviews whose difference is greater than a set threshold to an function named "significant difference?" which in turn triggers an email to notify the instructor.

[[File:model.JPG|frame|center]]

3. conflict_view.html.erb

Created a new view to display the new review and all the previous conflicting reviews to the instructor.

[[File:view.JPG|frame|center]]

4. routes.rb

Added a route for a newly created "conflict_view" page.

[[File:route.JPG|frame|center]]

== '''Test Plan''' ==

1) Login.

2) Click on ‘Assignments’ tab.

3) Click on the assignment which has to be reviewed.

4) Navigate to ‘Other’s Work’ section to open the reviews summary.

5) Select a team’s assignment and review it.

6) Give a review score (make one user to give all 0’s and other reviewer to give all 5’s for the same assignment) which in turn exceeds the threshold and submit.

7) Logout and check whether the instructor received an email for conflicting reviews.

== '''References''' ==

Expertiza
* https://expertiza.ncsu.edu/

Expertiza Github
* https://github.com/expertiza/expertiza

Expertiza Documentation
* http://wiki.expertiza.ncsu.edu/index.php/Expertiza_documentation

CSC/ECE 517 Fall 2018- Project E1865. Conflict Notification

2018-12-08T01:55:40Z

Pddalwad:

== '''Introduction''' ==

This project aims to enhance the review mapping of the two conflicting reviews which causes an email to be sent to the instructor when there is a considerable disparity in the grading between two reviews. The goal is to help the instructors by making the process of grading reviews easier and more accurate.

== '''Problem Statement''' ==

===Issue===

Currently, when a new review is submitted and the difference between the score of the new review and (average of the) scores of all previous reviews differ by more than a set threshold, an email is triggered to notify the instructor for such disparity. The email consists of an URL only for the new review.

== '''Application Flow''' ==

[[File:image_flow_1.jpeg|frame|center]]

[[File:image_flow_2.jpeg|frame|center]]

== '''UML DIAGRAM''' ==

[[File:uml.gif|frame|center]]

== '''Proposed Solutions''' ==

===Issue: Resolving the Conflict Notification===
Current scenario: The function 'significant_difference?' in the model response.rb takes on the average scores of all the existing reviews (by looping through each review to calculate the average) and compares it with the score of the recent response. If the difference is greater than the limit specified(notification_limit), it triggers an email to the instructor with the new response’s (conflicting response) URL.

Proposed changes: Instead of taking on the average scores for existing reviews, we will loop through each review not for calculating the average but to compare the new review score with each review score (a new function will be called to compare with existing responses once a new review is in system i.e. ‘questionnaire’ variable). If for any response the notification_limit is exceeded, the review URL of that iteration will be stored and at the end of the function once all the reviews are looped an email will be triggered comprising of the new review and stored reviews URLs.

Implemented solution:

Files created/changed:
1. response_controller.rb

Added a function "conflict_view" which returns all the IDs of the conflicting reviews.

[[File:controller.JPG|frame|center]]

2. response.rb

Added a function "scores_and_count_for_prev_reviews" which checks the difference between the score of the new review and the score of each of the previous reviews and returns the response IDs of all the reviews whose difference is greater than a set threshold to an function named "significant difference?" which in turn triggers an email to notify the instructor.

[[File:model.JPG|frame|center]]

3. conflict_view.html.erb

Created a new view to display the new review and all the previous conflicting reviews to the instructor.

[[File:view.JPG|frame|center]]

4. routes.rb

Added a route for a newly created "conflict_view" page.

[[File:route.JPG|frame|center]]

== '''Test Plan''' ==

1) Login.

2) Click on ‘Assignments’ tab.

3) Click on the assignment which has to be reviewed.

4) Navigate to ‘Other’s Work’ section to open the reviews summary.

5) Select a team’s assignment and review it.

6) Give a review score (make one user to give all 0’s and other reviewer to give all 5’s for the same assignment) which in turn exceeds the threshold and submit.

7) Logout and check whether the instructor received an email for conflicting reviews.

== '''References''' ==

Expertiza
* https://expertiza.ncsu.edu/

Expertiza Github
* https://github.com/expertiza/expertiza

Expertiza Documentation
* http://wiki.expertiza.ncsu.edu/index.php/Expertiza_documentation

CSC/ECE 517 Fall 2018- Project E1865. Conflict Notification

2018-12-08T01:49:11Z

Pddalwad:

== '''Introduction''' ==

This project aims to enhance the review mapping of the two conflicting reviews which causes an email to be sent to the instructor when there is a considerable disparity in the grading between two reviews. The goal is to help the instructors by making the process of grading reviews easier and more accurate.

== '''Problem Statement''' ==

===Issue===

Currently, when a new review is submitted and the difference between the score of the new review and (average of the) scores of all previous reviews differ by more than a set threshold, an email is triggered to notify the instructor for such disparity. The email consists of an URL only for the new review.

== '''Application Flow''' ==

[[File:studentflow1.jpeg|frame|center]]

[[File:image_flow_2.jpeg|frame|center]]

== '''UML DIAGRAM''' ==

[[File:uml.gif|frame|center]]

== '''Proposed Solutions''' ==

===Issue: Resolving the Conflict Notification===
Current scenario: The function 'significant_difference?' in the model response.rb takes on the average scores of all the existing reviews (by looping through each review to calculate the average) and compares it with the score of the recent response. If the difference is greater than the limit specified(notification_limit), it triggers an email to the instructor with the new response’s (conflicting response) URL.

Proposed changes: Instead of taking on the average scores for existing reviews, we will loop through each review not for calculating the average but to compare the new review score with each review score (a new function will be called to compare with existing responses once a new review is in system i.e. ‘questionnaire’ variable). If for any response the notification_limit is exceeded, the review URL of that iteration will be stored and at the end of the function once all the reviews are looped an email will be triggered comprising of the new review and stored reviews URLs.

Implemented solution:

Files changed:
1. response_controller.rb

[[File:controller.JPG|200x250px|frame|center]]

2. response.rb

[[File:model.JPG|200x250px|frame|center]]

== '''Test Plan''' ==

1) Login.

2) Click on ‘Assignments’ tab.

3) Click on the assignment which has to be reviewed.

4) Navigate to ‘Other’s Work’ section to open the reviews summary.

5) Select a team’s assignment and review it.

6) Give a review score (make one user to give all 0’s and other reviewer to give all 5’s for the same assignment) which in turn exceeds the threshold and submit.

7) Logout and check whether the instructor received an email for conflicting reviews.

== '''References''' ==

Expertiza
* https://expertiza.ncsu.edu/

Expertiza Github
* https://github.com/expertiza/expertiza

Expertiza Documentation
* http://wiki.expertiza.ncsu.edu/index.php/Expertiza_documentation

CSC/ECE 517 Fall 2018- Project E1865. Conflict Notification

2018-12-08T01:47:20Z

Pddalwad:

== '''Introduction''' ==

This project aims to enhance the review mapping of the two conflicting reviews which causes an email to be sent to the instructor when there is a considerable disparity in the grading between two reviews. The goal is to help the instructors by making the process of grading reviews easier and more accurate.

== '''Problem Statement''' ==

===Issue===

Currently, when a new review is submitted and the difference between the score of the new review and (average of the) scores of all previous reviews differ by more than a set threshold, an email is triggered to notify the instructor for such disparity. The email consists of an URL only for the new review.

== '''Application Flow''' ==

[[File:studentflow.png|10x10|frame|center]]

[[File:image_flow_2.jpeg|frame|center]]

== '''UML DIAGRAM''' ==

[[File:uml.gif|frame|center]]

== '''Proposed Solutions''' ==

===Issue: Resolving the Conflict Notification===
Current scenario: The function 'significant_difference?' in the model response.rb takes on the average scores of all the existing reviews (by looping through each review to calculate the average) and compares it with the score of the recent response. If the difference is greater than the limit specified(notification_limit), it triggers an email to the instructor with the new response’s (conflicting response) URL.

Proposed changes: Instead of taking on the average scores for existing reviews, we will loop through each review not for calculating the average but to compare the new review score with each review score (a new function will be called to compare with existing responses once a new review is in system i.e. ‘questionnaire’ variable). If for any response the notification_limit is exceeded, the review URL of that iteration will be stored and at the end of the function once all the reviews are looped an email will be triggered comprising of the new review and stored reviews URLs.

Implemented solution:

Files changed:
1. response_controller.rb

[[File:controller.JPG|200x250px|frame|center]]

2. response.rb

[[File:model.JPG|200x250px|frame|center]]

== '''Test Plan''' ==

1) Login.

2) Click on ‘Assignments’ tab.

3) Click on the assignment which has to be reviewed.

4) Navigate to ‘Other’s Work’ section to open the reviews summary.

5) Select a team’s assignment and review it.

6) Give a review score (make one user to give all 0’s and other reviewer to give all 5’s for the same assignment) which in turn exceeds the threshold and submit.

7) Logout and check whether the instructor received an email for conflicting reviews.

== '''References''' ==

Expertiza
* https://expertiza.ncsu.edu/

Expertiza Github
* https://github.com/expertiza/expertiza

Expertiza Documentation
* http://wiki.expertiza.ncsu.edu/index.php/Expertiza_documentation

CSC/ECE 517 Fall 2018- Project E1865. Conflict Notification

2018-12-08T01:47:05Z

Pddalwad:

== '''Introduction''' ==

This project aims to enhance the review mapping of the two conflicting reviews which causes an email to be sent to the instructor when there is a considerable disparity in the grading between two reviews. The goal is to help the instructors by making the process of grading reviews easier and more accurate.

== '''Problem Statement''' ==

===Issue===

Currently, when a new review is submitted and the difference between the score of the new review and (average of the) scores of all previous reviews differ by more than a set threshold, an email is triggered to notify the instructor for such disparity. The email consists of an URL only for the new review.

== '''Application Flow''' ==

[[File:studentflow.png|50x50|frame|center]]

[[File:image_flow_2.jpeg|frame|center]]

== '''UML DIAGRAM''' ==

[[File:uml.gif|frame|center]]

== '''Proposed Solutions''' ==

===Issue: Resolving the Conflict Notification===
Current scenario: The function 'significant_difference?' in the model response.rb takes on the average scores of all the existing reviews (by looping through each review to calculate the average) and compares it with the score of the recent response. If the difference is greater than the limit specified(notification_limit), it triggers an email to the instructor with the new response’s (conflicting response) URL.

Proposed changes: Instead of taking on the average scores for existing reviews, we will loop through each review not for calculating the average but to compare the new review score with each review score (a new function will be called to compare with existing responses once a new review is in system i.e. ‘questionnaire’ variable). If for any response the notification_limit is exceeded, the review URL of that iteration will be stored and at the end of the function once all the reviews are looped an email will be triggered comprising of the new review and stored reviews URLs.

Implemented solution:

Files changed:
1. response_controller.rb

[[File:controller.JPG|200x250px|frame|center]]

2. response.rb

[[File:model.JPG|200x250px|frame|center]]

== '''Test Plan''' ==

1) Login.

2) Click on ‘Assignments’ tab.

3) Click on the assignment which has to be reviewed.

4) Navigate to ‘Other’s Work’ section to open the reviews summary.

5) Select a team’s assignment and review it.

6) Give a review score (make one user to give all 0’s and other reviewer to give all 5’s for the same assignment) which in turn exceeds the threshold and submit.

7) Logout and check whether the instructor received an email for conflicting reviews.

== '''References''' ==

Expertiza
* https://expertiza.ncsu.edu/

Expertiza Github
* https://github.com/expertiza/expertiza

Expertiza Documentation
* http://wiki.expertiza.ncsu.edu/index.php/Expertiza_documentation

CSC/ECE 517 Fall 2018- Project E1865. Conflict Notification

2018-12-08T01:46:34Z

Pddalwad:

== '''Introduction''' ==

This project aims to enhance the review mapping of the two conflicting reviews which causes an email to be sent to the instructor when there is a considerable disparity in the grading between two reviews. The goal is to help the instructors by making the process of grading reviews easier and more accurate.

== '''Problem Statement''' ==

===Issue===

Currently, when a new review is submitted and the difference between the score of the new review and (average of the) scores of all previous reviews differ by more than a set threshold, an email is triggered to notify the instructor for such disparity. The email consists of an URL only for the new review.

== '''Application Flow''' ==

[[File:studentflow.png|50x50]]

[[File:image_flow_2.jpeg|frame|center]]

== '''UML DIAGRAM''' ==

[[File:uml.gif|frame|center]]

== '''Proposed Solutions''' ==

===Issue: Resolving the Conflict Notification===
Current scenario: The function 'significant_difference?' in the model response.rb takes on the average scores of all the existing reviews (by looping through each review to calculate the average) and compares it with the score of the recent response. If the difference is greater than the limit specified(notification_limit), it triggers an email to the instructor with the new response’s (conflicting response) URL.

Proposed changes: Instead of taking on the average scores for existing reviews, we will loop through each review not for calculating the average but to compare the new review score with each review score (a new function will be called to compare with existing responses once a new review is in system i.e. ‘questionnaire’ variable). If for any response the notification_limit is exceeded, the review URL of that iteration will be stored and at the end of the function once all the reviews are looped an email will be triggered comprising of the new review and stored reviews URLs.

Implemented solution:

Files changed:
1. response_controller.rb

[[File:controller.JPG|200x250px|frame|center]]

2. response.rb

[[File:model.JPG|200x250px|frame|center]]

== '''Test Plan''' ==

1) Login.

2) Click on ‘Assignments’ tab.

3) Click on the assignment which has to be reviewed.

4) Navigate to ‘Other’s Work’ section to open the reviews summary.

5) Select a team’s assignment and review it.

6) Give a review score (make one user to give all 0’s and other reviewer to give all 5’s for the same assignment) which in turn exceeds the threshold and submit.

7) Logout and check whether the instructor received an email for conflicting reviews.

== '''References''' ==

Expertiza
* https://expertiza.ncsu.edu/

Expertiza Github
* https://github.com/expertiza/expertiza

Expertiza Documentation
* http://wiki.expertiza.ncsu.edu/index.php/Expertiza_documentation

CSC/ECE 517 Fall 2018- Project E1865. Conflict Notification

2018-12-08T01:46:20Z

Pddalwad:

== '''Introduction''' ==

This project aims to enhance the review mapping of the two conflicting reviews which causes an email to be sent to the instructor when there is a considerable disparity in the grading between two reviews. The goal is to help the instructors by making the process of grading reviews easier and more accurate.

== '''Problem Statement''' ==

===Issue===

Currently, when a new review is submitted and the difference between the score of the new review and (average of the) scores of all previous reviews differ by more than a set threshold, an email is triggered to notify the instructor for such disparity. The email consists of an URL only for the new review.

== '''Application Flow''' ==

[[File:studentflow.png|100x100]]

[[File:image_flow_2.jpeg|frame|center]]

== '''UML DIAGRAM''' ==

[[File:uml.gif|frame|center]]

== '''Proposed Solutions''' ==

===Issue: Resolving the Conflict Notification===
Current scenario: The function 'significant_difference?' in the model response.rb takes on the average scores of all the existing reviews (by looping through each review to calculate the average) and compares it with the score of the recent response. If the difference is greater than the limit specified(notification_limit), it triggers an email to the instructor with the new response’s (conflicting response) URL.

Proposed changes: Instead of taking on the average scores for existing reviews, we will loop through each review not for calculating the average but to compare the new review score with each review score (a new function will be called to compare with existing responses once a new review is in system i.e. ‘questionnaire’ variable). If for any response the notification_limit is exceeded, the review URL of that iteration will be stored and at the end of the function once all the reviews are looped an email will be triggered comprising of the new review and stored reviews URLs.

Implemented solution:

Files changed:
1. response_controller.rb

[[File:controller.JPG|200x250px|frame|center]]

2. response.rb

[[File:model.JPG|200x250px|frame|center]]

== '''Test Plan''' ==

1) Login.

2) Click on ‘Assignments’ tab.

3) Click on the assignment which has to be reviewed.

4) Navigate to ‘Other’s Work’ section to open the reviews summary.

5) Select a team’s assignment and review it.

6) Give a review score (make one user to give all 0’s and other reviewer to give all 5’s for the same assignment) which in turn exceeds the threshold and submit.

7) Logout and check whether the instructor received an email for conflicting reviews.

== '''References''' ==

Expertiza
* https://expertiza.ncsu.edu/

Expertiza Github
* https://github.com/expertiza/expertiza

Expertiza Documentation
* http://wiki.expertiza.ncsu.edu/index.php/Expertiza_documentation

CSC/ECE 517 Fall 2018- Project E1865. Conflict Notification

2018-12-08T01:46:10Z

Pddalwad:

== '''Introduction''' ==

This project aims to enhance the review mapping of the two conflicting reviews which causes an email to be sent to the instructor when there is a considerable disparity in the grading between two reviews. The goal is to help the instructors by making the process of grading reviews easier and more accurate.

== '''Problem Statement''' ==

===Issue===

Currently, when a new review is submitted and the difference between the score of the new review and (average of the) scores of all previous reviews differ by more than a set threshold, an email is triggered to notify the instructor for such disparity. The email consists of an URL only for the new review.

== '''Application Flow''' ==

[[File:studentflow.png|100x150]]

[[File:image_flow_2.jpeg|frame|center]]

== '''UML DIAGRAM''' ==

[[File:uml.gif|frame|center]]

== '''Proposed Solutions''' ==

===Issue: Resolving the Conflict Notification===
Current scenario: The function 'significant_difference?' in the model response.rb takes on the average scores of all the existing reviews (by looping through each review to calculate the average) and compares it with the score of the recent response. If the difference is greater than the limit specified(notification_limit), it triggers an email to the instructor with the new response’s (conflicting response) URL.

Proposed changes: Instead of taking on the average scores for existing reviews, we will loop through each review not for calculating the average but to compare the new review score with each review score (a new function will be called to compare with existing responses once a new review is in system i.e. ‘questionnaire’ variable). If for any response the notification_limit is exceeded, the review URL of that iteration will be stored and at the end of the function once all the reviews are looped an email will be triggered comprising of the new review and stored reviews URLs.

Implemented solution:

Files changed:
1. response_controller.rb

[[File:controller.JPG|200x250px|frame|center]]

2. response.rb

[[File:model.JPG|200x250px|frame|center]]

== '''Test Plan''' ==

1) Login.

2) Click on ‘Assignments’ tab.

3) Click on the assignment which has to be reviewed.

4) Navigate to ‘Other’s Work’ section to open the reviews summary.

5) Select a team’s assignment and review it.

6) Give a review score (make one user to give all 0’s and other reviewer to give all 5’s for the same assignment) which in turn exceeds the threshold and submit.

7) Logout and check whether the instructor received an email for conflicting reviews.

== '''References''' ==

Expertiza
* https://expertiza.ncsu.edu/

Expertiza Github
* https://github.com/expertiza/expertiza

Expertiza Documentation
* http://wiki.expertiza.ncsu.edu/index.php/Expertiza_documentation

CSC/ECE 517 Fall 2018- Project E1865. Conflict Notification

2018-12-08T01:45:20Z

Pddalwad:

== '''Introduction''' ==

This project aims to enhance the review mapping of the two conflicting reviews which causes an email to be sent to the instructor when there is a considerable disparity in the grading between two reviews. The goal is to help the instructors by making the process of grading reviews easier and more accurate.

== '''Problem Statement''' ==

===Issue===

Currently, when a new review is submitted and the difference between the score of the new review and (average of the) scores of all previous reviews differ by more than a set threshold, an email is triggered to notify the instructor for such disparity. The email consists of an URL only for the new review.

== '''Application Flow''' ==

[[File:studentflow.png|100x150px]]

[[File:image_flow_2.jpeg|frame|center]]

== '''UML DIAGRAM''' ==

[[File:uml.gif|frame|center]]

== '''Proposed Solutions''' ==

===Issue: Resolving the Conflict Notification===
Current scenario: The function 'significant_difference?' in the model response.rb takes on the average scores of all the existing reviews (by looping through each review to calculate the average) and compares it with the score of the recent response. If the difference is greater than the limit specified(notification_limit), it triggers an email to the instructor with the new response’s (conflicting response) URL.

Proposed changes: Instead of taking on the average scores for existing reviews, we will loop through each review not for calculating the average but to compare the new review score with each review score (a new function will be called to compare with existing responses once a new review is in system i.e. ‘questionnaire’ variable). If for any response the notification_limit is exceeded, the review URL of that iteration will be stored and at the end of the function once all the reviews are looped an email will be triggered comprising of the new review and stored reviews URLs.

Implemented solution:

Files changed:
1. response_controller.rb

[[File:controller.JPG|200x250px|frame|center]]

2. response.rb

[[File:model.JPG|200x250px|frame|center]]

== '''Test Plan''' ==

1) Login.

2) Click on ‘Assignments’ tab.

3) Click on the assignment which has to be reviewed.

4) Navigate to ‘Other’s Work’ section to open the reviews summary.

5) Select a team’s assignment and review it.

6) Give a review score (make one user to give all 0’s and other reviewer to give all 5’s for the same assignment) which in turn exceeds the threshold and submit.

7) Logout and check whether the instructor received an email for conflicting reviews.

== '''References''' ==

Expertiza
* https://expertiza.ncsu.edu/

Expertiza Github
* https://github.com/expertiza/expertiza

Expertiza Documentation
* http://wiki.expertiza.ncsu.edu/index.php/Expertiza_documentation

CSC/ECE 517 Fall 2018- Project E1865. Conflict Notification

2018-12-08T01:44:50Z

Pddalwad:

== '''Introduction''' ==

This project aims to enhance the review mapping of the two conflicting reviews which causes an email to be sent to the instructor when there is a considerable disparity in the grading between two reviews. The goal is to help the instructors by making the process of grading reviews easier and more accurate.

== '''Problem Statement''' ==

===Issue===

Currently, when a new review is submitted and the difference between the score of the new review and (average of the) scores of all previous reviews differ by more than a set threshold, an email is triggered to notify the instructor for such disparity. The email consists of an URL only for the new review.

== '''Application Flow''' ==

[[File:studentflow.png|400x500px]]

[[File:image_flow_2.jpeg|frame|center]]

== '''UML DIAGRAM''' ==

[[File:uml.gif|frame|center]]

== '''Proposed Solutions''' ==

===Issue: Resolving the Conflict Notification===
Current scenario: The function 'significant_difference?' in the model response.rb takes on the average scores of all the existing reviews (by looping through each review to calculate the average) and compares it with the score of the recent response. If the difference is greater than the limit specified(notification_limit), it triggers an email to the instructor with the new response’s (conflicting response) URL.

Proposed changes: Instead of taking on the average scores for existing reviews, we will loop through each review not for calculating the average but to compare the new review score with each review score (a new function will be called to compare with existing responses once a new review is in system i.e. ‘questionnaire’ variable). If for any response the notification_limit is exceeded, the review URL of that iteration will be stored and at the end of the function once all the reviews are looped an email will be triggered comprising of the new review and stored reviews URLs.

Implemented solution:

Files changed:
1. response_controller.rb

[[File:controller.JPG|200x250px|frame|center]]

2. response.rb

[[File:model.JPG|200x250px|frame|center]]

== '''Test Plan''' ==

1) Login.

2) Click on ‘Assignments’ tab.

3) Click on the assignment which has to be reviewed.

4) Navigate to ‘Other’s Work’ section to open the reviews summary.

5) Select a team’s assignment and review it.

6) Give a review score (make one user to give all 0’s and other reviewer to give all 5’s for the same assignment) which in turn exceeds the threshold and submit.

7) Logout and check whether the instructor received an email for conflicting reviews.

== '''References''' ==

Expertiza
* https://expertiza.ncsu.edu/

Expertiza Github
* https://github.com/expertiza/expertiza

Expertiza Documentation
* http://wiki.expertiza.ncsu.edu/index.php/Expertiza_documentation

CSC/ECE 517 Fall 2018- Project E1865. Conflict Notification

2018-12-08T01:44:38Z

Pddalwad:

== '''Introduction''' ==

This project aims to enhance the review mapping of the two conflicting reviews which causes an email to be sent to the instructor when there is a considerable disparity in the grading between two reviews. The goal is to help the instructors by making the process of grading reviews easier and more accurate.

== '''Problem Statement''' ==

===Issue===

Currently, when a new review is submitted and the difference between the score of the new review and (average of the) scores of all previous reviews differ by more than a set threshold, an email is triggered to notify the instructor for such disparity. The email consists of an URL only for the new review.

== '''Application Flow''' ==

[[File:studentflow.png|200x200px]]

[[File:image_flow_2.jpeg|frame|center]]

== '''UML DIAGRAM''' ==

[[File:uml.gif|frame|center]]

== '''Proposed Solutions''' ==

===Issue: Resolving the Conflict Notification===
Current scenario: The function 'significant_difference?' in the model response.rb takes on the average scores of all the existing reviews (by looping through each review to calculate the average) and compares it with the score of the recent response. If the difference is greater than the limit specified(notification_limit), it triggers an email to the instructor with the new response’s (conflicting response) URL.

Proposed changes: Instead of taking on the average scores for existing reviews, we will loop through each review not for calculating the average but to compare the new review score with each review score (a new function will be called to compare with existing responses once a new review is in system i.e. ‘questionnaire’ variable). If for any response the notification_limit is exceeded, the review URL of that iteration will be stored and at the end of the function once all the reviews are looped an email will be triggered comprising of the new review and stored reviews URLs.

Implemented solution:

Files changed:
1. response_controller.rb

[[File:controller.JPG|200x250px|frame|center]]

2. response.rb

[[File:model.JPG|200x250px|frame|center]]

== '''Test Plan''' ==

1) Login.

2) Click on ‘Assignments’ tab.

3) Click on the assignment which has to be reviewed.

4) Navigate to ‘Other’s Work’ section to open the reviews summary.

5) Select a team’s assignment and review it.

6) Give a review score (make one user to give all 0’s and other reviewer to give all 5’s for the same assignment) which in turn exceeds the threshold and submit.

7) Logout and check whether the instructor received an email for conflicting reviews.

== '''References''' ==

Expertiza
* https://expertiza.ncsu.edu/

Expertiza Github
* https://github.com/expertiza/expertiza

Expertiza Documentation
* http://wiki.expertiza.ncsu.edu/index.php/Expertiza_documentation

CSC/ECE 517 Fall 2018- Project E1865. Conflict Notification

2018-12-08T01:44:24Z

Pddalwad:

== '''Introduction''' ==

This project aims to enhance the review mapping of the two conflicting reviews which causes an email to be sent to the instructor when there is a considerable disparity in the grading between two reviews. The goal is to help the instructors by making the process of grading reviews easier and more accurate.

== '''Problem Statement''' ==

===Issue===

Currently, when a new review is submitted and the difference between the score of the new review and (average of the) scores of all previous reviews differ by more than a set threshold, an email is triggered to notify the instructor for such disparity. The email consists of an URL only for the new review.

== '''Application Flow''' ==

[[File:studentflow.png|100x100px]]

[[File:image_flow_2.jpeg|frame|center]]

== '''UML DIAGRAM''' ==

[[File:uml.gif|frame|center]]

== '''Proposed Solutions''' ==

===Issue: Resolving the Conflict Notification===
Current scenario: The function 'significant_difference?' in the model response.rb takes on the average scores of all the existing reviews (by looping through each review to calculate the average) and compares it with the score of the recent response. If the difference is greater than the limit specified(notification_limit), it triggers an email to the instructor with the new response’s (conflicting response) URL.

Proposed changes: Instead of taking on the average scores for existing reviews, we will loop through each review not for calculating the average but to compare the new review score with each review score (a new function will be called to compare with existing responses once a new review is in system i.e. ‘questionnaire’ variable). If for any response the notification_limit is exceeded, the review URL of that iteration will be stored and at the end of the function once all the reviews are looped an email will be triggered comprising of the new review and stored reviews URLs.

Implemented solution:

Files changed:
1. response_controller.rb

[[File:controller.JPG|200x250px|frame|center]]

2. response.rb

[[File:model.JPG|200x250px|frame|center]]

== '''Test Plan''' ==

1) Login.

2) Click on ‘Assignments’ tab.

3) Click on the assignment which has to be reviewed.

4) Navigate to ‘Other’s Work’ section to open the reviews summary.

5) Select a team’s assignment and review it.

6) Give a review score (make one user to give all 0’s and other reviewer to give all 5’s for the same assignment) which in turn exceeds the threshold and submit.

7) Logout and check whether the instructor received an email for conflicting reviews.

== '''References''' ==

Expertiza
* https://expertiza.ncsu.edu/

Expertiza Github
* https://github.com/expertiza/expertiza

Expertiza Documentation
* http://wiki.expertiza.ncsu.edu/index.php/Expertiza_documentation

CSC/ECE 517 Fall 2018- Project E1865. Conflict Notification

2018-12-08T01:44:22Z

Pddalwad:

== '''Introduction''' ==

This project aims to enhance the review mapping of the two conflicting reviews which causes an email to be sent to the instructor when there is a considerable disparity in the grading between two reviews. The goal is to help the instructors by making the process of grading reviews easier and more accurate.

== '''Problem Statement''' ==

===Issue===

Currently, when a new review is submitted and the difference between the score of the new review and (average of the) scores of all previous reviews differ by more than a set threshold, an email is triggered to notify the instructor for such disparity. The email consists of an URL only for the new review.

== '''Application Flow''' ==

[[File:image_flow_1.jpeg|frame|center]]

[[File:image_flow_2.jpeg|frame|center]]

== '''UML DIAGRAM''' ==

[[File:uml.gif|frame|center]]

== '''Proposed Solutions''' ==

===Issue: Resolving the Conflict Notification===
Current scenario: The function 'significant_difference?' in the model response.rb takes on the average scores of all the existing reviews (by looping through each review to calculate the average) and compares it with the score of the recent response. If the difference is greater than the limit specified(notification_limit), it triggers an email to the instructor with the new response’s (conflicting response) URL.

Proposed changes: Instead of taking on the average scores for existing reviews, we will loop through each review not for calculating the average but to compare the new review score with each review score (a new function will be called to compare with existing responses once a new review is in system i.e. ‘questionnaire’ variable). If for any response the notification_limit is exceeded, the review URL of that iteration will be stored and at the end of the function once all the reviews are looped an email will be triggered comprising of the new review and stored reviews URLs.

Implemented solution:

Files created/changed:
1. response_controller.rb

Added a function "conflict_view" which returns all the IDs of the conflicting reviews.

[[File:controller.JPG|frame|center]]

2. response.rb

Added a function "scores_and_count_for_prev_reviews" which checks the difference between the score of the new review and the score of each of the previous reviews and returns the response IDs of all the reviews whose difference is greater than a set threshold to an function named "significant difference?" which in turn triggers an email to notify the instructor.

[[File:model.JPG|frame|center]]

3. conflict_view.html.erb

Created a new view to display the new review and all the previous conflicting reviews to the instructor.

[[File:view.JPG|frame|center]]

4. routes.rb

Added a route for a newly created "conflict_view" page.

[[File:route.JPG|frame|center]]

== '''Test Plan''' ==

1) Login.

2) Click on ‘Assignments’ tab.

3) Click on the assignment which has to be reviewed.

4) Navigate to ‘Other’s Work’ section to open the reviews summary.

5) Select a team’s assignment and review it.

6) Give a review score (make one user to give all 0’s and other reviewer to give all 5’s for the same assignment) which in turn exceeds the threshold and submit.

7) Logout and check whether the instructor received an email for conflicting reviews.

== '''References''' ==

Expertiza
* https://expertiza.ncsu.edu/

Expertiza Github
* https://github.com/expertiza/expertiza

Expertiza Documentation
* http://wiki.expertiza.ncsu.edu/index.php/Expertiza_documentation

CSC/ECE 517 Fall 2018- Project E1865. Conflict Notification

2018-12-08T01:43:43Z

Pddalwad:

== '''Introduction''' ==

This project aims to enhance the review mapping of the two conflicting reviews which causes an email to be sent to the instructor when there is a considerable disparity in the grading between two reviews. The goal is to help the instructors by making the process of grading reviews easier and more accurate.

== '''Problem Statement''' ==

===Issue===

Currently, when a new review is submitted and the difference between the score of the new review and (average of the) scores of all previous reviews differ by more than a set threshold, an email is triggered to notify the instructor for such disparity. The email consists of an URL only for the new review.

== '''Application Flow''' ==

[[File:studentflow.png|"upright=0.5"]]

[[File:image_flow_2.jpeg|frame|center]]

== '''UML DIAGRAM''' ==

[[File:uml.gif|frame|center]]

== '''Proposed Solutions''' ==

===Issue: Resolving the Conflict Notification===
Current scenario: The function 'significant_difference?' in the model response.rb takes on the average scores of all the existing reviews (by looping through each review to calculate the average) and compares it with the score of the recent response. If the difference is greater than the limit specified(notification_limit), it triggers an email to the instructor with the new response’s (conflicting response) URL.

Proposed changes: Instead of taking on the average scores for existing reviews, we will loop through each review not for calculating the average but to compare the new review score with each review score (a new function will be called to compare with existing responses once a new review is in system i.e. ‘questionnaire’ variable). If for any response the notification_limit is exceeded, the review URL of that iteration will be stored and at the end of the function once all the reviews are looped an email will be triggered comprising of the new review and stored reviews URLs.

Implemented solution:

Files changed:
1. response_controller.rb

[[File:controller.JPG|200x250px|frame|center]]

2. response.rb

[[File:model.JPG|200x250px|frame|center]]

== '''Test Plan''' ==

1) Login.

2) Click on ‘Assignments’ tab.

3) Click on the assignment which has to be reviewed.

4) Navigate to ‘Other’s Work’ section to open the reviews summary.

5) Select a team’s assignment and review it.

6) Give a review score (make one user to give all 0’s and other reviewer to give all 5’s for the same assignment) which in turn exceeds the threshold and submit.

7) Logout and check whether the instructor received an email for conflicting reviews.

== '''References''' ==

Expertiza
* https://expertiza.ncsu.edu/

Expertiza Github
* https://github.com/expertiza/expertiza

Expertiza Documentation
* http://wiki.expertiza.ncsu.edu/index.php/Expertiza_documentation

CSC/ECE 517 Fall 2018- Project E1865. Conflict Notification

2018-12-08T01:43:06Z

Pddalwad:

== '''Introduction''' ==

This project aims to enhance the review mapping of the two conflicting reviews which causes an email to be sent to the instructor when there is a considerable disparity in the grading between two reviews. The goal is to help the instructors by making the process of grading reviews easier and more accurate.

== '''Problem Statement''' ==

===Issue===

Currently, when a new review is submitted and the difference between the score of the new review and (average of the) scores of all previous reviews differ by more than a set threshold, an email is triggered to notify the instructor for such disparity. The email consists of an URL only for the new review.

== '''Application Flow''' ==

[[File:studentflow.png|upright=0.5]]

[[File:image_flow_2.jpeg|frame|center]]

== '''UML DIAGRAM''' ==

[[File:uml.gif|frame|center]]

== '''Proposed Solutions''' ==

===Issue: Resolving the Conflict Notification===
Current scenario: The function 'significant_difference?' in the model response.rb takes on the average scores of all the existing reviews (by looping through each review to calculate the average) and compares it with the score of the recent response. If the difference is greater than the limit specified(notification_limit), it triggers an email to the instructor with the new response’s (conflicting response) URL.

Proposed changes: Instead of taking on the average scores for existing reviews, we will loop through each review not for calculating the average but to compare the new review score with each review score (a new function will be called to compare with existing responses once a new review is in system i.e. ‘questionnaire’ variable). If for any response the notification_limit is exceeded, the review URL of that iteration will be stored and at the end of the function once all the reviews are looped an email will be triggered comprising of the new review and stored reviews URLs.

Implemented solution:

Files changed:
1. response_controller.rb

[[File:controller.JPG|200x250px|frame|center]]

2. response.rb

[[File:model.JPG|200x250px|frame|center]]

== '''Test Plan''' ==

1) Login.

2) Click on ‘Assignments’ tab.

3) Click on the assignment which has to be reviewed.

4) Navigate to ‘Other’s Work’ section to open the reviews summary.

5) Select a team’s assignment and review it.

6) Give a review score (make one user to give all 0’s and other reviewer to give all 5’s for the same assignment) which in turn exceeds the threshold and submit.

7) Logout and check whether the instructor received an email for conflicting reviews.

== '''References''' ==

Expertiza
* https://expertiza.ncsu.edu/

Expertiza Github
* https://github.com/expertiza/expertiza

Expertiza Documentation
* http://wiki.expertiza.ncsu.edu/index.php/Expertiza_documentation

CSC/ECE 517 Fall 2018- Project E1865. Conflict Notification

2018-12-08T01:41:14Z

Pddalwad:

== '''Introduction''' ==

This project aims to enhance the review mapping of the two conflicting reviews which causes an email to be sent to the instructor when there is a considerable disparity in the grading between two reviews. The goal is to help the instructors by making the process of grading reviews easier and more accurate.

== '''Problem Statement''' ==

===Issue===

Currently, when a new review is submitted and the difference between the score of the new review and (average of the) scores of all previous reviews differ by more than a set threshold, an email is triggered to notify the instructor for such disparity. The email consists of an URL only for the new review.

== '''Application Flow''' ==

[[File:studentflow.png]]

[[File:image_flow_2.jpeg|frame|center]]

== '''UML DIAGRAM''' ==

[[File:uml.gif|frame|center]]

== '''Proposed Solutions''' ==

===Issue: Resolving the Conflict Notification===
Current scenario: The function 'significant_difference?' in the model response.rb takes on the average scores of all the existing reviews (by looping through each review to calculate the average) and compares it with the score of the recent response. If the difference is greater than the limit specified(notification_limit), it triggers an email to the instructor with the new response’s (conflicting response) URL.

Proposed changes: Instead of taking on the average scores for existing reviews, we will loop through each review not for calculating the average but to compare the new review score with each review score (a new function will be called to compare with existing responses once a new review is in system i.e. ‘questionnaire’ variable). If for any response the notification_limit is exceeded, the review URL of that iteration will be stored and at the end of the function once all the reviews are looped an email will be triggered comprising of the new review and stored reviews URLs.

Implemented solution:

Files changed:
1. response_controller.rb

[[File:controller.JPG|200x250px|frame|center]]

2. response.rb

[[File:model.JPG|200x250px|frame|center]]

== '''Test Plan''' ==

1) Login.

2) Click on ‘Assignments’ tab.

3) Click on the assignment which has to be reviewed.

4) Navigate to ‘Other’s Work’ section to open the reviews summary.

5) Select a team’s assignment and review it.

6) Give a review score (make one user to give all 0’s and other reviewer to give all 5’s for the same assignment) which in turn exceeds the threshold and submit.

7) Logout and check whether the instructor received an email for conflicting reviews.

== '''References''' ==

Expertiza
* https://expertiza.ncsu.edu/

Expertiza Github
* https://github.com/expertiza/expertiza

Expertiza Documentation
* http://wiki.expertiza.ncsu.edu/index.php/Expertiza_documentation

CSC/ECE 517 Fall 2018- Project E1865. Conflict Notification

2018-12-08T01:40:59Z

Pddalwad:

== '''Introduction''' ==

This project aims to enhance the review mapping of the two conflicting reviews which causes an email to be sent to the instructor when there is a considerable disparity in the grading between two reviews. The goal is to help the instructors by making the process of grading reviews easier and more accurate.

== '''Problem Statement''' ==

===Issue===

Currently, when a new review is submitted and the difference between the score of the new review and (average of the) scores of all previous reviews differ by more than a set threshold, an email is triggered to notify the instructor for such disparity. The email consists of an URL only for the new review.

== '''Application Flow''' ==

[[File:studentflow.png|center]]

[[File:image_flow_2.jpeg|frame|center]]

== '''UML DIAGRAM''' ==

[[File:uml.gif|frame|center]]

== '''Proposed Solutions''' ==

===Issue: Resolving the Conflict Notification===
Current scenario: The function 'significant_difference?' in the model response.rb takes on the average scores of all the existing reviews (by looping through each review to calculate the average) and compares it with the score of the recent response. If the difference is greater than the limit specified(notification_limit), it triggers an email to the instructor with the new response’s (conflicting response) URL.

Proposed changes: Instead of taking on the average scores for existing reviews, we will loop through each review not for calculating the average but to compare the new review score with each review score (a new function will be called to compare with existing responses once a new review is in system i.e. ‘questionnaire’ variable). If for any response the notification_limit is exceeded, the review URL of that iteration will be stored and at the end of the function once all the reviews are looped an email will be triggered comprising of the new review and stored reviews URLs.

Implemented solution:

Files changed:
1. response_controller.rb

[[File:controller.JPG|200x250px|frame|center]]

2. response.rb

[[File:model.JPG|200x250px|frame|center]]

== '''Test Plan''' ==

1) Login.

2) Click on ‘Assignments’ tab.

3) Click on the assignment which has to be reviewed.

4) Navigate to ‘Other’s Work’ section to open the reviews summary.

5) Select a team’s assignment and review it.

6) Give a review score (make one user to give all 0’s and other reviewer to give all 5’s for the same assignment) which in turn exceeds the threshold and submit.

7) Logout and check whether the instructor received an email for conflicting reviews.

== '''References''' ==

Expertiza
* https://expertiza.ncsu.edu/

Expertiza Github
* https://github.com/expertiza/expertiza

Expertiza Documentation
* http://wiki.expertiza.ncsu.edu/index.php/Expertiza_documentation

File:Studentflow.png

2018-12-08T01:39:55Z

Pddalwad:

CSC/ECE 517 Fall 2018- Project E1865. Conflict Notification

2018-12-08T01:39:43Z

Pddalwad:

== '''Introduction''' ==

This project aims to enhance the review mapping of the two conflicting reviews which causes an email to be sent to the instructor when there is a considerable disparity in the grading between two reviews. The goal is to help the instructors by making the process of grading reviews easier and more accurate.

== '''Problem Statement''' ==

===Issue===

Currently, when a new review is submitted and the difference between the score of the new review and (average of the) scores of all previous reviews differ by more than a set threshold, an email is triggered to notify the instructor for such disparity. The email consists of an URL only for the new review.

== '''Application Flow''' ==

[[File:studentflow.png|frame|center]]

[[File:image_flow_2.jpeg|frame|center]]

== '''UML DIAGRAM''' ==

[[File:uml.gif|frame|center]]

== '''Proposed Solutions''' ==

===Issue: Resolving the Conflict Notification===
Current scenario: The function 'significant_difference?' in the model response.rb takes on the average scores of all the existing reviews (by looping through each review to calculate the average) and compares it with the score of the recent response. If the difference is greater than the limit specified(notification_limit), it triggers an email to the instructor with the new response’s (conflicting response) URL.

Proposed changes: Instead of taking on the average scores for existing reviews, we will loop through each review not for calculating the average but to compare the new review score with each review score (a new function will be called to compare with existing responses once a new review is in system i.e. ‘questionnaire’ variable). If for any response the notification_limit is exceeded, the review URL of that iteration will be stored and at the end of the function once all the reviews are looped an email will be triggered comprising of the new review and stored reviews URLs.

Implemented solution:

Files changed:
1. response_controller.rb

[[File:controller.JPG|200x250px|frame|center]]

2. response.rb

[[File:model.JPG|200x250px|frame|center]]

== '''Test Plan''' ==

1) Login.

2) Click on ‘Assignments’ tab.

3) Click on the assignment which has to be reviewed.

4) Navigate to ‘Other’s Work’ section to open the reviews summary.

5) Select a team’s assignment and review it.

6) Give a review score (make one user to give all 0’s and other reviewer to give all 5’s for the same assignment) which in turn exceeds the threshold and submit.

7) Logout and check whether the instructor received an email for conflicting reviews.

== '''References''' ==

Expertiza
* https://expertiza.ncsu.edu/

Expertiza Github
* https://github.com/expertiza/expertiza

Expertiza Documentation
* http://wiki.expertiza.ncsu.edu/index.php/Expertiza_documentation

CSC/ECE 517 Fall 2018- Project E1865. Conflict Notification

2018-12-08T01:39:05Z

Pddalwad:

== '''Introduction''' ==

This project aims to enhance the review mapping of the two conflicting reviews which causes an email to be sent to the instructor when there is a considerable disparity in the grading between two reviews. The goal is to help the instructors by making the process of grading reviews easier and more accurate.

== '''Problem Statement''' ==

===Issue===

Currently, when a new review is submitted and the difference between the score of the new review and (average of the) scores of all previous reviews differ by more than a set threshold, an email is triggered to notify the instructor for such disparity. The email consists of an URL only for the new review.

== '''Application Flow''' ==

[[File:student.png|frame|center]]

[[File:image_flow_2.jpeg|frame|center]]

== '''UML DIAGRAM''' ==

[[File:uml.gif|frame|center]]

== '''Proposed Solutions''' ==

===Issue: Resolving the Conflict Notification===
Current scenario: The function 'significant_difference?' in the model response.rb takes on the average scores of all the existing reviews (by looping through each review to calculate the average) and compares it with the score of the recent response. If the difference is greater than the limit specified(notification_limit), it triggers an email to the instructor with the new response’s (conflicting response) URL.

Proposed changes: Instead of taking on the average scores for existing reviews, we will loop through each review not for calculating the average but to compare the new review score with each review score (a new function will be called to compare with existing responses once a new review is in system i.e. ‘questionnaire’ variable). If for any response the notification_limit is exceeded, the review URL of that iteration will be stored and at the end of the function once all the reviews are looped an email will be triggered comprising of the new review and stored reviews URLs.

Implemented solution:

Files changed:
1. response_controller.rb

[[File:controller.JPG|200x250px|frame|center]]

2. response.rb

[[File:model.JPG|200x250px|frame|center]]

== '''Test Plan''' ==

1) Login.

2) Click on ‘Assignments’ tab.

3) Click on the assignment which has to be reviewed.

4) Navigate to ‘Other’s Work’ section to open the reviews summary.

5) Select a team’s assignment and review it.

6) Give a review score (make one user to give all 0’s and other reviewer to give all 5’s for the same assignment) which in turn exceeds the threshold and submit.

7) Logout and check whether the instructor received an email for conflicting reviews.

== '''References''' ==

Expertiza
* https://expertiza.ncsu.edu/

Expertiza Github
* https://github.com/expertiza/expertiza

Expertiza Documentation
* http://wiki.expertiza.ncsu.edu/index.php/Expertiza_documentation

CSC/ECE 517 Fall 2018- Project E1865. Conflict Notification

2018-12-08T01:23:20Z

Pddalwad:

== '''Introduction''' ==

This project aims to enhance the review mapping of the two conflicting reviews which causes an email to be sent to the instructor when there is a considerable disparity in the grading between two reviews. The goal is to help the instructors by making the process of grading reviews easier and more accurate.

== '''Problem Statement''' ==

===Issue===

Currently, when a new review is submitted and the difference between the score of the new review and (average of the) scores of all previous reviews differ by more than a set threshold, an email is triggered to notify the instructor for such disparity. The email consists of an URL only for the new review.

== '''Application Flow''' ==

[[File:image_flow_1.jpeg|frame|center]]

[[File:image_flow_2.jpeg|frame|center]]

== '''UML DIAGRAM''' ==

[[File:uml.gif|frame|center]]

== '''Proposed Solutions''' ==

===Issue: Resolving the Conflict Notification===
Current scenario: The function 'significant_difference?' in the model response.rb takes on the average scores of all the existing reviews (by looping through each review to calculate the average) and compares it with the score of the recent response. If the difference is greater than the limit specified(notification_limit), it triggers an email to the instructor with the new response’s (conflicting response) URL.

Proposed changes: Instead of taking on the average scores for existing reviews, we will loop through each review not for calculating the average but to compare the new review score with each review score (a new function will be called to compare with existing responses once a new review is in system i.e. ‘questionnaire’ variable). If for any response the notification_limit is exceeded, the review URL of that iteration will be stored and at the end of the function once all the reviews are looped an email will be triggered comprising of the new review and stored reviews URLs.

Implemented solution:

Files changed:
1. response_controller.rb

[[File:controller.JPG|200x250px|frame|center]]

2. response.rb

[[File:model.JPG|200x250px|frame|center]]

== '''Test Plan''' ==

1) Login.

2) Click on ‘Assignments’ tab.

3) Click on the assignment which has to be reviewed.

4) Navigate to ‘Other’s Work’ section to open the reviews summary.

5) Select a team’s assignment and review it.

6) Give a review score (make one user to give all 0’s and other reviewer to give all 5’s for the same assignment) which in turn exceeds the threshold and submit.

7) Logout and check whether the instructor received an email for conflicting reviews.

== '''References''' ==

Expertiza
* https://expertiza.ncsu.edu/

Expertiza Github
* https://github.com/expertiza/expertiza

Expertiza Documentation
* http://wiki.expertiza.ncsu.edu/index.php/Expertiza_documentation

CSC/ECE 517 Fall 2018- Project E1865. Conflict Notification

2018-12-08T01:22:43Z

Pddalwad:

== '''Introduction''' ==

This project aims to enhance the review mapping of the two conflicting reviews which causes an email to be sent to the instructor when there is a considerable disparity in the grading between two reviews. The goal is to help the instructors by making the process of grading reviews easier and more accurate.

== '''Problem Statement''' ==

===Issue===

Currently, when a new review is submitted and the difference between the score of the new review and (average of the) scores of all previous reviews differ by more than a set threshold, an email is triggered to notify the instructor for such disparity. The email consists of an URL only for the new review.

== '''Application Flow''' ==

[[File:image_flow_1.jpeg|frame|center]]

[[File:image_flow_2.jpeg|frame|center]]

== '''UML DIAGRAM''' ==

[[File:uml.gif|frame|center]]

== '''Proposed Solutions''' ==

===Issue: Resolving the Conflict Notification===
Current scenario: The function 'significant_difference?' in the model response.rb takes on the average scores of all the existing reviews (by looping through each review to calculate the average) and compares it with the score of the recent response. If the difference is greater than the limit specified(notification_limit), it triggers an email to the instructor with the new response’s (conflicting response) URL.

Proposed changes: Instead of taking on the average scores for existing reviews, we will loop through each review not for calculating the average but to compare the new review score with each review score (a new function will be called to compare with existing responses once a new review is in system i.e. ‘questionnaire’ variable). If for any response the notification_limit is exceeded, the review URL of that iteration will be stored and at the end of the function once all the reviews are looped an email will be triggered comprising of the new review and stored reviews URLs.

Implemented solution:

Files changed:
1. response_controller.rb

[[File:controller.JPG|100x150px|frame|center]]

2. response.rb

[[File:model.JPG|100x150px|frame|center]]

== '''Test Plan''' ==

1) Login.

2) Click on ‘Assignments’ tab.

3) Click on the assignment which has to be reviewed.

4) Navigate to ‘Other’s Work’ section to open the reviews summary.

5) Select a team’s assignment and review it.

6) Give a review score (make one user to give all 0’s and other reviewer to give all 5’s for the same assignment) which in turn exceeds the threshold and submit.

7) Logout and check whether the instructor received an email for conflicting reviews.

== '''References''' ==

Expertiza
* https://expertiza.ncsu.edu/

Expertiza Github
* https://github.com/expertiza/expertiza

Expertiza Documentation
* http://wiki.expertiza.ncsu.edu/index.php/Expertiza_documentation

CSC/ECE 517 Fall 2018- Project E1865. Conflict Notification

2018-12-08T01:18:56Z

Pddalwad:

== '''Introduction''' ==

This project aims to enhance the review mapping of the two conflicting reviews which causes an email to be sent to the instructor when there is a considerable disparity in the grading between two reviews. The goal is to help the instructors by making the process of grading reviews easier and more accurate.

== '''Problem Statement''' ==

===Issue===

Currently, when a new review is submitted and the difference between the score of the new review and (average of the) scores of all previous reviews differ by more than a set threshold, an email is triggered to notify the instructor for such disparity. The email consists of an URL only for the new review.

== '''Application Flow''' ==

[[File:image_flow_1.jpeg|frame|center]]

[[File:image_flow_2.jpeg|frame|center]]

== '''UML DIAGRAM''' ==

[[File:uml.gif|frame|center]]

== '''Proposed Solutions''' ==

===Issue: Resolving the Conflict Notification===
Current scenario: The function 'significant_difference?' in the model response.rb takes on the average scores of all the existing reviews (by looping through each review to calculate the average) and compares it with the score of the recent response. If the difference is greater than the limit specified(notification_limit), it triggers an email to the instructor with the new response’s (conflicting response) URL.

Proposed changes: Instead of taking on the average scores for existing reviews, we will loop through each review not for calculating the average but to compare the new review score with each review score (a new function will be called to compare with existing responses once a new review is in system i.e. ‘questionnaire’ variable). If for any response the notification_limit is exceeded, the review URL of that iteration will be stored and at the end of the function once all the reviews are looped an email will be triggered comprising of the new review and stored reviews URLs.

Implemented solution:

Files changed:
1. response_controller.rb

[[File:controller.JPG|frame|center]]

2. response.rb

[[File:model.JPG|frame|center]]

== '''Test Plan''' ==

1) Login.

2) Click on ‘Assignments’ tab.

3) Click on the assignment which has to be reviewed.

4) Navigate to ‘Other’s Work’ section to open the reviews summary.

5) Select a team’s assignment and review it.

6) Give a review score (make one user to give all 0’s and other reviewer to give all 5’s for the same assignment) which in turn exceeds the threshold and submit.

7) Logout and check whether the instructor received an email for conflicting reviews.

== '''References''' ==

Expertiza
* https://expertiza.ncsu.edu/

Expertiza Github
* https://github.com/expertiza/expertiza

Expertiza Documentation
* http://wiki.expertiza.ncsu.edu/index.php/Expertiza_documentation

File:Model.JPG

2018-12-08T01:18:21Z

Pddalwad:

CSC/ECE 517 Fall 2018- Project E1865. Conflict Notification

2018-12-08T01:17:57Z

Pddalwad:

File:Controller.JPG

2018-12-08T01:15:23Z

Pddalwad: uploaded a new version of "File:Controller.JPG"

CSC/ECE 517 Fall 2018- Project E1865. Conflict Notification

2018-12-08T01:00:15Z

Pddalwad:

CSC/ECE 517 Fall 2018- Project E1865. Conflict Notification

2018-12-07T23:44:51Z

Pddalwad:

File:Uml.gif

2018-12-07T23:44:05Z

Pddalwad:

CSC/ECE 517 Fall 2018- Project E1865. Conflict Notification

2018-12-07T23:43:33Z

Pddalwad:

CSC/ECE 517 Fall 2018- Project E1865. Conflict Notification

2018-11-22T05:18:09Z

Pddalwad: /* Issue: Resolving the Conflict Notification */

CSC/ECE 517 Fall 2018- Project E1865. Conflict Notification

2018-11-22T05:17:56Z

Pddalwad: /* Issue: Resolving the Conflict Notification */

CSC/ECE 517 Fall 2018- Project E1865. Conflict Notification

2018-11-22T05:17:46Z

Pddalwad: /* Issue: Resolving the Conflict Notification */