Expertiza_Wiki - User contributions [en]

CSC/ECE 517 Fall 2018/E1855 let course staff as well as students do reviews

2018-12-07T23:33:20Z

Rkovilk: /* Team */

== '''Introduction''' ==

The way Expertiza is set up right now is that only peers can review your work. However, there are cases when the course staff (Instructor/ TAs) would want to submit reviews as well. This project aims to implement this feature by allowing course staff to review the project on the same metrics as other students who review the project.

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

The current system does not allow instructors to submit reviews of student work. We will work upon the feature which will let them review using the same review form that students use to do reviews.

=== Current scenario ===

This is how some of the pages we are concerned with, currently look.

==== Submissions page for an assignment in Instructor View ====

[[File: Submissions_instr.jpeg | center]]

==== A typical Scores table in a Student View ====

[[File: Grades_view_team_current.png | center]]

== '''Proposed Solutions and Implementation''' ==

Following changes will be made to let staff perform reviews as well:

'''Step 1: Add a way for the instructors to perform a review.'''

We are planning to implement links to ''Begin review'', ''Edit review'','' View review'' and ''Submit review'' in the assignment submissions view.
When the instructor/TA reviews a work for the first time, he/she is added as a participant and a review response mapping is created.

Files edited:
* '''View: ''' ''app/views/assignments/list_submissions.html.erb'' - To add links in the instructor view
* '''Controller: ''' ''app/controllers/review_mapping_controller.rb'' - Method: add_instructor_as_reviewer

In the second case, we can see a 'Begin review' link. This is the initial state when instructor review has not been added to the submission.
Once the instructor adds a review and submits it, we can see the 'View review' link. In case he just saves the review, an 'Edit review' link will appear.
If the review deadline of one round is passed, the 'Edit review' link becomes 'Update review' link. This follows in line with what the student sees while performing a review. Similarly, just like students instructor would not able to edit or update the review once submitted.

[[File:Ins_TA_Review.png]]

'''Step 2: Add the instructor review in ''Your Scores'' table in case he has reviewed your work. Provide an icon to highlight the special nature of an instructors review.'''

Files edited:
* '''Assets: ''' ''app/assets/stylesheets/grades.scss'' - Icon to make an instructor's review distinct from other reviews
* '''View: ''' ''app/views/grades/view_team.html.erb'' - To modify the "Your scores" page to include an icon next to the peer review score indicating that the instructor's score is not included in the final peer review score.
* '''Models: '''
** ''app/models/answer.rb'' - Method: compute_scores | Modification in logic to ensure instructor review scores are not counted in the overall score of the student.
** ''app/models/vm_question_response_score_cell.rb'' - Included a new variable called 'is_instructor_review' to identify an instructor review
** ''app/models/vm_question_response_row.rb'' - Change in average_score_for_row method to not include an instructor review score
** ''app/models/vm_question_response.rb'' - Modified the add_answer method to include the is_instructor_review to each row_score object

A student should be able to make out if an instructor has reviewed his/his team's work. In case the instructor performs a review on the team's work, there will be an icon next to the instructor's review along with explicitly stating that it is an 'Instructor review'.
The average peer review score for the team has been modified to exclude the instructor's scores. Same has been taken into account for the average score calculated for each row.

[[File:Score_hover.png]]

Like shown in the above picture we can see a info button on which if we hover the text is shown.

Possible icons :
[[File:Instuctor.jpg]] [[File:Instructor1.jpg]]

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

'''Features testing:''' Many of our changes are reflected on views (user interface). Following is the list of tests that we will conduct with rspec/capybara.

# it "should let instructor/TAs perform a review for the submission of latest finished round if instructor/TAs has not started a review for the submission yet"
# it "should let instructor/TAs save a review"
# it "should let instructor/TAs review a previously saved review"
# it "should let instructor/TAs edit a previously saved review"
# it "should allow instructor/TAs perform a review after the deadline for reviewing has passed"

'''More testing:'''

# it "should let instructor/TAs update a review for the submission of latest finished round if instructor/TAs performed and saved a review for the previous round"
# it "should show "Instructor review" when a student views feedback on his/her submission if an instructor/TA has reviewed his/his team's work"
# it "should exclude the instructor's/TA's review score when calculating the average peer review score for the team"
# it "should exclude the instructor's/TA's review score when calculating the average score for each question in the review"

== '''Team''' ==
'''Members : '''
Harsh Shah,
Prachi Gupta,
Ramkumaar Kovil Kanthadai,
Raveena D'Costa.

'''Mentor :''' Dr.Edward Gehringer

== '''References''' ==

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

Pull Request
* https://github.com/expertiza/expertiza/pull/1304

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

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

CSC/ECE 517 Fall 2018/E1855 let course staff as well as students do reviews

2018-12-07T23:32:59Z

Rkovilk: /* Team */

== '''Introduction''' ==

The way Expertiza is set up right now is that only peers can review your work. However, there are cases when the course staff (Instructor/ TAs) would want to submit reviews as well. This project aims to implement this feature by allowing course staff to review the project on the same metrics as other students who review the project.

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

The current system does not allow instructors to submit reviews of student work. We will work upon the feature which will let them review using the same review form that students use to do reviews.

=== Current scenario ===

This is how some of the pages we are concerned with, currently look.

==== Submissions page for an assignment in Instructor View ====

[[File: Submissions_instr.jpeg | center]]

==== A typical Scores table in a Student View ====

[[File: Grades_view_team_current.png | center]]

== '''Proposed Solutions and Implementation''' ==

Following changes will be made to let staff perform reviews as well:

'''Step 1: Add a way for the instructors to perform a review.'''

We are planning to implement links to ''Begin review'', ''Edit review'','' View review'' and ''Submit review'' in the assignment submissions view.
When the instructor/TA reviews a work for the first time, he/she is added as a participant and a review response mapping is created.

Files edited:
* '''View: ''' ''app/views/assignments/list_submissions.html.erb'' - To add links in the instructor view
* '''Controller: ''' ''app/controllers/review_mapping_controller.rb'' - Method: add_instructor_as_reviewer

In the second case, we can see a 'Begin review' link. This is the initial state when instructor review has not been added to the submission.
Once the instructor adds a review and submits it, we can see the 'View review' link. In case he just saves the review, an 'Edit review' link will appear.
If the review deadline of one round is passed, the 'Edit review' link becomes 'Update review' link. This follows in line with what the student sees while performing a review. Similarly, just like students instructor would not able to edit or update the review once submitted.

[[File:Ins_TA_Review.png]]

'''Step 2: Add the instructor review in ''Your Scores'' table in case he has reviewed your work. Provide an icon to highlight the special nature of an instructors review.'''

Files edited:
* '''Assets: ''' ''app/assets/stylesheets/grades.scss'' - Icon to make an instructor's review distinct from other reviews
* '''View: ''' ''app/views/grades/view_team.html.erb'' - To modify the "Your scores" page to include an icon next to the peer review score indicating that the instructor's score is not included in the final peer review score.
* '''Models: '''
** ''app/models/answer.rb'' - Method: compute_scores | Modification in logic to ensure instructor review scores are not counted in the overall score of the student.
** ''app/models/vm_question_response_score_cell.rb'' - Included a new variable called 'is_instructor_review' to identify an instructor review
** ''app/models/vm_question_response_row.rb'' - Change in average_score_for_row method to not include an instructor review score
** ''app/models/vm_question_response.rb'' - Modified the add_answer method to include the is_instructor_review to each row_score object

A student should be able to make out if an instructor has reviewed his/his team's work. In case the instructor performs a review on the team's work, there will be an icon next to the instructor's review along with explicitly stating that it is an 'Instructor review'.
The average peer review score for the team has been modified to exclude the instructor's scores. Same has been taken into account for the average score calculated for each row.

[[File:Score_hover.png]]

Like shown in the above picture we can see a info button on which if we hover the text is shown.

Possible icons :
[[File:Instuctor.jpg]] [[File:Instructor1.jpg]]

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

'''Features testing:''' Many of our changes are reflected on views (user interface). Following is the list of tests that we will conduct with rspec/capybara.

# it "should let instructor/TAs perform a review for the submission of latest finished round if instructor/TAs has not started a review for the submission yet"
# it "should let instructor/TAs save a review"
# it "should let instructor/TAs review a previously saved review"
# it "should let instructor/TAs edit a previously saved review"
# it "should allow instructor/TAs perform a review after the deadline for reviewing has passed"

'''More testing:'''

# it "should let instructor/TAs update a review for the submission of latest finished round if instructor/TAs performed and saved a review for the previous round"
# it "should show "Instructor review" when a student views feedback on his/her submission if an instructor/TA has reviewed his/his team's work"
# it "should exclude the instructor's/TA's review score when calculating the average peer review score for the team"
# it "should exclude the instructor's/TA's review score when calculating the average score for each question in the review"

== '''Team''' ==
'''Members :'''

Harsh Shah,
Prachi Gupta,
Ramkumaar Kovil Kanthadai,
Raveena D'Costa.

'''Mentor :''' Dr.Edward Gehringer

== '''References''' ==

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

Pull Request
* https://github.com/expertiza/expertiza/pull/1304

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

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

CSC/ECE 517 Fall 2018/E1855 let course staff as well as students do reviews

2018-12-07T23:31:58Z

Rkovilk: /* Team */

== '''Introduction''' ==

The way Expertiza is set up right now is that only peers can review your work. However, there are cases when the course staff (Instructor/ TAs) would want to submit reviews as well. This project aims to implement this feature by allowing course staff to review the project on the same metrics as other students who review the project.

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

The current system does not allow instructors to submit reviews of student work. We will work upon the feature which will let them review using the same review form that students use to do reviews.

=== Current scenario ===

This is how some of the pages we are concerned with, currently look.

==== Submissions page for an assignment in Instructor View ====

[[File: Submissions_instr.jpeg | center]]

==== A typical Scores table in a Student View ====

[[File: Grades_view_team_current.png | center]]

== '''Proposed Solutions and Implementation''' ==

Following changes will be made to let staff perform reviews as well:

'''Step 1: Add a way for the instructors to perform a review.'''

We are planning to implement links to ''Begin review'', ''Edit review'','' View review'' and ''Submit review'' in the assignment submissions view.
When the instructor/TA reviews a work for the first time, he/she is added as a participant and a review response mapping is created.

Files edited:
* '''View: ''' ''app/views/assignments/list_submissions.html.erb'' - To add links in the instructor view
* '''Controller: ''' ''app/controllers/review_mapping_controller.rb'' - Method: add_instructor_as_reviewer

In the second case, we can see a 'Begin review' link. This is the initial state when instructor review has not been added to the submission.
Once the instructor adds a review and submits it, we can see the 'View review' link. In case he just saves the review, an 'Edit review' link will appear.
If the review deadline of one round is passed, the 'Edit review' link becomes 'Update review' link. This follows in line with what the student sees while performing a review. Similarly, just like students instructor would not able to edit or update the review once submitted.

[[File:Ins_TA_Review.png]]

'''Step 2: Add the instructor review in ''Your Scores'' table in case he has reviewed your work. Provide an icon to highlight the special nature of an instructors review.'''

Files edited:
* '''Assets: ''' ''app/assets/stylesheets/grades.scss'' - Icon to make an instructor's review distinct from other reviews
* '''View: ''' ''app/views/grades/view_team.html.erb'' - To modify the "Your scores" page to include an icon next to the peer review score indicating that the instructor's score is not included in the final peer review score.
* '''Models: '''
** ''app/models/answer.rb'' - Method: compute_scores | Modification in logic to ensure instructor review scores are not counted in the overall score of the student.
** ''app/models/vm_question_response_score_cell.rb'' - Included a new variable called 'is_instructor_review' to identify an instructor review
** ''app/models/vm_question_response_row.rb'' - Change in average_score_for_row method to not include an instructor review score
** ''app/models/vm_question_response.rb'' - Modified the add_answer method to include the is_instructor_review to each row_score object

A student should be able to make out if an instructor has reviewed his/his team's work. In case the instructor performs a review on the team's work, there will be an icon next to the instructor's review along with explicitly stating that it is an 'Instructor review'.
The average peer review score for the team has been modified to exclude the instructor's scores. Same has been taken into account for the average score calculated for each row.

[[File:Score_hover.png]]

Like shown in the above picture we can see a info button on which if we hover the text is shown.

Possible icons :
[[File:Instuctor.jpg]] [[File:Instructor1.jpg]]

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

'''Features testing:''' Many of our changes are reflected on views (user interface). Following is the list of tests that we will conduct with rspec/capybara.

# it "should let instructor/TAs perform a review for the submission of latest finished round if instructor/TAs has not started a review for the submission yet"
# it "should let instructor/TAs save a review"
# it "should let instructor/TAs review a previously saved review"
# it "should let instructor/TAs edit a previously saved review"
# it "should allow instructor/TAs perform a review after the deadline for reviewing has passed"

'''More testing:'''

# it "should let instructor/TAs update a review for the submission of latest finished round if instructor/TAs performed and saved a review for the previous round"
# it "should show "Instructor review" when a student views feedback on his/her submission if an instructor/TA has reviewed his/his team's work"
# it "should exclude the instructor's/TA's review score when calculating the average peer review score for the team"
# it "should exclude the instructor's/TA's review score when calculating the average score for each question in the review"

== '''Team''' ==
Members :

Harsh Shah
Prachi Gupta
Ramkumaar Kovil Kanthadai
Raveena D'Costa

Mentor : Dr.Edward Gehringer

== '''References''' ==

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

Pull Request
* https://github.com/expertiza/expertiza/pull/1304

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

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

CSC/ECE 517 Fall 2018/E1855 let course staff as well as students do reviews

2018-12-07T23:31:43Z

Rkovilk: /* Team */

== '''Introduction''' ==

The way Expertiza is set up right now is that only peers can review your work. However, there are cases when the course staff (Instructor/ TAs) would want to submit reviews as well. This project aims to implement this feature by allowing course staff to review the project on the same metrics as other students who review the project.

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

The current system does not allow instructors to submit reviews of student work. We will work upon the feature which will let them review using the same review form that students use to do reviews.

=== Current scenario ===

This is how some of the pages we are concerned with, currently look.

==== Submissions page for an assignment in Instructor View ====

[[File: Submissions_instr.jpeg | center]]

==== A typical Scores table in a Student View ====

[[File: Grades_view_team_current.png | center]]

== '''Proposed Solutions and Implementation''' ==

Following changes will be made to let staff perform reviews as well:

'''Step 1: Add a way for the instructors to perform a review.'''

We are planning to implement links to ''Begin review'', ''Edit review'','' View review'' and ''Submit review'' in the assignment submissions view.
When the instructor/TA reviews a work for the first time, he/she is added as a participant and a review response mapping is created.

Files edited:
* '''View: ''' ''app/views/assignments/list_submissions.html.erb'' - To add links in the instructor view
* '''Controller: ''' ''app/controllers/review_mapping_controller.rb'' - Method: add_instructor_as_reviewer

In the second case, we can see a 'Begin review' link. This is the initial state when instructor review has not been added to the submission.
Once the instructor adds a review and submits it, we can see the 'View review' link. In case he just saves the review, an 'Edit review' link will appear.
If the review deadline of one round is passed, the 'Edit review' link becomes 'Update review' link. This follows in line with what the student sees while performing a review. Similarly, just like students instructor would not able to edit or update the review once submitted.

[[File:Ins_TA_Review.png]]

'''Step 2: Add the instructor review in ''Your Scores'' table in case he has reviewed your work. Provide an icon to highlight the special nature of an instructors review.'''

Files edited:
* '''Assets: ''' ''app/assets/stylesheets/grades.scss'' - Icon to make an instructor's review distinct from other reviews
* '''View: ''' ''app/views/grades/view_team.html.erb'' - To modify the "Your scores" page to include an icon next to the peer review score indicating that the instructor's score is not included in the final peer review score.
* '''Models: '''
** ''app/models/answer.rb'' - Method: compute_scores | Modification in logic to ensure instructor review scores are not counted in the overall score of the student.
** ''app/models/vm_question_response_score_cell.rb'' - Included a new variable called 'is_instructor_review' to identify an instructor review
** ''app/models/vm_question_response_row.rb'' - Change in average_score_for_row method to not include an instructor review score
** ''app/models/vm_question_response.rb'' - Modified the add_answer method to include the is_instructor_review to each row_score object

A student should be able to make out if an instructor has reviewed his/his team's work. In case the instructor performs a review on the team's work, there will be an icon next to the instructor's review along with explicitly stating that it is an 'Instructor review'.
The average peer review score for the team has been modified to exclude the instructor's scores. Same has been taken into account for the average score calculated for each row.

[[File:Score_hover.png]]

Like shown in the above picture we can see a info button on which if we hover the text is shown.

Possible icons :
[[File:Instuctor.jpg]] [[File:Instructor1.jpg]]

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

'''Features testing:''' Many of our changes are reflected on views (user interface). Following is the list of tests that we will conduct with rspec/capybara.

# it "should let instructor/TAs perform a review for the submission of latest finished round if instructor/TAs has not started a review for the submission yet"
# it "should let instructor/TAs save a review"
# it "should let instructor/TAs review a previously saved review"
# it "should let instructor/TAs edit a previously saved review"
# it "should allow instructor/TAs perform a review after the deadline for reviewing has passed"

'''More testing:'''

# it "should let instructor/TAs update a review for the submission of latest finished round if instructor/TAs performed and saved a review for the previous round"
# it "should show "Instructor review" when a student views feedback on his/her submission if an instructor/TA has reviewed his/his team's work"
# it "should exclude the instructor's/TA's review score when calculating the average peer review score for the team"
# it "should exclude the instructor's/TA's review score when calculating the average score for each question in the review"

== '''Team''' ==
Members :

Harsh Shah

Prachi Gupta

Ramkumaar Kovil Kanthadai

Raveena D'Costa

Mentor : Dr.Edward Gehringer

== '''References''' ==

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

Pull Request
* https://github.com/expertiza/expertiza/pull/1304

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

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

CSC/ECE 517 Fall 2018/E1855 let course staff as well as students do reviews

2018-12-07T23:31:20Z

Rkovilk: /* References */

== '''Introduction''' ==

The way Expertiza is set up right now is that only peers can review your work. However, there are cases when the course staff (Instructor/ TAs) would want to submit reviews as well. This project aims to implement this feature by allowing course staff to review the project on the same metrics as other students who review the project.

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

The current system does not allow instructors to submit reviews of student work. We will work upon the feature which will let them review using the same review form that students use to do reviews.

=== Current scenario ===

This is how some of the pages we are concerned with, currently look.

==== Submissions page for an assignment in Instructor View ====

[[File: Submissions_instr.jpeg | center]]

==== A typical Scores table in a Student View ====

[[File: Grades_view_team_current.png | center]]

== '''Proposed Solutions and Implementation''' ==

Following changes will be made to let staff perform reviews as well:

'''Step 1: Add a way for the instructors to perform a review.'''

We are planning to implement links to ''Begin review'', ''Edit review'','' View review'' and ''Submit review'' in the assignment submissions view.
When the instructor/TA reviews a work for the first time, he/she is added as a participant and a review response mapping is created.

Files edited:
* '''View: ''' ''app/views/assignments/list_submissions.html.erb'' - To add links in the instructor view
* '''Controller: ''' ''app/controllers/review_mapping_controller.rb'' - Method: add_instructor_as_reviewer

In the second case, we can see a 'Begin review' link. This is the initial state when instructor review has not been added to the submission.
Once the instructor adds a review and submits it, we can see the 'View review' link. In case he just saves the review, an 'Edit review' link will appear.
If the review deadline of one round is passed, the 'Edit review' link becomes 'Update review' link. This follows in line with what the student sees while performing a review. Similarly, just like students instructor would not able to edit or update the review once submitted.

[[File:Ins_TA_Review.png]]

'''Step 2: Add the instructor review in ''Your Scores'' table in case he has reviewed your work. Provide an icon to highlight the special nature of an instructors review.'''

Files edited:
* '''Assets: ''' ''app/assets/stylesheets/grades.scss'' - Icon to make an instructor's review distinct from other reviews
* '''View: ''' ''app/views/grades/view_team.html.erb'' - To modify the "Your scores" page to include an icon next to the peer review score indicating that the instructor's score is not included in the final peer review score.
* '''Models: '''
** ''app/models/answer.rb'' - Method: compute_scores | Modification in logic to ensure instructor review scores are not counted in the overall score of the student.
** ''app/models/vm_question_response_score_cell.rb'' - Included a new variable called 'is_instructor_review' to identify an instructor review
** ''app/models/vm_question_response_row.rb'' - Change in average_score_for_row method to not include an instructor review score
** ''app/models/vm_question_response.rb'' - Modified the add_answer method to include the is_instructor_review to each row_score object

