Expertiza_Wiki - User contributions [en]

CSC/ECE 517 Fall 2017/E17A1 Expert Review.rb

2017-12-06T06:48:26Z

Anjain2:

This wiki page is the description of the E17A1 semester project - Let experts as well as students do reviews - for Fall 2017, CSC/ECE 517.

= Introduction =

[http://expertiza.ncsu.edu/ Expertiza] is an open source project based on [http://rubyonrails.org/ Ruby on Rails] framework. The Expertiza project is software to create reusable learning objects through peer review. It is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). It is used in select courses at NC State and by professors at several other colleges and universities. It also supports team projects, and the submission of almost any document type, including URLs and wiki pages. Expertiza enables the instructor to create new and customize existing assignments. It also enables the instructor to create a list of topics the students can sign up for as part of a project. Students can form teams in Expertiza to work on various projects and assignments. Expertiza supports submission across various document types, including the URLs and wiki pages.

= Existing Limitations =
*Currently, the functionality of calibration is limited. It does not support varying-rubric-by-round feature.
*For student side, there is no way to notify for an author to tell that a particular review that they received was submitted by an expert.
*Students are not able to see how an expert has rated the assignment, they can only see calibration results for calibrated assignments by clicking on the “Show calibration results” link.

= Tasks =
*Change in DB Schema
**“is_calibrated” field in assignment table to “has_expert_review”
**“calibrate_to” field in response_map table to “expert_review_to”
*User interface changes
**Original interface
[[File:Rsz 1old calibration page.png|1000px|Updated]]
[[File:Rsz_old_show.png|1000px|Updated]]
[[File:Rsz_GeneralTab.png]]
**Instructor side
***In assignment setting page (“General” tab), change the checkbox title from “Calibrated peer-review for training?” to “Add expert peer review?”
***When instructor clicks that checkbox, there will be a new tab named “Calibration”. Change the tab name from “Calibration” to “Expert review” on the assignment setting page [[File:Rsz_NewGeneral.png‎]]
**Student side
***Change the link title from “show calibration results” to “show expert peer-review results”[[File:Rsz_new_show.png|1000px|Updated]]
***Change the title in “response/show_calibration_results_for_student.html.erb” to start with “Expert review comparison report for”[[File:New_expert_review_page.png|1000px|Updated]]
*New features
**Let expert review support the vary-rubric-by-round functionality
**Support multiple expert reviews (Both TAs and instructors could do expert reviews)
*Tests
**Create expert_review_spec.rb file in spec/features folder
*Additional minor changes
**Reflect changes in DB schema at all places, including tests.
**Change the partial file name from “_calibration.html.erb” to “_expert_review.html.erb”
**Rename “response/show_calibration_results_for_student.html.erb” to “response/show_expert_review_results_for_student.html.erb” and also change other call sites
**

= Proposed Solution =
'''Change in database'''
The following schema changes will be implemented using a new migration file:
* “is_calibrated” field in assignment table to “has_expert_review”
* “calibrate_to” field in response_map table to “expert_review_to”

'''Change in User interface'''
The following files will be edited to reflect the changes in user interface as mentioned in tasks:
* #assignments/edit/_calibration.html.erb
* #response/show_calibration_results_for_student.html.erb
* #student_review/_responses.html.erb
* #student_review/list.html.erb
* #assignments/edit.html.erb
= Use Case Diagram =
[[File:Rsz_expertiza_uml-1.png]]

*Instructor and TAs are the "Experts" that can review the assignment.
*Multiple experts should be able to review the same assignment.
*When a student views the review, student should understand whether the review was made by an expert or a student.

=Major changes performed=
*app/controllers/response_controller.rb:
**Method: show_calibration_results_for_student
**Fetching all expert reviews performed for the respective assignment and respective team instead of fetching only instructor's response.
*app/assignments/edit/_expert_review.html.erb
**Showing multiple rounds of View/Begin review as per the current round and number of reviews already done by the expert (as it happens for students).
*app/views/response/show_expert_review_results_for_student.erb
**Showing calibrated response to students who have reviewed the assignment with responses of multiple experts for a particular round.
*app/views/student_review/_responses.html.erb
**Showing links for calibrated result for each round.

= Test Plan =
*Existing tests should be changed according to changes in database schema and user interface.
*A new test file expert_review_spec.rb will be created to unit test the changes with the following steps:
* Log in using instructor's or teaching assistant's credentials.
* General tab should have the checkbox titled 'Add expert peer review?'
* Click on the checkbox.
* There should be a tab "Expert review" on the assignment setting page.
* Log out and log in back using student's credentials.
* There should be a link titled 'show expert peer-review results'
* Test multiple expert reviews by submitting multiple reviews when logged in as an instructor or TA for the same assignment.
* Also test the vary-rubric-by-round functionality.

=== New Test ===
New tests will be written to test the new features added, like :
* assignment should support multiple expert review.
* current assignment should support vary-rubric-by-round.

=Links=
1. Pull request - https://github.com/expertiza/expertiza/pull/1114

CSC/ECE 517 Fall 2017/E17A1 Expert Review.rb

2017-12-06T06:47:46Z

Anjain2:

This wiki page is the description of the E17A1 semester project - Let experts as well as students do reviews - for Fall 2017, CSC/ECE 517.

= Introduction =

[http://expertiza.ncsu.edu/ Expertiza] is an open source project based on [http://rubyonrails.org/ Ruby on Rails] framework. The Expertiza project is software to create reusable learning objects through peer review. It is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). It is used in select courses at NC State and by professors at several other colleges and universities. It also supports team projects, and the submission of almost any document type, including URLs and wiki pages. Expertiza enables the instructor to create new and customize existing assignments. It also enables the instructor to create a list of topics the students can sign up for as part of a project. Students can form teams in Expertiza to work on various projects and assignments. Expertiza supports submission across various document types, including the URLs and wiki pages.

= Existing Limitations =
*Currently, the functionality of calibration is limited. It does not support varying-rubric-by-round feature.
*For student side, there is no way to notify for an author to tell that a particular review that they received was submitted by an expert.
*Students are not able to see how an expert has rated the assignment, they can only see calibration results for calibrated assignments by clicking on the “Show calibration results” link.

= Tasks =
*Change in DB Schema
**“is_calibrated” field in assignment table to “has_expert_review”
**“calibrate_to” field in response_map table to “expert_review_to”
*User interface changes
**Original interface
[[File:Rsz 1old calibration page.png|1000px|Updated]]
[[File:Rsz_old_show.png|1000px|Updated]]
[[File:Rsz_GeneralTab.png]]
**Instructor side
***In assignment setting page (“General” tab), change the checkbox title from “Calibrated peer-review for training?” to “Add expert peer review?”
***When instructor clicks that checkbox, there will be a new tab named “Calibration”. Change the tab name from “Calibration” to “Expert review” on the assignment setting page [[File:Rsz_NewGeneral.png‎]]
**Student side
***Change the link title from “show calibration results” to “show expert peer-review results”[[File:Rsz_new_show.png|1000px|Updated]]
***Change the title in “response/show_calibration_results_for_student.html.erb” to start with “Expert review comparison report for”[[File:New_expert_review_page.png|1000px|Updated]]
*New features
**Let expert review support the vary-rubric-by-round functionality
**Support multiple expert reviews (Both TAs and instructors could do expert reviews)
*Tests
**Create expert_review_spec.rb file in spec/features folder
*Additional minor changes
**Reflect changes in DB schema at all places, including tests.
**Change the partial file name from “_calibration.html.erb” to “_expert_review.html.erb”
**Rename “response/show_calibration_results_for_student.html.erb” to “response/show_expert_review_results_for_student.html.erb” and also change other call sites
**

= Proposed Solution =
'''Change in database'''
The following schema changes will be implemented using a new migration file:
* “is_calibrated” field in assignment table to “has_expert_review”
* “calibrate_to” field in response_map table to “expert_review_to”

'''Change in User interface'''
The following files will be edited to reflect the changes in user interface as mentioned in tasks:
* #assignments/edit/_calibration.html.erb
* #response/show_calibration_results_for_student.html.erb
* #student_review/_responses.html.erb
* #student_review/list.html.erb
* #assignments/edit.html.erb
= Use Case Diagram =
[[File:Rsz_expertiza_uml-1.png]]

*Instructor and TAs are the "Experts" that can review the assignment.
*Multiple experts should be able to review the same assignment.
*When a student views the review, student should understand whether the review was made by an expert or a student.

=Major changes performed=
*app/controllers/response_controller.rb:
Method: show_calibration_results_for_student
Fetching all expert reviews performed for the respective assignment and respective team instead of fetching only instructor's response.
*app/assignments/edit/_expert_review.html.erb
Showing multiple rounds of View/Begin review as per the current round and number of reviews already done by the expert (as it happens for students).
*app/views/response/show_expert_review_results_for_student.erb
Showing calibrated response to students who have reviewed the assignment with responses of multiple experts for a particular round.
*app/views/student_review/_responses.html.erb
Showing links for calibrated result for each round.

= Test Plan =
*Existing tests should be changed according to changes in database schema and user interface.
*A new test file expert_review_spec.rb will be created to unit test the changes with the following steps:
* Log in using instructor's or teaching assistant's credentials.
* General tab should have the checkbox titled 'Add expert peer review?'
* Click on the checkbox.
* There should be a tab "Expert review" on the assignment setting page.
* Log out and log in back using student's credentials.
* There should be a link titled 'show expert peer-review results'
* Test multiple expert reviews by submitting multiple reviews when logged in as an instructor or TA for the same assignment.
* Also test the vary-rubric-by-round functionality.

=== New Test ===
New tests will be written to test the new features added, like :
* assignment should support multiple expert review.
* current assignment should support vary-rubric-by-round.

=Links=
1. Pull request - https://github.com/expertiza/expertiza/pull/1114

CSC/ECE 517 Fall 2017/E17A1 Expert Review.rb

2017-12-06T06:25:25Z

Anjain2:

This wiki page is the description of the E17A1 semester project - Let experts as well as students do reviews - for Fall 2017, CSC/ECE 517.

= Introduction =

[http://expertiza.ncsu.edu/ Expertiza] is an open source project based on [http://rubyonrails.org/ Ruby on Rails] framework. The Expertiza project is software to create reusable learning objects through peer review. It is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). It is used in select courses at NC State and by professors at several other colleges and universities. It also supports team projects, and the submission of almost any document type, including URLs and wiki pages. Expertiza enables the instructor to create new and customize existing assignments. It also enables the instructor to create a list of topics the students can sign up for as part of a project. Students can form teams in Expertiza to work on various projects and assignments. Expertiza supports submission across various document types, including the URLs and wiki pages.

= Existing Limitations =
*Currently, the functionality of calibration is limited. It does not support varying-rubric-by-round feature.
*For student side, there is no way to notify for an author to tell that a particular review that they received was submitted by an expert.
*Students are not able to see how an expert has rated the assignment, they can only see calibration results for calibrated assignments by clicking on the “Show calibration results” link.

= Tasks =
*Change in DB Schema
**“is_calibrated” field in assignment table to “has_expert_review”
**“calibrate_to” field in response_map table to “expert_review_to”
*User interface changes
**Original interface
[[File:Rsz 1old calibration page.png|1000px|Updated]]
[[File:Rsz_old_show.png|1000px|Updated]]
[[File:Rsz_GeneralTab.png]]
**Instructor side
***In assignment setting page (“General” tab), change the checkbox title from “Calibrated peer-review for training?” to “Add expert peer review?”
***When instructor clicks that checkbox, there will be a new tab named “Calibration”. Change the tab name from “Calibration” to “Expert review” on the assignment setting page [[File:Rsz_NewGeneral.png‎]]
**Student side
***Change the link title from “show calibration results” to “show expert peer-review results”[[File:Rsz_new_show.png|1000px|Updated]]
***Change the title in “response/show_calibration_results_for_student.html.erb” to start with “Expert review comparison report for”[[File:New_expert_review_page.png|1000px|Updated]]
*New features
**Let expert review support the vary-rubric-by-round functionality
**Support multiple expert reviews (Both TAs and instructors could do expert reviews)
*Tests
**Create expert_review_spec.rb file in spec/features folder
*Additional minor changes
**Reflect changes in DB schema at all places, including tests.
**Change the partial file name from “_calibration.html.erb” to “_expert_review.html.erb”
**Rename “response/show_calibration_results_for_student.html.erb” to “response/show_expert_review_results_for_student.html.erb” and also change other call sites
**

= Proposed Solution =
'''Change in database'''
The following schema changes will be implemented using a new migration file:
* “is_calibrated” field in assignment table to “has_expert_review”
* “calibrate_to” field in response_map table to “expert_review_to”

'''Change in User interface'''
The following files will be edited to reflect the changes in user interface as mentioned in tasks:
* #assignments/edit/_calibration.html.erb
* #response/show_calibration_results_for_student.html.erb
* #student_review/_responses.html.erb
* #student_review/list.html.erb
* #assignments/edit.html.erb
= Use Case Diagram =
[[File:Rsz_expertiza_uml-1.png]]

*Instructor and TAs are the "Experts" that can review the assignment.
*Multiple experts should be able to review the same assignment.
*When a student views the review, student should understand whether the review was made by an expert or a student.

= Test Plan =
*Existing tests should be changed according to changes in database schema and user interface.
*A new test file expert_review_spec.rb will be created to unit test the changes with the following steps:
* Log in using instructor's or teaching assistant's credentials.
* General tab should have the checkbox titled 'Add expert peer review?'
* Click on the checkbox.
* There should be a tab "Expert review" on the assignment setting page.
* Log out and log in back using student's credentials.
* There should be a link titled 'show expert peer-review results'
* Test multiple expert reviews by submitting multiple reviews when logged in as an instructor or TA for the same assignment.
* Also test the vary-rubric-by-round functionality.

=== New Test ===
New tests will be written to test the new features added, like :
* assignment should support multiple expert review.
* current assignment should support vary-rubric-by-round.

=Links=
1. Pull request - https://github.com/expertiza/expertiza/pull/1114

CSC/ECE 517 Fall 2017/E17A1 Expert Review.rb

2017-11-15T05:07:52Z

Anjain2: /* Use Case Diagram */

This wiki page is the description of the E17A1 semester project - Let experts as well as students do reviews - for Fall 2017, CSC/ECE 517.

= Introduction =

[http://expertiza.ncsu.edu/ Expertiza] is an open source project based on [http://rubyonrails.org/ Ruby on Rails] framework. The Expertiza project is software to create reusable learning objects through peer review. It is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). It is used in select courses at NC State and by professors at several other colleges and universities. It also supports team projects, and the submission of almost any document type, including URLs and wiki pages. Expertiza enables the instructor to create new and customize existing assignments. It also enables the instructor to create a list of topics the students can sign up for as part of a project. Students can form teams in Expertiza to work on various projects and assignments. Expertiza supports submission across various document types, including the URLs and wiki pages.

= Existing Limitations =
*Currently, the functionality of calibration is limited. It does not support varying-rubric-by-round feature.
*For student side, there is no way to notify for an author to tell that a particular review that they received was submitted by an expert.
*Students are not able to see how an expert has rated the assignment, they can only see calibration results for calibrated assignments by clicking on the “Show calibration results” link.

= Tasks =
*Change in DB Schema
**“is_calibrated” field in assignment table to “has_expert_review”
**“calibrate_to” field in response_map table to “expert_review_to”
*User interface changes
**Original interface
[[File:Rsz 1old calibration page.png|1000px|Updated]]
[[File:Rsz_old_show.png|1000px|Updated]]
[[File:Rsz_GeneralTab.png]]
**Instructor side
***In assignment setting page (“General” tab), change the checkbox title from “Calibrated peer-review for training?” to “Add expert peer review?”
***When instructor clicks that checkbox, there will be a new tab named “Calibration”. Change the tab name from “Calibration” to “Expert review” on the assignment setting page [[File:Rsz_NewGeneral.png‎]]
**Student side
***Change the link title from “show calibration results” to “show expert peer-review results”[[File:Rsz_new_show.png|1000px|Updated]]
***Change the title in “response/show_calibration_results_for_student.html.erb” to start with “Expert review comparison report for”[[File:New_expert_review_page.png|1000px|Updated]]
*New features
**Let expert review support the vary-rubric-by-round functionality
**Support multiple expert reviews (Both TAs and instructors could do expert reviews)
*Tests
**Create expert_review_spec.rb file in spec/features folder
*Additional minor changes
**Reflect changes in DB schema at all places, including tests.
**Change the partial file name from “_calibration.html.erb” to “_expert_review.html.erb”
**Rename “response/show_calibration_results_for_student.html.erb” to “response/show_expert_review_results_for_student.html.erb” and also change other call sites
**

= Proposed Solution =
'''Change in database'''
The following schema changes will be implemented using a new migration file:
* “is_calibrated” field in assignment table to “has_expert_review”
* “calibrate_to” field in response_map table to “expert_review_to”

'''Change in User interface'''
The following files will be edited to reflect the changes in user interface as mentioned in tasks:
* #assignments/edit/_calibration.html.erb
* #response/show_calibration_results_for_student.html.erb
* #student_review/_responses.html.erb
* #student_review/list.html.erb
* #assignments/edit.html.erb
= Use Case Diagram =
[[File:Rsz_expertiza_uml-1.png]]

*Instructor and TAs are the "Experts" that can review the assignment.
*Multiple experts should be able to review the same assignment.
*When a student views the review, student should understand whether the review was made by an expert or a student.

= Test Plan =
*Existing tests should be changed according to changes in database schema and user interface.
*A new test file expert_review_spec.rb will be created to unit test the changes with the following steps:
* Log in using instructor's or teaching assistant's credentials.
* General tab should have the checkbox titled 'Add expert peer review?'
* Click on the checkbox.
* There should be a tab "Expert review" on the assignment setting page.
* Log out and log in back using student's credentials.
* There should be a link titled 'show expert peer-review results'
* Test multiple expert reviews by submitting multiple reviews when logged in as an instructor or TA for the same assignment.
* Also test the vary-rubric-by-round functionality.

=== New Test ===
New tests will be written to test the new features added, like :
* assignment should support multiple expert review.
* current assignment should support vary-rubric-by-round.

CSC/ECE 517 Fall 2017/E17A1 Expert Review.rb

2017-11-15T05:03:43Z

Anjain2: /* Use Case Diagram */

This wiki page is the description of the E17A1 semester project - Let experts as well as students do reviews - for Fall 2017, CSC/ECE 517.

= Introduction =

[http://expertiza.ncsu.edu/ Expertiza] is an open source project based on [http://rubyonrails.org/ Ruby on Rails] framework. The Expertiza project is software to create reusable learning objects through peer review. It is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). It is used in select courses at NC State and by professors at several other colleges and universities. It also supports team projects, and the submission of almost any document type, including URLs and wiki pages. Expertiza enables the instructor to create new and customize existing assignments. It also enables the instructor to create a list of topics the students can sign up for as part of a project. Students can form teams in Expertiza to work on various projects and assignments. Expertiza supports submission across various document types, including the URLs and wiki pages.

= Existing Limitations =
*Currently, the functionality of calibration is limited. It does not support varying-rubric-by-round feature.
*For student side, there is no way to notify for an author to tell that a particular review that they received was submitted by an expert.
*Students are not able to see how an expert has rated the assignment, they can only see calibration results for calibrated assignments by clicking on the “Show calibration results” link.

= Tasks =
*Change in DB Schema
**“is_calibrated” field in assignment table to “has_expert_review”
**“calibrate_to” field in response_map table to “expert_review_to”
*User interface changes
**Original interface
[[File:Rsz 1old calibration page.png|1000px|Updated]]
[[File:Rsz_old_show.png|1000px|Updated]]
[[File:Rsz_GeneralTab.png]]
**Instructor side
***In assignment setting page (“General” tab), change the checkbox title from “Calibrated peer-review for training?” to “Add expert peer review?”
***When instructor clicks that checkbox, there will be a new tab named “Calibration”. Change the tab name from “Calibration” to “Expert review” on the assignment setting page [[File:Rsz_NewGeneral.png‎]]
**Student side
***Change the link title from “show calibration results” to “show expert peer-review results”[[File:Rsz_new_show.png|1000px|Updated]]
***Change the title in “response/show_calibration_results_for_student.html.erb” to start with “Expert review comparison report for”[[File:New_expert_review_page.png|1000px|Updated]]
*New features
**Let expert review support the vary-rubric-by-round functionality
**Support multiple expert reviews (Both TAs and instructors could do expert reviews)
*Tests
**Create expert_review_spec.rb file in spec/features folder
*Additional minor changes
**Reflect changes in DB schema at all places, including tests.
**Change the partial file name from “_calibration.html.erb” to “_expert_review.html.erb”
**Rename “response/show_calibration_results_for_student.html.erb” to “response/show_expert_review_results_for_student.html.erb” and also change other call sites
**

= Proposed Solution =
'''Change in database'''
The following schema changes will be implemented using a new migration file:
* “is_calibrated” field in assignment table to “has_expert_review”
* “calibrate_to” field in response_map table to “expert_review_to”

'''Change in User interface'''
The following files will be edited to reflect the changes in user interface as mentioned in tasks:
* #assignments/edit/_calibration.html.erb
* #response/show_calibration_results_for_student.html.erb
* #student_review/_responses.html.erb
* #student_review/list.html.erb
* #assignments/edit.html.erb
= Use Case Diagram =
[[File:Rsz_expertiza_uml-1.png]]

*Instructor and TAs are the "Experts" reviewing the assignment.
*Multiple experts should be able to review the same assignment.
*When a student views the review, student should understand whether the review was made by an expert or a student.

= Test Plan =
*Existing tests should be changed according to changes in database schema and user interface.
*A new test file expert_review_spec.rb will be created to unit test the changes with the following steps:
* Log in using instructor's or teaching assistant's credentials.
* General tab should have the checkbox titled 'Add expert peer review?'
* Click on the checkbox.
* There should be a tab "Expert review" on the assignment setting page.
* Log out and log in back using student's credentials.
* There should be a link titled 'show expert peer-review results'
* Test multiple expert reviews by submitting multiple reviews when logged in as an instructor or TA for the same assignment.
* Also test the vary-rubric-by-round functionality.

=== New Test ===
New tests will be written to test the new features added, like :
* assignment should support multiple expert review.
* current assignment should support vary-rubric-by-round.

CSC/ECE 517 Fall 2017/E17A1 Expert Review.rb

2017-11-07T04:05:05Z

Anjain2: /* Introduction */

This wiki page is the description of the E17A1 semester project - Let experts as well as students do reviews - for Fall 2017, CSC/ECE 517.

= Introduction =

[http://expertiza.ncsu.edu/ Expertiza] is an open source project based on [http://rubyonrails.org/ Ruby on Rails] framework. The Expertiza project is software to create reusable learning objects through peer review. It is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). It is used in select courses at NC State and by professors at several other colleges and universities. It also supports team projects, and the submission of almost any document type, including URLs and wiki pages. Expertiza enables the instructor to create new and customize existing assignments. It also enables the instructor to create a list of topics the students can sign up for as part of a project. Students can form teams in Expertiza to work on various projects and assignments. Expertiza supports submission across various document types, including the URLs and wiki pages.

= Existing Limitations =
*Currently, the functionality of calibration is limited. It does not support varying-rubric-by-round feature.
*For student side, there is no way to notify for an author to tell that a particular review that they received was submitted by an expert.
*Students are not able to see how an expert has rated the assignment, they can only see calibration results for calibrated assignments by clicking on the “Show calibration results” link.

= Tasks =
*Change in DB Schema
**“is_calibrated” field in assignment table to “has_expert_review”
**“calibrate_to” field in response_map table to “expert_review_to”
*User interface changes
**Instructor side
***In assignment setting page (“General” tab), change the checkbox title from “Calibrated peer-review for training?” to “Add expert peer review?”
***When instructor clicks that checkbox, there will be a new tab named “Calibration”. Change the tab name from “Calibration” to “Expert review” on the assignment setting page
**Student side
***Change the link title from “show calibration results” to “show expert peer-review results”
Original:
[[File: Old_Show_17a1.png]]
***Change the title in “response/show_calibration_results_for_student.html.erb” to start with “Expert review comparison report for”
*New features
**Let expert review support the vary-rubric-by-round functionality
**Support multiple expert reviews (Both TAs and instructors could do expert reviews)
*Tests
**Create expert_review_spec.rb file in spec/features folder
*Additional minor changes
**Reflect changes in DB schema at all places, including tests.
**Change the partial file name from “_calibration.html.erb” to “_expert_review.html.erb”
**Rename “response/show_calibration_results_for_student.html.erb” to “response/show_expert_review_results_for_student.html.erb” and also change other call sites
**

= Proposed Solution =
'''Change in database'''
The following schema changes will be implemented using a new migration file:
* “is_calibrated” field in assignment table to “has_expert_review”
* “calibrate_to” field in response_map table to “expert_review_to”

'''Change in User interface'''
The following files will be edited to reflect the changes in user interface as mentioned in tasks:
* #assignments/edit/_calibration.html.erb
* #response/show_calibration_results_for_student.html.erb
* #student_review/_responses.html.erb
* #student_review/list.html.erb
* #assignments/edit.html.erb

= Test Plan =
*Existing tests should be changed according to changes in database schema and user interface.
*A new test file expert_review_spec.rb will be created to unit test the changes with the following steps:
* Log in using instructor's or teaching assistant's credentials.
* General tab should have the checkbox titled 'Add expert peer review?'
* Click on the checkbox.
* There should be a tab "Expert review" on the assignment setting page.
* Log out and log in back using student's credentials.
* There should be a link titled 'show expert peer-review results'
* Test multiple expert reviews by submitting multiple reviews when logged in as an instructor or TA for the same assignment.
* Also test the vary-rubric-by-round functionality.

CSC/ECE 517 Fall 2017/E17A1 Expert Review.rb

2017-11-07T04:04:44Z

Anjain2: /* Introduction */

This wiki page is the description of the E17A1 semester project - Let experts as well as students do reviews - for Fall 2017, CSC/ECE 517.

= Introduction =

'''Expertiza'''
[http://expertiza.ncsu.edu/ Expertiza] is an open source project based on [http://rubyonrails.org/ Ruby on Rails] framework. The Expertiza project is software to create reusable learning objects through peer review. It is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). It is used in select courses at NC State and by professors at several other colleges and universities. It also supports team projects, and the submission of almost any document type, including URLs and wiki pages. Expertiza enables the instructor to create new and customize existing assignments. It also enables the instructor to create a list of topics the students can sign up for as part of a project. Students can form teams in Expertiza to work on various projects and assignments. Expertiza supports submission across various document types, including the URLs and wiki pages.

= Existing Limitations =
*Currently, the functionality of calibration is limited. It does not support varying-rubric-by-round feature.
*For student side, there is no way to notify for an author to tell that a particular review that they received was submitted by an expert.
*Students are not able to see how an expert has rated the assignment, they can only see calibration results for calibrated assignments by clicking on the “Show calibration results” link.

= Tasks =
*Change in DB Schema
**“is_calibrated” field in assignment table to “has_expert_review”
**“calibrate_to” field in response_map table to “expert_review_to”
*User interface changes
**Instructor side
***In assignment setting page (“General” tab), change the checkbox title from “Calibrated peer-review for training?” to “Add expert peer review?”
***When instructor clicks that checkbox, there will be a new tab named “Calibration”. Change the tab name from “Calibration” to “Expert review” on the assignment setting page
**Student side
***Change the link title from “show calibration results” to “show expert peer-review results”
Original:
[[File: Old_Show_17a1.png]]
***Change the title in “response/show_calibration_results_for_student.html.erb” to start with “Expert review comparison report for”
*New features
**Let expert review support the vary-rubric-by-round functionality
**Support multiple expert reviews (Both TAs and instructors could do expert reviews)
*Tests
**Create expert_review_spec.rb file in spec/features folder
*Additional minor changes
**Reflect changes in DB schema at all places, including tests.
**Change the partial file name from “_calibration.html.erb” to “_expert_review.html.erb”
**Rename “response/show_calibration_results_for_student.html.erb” to “response/show_expert_review_results_for_student.html.erb” and also change other call sites
**

= Proposed Solution =
'''Change in database'''
The following schema changes will be implemented using a new migration file:
* “is_calibrated” field in assignment table to “has_expert_review”
* “calibrate_to” field in response_map table to “expert_review_to”

'''Change in User interface'''
The following files will be edited to reflect the changes in user interface as mentioned in tasks:
* #assignments/edit/_calibration.html.erb
* #response/show_calibration_results_for_student.html.erb
* #student_review/_responses.html.erb
* #student_review/list.html.erb
* #assignments/edit.html.erb

= Test Plan =
*Existing tests should be changed according to changes in database schema and user interface.
*A new test file expert_review_spec.rb will be created to unit test the changes with the following steps:
* Log in using instructor's or teaching assistant's credentials.
* General tab should have the checkbox titled 'Add expert peer review?'
* Click on the checkbox.
* There should be a tab "Expert review" on the assignment setting page.
* Log out and log in back using student's credentials.
* There should be a link titled 'show expert peer-review results'
* Test multiple expert reviews by submitting multiple reviews when logged in as an instructor or TA for the same assignment.
* Also test the vary-rubric-by-round functionality.

CSC/ECE 517 Fall 2017/E17A1 Expert Review.rb

2017-11-07T04:03:06Z

Anjain2: /* Introduction */

This wiki page is the description of the E17A1 semester project - Let experts as well as students do reviews - for Fall 2017, CSC/ECE 517.

= Introduction =

== Expertiza ==
[http://expertiza.ncsu.edu/ Expertiza] is an open source project based on [http://rubyonrails.org/ Ruby on Rails] framework. The Expertiza project is software to create reusable learning objects through peer review. It is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). It is used in select courses at NC State and by professors at several other colleges and universities. It also supports team projects, and the submission of almost any document type, including URLs and wiki pages. Expertiza enables the instructor to create new and customize existing assignments. It also enables the instructor to create a list of topics the students can sign up for as part of a project. Students can form teams in Expertiza to work on various projects and assignments. Expertiza supports submission across various document types, including the URLs and wiki pages.

= Existing Limitations =
*Currently, the functionality of calibration is limited. It does not support varying-rubric-by-round feature.
*For student side, there is no way to notify for an author to tell that a particular review that they received was submitted by an expert.
*Students are not able to see how an expert has rated the assignment, they can only see calibration results for calibrated assignments by clicking on the “Show calibration results” link.

= Tasks =
*Change in DB Schema
**“is_calibrated” field in assignment table to “has_expert_review”
**“calibrate_to” field in response_map table to “expert_review_to”
*User interface changes
**Instructor side
***In assignment setting page (“General” tab), change the checkbox title from “Calibrated peer-review for training?” to “Add expert peer review?”
***When instructor clicks that checkbox, there will be a new tab named “Calibration”. Change the tab name from “Calibration” to “Expert review” on the assignment setting page
**Student side
***Change the link title from “show calibration results” to “show expert peer-review results”
Original:
[[File: Old_Show_17a1.png]]
***Change the title in “response/show_calibration_results_for_student.html.erb” to start with “Expert review comparison report for”
*New features
**Let expert review support the vary-rubric-by-round functionality
**Support multiple expert reviews (Both TAs and instructors could do expert reviews)
*Tests
**Create expert_review_spec.rb file in spec/features folder
*Additional minor changes
**Reflect changes in DB schema at all places, including tests.
**Change the partial file name from “_calibration.html.erb” to “_expert_review.html.erb”
**Rename “response/show_calibration_results_for_student.html.erb” to “response/show_expert_review_results_for_student.html.erb” and also change other call sites
**

= Proposed Solution =
'''Change in database'''
The following schema changes will be implemented using a new migration file:
* “is_calibrated” field in assignment table to “has_expert_review”
* “calibrate_to” field in response_map table to “expert_review_to”

'''Change in User interface'''
The following files will be edited to reflect the changes in user interface as mentioned in tasks:
* #assignments/edit/_calibration.html.erb
* #response/show_calibration_results_for_student.html.erb
* #student_review/_responses.html.erb
* #student_review/list.html.erb
* #assignments/edit.html.erb

= Test Plan =
*Existing tests should be changed according to changes in database schema and user interface.
*A new test file expert_review_spec.rb will be created to unit test the changes with the following steps:
* Log in using instructor's or teaching assistant's credentials.
* General tab should have the checkbox titled 'Add expert peer review?'
* Click on the checkbox.
* There should be a tab "Expert review" on the assignment setting page.
* Log out and log in back using student's credentials.
* There should be a link titled 'show expert peer-review results'
* Test multiple expert reviews by submitting multiple reviews when logged in as an instructor or TA for the same assignment.
* Also test the vary-rubric-by-round functionality.

CSC/ECE 517 Fall 2017/E17A1 Expert Review.rb

2017-11-07T04:00:34Z

Anjain2: /* Solution */

This wiki page is the description of the E17A1 semester project - Let experts as well as students do reviews - for Fall 2017, CSC/ECE 517.

= Introduction =

=== Expertiza ===
[http://expertiza.ncsu.edu/ Expertiza] is an open source project based on [http://rubyonrails.org/ Ruby on Rails] framework. The Expertiza project is software to create reusable learning objects through peer review. It is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). It is used in select courses at NC State and by professors at several other colleges and universities. It also supports team projects, and the submission of almost any document type, including URLs and wiki pages. Expertiza enables the instructor to create new and customize existing assignments. It also enables the instructor to create a list of topics the students can sign up for as part of a project. Students can form teams in Expertiza to work on various projects and assignments. Expertiza supports submission across various document types, including the URLs and wiki pages.

=== Existing Limitations ===
*Currently, the functionality of calibration is limited. It does not support varying-rubric-by-round feature.
*For student side, there is no way to notify for an author to tell that a particular review that they received was submitted by an expert.
*Students are not able to see how an expert has rated the assignment, they can only see calibration results for calibrated assignments by clicking on the “Show calibration results” link.

=== Tasks ===
*Change in DB Schema
**“is_calibrated” field in assignment table to “has_expert_review”
**“calibrate_to” field in response_map table to “expert_review_to”
*User interface changes
**Instructor side
***In assignment setting page (“General” tab), change the checkbox title from “Calibrated peer-review for training?” to “Add expert peer review?”
***When instructor clicks that checkbox, there will be a new tab named “Calibration”. Change the tab name from “Calibration” to “Expert review” on the assignment setting page
**Student side
***Change the link title from “show calibration results” to “show expert peer-review results”
Original:
[[File: Old_Show_17a1.png]]
***Change the title in “response/show_calibration_results_for_student.html.erb” to start with “Expert review comparison report for”
*New features
**Let expert review support the vary-rubric-by-round functionality
**Support multiple expert reviews (Both TAs and instructors could do expert reviews)
*Tests
**Create expert_review_spec.rb file in spec/features folder
*Additional minor changes
**Reflect changes in DB schema at all places, including tests.
**Change the partial file name from “_calibration.html.erb” to “_expert_review.html.erb”
**Rename “response/show_calibration_results_for_student.html.erb” to “response/show_expert_review_results_for_student.html.erb” and also change other call sites
**

=== Solution ===
'''Change in database'''
The following schema changes will be implemented using a new migration file:
* “is_calibrated” field in assignment table to “has_expert_review”
* “calibrate_to” field in response_map table to “expert_review_to”

'''Change in User interface'''
The following files will be edited to reflect the changes in user interface as mentioned in tasks:
* #assignments/edit/_calibration.html.erb
* #response/show_calibration_results_for_student.html.erb
* #student_review/_responses.html.erb
* #student_review/list.html.erb
* #assignments/edit.html.erb

= Test Plan =
*Existing tests should be changed according to changes in database schema and user interface.
*A new test file expert_review_spec.rb will be created to unit test the changes with the following steps:
* Log in using instructor's or teaching assistant's credentials.
* General tab should have the checkbox titled 'Add expert peer review?'
* Click on the checkbox.
* There should be a tab "Expert review" on the assignment setting page.
* Log out and log in back using student's credentials.
* There should be a link titled 'show expert peer-review results'
* Test multiple expert reviews by submitting multiple reviews when logged in as an instructor or TA for the same assignment.
* Also test the vary-rubric-by-round functionality.

CSC/ECE 517 Fall 2017/E17A1 Expert Review.rb

2017-11-07T03:53:19Z

Anjain2: /* Existing Limitations */

This wiki page is the description of the E17A1 semester project - Let experts as well as students do reviews - for Fall 2017, CSC/ECE 517.

= Introduction =

=== Expertiza ===
[http://expertiza.ncsu.edu/ Expertiza] is an open source project based on [http://rubyonrails.org/ Ruby on Rails] framework. The Expertiza project is software to create reusable learning objects through peer review. It is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). It is used in select courses at NC State and by professors at several other colleges and universities. It also supports team projects, and the submission of almost any document type, including URLs and wiki pages. Expertiza enables the instructor to create new and customize existing assignments. It also enables the instructor to create a list of topics the students can sign up for as part of a project. Students can form teams in Expertiza to work on various projects and assignments. Expertiza supports submission across various document types, including the URLs and wiki pages.

=== Existing Limitations ===
*Currently, the functionality of calibration is limited. It does not support varying-rubric-by-round feature.
*For student side, there is no way to notify for an author to tell that a particular review that they received was submitted by an expert.
*Students are not able to see how an expert has rated the assignment, they can only see calibration results for calibrated assignments by clicking on the “Show calibration results” link.

=== Tasks ===
*Change in DB Schema
**“is_calibrated” field in assignment table to “has_expert_review”
**“calibrate_to” field in response_map table to “expert_review_to”
*User interface changes
**Instructor side
***In assignment setting page (“General” tab), change the checkbox title from “Calibrated peer-review for training?” to “Add expert peer review?”
***When instructor clicks that checkbox, there will be a new tab named “Calibration”. Change the tab name from “Calibration” to “Expert review” on the assignment setting page
**Student side
***Change the link title from “show calibration results” to “show expert peer-review results”
Original:
[[Image: Old_Show_17a1.png]]
***Change the title in “response/show_calibration_results_for_student.html.erb” to start with “Expert review comparison report for”
*New features
**Let expert review support the vary-rubric-by-round functionality
**Support multiple expert reviews (Both TAs and instructors could do expert reviews)
*Tests
**Create expert_review_spec.rb file in spec/features folder
*Additional minor changes
**Reflect changes in DB schema at all places, including tests.
**Change the partial file name from “_calibration.html.erb” to “_expert_review.html.erb”
**Rename “response/show_calibration_results_for_student.html.erb” to “response/show_expert_review_results_for_student.html.erb” and also change other call sites
**

=== Solution ===
==== Change in database ====
The following schema changes will be implemented using a new migration file:
* “is_calibrated” field in assignment table to “has_expert_review”
* “calibrate_to” field in response_map table to “expert_review_to”

==== Change in User interface ====
The following files will be edited to reflect the changes in user interface as mentioned in tasks:
#assignments/edit/_calibration.html.erb
#response/show_calibration_results_for_student.html.erb
#student_review/_responses.html.erb
#student_review/list.html.erb
#assignments/edit.html.erb

= Test Plan =
*Existing tests should be changed according to changes in database schema and user interface.
*A new test file expert_review_spec.rb will be created to unit test the changes with the following steps:
* Log in using instructor's or teaching assistant's credentials.
* General tab should have the checkbox titled 'Add expert peer review?'
* Click on the checkbox.
* There should be a tab "Expert review" on the assignment setting page.
* Log out and log in back using student's credentials.
* There should be a link titled 'show expert peer-review results'
* Test multiple expert reviews by submitting multiple reviews when logged in as an instructor or TA for the same assignment.
* Also test the vary-rubric-by-round functionality.

CSC/ECE 517 Fall 2017/E17A1 Expert Review.rb

2017-11-07T03:50:27Z

Anjain2: /* Existing Limitations */

This wiki page is the description of the E17A1 semester project - Let experts as well as students do reviews - for Fall 2017, CSC/ECE 517.

= Introduction =

=== Expertiza ===
[http://expertiza.ncsu.edu/ Expertiza] is an open source project based on [http://rubyonrails.org/ Ruby on Rails] framework. The Expertiza project is software to create reusable learning objects through peer review. It is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). It is used in select courses at NC State and by professors at several other colleges and universities. It also supports team projects, and the submission of almost any document type, including URLs and wiki pages. Expertiza enables the instructor to create new and customize existing assignments. It also enables the instructor to create a list of topics the students can sign up for as part of a project. Students can form teams in Expertiza to work on various projects and assignments. Expertiza supports submission across various document types, including the URLs and wiki pages.

=== Existing Limitations ===
*Currently, the functionality of calibration is limited. It does not support varying-rubric-by-round feature.
*For student side, there is no way to notify for an author to tell that a particular review that they received was submitted by an expert.
*Moreover,if an expert (instructor or TA) has reviewed an assignment, the students should be able to see how that expert rated the assignment, just like they can see calibration results for calibrated assignments by clicking on the “Show calibration results” link.

=== Tasks ===
*Change in DB Schema
**“is_calibrated” field in assignment table to “has_expert_review”
**“calibrate_to” field in response_map table to “expert_review_to”
*User interface changes
**Instructor side
***In assignment setting page (“General” tab), change the checkbox title from “Calibrated peer-review for training?” to “Add expert peer review?”
***When instructor clicks that checkbox, there will be a new tab named “Calibration”. Change the tab name from “Calibration” to “Expert review” on the assignment setting page
**Student side
***Change the link title from “show calibration results” to “show expert peer-review results”
***Change the title in “response/show_calibration_results_for_student.html.erb” to start with “Expert review comparison report for”
*New features
**Let expert review support the vary-rubric-by-round functionality
**Support multiple expert reviews (Both TAs and instructors could do expert reviews)
*Tests
**Create expert_review_spec.rb file in spec/features folder
*Additional minor changes
**Reflect changes in DB schema at all places, including tests.
**Change the partial file name from “_calibration.html.erb” to “_expert_review.html.erb”
**Rename “response/show_calibration_results_for_student.html.erb” to “response/show_expert_review_results_for_student.html.erb” and also change other call sites
**

=== Solution ===
==== Change in database ====
The following schema changes will be implemented using a new migration file:
* “is_calibrated” field in assignment table to “has_expert_review”
* “calibrate_to” field in response_map table to “expert_review_to”

==== Change in User interface ====
The following files will be edited to reflect the changes in user interface as mentioned in tasks:
#assignments/edit/_calibration.html.erb
#response/show_calibration_results_for_student.html.erb
#student_review/_responses.html.erb
#student_review/list.html.erb
#assignments/edit.html.erb

= Test Plan =
*Existing tests should be changed according to changes in database schema and user interface.
*A new test file expert_review_spec.rb will be created to unit test the changes with the following steps:
* Log in using instructor's or teaching assistant's credentials.
* General tab should have the checkbox titled 'Add expert peer review?'
* Click on the checkbox.
* There should be a tab "Expert review" on the assignment setting page.
* Log out and log in back using student's credentials.
* There should be a link titled 'show expert peer-review results'
* Test multiple expert reviews by submitting multiple reviews when logged in as an instructor or TA for the same assignment.
* Also test the vary-rubric-by-round functionality.

CSC/ECE 517 Fall 2017/E17A1 Expert Review.rb

2017-11-07T03:07:38Z

Anjain2: First draft of Expertiza final project (Fall 2017) E17A1: Let experts as well as students do reviews

This wiki page is the description of the E17A1 semester project - Let experts as well as students do reviews - for Fall 2017, CSC/ECE 517.

= Introduction =

=== Expertiza ===
[http://expertiza.ncsu.edu/ Expertiza] is an open source project based on [http://rubyonrails.org/ Ruby on Rails] framework. The Expertiza project is software to create reusable learning objects through peer review. It is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). It is used in select courses at NC State and by professors at several other colleges and universities. It also supports team projects, and the submission of almost any document type, including URLs and wiki pages. Expertiza enables the instructor to create new and customize existing assignments. It also enables the instructor to create a list of topics the students can sign up for as part of a project. Students can form teams in Expertiza to work on various projects and assignments. Expertiza supports submission across various document types, including the URLs and wiki pages.

=== Existing Limitations ===
**Currently, the functionality of calibration is limited. It does not support varying-rubric-by-round feature.
**For student side, there is no way to notify for an author to tell that a particular review that they received was submitted by an expert.
**Moreover,if an expert (instructor or TA) has reviewed an assignment, the students should be able to see how that expert rated the assignment, just like they can see calibration results for calibrated assignments by clicking on the “Show calibration results” link.

=== Tasks ===
*Change in DB Schema
**“is_calibrated” field in assignment table to “has_expert_review”
**“calibrate_to” field in response_map table to “expert_review_to”
*User interface changes
**Instructor side
***In assignment setting page (“General” tab), change the checkbox title from “Calibrated peer-review for training?” to “Add expert peer review?”
***When instructor clicks that checkbox, there will be a new tab named “Calibration”. Change the tab name from “Calibration” to “Expert review” on the assignment setting page
**Student side
***Change the link title from “show calibration results” to “show expert peer-review results”
***Change the title in “response/show_calibration_results_for_student.html.erb” to start with “Expert review comparison report for”
*New features
**Let expert review support the vary-rubric-by-round functionality
**Support multiple expert reviews (Both TAs and instructors could do expert reviews)
*Tests
**Create expert_review_spec.rb file in spec/features folder
*Additional minor changes
**Reflect changes in DB schema at all places, including tests.
**Change the partial file name from “_calibration.html.erb” to “_expert_review.html.erb”
**Rename “response/show_calibration_results_for_student.html.erb” to “response/show_expert_review_results_for_student.html.erb” and also change other call sites
**

=== Solution ===
==== Change in database ====
The following schema changes will be implemented using a new migration file:
* “is_calibrated” field in assignment table to “has_expert_review”
* “calibrate_to” field in response_map table to “expert_review_to”

==== Change in User interface ====
The following files will be edited to reflect the changes in user interface as mentioned in tasks:
#assignments/edit/_calibration.html.erb
#response/show_calibration_results_for_student.html.erb
#student_review/_responses.html.erb
#student_review/list.html.erb
#assignments/edit.html.erb

= Test Plan =
*Existing tests should be changed according to changes in database schema and user interface.
*A new test file expert_review_spec.rb will be created to unit test the changes with the following steps:
* Log in using instructor's or teaching assistant's credentials.
* General tab should have the checkbox titled 'Add expert peer review?'
* Click on the checkbox.
* There should be a tab "Expert review" on the assignment setting page.
* Log out and log in back using student's credentials.
* There should be a link titled 'show expert peer-review results'
* Test multiple expert reviews by submitting multiple reviews when logged in as an instructor or TA for the same assignment.
* Also test the vary-rubric-by-round functionality.

CSC/ECE 517 Fall 2017/E1765 Rubrics.rb

2017-10-30T02:00:38Z

Anjain2: /* Testing from UI */

==E1765. OSS project Brown: Rubrics==

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

__TOC__

===About Expertiza===

[http://expertiza.ncsu.edu/ Expertiza] is an open source project based on [http://rubyonrails.org/ Ruby on Rails] framework. The Expertiza project is software to create reusable learning objects through peer review. It is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). It is used in select courses at NC State and by professors at several other colleges and universities. It also supports team projects, and the submission of almost any document type, including URLs and wiki pages. Expertiza enables the instructor to create new and customize existing assignments. It also enables the instructor to create a list of topics the students can sign up for as part of a project. Students can form teams in Expertiza to work on various projects and assignments. Expertiza supports submission across various document types, including the URLs and wiki pages.

===About Questionnaires Controller===
This class manages the questions attached to a questionnaire. It enables the creation of new questionnaires, and editing of existing questionnaires. The questions attached to the questionnaire can either be added/updated manually from the user interface or imported from an existing comma separated file. Once the questions are added/updated satisfactorily, they can be exported as a comma separated file. The controller currently has its own import and export methods to achieve this functionality.

====Problem Statement====
The following tasks were accomplished in this project:

* Fixed Issue [https://github.com/expertiza/expertiza/issues/696 696]: Instructors can make changes to each others' rubric, which should not happen
* Updated action_allowed for access_control to prevent unauthorized access of methods..
* Implemented new feature [https://github.com/expertiza/expertiza/issues/577 577]: Dumping and loading rubric criterion from CSV
* Refactored Questionnaires Controller to use existing Import and Export controllers.
* Added import method in Questions model to enable creation of questions from CSV.

====Current Implementation====

=====Functionality=====
* Any user irrespective of his/ her privileges can edit the questionnaire.
::The questionnaire should be restricted to be editable only by an instructor, administrator, or a super administrator. Furthermore, an existing questionnaire should be restricted to be editable only by the instructor who created the questionnaire in the first place.
* Import and Export functionality in the Questionnaires Controller
::The current implementation of the Questionnaires controller uses its own import and export methods. The Questionnaires controller should instead use the import and export implemented for the intended purpose. This promotes separation of concerns and code reuse.

=====Drawbacks and Solutions=====
* '''Problem 1''': An instructor can change others' review rubrics.
::The method action_allowed in Questionnaires controller returns true for any user role for all actions.
<pre>
def action_allowed?
['Super-Administrator',
'Administrator',
'Instructor',
'Teaching Assistant', 'Student'].include? current_role_name
end
</pre>
* '''Solution''': The implementation has been changed in such a way that the restriction on who is allowed to edit an existing rubric is as follows:
**A super administrator can edit any existing rubric.
**An administrator can edit any existing rubric.
**An instructor can only edit an existing rubric if it was created by him or her. An instructor cannot edit a rubric created by another instructor.
**The other functionalities have been left as it is, assuming that any user can create, view, etc. a new or existing rubric.

* '''Problem 2''': Import / Export controller
::The feature to allow importing Questions from files and exporting the questions had been broken since the refactoring of Questionnaire controller in [https://github.com/expertiza/expertiza/issues/577 summer 2015].

* '''Solution''': Solution
**The export file and import file views have to be enhanced to allow import/export of questions.
**Questionnaire edit view will have to be enhanced to render the export_file/start and import_file/start views which would support importing questions from and importing questions to CSV files.

====Enhancements====
*The action_allowed? method in Questionnaires controller has been modified to check for separate roles based on the action:
** If the action is edit, it checks that the user is a super administrator, an administrator, or an instructor who created the questionnaire in the first place.
** Else, all users are allowed to perform the action. (Assuming that even a student is allowed to add a questionnaire such as polls, surveys, etc)

<pre>
def action_allowed?
if action_name == "edit"
@questionnaire = Questionnaire.find(params[:id])
(['Super-Administrator',
'Administrator'
].include? current_role_name) ||
((['Instructor'].include? current_role_name) && current_user_id?( @questionnaire.instructor_id))
else
['Super-Administrator',
'Administrator',
'Instructor',
'Teaching Assistant', 'Student'].include? current_role_name
end
end
</pre>

*Integrating export_file and import_file section with the questionnaire view allows questions to be imported into system from file, example CSV file and also to export question entries from system into an external file.
*The export_file and import_file views are now partial rendered as part of the edit questionnaire view.
<pre>
<%= link_to 'Import Questionnaire', :controller=>'import_file', :action=>'start', :model => 'Question', :id=> @questionnaire.id, :expected_fields => 'txt, type ,seq,size, break_before' %>|
<%= link_to 'Export Questionnaire', :controller=>'export_file',:action=>'start',:model=> 'Question',:id=> @questionnaire.id %>
</pre>

====Testing from UI====
Following are a few testcases with respect to our code changes that can be tried from UI:
1. Log in as instructor 1 and create a new rubric.

2. Log in as another instructor. Go to [ Edit] page for the rubric and try to edit the questions.

3. Re log in as a student. Go to [ Edit] page for the rubric and try to edit the questions.

3. Re log in as instructor 1. Go to [ Edit] page for the rubric and try to edit the questions.

4. Re log in as a super administrator / admininstrator. Go to [ Edit] page for the rubric and try to edit the questionnaire.

5. "Export" button can be used to export all the questions and its associated details from the current questionnaire into a csv file that would named with the name of the questionnaire.

6. Choose the file that contains the questions to be imported into the questionnaire and press "Import" button to import the details into questionnaire.
*The columns expected in the csv file would be displayed in the same page in the expected order.

===References===

#[https://github.com/expertiza/expertiza Expertiza on GitHub]
#[https://github.com/akshayjain114/expertiza GitHub Project Repository Fork]
#[http://expertiza.ncsu.edu/ The live Expertiza website]
#[https://www.youtube.com/watch?v=UX74MCM-kK0&feature=youtu.be Demo link]
#[http://wikis.lib.ncsu.edu/index.php/Expertiza Expertiza project documentation wiki]
#[https://relishapp.com/rspec Rspec Documentation]
#Clean Code: A handbook of agile software craftsmanship. Author: Robert C Martin

CSC/ECE 517 Fall 2017/E1765 Rubrics.rb

2017-10-30T02:00:26Z

Anjain2: /* Automated Testing using RSPEC */

==E1765. OSS project Brown: Rubrics==

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

__TOC__

===About Expertiza===

[http://expertiza.ncsu.edu/ Expertiza] is an open source project based on [http://rubyonrails.org/ Ruby on Rails] framework. The Expertiza project is software to create reusable learning objects through peer review. It is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). It is used in select courses at NC State and by professors at several other colleges and universities. It also supports team projects, and the submission of almost any document type, including URLs and wiki pages. Expertiza enables the instructor to create new and customize existing assignments. It also enables the instructor to create a list of topics the students can sign up for as part of a project. Students can form teams in Expertiza to work on various projects and assignments. Expertiza supports submission across various document types, including the URLs and wiki pages.

===About Questionnaires Controller===
This class manages the questions attached to a questionnaire. It enables the creation of new questionnaires, and editing of existing questionnaires. The questions attached to the questionnaire can either be added/updated manually from the user interface or imported from an existing comma separated file. Once the questions are added/updated satisfactorily, they can be exported as a comma separated file. The controller currently has its own import and export methods to achieve this functionality.

====Problem Statement====
The following tasks were accomplished in this project:

* Fixed Issue [https://github.com/expertiza/expertiza/issues/696 696]: Instructors can make changes to each others' rubric, which should not happen
* Updated action_allowed for access_control to prevent unauthorized access of methods..
* Implemented new feature [https://github.com/expertiza/expertiza/issues/577 577]: Dumping and loading rubric criterion from CSV
* Refactored Questionnaires Controller to use existing Import and Export controllers.
* Added import method in Questions model to enable creation of questions from CSV.

====Current Implementation====

=====Functionality=====
* Any user irrespective of his/ her privileges can edit the questionnaire.
::The questionnaire should be restricted to be editable only by an instructor, administrator, or a super administrator. Furthermore, an existing questionnaire should be restricted to be editable only by the instructor who created the questionnaire in the first place.
* Import and Export functionality in the Questionnaires Controller
::The current implementation of the Questionnaires controller uses its own import and export methods. The Questionnaires controller should instead use the import and export implemented for the intended purpose. This promotes separation of concerns and code reuse.

=====Drawbacks and Solutions=====
* '''Problem 1''': An instructor can change others' review rubrics.
::The method action_allowed in Questionnaires controller returns true for any user role for all actions.
<pre>
def action_allowed?
['Super-Administrator',
'Administrator',
'Instructor',
'Teaching Assistant', 'Student'].include? current_role_name
end
</pre>
* '''Solution''': The implementation has been changed in such a way that the restriction on who is allowed to edit an existing rubric is as follows:
**A super administrator can edit any existing rubric.
**An administrator can edit any existing rubric.
**An instructor can only edit an existing rubric if it was created by him or her. An instructor cannot edit a rubric created by another instructor.
**The other functionalities have been left as it is, assuming that any user can create, view, etc. a new or existing rubric.

* '''Problem 2''': Import / Export controller
::The feature to allow importing Questions from files and exporting the questions had been broken since the refactoring of Questionnaire controller in [https://github.com/expertiza/expertiza/issues/577 summer 2015].

* '''Solution''': Solution
**The export file and import file views have to be enhanced to allow import/export of questions.
**Questionnaire edit view will have to be enhanced to render the export_file/start and import_file/start views which would support importing questions from and importing questions to CSV files.

====Enhancements====
*The action_allowed? method in Questionnaires controller has been modified to check for separate roles based on the action:
** If the action is edit, it checks that the user is a super administrator, an administrator, or an instructor who created the questionnaire in the first place.
** Else, all users are allowed to perform the action. (Assuming that even a student is allowed to add a questionnaire such as polls, surveys, etc)

<pre>
def action_allowed?
if action_name == "edit"
@questionnaire = Questionnaire.find(params[:id])
(['Super-Administrator',
'Administrator'
].include? current_role_name) ||
((['Instructor'].include? current_role_name) && current_user_id?( @questionnaire.instructor_id))
else
['Super-Administrator',
'Administrator',
'Instructor',
'Teaching Assistant', 'Student'].include? current_role_name
end
end
</pre>

*Integrating export_file and import_file section with the questionnaire view allows questions to be imported into system from file, example CSV file and also to export question entries from system into an external file.
*The export_file and import_file views are now partial rendered as part of the edit questionnaire view.
<pre>
<%= link_to 'Import Questionnaire', :controller=>'import_file', :action=>'start', :model => 'Question', :id=> @questionnaire.id, :expected_fields => 'txt, type ,seq,size, break_before' %>|
<%= link_to 'Export Questionnaire', :controller=>'export_file',:action=>'start',:model=> 'Question',:id=> @questionnaire.id %>
</pre>

====Testing from UI====
TODO: Get proper steps with user name and password
Following are a few testcases with respect to our code changes that can be tried from UI:
1. Log in as instructor 1 and create a new rubric.

2. Log in as another instructor. Go to [ Edit] page for the rubric and try to edit the questions.

3. Re log in as a student. Go to [ Edit] page for the rubric and try to edit the questions.

3. Re log in as instructor 1. Go to [ Edit] page for the rubric and try to edit the questions.

4. Re log in as a super administrator / admininstrator. Go to [ Edit] page for the rubric and try to edit the questionnaire.

5. "Export" button can be used to export all the questions and its associated details from the current questionnaire into a csv file that would named with the name of the questionnaire.

6. Choose the file that contains the questions to be imported into the questionnaire and press "Import" button to import the details into questionnaire.
*The columns expected in the csv file would be displayed in the same page in the expected order.

===References===

#[https://github.com/expertiza/expertiza Expertiza on GitHub]
#[https://github.com/akshayjain114/expertiza GitHub Project Repository Fork]
#[http://expertiza.ncsu.edu/ The live Expertiza website]
#[https://www.youtube.com/watch?v=UX74MCM-kK0&feature=youtu.be Demo link]
#[http://wikis.lib.ncsu.edu/index.php/Expertiza Expertiza project documentation wiki]
#[https://relishapp.com/rspec Rspec Documentation]
#Clean Code: A handbook of agile software craftsmanship. Author: Robert C Martin

CSC/ECE 517 Fall 2017/E1765 Rubrics.rb

2017-10-30T02:00:17Z

Anjain2: /* Code improvements */

==E1765. OSS project Brown: Rubrics==

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

__TOC__

===About Expertiza===

[http://expertiza.ncsu.edu/ Expertiza] is an open source project based on [http://rubyonrails.org/ Ruby on Rails] framework. The Expertiza project is software to create reusable learning objects through peer review. It is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). It is used in select courses at NC State and by professors at several other colleges and universities. It also supports team projects, and the submission of almost any document type, including URLs and wiki pages. Expertiza enables the instructor to create new and customize existing assignments. It also enables the instructor to create a list of topics the students can sign up for as part of a project. Students can form teams in Expertiza to work on various projects and assignments. Expertiza supports submission across various document types, including the URLs and wiki pages.

===About Questionnaires Controller===
This class manages the questions attached to a questionnaire. It enables the creation of new questionnaires, and editing of existing questionnaires. The questions attached to the questionnaire can either be added/updated manually from the user interface or imported from an existing comma separated file. Once the questions are added/updated satisfactorily, they can be exported as a comma separated file. The controller currently has its own import and export methods to achieve this functionality.

====Problem Statement====
The following tasks were accomplished in this project:

* Fixed Issue [https://github.com/expertiza/expertiza/issues/696 696]: Instructors can make changes to each others' rubric, which should not happen
* Updated action_allowed for access_control to prevent unauthorized access of methods..
* Implemented new feature [https://github.com/expertiza/expertiza/issues/577 577]: Dumping and loading rubric criterion from CSV
* Refactored Questionnaires Controller to use existing Import and Export controllers.
* Added import method in Questions model to enable creation of questions from CSV.

====Current Implementation====

=====Functionality=====
* Any user irrespective of his/ her privileges can edit the questionnaire.
::The questionnaire should be restricted to be editable only by an instructor, administrator, or a super administrator. Furthermore, an existing questionnaire should be restricted to be editable only by the instructor who created the questionnaire in the first place.
* Import and Export functionality in the Questionnaires Controller
::The current implementation of the Questionnaires controller uses its own import and export methods. The Questionnaires controller should instead use the import and export implemented for the intended purpose. This promotes separation of concerns and code reuse.

=====Drawbacks and Solutions=====
* '''Problem 1''': An instructor can change others' review rubrics.
::The method action_allowed in Questionnaires controller returns true for any user role for all actions.
<pre>
def action_allowed?
['Super-Administrator',
'Administrator',
'Instructor',
'Teaching Assistant', 'Student'].include? current_role_name
end
</pre>
* '''Solution''': The implementation has been changed in such a way that the restriction on who is allowed to edit an existing rubric is as follows:
**A super administrator can edit any existing rubric.
**An administrator can edit any existing rubric.
**An instructor can only edit an existing rubric if it was created by him or her. An instructor cannot edit a rubric created by another instructor.
**The other functionalities have been left as it is, assuming that any user can create, view, etc. a new or existing rubric.

* '''Problem 2''': Import / Export controller
::The feature to allow importing Questions from files and exporting the questions had been broken since the refactoring of Questionnaire controller in [https://github.com/expertiza/expertiza/issues/577 summer 2015].

* '''Solution''': Solution
**The export file and import file views have to be enhanced to allow import/export of questions.
**Questionnaire edit view will have to be enhanced to render the export_file/start and import_file/start views which would support importing questions from and importing questions to CSV files.

====Enhancements====
*The action_allowed? method in Questionnaires controller has been modified to check for separate roles based on the action:
** If the action is edit, it checks that the user is a super administrator, an administrator, or an instructor who created the questionnaire in the first place.
** Else, all users are allowed to perform the action. (Assuming that even a student is allowed to add a questionnaire such as polls, surveys, etc)

<pre>
def action_allowed?
if action_name == "edit"
@questionnaire = Questionnaire.find(params[:id])
(['Super-Administrator',
'Administrator'
].include? current_role_name) ||
((['Instructor'].include? current_role_name) && current_user_id?( @questionnaire.instructor_id))
else
['Super-Administrator',
'Administrator',
'Instructor',
'Teaching Assistant', 'Student'].include? current_role_name
end
end
</pre>

*Integrating export_file and import_file section with the questionnaire view allows questions to be imported into system from file, example CSV file and also to export question entries from system into an external file.
*The export_file and import_file views are now partial rendered as part of the edit questionnaire view.
<pre>
<%= link_to 'Import Questionnaire', :controller=>'import_file', :action=>'start', :model => 'Question', :id=> @questionnaire.id, :expected_fields => 'txt, type ,seq,size, break_before' %>|
<%= link_to 'Export Questionnaire', :controller=>'export_file',:action=>'start',:model=> 'Question',:id=> @questionnaire.id %>
</pre>

====Automated Testing using RSPEC====
TODO: If any

====Testing from UI====
TODO: Get proper steps with user name and password
Following are a few testcases with respect to our code changes that can be tried from UI:
1. Log in as instructor 1 and create a new rubric.

2. Log in as another instructor. Go to [ Edit] page for the rubric and try to edit the questions.

3. Re log in as a student. Go to [ Edit] page for the rubric and try to edit the questions.

3. Re log in as instructor 1. Go to [ Edit] page for the rubric and try to edit the questions.

4. Re log in as a super administrator / admininstrator. Go to [ Edit] page for the rubric and try to edit the questionnaire.

5. "Export" button can be used to export all the questions and its associated details from the current questionnaire into a csv file that would named with the name of the questionnaire.

6. Choose the file that contains the questions to be imported into the questionnaire and press "Import" button to import the details into questionnaire.
*The columns expected in the csv file would be displayed in the same page in the expected order.

===References===

#[https://github.com/expertiza/expertiza Expertiza on GitHub]
#[https://github.com/akshayjain114/expertiza GitHub Project Repository Fork]
#[http://expertiza.ncsu.edu/ The live Expertiza website]
#[https://www.youtube.com/watch?v=UX74MCM-kK0&feature=youtu.be Demo link]
#[http://wikis.lib.ncsu.edu/index.php/Expertiza Expertiza project documentation wiki]
#[https://relishapp.com/rspec Rspec Documentation]
#Clean Code: A handbook of agile software craftsmanship. Author: Robert C Martin

CSC/ECE 517 Fall 2017/E1765 Rubrics.rb

2017-10-30T01:59:52Z

Anjain2: /* Drawbacks and Solutions */

==E1765. OSS project Brown: Rubrics==

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

__TOC__

===About Expertiza===

[http://expertiza.ncsu.edu/ Expertiza] is an open source project based on [http://rubyonrails.org/ Ruby on Rails] framework. The Expertiza project is software to create reusable learning objects through peer review. It is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). It is used in select courses at NC State and by professors at several other colleges and universities. It also supports team projects, and the submission of almost any document type, including URLs and wiki pages. Expertiza enables the instructor to create new and customize existing assignments. It also enables the instructor to create a list of topics the students can sign up for as part of a project. Students can form teams in Expertiza to work on various projects and assignments. Expertiza supports submission across various document types, including the URLs and wiki pages.

===About Questionnaires Controller===
This class manages the questions attached to a questionnaire. It enables the creation of new questionnaires, and editing of existing questionnaires. The questions attached to the questionnaire can either be added/updated manually from the user interface or imported from an existing comma separated file. Once the questions are added/updated satisfactorily, they can be exported as a comma separated file. The controller currently has its own import and export methods to achieve this functionality.

====Problem Statement====
The following tasks were accomplished in this project:

* Fixed Issue [https://github.com/expertiza/expertiza/issues/696 696]: Instructors can make changes to each others' rubric, which should not happen
* Updated action_allowed for access_control to prevent unauthorized access of methods..
* Implemented new feature [https://github.com/expertiza/expertiza/issues/577 577]: Dumping and loading rubric criterion from CSV
* Refactored Questionnaires Controller to use existing Import and Export controllers.
* Added import method in Questions model to enable creation of questions from CSV.

====Current Implementation====

=====Functionality=====
* Any user irrespective of his/ her privileges can edit the questionnaire.
::The questionnaire should be restricted to be editable only by an instructor, administrator, or a super administrator. Furthermore, an existing questionnaire should be restricted to be editable only by the instructor who created the questionnaire in the first place.
* Import and Export functionality in the Questionnaires Controller
::The current implementation of the Questionnaires controller uses its own import and export methods. The Questionnaires controller should instead use the import and export implemented for the intended purpose. This promotes separation of concerns and code reuse.

=====Drawbacks and Solutions=====
* '''Problem 1''': An instructor can change others' review rubrics.
::The method action_allowed in Questionnaires controller returns true for any user role for all actions.
<pre>
def action_allowed?
['Super-Administrator',
'Administrator',
'Instructor',
'Teaching Assistant', 'Student'].include? current_role_name
end
</pre>
* '''Solution''': The implementation has been changed in such a way that the restriction on who is allowed to edit an existing rubric is as follows:
**A super administrator can edit any existing rubric.
**An administrator can edit any existing rubric.
**An instructor can only edit an existing rubric if it was created by him or her. An instructor cannot edit a rubric created by another instructor.
**The other functionalities have been left as it is, assuming that any user can create, view, etc. a new or existing rubric.

* '''Problem 2''': Import / Export controller
::The feature to allow importing Questions from files and exporting the questions had been broken since the refactoring of Questionnaire controller in [https://github.com/expertiza/expertiza/issues/577 summer 2015].

* '''Solution''': Solution
**The export file and import file views have to be enhanced to allow import/export of questions.
**Questionnaire edit view will have to be enhanced to render the export_file/start and import_file/start views which would support importing questions from and importing questions to CSV files.

====Enhancements====
*The action_allowed? method in Questionnaires controller has been modified to check for separate roles based on the action:
** If the action is edit, it checks that the user is a super administrator, an administrator, or an instructor who created the questionnaire in the first place.
** Else, all users are allowed to perform the action. (Assuming that even a student is allowed to add a questionnaire such as polls, surveys, etc)

<pre>
def action_allowed?
if action_name == "edit"
@questionnaire = Questionnaire.find(params[:id])
(['Super-Administrator',
'Administrator'
].include? current_role_name) ||
((['Instructor'].include? current_role_name) && current_user_id?( @questionnaire.instructor_id))
else
['Super-Administrator',
'Administrator',
'Instructor',
'Teaching Assistant', 'Student'].include? current_role_name
end
end
</pre>

*Integrating export_file and import_file section with the questionnaire view allows questions to be imported into system from file, example CSV file and also to export question entries from system into an external file.
*The export_file and import_file views are now partial rendered as part of the edit questionnaire view.
<pre>
<%= link_to 'Import Questionnaire', :controller=>'import_file', :action=>'start', :model => 'Question', :id=> @questionnaire.id, :expected_fields => 'txt, type ,seq,size, break_before' %>|
<%= link_to 'Export Questionnaire', :controller=>'export_file',:action=>'start',:model=> 'Question',:id=> @questionnaire.id %>
</pre>

=====Code improvements=====
TODO: If any

====Automated Testing using RSPEC====
TODO: If any

====Testing from UI====
TODO: Get proper steps with user name and password
Following are a few testcases with respect to our code changes that can be tried from UI:
1. Log in as instructor 1 and create a new rubric.

2. Log in as another instructor. Go to [ Edit] page for the rubric and try to edit the questions.

3. Re log in as a student. Go to [ Edit] page for the rubric and try to edit the questions.

3. Re log in as instructor 1. Go to [ Edit] page for the rubric and try to edit the questions.

4. Re log in as a super administrator / admininstrator. Go to [ Edit] page for the rubric and try to edit the questionnaire.

5. "Export" button can be used to export all the questions and its associated details from the current questionnaire into a csv file that would named with the name of the questionnaire.

6. Choose the file that contains the questions to be imported into the questionnaire and press "Import" button to import the details into questionnaire.
*The columns expected in the csv file would be displayed in the same page in the expected order.

===References===

#[https://github.com/expertiza/expertiza Expertiza on GitHub]
#[https://github.com/akshayjain114/expertiza GitHub Project Repository Fork]
#[http://expertiza.ncsu.edu/ The live Expertiza website]
#[https://www.youtube.com/watch?v=UX74MCM-kK0&feature=youtu.be Demo link]
#[http://wikis.lib.ncsu.edu/index.php/Expertiza Expertiza project documentation wiki]
#[https://relishapp.com/rspec Rspec Documentation]
#Clean Code: A handbook of agile software craftsmanship. Author: Robert C Martin

CSC/ECE 517 Fall 2017/E1765 Rubrics.rb

2017-10-30T01:58:59Z

Anjain2: /* References */

==E1765. OSS project Brown: Rubrics==

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

__TOC__

===About Expertiza===

[http://expertiza.ncsu.edu/ Expertiza] is an open source project based on [http://rubyonrails.org/ Ruby on Rails] framework. The Expertiza project is software to create reusable learning objects through peer review. It is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). It is used in select courses at NC State and by professors at several other colleges and universities. It also supports team projects, and the submission of almost any document type, including URLs and wiki pages. Expertiza enables the instructor to create new and customize existing assignments. It also enables the instructor to create a list of topics the students can sign up for as part of a project. Students can form teams in Expertiza to work on various projects and assignments. Expertiza supports submission across various document types, including the URLs and wiki pages.

===About Questionnaires Controller===
This class manages the questions attached to a questionnaire. It enables the creation of new questionnaires, and editing of existing questionnaires. The questions attached to the questionnaire can either be added/updated manually from the user interface or imported from an existing comma separated file. Once the questions are added/updated satisfactorily, they can be exported as a comma separated file. The controller currently has its own import and export methods to achieve this functionality.

====Problem Statement====
The following tasks were accomplished in this project:

* Fixed Issue [https://github.com/expertiza/expertiza/issues/696 696]: Instructors can make changes to each others' rubric, which should not happen
* Updated action_allowed for access_control to prevent unauthorized access of methods..
* Implemented new feature [https://github.com/expertiza/expertiza/issues/577 577]: Dumping and loading rubric criterion from CSV
* Refactored Questionnaires Controller to use existing Import and Export controllers.
* Added import method in Questions model to enable creation of questions from CSV.

====Current Implementation====

=====Functionality=====
* Any user irrespective of his/ her privileges can edit the questionnaire.
::The questionnaire should be restricted to be editable only by an instructor, administrator, or a super administrator. Furthermore, an existing questionnaire should be restricted to be editable only by the instructor who created the questionnaire in the first place.
* Import and Export functionality in the Questionnaires Controller
::The current implementation of the Questionnaires controller uses its own import and export methods. The Questionnaires controller should instead use the import and export implemented for the intended purpose. This promotes separation of concerns and code reuse.

=====Drawbacks and Solutions=====
* '''Problem 1''': An instructor can change others' review rubrics.
::The method action_allowed in Questionnaires controller returns true for any user role for all actions.
<pre>
def action_allowed?
['Super-Administrator',
'Administrator',
'Instructor',
'Teaching Assistant', 'Student'].include? current_role_name
end
</pre>
* '''Solution''': The implementation has been changed in such a way that the restriction on who is allowed to edit an existing rubric is as follows:
**A super administrator can edit any existing rubric.
**An administrator can edit any existing rubric.
**An instructor can only edit an existing rubric if it was created by him or her. An instructor cannot edit a rubric created by another instructor.
**The other functionalities have been left as it is, assuming that any user can create, view, etc. a new or existing rubric.

* '''Problem 2''': TODO: Add import/export problem
::The feature to allow importing Questions from files and exporting the questions had been broken since the refactoring of Questionnaire controller in [https://github.com/expertiza/expertiza/issues/577 summer 2015].

* '''Solution''': Solution
**The export file and import file views have to be enhanced to allow import/export of questions.
**Questionnaire edit view will have to be enhanced to render the export_file/start and import_file/start views which would support importing questions from and importing questions to CSV files.

====Enhancements====
*The action_allowed? method in Questionnaires controller has been modified to check for separate roles based on the action:
** If the action is edit, it checks that the user is a super administrator, an administrator, or an instructor who created the questionnaire in the first place.
** Else, all users are allowed to perform the action. (Assuming that even a student is allowed to add a questionnaire such as polls, surveys, etc)

<pre>
def action_allowed?
if action_name == "edit"
@questionnaire = Questionnaire.find(params[:id])
(['Super-Administrator',
'Administrator'
].include? current_role_name) ||
((['Instructor'].include? current_role_name) && current_user_id?( @questionnaire.instructor_id))
else
['Super-Administrator',
'Administrator',
'Instructor',
'Teaching Assistant', 'Student'].include? current_role_name
end
end
</pre>

*Integrating export_file and import_file section with the questionnaire view allows questions to be imported into system from file, example CSV file and also to export question entries from system into an external file.
*The export_file and import_file views are now partial rendered as part of the edit questionnaire view.
<pre>
<%= link_to 'Import Questionnaire', :controller=>'import_file', :action=>'start', :model => 'Question', :id=> @questionnaire.id, :expected_fields => 'txt, type ,seq,size, break_before' %>|
<%= link_to 'Export Questionnaire', :controller=>'export_file',:action=>'start',:model=> 'Question',:id=> @questionnaire.id %>
</pre>

=====Code improvements=====
TODO: If any

====Automated Testing using RSPEC====
TODO: If any

====Testing from UI====
TODO: Get proper steps with user name and password
Following are a few testcases with respect to our code changes that can be tried from UI:
1. Log in as instructor 1 and create a new rubric.

2. Log in as another instructor. Go to [ Edit] page for the rubric and try to edit the questions.

3. Re log in as a student. Go to [ Edit] page for the rubric and try to edit the questions.

3. Re log in as instructor 1. Go to [ Edit] page for the rubric and try to edit the questions.

4. Re log in as a super administrator / admininstrator. Go to [ Edit] page for the rubric and try to edit the questionnaire.

5. "Export" button can be used to export all the questions and its associated details from the current questionnaire into a csv file that would named with the name of the questionnaire.

6. Choose the file that contains the questions to be imported into the questionnaire and press "Import" button to import the details into questionnaire.
*The columns expected in the csv file would be displayed in the same page in the expected order.

===References===

#[https://github.com/expertiza/expertiza Expertiza on GitHub]
#[https://github.com/akshayjain114/expertiza GitHub Project Repository Fork]
#[http://expertiza.ncsu.edu/ The live Expertiza website]
#[https://www.youtube.com/watch?v=UX74MCM-kK0&feature=youtu.be Demo link]
#[http://wikis.lib.ncsu.edu/index.php/Expertiza Expertiza project documentation wiki]
#[https://relishapp.com/rspec Rspec Documentation]
#Clean Code: A handbook of agile software craftsmanship. Author: Robert C Martin

CSC/ECE 517 Fall 2017/E1765 Rubrics.rb.

2017-10-27T13:31:04Z

Anjain2: moved CSC/ECE 517 Fall 2017/E1765 Rubrics.rb. to Archived - CSC/ECE 517 Fall 2017/E1765 Rubrics.rb.: Incorrect name

#REDIRECT [[Archived - CSC/ECE 517 Fall 2017/E1765 Rubrics.rb.]]

Archived - CSC/ECE 517 Fall 2017/E1765 Rubrics.rb.

2017-10-27T13:31:04Z

Anjain2: moved CSC/ECE 517 Fall 2017/E1765 Rubrics.rb. to Archived - CSC/ECE 517 Fall 2017/E1765 Rubrics.rb.: Incorrect name

==E1765. OSS project Brown: Rubrics==

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

__TOC__

===About Expertiza===

[http://expertiza.ncsu.edu/ Expertiza] is an open source project based on [http://rubyonrails.org/ Ruby on Rails] framework. The Expertiza project is software to create reusable learning objects through peer review. It is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). It is used in select courses at NC State and by professors at several other colleges and universities. It also supports team projects, and the submission of almost any document type, including URLs and wiki pages. Expertiza enables the instructor to create new and customize existing assignments. It also enables the instructor to create a list of topics the students can sign up for as part of a project. Students can form teams in Expertiza to work on various projects and assignments. Expertiza supports submission across various document types, including the URLs and wiki pages.

===Problem Statement===
The following tasks were accomplished in this project:

* Fixed Issue [https://github.com/expertiza/expertiza/issues/696 696]: Instructors can make changes to each others' rubric, which should not happen
* Updated action_allowed for access_control to prevent unauthorized access of methods..
* Implemented new feature [https://github.com/expertiza/expertiza/issues/577 577]: Dumping and loading rubric criterion from CSV
* Refactored Questionnaires Controller to use existing Import and Export controllers.
* Added import method in Questions model to enable creation of questions from CSV.

===About Questionnaires Controller===
This class manages the questions attached to a questionnaire. It enables the creation of new questionnaires, and editing of existing questionnaires. The questions attached to the questionnaire can either be added/updated manually from the user interface or imported from an existing comma separated file. Once the questions are added/updated satisfactorily, they can be exported as a comma separated file. The controller currently has its own import and export methods to achieve this functionality.

===Current Implementation===

=====Functionality=====
* Any user irrespective of his/ her privileges can edit the questionnaire.
::The questionnaire should be restricted to be editable only by an instructor, administrator, or a super administrator. Furthermore, an existing questionnaire should be restricted to be editable only by the instructor who created the questionnaire in the first place.
* Import and Export functionality in the Questionnaires Controller
::The current implementation of the Questionnaires controller uses its own import and export methods. The Questionnaires controller should instead use the import and export implemented for the intended purpose. This promotes separation of concerns and code reuse.

=====Drawbacks and Solutions=====
* '''Problem 1''': An instructor can change others' review rubrics.
::The method action_allowed in Questionnaires controller returns true for any user role for all actions.
<pre>
def action_allowed?
['Super-Administrator',
'Administrator',
'Instructor',
'Teaching Assistant', 'Student'].include? current_role_name
end
</pre>
* '''Solution''': The implementation has been changed in such a way that the restriction on who is allowed to edit an existing rubric is as follows:
**A super administrator can edit any existing rubric.
**An administrator can edit any existing rubric.
**An instructor can only edit an existing rubric if it was created by him or her. An instructor cannot edit a rubric created by another instructor.
**The other functionalities have been left as it is, assuming that any user can create, view, etc. a new or existing rubric.

* '''Problem 2''': TODO: Add import/export problem
::Description
* '''Solution''': Solution

===New Implementation===
*The action_allowed? method in Questionnaires controller has been modified to check for separate roles based on the action:
** If the action is edit, it checks that the user is a super administrator, an administrator, or an instructor who created the questionnaire in the first place.
** Else, all users are allowed to perform the action. (Assuming that even a student is allowed to add a questionnaire such as polls, surveys, etc)

<pre>
def action_allowed?
if action_name == "edit"
@questionnaire = Questionnaire.find(params[:id])
(['Super-Administrator',
'Administrator'
].include? current_role_name) ||
((['Instructor'].include? current_role_name) && current_user_id?( @questionnaire.instructor_id))
else
['Super-Administrator',
'Administrator',
'Instructor',
'Teaching Assistant', 'Student'].include? current_role_name
end
end
</pre>

* TODO: Add new implementation for import/export functionality.

===Code improvements===
TODO: If any

===Automated Testing using RSPEC===
TODO: If any

===Testing from UI===
TODO: Get proper steps with user name and password
Following are a few testcases with respect to our code changes that can be tried from UI:
1. Log in as instructor 1 and create a new rubric.

2. Log in as another instructor. Go to [ Edit] page for the rubric and try to edit the questions.

3. Re log in as a student. Go to [ Edit] page for the rubric and try to edit the questions.

3. Re log in as instructor 1. Go to [ Edit] page for the rubric and try to edit the questions.

4. Re log in as a super administrator / admininstrator. Go to [ Edit] page for the rubric and try to edit the questions.

5. TODO: Add steps for import/export reuse

===References===

#[https://github.com/expertiza/expertiza Expertiza on GitHub]
#[https://github.com/akshayjain114/expertiza GitHub Project Repository Fork]
#[http://expertiza.ncsu.edu/ The live Expertiza website]
#[ Demo link]
#[http://wikis.lib.ncsu.edu/index.php/Expertiza Expertiza project documentation wiki]
#[https://relishapp.com/rspec Rspec Documentation]
#Clean Code: A handbook of agile software craftsmanship. Author: Robert C Martin

CSC/ECE 517 Fall 2017/E1765 Rubrics.rb

2017-10-27T13:28:59Z

Anjain2: Created page with "==E1765. OSS project Brown: Rubrics== This page provides a description of the Expertiza based OSS project. __TOC__ ===About Expertiza=== [http://expertiza.ncsu.edu/ Expert..."

==E1765. OSS project Brown: Rubrics==

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

__TOC__

===About Expertiza===

[http://expertiza.ncsu.edu/ Expertiza] is an open source project based on [http://rubyonrails.org/ Ruby on Rails] framework. The Expertiza project is software to create reusable learning objects through peer review. It is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). It is used in select courses at NC State and by professors at several other colleges and universities. It also supports team projects, and the submission of almost any document type, including URLs and wiki pages. Expertiza enables the instructor to create new and customize existing assignments. It also enables the instructor to create a list of topics the students can sign up for as part of a project. Students can form teams in Expertiza to work on various projects and assignments. Expertiza supports submission across various document types, including the URLs and wiki pages.

===Problem Statement===
The following tasks were accomplished in this project:

* Fixed Issue [https://github.com/expertiza/expertiza/issues/696 696]: Instructors can make changes to each others' rubric, which should not happen
* Updated action_allowed for access_control to prevent unauthorized access of methods..
* Implemented new feature [https://github.com/expertiza/expertiza/issues/577 577]: Dumping and loading rubric criterion from CSV
* Refactored Questionnaires Controller to use existing Import and Export controllers.
* Added import method in Questions model to enable creation of questions from CSV.

===About Questionnaires Controller===
This class manages the questions attached to a questionnaire. It enables the creation of new questionnaires, and editing of existing questionnaires. The questions attached to the questionnaire can either be added/updated manually from the user interface or imported from an existing comma separated file. Once the questions are added/updated satisfactorily, they can be exported as a comma separated file. The controller currently has its own import and export methods to achieve this functionality.

===Current Implementation===

=====Functionality=====
* Any user irrespective of his/ her privileges can edit the questionnaire.
::The questionnaire should be restricted to be editable only by an instructor, administrator, or a super administrator. Furthermore, an existing questionnaire should be restricted to be editable only by the instructor who created the questionnaire in the first place.
* Import and Export functionality in the Questionnaires Controller
::The current implementation of the Questionnaires controller uses its own import and export methods. The Questionnaires controller should instead use the import and export implemented for the intended purpose. This promotes separation of concerns and code reuse.

=====Drawbacks and Solutions=====
* '''Problem 1''': An instructor can change others' review rubrics.
::The method action_allowed in Questionnaires controller returns true for any user role for all actions.
<pre>
def action_allowed?
['Super-Administrator',
'Administrator',
'Instructor',
'Teaching Assistant', 'Student'].include? current_role_name
end
</pre>
* '''Solution''': The implementation has been changed in such a way that the restriction on who is allowed to edit an existing rubric is as follows:
**A super administrator can edit any existing rubric.
**An administrator can edit any existing rubric.
**An instructor can only edit an existing rubric if it was created by him or her. An instructor cannot edit a rubric created by another instructor.
**The other functionalities have been left as it is, assuming that any user can create, view, etc. a new or existing rubric.

* '''Problem 2''': TODO: Add import/export problem
::Description
* '''Solution''': Solution

===New Implementation===
*The action_allowed? method in Questionnaires controller has been modified to check for separate roles based on the action:
** If the action is edit, it checks that the user is a super administrator, an administrator, or an instructor who created the questionnaire in the first place.
** Else, all users are allowed to perform the action. (Assuming that even a student is allowed to add a questionnaire such as polls, surveys, etc)

<pre>
def action_allowed?
if action_name == "edit"
@questionnaire = Questionnaire.find(params[:id])
(['Super-Administrator',
'Administrator'
].include? current_role_name) ||
((['Instructor'].include? current_role_name) && current_user_id?( @questionnaire.instructor_id))
else
['Super-Administrator',
'Administrator',
'Instructor',
'Teaching Assistant', 'Student'].include? current_role_name
end
end
</pre>

* TODO: Add new implementation for import/export functionality.

===Code improvements===
TODO: If any

===Automated Testing using RSPEC===
TODO: If any

===Testing from UI===
TODO: Get proper steps with user name and password
Following are a few testcases with respect to our code changes that can be tried from UI:
1. Log in as instructor 1 and create a new rubric.

2. Log in as another instructor. Go to [ Edit] page for the rubric and try to edit the questions.

3. Re log in as a student. Go to [ Edit] page for the rubric and try to edit the questions.

3. Re log in as instructor 1. Go to [ Edit] page for the rubric and try to edit the questions.

4. Re log in as a super administrator / admininstrator. Go to [ Edit] page for the rubric and try to edit the questions.

5. TODO: Add steps for import/export reuse

===References===

#[https://github.com/expertiza/expertiza Expertiza on GitHub]
#[https://github.com/akshayjain114/expertiza GitHub Project Repository Fork]
#[http://expertiza.ncsu.edu/ The live Expertiza website]
#[ Demo link]
#[http://wikis.lib.ncsu.edu/index.php/Expertiza Expertiza project documentation wiki]
#[https://relishapp.com/rspec Rspec Documentation]
#Clean Code: A handbook of agile software craftsmanship. Author: Robert C Martin

Archived - CSC/ECE 517 Fall 2017/E1765 Rubrics.rb.

2017-10-27T13:27:21Z

Anjain2: /* E1765. OSS project Brown: Rubrics */

==E1765. OSS project Brown: Rubrics==

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

__TOC__

===About Expertiza===

[http://expertiza.ncsu.edu/ Expertiza] is an open source project based on [http://rubyonrails.org/ Ruby on Rails] framework. The Expertiza project is software to create reusable learning objects through peer review. It is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). It is used in select courses at NC State and by professors at several other colleges and universities. It also supports team projects, and the submission of almost any document type, including URLs and wiki pages. Expertiza enables the instructor to create new and customize existing assignments. It also enables the instructor to create a list of topics the students can sign up for as part of a project. Students can form teams in Expertiza to work on various projects and assignments. Expertiza supports submission across various document types, including the URLs and wiki pages.

===Problem Statement===
The following tasks were accomplished in this project:

* Fixed Issue [https://github.com/expertiza/expertiza/issues/696 696]: Instructors can make changes to each others' rubric, which should not happen
* Updated action_allowed for access_control to prevent unauthorized access of methods..
* Implemented new feature [https://github.com/expertiza/expertiza/issues/577 577]: Dumping and loading rubric criterion from CSV
* Refactored Questionnaires Controller to use existing Import and Export controllers.
* Added import method in Questions model to enable creation of questions from CSV.

===About Questionnaires Controller===
This class manages the questions attached to a questionnaire. It enables the creation of new questionnaires, and editing of existing questionnaires. The questions attached to the questionnaire can either be added/updated manually from the user interface or imported from an existing comma separated file. Once the questions are added/updated satisfactorily, they can be exported as a comma separated file. The controller currently has its own import and export methods to achieve this functionality.

===Current Implementation===

=====Functionality=====
* Any user irrespective of his/ her privileges can edit the questionnaire.
::The questionnaire should be restricted to be editable only by an instructor, administrator, or a super administrator. Furthermore, an existing questionnaire should be restricted to be editable only by the instructor who created the questionnaire in the first place.
* Import and Export functionality in the Questionnaires Controller
::The current implementation of the Questionnaires controller uses its own import and export methods. The Questionnaires controller should instead use the import and export implemented for the intended purpose. This promotes separation of concerns and code reuse.

=====Drawbacks and Solutions=====
* '''Problem 1''': An instructor can change others' review rubrics.
::The method action_allowed in Questionnaires controller returns true for any user role for all actions.
<pre>
def action_allowed?
['Super-Administrator',
'Administrator',
'Instructor',
'Teaching Assistant', 'Student'].include? current_role_name
end
</pre>
* '''Solution''': The implementation has been changed in such a way that the restriction on who is allowed to edit an existing rubric is as follows:
**A super administrator can edit any existing rubric.
**An administrator can edit any existing rubric.
**An instructor can only edit an existing rubric if it was created by him or her. An instructor cannot edit a rubric created by another instructor.
**The other functionalities have been left as it is, assuming that any user can create, view, etc. a new or existing rubric.

* '''Problem 2''': TODO: Add import/export problem
::Description
* '''Solution''': Solution

===New Implementation===
*The action_allowed? method in Questionnaires controller has been modified to check for separate roles based on the action:
** If the action is edit, it checks that the user is a super administrator, an administrator, or an instructor who created the questionnaire in the first place.
** Else, all users are allowed to perform the action. (Assuming that even a student is allowed to add a questionnaire such as polls, surveys, etc)

<pre>
def action_allowed?
if action_name == "edit"
@questionnaire = Questionnaire.find(params[:id])
(['Super-Administrator',
'Administrator'
].include? current_role_name) ||
((['Instructor'].include? current_role_name) && current_user_id?( @questionnaire.instructor_id))
else
['Super-Administrator',
'Administrator',
'Instructor',
'Teaching Assistant', 'Student'].include? current_role_name
end
end
</pre>

* TODO: Add new implementation for import/export functionality.

===Code improvements===
TODO: If any

===Automated Testing using RSPEC===
TODO: If any

===Testing from UI===
TODO: Get proper steps with user name and password
Following are a few testcases with respect to our code changes that can be tried from UI:
1. Log in as instructor 1 and create a new rubric.

2. Log in as another instructor. Go to [ Edit] page for the rubric and try to edit the questions.

3. Re log in as a student. Go to [ Edit] page for the rubric and try to edit the questions.

3. Re log in as instructor 1. Go to [ Edit] page for the rubric and try to edit the questions.

4. Re log in as a super administrator / admininstrator. Go to [ Edit] page for the rubric and try to edit the questions.

5. TODO: Add steps for import/export reuse

===References===

#[https://github.com/expertiza/expertiza Expertiza on GitHub]
#[https://github.com/akshayjain114/expertiza GitHub Project Repository Fork]
#[http://expertiza.ncsu.edu/ The live Expertiza website]
#[ Demo link]
#[http://wikis.lib.ncsu.edu/index.php/Expertiza Expertiza project documentation wiki]
#[https://relishapp.com/rspec Rspec Documentation]
#Clean Code: A handbook of agile software craftsmanship. Author: Robert C Martin

Archived - CSC/ECE 517 Fall 2017/E1765 Rubrics.rb.

2017-10-27T13:26:35Z

==E1765. OSS project Brown: Rubrics==

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

__TOC__

===About Expertiza===

[http://expertiza.ncsu.edu/ Expertiza] is an open source project based on [http://rubyonrails.org/ Ruby on Rails] framework. The Expertiza project is software to create reusable learning objects through peer review. It is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). It is used in select courses at NC State and by professors at several other colleges and universities. It also supports team projects, and the submission of almost any document type, including URLs and wiki pages. Expertiza enables the instructor to create new and customize existing assignments. It also enables the instructor to create a list of topics the students can sign up for as part of a project. Students can form teams in Expertiza to work on various projects and assignments. Expertiza supports submission across various document types, including the URLs and wiki pages.

===Problem Statement===
The following tasks were accomplished in this project:

* Fixed Issue [https://github.com/expertiza/expertiza/issues/696 696]: Instructors can make changes to each others' rubric, which should not happen
* Updated action_allowed for access_control to prevent unauthorized access of methods..
* Implemented new feature [https://github.com/expertiza/expertiza/issues/577 577]: Dumping and loading rubric criterion from CSV
* Refactored Questionnaires Controller to use existing Import and Export controllers.
* Added import method in Questions model to enable creation of questions from CSV.

===About Questionnaires Controller===
This class manages the questions attached to a questionnaire. It enables the creation of new questionnaires, and editing of existing questionnaires. The questions attached to the questionnaire can either be added/updated manually from the user interface or imported from an existing comma separated file. Once the questions are added/updated satisfactorily, they can be exported as a comma separated file. The controller currently has its own import and export methods to achieve this functionality.

===Current Implementation===

=====Functionality=====
* Any user irrespective of his/ her privileges can edit the questionnaire.
::The questionnaire should be restricted to be editable only by an instructor, administrator, or a super administrator. Furthermore, an existing questionnaire should be restricted to be editable only by the instructor who created the questionnaire in the first place.
* Import and Export functionality in the Questionnaires Controller
::The current implementation of the Questionnaires controller uses its own import and export methods. The Questionnaires controller should instead use the import and export implemented for the intended purpose. This promotes separation of concerns and code reuse.

=====Drawbacks and Solutions=====
* '''Problem 1''': An instructor can change others' review rubrics.
::The method action_allowed in Questionnaires controller returns true for any user role for all actions.
<pre>
def action_allowed?
['Super-Administrator',
'Administrator',
'Instructor',
'Teaching Assistant', 'Student'].include? current_role_name
end
</pre>
* '''Solution''': The implementation has been changed in such a way that the restriction on who is allowed to edit an existing rubric is as follows:
**A super administrator can edit any existing rubric.
**An administrator can edit any existing rubric.
**An instructor can only edit an existing rubric if it was created by him or her. An instructor cannot edit a rubric created by another instructor.
**The other functionalities have been left as it is, assuming that any user can create, view, etc. a new or existing rubric.

* '''Problem 2''': TODO: Add import/export problem
::Description
* '''Solution''': Solution

===New Implementation===
*The action_allowed? method in Questionnaires controller has been modified to check for separate roles based on the action:
** If the action is edit, it checks that the user is a super administrator, an administrator, or an instructor who created the questionnaire in the first place.
** Else, all users are allowed to perform the action. (Assuming that even a student is allowed to add a questionnaire such as polls, surveys, etc)

<pre>
def action_allowed?
if action_name == "edit"
@questionnaire = Questionnaire.find(params[:id])
(['Super-Administrator',
'Administrator'
].include? current_role_name) ||
((['Instructor'].include? current_role_name) && current_user_id?( @questionnaire.instructor_id))
else
['Super-Administrator',
'Administrator',
'Instructor',
'Teaching Assistant', 'Student'].include? current_role_name
end
end
</pre>

* TODO: Add new implementation for import/export functionality.

===Code improvements===
TODO: If any

===Automated Testing using RSPEC===
TODO: If any

===Testing from UI===
TODO: Get proper steps with user name and password
Following are a few testcases with respect to our code changes that can be tried from UI:
1. Log in as instructor 1 and create a new rubric.

2. Log in as another instructor. Go to [ Edit] page for the rubric and try to edit the questions.

3. Re log in as a student. Go to [ Edit] page for the rubric and try to edit the questions.

3. Re log in as instructor 1. Go to [ Edit] page for the rubric and try to edit the questions.

4. Re log in as a super administrator / admininstrator. Go to [ Edit] page for the rubric and try to edit the questions.

5. TODO: Add steps

===References===

#[https://github.com/expertiza/expertiza Expertiza on GitHub]
#[https://github.com/akshayjain114/expertiza GitHub Project Repository Fork]
#[http://expertiza.ncsu.edu/ The live Expertiza website]
#[ Demo link]
#[http://wikis.lib.ncsu.edu/index.php/Expertiza Expertiza project documentation wiki]
#[https://relishapp.com/rspec Rspec Documentation]
#Clean Code: A handbook of agile software craftsmanship. Author: Robert C Martin