Expertiza_Wiki - User contributions [en]

CSC/ECE 517 Fall 2020 - E2081. Add a "cake" item type to rubrics

2020-10-29T00:59:50Z

Rma9: /* Proposed Solution */

=='''Problem Definition'''==

Expertiza rubrics are utilized to build questionnaires and these rubrics incorporate several kinds of items, including Criterion (dropdown + comment), Checkbox, MultipleChoice, and Scale. When we use these questionnaires for reviews, for example the teammate review assessment we encounter a few problems. One “problem” with all of these types is that there is nothing to stop a reviewer (say some student) from assigning the maximum score to all the reviewees (student's teammates). This is indeed a problem for teammate assessment, when the faculty asks for what fraction of the work each teammate did.So an alternative is needed, let’s call it a “Cake” item type, that allows a reviewer to divide a “cake” in any way between the reviewees, but does not allow him/her to divvy up more than 100% of the cake.

# When the reviewer submits a score that would bring the total assigned for this item to > 100%, the system needs to warn.
# The system must a reviewer to give him/herself a score
# The proposed design needs to be compatible with existing self reviews code and teammates reviews
# Design should be extensible to other kind of reviews apart from teammate reviews as well

[[File:1_hjrnZknuFZswxaOKFCrDjQ.png|center]]

For instance, the above figure consists of a team of 4 members, with self included as a team-member when reviewing every member's contribution.
<br>If A has reviewed his other 3 teammates B, C, D with contributions of 15%, 10%, and 45% respectively, he should only be allowed to review self with a contribution of 30% or lesser.

=='''Design'''==
==='''Proposed Solution'''===

The issue asks us to have a Cake type for the question taking in a participant’s contribution, whenever s/he is reviewing the other teammates. We add in a new Question type ‘Cake’, which will be extended from the Scored Question model [cake < scored question < choice question < question].

Potential ways of displaying the Cake question on the UI:

* Stars: Existing design for teammate reviews uses stars to symbolize the contribution provided by each student. We can implement the cake type using the same.
Cons: Stars are not very versatile when there are a greater number of students per team and if the student wants to equally rate their contribution.

* Drop Down: In order to give the student more flexibility, another way a student can pick the contribution of each team member is using a dropdown of the % values.
Cons: Drop down values need to be restricted to intervals of 5 or more, as the drop down becomes too long to display all values from 0-100.

* Text box with up-down arrows: Provides utmost flexibility and precision to the student while adding contribution of his team members, we can provide a text box with necessary validations which lets the student provide the contribution % for his teammates as any integral number within the limits. There will also be text to warn the user about how much contribution is remaining based on what is typed into the box and any previously completed teammate reviews.

We plan to implement the text box as follows:

[[File:Screen_Shot_2019-12-07_at_3.07.57_PM.png|center]]

Addressing self-reviews for Cake Type:

The amount of credit assigned to self will be the remaining amount of percentage not given to the other teammates for the reviews. This will eliminate the need to do a self-review to specifically assign the leftover percentage to oneself. The self percentages for the cake questions will only be assigned to a student once they have completed the reviews for all other teammates. This will ensure that the students are motivated to complete the teammate reviews and the self-review calculation is executed once (instead of needing to re-calculate after each review).

In the current system workflow, we found that the teammate reviews are taken as instances of TeammateReviewResponseMap. The questionnaire for reviewing teammates includes the question asking the cake (contribution) factor. Ideally, the cake should include the reviewer as well.

Currently, whenever a participant is reviewing their teammates they are shown a view where the names of their teammates are displayed with a 'Review' link next to them. The last line has the user name displayed with no link but reminder text to complete their reviews. We plan on updating this view once the reviews are complete for all teammates with a 'View' link in the user's line item that will show all of the self cake contributions.

Steps to reproduce the proposed workflow:
#Log in to expertiza to view the home page
#Login as an Instructor, and then impersonate a student or login as a Student
#Go to Assignments -> Your team
#You will see a list of your teammates with a link: ‘Review’
#You will see yourself with no present link, this will become visible once you complete all reviews as: 'View'
#You can see the questions for asking the contribution as a cake type
#There will be a text description next to it denoting what part of the cake is taken (what contribution factor of the work is used)
#For yourself the view will automatically be filled out with the leftover percentages for each cake contribution

==='''Why we chose this approach'''===
We found that it was efficient calculate a self contribution as the remaining percentage not assigned to all other teammates. This eliminates the need to create a specialized self-review to assign a contribution to oneself. We decided that it would be best to allow access to the self review once all other teammate reviews are complete because it encourages users to do their reviews and the final calculation for self contribution needs to only be done once.

==='''Implementation'''===

==='''Test plan'''===

==='''Deployment'''===

=='''Team Members'''==
*Jordan, Dylan Tyler dtjordan@ncsu.edu

*Ruoyun Ma rma9@ncsu.edu

*Han, Lige lhan6@ncsu.edu

*Kollipara, Siddhartha skollip@ncsu.edu

*'''Mentor''': Ed Gehringer (efg@ncsu.edu)

=='''References'''==
*[https://expertiza.csc.ncsu.edu/index.php/CSC/ECE_517_Fall_2019_-_E1992._Add_cake_type_to_rubrics_design CSC/ECE 517 Fall 2019 - E1992. Add cake type to rubrics design]
*[https://github.com/expertiza/expertiza Expertiza on GitHub]
*[http://expertiza.ncsu.edu/ The live Expertiza website]
*[http://research.csc.ncsu.edu/efg/expertiza Expertiza project Details]
*[https://www.youtube.com/channel/UCdKXzox7hrWjfOMML6FzTWg Expertiza YouTube Channel]

CSC/ECE 517 Fall 2020 - E2081. Add a "cake" item type to rubrics

2020-10-23T02:56:37Z

Rma9: /* Why we chose this approach: */

=='''Problem Definition'''==

Expertiza rubrics are utilized to build questionnaires and these rubrics incorporate several kinds of items, including Criterion (dropdown + comment), Checkbox, MultipleChoice, and Scale. When we use these questionnaires for reviews, for example the teammate review assessment we encounter a few problems. One “problem” with all of these types is that there is nothing to stop a reviewer (say some student) from assigning the maximum score to all the reviewees (student's teammates). This is indeed a problem for teammate assessment, when the faculty asks for what fraction of the work each teammate did.So an alternative is needed, let’s call it a “Cake” item type, that allows a reviewer to divide a “cake” in any way between the reviewees, but does not allow him/her to divvy up more than 100% of the cake.

#When the reviewer submits a score that would bring the total assigned for this item to > 100%, the system needs to warn.
#Allow a reviewer to give him/herself a score
# Proposed design needs to be compatible with existing self reviews code and teammates reviews
# Should be extensible to other kind of reviews apart from teammate reviews as well

[[File:1_hjrnZknuFZswxaOKFCrDjQ.png|center]]

For instance, the above figure consists of a team of 4 members, with self included as a team-member when reviewing every member's contribution.
<br>If A has reviewed his other 3 teammates B, C, D with contributions of 15%, 10%, and 45% respectively, he should only be allowed to review self with a contribution of 30% or lesser.

=='''Design'''==
==='''Proposed Solution'''===

The issue asks us to have a Cake type for the question taking in a participant’s contribution, whenever s/he is reviewing the other teammates. We add in a new Question type ‘Cake’, which will be extended from the Scored Question model [cake < scored question < choice question < question].

Potential ways of displaying the Cake question on the UI:

* Stars: Existing design for teammate reviews uses stars to symbolize the contribution provided by each student. We can implement the cake type using the same.
Cons: Stars are not very versatile when there are a greater number of students per team and if the student wants to equally rate their contribution.

* Drop Down: In order to give the student more flexibility, another way a student can pick the contribution of each team member is using a dropdown of the % values.
Cons: Drop down values need to be restricted to intervals of 5 or more, as the drop down becomes too long to display all values from 0-100.

* Text box with up-down arrows: Provides utmost flexibility and precision to the student while adding contribution of his team members, we can provide a text box with necessary validations which lets the student provide the contribution % for his teammates as any integral number within the limits. There will also be text to warn the user about how much contribution is remaining based on what is typed into the box and any previously completed teammate reviews.

We plan to implement the text box as follows:

[[File:Screen_Shot_2019-12-07_at_3.07.57_PM.png|center]]

Addressing self-reviews for Cake Type:

The amount of credit assigned to self will be the remaining amount of percentage not given to the other teammates for the reviews. This will eliminate the need to do a self-review to specifically assign the leftover percentage to oneself. The self percentages for the cake questions will only be assigned to a student once they have completed the reviews for all other teammates. This will ensure that the students are motivated to complete the teammate reviews and the self-review calculation is executed once (instead of needing to re-calculate after each review).

In the current system workflow, we found that the teammate reviews are taken as instances of TeammateReviewResponseMap. The questionnaire for reviewing teammates includes the question asking the cake (contribution) factor. Ideally, the cake should include the reviewer as well.

Currently, whenever a participant is reviewing their teammates they are shown a view where the names of their teammates are displayed with a 'Review' link next to them. The last line has the user name displayed with no link but reminder text to complete their reviews. We plan on updating this view once the reviews are complete for all teammates with a 'View' link in the user's line item that will show all of the self cake contributions.

Steps to reproduce the proposed workflow:
#Log in to expertiza to view the home page
#Login as an Instructor, and then impersonate a student or login as a Student
#Go to Assignments -> Your team
#You will see a list of your teammates with a link: ‘Review’
#You will see yourself with no present link, this will become visible once you complete all reviews as: 'View'
#You can see the questions for asking the contribution as a cake type
#There will be a text description next to it denoting what part of the cake is taken (what contribution factor of the work is used)
#For yourself the view will automatically be filled out with the leftover percentages for each cake contribution

==='''Why we chose this approach'''===
We found that it was efficient calculate a self contribution as the remaining percentage not assigned to all other teammates. This eliminates the need to create a specialized self-review to assign a contribution to oneself. We decided that it would be best to allow access to the self review once all other teammate reviews are complete because it encourages users to do their reviews and the final calculation for self contribution needs to only be done once.

==='''Implementation'''===

==='''Test plan'''===

==='''Deployment'''===

=='''Team Members'''==
*Jordan, Dylan Tyler dtjordan@ncsu.edu

*Ruoyun Ma rma9@ncsu.edu

*Han, Lige lhan6@ncsu.edu

*Kollipara, Siddhartha skollip@ncsu.edu

*'''Mentor''': Ed Gehringer (efg@ncsu.edu)

=='''References'''==
*[https://expertiza.csc.ncsu.edu/index.php/CSC/ECE_517_Fall_2019_-_E1992._Add_cake_type_to_rubrics_design CSC/ECE 517 Fall 2019 - E1992. Add cake type to rubrics design]
*[https://github.com/expertiza/expertiza Expertiza on GitHub]
*[http://expertiza.ncsu.edu/ The live Expertiza website]
*[http://research.csc.ncsu.edu/efg/expertiza Expertiza project Details]
*[https://www.youtube.com/channel/UCdKXzox7hrWjfOMML6FzTWg Expertiza YouTube Channel]

CSC/ECE 517 Fall 2020 - E2081. Add a "cake" item type to rubrics

2020-10-23T02:56:16Z

Rma9: /* Design */

=='''Problem Definition'''==

Expertiza rubrics are utilized to build questionnaires and these rubrics incorporate several kinds of items, including Criterion (dropdown + comment), Checkbox, MultipleChoice, and Scale. When we use these questionnaires for reviews, for example the teammate review assessment we encounter a few problems. One “problem” with all of these types is that there is nothing to stop a reviewer (say some student) from assigning the maximum score to all the reviewees (student's teammates). This is indeed a problem for teammate assessment, when the faculty asks for what fraction of the work each teammate did.So an alternative is needed, let’s call it a “Cake” item type, that allows a reviewer to divide a “cake” in any way between the reviewees, but does not allow him/her to divvy up more than 100% of the cake.

#When the reviewer submits a score that would bring the total assigned for this item to > 100%, the system needs to warn.
#Allow a reviewer to give him/herself a score
# Proposed design needs to be compatible with existing self reviews code and teammates reviews
# Should be extensible to other kind of reviews apart from teammate reviews as well

[[File:1_hjrnZknuFZswxaOKFCrDjQ.png|center]]

For instance, the above figure consists of a team of 4 members, with self included as a team-member when reviewing every member's contribution.
<br>If A has reviewed his other 3 teammates B, C, D with contributions of 15%, 10%, and 45% respectively, he should only be allowed to review self with a contribution of 30% or lesser.

=='''Design'''==
==='''Proposed Solution'''===

The issue asks us to have a Cake type for the question taking in a participant’s contribution, whenever s/he is reviewing the other teammates. We add in a new Question type ‘Cake’, which will be extended from the Scored Question model [cake < scored question < choice question < question].

Potential ways of displaying the Cake question on the UI:

* Stars: Existing design for teammate reviews uses stars to symbolize the contribution provided by each student. We can implement the cake type using the same.
Cons: Stars are not very versatile when there are a greater number of students per team and if the student wants to equally rate their contribution.

* Drop Down: In order to give the student more flexibility, another way a student can pick the contribution of each team member is using a dropdown of the % values.
Cons: Drop down values need to be restricted to intervals of 5 or more, as the drop down becomes too long to display all values from 0-100.

* Text box with up-down arrows: Provides utmost flexibility and precision to the student while adding contribution of his team members, we can provide a text box with necessary validations which lets the student provide the contribution % for his teammates as any integral number within the limits. There will also be text to warn the user about how much contribution is remaining based on what is typed into the box and any previously completed teammate reviews.

We plan to implement the text box as follows:

[[File:Screen_Shot_2019-12-07_at_3.07.57_PM.png|center]]

Addressing self-reviews for Cake Type:

The amount of credit assigned to self will be the remaining amount of percentage not given to the other teammates for the reviews. This will eliminate the need to do a self-review to specifically assign the leftover percentage to oneself. The self percentages for the cake questions will only be assigned to a student once they have completed the reviews for all other teammates. This will ensure that the students are motivated to complete the teammate reviews and the self-review calculation is executed once (instead of needing to re-calculate after each review).

In the current system workflow, we found that the teammate reviews are taken as instances of TeammateReviewResponseMap. The questionnaire for reviewing teammates includes the question asking the cake (contribution) factor. Ideally, the cake should include the reviewer as well.

Currently, whenever a participant is reviewing their teammates they are shown a view where the names of their teammates are displayed with a 'Review' link next to them. The last line has the user name displayed with no link but reminder text to complete their reviews. We plan on updating this view once the reviews are complete for all teammates with a 'View' link in the user's line item that will show all of the self cake contributions.

Steps to reproduce the proposed workflow:
#Log in to expertiza to view the home page
#Login as an Instructor, and then impersonate a student or login as a Student
#Go to Assignments -> Your team
#You will see a list of your teammates with a link: ‘Review’
#You will see yourself with no present link, this will become visible once you complete all reviews as: 'View'
#You can see the questions for asking the contribution as a cake type
#There will be a text description next to it denoting what part of the cake is taken (what contribution factor of the work is used)
#For yourself the view will automatically be filled out with the leftover percentages for each cake contribution

===Why we chose this approach:===
We found that it was efficient calculate a self contribution as the remaining percentage not assigned to all other teammates. This eliminates the need to create a specialized self-review to assign a contribution to oneself. We decided that it would be best to allow access to the self review once all other teammate reviews are complete because it encourages users to do their reviews and the final calculation for self contribution needs to only be done once.

==='''Implementation'''===

==='''Test plan'''===

==='''Deployment'''===

=='''Team Members'''==
*Jordan, Dylan Tyler dtjordan@ncsu.edu

*Ruoyun Ma rma9@ncsu.edu

*Han, Lige lhan6@ncsu.edu

*Kollipara, Siddhartha skollip@ncsu.edu

*'''Mentor''': Ed Gehringer (efg@ncsu.edu)

=='''References'''==
*[https://expertiza.csc.ncsu.edu/index.php/CSC/ECE_517_Fall_2019_-_E1992._Add_cake_type_to_rubrics_design CSC/ECE 517 Fall 2019 - E1992. Add cake type to rubrics design]
*[https://github.com/expertiza/expertiza Expertiza on GitHub]
*[http://expertiza.ncsu.edu/ The live Expertiza website]
*[http://research.csc.ncsu.edu/efg/expertiza Expertiza project Details]
*[https://www.youtube.com/channel/UCdKXzox7hrWjfOMML6FzTWg Expertiza YouTube Channel]

CSC/ECE 517 Fall 2020 - E2081. Add a "cake" item type to rubrics

2020-10-23T01:55:01Z

Rma9: /* Problem Definition: */

=='''Problem Definition'''==

Expertiza rubrics are utilized to build questionnaires and these rubrics incorporate several kinds of items, including Criterion (dropdown + comment), Checkbox, MultipleChoice, and Scale. When we use these questionnaires for reviews, for example the teammate review assessment we encounter a few problems. One “problem” with all of these types is that there is nothing to stop a reviewer (say some student) from assigning the maximum score to all the reviewees (student's teammates). This is indeed a problem for teammate assessment, when the faculty asks for what fraction of the work each teammate did.So an alternative is needed, let’s call it a “Cake” item type, that allows a reviewer to divide a “cake” in any way between the reviewees, but does not allow him/her to divvy up more than 100% of the cake.

#When the reviewer submits a score that would bring the total assigned for this item to > 100%, the system needs to warn.
#Allow a reviewer to give him/herself a score
# Proposed design needs to be compatible with existing self reviews code and teammates reviews
# Should be extensible to other kind of reviews apart from teammate reviews as well

[[File:1_hjrnZknuFZswxaOKFCrDjQ.png|center]]

For instance, the above figure consists of a team of 4 members, with self included as a team-member when reviewing every member's contribution.
<br>If A has reviewed his other 3 teammates B, C, D with contributions of 15%, 10%, and 45% respectively, he should only be allowed to review self with a contribution of 30% or lesser.

==Design==
===Proposed Solution:===

The issue asks us to have a Cake type for the question taking in a participant’s contribution, whenever s/he is reviewing the other teammates. We add in a new Question type ‘Cake’, which will be extended from the Scored Question model [cake < scored question < choice question < question].

Potential ways of displaying the Cake question on the UI:

* Stars: Existing design for teammate reviews uses stars to symbolize the contribution provided by each student. We can implement the cake type using the same.
Cons: Stars are not very versatile when there are a greater number of students per team and if the student wants to equally rate their contribution.

* Drop Down: In order to give the student more flexibility, another way a student can pick the contribution of each team member is using a dropdown of the % values.
Cons: Drop down values need to be restricted to intervals of 5 or more, as the drop down becomes too long to display all values from 0-100.

* Text box with up-down arrows: Provides utmost flexibility and precision to the student while adding contribution of his team members, we can provide a text box with necessary validations which lets the student provide the contribution % for his teammates as any integral number within the limits.

We decided to implement the text box, looks as follows:

[[File:Screen_Shot_2019-12-07_at_3.07.57_PM.png|center]]

Addressing self-reviews for Cake Type:

The amount of credit assigned to self will be the remaining amount of percentage not given to the other teammates for the reviews. This will eliminate the need to do a self-review to specifically assign the leftover percentage to oneself. The self percentages for the cake questions will only be assigned to a student once they have completed the reviews for all other teammates. This will ensure that the students are motivated to complete the teammate reviews and the self-review calculation is executed once (instead of needing to re-calculate after each review).

Steps to reproduce the proposed workflow:
#Log in to expertiza to view the home page
#Login as an Instructor, and then impersonate a student or login as a Student
#Go to Assignments -> Your team
#You will see a list of your teammates with a link: ‘Review’
#You will see yourself with no present link, this will become visible once you complete all reviews as: 'View'
#You can see the questions for asking the contribution as a cake type
#There will be a text description next to it denoting what part of the cake is taken (what contribution factor of the work is used)
#For yourself the view will automatically be filled out with the leftover percentages for each cake contribution

==='''Implementation'''===

==='''Test plan'''===

==='''Deployment'''===

=='''Team Members'''==
*Jordan, Dylan Tyler dtjordan@ncsu.edu

*Ruoyun Ma rma9@ncsu.edu

*Han, Lige lhan6@ncsu.edu

*Kollipara, Siddhartha skollip@ncsu.edu

*'''Mentor''': Ed Gehringer (efg@ncsu.edu)

=='''References'''==
*[https://expertiza.csc.ncsu.edu/index.php/CSC/ECE_517_Fall_2019_-_E1992._Add_cake_type_to_rubrics_design CSC/ECE 517 Fall 2019 - E1992. Add cake type to rubrics design]
*[https://github.com/expertiza/expertiza Expertiza on GitHub]
*[http://expertiza.ncsu.edu/ The live Expertiza website]
*[http://research.csc.ncsu.edu/efg/expertiza Expertiza project Details]
*[https://www.youtube.com/channel/UCdKXzox7hrWjfOMML6FzTWg Expertiza YouTube Channel]

CSC/ECE 517 Fall 2020 - E2081. Add a "cake" item type to rubrics

2020-10-23T01:10:19Z

Rma9: /* Problem Definition: */

=='''Problem Definition:'''==

Expertiza rubrics are utilized to build questionnaires and these rubrics incorporate several kinds of items, including Criterion (dropdown + comment), Checkbox, MultipleChoice, and Scale. When we use these questionnaires for reviews, for example the teammate review assessment we encounter a few problems. One “problem” with all of these types is that there is nothing to stop a reviewer (say some student) from assigning the maximum score to all the reviewees (student's teammates). This is indeed a problem for teammate assessment, when the faculty asks for what fraction of the work each teammate did.So an alternative is needed, let’s call it a “Cake” item type, that allows a reviewer to divide a “cake” in any way between the reviewees, but does not allow him/her to divvy up more than 100% of the cake.

#When the reviewer submits a score that would bring the total assigned for this item to > 100%, the system needs to warn.
#Allow a reviewer to give him/herself a score
# Proposed design needs to be compatible with existing self reviews code and teammates reviews
# Should be extensible to other kind of reviews apart from teammate reviews as well

[[File:1_hjrnZknuFZswxaOKFCrDjQ.png|center]]

For instance, the above figure consists of a team of 4 members, with self included as a team-member when reviewing every member's contribution.
<br>If A has reviewed his other 3 teammates B, C, D with contributions of 15%, 10%, and 45% respectively, he should only be allowed to review self with a contribution of 30% or lesser.

==Design==
===Proposed Solution:===

The issue asks us to have a Cake type for the question taking in a participant’s contribution, whenever s/he is reviewing the other teammates. We add in a new Question type ‘Cake’, which will be extended from the Scored Question model [cake < scored question < choice question < question].

Potential ways of displaying the Cake question on the UI:

* Stars: Existing design for teammate reviews uses stars to symbolize the contribution provided by each student. We can implement the cake type using the same.
Cons: Stars are not very versatile when there are a greater number of students per team and if the student wants to equally rate their contribution.

* Drop Down: In order to give the student more flexibility, another way a student can pick the contribution of each team member is using a dropdown of the % values.
Cons: Drop down values need to be restricted to intervals of 5 or more, as the drop down becomes too long to display all values from 0-100.

* Text box with up-down arrows: Provides utmost flexibility and precision to the student while adding contribution of his team members, we can provide a text box with necessary validations which lets the student provide the contribution % for his teammates as any integral number within the limits.

We decided to implement the text box, looks as follows:

[[File:Screen_Shot_2019-12-07_at_3.07.57_PM.png|center]]

==='''Implementation'''===

==='''Test plan'''===

==='''Deployment'''===

=='''Team Members'''==
*Jordan, Dylan Tyler dtjordan@ncsu.edu

*Ruoyun Ma rma9@ncsu.edu

*Han, Lige lhan6@ncsu.edu

*Kollipara, Siddhartha skollip@ncsu.edu

*'''Mentor''': Ed Gehringer (efg@ncsu.edu)

=='''References'''==
*[https://expertiza.csc.ncsu.edu/index.php/CSC/ECE_517_Fall_2019_-_E1992._Add_cake_type_to_rubrics_design CSC/ECE 517 Fall 2019 - E1992. Add cake type to rubrics design]
*[https://github.com/expertiza/expertiza Expertiza on GitHub]
*[http://expertiza.ncsu.edu/ The live Expertiza website]
*[http://research.csc.ncsu.edu/efg/expertiza Expertiza project Details]
*[https://www.youtube.com/channel/UCdKXzox7hrWjfOMML6FzTWg Expertiza YouTube Channel]

CSC/ECE 517 Fall 2020 - E2081. Add a "cake" item type to rubrics

2020-10-23T01:07:16Z

Rma9: /* References */

==Problem Definition:==

Expertiza rubrics are utilized to build questionnaires and these rubrics incorporate several kinds of items, including Criterion (dropdown + comment), Checkbox, MultipleChoice, and Scale. When we use these questionnaires for reviews, for example the teammate review assessment we encounter a few problems. One “problem” with all of these types is that there is nothing to stop a reviewer (say some student) from assigning the maximum score to all the reviewees (student's teammates). This is indeed a problem for teammate assessment, when the faculty asks for what fraction of the work each teammate did.So an alternative is needed, let’s call it a “Cake” item type, that allows a reviewer to divide a “cake” in any way between the reviewees, but does not allow him/her to divvy up more than 100% of the cake.

#When the reviewer submits a score that would bring the total assigned for this item to > 100%, the system needs to warn.
#Allow a reviewer to give him/herself a score
# Proposed design needs to be compatible with existing self reviews code and teammates reviews
# Should be extensible to other kind of reviews apart from teammate reviews as well

[[File:1_hjrnZknuFZswxaOKFCrDjQ.png|center]]

For instance, the above figure consists of a team of 4 members, with self included as a team-member when reviewing every member's contribution.
<br>If A has reviewed his other 3 teammates B, C, D with contributions of 15%, 10%, and 45% respectively, he should only be allowed to review self with a contribution of 30% or lesser.

==Design==
===Proposed Solution:===

The issue asks us to have a Cake type for the question taking in a participant’s contribution, whenever s/he is reviewing the other teammates. We add in a new Question type ‘Cake’, which will be extended from the Scored Question model [cake < scored question < choice question < question].

Potential ways of displaying the Cake question on the UI:

* Stars: Existing design for teammate reviews uses stars to symbolize the contribution provided by each student. We can implement the cake type using the same.
Cons: Stars are not very versatile when there are a greater number of students per team and if the student wants to equally rate their contribution.

* Drop Down: In order to give the student more flexibility, another way a student can pick the contribution of each team member is using a dropdown of the % values.
Cons: Drop down values need to be restricted to intervals of 5 or more, as the drop down becomes too long to display all values from 0-100.

* Text box with up-down arrows: Provides utmost flexibility and precision to the student while adding contribution of his team members, we can provide a text box with necessary validations which lets the student provide the contribution % for his teammates as any integral number within the limits.

We decided to implement the text box, looks as follows:

[[File:Screen_Shot_2019-12-07_at_3.07.57_PM.png|center]]

==='''Implementation'''===

==='''Test plan'''===

==='''Deployment'''===

=='''Team Members'''==
*Jordan, Dylan Tyler dtjordan@ncsu.edu

*Ruoyun Ma rma9@ncsu.edu

*Han, Lige lhan6@ncsu.edu

*Kollipara, Siddhartha skollip@ncsu.edu

*'''Mentor''': Ed Gehringer (efg@ncsu.edu)

=='''References'''==
*[https://expertiza.csc.ncsu.edu/index.php/CSC/ECE_517_Fall_2019_-_E1992._Add_cake_type_to_rubrics_design CSC/ECE 517 Fall 2019 - E1992. Add cake type to rubrics design]
*[https://github.com/expertiza/expertiza Expertiza on GitHub]
*[http://expertiza.ncsu.edu/ The live Expertiza website]
*[http://research.csc.ncsu.edu/efg/expertiza Expertiza project Details]
*[https://www.youtube.com/channel/UCdKXzox7hrWjfOMML6FzTWg Expertiza YouTube Channel]

CSC/ECE 517 Fall 2020 - E2081. Add a "cake" item type to rubrics

2020-10-23T01:04:59Z

Rma9: /* References */

CSC/ECE 517 Fall 2020 - E2081. Add a "cake" item type to rubrics

2020-10-23T01:04:34Z

Rma9: /* References */

CSC/ECE 517 Fall 2020 - E2081. Add a "cake" item type to rubrics

2020-10-23T01:01:03Z

Rma9: /* References */

CSC/ECE 517 Fall 2020 - E2081. Add a "cake" item type to rubrics

2020-10-22T23:41:53Z

Rma9: Create a new web page and write contents

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

==='''Files Involved'''===

==='''Changes plan to make'''===

=='''Design'''==

==='''Implementation'''===

==='''Test plan'''===

==='''Deployment'''===

=='''Team Members'''==
*Jordan, Dylan Tyler dtjordan@ncsu.edu

*Ruoyun Ma rma9@ncsu.edu

*Han, Lige lhan6@ncsu.edu

*Kollipara, Siddhartha skollip@ncsu.edu

*'''Mentor''': Ed Gehringer (efg@ncsu.edu)

=='''References'''==
*[https://github.com/expertiza/expertiza Expertiza on GitHub]
*[http://expertiza.ncsu.edu/ The live Expertiza website]
*[http://research.csc.ncsu.edu/efg/expertiza Expertiza project Details]
*[https://www.youtube.com/channel/UCdKXzox7hrWjfOMML6FzTWg Expertiza YouTube Channel]

CSC/ECE 517 Fall 2020

2020-10-22T23:27:41Z

Rma9: Adding new page of E2081

== 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]]
* [[CSC/ECE 517 Fall 2020 - E2075. calibration submissions should be copied along with calibration assignments]]
* [[CSC/ECE 517 Fall 2020 - E2076. Allow users to create an account and submit work to an "assignment" (e.g., for conference reviewing)]]
* [[CSC/ECE 517 Fall 2020 - E2080. Track the time students look at other submissions]]
* [[CSC/ECE 517 Fall 2020 - E2081. Add a "cake" item type to rubrics]]
* [[CSC/ECE 517 Fall 2020 - E2079. Improve Search Facility In Expertiza]]
* [[CSC/ECE 517 Fall 2020 - E2087. Conflict notification. Improve Search Facility In Expertiza]]

CSC/ECE 517 Fall 2020 - E2065. Fix view in student task/list page

2020-10-16T08:30:26Z

Rma9:

=='''Team Members'''==
*Junyan Li jli56@ncsu.edu

*Ruoyun Ma rma9@ncsu.edu

*Xiwen Chen xchen33@ncsu.edu

*'''Mentor''': Saurabh Shingte (svshingt@ncsu.edu)

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

The student_task/list page is the page displayed to a student after logging in into expertiza.

It has mainly two div(s), one to show the upcoming tasks including 2 parts:

* Information about tasks. It shows the projects that need to be completed and how long they are close to the deadline, and marks specific revisions prompts.

* Show the record of each group collaborator(s) for each course.

Another div is to display all the assignments and their information, include Assignment, Course, Topic, Current Stage, Review Grade, Badges, Stage Deadline, Copyright Grants and Make Public.

Original page before modifying showing below, all the courses and all the assignments are displaying in the same table, and badges have own column.

[[File:Orignal.JPG|1000px]]
[[File:Originalcourse.JPG|1000px]]

==='''Files Involved'''===

*app/helpers/student_task_helper.rb

*app/views/student_task/list.html.erb

*spec/features/airbrake_expection_errors_feature_tests_spec.rb

*spec/features/student_task_spec.rb

==='''Problems that need to be fixed'''===

Here are some existing problems and unclear parts of the page：

*'''Problem1''': Consider the cases where a student might be enrolled in assignments from more than one course. In this case, assignments should be grouped by course, with the course name given before the listing of the first assignment.

*'''Problem2''': Remove the column for Review Grade because it makes no sense, change Review Grade to Submission Grade. Show the actual score and show the blue button. If you hover over your mouse at the blue button, should also show the commands about grades.

*'''Problem3''': Delete the badges column, and if the Assignment has a badge, mark it directly next to the assignment name under the assignment column.

*'''Problem4''': There is an unnecessary gap between the two div. It needs to be rearranged to be more beautiful.

=='''Solutions'''==
==='''Problem 1, group the course and display on different tables'''===

Fixing app/views/student_task/list.html.erb

original code of how to display course are showing below
<pre>
<div class="topictable">
<table class="table table-striped" cellpadding="2">
<tr class="taskheader">
<th>Assignment</th>
<th>Course</th>
<th>Topic</th>
<th>Current Stage</th>
<th>Review Grade</th>
<th>Badges</th>
<th>Stage Deadline <img src="/assets/info.png" title="You can change 'Preferred Time Zone' in 'Profile' in the banner."/></th>
<th>Publishing Rights</th>
</tr>
<% @student_tasks.each do |student_task| %>
<% participant = student_task.participant %>
<% if student_task.assignment %>
<tr class="listingRow">

<td><b><%= link_to student_task.assignment.name, :action => 'view', :id => participant %></b></td>

<td><%= student_task.course.try :name %></td>

<% topic_id = SignedUpTeam.topic_id(participant.parent_id, participant.user_id) %>
<% if SignUpTopic.exists?(topic_id) %>
<td><%= SignUpTopic.find(topic_id).try :topic_name %></td>
<% else %>
<td>-</td>
<% end %>

<td>
<% if participant.assignment.link_for_current_stage(topic_id)!= nil && participant.assignment.link_for_current_stage(topic_id).length!=0%>
<%= link_to participant.assignment.current_stage_name(topic_id), participant.assignment.link_for_current_stage(topic_id) %>
<% else %>
<%= participant.assignment.current_stage_name(topic_id) %>
<% end %>
</td>

<td><%= get_review_grade_info(participant) %></td>

<td><%= get_awarded_badges(participant) %></td>

<td><%= student_task.stage_deadline.in_time_zone(session[:user].timezonepref) %></td>

<td align=center><%= participant.permission_granted ? "granted" : "denied" %></td>
</tr>
<% end %>
<% end %>
</table>
</pre>

In order to group the courses, we added a group_by method to find out which courses does this assignment belongs to, and group the assignments that has the same courses name at one table. The modified code is showing below.

<pre>
<% group = @student_tasks.group_by(&:course).each do | course, student_tasks|%>
<% if course%>
<%end %>
<div class="topictable" style="float: right;width: 80%;margin-bottom: 10px; display: inline-block; border: 1px solid #000000">

<% if !student_tasks.first.course %>
<h1>No Course Assigned Yet</h1>
<%else%>
<h1><%=student_tasks.first.course.try :name %></h1>
<%end%>
</pre>

We will print out the course name as each table head, group the assignments, and we take down Course coloum from table content since the course name is already showing as table head. Also, for the assignments that have not assigned to a course, we will print out <q>No Course Assigned Yet</q>.

==='''Problem 2, submission grade display'''===

Fixing app/views/student_task/list.html.erb
app/helpers/student_task_helper.rb

For this problem, first, we change Review Grade to Submission grade, which only need to modify
<pre>
<th>Review Grade</th>
</pre>
to
<pre>
<th>Submission Grade</th>
</pre>
on list.html.erb.

Second, we change how we display the score. Instead of showing a blue button, we added how much scores they got (e.g. 32/40), which make users easier to see what scores they got. We modified get_review_grade_info(participant) function inside of student_task_helper.rb.

Original code is showing below
<pre>
def get_review_grade_info(participant)
info = ''
if participant.try(:review_grade).try(:grade_for_reviewer).nil? ||
participant.try(:review_grade).try(:comment_for_reviewer).nil?
result = "N/A"
else
info = "Score: " + participant.try(:review_grade).try(:grade_for_reviewer).to_s + "/100\n"
info += "Comment: " + participant.try(:review_grade).try(:comment_for_reviewer).to_s
info = truncate(info, length: 1500, omission: '...')
result = "<img src = '/assets/info.png' title = '" + info + "'>"
end
result.html_safe
end
</pre>

In the orignal code, each grade is assigned to /100, which is not correct because not every assignment has 10 reviews (one review count for 10 point). Instead of using /100, we use num_reviews_allowed, it will give us the maximum reviews that each assignments are allowed. Since we need to display the current score on the page, we need an array to carry the current score and display it on the result. The modified code showing below.

<pre>
def get_review_grade_info(participant)
info = ''
if participant.try(:review_grade).try(:grade_for_reviewer).nil? ||
participant.try(:review_grade).try(:comment_for_reviewer).nil?
result = "N/A"
else
score = participant.try(:review_grade).try(:grade_for_reviewer).to_s + "/" + (participant.assignment.num_reviews_allowed*10).to_s
info = "Score: " + participant.try(:review_grade).try(:grade_for_reviewer).to_s + "/" + (participant.assignment.num_reviews_allowed*10).to_s + "\n"
info += "Comment: " + participant.try(:review_grade).try(:comment_for_reviewer).to_s
info = truncate(info, length: 1500, omission: '...')
result = score + "<img src = '/assets/info.png' title = '" + info + "'>"
end
</pre>

==='''Problem 3, badges showing location fixing'''===

Fixing app/views/student_task/list.html.erb

Since not too many assignments are able to get badges, that make badges column barely have contents. Therefore, we display it after the assignment name and delete Badges coloum. If one student gets a badge, it will display a small picture after the badged assignment. Hover over your mouse on it, and it will display the information about this badge.

<pre>

<td><b><%= link_to student_task.assignment.name, :action => 'view', :id => participant %></b><p><%= get_awarded_badges(participant) %></p></td>
</pre>

==='''Problem 4, unnecessary white space'''===
Fixing app/views/student_task/list.html.erb
Our main purpose of this project is to make the student_task/list page looks better. For problem 4, we fixed unnecessary white space between two divs. We changed two div's style to style = <q>width:18</q> and style = <q>width:80</q>, so two div will display on the same lines.
<pre>
<div class="taskbox" style="width:18%; display: inline-block; float:left; margin-right: 10px;" >
</pre>

<pre>
<div class="topictable" style="float: right;width: 80%;margin-bottom: 10px; display: inline-block; border: 1px solid #000000">
</pre>
=='''Test'''==

==='''Page Change Display'''===

Page showing right now
[[File:Coursedisplay.PNG|1000px]]

[[File:Differentgroup.JPG|1000px]]

==='''RSpec test'''===
According to the modification of each problem, we write test separately to test whether its function is realized or not.

First, we modified spec/features/airbrake_expection_errors_feature_tests_spec.rb. Since when no assignment was assigned to the student, it should not show the table content on the page. Change from
<pre>
it "can access to '/student_task/list' after login as a student" do
stu = create(:student)
login_as stu.name
visit '/tree_display/list'
expect(page).to have_current_path('/student_task/list')
expect(page).to have_content('Assignments')
expect(page).to have_content('Tasks not yet started')
expect(page).to have_content('Students who have teamed with you')
expect(page).to have_content('Review Grade')
expect(page).to have_content('Publishing Rights')
expect(page).not_to have_content('Welcome!')
expect(page).not_to have_content('User Name')
expect(page).not_to have_content('Password')
expect(page).not_to have_content('SIGN IN')
end
</pre>

to

<pre>
it "can access to '/student_task/list' after login as a student" do
stu = create(:student)
login_as stu.name
visit '/tree_display/list'
expect(page).to have_current_path('/student_task/list')
expect(page).to have_content('Assignments')
expect(page).to have_content('Tasks not yet started')
expect(page).to have_content('Students who have teamed with you')
expect(page).not_to have_content('Review Grade')
expect(page).not_to have_content('Publishing Rights')
expect(page).not_to have_content('Welcome!')
expect(page).not_to have_content('User Name')
expect(page).not_to have_content('Password')
expect(page).not_to have_content('SIGN IN')
end
</pre>

==='''Deployment'''===

We deploy this part of the program on VCL to test UI and other functions. The link to the website is as follows:
[http://152.46.19.28:8080 E2065 Repo Link]

Using the following account to log in for testing：

Username: instructor6

Password: password

And then click [http://152.46.19.28:8080/student_task/list 'Assignments'] to the fixed page.

=='''References'''==
*[https://github.com/expertiza/expertiza Expertiza on GitHub]
*[http://expertiza.ncsu.edu/ The live Expertiza website]
*[http://research.csc.ncsu.edu/efg/expertiza Expertiza project Details]
*[https://www.youtube.com/channel/UCdKXzox7hrWjfOMML6FzTWg Expertiza YouTube Channel]

CSC/ECE 517 Fall 2020 - E2065. Fix view in student task/list page

2020-10-16T07:01:11Z

Rma9: /* Problem 4, unnecssary white space */

=='''Team Members'''==
*Junyan Li jli56@ncsu.edu

*Ruoyun Ma rma9@ncsu.edu

*Xiwen Chen xchen33@ncsu.edu

*'''Mentor''': Saurabh Shingte (svshingt@ncsu.edu)

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

The student_task/list page is the page displayed to a student after logging in into expertiza.

It has mainly two div(s), one to show the upcoming tasks including 2 parts:

* Information about tasks. It shows the projects that need to be completed and how long they are close to the deadline, and marks specific revisions prompts.

* Show the record of each group collaborator(s) for each course.

Another div is to display all the assignments and their information, include Assignment, Course, Topic, Current Stage, Review Grade, Badges, Stage Deadline, Copyright Grants and Make Public.

Original page before modifying showing below, all the courses and all the assignments are displaying in the same table, and badges have own column.

[[File:Orignal.JPG|1000px]]
[[File:Originalcourse.JPG|1000px]]

==='''Files Involved'''===

*app/helpers/student_task_helper.rb

*app/views/student_task/list.html.erb

*spec/features/airbrake_expection_errors_feature_tests_spec.rb

*spec/features/student_task_spec.rb

==='''Problems that need to be fixed'''===

Here are some existing problems and unclear parts of the page：

*'''Problem1''': Consider the cases where a student might be enrolled in assignments from more than one course. In this case, assignments should be grouped by course, with the course name given before the listing of the first assignment.

*'''Problem2''': Remove the column for Review Grade because it makes no sense, change Review Grade to Submission Grade. Show the actual score and show the blue button. If you hover over your mouse at the blue button, should also show the commands about grades.

*'''Problem3''': Delete the badges column, and if the Assignment has a badge, mark it directly next to the assignment name under the assignment column.

*'''Problem4''': There is an unnecessary gap between the two div. It needs to be rearranged to be more beautiful.

=='''Solutions'''==
==='''Problem 1, group the course and display on different tables'''===

Fixing app/views/student_task/list.html.erb

original code of how to display course are showing below
<pre>
<div class="topictable">
<table class="table table-striped" cellpadding="2">
<tr class="taskheader">
<th>Assignment</th>
<th>Course</th>
<th>Topic</th>
<th>Current Stage</th>
<th>Review Grade</th>
<th>Badges</th>
<th>Stage Deadline <img src="/assets/info.png" title="You can change 'Preferred Time Zone' in 'Profile' in the banner."/></th>
<th>Publishing Rights</th>
</tr>
<% @student_tasks.each do |student_task| %>
<% participant = student_task.participant %>
<% if student_task.assignment %>
<tr class="listingRow">

<td><b><%= link_to student_task.assignment.name, :action => 'view', :id => participant %></b></td>

<td><%= student_task.course.try :name %></td>

<% topic_id = SignedUpTeam.topic_id(participant.parent_id, participant.user_id) %>
<% if SignUpTopic.exists?(topic_id) %>
<td><%= SignUpTopic.find(topic_id).try :topic_name %></td>
<% else %>
<td>-</td>
<% end %>

<td>
<% if participant.assignment.link_for_current_stage(topic_id)!= nil && participant.assignment.link_for_current_stage(topic_id).length!=0%>
<%= link_to participant.assignment.current_stage_name(topic_id), participant.assignment.link_for_current_stage(topic_id) %>
<% else %>
<%= participant.assignment.current_stage_name(topic_id) %>
<% end %>
</td>

<td><%= get_review_grade_info(participant) %></td>

<td><%= get_awarded_badges(participant) %></td>

<td><%= student_task.stage_deadline.in_time_zone(session[:user].timezonepref) %></td>

<td align=center><%= participant.permission_granted ? "granted" : "denied" %></td>
</tr>
<% end %>
<% end %>
</table>
</pre>

In order to group the courses, we added a group_by method to find out which courses does this assignment belongs to, and group the assignments that has the same courses name at one table. The modified code is showing below.

<pre>
<% group = @student_tasks.group_by(&:course).each do | course, student_tasks|%>
<% if course%>
<%end %>
<div class="topictable" style="float: right;width: 80%;margin-bottom: 10px; display: inline-block; border: 1px solid #000000">

<% if !student_tasks.first.course %>
<h1>No Course Assigned Yet</h1>
<%else%>
<h1><%=student_tasks.first.course.try :name %></h1>
<%end%>
</pre>

We will print out the course name as each table head, group the assignments, and we take down Course coloum from table content since the course name is already showing as table head. Also, for the assignments that have not assigned to a course, we will print out <q>No Course Assigned Yet</q>.

==='''Problem 2, submission grade display'''===

Fixing app/views/student_task/list.html.erb
app/helpers/student_task_helper.rb

For this problem, first, we change Review Grade to Submission grade, which only need to modify
<pre>
<th>Review Grade</th>
</pre>
to
<pre>
<th>Submission Grade</th>
</pre>
on list.html.erb.

Second, we change how we display the score. Instead of showing a blue button, we added how much scores they got (e.g. 32/40), which make users easier to see what scores they got. We modified get_review_grade_info(participant) function inside of student_task_helper.rb.

Original code is showing below
<pre>
def get_review_grade_info(participant)
info = ''
if participant.try(:review_grade).try(:grade_for_reviewer).nil? ||
participant.try(:review_grade).try(:comment_for_reviewer).nil?
result = "N/A"
else
info = "Score: " + participant.try(:review_grade).try(:grade_for_reviewer).to_s + "/100\n"
info += "Comment: " + participant.try(:review_grade).try(:comment_for_reviewer).to_s
info = truncate(info, length: 1500, omission: '...')
result = "<img src = '/assets/info.png' title = '" + info + "'>"
end
result.html_safe
end
</pre>

In the orignal code, each grade is assigned to /100, which is not correct because not every assignment has 10 reviews (one review count for 10 point). Instead of using /100, we use num_reviews_allowed, it will give us the maximum reviews that each assignments are allowed. Since we need to display the current score on the page, we need an array to carry the current score and display it on the result. The modified code showing below.

<pre>
def get_review_grade_info(participant)
info = ''
if participant.try(:review_grade).try(:grade_for_reviewer).nil? ||
participant.try(:review_grade).try(:comment_for_reviewer).nil?
result = "N/A"
else
score = participant.try(:review_grade).try(:grade_for_reviewer).to_s + "/" + (participant.assignment.num_reviews_allowed*10).to_s
info = "Score: " + participant.try(:review_grade).try(:grade_for_reviewer).to_s + "/" + (participant.assignment.num_reviews_allowed*10).to_s + "\n"
info += "Comment: " + participant.try(:review_grade).try(:comment_for_reviewer).to_s
info = truncate(info, length: 1500, omission: '...')
result = score + "<img src = '/assets/info.png' title = '" + info + "'>"
end
</pre>

==='''Problem 3, badges showing location fixing'''===

Fixing app/views/student_task/list.html.erb

Since not too many assignments are able to get badges, that make badges column barely have contents. Therefore, we display it after the assignment name and delete Badges coloum. If one student gets a badge, it will display a small picture after the badged assignment. Hover over your mouse on it, and it will display the information about this badge.

<pre>

<td><b><%= link_to student_task.assignment.name, :action => 'view', :id => participant %></b><p><%= get_awarded_badges(participant) %></p></td>
</pre>

==='''Problem 4, unnecessary white space'''===
Fixing app/views/student_task/list.html.erb
Our main purpose of this project is to make the student_task/list page looks better. For problem 4, we fixed unnecessary white space between two divs. We changed two div's style to style = <q>width:18</q> and style = <q>width:80</q>, so two div will display on the same lines.
<pre>
<div class="taskbox" style="width:18%; display: inline-block; float:left; margin-right: 10px;" >
</pre>

<pre>
<div class="topictable" style="float: right;width: 80%;margin-bottom: 10px; display: inline-block; border: 1px solid #000000">
</pre>

==='''Page Change Display'''===

Page showing right now
[[File:Coursedisplay.PNG|1000px]]

[[File:Differentgroup.JPG|1000px]]

=='''RSpec test'''==
According to the modification of each problem, we write test separately to test whether its function is realized or not.

First, we modified spec/features/airbrake_expection_errors_feature_tests_spec.rb. Since when no assignment was assigned to the student, it should not show the table content on the page. Change from
<pre>
it "can access to '/student_task/list' after login as a student" do
stu = create(:student)
login_as stu.name
visit '/tree_display/list'
expect(page).to have_current_path('/student_task/list')
expect(page).to have_content('Assignments')
expect(page).to have_content('Tasks not yet started')
expect(page).to have_content('Students who have teamed with you')
expect(page).to have_content('Review Grade')
expect(page).to have_content('Publishing Rights')
expect(page).not_to have_content('Welcome!')
expect(page).not_to have_content('User Name')
expect(page).not_to have_content('Password')
expect(page).not_to have_content('SIGN IN')
end
</pre>

to

<pre>
it "can access to '/student_task/list' after login as a student" do
stu = create(:student)
login_as stu.name
visit '/tree_display/list'
expect(page).to have_current_path('/student_task/list')
expect(page).to have_content('Assignments')
expect(page).to have_content('Tasks not yet started')
expect(page).to have_content('Students who have teamed with you')
expect(page).not_to have_content('Review Grade')
expect(page).not_to have_content('Publishing Rights')
expect(page).not_to have_content('Welcome!')
expect(page).not_to have_content('User Name')
expect(page).not_to have_content('Password')
expect(page).not_to have_content('SIGN IN')
end
</pre>

==='''Test Repo'''===

We deploy this part of the program on VCL to test UI and other functions. The link to the website is as follows:
[http://152.46.19.28:8080 E2065 Repo Link]

Using the following account to log in for testing：

Username: instructor6

Password: password

And then click [http://152.46.19.28:8080/student_task/list 'Assignments'] to the fixed page.

=='''References'''==
*[https://github.com/expertiza/expertiza Expertiza on GitHub]
*[http://expertiza.ncsu.edu/ The live Expertiza website]
*[http://research.csc.ncsu.edu/efg/expertiza Expertiza project Details]
*[https://www.youtube.com/channel/UCdKXzox7hrWjfOMML6FzTWg Expertiza YouTube Channel]

CSC/ECE 517 Fall 2020 - E2065. Fix view in student task/list page

2020-10-16T06:27:50Z

Rma9: /* Test Repo */ Add test way

=='''Team Members'''==
*Junyan Li jli56@ncsu.edu

*Ruoyun Ma rma9@ncsu.edu

*Xiwen Chen xchen33@ncsu.edu

*Mentor:Saurabh Shingte (svshingt@ncsu.edu)

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

The student_task/list page is the page displayed to a student after logging in into expertiza.

It has mainly two div(s), one to show the upcoming tasks including 2 parts:

* Information about tasks. It shows the projects that need to be completed and how long they are close to the deadline, and marks specific revisions prompts.

* Show the record of each group collaborator(s) for each course.

Another div is to display all the assignments and their information, include Assignment, Course, Topic, Current Stage, Review Grade, Badges, Stage Deadline, Copyright Grants and Make Public.

Original page before modifying showing below, all the courses and all the assignments are displaying in the same table, and badges have own column.

[[File:Orignal.JPG|1000px]]
[[File:Originalcourse.JPG|1000px]]

==='''Problems that need to be fixed'''===

Here are some existing problems and unclear parts of the page：

*'''Problem1''': Consider the cases where a student might be enrolled in assignments from more than one course. In this case, assignments should be grouped by course, with the course name given before the listing of the first assignment.

*'''Problem2''': Remove the column for Review Grade because it makes no sense, change Review Grade to Submission Grade. Show the actual score and show the blue button. If you hover over your mouse at the blue button, should also show the commands about grades.

*'''Problem3''': Delete the badges column, and if the Assignment has a badge, mark it directly next to the assignment name under the assignment column.

*'''Problem4''': There is an unnecessary gap between the two div. It needs to be rearranged to be more beautiful.

=='''Solutions'''==
==='''Problem 1, group the course and display on different tables'''===

Fixing app/views/student_task/list.html.erb

original code of how to display course are showing below
<pre>
<div class="topictable">
<table class="table table-striped" cellpadding="2">
<tr class="taskheader">
<th>Assignment</th>
<th>Course</th>
<th>Topic</th>
<th>Current Stage</th>
<th>Review Grade</th>
<th>Badges</th>
<th>Stage Deadline <img src="/assets/info.png" title="You can change 'Preferred Time Zone' in 'Profile' in the banner."/></th>
<th>Publishing Rights</th>
</tr>
<% @student_tasks.each do |student_task| %>
<% participant = student_task.participant %>
<% if student_task.assignment %>
<tr class="listingRow">

<td><b><%= link_to student_task.assignment.name, :action => 'view', :id => participant %></b></td>

<td><%= student_task.course.try :name %></td>

<% topic_id = SignedUpTeam.topic_id(participant.parent_id, participant.user_id) %>
<% if SignUpTopic.exists?(topic_id) %>
<td><%= SignUpTopic.find(topic_id).try :topic_name %></td>
<% else %>
<td>-</td>
<% end %>

<td>
<% if participant.assignment.link_for_current_stage(topic_id)!= nil && participant.assignment.link_for_current_stage(topic_id).length!=0%>
<%= link_to participant.assignment.current_stage_name(topic_id), participant.assignment.link_for_current_stage(topic_id) %>
<% else %>
<%= participant.assignment.current_stage_name(topic_id) %>
<% end %>
</td>

<td><%= get_review_grade_info(participant) %></td>

<td><%= get_awarded_badges(participant) %></td>

<td><%= student_task.stage_deadline.in_time_zone(session[:user].timezonepref) %></td>

<td align=center><%= participant.permission_granted ? "granted" : "denied" %></td>
</tr>
<% end %>
<% end %>
</table>
</pre>

In order to group the courses, we added a group_by method to find out which courses does this assignment belongs to, and group the assignments that has the same courses name at one table. The modified code is showing below.

<pre>
<% group = @student_tasks.group_by(&:course).each do | course, student_tasks|%>
<% if course%>
<%end %>
<div class="topictable" style="float: right;width: 80%;margin-bottom: 10px; display: inline-block; border: 1px solid #000000">

<% if !student_tasks.first.course %>
<h1>No Course Assigned Yet</h1>
<%else%>
<h1><%=student_tasks.first.course.try :name %></h1>
<%end%>
</pre>

We will print out the course name as each table head, group the assignments, and we take down Course coloum from table content since the course name is already showing as table head. Also, for the assignments that have not assigned to a course, we will print out <q>No Course Assigned Yet</q>.

==='''Problem 2, submission grade display'''===

Fixing app/views/student_task/list.html.erb
app/helpers/student_task_helper.rb

For this problem, first, we change Review Grade to Submission grade, which only need to modify
<pre>
<th>Review Grade</th>
</pre>
to
<pre>
<th>Submission Grade</th>
</pre>
on list.html.erb.

Second, we change how we display the score. Instead of showing a blue button, we added how much scores they got (e.g. 32/40), which make users easier to see what scores they got. We modified get_review_grade_info(participant) function inside of student_task_helper.rb.

Original code is showing below
<pre>
def get_review_grade_info(participant)
info = ''
if participant.try(:review_grade).try(:grade_for_reviewer).nil? ||
participant.try(:review_grade).try(:comment_for_reviewer).nil?
result = "N/A"
else
info = "Score: " + participant.try(:review_grade).try(:grade_for_reviewer).to_s + "/100\n"
info += "Comment: " + participant.try(:review_grade).try(:comment_for_reviewer).to_s
info = truncate(info, length: 1500, omission: '...')
result = "<img src = '/assets/info.png' title = '" + info + "'>"
end
result.html_safe
end
</pre>

In the orignal code, each grade is assigned to /100, which is not correct because not every assignment has 10 reviews (one review count for 10 point). Instead of using /100, we use num_reviews_allowed, it will give us the maximum reviews that each assignments are allowed. Since we need to display the current score on the page, we need an array to carry the current score and display it on the result. The modified code showing below.

<pre>
def get_review_grade_info(participant)
info = ''
if participant.try(:review_grade).try(:grade_for_reviewer).nil? ||
participant.try(:review_grade).try(:comment_for_reviewer).nil?
result = "N/A"
else
score = participant.try(:review_grade).try(:grade_for_reviewer).to_s + "/" + (participant.assignment.num_reviews_allowed*10).to_s
info = "Score: " + participant.try(:review_grade).try(:grade_for_reviewer).to_s + "/" + (participant.assignment.num_reviews_allowed*10).to_s + "\n"
info += "Comment: " + participant.try(:review_grade).try(:comment_for_reviewer).to_s
info = truncate(info, length: 1500, omission: '...')
result = score + "<img src = '/assets/info.png' title = '" + info + "'>"
end
</pre>

==='''Problem 3, badges showing location fixing'''===

Fixing app/views/student_task/list.html.erb

Since not too many assignments are able to get badges, that make badges column barely have contents. Therefore, we display it after the assignment name and delete Badges coloum. If one student gets a badge, it will display a small picture after the badged assignment. Hover over your mouse on it, and it will display the information about this badge.

<pre>

<td><b><%= link_to student_task.assignment.name, :action => 'view', :id => participant %></b><p><%= get_awarded_badges(participant) %></p></td>
</pre>

==='''Problem 4, unnecssary white space'''===
Fixing app/views/student_task/list.html.erb
Our main purpose of this project is to make the student_task/list page looks better. For problem 4, we fixed unnessary white space between two divs. We changed two div's style to style = <q>width:18</q> and style = <q>width:80</q>, so two div will display on the same lines.
<pre>
<div class="taskbox" style="width:18%; display: inline-block; float:left; margin-right: 10px;" >
</pre>

<pre>
<div class="topictable" style="float: right;width: 80%;margin-bottom: 10px; display: inline-block; border: 1px solid #000000">
</pre>

==='''Page Change Display'''===

Page showing right now
[[File:Coursedisplay.PNG|1000px]]

[[File:Differentgroup.JPG|1000px]]

=='''RSpec test'''==
According to the modification of each problem, we write test separately to test whether its function is realized or not.

==='''Test Repo'''===

We deploy this part of the program on VCL to test UI and other functions. The link to the website is as follows:
[http://152.46.19.28:8080 E2065 Repo Link]

Using the following account to log in for testing：

Username: instructor6

Password: password

And then click [http://152.46.19.28:8080/student_task/list 'Assignment'] to the fixed page.

=='''References'''==
*[https://github.com/expertiza/expertiza Expertiza on GitHub]
*[http://expertiza.ncsu.edu/ The live Expertiza website]
*[http://research.csc.ncsu.edu/efg/expertiza Expertiza project Details]
*[https://www.youtube.com/channel/UCdKXzox7hrWjfOMML6FzTWg Expertiza YouTube Channel]

CSC/ECE 517 Fall 2020 - E2065. Fix view in student task/list page

2020-10-16T06:20:54Z

Rma9: /* Test Repo */ Add repo link

=='''Team Members'''==
*Junyan Li jli56@ncsu.edu

*Ruoyun Ma rma9@ncsu.edu

*Xiwen Chen xchen33@ncsu.edu

*Mentor:Saurabh Shingte (svshingt@ncsu.edu)

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

The student_task/list page is the page displayed to a student after logging in into expertiza.

It has mainly two div(s), one to show the upcoming tasks including 2 parts:

* Information about tasks. It shows the projects that need to be completed and how long they are close to the deadline, and marks specific revisions prompts.

* Show the record of each group collaborator(s) for each course.

Another div is to display all the assignments and their information, include Assignment, Course, Topic, Current Stage, Review Grade, Badges, Stage Deadline, Copyright Grants and Make Public.

Original page before modifying showing below

[[File:Orignal.JPG|1000px]]
[[File:Originalcourse.JPG|1000px]]

==='''Problems that need to be fixed'''===

Here are some existing problems and unclear parts of the page：

*Problem1: Consider the cases where a student might be enrolled in assignments from more than one course. In this case, assignments should be grouped by course, with the course name given before the listing of the first assignment.

*Problem2: Remove the column for Review Grade because it makes no sense, change Review Grade to Submission Grade. Show the actual score and show the blue button. If you hover over your mouse at the blue button, should also show the commands about grades.

*Problem3: Delete the badges column, and if the Assignment has a badge, mark it directly next to the assignment name under the assignment column.

*Problem4: There is an unnecessary gap between the two div. It needs to be rearranged to be more beautiful.

=='''Solutions'''==
==='''Problem 1, group the course and display on different tables'''===

Fixing app/views/student_task/list.html.erb

original code of how to display course are showing below
<pre>
<div class="topictable">
<table class="table table-striped" cellpadding="2">
<tr class="taskheader">
<th>Assignment</th>
<th>Course</th>
<th>Topic</th>
<th>Current Stage</th>
<th>Review Grade</th>
<th>Badges</th>
<th>Stage Deadline <img src="/assets/info.png" title="You can change 'Preferred Time Zone' in 'Profile' in the banner."/></th>
<th>Publishing Rights</th>
</tr>
<% @student_tasks.each do |student_task| %>
<% participant = student_task.participant %>
<% if student_task.assignment %>
<tr class="listingRow">

<td><b><%= link_to student_task.assignment.name, :action => 'view', :id => participant %></b></td>

<td><%= student_task.course.try :name %></td>

<% topic_id = SignedUpTeam.topic_id(participant.parent_id, participant.user_id) %>
<% if SignUpTopic.exists?(topic_id) %>
<td><%= SignUpTopic.find(topic_id).try :topic_name %></td>
<% else %>
<td>-</td>
<% end %>

<td>
<% if participant.assignment.link_for_current_stage(topic_id)!= nil && participant.assignment.link_for_current_stage(topic_id).length!=0%>
<%= link_to participant.assignment.current_stage_name(topic_id), participant.assignment.link_for_current_stage(topic_id) %>
<% else %>
<%= participant.assignment.current_stage_name(topic_id) %>
<% end %>
</td>

<td><%= get_review_grade_info(participant) %></td>

<td><%= get_awarded_badges(participant) %></td>

<td><%= student_task.stage_deadline.in_time_zone(session[:user].timezonepref) %></td>

<td align=center><%= participant.permission_granted ? "granted" : "denied" %></td>
</tr>
<% end %>
<% end %>
</table>
</pre>

In order to group the courses, we added a group_by method to find out which courses does this assignment belongs to, and group the assignments that has the same courses name at one table. The modified code is showing below.

<pre>
<% group = @student_tasks.group_by(&:course).each do | course, student_tasks|%>
<% if course%>
<%end %>
<div class="topictable" style="float: right;width: 80%;margin-bottom: 10px; display: inline-block; border: 1px solid #000000">

<% if !student_tasks.first.course %>
<h1>No Course Assigned Yet</h1>
<%else%>
<h1><%=student_tasks.first.course.try :name %></h1>
<%end%>
</pre>

We will print out the course name as each table head, group the assignments, and we take down Course coloum from table content since the course name is already showing as table head. Also, for the assignments that have not assigned to a course, we will print out <q>No Course Assigned Yet</q>.

==='''Problem 2, submission grade display'''===

Fixing app/views/student_task/list.html.erb
app/helpers/student_task_helper.rb

For this problem, first, we change Review Grade to Submission grade, which only need to modify
<pre>
<th>Review Grade</th>
</pre>
to
<pre>
<th>Submission Grade</th>
</pre>
on list.html.erb.

Second, we change how we display the score. Instead of showing a blue button, we added how much scores they got (e.g. 32/40), which make users easier to see what scores they got. We modified get_review_grade_info(participant) function inside of student_task_helper.rb.

Original code is showing below
<pre>
def get_review_grade_info(participant)
info = ''
if participant.try(:review_grade).try(:grade_for_reviewer).nil? ||
participant.try(:review_grade).try(:comment_for_reviewer).nil?
result = "N/A"
else
info = "Score: " + participant.try(:review_grade).try(:grade_for_reviewer).to_s + "/100\n"
info += "Comment: " + participant.try(:review_grade).try(:comment_for_reviewer).to_s
info = truncate(info, length: 1500, omission: '...')
result = "<img src = '/assets/info.png' title = '" + info + "'>"
end
result.html_safe
end
</pre>

In the orignal code, each grade is assigned to /100, which is not correct because not every assignment has 10 reviews (one review count for 10 point). Instead of using /100, we use num_reviews_allowed, it will give us the maximum reviews that each assignments are allowed. Since we need to display the current score on the page, we need an array to carry the current score and display it on the result. The modified code showing below.

<pre>
def get_review_grade_info(participant)
info = ''
if participant.try(:review_grade).try(:grade_for_reviewer).nil? ||
participant.try(:review_grade).try(:comment_for_reviewer).nil?
result = "N/A"
else
score = participant.try(:review_grade).try(:grade_for_reviewer).to_s + "/" + (participant.assignment.num_reviews_allowed*10).to_s
info = "Score: " + participant.try(:review_grade).try(:grade_for_reviewer).to_s + "/" + (participant.assignment.num_reviews_allowed*10).to_s + "\n"
info += "Comment: " + participant.try(:review_grade).try(:comment_for_reviewer).to_s
info = truncate(info, length: 1500, omission: '...')
result = score + "<img src = '/assets/info.png' title = '" + info + "'>"
end
</pre>

==='''Problem 3, badges showing location fixing'''===

Fixing app/views/student_task/list.html.erb

Since not too many assignments are able to get badges, that make badges column barely have contents. Therefore, we display it after the assignment name and delete Badges coloum. If one student gets a badge, it will display a small picture after the badged assignment. Hover over your mouse on it, and it will display the information about this badge.

<pre>

<td><b><%= link_to student_task.assignment.name, :action => 'view', :id => participant %></b><p><%= get_awarded_badges(participant) %></p></td>
</pre>

==='''Problem 4, unnecssary white space'''===
Fixing app/views/student_task/list.html.erb
Our main purpose of this project is to make the student_task/list page looks better. For problem 4, we fixed unnessary white space between two divs. We changed two div's style to style = <q>width:18</q> and style = <q>width:80</q>, so two div will display on the same lines.
<pre>
<div class="taskbox" style="width:18%; display: inline-block; float:left; margin-right: 10px;" >
</pre>

<pre>
<div class="topictable" style="float: right;width: 80%;margin-bottom: 10px; display: inline-block; border: 1px solid #000000">
</pre>

==='''Page Change Display'''===

Page showing right now
[[File:Coursedisplay.PNG|1000px]]

[[File:Differentgroup.JPG|1000px]]

=='''RSpec test'''==
According to the modification of each problem, we write test separately to test whether its function is realized or not.

==='''Test Repo'''===
We deploy this part of the program on VCL to test UI and other functions. The link to the website is as follows:
[http://152.46.19.28:8080 E2065 Repo Link]
Using the following account to log in for testing：
Username: instructor6
Password: password

=='''References'''==
*[https://github.com/expertiza/expertiza Expertiza on GitHub]
*[http://expertiza.ncsu.edu/ The live Expertiza website]
*[http://research.csc.ncsu.edu/efg/expertiza Expertiza project Details]
*[https://www.youtube.com/channel/UCdKXzox7hrWjfOMML6FzTWg Expertiza YouTube Channel]

CSC/ECE 517 Fall 2020 - E2065. Fix view in student task/list page

2020-10-12T08:13:11Z

Rma9: Add test repo and edit reference

==E2065. Fix view in student_task/list page==

This page provides a description of the Expertiza based OSS project.

__TOC__

===Team Members===
*Junyan Li jli56@ncsu.edu
*Ruoyun Ma rma9@ncsu.edu
*Xiwen Chen xchen33@ncsu.edu

*Mentor:Saurabh Shingte (svshingt@ncsu.edu)
=== Problem Statement===
=====Background=====

The student_task/list page is the page displayed to a student after logging in into expertiza.
It has mainly two div(s), one to show the upcoming tasks including 2 parts:
* Information about tasks. It shows the projects that need to be completed and how long they are close to the deadline, and marks specific revisions prompts.
* Show the record of each group collaborator(s) for each course.
Another div is to display all the assignments and their information, include Assignment, Course, Topic, Current Stage, Review Grade, Badges, Stage Deadline, Copyright Grants and Make Public.

[for partner：Adding picture about page]
=====Problems that need to be fixed=====
Here are some existing problems and unclear parts of the page：

Problem1: Consider the cases where a student might be enrolled in assignments from more than one course. In this case, assignments should be grouped by course, with the course name given before the listing of the first assignment.
Problem2: Remove the column for Review Grade because it makes no sense.
Problem3: Delete the badges column, and if the Assignment has a badge, mark it directly next to the assignment name under the assignment column.
Problem4: There is an unnecessary gap between the two div. It needs to be rearranged to be more beautiful.

===Solutions===

（for partners：For every prblem，write out the part of the added code, that is, the effect before and after the comparison. Adding pictures.）

=====RSpec test=====
According to the modification of each problem, we write test separately to test whether its function is realized or not.

===Test Repo===
We deploy this part of the program on VCL to test UI and other functions. The link to the website is as follows:
（———website———）
Using the following account to log in for testing：
（———account and password———）

===References===
*[https://github.com/expertiza/expertiza Expertiza on GitHub]
*[http://expertiza.ncsu.edu/ The live Expertiza website]
*[http://research.csc.ncsu.edu/efg/expertiza Expertiza project Details]
*[https://www.youtube.com/channel/UCdKXzox7hrWjfOMML6FzTWg Expertiza YouTube Channel]

CSC/ECE 517 Fall 2020 - E2065. Fix view in student task/list page

2020-10-12T08:04:50Z

Rma9: /* Solutions */ Raise the level of solutions

CSC/ECE 517 Fall 2020 - E2065. Fix view in student task/list page

2020-10-12T08:02:41Z

Rma9: Add frames, and edit Problem Statement

==E2065. Fix view in student_task/list page==

This page provides a description of the Expertiza based OSS project.

__TOC__

===Team Members===
*Junyan Li jli56@ncsu.edu
*Ruoyun Ma rma9@ncsu.edu
*Xiwen Chen xchen33@ncsu.edu

*Mentor:Saurabh Shingte (svshingt@ncsu.edu)
=== Problem Statement===
=====Background=====

The student_task/list page is the page displayed to a student after logging in into expertiza.
It has mainly two div(s), one to show the upcoming tasks including 2 parts:
* Information about tasks. It shows the projects that need to be completed and how long they are close to the deadline, and marks specific revisions prompts.
* Show the record of each group collaborator(s) for each course.
Another div is to display all the assignments and their information, include Assignment, Course, Topic, Current Stage, Review Grade, Badges, Stage Deadline, Copyright Grants and Make Public.

[for partner：Adding picture about page]
=====Problems that need to be fixed=====
Here are some existing problems and unclear parts of the page：

Problem1: Consider the cases where a student might be enrolled in assignments from more than one course. In this case, assignments should be grouped by course, with the course name given before the listing of the first assignment.
Problem2: Remove the column for Review Grade because it makes no sense.
Problem3: Delete the badges column, and if the Assignment has a badge, mark it directly next to the assignment name under the assignment column.
Problem4: There is an unnecessary gap between the two div. It needs to be rearranged to be more beautiful.

=====Solutions=====

（for partners：For every prblem，write out the part of the added code, that is, the effect before and after the comparison. Adding pictures.）

=====RSpec test=====
According to the modification of each problem, we write test separately to test whether its function is realized or not.

===References===

CSC/ECE 517 Fall 2020

2020-10-12T07:06:52Z

Rma9: Adding new page of E2065

* [[Dummy URL]]
* [[Dummy Url2]]
* [[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 - E2064. Refactor reputation_web_service_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]]