A student should be able to make out if an instructor has reviewed his/his team's work. In case the instructor performs a review on the team's work, there will be an icon next to the instructor's review along with explicitly stating that it is an 'Instructor review'.
The average peer review score for the team has been modified to exclude the instructor's scores. Same has been taken into account for the average score calculated for each row.

[[File:Score_hover.png]]

Like shown in the above picture we can see a info button on which if we hover the text is shown.

Possible icons :
[[File:Instuctor.jpg]] [[File:Instructor1.jpg]]

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

'''Features testing:''' Many of our changes are reflected on views (user interface). Following is the list of tests that we will conduct with rspec/capybara.

# it "should let instructor/TAs perform a review for the submission of latest finished round if instructor/TAs has not started a review for the submission yet"
# it "should let instructor/TAs save a review"
# it "should let instructor/TAs review a previously saved review"
# it "should let instructor/TAs edit a previously saved review"
# it "should allow instructor/TAs perform a review after the deadline for reviewing has passed"

'''More testing:'''

# it "should let instructor/TAs update a review for the submission of latest finished round if instructor/TAs performed and saved a review for the previous round"
# it "should show "Instructor review" when a student views feedback on his/her submission if an instructor/TA has reviewed his/his team's work"
# it "should exclude the instructor's/TA's review score when calculating the average peer review score for the team"
# it "should exclude the instructor's/TA's review score when calculating the average score for each question in the review"

== '''Team''' ==
Members :
Harsh Shah
Prachi Gupta
Ramkumaar Kovil Kanthadai
Raveena D'Costa

Mentor : Dr.Edward Gehringer

== '''References''' ==

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

Pull Request
* https://github.com/expertiza/expertiza/pull/1304

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

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

CSC/ECE 517 Fall 2018/E1855 let course staff as well as students do reviews

2018-12-07T23:25:44Z

Rkovilk: /* Proposed Solutions and Implementation */

== '''Introduction''' ==

The way Expertiza is set up right now is that only peers can review your work. However, there are cases when the course staff (Instructor/ TAs) would want to submit reviews as well. This project aims to implement this feature by allowing course staff to review the project on the same metrics as other students who review the project.

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

The current system does not allow instructors to submit reviews of student work. We will work upon the feature which will let them review using the same review form that students use to do reviews.

=== Current scenario ===

This is how some of the pages we are concerned with, currently look.

==== Submissions page for an assignment in Instructor View ====

[[File: Submissions_instr.jpeg | center]]

==== A typical Scores table in a Student View ====

[[File: Grades_view_team_current.png | center]]

== '''Proposed Solutions and Implementation''' ==

Following changes will be made to let staff perform reviews as well:

'''Step 1: Add a way for the instructors to perform a review.'''

We are planning to implement links to ''Begin review'', ''Edit review'','' View review'' and ''Submit review'' in the assignment submissions view.
When the instructor/TA reviews a work for the first time, he/she is added as a participant and a review response mapping is created.

Files edited:
* '''View: ''' ''app/views/assignments/list_submissions.html.erb'' - To add links in the instructor view
* '''Controller: ''' ''app/controllers/review_mapping_controller.rb'' - Method: add_instructor_as_reviewer

In the second case, we can see a 'Begin review' link. This is the initial state when instructor review has not been added to the submission.
Once the instructor adds a review and submits it, we can see the 'View review' link. In case he just saves the review, an 'Edit review' link will appear.
If the review deadline of one round is passed, the 'Edit review' link becomes 'Update review' link. This follows in line with what the student sees while performing a review. Similarly, just like students instructor would not able to edit or update the review once submitted.

[[File:Ins_TA_Review.png]]

'''Step 2: Add the instructor review in ''Your Scores'' table in case he has reviewed your work. Provide an icon to highlight the special nature of an instructors review.'''

Files edited:
* '''Assets: ''' ''app/assets/stylesheets/grades.scss'' - Icon to make an instructor's review distinct from other reviews
* '''View: ''' ''app/views/grades/view_team.html.erb'' - To modify the "Your scores" page to include an icon next to the peer review score indicating that the instructor's score is not included in the final peer review score.
* '''Models: '''
** ''app/models/answer.rb'' - Method: compute_scores | Modification in logic to ensure instructor review scores are not counted in the overall score of the student.
** ''app/models/vm_question_response_score_cell.rb'' - Included a new variable called 'is_instructor_review' to identify an instructor review
** ''app/models/vm_question_response_row.rb'' - Change in average_score_for_row method to not include an instructor review score
** ''app/models/vm_question_response.rb'' - Modified the add_answer method to include the is_instructor_review to each row_score object

A student should be able to make out if an instructor has reviewed his/his team's work. In case the instructor performs a review on the team's work, there will be an icon next to the instructor's review along with explicitly stating that it is an 'Instructor review'.
The average peer review score for the team has been modified to exclude the instructor's scores. Same has been taken into account for the average score calculated for each row.

[[File:Score_hover.png]]

Like shown in the above picture we can see a info button on which if we hover the text is shown.

Possible icons :
[[File:Instuctor.jpg]] [[File:Instructor1.jpg]]

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

'''Features testing:''' Many of our changes are reflected on views (user interface). Following is the list of tests that we will conduct with rspec/capybara.

# it "should let instructor/TAs perform a review for the submission of latest finished round if instructor/TAs has not started a review for the submission yet"
# it "should let instructor/TAs save a review"
# it "should let instructor/TAs review a previously saved review"
# it "should let instructor/TAs edit a previously saved review"
# it "should allow instructor/TAs perform a review after the deadline for reviewing has passed"

'''More testing:'''

# it "should let instructor/TAs update a review for the submission of latest finished round if instructor/TAs performed and saved a review for the previous round"
# it "should show "Instructor review" when a student views feedback on his/her submission if an instructor/TA has reviewed his/his team's work"
# it "should exclude the instructor's/TA's review score when calculating the average peer review score for the team"
# it "should exclude the instructor's/TA's review score when calculating the average score for each question in the review"

== '''References''' ==

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

Pull Request
* https://github.com/expertiza/expertiza/pull/1304

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

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

CSC/ECE 517 Fall 2018/E1855 let course staff as well as students do reviews

2018-12-07T23:24:33Z

Rkovilk: /* Proposed Solutions and Implementation */

== '''Introduction''' ==

The way Expertiza is set up right now is that only peers can review your work. However, there are cases when the course staff (Instructor/ TAs) would want to submit reviews as well. This project aims to implement this feature by allowing course staff to review the project on the same metrics as other students who review the project.

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

The current system does not allow instructors to submit reviews of student work. We will work upon the feature which will let them review using the same review form that students use to do reviews.

=== Current scenario ===

This is how some of the pages we are concerned with, currently look.

==== Submissions page for an assignment in Instructor View ====

[[File: Submissions_instr.jpeg | center]]

==== A typical Scores table in a Student View ====

[[File: Grades_view_team_current.png | center]]

== '''Proposed Solutions and Implementation''' ==

Following changes will be made to let staff perform reviews as well:

'''Step 1: Add a way for the instructors to perform a review.'''

We are planning to implement links to ''Begin review'', ''Edit review'','' View review'' and ''Submit review'' in the assignment submissions view.
When the instructor/TA reviews a work for the first time, he/she is added as a participant and a review response mapping is created.

Files edited:
* '''View: ''' ''app/views/assignments/list_submissions.html.erb'' - To add links in the instructor view
* '''Controller: ''' ''app/controllers/review_mapping_controller.rb'' - Method: add_instructor_as_reviewer

In the second case, we can see a 'Begin review' link. This is the initial state when instructor review has not been added to the submission.
Once the instructor adds a review and submits it, we can see the 'View review' link. In case he just saves the review, an 'Edit review' link will appear.
If the review deadline of one round is passed, the 'Edit review' link becomes 'Update review' link. This follows in line with what the student sees while performing a review. Similarly, just like students instructor would not able to edit or update the review once submitted.

[[File:Ins_TA_Review.png]]

'''Step 2: Add the instructor review in ''Your Scores'' table in case he has reviewed your work. Provide an icon to highlight the special nature of an instructors review.'''

Files edited:
* '''Assets: ''' ''app/assets/stylesheets/grades.scss'' - Icon to make an instructor's review distinct from other reviews
* '''View: ''' ''app/views/grades/view_team.html.erb'' - To modify the "Your scores" page to include an icon next to the peer review score indicating that the instructor's score is not included in the final peer review score.
* '''Models: '''
** ''app/models/answer.rb'' - Method: compute_scores | Modification in logic to ensure instructor review scores are not counted in the overall score of the student.
** ''app/models/vm_question_response_score_cell.rb'' - Included a new variable called 'is_instructor_review' to identify an instructor review
** ''app/models/vm_question_response_row.rb'' - Change in average_score_for_row method to not include an instructor review score
** ''app/models/vm_question_response.rb'' - Modified the add_answer method to include the is_instructor_review to each row_score object

A student should be able to make out if an instructor has reviewed his/his team's work. In case the instructor performs a review on the team's work, there will be an icon next to the instructor's review along with explicitly stating that it is an 'Instructor review'.
The average peer review score for the team has been modified to exclude the instructor's scores. Same has been taken into account for the average score calculated for each row.

[[File:Score_hover.png]]

Possible icons :
[[File:Instuctor.jpg]] [[File:Instructor1.jpg]]

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

'''Features testing:''' Many of our changes are reflected on views (user interface). Following is the list of tests that we will conduct with rspec/capybara.

# it "should let instructor/TAs perform a review for the submission of latest finished round if instructor/TAs has not started a review for the submission yet"
# it "should let instructor/TAs save a review"
# it "should let instructor/TAs review a previously saved review"
# it "should let instructor/TAs edit a previously saved review"
# it "should allow instructor/TAs perform a review after the deadline for reviewing has passed"

'''More testing:'''

# it "should let instructor/TAs update a review for the submission of latest finished round if instructor/TAs performed and saved a review for the previous round"
# it "should show "Instructor review" when a student views feedback on his/her submission if an instructor/TA has reviewed his/his team's work"
# it "should exclude the instructor's/TA's review score when calculating the average peer review score for the team"
# it "should exclude the instructor's/TA's review score when calculating the average score for each question in the review"

== '''References''' ==

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

Pull Request
* https://github.com/expertiza/expertiza/pull/1304

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

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

CSC/ECE 517 Fall 2018/E1855 let course staff as well as students do reviews

2018-12-07T23:24:01Z

Rkovilk: /* Proposed Solutions and Implementation */

== '''Introduction''' ==

The way Expertiza is set up right now is that only peers can review your work. However, there are cases when the course staff (Instructor/ TAs) would want to submit reviews as well. This project aims to implement this feature by allowing course staff to review the project on the same metrics as other students who review the project.

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

The current system does not allow instructors to submit reviews of student work. We will work upon the feature which will let them review using the same review form that students use to do reviews.

=== Current scenario ===

This is how some of the pages we are concerned with, currently look.

==== Submissions page for an assignment in Instructor View ====

[[File: Submissions_instr.jpeg | center]]

==== A typical Scores table in a Student View ====

[[File: Grades_view_team_current.png | center]]

== '''Proposed Solutions and Implementation''' ==

Following changes will be made to let staff perform reviews as well:

'''Step 1: Add a way for the instructors to perform a review.'''

We are planning to implement links to ''Begin review'', ''Edit review'','' View review'' and ''Submit review'' in the assignment submissions view.
When the instructor/TA reviews a work for the first time, he/she is added as a participant and a review response mapping is created.

Files edited:
* '''View: ''' ''app/views/assignments/list_submissions.html.erb'' - To add links in the instructor view
* '''Controller: ''' ''app/controllers/review_mapping_controller.rb'' - Method: add_instructor_as_reviewer

In the second case, we can see a 'Begin review' link. This is the initial state when instructor review has not been added to the submission.
Once the instructor adds a review and submits it, we can see the 'View review' link. In case he just saves the review, an 'Edit review' link will appear.
If the review deadline of one round is passed, the 'Edit review' link becomes 'Update review' link. This follows in line with what the student sees while performing a review. Similarly, just like students instructor would not able to edit or update the review once submitted.

'''Step 2: Add the instructor review in ''Your Scores'' table in case he has reviewed your work. Provide an icon to highlight the special nature of an instructors review.'''

[[File:Ins_TA_Review.png]]

Files edited:
* '''Assets: ''' ''app/assets/stylesheets/grades.scss'' - Icon to make an instructor's review distinct from other reviews
* '''View: ''' ''app/views/grades/view_team.html.erb'' - To modify the "Your scores" page to include an icon next to the peer review score indicating that the instructor's score is not included in the final peer review score.
* '''Models: '''
** ''app/models/answer.rb'' - Method: compute_scores | Modification in logic to ensure instructor review scores are not counted in the overall score of the student.
** ''app/models/vm_question_response_score_cell.rb'' - Included a new variable called 'is_instructor_review' to identify an instructor review
** ''app/models/vm_question_response_row.rb'' - Change in average_score_for_row method to not include an instructor review score
** ''app/models/vm_question_response.rb'' - Modified the add_answer method to include the is_instructor_review to each row_score object

A student should be able to make out if an instructor has reviewed his/his team's work. In case the instructor performs a review on the team's work, there will be an icon next to the instructor's review along with explicitly stating that it is an 'Instructor review'.
The average peer review score for the team has been modified to exclude the instructor's scores. Same has been taken into account for the average score calculated for each row.

[[File:Score_hover.png]]

Possible icons :
[[File:Instuctor.jpg]] [[File:Instructor1.jpg]]

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

'''Features testing:''' Many of our changes are reflected on views (user interface). Following is the list of tests that we will conduct with rspec/capybara.

# it "should let instructor/TAs perform a review for the submission of latest finished round if instructor/TAs has not started a review for the submission yet"
# it "should let instructor/TAs save a review"
# it "should let instructor/TAs review a previously saved review"
# it "should let instructor/TAs edit a previously saved review"
# it "should allow instructor/TAs perform a review after the deadline for reviewing has passed"

'''More testing:'''

# it "should let instructor/TAs update a review for the submission of latest finished round if instructor/TAs performed and saved a review for the previous round"
# it "should show "Instructor review" when a student views feedback on his/her submission if an instructor/TA has reviewed his/his team's work"
# it "should exclude the instructor's/TA's review score when calculating the average peer review score for the team"
# it "should exclude the instructor's/TA's review score when calculating the average score for each question in the review"

== '''References''' ==

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

Pull Request
* https://github.com/expertiza/expertiza/pull/1304

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

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

File:Score hover.png

2018-12-07T23:22:49Z

Rkovilk:

CSC/ECE 517 Fall 2018/E1855 let course staff as well as students do reviews

2018-12-07T23:22:18Z

Rkovilk: /* Proposed Solutions and Implementation */

== '''Introduction''' ==

The way Expertiza is set up right now is that only peers can review your work. However, there are cases when the course staff (Instructor/ TAs) would want to submit reviews as well. This project aims to implement this feature by allowing course staff to review the project on the same metrics as other students who review the project.

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

The current system does not allow instructors to submit reviews of student work. We will work upon the feature which will let them review using the same review form that students use to do reviews.

=== Current scenario ===

This is how some of the pages we are concerned with, currently look.

==== Submissions page for an assignment in Instructor View ====

[[File: Submissions_instr.jpeg | center]]

==== A typical Scores table in a Student View ====

[[File: Grades_view_team_current.png | center]]

== '''Proposed Solutions and Implementation''' ==

Following changes will be made to let staff perform reviews as well:

'''Step 1: Add a way for the instructors to perform a review.'''

We are planning to implement links to ''Begin review'', ''Edit review'','' View review'' and ''Submit review'' in the assignment submissions view.
When the instructor/TA reviews a work for the first time, he/she is added as a participant and a review response mapping is created.

Files edited:
* '''View: ''' ''app/views/assignments/list_submissions.html.erb'' - To add links in the instructor view
* '''Controller: ''' ''app/controllers/review_mapping_controller.rb'' - Method: add_instructor_as_reviewer

In the second case, we can see a 'Begin review' link. This is the initial state when instructor review has not been added to the submission.
Once the instructor adds a review and submits it, we can see the 'View review' link. In case he just saves the review, an 'Edit review' link will appear.
If the review deadline of one round is passed, the 'Edit review' link becomes 'Update review' link. This follows in line with what the student sees while performing a review. Similarly, just like students instructor would not able to edit or update the review once submitted.

'''Step 2: Add the instructor review in ''Your Scores'' table in case he has reviewed your work. Provide an icon to highlight the special nature of an instructors review.'''

[[File:Ins_TA_Review.png]]

Files edited:
* '''Assets: ''' ''app/assets/stylesheets/grades.scss'' - Icon to make an instructor's review distinct from other reviews
* '''View: ''' ''app/views/grades/view_team.html.erb'' - To modify the "Your scores" page to include an icon next to the peer review score indicating that the instructor's score is not included in the final peer review score.
* '''Models: '''
** ''app/models/answer.rb'' - Method: compute_scores | Modification in logic to ensure instructor review scores are not counted in the overall score of the student.
** ''app/models/vm_question_response_score_cell.rb'' - Included a new variable called 'is_instructor_review' to identify an instructor review
** ''app/models/vm_question_response_row.rb'' - Change in average_score_for_row method to not include an instructor review score
** ''app/models/vm_question_response.rb'' - Modified the add_answer method to include the is_instructor_review to each row_score object

A student should be able to make out if an instructor has reviewed his/his team's work. In case the instructor performs a review on the team's work, there will be an icon next to the instructor's review along with explicitly stating that it is an 'Instructor review'.
The average peer review score for the team has been modified to exclude the instructor's scores. Same has been taken into account for the average score calculated for each row.

[[File:Score_hover.png]]

Possible icons :
[[File:Instuctor.jpg]] [[File:Instructor1.jpg]]

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

'''Features testing:''' Many of our changes are reflected on views (user interface). Following is the list of tests that we will conduct with rspec/capybara.

# it "should let instructor/TAs perform a review for the submission of latest finished round if instructor/TAs has not started a review for the submission yet"
# it "should let instructor/TAs save a review"
# it "should let instructor/TAs review a previously saved review"
# it "should let instructor/TAs edit a previously saved review"
# it "should allow instructor/TAs perform a review after the deadline for reviewing has passed"

'''More testing:'''

# it "should let instructor/TAs update a review for the submission of latest finished round if instructor/TAs performed and saved a review for the previous round"
# it "should show "Instructor review" when a student views feedback on his/her submission if an instructor/TA has reviewed his/his team's work"
# it "should exclude the instructor's/TA's review score when calculating the average peer review score for the team"
# it "should exclude the instructor's/TA's review score when calculating the average score for each question in the review"

== '''References''' ==

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

Pull Request
* https://github.com/expertiza/expertiza/pull/1304

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

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

File:Ins TA Review.png

2018-12-07T21:51:06Z

Rkovilk:

CSC/ECE 517 Fall 2018/E1855 let course staff as well as students do reviews

2018-12-07T21:50:33Z

Rkovilk: /* Proposed Solutions and Implementation */

== '''Introduction''' ==

The way Expertiza is set up right now is that only peers can review your work. However, there are cases when the course staff (Instructor/ TAs) would want to submit reviews as well. This project aims to implement this feature by allowing course staff to review the project on the same metrics as other students who review the project.

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

The current system does not allow instructors to submit reviews of student work. We will work upon the feature which will let them review using the same review form that students use to do reviews.

=== Current scenario ===

This is how some of the pages we are concerned with, currently look.

==== Submissions page for an assignment in Instructor View ====

[[File: Submissions_instr.jpeg | center]]

==== A typical Scores table in a Student View ====

[[File: Grades_view_team_current.png | center]]

== '''Proposed Solutions and Implementation''' ==

Following changes will be made to let staff perform reviews as well:

'''Step 1: Add a way for the instructors to perform a review.'''

We are planning to implement links to ''Begin review'', ''Edit review'','' View review'' and ''Submit review'' in the assignment submissions view.
When the instructor/TA reviews a work for the first time, he/she is added as a participant and a review response mapping is created.

Files edited:
* '''View: ''' ''app/views/assignments/list_submissions.html.erb'' - To add links in the instructor view
* '''Controller: ''' ''app/controllers/review_mapping_controller.rb'' - Method: add_instructor_as_reviewer

In the second case, we can see a 'Begin review' link. This is the initial state when instructor review has not been added to the submission.
Once the instructor adds a review and submits it, we can see the 'View review' link. In case he just saves the review, an 'Edit review' link will appear.
If the review deadline of one round is passed, the 'Edit review' link becomes 'Update review' link. This follows in line with what the student sees while performing a review. Similarly, just like students instructor would not able to edit or update the review once submitted.

'''Step 2: Add the instructor review in ''Your Scores'' table in case he has reviewed your work. Provide an icon to highlight the special nature of an instructors review.'''

[[File:Ins_TA_Review.png]]

