Expertiza_Wiki - User contributions [en]

CSC/ECE 517 Fall 2020 - E2085. Allow reviewers to bid on what to review

2020-10-22T00:47:11Z

Lgdeloss: /* Objectives */

==Project Overview==
=== ''Background'' ===
Assigning reviews to users is a complicated process. Currently, reviews are still assigned using a first-come-first-served basis. However, reviews could be bid on like how topics are bid on. This would involve matching multiple students to review a submission up to the maximum reviewers for a submission.

=== ''Objectives'' ===
# Implement top trading cycles on a web service.
# Add front end code to allow bidding on topics and call the appropriate web service from the lottery controller.
# Add test cases regarding new changes

=== ''Previous Work'' ===
There have been two previous implementations:
* Fall 2019 [http://wiki.expertiza.ncsu.edu/index.php/CSC/ECE_517_Fall_2019_-_E1986._Allow_reviewers_to_bid_on_what_to_review here]
* Spring 2020 [https://expertiza.csc.ncsu.edu/index.php/CSC/ECE_517_Spring_2020_-_E2021._Allow_reviewers_to_bid_on_what_to_review here]

=== ''Relevant Links'' ===
''Github Repository'': https://github.com/uahamedncsu/expertiza/tree/beta 
''Pull Request'': https://github.com/expertiza/expertiza/pull/1822 
''Video Demo'': [https://expertiza.csc.ncsu.edu/index.php/Main_Page [Not Created]] 

=== ''Files Modified'' ===
Will list all the files we change while implementing our project

 

==Design==
Here we talk about the design plan and include figures and whatever else we need.

=== ''User Interface'' ===

===''Potential Challenges''===

 

==Implementation==
Once we begin working, this section will have all our changes and be categorized by tasks

 
==Test Plan==
This section outlines the test plan for this project including testing scenarios/edge cases, the manual testing plan, and the automatic/RSpec testing plan.

=== ''Basic Test Scenario'' ===
*Reviewers bid on multiple projects at different times
** Bidding algorithm should give priority to reviewers that bid first and should assign based on reviewers ranking

=== ''Edge Cases'' ===
* All reviewers bid on the same project
** If different time stamps: bidding algorithm should give priority to reviewers that bid first
** If same time stamps: bidding algorithm should assign reviews randomly
* None of the reviews bid on any projects
** Bidding algorithm should assign reviews randomly
* Reviewer bids on their own project
** Bidding algorithm should not allow a reviewer to bid on their own project and should have validation to prevent assigning a reviewer their own project
* None of the reviewers bid on a specific project
** Bidding algorithm should still assign reviewers to this project

=== ''Manual Testing Plan'' ===
Manual testing should be preformed on an Expertiza server. 
Manual testing should (''at a minimum''):
* test that the UI is implemented as expected
* test that a participant can bid on projects to review
** test that a participant can move projects into the bidding column
** test that a participant can reorder projects in the bidding column
** test that a participant's bidding preferences save

=== ''RSpec Testing Plan'' ===
RSpec tests will need to be written to related controller(s) and model(s). 
These RSpec tests should (''at a minimum''):
* test basic functionality of controller(s)
* test validation of the model(s)
* test the scenarios (basic case & edge cases) mentioned above

 

==Team==
Yasmin Ahamed Adam (uahamed) 
Ryan Grainger (rpgraing) 
Luis Delossantos (lgdeloss) 
Colleen "Bria" Engen (ceengen) 
'''Mentor:''' Saurabh Shingte (svshingt)

 
==Resources==
''Previous Implementations'': [[http://wiki.expertiza.ncsu.edu/index.php/CSC/ECE_517_Fall_2019_-_E1986._Allow_reviewers_to_bid_on_what_to_review 1]], [[https://expertiza.csc.ncsu.edu/index.php/CSC/ECE_517_Spring_2020_-_E2021._Allow_reviewers_to_bid_on_what_to_review 2]] 
''Bidding Interface Implementation Pull Request'': [[https://github.com/expertiza/expertiza/pull/778 3]]

CSC/ECE 517 Fall 2020 - E2085. Allow reviewers to bid on what to review

2020-10-22T00:44:52Z

Lgdeloss: /* Background */

==Project Overview==
=== ''Background'' ===
Assigning reviews to users is a complicated process. Currently, reviews are still assigned using a first-come-first-served basis. However, reviews could be bid on like how topics are bid on. This would involve matching multiple students to review a submission up to the maximum reviewers for a submission.

=== ''Objectives'' ===
# Implement top trading cycles on a web service.
# Add front end code to allow bidding on topics and call the appropriate web service from the lottery controller.
# Make sure solutions is similar to the bidding process on topics.
# Add test cases regarding new changes

=== ''Previous Work'' ===
There have been two previous implementations:
* Fall 2019 [http://wiki.expertiza.ncsu.edu/index.php/CSC/ECE_517_Fall_2019_-_E1986._Allow_reviewers_to_bid_on_what_to_review here]
* Spring 2020 [https://expertiza.csc.ncsu.edu/index.php/CSC/ECE_517_Spring_2020_-_E2021._Allow_reviewers_to_bid_on_what_to_review here]

=== ''Relevant Links'' ===
''Github Repository'': https://github.com/uahamedncsu/expertiza/tree/beta 
''Pull Request'': https://github.com/expertiza/expertiza/pull/1822 
''Video Demo'': [https://expertiza.csc.ncsu.edu/index.php/Main_Page [Not Created]] 

=== ''Files Modified'' ===
Will list all the files we change while implementing our project

 

==Design==
Here we talk about the design plan and include figures and whatever else we need.

=== ''User Interface'' ===

===''Potential Challenges''===

 

==Implementation==
Once we begin working, this section will have all our changes and be categorized by tasks

 
==Test Plan==
This section outlines the test plan for this project including testing scenarios/edge cases, the manual testing plan, and the automatic/RSpec testing plan.

=== ''Basic Test Scenario'' ===
*Reviewers bid on multiple projects at different times
** Bidding algorithm should give priority to reviewers that bid first and should assign based on reviewers ranking

=== ''Edge Cases'' ===
* All reviewers bid on the same project
** If different time stamps: bidding algorithm should give priority to reviewers that bid first
** If same time stamps: bidding algorithm should assign reviews randomly
* None of the reviews bid on any projects
** Bidding algorithm should assign reviews randomly
* Reviewer bids on their own project
** Bidding algorithm should not allow a reviewer to bid on their own project and should have validation to prevent assigning a reviewer their own project
* None of the reviewers bid on a specific project
** Bidding algorithm should still assign reviewers to this project

=== ''Manual Testing Plan'' ===
Manual testing should be preformed on an Expertiza server. 
Manual testing should (''at a minimum''):
* test that the UI is implemented as expected
* test that a participant can bid on projects to review
** test that a participant can move projects into the bidding column
** test that a participant can reorder projects in the bidding column
** test that a participant's bidding preferences save

=== ''RSpec Testing Plan'' ===
RSpec tests will need to be written to related controller(s) and model(s). 
These RSpec tests should (''at a minimum''):
* test basic functionality of controller(s)
* test validation of the model(s)
* test the scenarios (basic case & edge cases) mentioned above

 

==Team==
Yasmin Ahamed Adam (uahamed) 
Ryan Grainger (rpgraing) 
Luis Delossantos (lgdeloss) 
Colleen "Bria" Engen (ceengen) 
'''Mentor:''' Saurabh Shingte (svshingt)

 
==Resources==
''Previous Implementations'': [[http://wiki.expertiza.ncsu.edu/index.php/CSC/ECE_517_Fall_2019_-_E1986._Allow_reviewers_to_bid_on_what_to_review 1]], [[https://expertiza.csc.ncsu.edu/index.php/CSC/ECE_517_Spring_2020_-_E2021._Allow_reviewers_to_bid_on_what_to_review 2]] 
''Bidding Interface Implementation Pull Request'': [[https://github.com/expertiza/expertiza/pull/778 3]]

CSC/ECE 517 Fall 2020 - E2085. Allow reviewers to bid on what to review

2020-10-22T00:43:05Z

Lgdeloss: /* Objectives */

==Project Overview==
=== ''Background'' ===
Talk about the bidding process and the review process..kind of like an summary of what were doing and why

=== ''Objectives'' ===
# Implement top trading cycles on a web service.
# Add front end code to allow bidding on topics and call the appropriate web service from the lottery controller.
# Make sure solutions is similar to the bidding process on topics.
# Add test cases regarding new changes

=== ''Previous Work'' ===
There have been two previous implementations:
* Fall 2019 [http://wiki.expertiza.ncsu.edu/index.php/CSC/ECE_517_Fall_2019_-_E1986._Allow_reviewers_to_bid_on_what_to_review here]
* Spring 2020 [https://expertiza.csc.ncsu.edu/index.php/CSC/ECE_517_Spring_2020_-_E2021._Allow_reviewers_to_bid_on_what_to_review here]

=== ''Relevant Links'' ===
''Github Repository'': https://github.com/uahamedncsu/expertiza/tree/beta 
''Pull Request'': https://github.com/expertiza/expertiza/pull/1822 
''Video Demo'': [https://expertiza.csc.ncsu.edu/index.php/Main_Page [Not Created]] 

=== ''Files Modified'' ===
Will list all the files we change while implementing our project

 

==Design==
Here we talk about the design plan and include figures and whatever else we need.

=== ''User Interface'' ===

===''Potential Challenges''===

 

==Implementation==
Once we begin working, this section will have all our changes and be categorized by tasks

 
==Test Plan==
This section outlines the test plan for this project including testing scenarios/edge cases, the manual testing plan, and the automatic/RSpec testing plan.

=== ''Basic Test Scenario'' ===
*Reviewers bid on multiple projects at different times
** Bidding algorithm should give priority to reviewers that bid first and should assign based on reviewers ranking

=== ''Edge Cases'' ===
* All reviewers bid on the same project
** If different time stamps: bidding algorithm should give priority to reviewers that bid first
** If same time stamps: bidding algorithm should assign reviews randomly
* None of the reviews bid on any projects
** Bidding algorithm should assign reviews randomly
* Reviewer bids on their own project
** Bidding algorithm should not allow a reviewer to bid on their own project and should have validation to prevent assigning a reviewer their own project
* None of the reviewers bid on a specific project
** Bidding algorithm should still assign reviewers to this project

=== ''Manual Testing Plan'' ===
Manual testing should be preformed on an Expertiza server. 
Manual testing should (''at a minimum''):
* test that the UI is implemented as expected
* test that a participant can bid on projects to review
** test that a participant can move projects into the bidding column
** test that a participant can reorder projects in the bidding column
** test that a participant's bidding preferences save

=== ''RSpec Testing Plan'' ===
RSpec tests will need to be written to related controller(s) and model(s). 
These RSpec tests should (''at a minimum''):
* test basic functionality of controller(s)
* test validation of the model(s)
* test the scenarios (basic case & edge cases) mentioned above

 

==Team==
Yasmin Ahamed Adam (uahamed) 
Ryan Grainger (rpgraing) 
Luis Delossantos (lgdeloss) 
Colleen "Bria" Engen (ceengen) 
'''Mentor:''' Saurabh Shingte (svshingt)

 
==Resources==
''Previous Implementations'': [[http://wiki.expertiza.ncsu.edu/index.php/CSC/ECE_517_Fall_2019_-_E1986._Allow_reviewers_to_bid_on_what_to_review 1]], [[https://expertiza.csc.ncsu.edu/index.php/CSC/ECE_517_Spring_2020_-_E2021._Allow_reviewers_to_bid_on_what_to_review 2]] 
''Bidding Interface Implementation Pull Request'': [[https://github.com/expertiza/expertiza/pull/778 3]]

CSC/ECE 517 Fall 2020 - E2085. Allow reviewers to bid on what to review

2020-10-22T00:25:04Z

Lgdeloss: /* Objectives */

==Project Overview==
=== ''Background'' ===
Talk about the bidding process and the review process..kind of like an summary of what were doing and why

=== ''Objectives'' ===
# Implement top trading cycles on a web service.
# Add front end code to allow bidding on topics and call the appropriate web service from the lottery controller.
# Make sure solutions is similar to the bidding process on topics.

=== ''Previous Work'' ===
There have been two previous implementations:
* Fall 2019 [http://wiki.expertiza.ncsu.edu/index.php/CSC/ECE_517_Fall_2019_-_E1986._Allow_reviewers_to_bid_on_what_to_review here]
* Spring 2020 [https://expertiza.csc.ncsu.edu/index.php/CSC/ECE_517_Spring_2020_-_E2021._Allow_reviewers_to_bid_on_what_to_review here]

=== ''Relevant Links'' ===
''Github Repository'': https://github.com/uahamedncsu/expertiza/tree/beta 
''Pull Request'': https://github.com/expertiza/expertiza/pull/1822 
''Video Demo'': [https://expertiza.csc.ncsu.edu/index.php/Main_Page [Not Created]] 

=== ''Files Modified'' ===
Will list all the files we change while implementing our project

 

==Design==
Here we talk about the design plan and include figures and whatever else we need.

=== ''User Interface'' ===

===''Potential Challenges''===

 

==Implementation==
Once we begin working, this section will have all our changes and be categorized by tasks

 
==Test Plan==
This section outlines the test plan for this project including testing scenarios/edge cases, the manual testing plan, and the automatic/RSpec testing plan.

=== ''Basic Test Scenario'' ===
*Reviewers bid on multiple projects at different times
** Bidding algorithm should give priority to reviewers that bid first and should assign based on reviewers ranking

=== ''Edge Cases'' ===
* All reviewers bid on the same project
** If different time stamps: bidding algorithm should give priority to reviewers that bid first
** If same time stamps: bidding algorithm should assign reviews randomly
* None of the reviews bid on any projects
** Bidding algorithm should assign reviews randomly
* Reviewer bids on their own project
** Bidding algorithm should not allow a reviewer to bid on their own project and should have validation to prevent assigning a reviewer their own project
* None of the reviewers bid on a specific project
** Bidding algorithm should still assign reviewers to this project

=== ''Manual Testing Plan'' ===
Manual testing should be preformed on an Expertiza server. 
Manual testing should (''at a minimum''):
* test that the UI is implemented as expected
* test that a participant can bid on projects to review
** test that a participant can move projects into the bidding column
** test that a participant can reorder projects in the bidding column
** test that a participant's bidding preferences save

=== ''RSpec Testing Plan'' ===
RSpec tests will need to be written to related controller(s) and model(s). 
These RSpec tests should (''at a minimum''):
* test basic functionality of controller(s)
* test validation of the model(s)
* test the scenarios (basic case & edge cases) mentioned above

 

==Team==
Yasmin Ahamed Adam (uahamed) 
Ryan Grainger (rpgraing) 
Luis Delossantos (lgdeloss) 
Colleen "Bria" Engen (ceengen) 
'''Mentor:''' Saurabh Shingte (svshingt)

 
==Resources==
''Previous Implementations'': [[http://wiki.expertiza.ncsu.edu/index.php/CSC/ECE_517_Fall_2019_-_E1986._Allow_reviewers_to_bid_on_what_to_review 1]], [[https://expertiza.csc.ncsu.edu/index.php/CSC/ECE_517_Spring_2020_-_E2021._Allow_reviewers_to_bid_on_what_to_review 2]] 
''Bidding Interface Implementation Pull Request'': [[https://github.com/expertiza/expertiza/pull/778 3]]

CSC/ECE 517 Fall 2020 - E2085. Allow reviewers to bid on what to review

2020-10-22T00:22:01Z

Lgdeloss: /* Objectives */

==Project Overview==
=== ''Background'' ===
Talk about the bidding process and the review process..kind of like an summary of what were doing and why

=== ''Objectives'' ===
1. Implement top trading cycles on a web service.
2. Add front end code to allow bidding on topics and call the appropriate web service from the lottery controller.
3. Make sure solutions is similar to the bidding process on topics.

=== ''Previous Work'' ===
There have been two previous implementations:
* Fall 2019 [http://wiki.expertiza.ncsu.edu/index.php/CSC/ECE_517_Fall_2019_-_E1986._Allow_reviewers_to_bid_on_what_to_review here]
* Spring 2020 [https://expertiza.csc.ncsu.edu/index.php/CSC/ECE_517_Spring_2020_-_E2021._Allow_reviewers_to_bid_on_what_to_review here]

=== ''Relevant Links'' ===
''Github Repository'': https://github.com/uahamedncsu/expertiza/tree/beta 
''Pull Request'': https://github.com/expertiza/expertiza/pull/1822 
''Video Demo'': [https://expertiza.csc.ncsu.edu/index.php/Main_Page [Not Created]] 

=== ''Files Modified'' ===
Will list all the files we change while implementing our project

 

==Design==
Here we talk about the design plan and include figures and whatever else we need.

=== ''User Interface'' ===

===''Potential Challenges''===

 

==Implementation==
Once we begin working, this section will have all our changes and be categorized by tasks

 
==Test Plan==
This section outlines the test plan for this project including testing scenarios/edge cases, the manual testing plan, and the automatic/RSpec testing plan.

=== ''Basic Test Scenario'' ===
*Reviewers bid on multiple projects at different times
** Bidding algorithm should give priority to reviewers that bid first and should assign based on reviewers ranking

=== ''Edge Cases'' ===
* All reviewers bid on the same project
** If different time stamps: bidding algorithm should give priority to reviewers that bid first
** If same time stamps: bidding algorithm should assign reviews randomly
* None of the reviews bid on any projects
** Bidding algorithm should assign reviews randomly
* Reviewer bids on their own project
** Bidding algorithm should not allow a reviewer to bid on their own project and should have validation to prevent assigning a reviewer their own project
* None of the reviewers bid on a specific project
** Bidding algorithm should still assign reviewers to this project

=== ''Manual Testing Plan'' ===
Manual testing should be preformed on an Expertiza server. 
Manual testing should (''at a minimum''):
* test that the UI is implemented as expected
* test that a participant can bid on projects to review
** test that a participant can move projects into the bidding column
** test that a participant can reorder projects in the bidding column
** test that a participant's bidding preferences save

=== ''RSpec Testing Plan'' ===
RSpec tests will need to be written to related controller(s) and model(s). 
These RSpec tests should (''at a minimum''):
* test basic functionality of controller(s)
* test validation of the model(s)
* test the scenarios (basic case & edge cases) mentioned above

 

==Team==
Yasmin Ahamed Adam (uahamed) 
Ryan Grainger (rpgraing) 
Luis Delossantos (lgdeloss) 
Colleen "Bria" Engen (ceengen) 
'''Mentor:''' Saurabh Shingte (svshingt)

 
==Resources==
''Previous Implementations'': [[http://wiki.expertiza.ncsu.edu/index.php/CSC/ECE_517_Fall_2019_-_E1986._Allow_reviewers_to_bid_on_what_to_review 1]], [[https://expertiza.csc.ncsu.edu/index.php/CSC/ECE_517_Spring_2020_-_E2021._Allow_reviewers_to_bid_on_what_to_review 2]] 
''Bidding Interface Implementation Pull Request'': [[https://github.com/expertiza/expertiza/pull/778 3]]

CSC/ECE 517 Fall 2020

2020-10-22T00:08:41Z

Lgdeloss: /* Writing Assignments */

== Writing Assignments ==
* [[CSC/ECE 517 Fall 2020 - E2070. Refactor response_controller.rb]]
* [[CSC/ECE 517 Fall 2020 - E2068. Refactor quiz_questionnaires_controller.rb]]
* [[CSC/ECE 517 Fall 2020 - E2062. Add test cases to review_mapping_helper.rb]]
* [[CSC/ECE 517 Fall 2020 - E2063. Refactor tree-display.js and tree_display_controller.rb]]
* [[CSC/ECE 517 Fall 2020 - E2064. Refactor reputation_web_service_controller.rb]]
* [[CSC/ECE 517 Fall 2020 - E2065. Fix view in student_task/list page]]
* [[CSC/ECE 517 Fall 2020 - E2066. Refactor lottery controller.rb]]
* [[CSC/ECE 517 Fall 2020 - E2067. Refactor student_teams_controller.rb]]
* [[CSC/ECE 517 Fall 2020 - E2073. Refactor course_controller.rb]]
* [[CSC/ECE 517 Fall 2020 - E2057. Restrict TAs’ ability to change their own grade and limit file-size upload]]
* [[CSC/ECE 517 Fall 2020 - E2052. Remove multiple topics at a time]]
* [[CSC/ECE 517 Fall 2020 - E2052. Remove multiple topics at a time]]
* [[CSC/ECE 517 Fall 2020 - E2056 Account_Request_Controller.rb]]
* [[CSC/ECE 517 Fall 2020 - E2059. Email notification to reviewers and instructors.rb]]
* [[CSC/ECE 517 Fall 2020 - E2058. Two issues related to assignment management]]
* [[CSC/ECE 517 Fall 2020 - E2071. Improve assessment360_controller.rb]]
* [[CSC/ECE 517 Fall 2020 - E2054. Auto generate submission directory names based on assignment names]]
* [[CSC/ECE 517 Fall 2020 - E2060. Review report should link to the usual view for reviews]]

== Final Project Design Documents ==
* [[CSC/ECE 517 Fall 2020 - E2082. Track time between successive tag assignments]]
* [[CSC/ECE 517 Fall 2020 - E2078. Improve self-review Link peer review & self-review to derive grades]]
* [[CSC/ECE 517 Fall 2020 - E2083. Revision_planning_tool_E2016]]
* [[CSC/ECE 517 Fall 2020 - E2085. Allow reviewers to bid on what to review]]
* [[CSC/ECE 517 Fall 2020 - E2086. Let course staff as well as students do reviews]]
* [[CSC/ECE 517 Fall 2020 - SQLFE. Refactor Submission.java]]