Files edited:
* '''Assets: ''' ''app/assets/stylesheets/grades.scss'' - Icon to make an instructor's review distinct from other reviews
* '''View: ''' ''app/views/grades/view_team.html.erb'' - To modify the "Your scores" page to include an icon next to the peer review score indicating that the instructor's score is not included in the final peer review score.
* '''Models: '''
** ''app/models/answer.rb'' - Method: compute_scores | Modification in logic to ensure instructor review scores are not counted in the overall score of the student.
** ''app/models/vm_question_response_score_cell.rb'' - Included a new variable called 'is_instructor_review' to identify an instructor review
** ''app/models/vm_question_response_row.rb'' - Change in average_score_for_row method to not include an instructor review score
** ''app/models/vm_question_response.rb'' - Modified the add_answer method to include the is_instructor_review to each row_score object

A student should be able to make out if an instructor has reviewed his/his team's work. In case the instructor performs a review on the team's work, there will be an icon next to the instructor's review along with explicitly stating that it is an 'Instructor review'.
The average peer review score for the team has been modified to exclude the instructor's scores. Same has been taken into account for the average score calculated for each row.

Possible icons :
[[File:Instuctor.jpg]] [[File:Instructor1.jpg]]

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

'''Features testing:''' Many of our changes are reflected on views (user interface). Following is the list of tests that we will conduct with rspec/capybara.

# it "should let instructor/TAs perform a review for the submission of latest finished round if instructor/TAs has not started a review for the submission yet"
# it "should let instructor/TAs save a review"
# it "should let instructor/TAs review a previously saved review"
# it "should let instructor/TAs edit a previously saved review"
# it "should allow instructor/TAs perform a review after the deadline for reviewing has passed"

'''More testing:'''

# it "should let instructor/TAs update a review for the submission of latest finished round if instructor/TAs performed and saved a review for the previous round"
# it "should show "Instructor review" when a student views feedback on his/her submission if an instructor/TA has reviewed his/his team's work"
# it "should exclude the instructor's/TA's review score when calculating the average peer review score for the team"
# it "should exclude the instructor's/TA's review score when calculating the average score for each question in the review"

== '''References''' ==

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

Pull Request
* https://github.com/expertiza/expertiza/pull/1304

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

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

CSC/ECE 517 Fall 2018/E1855 let course staff as well as students do reviews

2018-12-05T23:35:14Z

Rkovilk: /* References */

== '''Introduction''' ==

The way Expertiza is set up right now is that only peers can review your work. However, there are cases when the course staff (Instructor/ TAs) would want to submit reviews as well. This project aims to implement this feature by allowing course staff to review the project on the same metrics as other students who review the project.

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

The current system does not allow instructors to submit reviews of student work. We will work upon the feature which will let them review using the same review form that students use to do reviews.

=== Current scenario ===

This is how some of the pages we are concerned with, currently look.

==== Submissions page for an assignment in Instructor View ====

[[File: Submissions_instr.jpeg | center]]

==== A typical Scores table in a Student View ====

[[File: Grades_view_team_current.png | center]]

== '''Proposed Solutions and Implementation''' ==

Following changes will be made to let staff perform reviews as well:

'''Step 1: Add a way for the instructors to perform a review.'''

We are planning to implement links to ''Begin review'', ''Edit review'','' View review'' and ''Submit review'' in the assignment submissions view.
When the instructor/TA reviews a work for the first time, he/she is added as a participant and a review response mapping is created.

Files edited:
* '''View: ''' ''app/views/assignments/list_submissions.html.erb'' - To add links in the instructor view
* '''Controller: ''' ''app/controllers/review_mapping_controller.rb'' - Method: add_instructor_as_reviewer

In the second case, we can see a 'Begin review' link. This is the initial state when instructor review has not been added to the submission.
Once the instructor adds a review and submits it, we can see the 'View review' link. In case he just saves the review, an 'Edit review' link will appear.
If the review deadline of one round is passed, the 'Edit review' link becomes 'Update review' link. This follows in line with what the student sees while performing a review. Similarly, just like students instructor would not able to edit or update the review once submitted.

'''Step 2: Add the instructor review in ''Your Scores'' table in case he has reviewed your work. Provide an icon to highlight the special nature of an instructors review.'''

Files edited:
* '''Assets: ''' ''app/assets/stylesheets/grades.scss'' - Icon to make an instructor's review distinct from other reviews
* '''View: ''' ''app/views/grades/view_team.html.erb'' - To modify the "Your scores" page to include an icon next to the peer review score indicating that the instructor's score is not included in the final peer review score.
* '''Models: '''
** ''app/models/answer.rb'' - Method: compute_scores | Modification in logic to ensure instructor review scores are not counted in the overall score of the student.
** ''app/models/vm_question_response_score_cell.rb'' - Included a new variable called 'is_instructor_review' to identify an instructor review
** ''app/models/vm_question_response_row.rb'' - Change in average_score_for_row method to not include an instructor review score
** ''app/models/vm_question_response.rb'' - Modified the add_answer method to include the is_instructor_review to each row_score object

A student should be able to make out if an instructor has reviewed his/his team's work. In case the instructor performs a review on the team's work, there will be an icon next to the instructor's review along with explicitly stating that it is an 'Instructor review'.
The average peer review score for the team has been modified to exclude the instructor's scores. Same has been taken into account for the average score calculated for each row.

Possible icons :
[[File:Instuctor.jpg]] [[File:Instructor1.jpg]]

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

'''Features testing:''' Many of our changes are reflected on views (user interface). Following is the list of tests that we will conduct with rspec/capybara.

# it "should let instructor/TAs perform a review for the submission of latest finished round if instructor/TAs has not started a review for the submission yet"
# it "should let instructor/TAs save a review"
# it "should let instructor/TAs review a previously saved review"
# it "should let instructor/TAs edit a previously saved review"
# it "should allow instructor/TAs perform a review after the deadline for reviewing has passed"

'''More testing:'''

# it "should let instructor/TAs update a review for the submission of latest finished round if instructor/TAs performed and saved a review for the previous round"
# it "should show "Instructor review" when a student views feedback on his/her submission if an instructor/TA has reviewed his/his team's work"
# it "should exclude the instructor's/TA's review score when calculating the average peer review score for the team"
# it "should exclude the instructor's/TA's review score when calculating the average score for each question in the review"

== '''References''' ==

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

Pull Request
* https://github.com/expertiza/expertiza/pull/1304

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

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

CSC/ECE 517 Fall 2018/E1855 let course staff as well as students do reviews

2018-11-21T05:36:02Z

Rkovilk: /* Proposed Solutions and Implementation */

== '''Introduction''' ==

The way Expertiza is set up right now is that only peers can review your work. However, there are cases when the course staff (Instructor/ TAs) would want to submit reviews as well. This project aims to implement this feature by allowing course staff to review the project on the same metrics as other students who review the project.

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

The current system does not allow instructors to submit reviews of student work. We will work upon the feature which will let them review using the same review form that students use to do reviews.

=== Current scenario ===

This is how some of the pages we are concerned with, currently look.

==== Submissions page for an assignment in Instructor View ====

[[File: Submissions_instr.jpeg | center]]

==== A typical Scores table in a Student View ====

[[File: Grades_view_team_current.png | center]]

== '''Proposed Solutions and Implementation''' ==

Following changes will be made to let staff perform reviews as well:

'''Step 1: Add a way for the instructors to perform a review.'''

We are planning to implement links to ''Begin review'', ''Edit review'','' View review'' and ''Submit review'' in the assignment submissions view.
When the instructor/TA reviews a work for the first time, he/she is added as a participant and a review response mapping is created.

Files edited:
* '''View: ''' ''app/views/assignments/list_submissions.html.erb'' - To add links in the instructor view
* '''Controller: ''' ''app/controllers/review_mapping_controller.rb'' - Method: add_instructor_as_reviewer

In the second case, we can see a 'Begin review' link. This is the initial state when instructor review has not been added to the submission.
Once the instructor adds a review and submits it, we can see the 'View review' link. In case he just saves the review, an 'Edit review' link will appear.
If the review deadline of one round is passed, the 'Edit review' link becomes 'Update review' link. This follows in line with what the student sees while performing a review. Similarly, just like students instructor would not able to edit or update the review once submitted.

'''Step 2: Add the instructor review in ''Your Scores'' table in case he has reviewed your work. Provide an icon to highlight the special nature of an instructors review.'''

Files edited:
* '''Assets: ''' ''app/assets/stylesheets/grades.scss'' - Icon to make an instructor's review distinct from other reviews
* '''View: ''' ''app/views/grades/view_team.html.erb'' - To modify the "Your scores" page to include an icon next to the peer review score indicating that the instructor's score is not included in the final peer review score.
* '''Models: '''
** ''app/models/answer.rb'' - Method: compute_scores | Modification in logic to ensure instructor review scores are not counted in the overall score of the student.
** ''app/models/vm_question_response_score_cell.rb'' - Included a new variable called 'is_instructor_review' to identify an instructor review
** ''app/models/vm_question_response_row.rb'' - Change in average_score_for_row method to not include an instructor review score
** ''app/models/vm_question_response.rb'' - Modified the add_answer method to include the is_instructor_review to each row_score object

A student should be able to make out if an instructor has reviewed his/his team's work. In case the instructor performs a review on the team's work, there will be an icon next to the instructor's review along with explicitly stating that it is an 'Instructor review'.
The average peer review score for the team has been modified to exclude the instructor's scores. Same has been taken into account for the average score calculated for each row.

Possible icons :
[[File:Instuctor.jpg]] [[File:Instructor1.jpg]]

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

'''Features testing:''' Many of our changes are reflected on views (user interface). Following is the list of tests that we will conduct with rspec/capybara.

# it "should let instructor/TAs perform a review for the submission of latest finished round if instructor/TAs has not started a review for the submission yet"
# it "should let instructor/TAs save a review"
# it "should let instructor/TAs review a previously saved review"
# it "should let instructor/TAs edit a previously saved review"
# it "should allow instructor/TAs perform a review after the deadline for reviewing has passed"

'''More testing:'''

# it "should let instructor/TAs update a review for the submission of latest finished round if instructor/TAs performed and saved a review for the previous round"
# it "should show "Instructor review" when a student views feedback on his/her submission if an instructor/TA has reviewed his/his team's work"
# it "should exclude the instructor's/TA's review score when calculating the average peer review score for the team"
# it "should exclude the instructor's/TA's review score when calculating the average score for each question in the review"

== '''References''' ==

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

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

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

CSC/ECE 517 Fall 2018/E1855 let course staff as well as students do reviews

2018-11-21T05:35:32Z

Rkovilk: /* Proposed Solutions and Implementation */

== '''Introduction''' ==

The way Expertiza is set up right now is that only peers can review your work. However, there are cases when the course staff (Instructor/ TAs) would want to submit reviews as well. This project aims to implement this feature by allowing course staff to review the project on the same metrics as other students who review the project.

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

The current system does not allow instructors to submit reviews of student work. We will work upon the feature which will let them review using the same review form that students use to do reviews.

=== Current scenario ===

This is how some of the pages we are concerned with, currently look.

==== Submissions page for an assignment in Instructor View ====

[[File: Submissions_instr.jpeg | center]]

==== A typical Scores table in a Student View ====

[[File: Grades_view_team_current.png | center]]

== '''Proposed Solutions and Implementation''' ==

Following changes will be made to let staff perform reviews as well:

'''Step 1: Add a way for the instructors to perform a review.'''

We are planning to implement links to ''Begin review'', ''Edit review'','' View review'' and ''Submit review'' in the assignment submissions view.
When the instructor/TA reviews a work for the first time, he/she is added as a participant and a review response mapping is created.

Files edited:
* '''View: ''' ''app/views/assignments/list_submissions.html.erb'' - To add links in the instructor view
* '''Controller: ''' ''app/controllers/review_mapping_controller.rb'' - Method: add_instructor_as_reviewer

In the second case, we can see a 'Begin review' link. This is the initial state when instructor review has not been added to the submission.
Once the instructor adds a review and submits it, we can see the 'View review' link. In case he just saves the review, an 'Edit review' link will appear.
If the review deadline of one round is passed, the 'Edit review' link becomes 'Update review' link. This follows in line with what the student sees while performing a review. Similarly, just like students instructor would not able to edit or update the review once submitted.

'''Step 2: Add the instructor review in ''Your Scores'' table in case he has reviewed your work. Provide an icon to highlight the special nature of an instructors review.'''

Files edited:
* '''Assets: ''' ''app/assets/stylesheets/grades.scss'' - Icon to make an instructor's review distinct from other reviews
* '''View: ''' ''app/views/grades/view_team.html.erb'' - To modify the "Your scores" page to include an icon next to the peer review score indicating that the instructor's score is not included in the final peer review score.
* '''Models: '''
** ''app/models/answer.rb'' - Method: compute_scores | Modification in logic to ensure instructor review scores are not counted in the overall score of the student.
** ''app/models/vm_question_response_score_cell.rb'' - Included a new variable called 'is_instructor_review' to identify an instructor review
** ''app/models/vm_question_response_row.rb'' - Change in average_score_for_row method to not include an instructor review score
** ''app/models/vm_question_response.rb'' - Modified the add_answer method to include the is_instructor_review to each row_score object

A student should be able to make out if an instructor has reviewed his/his team's work. In case the instructor performs a review on the team's work, there will be an icon next to the instructor's review along with explicitly stating that it is an 'Instructor review'.
The average peer review score for the team has been modified to exclude the instructor's scores. Same has been taken into account for the average score calculated for each row.

Possible icons:
[[File:Instuctor.jpg]] [[File:Instructor1.jpg]]

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

'''Features testing:''' Many of our changes are reflected on views (user interface). Following is the list of tests that we will conduct with rspec/capybara.

# it "should let instructor/TAs perform a review for the submission of latest finished round if instructor/TAs has not started a review for the submission yet"
# it "should let instructor/TAs save a review"
# it "should let instructor/TAs review a previously saved review"
# it "should let instructor/TAs edit a previously saved review"
# it "should allow instructor/TAs perform a review after the deadline for reviewing has passed"

'''More testing:'''

# it "should let instructor/TAs update a review for the submission of latest finished round if instructor/TAs performed and saved a review for the previous round"
# it "should show "Instructor review" when a student views feedback on his/her submission if an instructor/TA has reviewed his/his team's work"
# it "should exclude the instructor's/TA's review score when calculating the average peer review score for the team"
# it "should exclude the instructor's/TA's review score when calculating the average score for each question in the review"

== '''References''' ==

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

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

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

CSC/ECE 517 Fall 2018/E1855 let course staff as well as students do reviews

2018-11-21T05:35:18Z

Rkovilk: /* Proposed Solutions and Implementation */

== '''Introduction''' ==

The way Expertiza is set up right now is that only peers can review your work. However, there are cases when the course staff (Instructor/ TAs) would want to submit reviews as well. This project aims to implement this feature by allowing course staff to review the project on the same metrics as other students who review the project.

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

The current system does not allow instructors to submit reviews of student work. We will work upon the feature which will let them review using the same review form that students use to do reviews.

=== Current scenario ===

This is how some of the pages we are concerned with, currently look.

==== Submissions page for an assignment in Instructor View ====

[[File: Submissions_instr.jpeg | center]]

==== A typical Scores table in a Student View ====

[[File: Grades_view_team_current.png | center]]

== '''Proposed Solutions and Implementation''' ==

Following changes will be made to let staff perform reviews as well:

'''Step 1: Add a way for the instructors to perform a review.'''

We are planning to implement links to ''Begin review'', ''Edit review'','' View review'' and ''Submit review'' in the assignment submissions view.
When the instructor/TA reviews a work for the first time, he/she is added as a participant and a review response mapping is created.

Files edited:
* '''View: ''' ''app/views/assignments/list_submissions.html.erb'' - To add links in the instructor view
* '''Controller: ''' ''app/controllers/review_mapping_controller.rb'' - Method: add_instructor_as_reviewer

In the second case, we can see a 'Begin review' link. This is the initial state when instructor review has not been added to the submission.
Once the instructor adds a review and submits it, we can see the 'View review' link. In case he just saves the review, an 'Edit review' link will appear.
If the review deadline of one round is passed, the 'Edit review' link becomes 'Update review' link. This follows in line with what the student sees while performing a review. Similarly, just like students instructor would not able to edit or update the review once submitted.

'''Step 2: Add the instructor review in ''Your Scores'' table in case he has reviewed your work. Provide an icon to highlight the special nature of an instructors review.'''

Files edited:
* '''Assets: ''' ''app/assets/stylesheets/grades.scss'' - Icon to make an instructor's review distinct from other reviews
* '''View: ''' ''app/views/grades/view_team.html.erb'' - To modify the "Your scores" page to include an icon next to the peer review score indicating that the instructor's score is not included in the final peer review score.
* '''Models: '''
** ''app/models/answer.rb'' - Method: compute_scores | Modification in logic to ensure instructor review scores are not counted in the overall score of the student.
** ''app/models/vm_question_response_score_cell.rb'' - Included a new variable called 'is_instructor_review' to identify an instructor review
** ''app/models/vm_question_response_row.rb'' - Change in average_score_for_row method to not include an instructor review score
** ''app/models/vm_question_response.rb'' - Modified the add_answer method to include the is_instructor_review to each row_score object

A student should be able to make out if an instructor has reviewed his/his team's work. In case the instructor performs a review on the team's work, there will be an icon next to the instructor's review along with explicitly stating that it is an 'Instructor review'.
The average peer review score for the team has been modified to exclude the instructor's scores. Same has been taken into account for the average score calculated for each row.

Possible icons [[File:Instuctor.jpg]] [[File:Instructor1.jpg]]

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

'''Features testing:''' Many of our changes are reflected on views (user interface). Following is the list of tests that we will conduct with rspec/capybara.

# it "should let instructor/TAs perform a review for the submission of latest finished round if instructor/TAs has not started a review for the submission yet"
# it "should let instructor/TAs save a review"
# it "should let instructor/TAs review a previously saved review"
# it "should let instructor/TAs edit a previously saved review"
# it "should allow instructor/TAs perform a review after the deadline for reviewing has passed"

'''More testing:'''

# it "should let instructor/TAs update a review for the submission of latest finished round if instructor/TAs performed and saved a review for the previous round"
# it "should show "Instructor review" when a student views feedback on his/her submission if an instructor/TA has reviewed his/his team's work"
# it "should exclude the instructor's/TA's review score when calculating the average peer review score for the team"
# it "should exclude the instructor's/TA's review score when calculating the average score for each question in the review"

== '''References''' ==

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

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

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

CSC/ECE 517 Fall 2018/E1855 let course staff as well as students do reviews

2018-11-21T05:35:03Z

Rkovilk: /* Proposed Solutions and Implementation */

== '''Introduction''' ==

The way Expertiza is set up right now is that only peers can review your work. However, there are cases when the course staff (Instructor/ TAs) would want to submit reviews as well. This project aims to implement this feature by allowing course staff to review the project on the same metrics as other students who review the project.

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

The current system does not allow instructors to submit reviews of student work. We will work upon the feature which will let them review using the same review form that students use to do reviews.

=== Current scenario ===

This is how some of the pages we are concerned with, currently look.

==== Submissions page for an assignment in Instructor View ====

[[File: Submissions_instr.jpeg | center]]

==== A typical Scores table in a Student View ====

[[File: Grades_view_team_current.png | center]]

== '''Proposed Solutions and Implementation''' ==

Following changes will be made to let staff perform reviews as well:

'''Step 1: Add a way for the instructors to perform a review.'''

We are planning to implement links to ''Begin review'', ''Edit review'','' View review'' and ''Submit review'' in the assignment submissions view.
When the instructor/TA reviews a work for the first time, he/she is added as a participant and a review response mapping is created.

Files edited:
* '''View: ''' ''app/views/assignments/list_submissions.html.erb'' - To add links in the instructor view
* '''Controller: ''' ''app/controllers/review_mapping_controller.rb'' - Method: add_instructor_as_reviewer

In the second case, we can see a 'Begin review' link. This is the initial state when instructor review has not been added to the submission.
Once the instructor adds a review and submits it, we can see the 'View review' link. In case he just saves the review, an 'Edit review' link will appear.
If the review deadline of one round is passed, the 'Edit review' link becomes 'Update review' link. This follows in line with what the student sees while performing a review. Similarly, just like students instructor would not able to edit or update the review once submitted.

'''Step 2: Add the instructor review in ''Your Scores'' table in case he has reviewed your work. Provide an icon to highlight the special nature of an instructors review.'''

Files edited:
* '''Assets: ''' ''app/assets/stylesheets/grades.scss'' - Icon to make an instructor's review distinct from other reviews
* '''View: ''' ''app/views/grades/view_team.html.erb'' - To modify the "Your scores" page to include an icon next to the peer review score indicating that the instructor's score is not included in the final peer review score.
* '''Models: '''
** ''app/models/answer.rb'' - Method: compute_scores | Modification in logic to ensure instructor review scores are not counted in the overall score of the student.
** ''app/models/vm_question_response_score_cell.rb'' - Included a new variable called 'is_instructor_review' to identify an instructor review
** ''app/models/vm_question_response_row.rb'' - Change in average_score_for_row method to not include an instructor review score
** ''app/models/vm_question_response.rb'' - Modified the add_answer method to include the is_instructor_review to each row_score object

A student should be able to make out if an instructor has reviewed his/his team's work. In case the instructor performs a review on the team's work, there will be an icon next to the instructor's review along with explicitly stating that it is an 'Instructor review'.
The average peer review score for the team has been modified to exclude the instructor's scores. Same has been taken into account for the average score calculated for each row.

Possible icons [[File:Instuctor.jpg]] [[File:Instuctor1.jpg]]

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

'''Features testing:''' Many of our changes are reflected on views (user interface). Following is the list of tests that we will conduct with rspec/capybara.

# it "should let instructor/TAs perform a review for the submission of latest finished round if instructor/TAs has not started a review for the submission yet"
# it "should let instructor/TAs save a review"
# it "should let instructor/TAs review a previously saved review"
# it "should let instructor/TAs edit a previously saved review"
# it "should allow instructor/TAs perform a review after the deadline for reviewing has passed"

'''More testing:'''

# it "should let instructor/TAs update a review for the submission of latest finished round if instructor/TAs performed and saved a review for the previous round"
# it "should show "Instructor review" when a student views feedback on his/her submission if an instructor/TA has reviewed his/his team's work"
# it "should exclude the instructor's/TA's review score when calculating the average peer review score for the team"
# it "should exclude the instructor's/TA's review score when calculating the average score for each question in the review"

== '''References''' ==

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

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

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

File:Instructor1.jpg

2018-11-21T05:34:25Z

Rkovilk:

File:Instuctor.jpg

2018-11-21T05:34:10Z

Rkovilk:

CSC/ECE 517 Fall 2018/E1855 let course staff as well as students do reviews

2018-11-21T05:33:41Z

Rkovilk:

== '''Introduction''' ==

The way Expertiza is set up right now is that only peers can review your work. However, there are cases when the course staff (Instructor/ TAs) would want to submit reviews as well. This project aims to implement this feature by allowing course staff to review the project on the same metrics as other students who review the project.

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

The current system does not allow instructors to submit reviews of student work. We will work upon the feature which will let them review using the same review form that students use to do reviews.

=== Current scenario ===

This is how some of the pages we are concerned with, currently look.

==== Submissions page for an assignment in Instructor View ====

[[File: Submissions_instr.jpeg | center]]

==== A typical Scores table in a Student View ====

[[File: Grades_view_team_current.png | center]]

== '''Proposed Solutions and Implementation''' ==

Following changes will be made to let staff perform reviews as well:

'''Step 1: Add a way for the instructors to perform a review.'''

We are planning to implement links to ''Begin review'', ''Edit review'','' View review'' and ''Submit review'' in the assignment submissions view.
When the instructor/TA reviews a work for the first time, he/she is added as a participant and a review response mapping is created.

Files edited:
* '''View: ''' ''app/views/assignments/list_submissions.html.erb'' - To add links in the instructor view
* '''Controller: ''' ''app/controllers/review_mapping_controller.rb'' - Method: add_instructor_as_reviewer

In the second case, we can see a 'Begin review' link. This is the initial state when instructor review has not been added to the submission.
Once the instructor adds a review and submits it, we can see the 'View review' link. In case he just saves the review, an 'Edit review' link will appear.
If the review deadline of one round is passed, the 'Edit review' link becomes 'Update review' link. This follows in line with what the student sees while performing a review. Similarly, just like students instructor would not able to edit or update the review once submitted.

'''Step 2: Add the instructor review in ''Your Scores'' table in case he has reviewed your work. Provide an icon to highlight the special nature of an instructors review.'''

Files edited:
* '''Assets: ''' ''app/assets/stylesheets/grades.scss'' - Icon to make an instructor's review distinct from other reviews
* '''View: ''' ''app/views/grades/view_team.html.erb'' - To modify the "Your scores" page to include an icon next to the peer review score indicating that the instructor's score is not included in the final peer review score.
* '''Models: '''
** ''app/models/answer.rb'' - Method: compute_scores | Modification in logic to ensure instructor review scores are not counted in the overall score of the student.
** ''app/models/vm_question_response_score_cell.rb'' - Included a new variable called 'is_instructor_review' to identify an instructor review
** ''app/models/vm_question_response_row.rb'' - Change in average_score_for_row method to not include an instructor review score
** ''app/models/vm_question_response.rb'' - Modified the add_answer method to include the is_instructor_review to each row_score object

A student should be able to make out if an instructor has reviewed his/his team's work. In case the instructor performs a review on the team's work, there will be an icon next to the instructor's review along with explicitly stating that it is an 'Instructor review'.
The average peer review score for the team has been modified to exclude the instructor's scores. Same has been taken into account for the average score calculated for each row.

Possible icons [[File:instuctor.png]] [[File:instuctor1.png]]

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

'''Features testing:''' Many of our changes are reflected on views (user interface). Following is the list of tests that we will conduct with rspec/capybara.

# it "should let instructor/TAs perform a review for the submission of latest finished round if instructor/TAs has not started a review for the submission yet"
# it "should let instructor/TAs save a review"
# it "should let instructor/TAs review a previously saved review"
# it "should let instructor/TAs edit a previously saved review"
# it "should allow instructor/TAs perform a review after the deadline for reviewing has passed"

'''More testing:'''

# it "should let instructor/TAs update a review for the submission of latest finished round if instructor/TAs performed and saved a review for the previous round"
# it "should show "Instructor review" when a student views feedback on his/her submission if an instructor/TA has reviewed his/his team's work"
# it "should exclude the instructor's/TA's review score when calculating the average peer review score for the team"
# it "should exclude the instructor's/TA's review score when calculating the average score for each question in the review"

== '''References''' ==

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

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

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

E1830 OSS Project Juniper: Bookmark enhancements

2018-11-09T19:45:13Z

Rkovilk: /* Testing Plan */

'''Peer Review Information'''

For users intending to view the Expertiza Bookmark enhancement associated with this assignment, the credentials are below:

Instructor login: username -> instructor6, password -> password

Student Accounts for Impersonation : student6340, student6341; Assignment -> Exercises, CSC 456, Fall 2015

'''
== Introduction ==
'''

'''Expertiza Background'''

Expertiza is an open-source educational web application developed on Ruby on Rails platform. Students and Instructors (including TA's) use this application though their credentials. Instructors can add new projects, assignments etc as well edit the previous ones and at a later stage can see the student submission and grade them. They can even put a time limit (deadline) for submitting the assignment. Students can form teams for the projects, submit their work through handles (Wiki page, link to a video etc). Students can even review their teammates and other peers, as well give them any suggestions if required.

GitHub hooks to Expertiza to encourage contributors. Expertiza project is supported by National Science Foundation.

'''Description of the current project'''

This project is intended to make Bookmarks more user-friendly, credible and valid. Bookmarks in expertiza are created by reviewers and can be used by authors for their work on any project. On each line of the signup sheet are two icons, one for adding a bookmark to the topic, and another for viewing bookmarks on the topic. If the instructor allows the participants to create bookmarks, then only a participant has access to create and view them. He should be able to create a new Bookmark only if he enters a valid one.

Now a new rubric is added for reviewing the bookmarks added to a topic and this is accessible only to members belonging to the topic. Therefore ratings can be now done via a drop-down or rubric.

== Issues ==

'''Problem 1'''

When a user after logging into expertiza goes to 'Create New Bookmark page" or "View existing bookmarks page", he's not able to go back to Sign-up sheet using "back" button.

[[File:back.png]]

Solution :

[[File:fixed_back_link.png]]

'''Problem 2'''

Bookmarks had only one option while reviewing and it was to use a drop down to give a score. Also the average rating metric had a bug and hence showed wrong values even when bookmark was not reviewed. The bug was fixed and the rubric feature was adding a new controller.

Now choosing "Scale" Option instead of "Dropdown" allows one to use a rubric instead.

[[File:scale.png]]

The rubric for rating the bookmark shows up as a link that looks as follows :

[[File:begin_review.png]]

The rubric looks like :

[[File:bookmark_review_rubric.png]]

== Testing Plan ==

'''Scope of our changes'''

The changes made in this project affect the Bookmark Controller so tests are written for its validity.

Also we noticed that the Bookmark Model didn't have any testing done so we are planning to test that.

While manually testing for correctness we came the issue of average rating present even when no rating of the bookmark was added, additionally the computation of average had a bug and was hence giving wrong average value.

The picture below shows the the bug the previous code had :

It shows an average rating value of 4.0 even when no review was done.

[[File:Wrong_avg.png]]

== Files modified in current project ==

'''''1. Fixing Average problem and adding Rubric feature :'''''

The following files were modified for fixing the average rating bug and adding rubric for the same.

app/models/bookmark_rating_response_map.rb

app/controllers/bookmark_rating_questionnaire_controller.rb

app/controllers/bookmarks_controller.rb

app/controllers/response_controller.rb

app/views/assignments/edit/_rubrics.html.erb

app/views/bookmarks/bookmark_rating.html.erb

app/views/bookmarks/list.html.erb

app/views/response/view.html.erb

config/routes.rb

'''''2. Tests for Model and Controller :'''''

spec/controllers/bookmarks_controller_spec.rb

spec/models/bookmark_spec.rb

spec/factories/factories.rb

== Automated & UI Testing ==

Automated RSpec tests were added to ensure the bookmarks are valid. Separate tests were written for the Bookmark Model and BookmarkRating Controller files.
The videos of the tests are uploaded onto YouTube and the links are provided in the references section.

Below shown is the coverage details

[[File:Coverage1.png]]

[[File:Coverage2.png]]

'''a) Back button for the page "View Bookmark" and "Create Bookmark" was resolved.'''

1. Login with the credentials to expertiza.

2. Go to 'My assignments' and select OSS Project/writeup.

3. Select 'Signup sheet'.

4. Many titles for projects are shown. Select a title and choose either 'View Bookmark' or 'Add Bookmark' button

5. If you choose 'View Bookmark', after viewing, press the back button to go back to Signup sheet.

6. You will land up in Sign-up sheet page.

7. If you choose 'Add Bookmark', you can add by giving Bookmark details and save it.

8. Now press back button.

9. You will land in Sign-up sheet page.

'''b) Adding Bookmark Rubric.'''

1. Login into the expertiza with the Instructor/TA credentials.

2. Go to 'Manage Content -> Questionnaires'

3. Select new public/private item under BookmarkRating

4. Fill in with required values and create it.

5. After this if you go to bookmark rubric option it should be visible

'''c) Allowing Bookmark Rubric.'''

1. Login into the expertiza with the Instructor/TA credentials.

2. Go to 'Manage Content -> Assignments'

3. Select the appropriate project

4. Now edit the project.

5. Check the box "Allow participants to create bookmarks?" under Topics tab if not done already.

6. Choose the appropriate rubric from the list or create one following steps from above.

7. Now under Rubrics tab choose the "Scale" option for Scored-question display style.

== Future Work ==

1. A reviewer can be recognized or credited if he added useful bookmarks i.e if the author has made use of the bookmark.

2. A function to add badges automatically if a participant had submitted more than threshold number of useful bookmarks.

3. The UI is basic and it can be further improved.

== References ==

1. Expertiza on Github : https://github.com/rahuliyer95/expertiza

2. Videos on YouTube : https://youtu.be/F95FA9Iam0s, https://youtu.be/tPpowgNRINk

3. Pull Request : https://github.com/expertiza/expertiza/pull/1266

File:Wrong avg.png

2018-11-09T19:43:48Z

Rkovilk:

E1830 OSS Project Juniper: Bookmark enhancements

2018-11-09T19:43:21Z

Rkovilk: /* Testing Plan */

'''Peer Review Information'''

For users intending to view the Expertiza Bookmark enhancement associated with this assignment, the credentials are below:

Instructor login: username -> instructor6, password -> password

Student Accounts for Impersonation : student6340, student6341; Assignment -> Exercises, CSC 456, Fall 2015

'''
== Introduction ==
'''

'''Expertiza Background'''

Expertiza is an open-source educational web application developed on Ruby on Rails platform. Students and Instructors (including TA's) use this application though their credentials. Instructors can add new projects, assignments etc as well edit the previous ones and at a later stage can see the student submission and grade them. They can even put a time limit (deadline) for submitting the assignment. Students can form teams for the projects, submit their work through handles (Wiki page, link to a video etc). Students can even review their teammates and other peers, as well give them any suggestions if required.

GitHub hooks to Expertiza to encourage contributors. Expertiza project is supported by National Science Foundation.

'''Description of the current project'''

This project is intended to make Bookmarks more user-friendly, credible and valid. Bookmarks in expertiza are created by reviewers and can be used by authors for their work on any project. On each line of the signup sheet are two icons, one for adding a bookmark to the topic, and another for viewing bookmarks on the topic. If the instructor allows the participants to create bookmarks, then only a participant has access to create and view them. He should be able to create a new Bookmark only if he enters a valid one.

Now a new rubric is added for reviewing the bookmarks added to a topic and this is accessible only to members belonging to the topic. Therefore ratings can be now done via a drop-down or rubric.

== Issues ==

'''Problem 1'''

When a user after logging into expertiza goes to 'Create New Bookmark page" or "View existing bookmarks page", he's not able to go back to Sign-up sheet using "back" button.

[[File:back.png]]

Solution :

[[File:fixed_back_link.png]]

'''Problem 2'''

Bookmarks had only one option while reviewing and it was to use a drop down to give a score. Also the average rating metric had a bug and hence showed wrong values even when bookmark was not reviewed. The bug was fixed and the rubric feature was adding a new controller.

Now choosing "Scale" Option instead of "Dropdown" allows one to use a rubric instead.

[[File:scale.png]]

The rubric for rating the bookmark shows up as a link that looks as follows :

[[File:begin_review.png]]

The rubric looks like :

[[File:bookmark_review_rubric.png]]

== Testing Plan ==

'''Scope of our changes'''

The changes made in this project affect the Bookmark Controller so tests are written for its validity.

Also we noticed that the Bookmark Model didn't have any testing done so we are planning to test that.

While manually testing for correctness we came the issue of average rating present even when no rating of the bookmark was added, additionally the computation of average had a bug and was hence giving wrong average value.

[[File:Wrong_avg.png]]

== Files modified in current project ==

'''''1. Fixing Average problem and adding Rubric feature :'''''

The following files were modified for fixing the average rating bug and adding rubric for the same.

app/models/bookmark_rating_response_map.rb

app/controllers/bookmark_rating_questionnaire_controller.rb

app/controllers/bookmarks_controller.rb

app/controllers/response_controller.rb

app/views/assignments/edit/_rubrics.html.erb

app/views/bookmarks/bookmark_rating.html.erb

app/views/bookmarks/list.html.erb

app/views/response/view.html.erb

config/routes.rb

'''''2. Tests for Model and Controller :'''''

spec/controllers/bookmarks_controller_spec.rb

spec/models/bookmark_spec.rb

spec/factories/factories.rb

== Automated & UI Testing ==

Automated RSpec tests were added to ensure the bookmarks are valid. Separate tests were written for the Bookmark Model and BookmarkRating Controller files.
The videos of the tests are uploaded onto YouTube and the links are provided in the references section.

Below shown is the coverage details

[[File:Coverage1.png]]

[[File:Coverage2.png]]

'''a) Back button for the page "View Bookmark" and "Create Bookmark" was resolved.'''

1. Login with the credentials to expertiza.

2. Go to 'My assignments' and select OSS Project/writeup.

3. Select 'Signup sheet'.

4. Many titles for projects are shown. Select a title and choose either 'View Bookmark' or 'Add Bookmark' button

5. If you choose 'View Bookmark', after viewing, press the back button to go back to Signup sheet.

6. You will land up in Sign-up sheet page.

7. If you choose 'Add Bookmark', you can add by giving Bookmark details and save it.

8. Now press back button.

9. You will land in Sign-up sheet page.

'''b) Adding Bookmark Rubric.'''

1. Login into the expertiza with the Instructor/TA credentials.

2. Go to 'Manage Content -> Questionnaires'

3. Select new public/private item under BookmarkRating

4. Fill in with required values and create it.

5. After this if you go to bookmark rubric option it should be visible

'''c) Allowing Bookmark Rubric.'''

1. Login into the expertiza with the Instructor/TA credentials.

2. Go to 'Manage Content -> Assignments'

3. Select the appropriate project

4. Now edit the project.

5. Check the box "Allow participants to create bookmarks?" under Topics tab if not done already.

6. Choose the appropriate rubric from the list or create one following steps from above.

7. Now under Rubrics tab choose the "Scale" option for Scored-question display style.

== Future Work ==

1. A reviewer can be recognized or credited if he added useful bookmarks i.e if the author has made use of the bookmark.

2. A function to add badges automatically if a participant had submitted more than threshold number of useful bookmarks.

3. The UI is basic and it can be further improved.

== References ==

1. Expertiza on Github : https://github.com/rahuliyer95/expertiza

2. Videos on YouTube : https://youtu.be/F95FA9Iam0s, https://youtu.be/tPpowgNRINk

3. Pull Request : https://github.com/expertiza/expertiza/pull/1266

E1830 OSS Project Juniper: Bookmark enhancements

2018-11-09T19:17:10Z

Rkovilk:

'''Peer Review Information'''

For users intending to view the Expertiza Bookmark enhancement associated with this assignment, the credentials are below:

Instructor login: username -> instructor6, password -> password

Student Accounts for Impersonation : student6340, student6341; Assignment -> Exercises, CSC 456, Fall 2015

'''
== Introduction ==
'''

'''Expertiza Background'''

Expertiza is an open-source educational web application developed on Ruby on Rails platform. Students and Instructors (including TA's) use this application though their credentials. Instructors can add new projects, assignments etc as well edit the previous ones and at a later stage can see the student submission and grade them. They can even put a time limit (deadline) for submitting the assignment. Students can form teams for the projects, submit their work through handles (Wiki page, link to a video etc). Students can even review their teammates and other peers, as well give them any suggestions if required.

GitHub hooks to Expertiza to encourage contributors. Expertiza project is supported by National Science Foundation.

'''Description of the current project'''

This project is intended to make Bookmarks more user-friendly, credible and valid. Bookmarks in expertiza are created by reviewers and can be used by authors for their work on any project. On each line of the signup sheet are two icons, one for adding a bookmark to the topic, and another for viewing bookmarks on the topic. If the instructor allows the participants to create bookmarks, then only a participant has access to create and view them. He should be able to create a new Bookmark only if he enters a valid one.

Now a new rubric is added for reviewing the bookmarks added to a topic and this is accessible only to members belonging to the topic. Therefore ratings can be now done via a drop-down or rubric.

== Issues ==

'''Problem 1'''

When a user after logging into expertiza goes to 'Create New Bookmark page" or "View existing bookmarks page", he's not able to go back to Sign-up sheet using "back" button.

[[File:back.png]]

Solution :

[[File:fixed_back_link.png]]

'''Problem 2'''

Bookmarks had only one option while reviewing and it was to use a drop down to give a score. Also the average rating metric had a bug and hence showed wrong values even when bookmark was not reviewed. The bug was fixed and the rubric feature was adding a new controller.

Now choosing "Scale" Option instead of "Dropdown" allows one to use a rubric instead.

[[File:scale.png]]

The rubric for rating the bookmark shows up as a link that looks as follows :

[[File:begin_review.png]]

The rubric looks like :

[[File:bookmark_review_rubric.png]]

== Testing Plan ==

'''Scope of our changes'''

The changes made in this project affect the Bookmark Controller so tests are written for its validity.

Also we noticed that the Bookmark Model didn't have any testing done so we are planning to test that.

While manually testing for correctness we came the issue of average rating present even when no rating of the bookmark was added, additionally the computation of average had a bug and was hence giving wrong average value.

== Files modified in current project ==

'''''1. Fixing Average problem and adding Rubric feature :'''''

The following files were modified for fixing the average rating bug and adding rubric for the same.

app/models/bookmark_rating_response_map.rb

app/controllers/bookmark_rating_questionnaire_controller.rb

app/controllers/bookmarks_controller.rb

app/controllers/response_controller.rb

app/views/assignments/edit/_rubrics.html.erb

app/views/bookmarks/bookmark_rating.html.erb

app/views/bookmarks/list.html.erb

app/views/response/view.html.erb

config/routes.rb

'''''2. Tests for Model and Controller :'''''

spec/controllers/bookmarks_controller_spec.rb

spec/models/bookmark_spec.rb

spec/factories/factories.rb

== Automated & UI Testing ==

Automated RSpec tests were added to ensure the bookmarks are valid. Separate tests were written for the Bookmark Model and BookmarkRating Controller files.
The videos of the tests are uploaded onto YouTube and the links are provided in the references section.

Below shown is the coverage details

[[File:Coverage1.png]]

[[File:Coverage2.png]]

'''a) Back button for the page "View Bookmark" and "Create Bookmark" was resolved.'''

1. Login with the credentials to expertiza.

2. Go to 'My assignments' and select OSS Project/writeup.

3. Select 'Signup sheet'.

4. Many titles for projects are shown. Select a title and choose either 'View Bookmark' or 'Add Bookmark' button

5. If you choose 'View Bookmark', after viewing, press the back button to go back to Signup sheet.

6. You will land up in Sign-up sheet page.

7. If you choose 'Add Bookmark', you can add by giving Bookmark details and save it.

8. Now press back button.

9. You will land in Sign-up sheet page.

'''b) Adding Bookmark Rubric.'''

1. Login into the expertiza with the Instructor/TA credentials.

2. Go to 'Manage Content -> Questionnaires'

3. Select new public/private item under BookmarkRating

4. Fill in with required values and create it.

5. After this if you go to bookmark rubric option it should be visible

'''c) Allowing Bookmark Rubric.'''

1. Login into the expertiza with the Instructor/TA credentials.

2. Go to 'Manage Content -> Assignments'

3. Select the appropriate project

4. Now edit the project.

5. Check the box "Allow participants to create bookmarks?" under Topics tab if not done already.

6. Choose the appropriate rubric from the list or create one following steps from above.

7. Now under Rubrics tab choose the "Scale" option for Scored-question display style.

== Future Work ==

1. A reviewer can be recognized or credited if he added useful bookmarks i.e if the author has made use of the bookmark.

2. A function to add badges automatically if a participant had submitted more than threshold number of useful bookmarks.

3. The UI is basic and it can be further improved.

== References ==

1. Expertiza on Github : https://github.com/rahuliyer95/expertiza

2. Videos on YouTube : https://youtu.be/F95FA9Iam0s, https://youtu.be/tPpowgNRINk

3. Pull Request : https://github.com/expertiza/expertiza/pull/1266

E1830 OSS Project Juniper: Bookmark enhancements

2018-11-05T02:14:24Z

Rkovilk: /* Automated & UI Testing */

'''Peer Review Information'''

For users intending to view the Expertiza Bookmark enhancement associated with this assignment, the credentials are below:

Instructor login: username -> instructor6, password -> password

Student Accounts for Impersonation : student6340, student6341; Assignment -> Exercises, CSC 456, Fall 2015

'''
== Introduction ==
'''

'''Expertiza Background'''

Expertiza is an open-source educational web application developed on Ruby on Rails platform. Students and Instructors (including TA's) use this application though their credentials. Instructors can add new projects, assignments etc as well edit the previous ones and at a later stage can see the student submission and grade them. They can even put a time limit (deadline) for submitting the assignment. Students can form teams for the projects, submit their work through handles (Wiki page, link to a video etc). Students can even review their teammates and other peers, as well give them any suggestions if required.

GitHub hooks to Expertiza to encourage contributors. Expertiza project is supported by National Science Foundation.

'''Description of the current project'''

This project is intended to make Bookmarks more user-friendly, credible and valid. Bookmarks in expertiza are created by reviewers and can be used by authors for their work on any project. On each line of the signup sheet are two icons, one for adding a bookmark to the topic, and another for viewing bookmarks on the topic. If the instructor allows the participants to create bookmarks, then only a participant has access to create and view them. He should be able to create a new Bookmark only if he enters a valid one.

Now a new rubric is added for reviewing the bookmarks added to a topic and this is accessible only to members belonging to the topic. Therefore ratings can be now done via a drop-down or rubric.

== Issues ==

'''Problem 1'''

When a user after logging into expertiza goes to 'Create New Bookmark page" or "View existing bookmarks page", he's not able to go back to Sign-up sheet using "back" button.

[[File:back.png]]

Solution :

[[File:fixed_back_link.png]]

'''Problem 2'''

Bookmarks had only one option while reviewing and it was to use a drop down to give a score. Also the average rating metric had a bug and hence showed wrong values even when bookmark was not reviewed. The bug was fixed and the rubric feature was adding a new controller.

Now choosing "Scale" Option instead of "Dropdown" allows one to use a rubric instead.

[[File:scale.png]]

The rubric for rating the bookmark shows up as a link that looks as follows :

[[File:begin_review.png]]

The rubric looks like :

[[File:bookmark_review_rubric.png]]

== Files modified in current project ==

'''''1. Fixing Average problem and adding Rubric feature :'''''

The following files were modified for fixing the average rating bug and adding rubric for the same.

app/models/bookmark_rating_response_map.rb

app/controllers/bookmark_rating_questionnaire_controller.rb

app/controllers/bookmarks_controller.rb

app/controllers/response_controller.rb

app/views/assignments/edit/_rubrics.html.erb

app/views/bookmarks/bookmark_rating.html.erb

app/views/bookmarks/list.html.erb

app/views/response/view.html.erb

config/routes.rb

'''''2. Tests for Model and Controller :'''''

spec/controllers/bookmarks_controller_spec.rb

spec/models/bookmark_spec.rb

spec/factories/factories.rb

== Automated & UI Testing ==

Automated RSpec tests were added to ensure the bookmarks are valid. Separate tests were written for the Bookmark Model and BookmarkRating Controller files.
The videos of the tests are uploaded onto YouTube and the links are provided in the references section.

Below shown is the coverage details

[[File:Coverage1.png]]

[[File:Coverage2.png]]

'''a) Back button for the page "View Bookmark" and "Create Bookmark" was resolved.'''

1. Login with the credentials to expertiza.

2. Go to 'My assignments' and select OSS Project/writeup.

3. Select 'Signup sheet'.

4. Many titles for projects are shown. Select a title and choose either 'View Bookmark' or 'Add Bookmark' button

5. If you choose 'View Bookmark', after viewing, press the back button to go back to Signup sheet.

6. You will land up in Sign-up sheet page.

7. If you choose 'Add Bookmark', you can add by giving Bookmark details and save it.

8. Now press back button.

9. You will land in Sign-up sheet page.

'''b) Adding Bookmark Rubric.'''

1. Login into the expertiza with the Instructor/TA credentials.

2. Go to 'Manage Content -> Questionnaires'

3. Select new public/private item under BookmarkRating

4. Fill in with required values and create it.

5. After this if you go to bookmark rubric option it should be visible

'''c) Allowing Bookmark Rubric.'''

1. Login into the expertiza with the Instructor/TA credentials.

2. Go to 'Manage Content -> Assignments'

3. Select the appropriate project

4. Now edit the project.

5. Check the box "Allow participants to create bookmarks?" under Topics tab if not done already.

6. Choose the appropriate rubric from the list or create one following steps from above.

7. Now under Rubrics tab choose the "Scale" option for Scored-question display style.

== Future Work ==

1. A reviewer can be recognized or credited if he added useful bookmarks i.e if the author has made use of the bookmark.

2. A function to add badges automatically if a participant had submitted more than threshold number of useful bookmarks.

3. The UI is basic and it can be further improved.

== References ==

1. Expertiza on Github : https://github.com/rahuliyer95/expertiza

2. Videos on YouTube : https://youtu.be/F95FA9Iam0s, https://youtu.be/tPpowgNRINk

3. Pull Request : https://github.com/expertiza/expertiza/pull/1266

File:Coverage2.png

2018-11-05T02:13:09Z

Rkovilk:

File:Coverage1.png

2018-11-05T02:12:11Z

Rkovilk:

E1830 OSS Project Juniper: Bookmark enhancements

2018-11-05T02:11:34Z

Rkovilk: /* Automated & UI Testing */

'''Peer Review Information'''

For users intending to view the Expertiza Bookmark enhancement associated with this assignment, the credentials are below:

Instructor login: username -> instructor6, password -> password

Student Accounts for Impersonation : student6340, student6341; Assignment -> Exercises, CSC 456, Fall 2015

'''
== Introduction ==
'''

'''Expertiza Background'''

Expertiza is an open-source educational web application developed on Ruby on Rails platform. Students and Instructors (including TA's) use this application though their credentials. Instructors can add new projects, assignments etc as well edit the previous ones and at a later stage can see the student submission and grade them. They can even put a time limit (deadline) for submitting the assignment. Students can form teams for the projects, submit their work through handles (Wiki page, link to a video etc). Students can even review their teammates and other peers, as well give them any suggestions if required.

GitHub hooks to Expertiza to encourage contributors. Expertiza project is supported by National Science Foundation.

'''Description of the current project'''

This project is intended to make Bookmarks more user-friendly, credible and valid. Bookmarks in expertiza are created by reviewers and can be used by authors for their work on any project. On each line of the signup sheet are two icons, one for adding a bookmark to the topic, and another for viewing bookmarks on the topic. If the instructor allows the participants to create bookmarks, then only a participant has access to create and view them. He should be able to create a new Bookmark only if he enters a valid one.

Now a new rubric is added for reviewing the bookmarks added to a topic and this is accessible only to members belonging to the topic. Therefore ratings can be now done via a drop-down or rubric.

== Issues ==

'''Problem 1'''

When a user after logging into expertiza goes to 'Create New Bookmark page" or "View existing bookmarks page", he's not able to go back to Sign-up sheet using "back" button.

[[File:back.png]]

Solution :

[[File:fixed_back_link.png]]

'''Problem 2'''

Bookmarks had only one option while reviewing and it was to use a drop down to give a score. Also the average rating metric had a bug and hence showed wrong values even when bookmark was not reviewed. The bug was fixed and the rubric feature was adding a new controller.

Now choosing "Scale" Option instead of "Dropdown" allows one to use a rubric instead.

[[File:scale.png]]

The rubric for rating the bookmark shows up as a link that looks as follows :

[[File:begin_review.png]]

The rubric looks like :

[[File:bookmark_review_rubric.png]]

== Files modified in current project ==

'''''1. Fixing Average problem and adding Rubric feature :'''''

The following files were modified for fixing the average rating bug and adding rubric for the same.

app/models/bookmark_rating_response_map.rb

app/controllers/bookmark_rating_questionnaire_controller.rb

app/controllers/bookmarks_controller.rb

app/controllers/response_controller.rb

app/views/assignments/edit/_rubrics.html.erb

app/views/bookmarks/bookmark_rating.html.erb

app/views/bookmarks/list.html.erb

app/views/response/view.html.erb

config/routes.rb

'''''2. Tests for Model and Controller :'''''

spec/controllers/bookmarks_controller_spec.rb

spec/models/bookmark_spec.rb

spec/factories/factories.rb

== Automated & UI Testing ==

Automated RSpec tests were added to ensure the bookmarks are valid. Separate tests were written for the Bookmark Model and BookmarkRating Controller files.
The videos of the tests are uploaded onto YouTube and the links are provided in the references section.

Below shown is the coverage details

[[File:Coverage1.png]]

[[File:Coverage2.png]]

'''a) Back button for the page "View Bookmark" and "Create Bookmark" was resolved.'''

1. Login with the credentials to expertiza.

2. Go to 'My assignments' and select OSS Project/writeup.

3. Select 'Signup sheet'.

4. Many titles for projects are shown. Select a title and choose either 'View Bookmark' or 'Add Bookmark' button

5. If you choose 'View Bookmark', after viewing, press the back button to go back to Signup sheet.

6. You will land up in Sign-up sheet page.

7. If you choose 'Add Bookmark', you can add by giving Bookmark details and save it.

8. Now press back button.

9. You will land in Sign-up sheet page.

'''b) Adding Bookmark Rubric.'''

1. Login into the expertiza with the Instructor/TA credentials.

2. Go to 'Manage Content -> Questionnaires'

3. Select new public/private item under BookmarkRating

4. Fill in with required values and create it.

5. After this if you go to bookmark rubric option it should be visible

'''c) Allowing Bookmark Rubric.'''

1. Login into the expertiza with the Instructor/TA credentials.

2. Go to 'Manage Content -> Assignments'

3. Select the appropriate project

4. Now edit the project.

5. Check the box "Allow participants to create bookmarks?" under Topics tab if not done already.

6. Choose the appropriate rubric from the list or create one following steps from above.

7. Now under Rubrics tab choose the "Scale" option for Scored-question display style.

== Future Work ==

1. A reviewer can be recognized or credited if he added useful bookmarks i.e if the author has made use of the bookmark.

2. A function to add badges automatically if a participant had submitted more than threshold number of useful bookmarks.

3. The UI is basic and it can be further improved.

== References ==

1. Expertiza on Github : https://github.com/rahuliyer95/expertiza

2. Videos on YouTube : https://youtu.be/F95FA9Iam0s, https://youtu.be/tPpowgNRINk

3. Pull Request : https://github.com/expertiza/expertiza/pull/1266

E1830 OSS Project Juniper: Bookmark enhancements

2018-11-02T23:07:12Z

Rkovilk: /* Automated & UI Testing */

'''Peer Review Information'''

For users intending to view the Expertiza Bookmark enhancement associated with this assignment, the credentials are below:

Instructor login: username -> instructor6, password -> password

Student Accounts for Impersonation : student6340, student6341; Assignment -> Exercises, CSC 456, Fall 2015

'''
== Introduction ==
'''

'''Expertiza Background'''

Expertiza is an open-source educational web application developed on Ruby on Rails platform. Students and Instructors (including TA's) use this application though their credentials. Instructors can add new projects, assignments etc as well edit the previous ones and at a later stage can see the student submission and grade them. They can even put a time limit (deadline) for submitting the assignment. Students can form teams for the projects, submit their work through handles (Wiki page, link to a video etc). Students can even review their teammates and other peers, as well give them any suggestions if required.

GitHub hooks to Expertiza to encourage contributors. Expertiza project is supported by National Science Foundation.

'''Description of the current project'''

This project is intended to make Bookmarks more user-friendly, credible and valid. Bookmarks in expertiza are created by reviewers and can be used by authors for their work on any project. On each line of the signup sheet are two icons, one for adding a bookmark to the topic, and another for viewing bookmarks on the topic. If the instructor allows the participants to create bookmarks, then only a participant has access to create and view them. He should be able to create a new Bookmark only if he enters a valid one.

Now a new rubric is added for reviewing the bookmarks added to a topic and this is accessible only to members belonging to the topic. Therefore ratings can be now done via a drop-down or rubric.

== Issues ==

'''Problem 1'''

When a user after logging into expertiza goes to 'Create New Bookmark page" or "View existing bookmarks page", he's not able to go back to Sign-up sheet using "back" button.

[[File:back.png]]

Solution :

[[File:fixed_back_link.png]]

'''Problem 2'''

Bookmarks had only one option while reviewing and it was to use a drop down to give a score. Also the average rating metric had a bug and hence showed wrong values even when bookmark was not reviewed. The bug was fixed and the rubric feature was adding a new controller.

Now choosing "Scale" Option instead of "Dropdown" allows one to use a rubric instead.

[[File:scale.png]]

The rubric for rating the bookmark shows up as a link that looks as follows :

[[File:begin_review.png]]

The rubric looks like :

[[File:bookmark_review_rubric.png]]

== Files modified in current project ==

'''''1. Fixing Average problem and adding Rubric feature :'''''

The following files were modified for fixing the average rating bug and adding rubric for the same.

app/models/bookmark_rating_response_map.rb

app/controllers/bookmark_rating_questionnaire_controller.rb

app/controllers/bookmarks_controller.rb

app/controllers/response_controller.rb

app/views/assignments/edit/_rubrics.html.erb

app/views/bookmarks/bookmark_rating.html.erb

app/views/bookmarks/list.html.erb

app/views/response/view.html.erb

config/routes.rb

'''''2. Tests for Model and Controller :'''''

spec/controllers/bookmarks_controller_spec.rb

spec/models/bookmark_spec.rb

spec/factories/factories.rb

== Automated & UI Testing ==

Automated RSpec tests were added to ensure the bookmarks are valid. Separate tests were written for the Bookmark Model and BookmarkRating Controller files.
The videos of the tests are uploaded onto YouTube and the links are provided in the references section.

'''a) Back button for the page "View Bookmark" and "Create Bookmark" was resolved.'''

1. Login with the credentials to expertiza.

2. Go to 'My assignments' and select OSS Project/writeup.

3. Select 'Signup sheet'.

4. Many titles for projects are shown. Select a title and choose either 'View Bookmark' or 'Add Bookmark' button

5. If you choose 'View Bookmark', after viewing, press the back button to go back to Signup sheet.

6. You will land up in Sign-up sheet page.

7. If you choose 'Add Bookmark', you can add by giving Bookmark details and save it.

8. Now press back button.

9. You will land in Sign-up sheet page.

'''b) Adding Bookmark Rubric.'''

1. Login into the expertiza with the Instructor/TA credentials.

2. Go to 'Manage Content -> Questionnaires'

3. Select new public/private item under BookmarkRating

4. Fill in with required values and create it.

5. After this if you go to bookmark rubric option it should be visible

'''c) Allowing Bookmark Rubric.'''

1. Login into the expertiza with the Instructor/TA credentials.

2. Go to 'Manage Content -> Assignments'

3. Select the appropriate project

4. Now edit the project.

5. Check the box "Allow participants to create bookmarks?" under Topics tab if not done already.

6. Choose the appropriate rubric from the list or create one following steps from above.

7. Now under Rubrics tab choose the "Scale" option for Scored-question display style.

== Future Work ==

1. A reviewer can be recognized or credited if he added useful bookmarks i.e if the author has made use of the bookmark.

2. A function to add badges automatically if a participant had submitted more than threshold number of useful bookmarks.

3. The UI is basic and it can be further improved.

== References ==

1. Expertiza on Github : https://github.com/rahuliyer95/expertiza

2. Videos on YouTube : https://youtu.be/F95FA9Iam0s, https://youtu.be/tPpowgNRINk

3. Pull Request : https://github.com/expertiza/expertiza/pull/1266

E1830 OSS Project Juniper: Bookmark enhancements

2018-11-02T23:06:30Z

Rkovilk:

'''Peer Review Information'''

For users intending to view the Expertiza Bookmark enhancement associated with this assignment, the credentials are below:

Instructor login: username -> instructor6, password -> password

Student Accounts for Impersonation : student6340, student6341; Assignment -> Exercises, CSC 456, Fall 2015

'''
== Introduction ==
'''

'''Expertiza Background'''

Expertiza is an open-source educational web application developed on Ruby on Rails platform. Students and Instructors (including TA's) use this application though their credentials. Instructors can add new projects, assignments etc as well edit the previous ones and at a later stage can see the student submission and grade them. They can even put a time limit (deadline) for submitting the assignment. Students can form teams for the projects, submit their work through handles (Wiki page, link to a video etc). Students can even review their teammates and other peers, as well give them any suggestions if required.

GitHub hooks to Expertiza to encourage contributors. Expertiza project is supported by National Science Foundation.

'''Description of the current project'''

This project is intended to make Bookmarks more user-friendly, credible and valid. Bookmarks in expertiza are created by reviewers and can be used by authors for their work on any project. On each line of the signup sheet are two icons, one for adding a bookmark to the topic, and another for viewing bookmarks on the topic. If the instructor allows the participants to create bookmarks, then only a participant has access to create and view them. He should be able to create a new Bookmark only if he enters a valid one.

Now a new rubric is added for reviewing the bookmarks added to a topic and this is accessible only to members belonging to the topic. Therefore ratings can be now done via a drop-down or rubric.

== Issues ==

'''Problem 1'''

When a user after logging into expertiza goes to 'Create New Bookmark page" or "View existing bookmarks page", he's not able to go back to Sign-up sheet using "back" button.

[[File:back.png]]

Solution :

[[File:fixed_back_link.png]]

'''Problem 2'''

Bookmarks had only one option while reviewing and it was to use a drop down to give a score. Also the average rating metric had a bug and hence showed wrong values even when bookmark was not reviewed. The bug was fixed and the rubric feature was adding a new controller.

Now choosing "Scale" Option instead of "Dropdown" allows one to use a rubric instead.

[[File:scale.png]]

The rubric for rating the bookmark shows up as a link that looks as follows :

[[File:begin_review.png]]

The rubric looks like :

[[File:bookmark_review_rubric.png]]

== Files modified in current project ==

'''''1. Fixing Average problem and adding Rubric feature :'''''

The following files were modified for fixing the average rating bug and adding rubric for the same.

app/models/bookmark_rating_response_map.rb

app/controllers/bookmark_rating_questionnaire_controller.rb

app/controllers/bookmarks_controller.rb

app/controllers/response_controller.rb

app/views/assignments/edit/_rubrics.html.erb

app/views/bookmarks/bookmark_rating.html.erb

app/views/bookmarks/list.html.erb

app/views/response/view.html.erb

config/routes.rb

'''''2. Tests for Model and Controller :'''''

spec/controllers/bookmarks_controller_spec.rb

spec/models/bookmark_spec.rb

spec/factories/factories.rb

== Automated & UI Testing ==

Automated RSpec tests were added to ensure the bookmarks are valid. Separate tests were written for the Bookmark Model and BookmarkRating Controller files.
The videos of the tests are uploaded onto YouTube and the links are provided in the references section.

'''a) Back button for the page "View Bookmark" and "Create Bookmark" was resolved.'''

1. Login with the credentials to expertiza.

2. Go to 'My assignments' and select OSS Project/writeup.

3. Select 'Signup sheet'.

4. Many titles for projects are shown. Select a title and choose either 'View Bookmark' or 'Add Bookmark' button

5. If you choose 'View Bookmark', after viewing, press the back button to go back to Signup sheet.

6. You will land up in Sign-up sheet page.

7. If you choose 'Add Bookmark', you can add by giving Bookmark details and save it.

8. Now press back button.

9. You will land in Sign-up sheet page.

'''b) Adding Bookmark Rubric.'''

1. Login into the expertiza with the Instructor/TA credentials.

2. Go to 'Manage Content -> Questionnaires'

3. Select new public/private item under BookmarkRating

4. Fill in with required values and create it.

5. After this if you go to bookmark rubric option it should be visible

'''c) Allowing Bookmark Rubric.'''

1. Login into the expertiza with the Instructor/TA credentials.

2. Go to 'Manage Content -> Assignments'

3. Select the appropriate project

4. Now edit the project.

5. Check the box "Allow participants to create bookmarks?" under Topics tab if not done already.

6. Choose the appropriate rubric from the list or create one following steps from above.

7. Now under Rubrics tab choose the "Scale" option for Scored-question display style.

== Future Work ==

1. A reviewer can be recognized or credited if he added useful bookmarks i.e if the author has made use of the bookmark.

2. A function to add badges automatically if a participant had submitted more than threshold number of useful bookmarks.

3. The UI is basic and it can be further improved.

== References ==

1. Expertiza on Github : https://github.com/rahuliyer95/expertiza

2. Videos on YouTube : https://youtu.be/F95FA9Iam0s, https://youtu.be/tPpowgNRINk

3. Pull Request : https://github.com/expertiza/expertiza/pull/1266

File:Bookmark review rubric.png

2018-11-02T23:02:06Z

Rkovilk:

E1830 OSS Project Juniper: Bookmark enhancements

2018-11-02T23:01:43Z

Rkovilk: /* Issues */

'''Peer Review Information'''

For users intending to view the Expertiza Bookmark enhancement associated with this assignment, the credentials are below:

Instructor login: username -> instructor6, password -> password

'''
== Introduction ==
'''

'''Expertiza Background'''

Expertiza is an open-source educational web application developed on Ruby on Rails platform. Students and Instructors (including TA's) use this application though their credentials. Instructors can add new projects, assignments etc as well edit the previous ones and at a later stage can see the student submission and grade them. They can even put a time limit (deadline) for submitting the assignment. Students can form teams for the projects, submit their work through handles (Wiki page, link to a video etc). Students can even review their teammates and other peers, as well give them any suggestions if required.

GitHub hooks to Expertiza to encourage contributors. Expertiza project is supported by National Science Foundation.

'''Description of the current project'''

This project is intended to make Bookmarks more user-friendly, credible and valid. Bookmarks in expertiza are created by reviewers and can be used by authors for their work on any project. On each line of the signup sheet are two icons, one for adding a bookmark to the topic, and another for viewing bookmarks on the topic. If the instructor allows the participants to create bookmarks, then only a participant has access to create and view them. He should be able to create a new Bookmark only if he enters a valid one.

Now a new rubric is added for reviewing the bookmarks added to a topic and this is accessible only to members belonging to the topic. Therefore ratings can be now done via a drop-down or rubric.

== Issues ==

'''Problem 1'''

When a user after logging into expertiza goes to 'Create New Bookmark page" or "View existing bookmarks page", he's not able to go back to Sign-up sheet using "back" button.

[[File:back.png]]

Solution :

[[File:fixed_back_link.png]]

'''Problem 2'''

Bookmarks had only one option while reviewing and it was to use a drop down to give a score. Also the average rating metric had a bug and hence showed wrong values even when bookmark was not reviewed. The bug was fixed and the rubric feature was adding a new controller.

Now choosing "Scale" Option instead of "Dropdown" allows one to use a rubric instead.

[[File:scale.png]]

The rubric for rating the bookmark shows up as a link that looks as follows :

[[File:begin_review.png]]

The rubric looks like :

[[File:bookmark_review_rubric.png]]

== Files modified in current project ==

'''''1. Fixing Average problem and adding Rubric feature :'''''

The following files were modified for fixing the average rating bug and adding rubric for the same.

app/models/bookmark_rating_response_map.rb

app/controllers/bookmark_rating_questionnaire_controller.rb

app/controllers/bookmarks_controller.rb

app/controllers/response_controller.rb

app/views/assignments/edit/_rubrics.html.erb

app/views/bookmarks/bookmark_rating.html.erb

app/views/bookmarks/list.html.erb

app/views/response/view.html.erb

config/routes.rb

'''''2. Tests for Model and Controller :'''''

spec/controllers/bookmarks_controller_spec.rb

spec/models/bookmark_spec.rb

spec/factories/factories.rb

== Automated & UI Testing ==

Automated RSpec tests were added to ensure the bookmarks are valid. Separate tests were written for the Bookmark Model and BookmarkRating Controller files.
The videos of the tests are uploaded onto YouTube and the links are provided in the references section.

'''a) Back button for the page "View Bookmark" and "Create Bookmark" was resolved.'''

1. Login with the credentials to expertiza.

2. Go to 'My assignments' and select OSS Project/writeup.

3. Select 'Signup sheet'.

4. Many titles for projects are shown. Select a title and choose either 'View Bookmark' or 'Add Bookmark' button

5. If you choose 'View Bookmark', after viewing, press the back button to go back to Signup sheet.

6. You will land up in Sign-up sheet page.

7. If you choose 'Add Bookmark', you can add by giving Bookmark details and save it.

8. Now press back button.

9. You will land in Sign-up sheet page.

'''b) Adding Bookmark Rubric.'''

1. Login into the expertiza with the Instructor/TA credentials.

2. Go to 'Manage Content -> Questionnaires'

3. Select new public/private item under BookmarkRating

4. Fill in with required values and create it.

5. After this if you go to bookmark rubric option it should be visible

'''c) Allowing Bookmark Rubric.'''

1. Login into the expertiza with the Instructor/TA credentials.

2. Go to 'Manage Content -> Assignments'

3. Select the appropriate project

4. Now edit the project.

5. Check the box "Allow participants to create bookmarks?" under Topics tab if not done already.

6. Choose the appropriate rubric from the list or create one following steps from above.

7. Now under Rubrics tab choose the "Scale" option for Scored-question display style.

== Future Work ==

1. A reviewer can be recognized or credited if he added useful bookmarks i.e if the author has made use of the bookmark.

2. A function to add badges automatically if a participant had submitted more than threshold number of useful bookmarks.

3. The UI is basic and it can be further improved.

== References ==

1. Expertiza on Github : https://github.com/rahuliyer95/expertiza

2. Videos on YouTube : https://youtu.be/F95FA9Iam0s, https://youtu.be/tPpowgNRINk

3. Pull Request : https://github.com/expertiza/expertiza/pull/1266

E1830 OSS Project Juniper: Bookmark enhancements

2018-11-02T22:59:38Z

Rkovilk: /* Introduction */

'''Peer Review Information'''

For users intending to view the Expertiza Bookmark enhancement associated with this assignment, the credentials are below:

Instructor login: username -> instructor6, password -> password

'''
== Introduction ==
'''

'''Expertiza Background'''

Expertiza is an open-source educational web application developed on Ruby on Rails platform. Students and Instructors (including TA's) use this application though their credentials. Instructors can add new projects, assignments etc as well edit the previous ones and at a later stage can see the student submission and grade them. They can even put a time limit (deadline) for submitting the assignment. Students can form teams for the projects, submit their work through handles (Wiki page, link to a video etc). Students can even review their teammates and other peers, as well give them any suggestions if required.

GitHub hooks to Expertiza to encourage contributors. Expertiza project is supported by National Science Foundation.

'''Description of the current project'''

This project is intended to make Bookmarks more user-friendly, credible and valid. Bookmarks in expertiza are created by reviewers and can be used by authors for their work on any project. On each line of the signup sheet are two icons, one for adding a bookmark to the topic, and another for viewing bookmarks on the topic. If the instructor allows the participants to create bookmarks, then only a participant has access to create and view them. He should be able to create a new Bookmark only if he enters a valid one.

Now a new rubric is added for reviewing the bookmarks added to a topic and this is accessible only to members belonging to the topic. Therefore ratings can be now done via a drop-down or rubric.

== Issues ==

'''Problem 1'''

When a user after logging into expertiza goes to 'Create New Bookmark page" or "View existing bookmarks page", he's not able to go back to Sign-up sheet using "back" button.

[[File:back.png]]

Solution :

[[File:fixed_back_link.png]]

'''Problem 2'''

Bookmarks had only one option while reviewing and it was to use a drop down to give a score. Also the average rating metric had a bug and hence showed wrong values even when bookmark was not reviewed. The bug was fixed and the rubric feature was adding a new controller.

Now choosing "Scale" Option instead of "Dropdown" allows one to use a rubric instead.

[[File:scale.png]]

The rubric for rating the bookmark looks as follows :

[[File:begin_review.png]]

== Files modified in current project ==

'''''1. Fixing Average problem and adding Rubric feature :'''''

The following files were modified for fixing the average rating bug and adding rubric for the same.

app/models/bookmark_rating_response_map.rb

app/controllers/bookmark_rating_questionnaire_controller.rb

app/controllers/bookmarks_controller.rb

app/controllers/response_controller.rb

app/views/assignments/edit/_rubrics.html.erb

app/views/bookmarks/bookmark_rating.html.erb

app/views/bookmarks/list.html.erb

app/views/response/view.html.erb

config/routes.rb

'''''2. Tests for Model and Controller :'''''

spec/controllers/bookmarks_controller_spec.rb

spec/models/bookmark_spec.rb

spec/factories/factories.rb

== Automated & UI Testing ==

Automated RSpec tests were added to ensure the bookmarks are valid. Separate tests were written for the Bookmark Model and BookmarkRating Controller files.
The videos of the tests are uploaded onto YouTube and the links are provided in the references section.

'''a) Back button for the page "View Bookmark" and "Create Bookmark" was resolved.'''

1. Login with the credentials to expertiza.

2. Go to 'My assignments' and select OSS Project/writeup.

3. Select 'Signup sheet'.

4. Many titles for projects are shown. Select a title and choose either 'View Bookmark' or 'Add Bookmark' button

5. If you choose 'View Bookmark', after viewing, press the back button to go back to Signup sheet.

6. You will land up in Sign-up sheet page.

7. If you choose 'Add Bookmark', you can add by giving Bookmark details and save it.

8. Now press back button.

9. You will land in Sign-up sheet page.

'''b) Adding Bookmark Rubric.'''

1. Login into the expertiza with the Instructor/TA credentials.

2. Go to 'Manage Content -> Questionnaires'

3. Select new public/private item under BookmarkRating

4. Fill in with required values and create it.

5. After this if you go to bookmark rubric option it should be visible

'''c) Allowing Bookmark Rubric.'''

1. Login into the expertiza with the Instructor/TA credentials.

2. Go to 'Manage Content -> Assignments'

3. Select the appropriate project

4. Now edit the project.

5. Check the box "Allow participants to create bookmarks?" under Topics tab if not done already.

6. Choose the appropriate rubric from the list or create one following steps from above.

7. Now under Rubrics tab choose the "Scale" option for Scored-question display style.

== Future Work ==

1. A reviewer can be recognized or credited if he added useful bookmarks i.e if the author has made use of the bookmark.

2. A function to add badges automatically if a participant had submitted more than threshold number of useful bookmarks.

3. The UI is basic and it can be further improved.

== References ==

1. Expertiza on Github : https://github.com/rahuliyer95/expertiza

2. Videos on YouTube : https://youtu.be/F95FA9Iam0s, https://youtu.be/tPpowgNRINk

3. Pull Request : https://github.com/expertiza/expertiza/pull/1266

E1830 OSS Project Juniper: Bookmark enhancements

2018-11-02T22:55:45Z

Rkovilk: /* Automated & UI Testing */

'''Peer Review Information'''

For users intending to view the Expertiza Bookmark enhancement associated with this assignment, the credentials are below:

Instructor login: username -> instructor6, password -> password

'''
== Introduction ==
'''

'''Expertiza Background'''

Expertiza is an open-source educational web application developed on Ruby on Rails platform. Students and Instructors (including TA's) use this application though their credentials. Instructors can add new projects, assignments etc as well edit the previous ones and at a later stage can see the student submission and grade them. They can even put a time limit (deadline) for submitting the assignment. Students can form teams for the projects, submit their work through handles (Wiki page, link to a video etc). Students can even review their teammates and other peers, as well give them any suggestions if required.

GitHub hooks to Expertiza to encourage contributors. Expertiza project is supported by National Science Foundation.

'''Description of the current project'''

This project is intended to make Bookmarks more user-friendly, credible and valid. Bookmarks in expertiza are created by reviewers and can be used by authors for their work on any project. On each line of the signup sheet are two icons, one for adding a bookmark to the topic, and another for viewing bookmarks on the topic. If the instructor allows the participants to create bookmarks, then only a participant has access to create and view them. He should be able to create a new Bookmark only if he enters a valid one.

Now a new rubric is added for reviewing the bookmarks added to a topic and is accessible only to members belonging to the topic.
Tests are written to ensure validity of the bookmark feature.

== Issues ==

'''Problem 1'''

When a user after logging into expertiza goes to 'Create New Bookmark page" or "View existing bookmarks page", he's not able to go back to Sign-up sheet using "back" button.

[[File:back.png]]

Solution :

[[File:fixed_back_link.png]]

'''Problem 2'''

Bookmarks had only one option while reviewing and it was to use a drop down to give a score. Also the average rating metric had a bug and hence showed wrong values even when bookmark was not reviewed. The bug was fixed and the rubric feature was adding a new controller.

Now choosing "Scale" Option instead of "Dropdown" allows one to use a rubric instead.

[[File:scale.png]]

The rubric for rating the bookmark looks as follows :

[[File:begin_review.png]]

== Files modified in current project ==

'''''1. Fixing Average problem and adding Rubric feature :'''''

The following files were modified for fixing the average rating bug and adding rubric for the same.

app/models/bookmark_rating_response_map.rb

app/controllers/bookmark_rating_questionnaire_controller.rb

app/controllers/bookmarks_controller.rb

app/controllers/response_controller.rb

app/views/assignments/edit/_rubrics.html.erb

app/views/bookmarks/bookmark_rating.html.erb

app/views/bookmarks/list.html.erb

app/views/response/view.html.erb

config/routes.rb

'''''2. Tests for Model and Controller :'''''

spec/controllers/bookmarks_controller_spec.rb

spec/models/bookmark_spec.rb

spec/factories/factories.rb

== Automated & UI Testing ==

Automated RSpec tests were added to ensure the bookmarks are valid. Separate tests were written for the Bookmark Model and BookmarkRating Controller files.
The videos of the tests are uploaded onto YouTube and the links are provided in the references section.

'''a) Back button for the page "View Bookmark" and "Create Bookmark" was resolved.'''

1. Login with the credentials to expertiza.

2. Go to 'My assignments' and select OSS Project/writeup.

3. Select 'Signup sheet'.

4. Many titles for projects are shown. Select a title and choose either 'View Bookmark' or 'Add Bookmark' button

5. If you choose 'View Bookmark', after viewing, press the back button to go back to Signup sheet.

6. You will land up in Sign-up sheet page.

7. If you choose 'Add Bookmark', you can add by giving Bookmark details and save it.

8. Now press back button.

9. You will land in Sign-up sheet page.

'''b) Adding Bookmark Rubric.'''

1. Login into the expertiza with the Instructor/TA credentials.

2. Go to 'Manage Content -> Questionnaires'

3. Select new public/private item under BookmarkRating

4. Fill in with required values and create it.

5. After this if you go to bookmark rubric option it should be visible

'''c) Allowing Bookmark Rubric.'''

1. Login into the expertiza with the Instructor/TA credentials.

2. Go to 'Manage Content -> Assignments'

3. Select the appropriate project

4. Now edit the project.

5. Check the box "Allow participants to create bookmarks?" under Topics tab if not done already.

6. Choose the appropriate rubric from the list or create one following steps from above.

7. Now under Rubrics tab choose the "Scale" option for Scored-question display style.

== Future Work ==

1. A reviewer can be recognized or credited if he added useful bookmarks i.e if the author has made use of the bookmark.

2. A function to add badges automatically if a participant had submitted more than threshold number of useful bookmarks.

3. The UI is basic and it can be further improved.

== References ==

1. Expertiza on Github : https://github.com/rahuliyer95/expertiza

2. Videos on YouTube : https://youtu.be/F95FA9Iam0s, https://youtu.be/tPpowgNRINk

3. Pull Request : https://github.com/expertiza/expertiza/pull/1266

E1830 OSS Project Juniper: Bookmark enhancements

2018-11-02T22:55:00Z

Rkovilk: /* References */

'''Peer Review Information'''

For users intending to view the Expertiza Bookmark enhancement associated with this assignment, the credentials are below:

Instructor login: username -> instructor6, password -> password

'''
== Introduction ==
'''

'''Expertiza Background'''

Expertiza is an open-source educational web application developed on Ruby on Rails platform. Students and Instructors (including TA's) use this application though their credentials. Instructors can add new projects, assignments etc as well edit the previous ones and at a later stage can see the student submission and grade them. They can even put a time limit (deadline) for submitting the assignment. Students can form teams for the projects, submit their work through handles (Wiki page, link to a video etc). Students can even review their teammates and other peers, as well give them any suggestions if required.

GitHub hooks to Expertiza to encourage contributors. Expertiza project is supported by National Science Foundation.

'''Description of the current project'''

This project is intended to make Bookmarks more user-friendly, credible and valid. Bookmarks in expertiza are created by reviewers and can be used by authors for their work on any project. On each line of the signup sheet are two icons, one for adding a bookmark to the topic, and another for viewing bookmarks on the topic. If the instructor allows the participants to create bookmarks, then only a participant has access to create and view them. He should be able to create a new Bookmark only if he enters a valid one.

Now a new rubric is added for reviewing the bookmarks added to a topic and is accessible only to members belonging to the topic.
Tests are written to ensure validity of the bookmark feature.

== Issues ==

'''Problem 1'''

When a user after logging into expertiza goes to 'Create New Bookmark page" or "View existing bookmarks page", he's not able to go back to Sign-up sheet using "back" button.

[[File:back.png]]

Solution :

[[File:fixed_back_link.png]]

'''Problem 2'''

Bookmarks had only one option while reviewing and it was to use a drop down to give a score. Also the average rating metric had a bug and hence showed wrong values even when bookmark was not reviewed. The bug was fixed and the rubric feature was adding a new controller.

Now choosing "Scale" Option instead of "Dropdown" allows one to use a rubric instead.

[[File:scale.png]]

The rubric for rating the bookmark looks as follows :

[[File:begin_review.png]]

== Files modified in current project ==

'''''1. Fixing Average problem and adding Rubric feature :'''''

The following files were modified for fixing the average rating bug and adding rubric for the same.

app/models/bookmark_rating_response_map.rb

app/controllers/bookmark_rating_questionnaire_controller.rb

app/controllers/bookmarks_controller.rb

app/controllers/response_controller.rb

app/views/assignments/edit/_rubrics.html.erb

app/views/bookmarks/bookmark_rating.html.erb

app/views/bookmarks/list.html.erb

app/views/response/view.html.erb

config/routes.rb

'''''2. Tests for Model and Controller :'''''

spec/controllers/bookmarks_controller_spec.rb

spec/models/bookmark_spec.rb

spec/factories/factories.rb

== Automated & UI Testing ==

Automated RSpec tests were added to ensure the bookmarks are valid. Separate tests were written for the Bookmark Model and BookmarkRating Controller files.
The videos of the tests are uploaded onto YouTube and the links are provided in the references section.

'''a) Back button for the page "View Bookmark" and "Create Bookmark" was resolved.'''

1. Login with the credentials to expertiza.

2. Go to 'My assignments' and select OSS Project/writeup.

3. Select 'Signup sheet'.

4. Many titles for projects are shown. Select a title and choose either 'View Bookmark' or 'Add Bookmark' button

5. If you choose 'View Bookmark', after viewing, press the back button to go back to Signup sheet.

6. You will land up in Sign-up sheet page.

7. If you choose 'Add Bookmark', you can add by giving Bookmark details and save it.

8. Now press back button.

9. You will land in Sign-up sheet page.

'''c) Adding Bookmark Rubric.'''

1. Login into the expertiza with the Instructor/TA credentials.

2. Go to 'Manage Content -> Questionnaires'

3. Select new public/private item under BookmarkRating

4. Fill in with required values and create it.

5. After this if you go to bookmark rubric option it should be visible

'''c) Allowing Bookmark Rubric.'''

1. Login into the expertiza with the Instructor/TA credentials.

2. Go to 'Manage Content -> Assignments'

3. Select the appropriate project

4. Now edit the project.

5. Check the box "Allow participants to create bookmarks?" under Topics tab if not done already.

6. Choose the appropriate rubric from the list or create one following steps from above.

7. Now under Rubrics tab choose the "Scale" option for Scored-question display style.

== Future Work ==

1. A reviewer can be recognized or credited if he added useful bookmarks i.e if the author has made use of the bookmark.

2. A function to add badges automatically if a participant had submitted more than threshold number of useful bookmarks.

3. The UI is basic and it can be further improved.

== References ==

1. Expertiza on Github : https://github.com/rahuliyer95/expertiza

2. Videos on YouTube : https://youtu.be/F95FA9Iam0s, https://youtu.be/tPpowgNRINk

3. Pull Request : https://github.com/expertiza/expertiza/pull/1266

E1830 OSS Project Juniper: Bookmark enhancements

2018-11-02T22:54:17Z

Rkovilk: /* Files modified in current project */

'''Peer Review Information'''

For users intending to view the Expertiza Bookmark enhancement associated with this assignment, the credentials are below:

Instructor login: username -> instructor6, password -> password

'''
== Introduction ==
'''

'''Expertiza Background'''

Expertiza is an open-source educational web application developed on Ruby on Rails platform. Students and Instructors (including TA's) use this application though their credentials. Instructors can add new projects, assignments etc as well edit the previous ones and at a later stage can see the student submission and grade them. They can even put a time limit (deadline) for submitting the assignment. Students can form teams for the projects, submit their work through handles (Wiki page, link to a video etc). Students can even review their teammates and other peers, as well give them any suggestions if required.

GitHub hooks to Expertiza to encourage contributors. Expertiza project is supported by National Science Foundation.

'''Description of the current project'''

This project is intended to make Bookmarks more user-friendly, credible and valid. Bookmarks in expertiza are created by reviewers and can be used by authors for their work on any project. On each line of the signup sheet are two icons, one for adding a bookmark to the topic, and another for viewing bookmarks on the topic. If the instructor allows the participants to create bookmarks, then only a participant has access to create and view them. He should be able to create a new Bookmark only if he enters a valid one.

Now a new rubric is added for reviewing the bookmarks added to a topic and is accessible only to members belonging to the topic.
Tests are written to ensure validity of the bookmark feature.

== Issues ==

'''Problem 1'''

When a user after logging into expertiza goes to 'Create New Bookmark page" or "View existing bookmarks page", he's not able to go back to Sign-up sheet using "back" button.

[[File:back.png]]

Solution :

[[File:fixed_back_link.png]]

'''Problem 2'''

Bookmarks had only one option while reviewing and it was to use a drop down to give a score. Also the average rating metric had a bug and hence showed wrong values even when bookmark was not reviewed. The bug was fixed and the rubric feature was adding a new controller.

Now choosing "Scale" Option instead of "Dropdown" allows one to use a rubric instead.

[[File:scale.png]]

The rubric for rating the bookmark looks as follows :

[[File:begin_review.png]]

== Files modified in current project ==

'''''1. Fixing Average problem and adding Rubric feature :'''''

The following files were modified for fixing the average rating bug and adding rubric for the same.

app/models/bookmark_rating_response_map.rb

app/controllers/bookmark_rating_questionnaire_controller.rb

app/controllers/bookmarks_controller.rb

app/controllers/response_controller.rb

app/views/assignments/edit/_rubrics.html.erb

app/views/bookmarks/bookmark_rating.html.erb

app/views/bookmarks/list.html.erb

app/views/response/view.html.erb

config/routes.rb

'''''2. Tests for Model and Controller :'''''

spec/controllers/bookmarks_controller_spec.rb

spec/models/bookmark_spec.rb

spec/factories/factories.rb

== Automated & UI Testing ==

Automated RSpec tests were added to ensure the bookmarks are valid. Separate tests were written for the Bookmark Model and BookmarkRating Controller files.
The videos of the tests are uploaded onto YouTube and the links are provided in the references section.

'''a) Back button for the page "View Bookmark" and "Create Bookmark" was resolved.'''

1. Login with the credentials to expertiza.

2. Go to 'My assignments' and select OSS Project/writeup.

3. Select 'Signup sheet'.

4. Many titles for projects are shown. Select a title and choose either 'View Bookmark' or 'Add Bookmark' button

5. If you choose 'View Bookmark', after viewing, press the back button to go back to Signup sheet.

6. You will land up in Sign-up sheet page.

7. If you choose 'Add Bookmark', you can add by giving Bookmark details and save it.

8. Now press back button.

9. You will land in Sign-up sheet page.

'''c) Adding Bookmark Rubric.'''

1. Login into the expertiza with the Instructor/TA credentials.

2. Go to 'Manage Content -> Questionnaires'

3. Select new public/private item under BookmarkRating

4. Fill in with required values and create it.

5. After this if you go to bookmark rubric option it should be visible

'''c) Allowing Bookmark Rubric.'''

1. Login into the expertiza with the Instructor/TA credentials.

2. Go to 'Manage Content -> Assignments'

3. Select the appropriate project

4. Now edit the project.

5. Check the box "Allow participants to create bookmarks?" under Topics tab if not done already.

6. Choose the appropriate rubric from the list or create one following steps from above.

7. Now under Rubrics tab choose the "Scale" option for Scored-question display style.

== Future Work ==

1. A reviewer can be recognized or credited if he added useful bookmarks i.e if the author has made use of the bookmark.

2. A function to add badges automatically if a participant had submitted more than threshold number of useful bookmarks.

3. The UI is basic and it can be further improved.

== References ==

1. Expertiza on Github : https://github.com/rahuliyer95/expertiza

2. Videos on youtube : https://youtu.be/F95FA9Iam0s, https://youtu.be/tPpowgNRINk

2. Pull Request : https://github.com/expertiza/expertiza/pull/1266

E1830 OSS Project Juniper: Bookmark enhancements

2018-11-02T22:54:01Z

Rkovilk: /* Files modified in current project */

'''Peer Review Information'''

For users intending to view the Expertiza Bookmark enhancement associated with this assignment, the credentials are below:

Instructor login: username -> instructor6, password -> password

'''
== Introduction ==
'''

'''Expertiza Background'''

Expertiza is an open-source educational web application developed on Ruby on Rails platform. Students and Instructors (including TA's) use this application though their credentials. Instructors can add new projects, assignments etc as well edit the previous ones and at a later stage can see the student submission and grade them. They can even put a time limit (deadline) for submitting the assignment. Students can form teams for the projects, submit their work through handles (Wiki page, link to a video etc). Students can even review their teammates and other peers, as well give them any suggestions if required.

GitHub hooks to Expertiza to encourage contributors. Expertiza project is supported by National Science Foundation.

'''Description of the current project'''

This project is intended to make Bookmarks more user-friendly, credible and valid. Bookmarks in expertiza are created by reviewers and can be used by authors for their work on any project. On each line of the signup sheet are two icons, one for adding a bookmark to the topic, and another for viewing bookmarks on the topic. If the instructor allows the participants to create bookmarks, then only a participant has access to create and view them. He should be able to create a new Bookmark only if he enters a valid one.

Now a new rubric is added for reviewing the bookmarks added to a topic and is accessible only to members belonging to the topic.
Tests are written to ensure validity of the bookmark feature.

== Issues ==

'''Problem 1'''

When a user after logging into expertiza goes to 'Create New Bookmark page" or "View existing bookmarks page", he's not able to go back to Sign-up sheet using "back" button.

[[File:back.png]]

Solution :

[[File:fixed_back_link.png]]

'''Problem 2'''

Bookmarks had only one option while reviewing and it was to use a drop down to give a score. Also the average rating metric had a bug and hence showed wrong values even when bookmark was not reviewed. The bug was fixed and the rubric feature was adding a new controller.

Now choosing "Scale" Option instead of "Dropdown" allows one to use a rubric instead.

[[File:scale.png]]

The rubric for rating the bookmark looks as follows :

[[File:begin_review.png]]

== Files modified in current project ==

'''''1. Fixing Average problem and adding Rubric feature :'''''

The following files were modified for fixing the average rating bug and adding rubric for the same.

app/models/bookmark_rating_response_map.rb

app/controllers/bookmark_rating_questionnaire_controller.rb

app/controllers/bookmarks_controller.rb

app/controllers/response_controller.rb

app/views/assignments/edit/_rubrics.html.erb

app/views/bookmarks/bookmark_rating.html.erb

app/views/bookmarks/list.html.erb

app/views/response/view.html.erb

config/routes.rb

''2. Tests for Model and Controller :''

spec/controllers/bookmarks_controller_spec.rb

spec/models/bookmark_spec.rb

spec/factories/factories.rb

== Automated & UI Testing ==

Automated RSpec tests were added to ensure the bookmarks are valid. Separate tests were written for the Bookmark Model and BookmarkRating Controller files.
The videos of the tests are uploaded onto YouTube and the links are provided in the references section.

'''a) Back button for the page "View Bookmark" and "Create Bookmark" was resolved.'''

1. Login with the credentials to expertiza.

2. Go to 'My assignments' and select OSS Project/writeup.

3. Select 'Signup sheet'.

4. Many titles for projects are shown. Select a title and choose either 'View Bookmark' or 'Add Bookmark' button

5. If you choose 'View Bookmark', after viewing, press the back button to go back to Signup sheet.

6. You will land up in Sign-up sheet page.

7. If you choose 'Add Bookmark', you can add by giving Bookmark details and save it.

8. Now press back button.

9. You will land in Sign-up sheet page.

'''c) Adding Bookmark Rubric.'''

1. Login into the expertiza with the Instructor/TA credentials.

2. Go to 'Manage Content -> Questionnaires'

3. Select new public/private item under BookmarkRating

4. Fill in with required values and create it.

5. After this if you go to bookmark rubric option it should be visible

'''c) Allowing Bookmark Rubric.'''

1. Login into the expertiza with the Instructor/TA credentials.

2. Go to 'Manage Content -> Assignments'

3. Select the appropriate project

4. Now edit the project.

5. Check the box "Allow participants to create bookmarks?" under Topics tab if not done already.

6. Choose the appropriate rubric from the list or create one following steps from above.

7. Now under Rubrics tab choose the "Scale" option for Scored-question display style.

== Future Work ==

1. A reviewer can be recognized or credited if he added useful bookmarks i.e if the author has made use of the bookmark.

2. A function to add badges automatically if a participant had submitted more than threshold number of useful bookmarks.

3. The UI is basic and it can be further improved.

== References ==

1. Expertiza on Github : https://github.com/rahuliyer95/expertiza

2. Videos on youtube : https://youtu.be/F95FA9Iam0s, https://youtu.be/tPpowgNRINk

2. Pull Request : https://github.com/expertiza/expertiza/pull/1266

E1830 OSS Project Juniper: Bookmark enhancements

2018-11-02T22:53:13Z

Rkovilk: /* Issues */

'''Peer Review Information'''

For users intending to view the Expertiza Bookmark enhancement associated with this assignment, the credentials are below:

Instructor login: username -> instructor6, password -> password

'''
== Introduction ==
'''

'''Expertiza Background'''

Expertiza is an open-source educational web application developed on Ruby on Rails platform. Students and Instructors (including TA's) use this application though their credentials. Instructors can add new projects, assignments etc as well edit the previous ones and at a later stage can see the student submission and grade them. They can even put a time limit (deadline) for submitting the assignment. Students can form teams for the projects, submit their work through handles (Wiki page, link to a video etc). Students can even review their teammates and other peers, as well give them any suggestions if required.

GitHub hooks to Expertiza to encourage contributors. Expertiza project is supported by National Science Foundation.

'''Description of the current project'''

This project is intended to make Bookmarks more user-friendly, credible and valid. Bookmarks in expertiza are created by reviewers and can be used by authors for their work on any project. On each line of the signup sheet are two icons, one for adding a bookmark to the topic, and another for viewing bookmarks on the topic. If the instructor allows the participants to create bookmarks, then only a participant has access to create and view them. He should be able to create a new Bookmark only if he enters a valid one.

Now a new rubric is added for reviewing the bookmarks added to a topic and is accessible only to members belonging to the topic.
Tests are written to ensure validity of the bookmark feature.

== Issues ==

'''Problem 1'''

When a user after logging into expertiza goes to 'Create New Bookmark page" or "View existing bookmarks page", he's not able to go back to Sign-up sheet using "back" button.

[[File:back.png]]

Solution :

[[File:fixed_back_link.png]]

'''Problem 2'''

Bookmarks had only one option while reviewing and it was to use a drop down to give a score. Also the average rating metric had a bug and hence showed wrong values even when bookmark was not reviewed. The bug was fixed and the rubric feature was adding a new controller.

Now choosing "Scale" Option instead of "Dropdown" allows one to use a rubric instead.

[[File:scale.png]]

The rubric for rating the bookmark looks as follows :

[[File:begin_review.png]]

== Files modified in current project ==

''1. Fixing Average problem and adding Rubric feature :''

The following files were modified for fixing the average rating bug and adding rubric for the same.

app/models/bookmark_rating_response_map.rb

app/controllers/bookmark_rating_questionnaire_controller.rb

app/controllers/bookmarks_controller.rb

app/controllers/response_controller.rb

app/views/assignments/edit/_rubrics.html.erb

app/views/bookmarks/bookmark_rating.html.erb

app/views/bookmarks/list.html.erb

app/views/response/view.html.erb

config/routes.rb

''2. Tests for Model and Controller :''

spec/controllers/bookmarks_controller_spec.rb

spec/models/bookmark_spec.rb

spec/factories/factories.rb

== Automated & UI Testing ==

Automated RSpec tests were added to ensure the bookmarks are valid. Separate tests were written for the Bookmark Model and BookmarkRating Controller files.
The videos of the tests are uploaded onto YouTube and the links are provided in the references section.

'''a) Back button for the page "View Bookmark" and "Create Bookmark" was resolved.'''

1. Login with the credentials to expertiza.

2. Go to 'My assignments' and select OSS Project/writeup.

3. Select 'Signup sheet'.

4. Many titles for projects are shown. Select a title and choose either 'View Bookmark' or 'Add Bookmark' button

5. If you choose 'View Bookmark', after viewing, press the back button to go back to Signup sheet.

6. You will land up in Sign-up sheet page.

7. If you choose 'Add Bookmark', you can add by giving Bookmark details and save it.

8. Now press back button.

9. You will land in Sign-up sheet page.

'''c) Adding Bookmark Rubric.'''

1. Login into the expertiza with the Instructor/TA credentials.

2. Go to 'Manage Content -> Questionnaires'

3. Select new public/private item under BookmarkRating

4. Fill in with required values and create it.

5. After this if you go to bookmark rubric option it should be visible

'''c) Allowing Bookmark Rubric.'''

1. Login into the expertiza with the Instructor/TA credentials.

2. Go to 'Manage Content -> Assignments'

3. Select the appropriate project

4. Now edit the project.

5. Check the box "Allow participants to create bookmarks?" under Topics tab if not done already.

6. Choose the appropriate rubric from the list or create one following steps from above.

7. Now under Rubrics tab choose the "Scale" option for Scored-question display style.

== Future Work ==

1. A reviewer can be recognized or credited if he added useful bookmarks i.e if the author has made use of the bookmark.

2. A function to add badges automatically if a participant had submitted more than threshold number of useful bookmarks.

3. The UI is basic and it can be further improved.

== References ==

1. Expertiza on Github : https://github.com/rahuliyer95/expertiza

2. Videos on youtube : https://youtu.be/F95FA9Iam0s, https://youtu.be/tPpowgNRINk

2. Pull Request : https://github.com/expertiza/expertiza/pull/1266

E1830 OSS Project Juniper: Bookmark enhancements

2018-11-02T22:52:42Z

Rkovilk: /* Issues */

'''Peer Review Information'''

For users intending to view the Expertiza Bookmark enhancement associated with this assignment, the credentials are below:

Instructor login: username -> instructor6, password -> password

'''
== Introduction ==
'''

'''Expertiza Background'''

Expertiza is an open-source educational web application developed on Ruby on Rails platform. Students and Instructors (including TA's) use this application though their credentials. Instructors can add new projects, assignments etc as well edit the previous ones and at a later stage can see the student submission and grade them. They can even put a time limit (deadline) for submitting the assignment. Students can form teams for the projects, submit their work through handles (Wiki page, link to a video etc). Students can even review their teammates and other peers, as well give them any suggestions if required.

GitHub hooks to Expertiza to encourage contributors. Expertiza project is supported by National Science Foundation.

'''Description of the current project'''

This project is intended to make Bookmarks more user-friendly, credible and valid. Bookmarks in expertiza are created by reviewers and can be used by authors for their work on any project. On each line of the signup sheet are two icons, one for adding a bookmark to the topic, and another for viewing bookmarks on the topic. If the instructor allows the participants to create bookmarks, then only a participant has access to create and view them. He should be able to create a new Bookmark only if he enters a valid one.

Now a new rubric is added for reviewing the bookmarks added to a topic and is accessible only to members belonging to the topic.
Tests are written to ensure validity of the bookmark feature.

== Issues ==

'''Problem 1'''

When a user after logging into expertiza goes to 'Create New Bookmark page" or "View existing bookmarks page", he's not able to go back to Sign-up sheet using "back" button.

[[File:back.png]]

Solution :

[[File:fixed_back_link.png]]

[[File:back_fixed.png|200px]]

'''Problem 2'''

Bookmarks had only one option while reviewing and it was to use a drop down to give a score. Also the average rating metric had a bug and hence showed wrong values even when bookmark was not reviewed. The bug was fixed and the rubric feature was adding a new controller.

Now choosing "Scale" Option instead of "Dropdown" allows one to use a rubric instead.

[[File:scale.png]]

The rubric for rating the bookmark looks as follows :

[[File:begin_review.png]]

== Files modified in current project ==

''1. Fixing Average problem and adding Rubric feature :''

The following files were modified for fixing the average rating bug and adding rubric for the same.

app/models/bookmark_rating_response_map.rb

app/controllers/bookmark_rating_questionnaire_controller.rb

app/controllers/bookmarks_controller.rb

app/controllers/response_controller.rb

app/views/assignments/edit/_rubrics.html.erb

app/views/bookmarks/bookmark_rating.html.erb

app/views/bookmarks/list.html.erb

app/views/response/view.html.erb

config/routes.rb

''2. Tests for Model and Controller :''

spec/controllers/bookmarks_controller_spec.rb

spec/models/bookmark_spec.rb

spec/factories/factories.rb

== Automated & UI Testing ==

Automated RSpec tests were added to ensure the bookmarks are valid. Separate tests were written for the Bookmark Model and BookmarkRating Controller files.
The videos of the tests are uploaded onto YouTube and the links are provided in the references section.

'''a) Back button for the page "View Bookmark" and "Create Bookmark" was resolved.'''

1. Login with the credentials to expertiza.

2. Go to 'My assignments' and select OSS Project/writeup.

3. Select 'Signup sheet'.

4. Many titles for projects are shown. Select a title and choose either 'View Bookmark' or 'Add Bookmark' button

5. If you choose 'View Bookmark', after viewing, press the back button to go back to Signup sheet.

6. You will land up in Sign-up sheet page.

7. If you choose 'Add Bookmark', you can add by giving Bookmark details and save it.

8. Now press back button.

9. You will land in Sign-up sheet page.

'''c) Adding Bookmark Rubric.'''

1. Login into the expertiza with the Instructor/TA credentials.

2. Go to 'Manage Content -> Questionnaires'

3. Select new public/private item under BookmarkRating

4. Fill in with required values and create it.

5. After this if you go to bookmark rubric option it should be visible

'''c) Allowing Bookmark Rubric.'''

1. Login into the expertiza with the Instructor/TA credentials.

2. Go to 'Manage Content -> Assignments'

3. Select the appropriate project

4. Now edit the project.

5. Check the box "Allow participants to create bookmarks?" under Topics tab if not done already.

6. Choose the appropriate rubric from the list or create one following steps from above.

7. Now under Rubrics tab choose the "Scale" option for Scored-question display style.

== Future Work ==

1. A reviewer can be recognized or credited if he added useful bookmarks i.e if the author has made use of the bookmark.

2. A function to add badges automatically if a participant had submitted more than threshold number of useful bookmarks.

3. The UI is basic and it can be further improved.

== References ==

1. Expertiza on Github : https://github.com/rahuliyer95/expertiza

2. Videos on youtube : https://youtu.be/F95FA9Iam0s, https://youtu.be/tPpowgNRINk

2. Pull Request : https://github.com/expertiza/expertiza/pull/1266

File:Begin review.png

2018-11-02T22:52:02Z

Rkovilk:

File:Scale.png

2018-11-02T22:51:12Z

Rkovilk:

E1830 OSS Project Juniper: Bookmark enhancements

2018-11-02T22:50:49Z

Rkovilk: /* Issues */

'''Peer Review Information'''

For users intending to view the Expertiza Bookmark enhancement associated with this assignment, the credentials are below:

Instructor login: username -> instructor6, password -> password

'''
== Introduction ==
'''

'''Expertiza Background'''

Expertiza is an open-source educational web application developed on Ruby on Rails platform. Students and Instructors (including TA's) use this application though their credentials. Instructors can add new projects, assignments etc as well edit the previous ones and at a later stage can see the student submission and grade them. They can even put a time limit (deadline) for submitting the assignment. Students can form teams for the projects, submit their work through handles (Wiki page, link to a video etc). Students can even review their teammates and other peers, as well give them any suggestions if required.

GitHub hooks to Expertiza to encourage contributors. Expertiza project is supported by National Science Foundation.

'''Description of the current project'''

This project is intended to make Bookmarks more user-friendly, credible and valid. Bookmarks in expertiza are created by reviewers and can be used by authors for their work on any project. On each line of the signup sheet are two icons, one for adding a bookmark to the topic, and another for viewing bookmarks on the topic. If the instructor allows the participants to create bookmarks, then only a participant has access to create and view them. He should be able to create a new Bookmark only if he enters a valid one.

Now a new rubric is added for reviewing the bookmarks added to a topic and is accessible only to members belonging to the topic.
Tests are written to ensure validity of the bookmark feature.

== Issues ==

'''Problem 1'''

When a user after logging into expertiza goes to 'Create New Bookmark page" or "View existing bookmarks page", he's not able to go back to Sign-up sheet using "back" button.

[[File:back.png]]

Solution :

[[File:fixed_back_link.png]]

[[File:back_fixed.png|200px]]

'''Problem 2'''

Bookmarks had only one option while reviewing and it was to use a drop down to give a score. Also the average rating metric had a bug and hence showed wrong values even when bookmark was not reviewed. The bug was fixed and the rubric feature was adding a new controller.

Now choosing "Scale" Option instead of "Dropdown" allows one to use a rubric instead.

[[File:scale.png]]

The rubric for rating the bookmark looks as follows :

[[File:begin_review.png]]

== Files modified in current project ==

''1. Fixing Average problem and adding Rubric feature :''

The following files were modified for fixing the average rating bug and adding rubric for the same.

app/models/bookmark_rating_response_map.rb

app/controllers/bookmark_rating_questionnaire_controller.rb

app/controllers/bookmarks_controller.rb

app/controllers/response_controller.rb

app/views/assignments/edit/_rubrics.html.erb

app/views/bookmarks/bookmark_rating.html.erb

app/views/bookmarks/list.html.erb

app/views/response/view.html.erb

config/routes.rb

''2. Tests for Model and Controller :''

spec/controllers/bookmarks_controller_spec.rb

spec/models/bookmark_spec.rb

spec/factories/factories.rb

== Automated & UI Testing ==

Automated RSpec tests were added to ensure the bookmarks are valid. Separate tests were written for the Bookmark Model and BookmarkRating Controller files.
The videos of the tests are uploaded onto YouTube and the links are provided in the references section.

'''a) Back button for the page "View Bookmark" and "Create Bookmark" was resolved.'''

1. Login with the credentials to expertiza.

2. Go to 'My assignments' and select OSS Project/writeup.

3. Select 'Signup sheet'.

4. Many titles for projects are shown. Select a title and choose either 'View Bookmark' or 'Add Bookmark' button

5. If you choose 'View Bookmark', after viewing, press the back button to go back to Signup sheet.

6. You will land up in Sign-up sheet page.

7. If you choose 'Add Bookmark', you can add by giving Bookmark details and save it.

8. Now press back button.

9. You will land in Sign-up sheet page.

'''c) Adding Bookmark Rubric.'''

1. Login into the expertiza with the Instructor/TA credentials.

2. Go to 'Manage Content -> Questionnaires'

3. Select new public/private item under BookmarkRating

4. Fill in with required values and create it.

5. After this if you go to bookmark rubric option it should be visible

'''c) Allowing Bookmark Rubric.'''

1. Login into the expertiza with the Instructor/TA credentials.

2. Go to 'Manage Content -> Assignments'

3. Select the appropriate project

4. Now edit the project.

5. Check the box "Allow participants to create bookmarks?" under Topics tab if not done already.

6. Choose the appropriate rubric from the list or create one following steps from above.

7. Now under Rubrics tab choose the "Scale" option for Scored-question display style.

== Future Work ==

1. A reviewer can be recognized or credited if he added useful bookmarks i.e if the author has made use of the bookmark.

2. A function to add badges automatically if a participant had submitted more than threshold number of useful bookmarks.

3. The UI is basic and it can be further improved.

== References ==

1. Expertiza on Github : https://github.com/rahuliyer95/expertiza

2. Videos on youtube : https://youtu.be/F95FA9Iam0s, https://youtu.be/tPpowgNRINk

2. Pull Request : https://github.com/expertiza/expertiza/pull/1266

E1830 OSS Project Juniper: Bookmark enhancements

2018-11-02T22:48:34Z

Rkovilk: /* Issues */

'''Peer Review Information'''

For users intending to view the Expertiza Bookmark enhancement associated with this assignment, the credentials are below:

Instructor login: username -> instructor6, password -> password

'''
== Introduction ==
'''

'''Expertiza Background'''

Expertiza is an open-source educational web application developed on Ruby on Rails platform. Students and Instructors (including TA's) use this application though their credentials. Instructors can add new projects, assignments etc as well edit the previous ones and at a later stage can see the student submission and grade them. They can even put a time limit (deadline) for submitting the assignment. Students can form teams for the projects, submit their work through handles (Wiki page, link to a video etc). Students can even review their teammates and other peers, as well give them any suggestions if required.

GitHub hooks to Expertiza to encourage contributors. Expertiza project is supported by National Science Foundation.

'''Description of the current project'''

This project is intended to make Bookmarks more user-friendly, credible and valid. Bookmarks in expertiza are created by reviewers and can be used by authors for their work on any project. On each line of the signup sheet are two icons, one for adding a bookmark to the topic, and another for viewing bookmarks on the topic. If the instructor allows the participants to create bookmarks, then only a participant has access to create and view them. He should be able to create a new Bookmark only if he enters a valid one.

Now a new rubric is added for reviewing the bookmarks added to a topic and is accessible only to members belonging to the topic.
Tests are written to ensure validity of the bookmark feature.

== Issues ==

'''Problem 1'''

When a user after logging into expertiza goes to 'Create New Bookmark page" or "View existing bookmarks page", he's not able to go back to Sign-up sheet using "back" button.

[[File:back.png]]

Solution :

[[File:fixed_back_link.png|200px]]

[[File:back_fixed.png|200px]]

'''Problem 2'''

Bookmarks had only one option while reviewing and it was to use a drop down to give a score. Also the average rating metric had a bug and hence showed wrong values even when bookmark was not reviewed. The bug was fixed and the rubric feature was adding a new controller.

Now choosing "Scale" Option instead of "Dropdown" allows one to use a rubric instead.

[[File:scale.png]]

The rubric for rating the bookmark looks as follows :

[[File:begin_review.png]]

== Files modified in current project ==

''1. Fixing Average problem and adding Rubric feature :''

The following files were modified for fixing the average rating bug and adding rubric for the same.

app/models/bookmark_rating_response_map.rb

app/controllers/bookmark_rating_questionnaire_controller.rb

app/controllers/bookmarks_controller.rb

app/controllers/response_controller.rb

app/views/assignments/edit/_rubrics.html.erb

app/views/bookmarks/bookmark_rating.html.erb

app/views/bookmarks/list.html.erb

app/views/response/view.html.erb

config/routes.rb

''2. Tests for Model and Controller :''

spec/controllers/bookmarks_controller_spec.rb

spec/models/bookmark_spec.rb

spec/factories/factories.rb

== Automated & UI Testing ==

Automated RSpec tests were added to ensure the bookmarks are valid. Separate tests were written for the Bookmark Model and BookmarkRating Controller files.
The videos of the tests are uploaded onto YouTube and the links are provided in the references section.

'''a) Back button for the page "View Bookmark" and "Create Bookmark" was resolved.'''

1. Login with the credentials to expertiza.

2. Go to 'My assignments' and select OSS Project/writeup.

3. Select 'Signup sheet'.

4. Many titles for projects are shown. Select a title and choose either 'View Bookmark' or 'Add Bookmark' button

5. If you choose 'View Bookmark', after viewing, press the back button to go back to Signup sheet.

6. You will land up in Sign-up sheet page.

7. If you choose 'Add Bookmark', you can add by giving Bookmark details and save it.

8. Now press back button.

9. You will land in Sign-up sheet page.

'''c) Adding Bookmark Rubric.'''

1. Login into the expertiza with the Instructor/TA credentials.

2. Go to 'Manage Content -> Questionnaires'

3. Select new public/private item under BookmarkRating

4. Fill in with required values and create it.

5. After this if you go to bookmark rubric option it should be visible

'''c) Allowing Bookmark Rubric.'''

1. Login into the expertiza with the Instructor/TA credentials.

2. Go to 'Manage Content -> Assignments'

3. Select the appropriate project

4. Now edit the project.

5. Check the box "Allow participants to create bookmarks?" under Topics tab if not done already.

6. Choose the appropriate rubric from the list or create one following steps from above.

7. Now under Rubrics tab choose the "Scale" option for Scored-question display style.

== Future Work ==

1. A reviewer can be recognized or credited if he added useful bookmarks i.e if the author has made use of the bookmark.

2. A function to add badges automatically if a participant had submitted more than threshold number of useful bookmarks.

3. The UI is basic and it can be further improved.

== References ==

1. Expertiza on Github : https://github.com/rahuliyer95/expertiza

2. Videos on youtube : https://youtu.be/F95FA9Iam0s, https://youtu.be/tPpowgNRINk

2. Pull Request : https://github.com/expertiza/expertiza/pull/1266

File:Fixed back link.png

2018-11-02T22:47:57Z

Rkovilk:

File:Back fixed.png

2018-11-02T22:47:03Z

Rkovilk: uploaded a new version of "File:Back fixed.png"

E1830 OSS Project Juniper: Bookmark enhancements

2018-11-02T22:05:24Z

Rkovilk: /* Issues */

'''Peer Review Information'''

For users intending to view the Expertiza Bookmark enhancement associated with this assignment, the credentials are below:

Instructor login: username -> instructor6, password -> password

'''
== Introduction ==
'''

'''Expertiza Background'''

Expertiza is an open-source educational web application developed on Ruby on Rails platform. Students and Instructors (including TA's) use this application though their credentials. Instructors can add new projects, assignments etc as well edit the previous ones and at a later stage can see the student submission and grade them. They can even put a time limit (deadline) for submitting the assignment. Students can form teams for the projects, submit their work through handles (Wiki page, link to a video etc). Students can even review their teammates and other peers, as well give them any suggestions if required.

GitHub hooks to Expertiza to encourage contributors. Expertiza project is supported by National Science Foundation.

'''Description of the current project'''

This project is intended to make Bookmarks more user-friendly, credible and valid. Bookmarks in expertiza are created by reviewers and can be used by authors for their work on any project. On each line of the signup sheet are two icons, one for adding a bookmark to the topic, and another for viewing bookmarks on the topic. If the instructor allows the participants to create bookmarks, then only a participant has access to create and view them. He should be able to create a new Bookmark only if he enters a valid one.

Now a new rubric is added for reviewing the bookmarks added to a topic and is accessible only to members belonging to the topic.
Tests are written to ensure validity of the bookmark feature.

== Issues ==

'''Problem 1'''

When a user after logging into expertiza goes to 'Create New Bookmark page" or "View existing bookmarks page", he's not able to go back to Sign-up sheet using "back" button.

[[File:back.png]]

Solution :

[[File:fixed_back_link.png]]

[[File:back_fixed.png|200px]]

'''Problem 2'''

Bookmarks had only one option while reviewing and it was to use a drop down to give a score. Also the average rating metric had a bug and hence showed wrong values even when bookmark was not reviewed. The bug was fixed and the rubric feature was adding a new controller.

Now choosing "Scale" Option instead of "Dropdown" allows one to use a rubric instead.

[[File:scale.png]]

The rubric for rating the bookmark looks as follows :

[[File:begin_review.png]]

== Files modified in current project ==

''1. Fixing Average problem and adding Rubric feature :''

The following files were modified for fixing the average rating bug and adding rubric for the same.

app/models/bookmark_rating_response_map.rb

app/controllers/bookmark_rating_questionnaire_controller.rb

app/controllers/bookmarks_controller.rb

app/controllers/response_controller.rb

app/views/assignments/edit/_rubrics.html.erb

app/views/bookmarks/bookmark_rating.html.erb

app/views/bookmarks/list.html.erb

app/views/response/view.html.erb

config/routes.rb

''2. Tests for Model and Controller :''

spec/controllers/bookmarks_controller_spec.rb

spec/models/bookmark_spec.rb

spec/factories/factories.rb

== Automated & UI Testing ==

Automated RSpec tests were added to ensure the bookmarks are valid. Separate tests were written for the Bookmark Model and BookmarkRating Controller files.
The videos of the tests are uploaded onto YouTube and the links are provided in the references section.

'''a) Back button for the page "View Bookmark" and "Create Bookmark" was resolved.'''

1. Login with the credentials to expertiza.

2. Go to 'My assignments' and select OSS Project/writeup.

3. Select 'Signup sheet'.

4. Many titles for projects are shown. Select a title and choose either 'View Bookmark' or 'Add Bookmark' button

5. If you choose 'View Bookmark', after viewing, press the back button to go back to Signup sheet.

6. You will land up in Sign-up sheet page.

7. If you choose 'Add Bookmark', you can add by giving Bookmark details and save it.

8. Now press back button.

9. You will land in Sign-up sheet page.

'''c) Adding Bookmark Rubric.'''

1. Login into the expertiza with the Instructor/TA credentials.

2. Go to 'Manage Content -> Questionnaires'

3. Select new public/private item under BookmarkRating

4. Fill in with required values and create it.

5. After this if you go to bookmark rubric option it should be visible

'''c) Allowing Bookmark Rubric.'''

1. Login into the expertiza with the Instructor/TA credentials.

2. Go to 'Manage Content -> Assignments'

3. Select the appropriate project

4. Now edit the project.

5. Check the box "Allow participants to create bookmarks?" under Topics tab if not done already.

6. Choose the appropriate rubric from the list or create one following steps from above.

7. Now under Rubrics tab choose the "Scale" option for Scored-question display style.

== Future Work ==

1. A reviewer can be recognized or credited if he added useful bookmarks i.e if the author has made use of the bookmark.

2. A function to add badges automatically if a participant had submitted more than threshold number of useful bookmarks.

3. The UI is basic and it can be further improved.

== References ==

1. Expertiza on Github : https://github.com/rahuliyer95/expertiza

2. Videos on youtube : https://youtu.be/F95FA9Iam0s, https://youtu.be/tPpowgNRINk

2. Pull Request : https://github.com/expertiza/expertiza/pull/1266

File:Back fixed.png

2018-11-02T22:03:56Z

Rkovilk: uploaded a new version of "File:Back fixed.png"

File:Back fixed.png

2018-11-02T22:03:13Z

Rkovilk:

File:Back.png

2018-11-02T22:02:35Z

Rkovilk:

E1830 OSS Project Juniper: Bookmark enhancements

2018-11-02T22:01:27Z

Rkovilk: /* Introduction */

'''Peer Review Information'''

For users intending to view the Expertiza Bookmark enhancement associated with this assignment, the credentials are below:

Instructor login: username -> instructor6, password -> password

'''
== Introduction ==
'''

'''Expertiza Background'''

Expertiza is an open-source educational web application developed on Ruby on Rails platform. Students and Instructors (including TA's) use this application though their credentials. Instructors can add new projects, assignments etc as well edit the previous ones and at a later stage can see the student submission and grade them. They can even put a time limit (deadline) for submitting the assignment. Students can form teams for the projects, submit their work through handles (Wiki page, link to a video etc). Students can even review their teammates and other peers, as well give them any suggestions if required.

GitHub hooks to Expertiza to encourage contributors. Expertiza project is supported by National Science Foundation.

'''Description of the current project'''

This project is intended to make Bookmarks more user-friendly, credible and valid. Bookmarks in expertiza are created by reviewers and can be used by authors for their work on any project. On each line of the signup sheet are two icons, one for adding a bookmark to the topic, and another for viewing bookmarks on the topic. If the instructor allows the participants to create bookmarks, then only a participant has access to create and view them. He should be able to create a new Bookmark only if he enters a valid one.

Now a new rubric is added for reviewing the bookmarks added to a topic and is accessible only to members belonging to the topic.
Tests are written to ensure validity of the bookmark feature.

== Issues ==

'''Problem 1'''

When a user after logging into expertiza goes to 'Create New Bookmark page" or "View existing bookmarks page", he's not able to go back to Sign-up sheet using "back" button.

[[File:back.png]]

Solution :

[[File:fixed_back_link.png]]

[[File:back_fixed.png]]

'''Problem 2'''

Bookmarks had only one option while reviewing and it was to use a drop down to give a score. Also the average rating metric had a bug and hence showed wrong values even when bookmark was not reviewed. The bug was fixed and the rubric feature was adding a new controller.

Now choosing "Scale" Option instead of "Dropdown" allows one to use a rubric instead.

[[File:scale.png]]

The rubric for rating the bookmark looks as follows :

[[File:begin_review.png]]

== Files modified in current project ==

''1. Fixing Average problem and adding Rubric feature :''

The following files were modified for fixing the average rating bug and adding rubric for the same.

app/models/bookmark_rating_response_map.rb

app/controllers/bookmark_rating_questionnaire_controller.rb

app/controllers/bookmarks_controller.rb

app/controllers/response_controller.rb

app/views/assignments/edit/_rubrics.html.erb

app/views/bookmarks/bookmark_rating.html.erb

app/views/bookmarks/list.html.erb

app/views/response/view.html.erb

config/routes.rb

''2. Tests for Model and Controller :''

spec/controllers/bookmarks_controller_spec.rb

spec/models/bookmark_spec.rb

spec/factories/factories.rb

== Automated & UI Testing ==

Automated RSpec tests were added to ensure the bookmarks are valid. Separate tests were written for the Bookmark Model and BookmarkRating Controller files.
The videos of the tests are uploaded onto YouTube and the links are provided in the references section.

'''a) Back button for the page "View Bookmark" and "Create Bookmark" was resolved.'''

1. Login with the credentials to expertiza.

2. Go to 'My assignments' and select OSS Project/writeup.

3. Select 'Signup sheet'.

4. Many titles for projects are shown. Select a title and choose either 'View Bookmark' or 'Add Bookmark' button

5. If you choose 'View Bookmark', after viewing, press the back button to go back to Signup sheet.

6. You will land up in Sign-up sheet page.

7. If you choose 'Add Bookmark', you can add by giving Bookmark details and save it.

8. Now press back button.

9. You will land in Sign-up sheet page.

'''c) Adding Bookmark Rubric.'''

1. Login into the expertiza with the Instructor/TA credentials.

2. Go to 'Manage Content -> Questionnaires'

3. Select new public/private item under BookmarkRating

4. Fill in with required values and create it.

5. After this if you go to bookmark rubric option it should be visible

'''c) Allowing Bookmark Rubric.'''

1. Login into the expertiza with the Instructor/TA credentials.

2. Go to 'Manage Content -> Assignments'

3. Select the appropriate project

4. Now edit the project.

5. Check the box "Allow participants to create bookmarks?" under Topics tab if not done already.

6. Choose the appropriate rubric from the list or create one following steps from above.

7. Now under Rubrics tab choose the "Scale" option for Scored-question display style.

== Future Work ==

1. A reviewer can be recognized or credited if he added useful bookmarks i.e if the author has made use of the bookmark.

2. A function to add badges automatically if a participant had submitted more than threshold number of useful bookmarks.

3. The UI is basic and it can be further improved.

== References ==

1. Expertiza on Github : https://github.com/rahuliyer95/expertiza

2. Videos on youtube : https://youtu.be/F95FA9Iam0s, https://youtu.be/tPpowgNRINk

2. Pull Request : https://github.com/expertiza/expertiza/pull/1266