Expertiza_Wiki - User contributions [en]

File:Spec4.png

2020-11-24T03:52:07Z

Nkashya:

CSC/ECE 517 Fall 2020 - E2075. calibration submissions should be copied along with calibration assignments

2020-11-24T03:51:52Z

Nkashya:

This wiki page describes the changes made under E2075, to ensure calibration submissions are copied along with calibration assignments for CSC/ECE 517, Fall 2020.

__TOC__

== About Expertiza ==
Expertiza is an open source project based on Ruby on Rails framework, created and maintained by the joint efforts of students and faculty at North Carolina State University.

It allows the instructors to create new assignments and customize new or existing assignments. Expertiza also allows an instructor to create a list of topics the students can sign up for. Students can form teams on the web application to work on various projects and assignments together. Additionally, students can peer review each other's submissions allowing them to improve upon their work. Expertiza supports submission across various document types, including the URLs and wiki pages.

= Introduction =

The Expertiza project allows "calibration assignments" to be performed where students are asked to review work that has also been reviewed by a member of the course staff. Calibration is the term used for rectifying, or checking or determining something. In the context of this project, a 'Calibrated review' is one which is performed by a student, so that (s)he can verify their work by comparing it with the instructor's response for the same assignment. If the student’s review “resembles” the staff-member’s review, then the student is presumed to be a competent reviewer. Since calibration reviews are meant as reference for better performance of peer reviews (which are performed later), they are not graded.

= Problem Statement =

== Project Purpose ==
Calibration submissions should be copied along with calibration assignments.

== Issue in current implementation ==
On creating a copy of a previous assignment, say for example Design Exercise, Fall '20 for the Fall '21 semester - the calibration assignments associated with it are not copied over. The instructor is required to impersonate extra participants, and submit work on behalf of each of the extra participants. This is obviously extra trouble, and it would be a lot more convenient if an instructor didn’t have to resubmit the same calibration submissions over and over, every semester. 

'''The following steps were taken to test the aforementioned issues:'''

'''Step 1:''' On copying the Design exercise assignment 
[[File:copy_2075.png]] 

'''Step 2:''' The original file contains the following calibration reviews 
[[File:cali_a_2075.png]] 

'''Step 3:''' However, the copy doesn't contain any of the calibrated reviews 
[[File:cali_b_2075.png]] 

= Implementation =
==MVC==

The project is implemented in Ruby on Rails that uses MVC architecture. We have three separate modules namely User Interface, Database Model and Control Flow(Model, View and Controller).

==Principle==

We tend to reuse the already existing functionalities and data to our design. The calibration reviews that are present in the previous exercise will be copied into the newly created exercise which would prevent the instructor to perform additional tasks of performing reviews repeatedly. This would also prevent code duplication and additional memory usage.

== Design ==
The following must be added to the current implementation:

* Participants with 'View' and 'Edit' actions in the calibration tab are copied over to the new version, as they are considered calibration submissions
* All hyperlinks and files associated with the above mentioned participants are copied over as well
* Participants with the 'Begin' action are not copied over
* A check is put in place to make sure that these steps are taken only for copying assignments with calibration reviews. This is signified by a calibration tab in the tool bar, on the edit page.

==Difference between Previous Implementation and Identified Solution ==

===Previous Implementation===

[[File:um20201.png]]

===Identified Implementation===

[[File:um20221.png]]

== Files Involved ==
* '''app/models/assignment_form.rb'''
* '''app/views/assignments/edit/_calibration.html.erb'''
* ''' db/schema.rb'''

== Changes in code ==
All changes mentioned below have been made in app/models/assignment_form.rb

[[File:Code_2075.jpeg |1000px|Image: 1000 pixels]] 
[[File:Code1_2075.jpeg |1000px|Image: 1000 pixels]] 
[[File:Code2_2075.jpeg |1000px|Image: 1000 pixels]] 
[[File:Code3_2075.jpeg |1000px|Image: 1000 pixels]] 
[[File:Code4_2075.jpeg |1000px|Image: 1000 pixels]] 
[[File:Code5_2075.jpeg |1000px|Image: 1000 pixels]] 
[[File:Code6_2075.jpeg |1000px|Image: 1000 pixels]]
[[File:Code7_2075.jpeg |1000px|Image: 1000 pixels]] 

= Test Plan =

== Manual Testing Plan ==
* To check if the UI is working as expected [No broken links]
* The submissions [Files and Hyperlinks] are copied when an assignment for calibration is copied.

=== Directions for Manual Testing ===
The following steps must be performed to test the project UI: 
'''Step 1:''' Log in as an Instructor, with Username - instructor6, Password - password 
[[File:logging_in_2075.png |1000px|Image: 1000 pixels]] 

'''Step 2:''' Find an assignment with calibration submissions present, which is represented by a calibration tab on the editing page. In this case, the assignment chosen is called "Design exercise" 
[[File:editing_2075.png |1000px|Image: 1000 pixels]] 

[[File:with_calib.png |1000px|Image: 1000 pixels]] 

'''Step 3:''' Copy the assignment, by selecting the icon shown below 
[[File:copying_2075.png |1000px|Image: 1000 pixels]] 

'''Step 4:''' On inspection of the copied assignment, it is observed that the calibration assignments have been copied over. 
[[File:copied_2075.png |1000px|Image: 1000 pixels]] 

'''Step 5:''' In the similar way, if the calibration tab has any files attached by the reviewers, then the files would get copied along with the participant details. Below is an assignment in which one participant has submitted a file named review1.txt in calibration.
[[File:orgde.png]]

'''Step 6:''' As the assignment has a file in calibration tab, even the copy of the assignment will have the same file with same content copied over to the calibration tab. Below is the copied assignment's calibration tab containing review1.txt created by the participant in original design exercise
[[File:copde.png]]

== Video illustrating changes ==
[https://www.youtube.com/watch?v=cyhy2mVXcPM&feature=youtu.be '''E2075 Video Link''']

== RSpec Testing Plan ==
Below are the rspec testcases used to test the application.

[[File:spec1.png]]

[[File:spec4.png]]

[[File:spec3.png]]

= Useful Links =
*[http://152.46.18.202:8080/ Server running changes implemented under E2075]
*[https://github.com/mounikaprakash/expertiza GitHub repo with changes made under E2075]
*[https://github.com/expertiza/expertiza Expertiza on GitHub]
*[http://expertiza.ncsu.edu/ The live Expertiza website]
*[http://research.csc.ncsu.edu/efg/expertiza Expertiza project Details]

= Team Information =
* Nischal Badarinath Kashyap
* Mounika Bachu
* Akshay Podila
* Dhanraj Raghunathan

File:Spec3.png

2020-11-24T03:51:24Z

Nkashya:

File:Spec2.png

2020-11-24T03:51:07Z

Nkashya: Nkashya uploaded a new version of File:Spec2.png

File:Spec1.png

2020-11-24T03:50:45Z

Nkashya:

CSC/ECE 517 Fall 2020 - E2075. calibration submissions should be copied along with calibration assignments

2020-11-24T03:49:49Z

Nkashya:

This wiki page describes the changes made under E2075, to ensure calibration submissions are copied along with calibration assignments for CSC/ECE 517, Fall 2020.

__TOC__

== About Expertiza ==
Expertiza is an open source project based on Ruby on Rails framework, created and maintained by the joint efforts of students and faculty at North Carolina State University.

It allows the instructors to create new assignments and customize new or existing assignments. Expertiza also allows an instructor to create a list of topics the students can sign up for. Students can form teams on the web application to work on various projects and assignments together. Additionally, students can peer review each other's submissions allowing them to improve upon their work. Expertiza supports submission across various document types, including the URLs and wiki pages.

= Introduction =

The Expertiza project allows "calibration assignments" to be performed where students are asked to review work that has also been reviewed by a member of the course staff. Calibration is the term used for rectifying, or checking or determining something. In the context of this project, a 'Calibrated review' is one which is performed by a student, so that (s)he can verify their work by comparing it with the instructor's response for the same assignment. If the student’s review “resembles” the staff-member’s review, then the student is presumed to be a competent reviewer. Since calibration reviews are meant as reference for better performance of peer reviews (which are performed later), they are not graded.

= Problem Statement =

== Project Purpose ==
Calibration submissions should be copied along with calibration assignments.

== Issue in current implementation ==
On creating a copy of a previous assignment, say for example Design Exercise, Fall '20 for the Fall '21 semester - the calibration assignments associated with it are not copied over. The instructor is required to impersonate extra participants, and submit work on behalf of each of the extra participants. This is obviously extra trouble, and it would be a lot more convenient if an instructor didn’t have to resubmit the same calibration submissions over and over, every semester. 

'''The following steps were taken to test the aforementioned issues:'''

'''Step 1:''' On copying the Design exercise assignment 
[[File:copy_2075.png]] 

'''Step 2:''' The original file contains the following calibration reviews 
[[File:cali_a_2075.png]] 

'''Step 3:''' However, the copy doesn't contain any of the calibrated reviews 
[[File:cali_b_2075.png]] 

= Implementation =
==MVC==

The project is implemented in Ruby on Rails that uses MVC architecture. We have three separate modules namely User Interface, Database Model and Control Flow(Model, View and Controller).

==Principle==

We tend to reuse the already existing functionalities and data to our design. The calibration reviews that are present in the previous exercise will be copied into the newly created exercise which would prevent the instructor to perform additional tasks of performing reviews repeatedly. This would also prevent code duplication and additional memory usage.

== Design ==
The following must be added to the current implementation:

* Participants with 'View' and 'Edit' actions in the calibration tab are copied over to the new version, as they are considered calibration submissions
* All hyperlinks and files associated with the above mentioned participants are copied over as well
* Participants with the 'Begin' action are not copied over
* A check is put in place to make sure that these steps are taken only for copying assignments with calibration reviews. This is signified by a calibration tab in the tool bar, on the edit page.

==Difference between Previous Implementation and Identified Solution ==

===Previous Implementation===

[[File:um20201.png]]

===Identified Implementation===

[[File:um20221.png]]

== Files Involved ==
* '''app/models/assignment_form.rb'''
* '''app/views/assignments/edit/_calibration.html.erb'''
* ''' db/schema.rb'''

== Changes in code ==
All changes mentioned below have been made in app/models/assignment_form.rb

[[File:Code_2075.jpeg |1000px|Image: 1000 pixels]] 
[[File:Code1_2075.jpeg |1000px|Image: 1000 pixels]] 
[[File:Code2_2075.jpeg |1000px|Image: 1000 pixels]] 
[[File:Code3_2075.jpeg |1000px|Image: 1000 pixels]] 
[[File:Code4_2075.jpeg |1000px|Image: 1000 pixels]] 
[[File:Code5_2075.jpeg |1000px|Image: 1000 pixels]] 
[[File:Code6_2075.jpeg |1000px|Image: 1000 pixels]]
[[File:Code7_2075.jpeg |1000px|Image: 1000 pixels]] 

= Test Plan =

== Manual Testing Plan ==
* To check if the UI is working as expected [No broken links]
* The submissions [Files and Hyperlinks] are copied when an assignment for calibration is copied.

=== Directions for Manual Testing ===
The following steps must be performed to test the project UI: 
'''Step 1:''' Log in as an Instructor, with Username - instructor6, Password - password 
[[File:logging_in_2075.png |1000px|Image: 1000 pixels]] 

'''Step 2:''' Find an assignment with calibration submissions present, which is represented by a calibration tab on the editing page. In this case, the assignment chosen is called "Design exercise" 
[[File:editing_2075.png |1000px|Image: 1000 pixels]] 

[[File:with_calib.png |1000px|Image: 1000 pixels]] 

'''Step 3:''' Copy the assignment, by selecting the icon shown below 
[[File:copying_2075.png |1000px|Image: 1000 pixels]] 

'''Step 4:''' On inspection of the copied assignment, it is observed that the calibration assignments have been copied over. 
[[File:copied_2075.png |1000px|Image: 1000 pixels]] 

'''Step 5:''' In the similar way, if the calibration tab has any files attached by the reviewers, then the files would get copied along with the participant details. Below is an assignment in which one participant has submitted a file named review1.txt in calibration.
[[File:orgde.png]]

'''Step 6:''' As the assignment has a file in calibration tab, even the copy of the assignment will have the same file with same content copied over to the calibration tab. Below is the copied assignment's calibration tab containing review1.txt created by the participant in original design exercise
[[File:copde.png]]

== Video illustrating changes ==
[https://www.youtube.com/watch?v=cyhy2mVXcPM&feature=youtu.be '''E2075 Video Link''']

== RSpec Testing Plan ==
Below are the rspec testcases used to test the application.

[[File:spec1.png]]

[[File:spec2.png]]

[[File:spec3.png]]

= Useful Links =
*[http://152.46.18.202:8080/ Server running changes implemented under E2075]
*[https://github.com/mounikaprakash/expertiza GitHub repo with changes made under E2075]
*[https://github.com/expertiza/expertiza Expertiza on GitHub]
*[http://expertiza.ncsu.edu/ The live Expertiza website]
*[http://research.csc.ncsu.edu/efg/expertiza Expertiza project Details]

= Team Information =
* Nischal Badarinath Kashyap
* Mounika Bachu
* Akshay Podila
* Dhanraj Raghunathan

CSC/ECE 517 Fall 2020 - E2075. calibration submissions should be copied along with calibration assignments

2020-11-24T03:45:35Z

Nkashya:

This wiki page describes the changes made under E2075, to ensure calibration submissions are copied along with calibration assignments for CSC/ECE 517, Fall 2020.

__TOC__

== About Expertiza ==
Expertiza is an open source project based on Ruby on Rails framework, created and maintained by the joint efforts of students and faculty at North Carolina State University.

It allows the instructors to create new assignments and customize new or existing assignments. Expertiza also allows an instructor to create a list of topics the students can sign up for. Students can form teams on the web application to work on various projects and assignments together. Additionally, students can peer review each other's submissions allowing them to improve upon their work. Expertiza supports submission across various document types, including the URLs and wiki pages.

= Introduction =

The Expertiza project allows "calibration assignments" to be performed where students are asked to review work that has also been reviewed by a member of the course staff. Calibration is the term used for rectifying, or checking or determining something. In the context of this project, a 'Calibrated review' is one which is performed by a student, so that (s)he can verify their work by comparing it with the instructor's response for the same assignment. If the student’s review “resembles” the staff-member’s review, then the student is presumed to be a competent reviewer. Since calibration reviews are meant as reference for better performance of peer reviews (which are performed later), they are not graded.

= Problem Statement =

== Project Purpose ==
Calibration submissions should be copied along with calibration assignments.

== Issue in current implementation ==
On creating a copy of a previous assignment, say for example Design Exercise, Fall '20 for the Fall '21 semester - the calibration assignments associated with it are not copied over. The instructor is required to impersonate extra participants, and submit work on behalf of each of the extra participants. This is obviously extra trouble, and it would be a lot more convenient if an instructor didn’t have to resubmit the same calibration submissions over and over, every semester. 

'''The following steps were taken to test the aforementioned issues:'''

'''Step 1:''' On copying the Design exercise assignment 
[[File:copy_2075.png]] 

'''Step 2:''' The original file contains the following calibration reviews 
[[File:cali_a_2075.png]] 

'''Step 3:''' However, the copy doesn't contain any of the calibrated reviews 
[[File:cali_b_2075.png]] 

= Implementation =
==MVC==

The project is implemented in Ruby on Rails that uses MVC architecture. We have three separate modules namely User Interface, Database Model and Control Flow(Model, View and Controller).

==Principle==

We tend to reuse the already existing functionalities and data to our design. The calibration reviews that are present in the previous exercise will be copied into the newly created exercise which would prevent the instructor to perform additional tasks of performing reviews repeatedly. This would also prevent code duplication and additional memory usage.

== Design ==
The following must be added to the current implementation:

* Participants with 'View' and 'Edit' actions in the calibration tab are copied over to the new version, as they are considered calibration submissions
* All hyperlinks and files associated with the above mentioned participants are copied over as well
* Participants with the 'Begin' action are not copied over
* A check is put in place to make sure that these steps are taken only for copying assignments with calibration reviews. This is signified by a calibration tab in the tool bar, on the edit page.

==Difference between Previous Implementation and Identified Solution ==

===Previous Implementation===

[[File:um20201.png]]

===Identified Implementation===

[[File:um20221.png]]

== Files Involved ==
* '''app/models/assignment_form.rb'''
* '''app/views/assignments/edit/_calibration.html.erb'''
* ''' db/schema.rb'''

== Changes in code ==
All changes mentioned below have been made in app/models/assignment_form.rb

[[File:Code_2075.jpeg |1000px|Image: 1000 pixels]] 
[[File:Code1_2075.jpeg |1000px|Image: 1000 pixels]] 
[[File:Code2_2075.jpeg |1000px|Image: 1000 pixels]] 
[[File:Code3_2075.jpeg |1000px|Image: 1000 pixels]] 
[[File:Code4_2075.jpeg |1000px|Image: 1000 pixels]] 
[[File:Code5_2075.jpeg |1000px|Image: 1000 pixels]] 
[[File:Code6_2075.jpeg |1000px|Image: 1000 pixels]]
[[File:Code7_2075.jpeg |1000px|Image: 1000 pixels]] 

= Test Plan =

== Manual Testing Plan ==
* To check if the UI is working as expected [No broken links]
* The submissions [Files and Hyperlinks] are copied when an assignment for calibration is copied.

=== Directions for Manual Testing ===
The following steps must be performed to test the project UI: 
'''Step 1:''' Log in as an Instructor, with Username - instructor6, Password - password 
[[File:logging_in_2075.png |1000px|Image: 1000 pixels]] 

'''Step 2:''' Find an assignment with calibration submissions present, which is represented by a calibration tab on the editing page. In this case, the assignment chosen is called "Design exercise" 
[[File:editing_2075.png |1000px|Image: 1000 pixels]] 

[[File:with_calib.png |1000px|Image: 1000 pixels]] 

'''Step 3:''' Copy the assignment, by selecting the icon shown below 
[[File:copying_2075.png |1000px|Image: 1000 pixels]] 

'''Step 4:''' On inspection of the copied assignment, it is observed that the calibration assignments have been copied over. 
[[File:copied_2075.png |1000px|Image: 1000 pixels]] 

'''Step 5:''' In the similar way, if the calibration tab has any files attached by the reviewers, then the files would get copied along with the participant details. Below is an assignment in which one participant has submitted a file named review1.txt in calibration.
[[File:orgde.png]]

'''Step 6:''' As the assignment has a file in calibration tab, even the copy of the assignment will have the same file with same content copied over to the calibration tab. Below is the copied assignment's calibration tab containing review1.txt created by the participant in original design exercise
[[File:copde.png]]

== Video illustrating changes ==
[https://www.youtube.com/watch?v=cyhy2mVXcPM&feature=youtu.be '''E2075 Video Link''']

== RSpec Testing Plan ==
Calibration checks were added to the assignments_contoller_spec.rb

[[File:Test1_2075.png |1000px|Image: 1000 pixels]] 
[[File:Test2_2075.png |1000px|Image: 1000 pixels]] 

= Useful Links =
*[http://152.46.18.202:8080/ Server running changes implemented under E2075]
*[https://github.com/mounikaprakash/expertiza GitHub repo with changes made under E2075]
*[https://github.com/expertiza/expertiza Expertiza on GitHub]
*[http://expertiza.ncsu.edu/ The live Expertiza website]
*[http://research.csc.ncsu.edu/efg/expertiza Expertiza project Details]

= Team Information =
* Nischal Badarinath Kashyap
* Mounika Bachu
* Akshay Podila
* Dhanraj Raghunathan

CSC/ECE 517 Fall 2020 - E2075. calibration submissions should be copied along with calibration assignments

2020-11-24T03:45:09Z

Nkashya:

This wiki page describes the changes made under E2075, to ensure calibration submissions are copied along with calibration assignments for CSC/ECE 517, Fall 2020.

__TOC__

== About Expertiza ==
Expertiza is an open source project based on Ruby on Rails framework, created and maintained by the joint efforts of students and faculty at North Carolina State University.

It allows the instructors to create new assignments and customize new or existing assignments. Expertiza also allows an instructor to create a list of topics the students can sign up for. Students can form teams on the web application to work on various projects and assignments together. Additionally, students can peer review each other's submissions allowing them to improve upon their work. Expertiza supports submission across various document types, including the URLs and wiki pages.

= Introduction =

The Expertiza project allows "calibration assignments" to be performed where students are asked to review work that has also been reviewed by a member of the course staff. Calibration is the term used for rectifying, or checking or determining something. In the context of this project, a 'Calibrated review' is one which is performed by a student, so that (s)he can verify their work by comparing it with the instructor's response for the same assignment. If the student’s review “resembles” the staff-member’s review, then the student is presumed to be a competent reviewer. Since calibration reviews are meant as reference for better performance of peer reviews (which are performed later), they are not graded.

= Problem Statement =

== Project Purpose ==
Calibration submissions should be copied along with calibration assignments.

== Issue in current implementation ==
On creating a copy of a previous assignment, say for example Design Exercise, Fall '20 for the Fall '21 semester - the calibration assignments associated with it are not copied over. The instructor is required to impersonate extra participants, and submit work on behalf of each of the extra participants. This is obviously extra trouble, and it would be a lot more convenient if an instructor didn’t have to resubmit the same calibration submissions over and over, every semester. 

'''The following steps were taken to test the aforementioned issues:'''

'''Step 1:''' On copying the Design exercise assignment 
[[File:copy_2075.png]] 

'''Step 2:''' The original file contains the following calibration reviews 
[[File:cali_a_2075.png]] 

'''Step 3:''' However, the copy doesn't contain any of the calibrated reviews 
[[File:cali_b_2075.png]] 

= Implementation =
==MVC==

The project is implemented in Ruby on Rails that uses MVC architecture. We have three separate modules namely User Interface, Database Model and Control Flow(Model, View and Controller).

==Principle==

We tend to reuse the already existing functionalities and data to our design. The calibration reviews that are present in the previous exercise will be copied into the newly created exercise which would prevent the instructor to perform additional tasks of performing reviews repeatedly. This would also prevent code duplication and additional memory usage.

== Design ==
The following must be added to the current implementation:

* Participants with 'View' and 'Edit' actions in the calibration tab are copied over to the new version, as they are considered calibration submissions
* All hyperlinks and files associated with the above mentioned participants are copied over as well
* Participants with the 'Begin' action are not copied over
* A check is put in place to make sure that these steps are taken only for copying assignments with calibration reviews. This is signified by a calibration tab in the tool bar, on the edit page.

==Difference between Previous Implementation and Identified Solution ==

===Previous Implementation===

[[File:um20201.png]]

===Identified Implementation===

[[File:um20221.png]]

== Files Involved ==
* '''app/models/assignment_form.rb'''
* '''app/views/assignments/edit/_calibration.html.erb'''
* ''' db/schema.rb'''

== Changes in code ==
All changes mentioned below have been made in app/models/assignment_form.rb

[[File:Code_2075.jpeg |1000px|Image: 1000 pixels]] 
[[File:Code1_2075.jpeg |1000px|Image: 1000 pixels]] 
[[File:Code2_2075.jpeg |1000px|Image: 1000 pixels]] 
[[File:Code3_2075.jpeg |1000px|Image: 1000 pixels]] 
[[File:Code4_2075.jpeg |1000px|Image: 1000 pixels]] 
[[File:Code5_2075.jpeg |1000px|Image: 1000 pixels]] 
[[File:Code6_2075.jpeg |1000px|Image: 1000 pixels]]
[[File:Code7_2075.jpeg |1000px|Image: 1000 pixels]] 

= Test Plan =

== Manual Testing Plan ==
* To check if the UI is working as expected [No broken links]
* The submissions [Files and Hyperlinks] are copied when an assignment for calibration is copied.

=== Directions for Manual Testing ===
The following steps must be performed to test the project UI: 
'''Step 1:''' Log in as an Instructor, with Username - instructor6, Password - password 
[[File:logging_in_2075.png |1000px|Image: 1000 pixels]] 

'''Step 2:''' Find an assignment with calibration submissions present, which is represented by a calibration tab on the editing page. In this case, the assignment chosen is called "Design exercise" 
[[File:editing_2075.png |1000px|Image: 1000 pixels]] 

[[File:with_calib.png |1000px|Image: 1000 pixels]] 

'''Step 3:''' Copy the assignment, by selecting the icon shown below 
[[File:copying_2075.png |1000px|Image: 1000 pixels]] 

'''Step 4:''' On inspection of the copied assignment, it is observed that the calibration assignments have been copied over. 
[[File:copied_2075.png |1000px|Image: 1000 pixels]] 

'''Step 5:''' In the similar way, if the calibration tab has any files attached by the reviewers, then the files would get copied along with the participant details. Below is an assignment in which one participant has submitted a file named review1.txt in calibration.
[[File:orgde.png]] <be>

'''Step 6:''' As the assignment has a file in calibration tab, even the copy of the assignment will have the same file with same content copied over to the calibration tab. Below is the copied assignment's calibration tab containing review1.txt created by the participant in original design exercise
[[File:copde.png]]

== Video illustrating changes ==
[https://www.youtube.com/watch?v=cyhy2mVXcPM&feature=youtu.be '''E2075 Video Link''']

== RSpec Testing Plan ==
Calibration checks were added to the assignments_contoller_spec.rb

[[File:Test1_2075.png |1000px|Image: 1000 pixels]] 
[[File:Test2_2075.png |1000px|Image: 1000 pixels]] 

= Useful Links =
*[http://152.46.18.202:8080/ Server running changes implemented under E2075]
*[https://github.com/mounikaprakash/expertiza GitHub repo with changes made under E2075]
*[https://github.com/expertiza/expertiza Expertiza on GitHub]
*[http://expertiza.ncsu.edu/ The live Expertiza website]
*[http://research.csc.ncsu.edu/efg/expertiza Expertiza project Details]

= Team Information =
* Nischal Badarinath Kashyap
* Mounika Bachu
* Akshay Podila
* Dhanraj Raghunathan

CSC/ECE 517 Fall 2020 - E2075. calibration submissions should be copied along with calibration assignments

2020-11-24T03:44:15Z

Nkashya:

This wiki page describes the changes made under E2075, to ensure calibration submissions are copied along with calibration assignments for CSC/ECE 517, Fall 2020.

__TOC__

== About Expertiza ==
Expertiza is an open source project based on Ruby on Rails framework, created and maintained by the joint efforts of students and faculty at North Carolina State University.

It allows the instructors to create new assignments and customize new or existing assignments. Expertiza also allows an instructor to create a list of topics the students can sign up for. Students can form teams on the web application to work on various projects and assignments together. Additionally, students can peer review each other's submissions allowing them to improve upon their work. Expertiza supports submission across various document types, including the URLs and wiki pages.

= Introduction =

The Expertiza project allows "calibration assignments" to be performed where students are asked to review work that has also been reviewed by a member of the course staff. Calibration is the term used for rectifying, or checking or determining something. In the context of this project, a 'Calibrated review' is one which is performed by a student, so that (s)he can verify their work by comparing it with the instructor's response for the same assignment. If the student’s review “resembles” the staff-member’s review, then the student is presumed to be a competent reviewer. Since calibration reviews are meant as reference for better performance of peer reviews (which are performed later), they are not graded.

= Problem Statement =

== Project Purpose ==
Calibration submissions should be copied along with calibration assignments.

== Issue in current implementation ==
On creating a copy of a previous assignment, say for example Design Exercise, Fall '20 for the Fall '21 semester - the calibration assignments associated with it are not copied over. The instructor is required to impersonate extra participants, and submit work on behalf of each of the extra participants. This is obviously extra trouble, and it would be a lot more convenient if an instructor didn’t have to resubmit the same calibration submissions over and over, every semester. 

'''The following steps were taken to test the aforementioned issues:'''

'''Step 1:''' On copying the Design exercise assignment 
[[File:copy_2075.png]] 

'''Step 2:''' The original file contains the following calibration reviews 
[[File:cali_a_2075.png]] 

'''Step 3:''' However, the copy doesn't contain any of the calibrated reviews 
[[File:cali_b_2075.png]] 

= Implementation =
==MVC==

The project is implemented in Ruby on Rails that uses MVC architecture. We have three separate modules namely User Interface, Database Model and Control Flow(Model, View and Controller).

==Principle==

We tend to reuse the already existing functionalities and data to our design. The calibration reviews that are present in the previous exercise will be copied into the newly created exercise which would prevent the instructor to perform additional tasks of performing reviews repeatedly. This would also prevent code duplication and additional memory usage.

== Design ==
The following must be added to the current implementation:

* Participants with 'View' and 'Edit' actions in the calibration tab are copied over to the new version, as they are considered calibration submissions
* All hyperlinks and files associated with the above mentioned participants are copied over as well
* Participants with the 'Begin' action are not copied over
* A check is put in place to make sure that these steps are taken only for copying assignments with calibration reviews. This is signified by a calibration tab in the tool bar, on the edit page.

==Difference between Previous Implementation and Identified Solution ==

===Previous Implementation===

[[File:um20201.png]]

===Identified Implementation===

[[File:um20221.png]]

== Files Involved ==
* '''app/models/assignment_form.rb'''
* '''app/views/assignments/edit/_calibration.html.erb'''
* ''' db/schema.rb'''

== Changes in code ==
All changes mentioned below have been made in app/models/assignment_form.rb

[[File:Code_2075.jpeg |1000px|Image: 1000 pixels]] 
[[File:Code1_2075.jpeg |1000px|Image: 1000 pixels]] 
[[File:Code2_2075.jpeg |1000px|Image: 1000 pixels]] 
[[File:Code3_2075.jpeg |1000px|Image: 1000 pixels]] 
[[File:Code4_2075.jpeg |1000px|Image: 1000 pixels]] 
[[File:Code5_2075.jpeg |1000px|Image: 1000 pixels]] 
[[File:Code6_2075.jpeg |1000px|Image: 1000 pixels]]
[[File:Code7_2075.jpeg |1000px|Image: 1000 pixels]] 

= Test Plan =

== Manual Testing Plan ==
* To check if the UI is working as expected [No broken links]
* The submissions [Files and Hyperlinks] are copied when an assignment for calibration is copied.

=== Directions for Manual Testing ===
The following steps must be performed to test the project UI: 
'''Step 1:''' Log in as an Instructor, with Username - instructor6, Password - password 
[[File:logging_in_2075.png |1000px|Image: 1000 pixels]] 

'''Step 2:''' Find an assignment with calibration submissions present, which is represented by a calibration tab on the editing page. In this case, the assignment chosen is called "Design exercise" 
[[File:editing_2075.png |1000px|Image: 1000 pixels]] 

[[File:with_calib.png |1000px|Image: 1000 pixels]] 

'''Step 3:''' Copy the assignment, by selecting the icon shown below 
[[File:copying_2075.png |1000px|Image: 1000 pixels]] 

'''Step 4:''' On inspection of the copied assignment, it is observed that the calibration assignments have been copied over. 
[[File:copied_2075.png |1000px|Image: 1000 pixels]] 

'''Step 5:''' In the similar way, if the calibration tab has any files attached by the reviewers, then the files would get copied along with the participant details. Below is an assignment in which one participant has submitted a file named review1.txt in calibration.
[[File:orgde.png]]

'''Step 6:''' As the assignment has a file in calibration tab, even the copy of the assignment will have the same file with same content copied over to the calibration tab. Below is the copied assignment's calibration tab containing review1.txt created by the participant in original design exercise
[[File:copde.png]]

== Video illustrating changes ==
[https://www.youtube.com/watch?v=cyhy2mVXcPM&feature=youtu.be '''E2075 Video Link''']

== RSpec Testing Plan ==
Calibration checks were added to the assignments_contoller_spec.rb

[[File:Test1_2075.png |1000px|Image: 1000 pixels]] 
[[File:Test2_2075.png |1000px|Image: 1000 pixels]] 

= Useful Links =
*[http://152.46.18.202:8080/ Server running changes implemented under E2075]
*[https://github.com/mounikaprakash/expertiza GitHub repo with changes made under E2075]
*[https://github.com/expertiza/expertiza Expertiza on GitHub]
*[http://expertiza.ncsu.edu/ The live Expertiza website]
*[http://research.csc.ncsu.edu/efg/expertiza Expertiza project Details]

= Team Information =
* Nischal Badarinath Kashyap
* Mounika Bachu
* Akshay Podila
* Dhanraj Raghunathan

File:Copde.png

2020-11-24T03:42:34Z

Nkashya:

File:Orgde.png

2020-11-24T03:42:21Z

Nkashya:

CSC/ECE 517 Fall 2020 - E2075. calibration submissions should be copied along with calibration assignments

2020-11-24T03:41:59Z

Nkashya:

This wiki page describes the changes made under E2075, to ensure calibration submissions are copied along with calibration assignments for CSC/ECE 517, Fall 2020.

__TOC__

== About Expertiza ==
Expertiza is an open source project based on Ruby on Rails framework, created and maintained by the joint efforts of students and faculty at North Carolina State University.

It allows the instructors to create new assignments and customize new or existing assignments. Expertiza also allows an instructor to create a list of topics the students can sign up for. Students can form teams on the web application to work on various projects and assignments together. Additionally, students can peer review each other's submissions allowing them to improve upon their work. Expertiza supports submission across various document types, including the URLs and wiki pages.

= Introduction =

The Expertiza project allows "calibration assignments" to be performed where students are asked to review work that has also been reviewed by a member of the course staff. Calibration is the term used for rectifying, or checking or determining something. In the context of this project, a 'Calibrated review' is one which is performed by a student, so that (s)he can verify their work by comparing it with the instructor's response for the same assignment. If the student’s review “resembles” the staff-member’s review, then the student is presumed to be a competent reviewer. Since calibration reviews are meant as reference for better performance of peer reviews (which are performed later), they are not graded.

= Problem Statement =

== Project Purpose ==
Calibration submissions should be copied along with calibration assignments.

== Issue in current implementation ==
On creating a copy of a previous assignment, say for example Design Exercise, Fall '20 for the Fall '21 semester - the calibration assignments associated with it are not copied over. The instructor is required to impersonate extra participants, and submit work on behalf of each of the extra participants. This is obviously extra trouble, and it would be a lot more convenient if an instructor didn’t have to resubmit the same calibration submissions over and over, every semester. 

'''The following steps were taken to test the aforementioned issues:'''

'''Step 1:''' On copying the Design exercise assignment 
[[File:copy_2075.png]] 

'''Step 2:''' The original file contains the following calibration reviews 
[[File:cali_a_2075.png]] 

'''Step 3:''' However, the copy doesn't contain any of the calibrated reviews 
[[File:cali_b_2075.png]] 

= Implementation =
==MVC==

The project is implemented in Ruby on Rails that uses MVC architecture. We have three separate modules namely User Interface, Database Model and Control Flow(Model, View and Controller).

==Principle==

We tend to reuse the already existing functionalities and data to our design. The calibration reviews that are present in the previous exercise will be copied into the newly created exercise which would prevent the instructor to perform additional tasks of performing reviews repeatedly. This would also prevent code duplication and additional memory usage.

== Design ==
The following must be added to the current implementation:

* Participants with 'View' and 'Edit' actions in the calibration tab are copied over to the new version, as they are considered calibration submissions
* All hyperlinks and files associated with the above mentioned participants are copied over as well
* Participants with the 'Begin' action are not copied over
* A check is put in place to make sure that these steps are taken only for copying assignments with calibration reviews. This is signified by a calibration tab in the tool bar, on the edit page.

==Difference between Previous Implementation and Identified Solution ==

===Previous Implementation===

[[File:um20201.png]]

===Identified Implementation===

[[File:um20221.png]]

== Files Involved ==
* '''app/models/assignment_form.rb'''
* '''app/views/assignments/edit/_calibration.html.erb'''
* ''' db/schema.rb'''

== Changes in code ==
All changes mentioned below have been made in app/models/assignment_form.rb

[[File:Code_2075.jpeg |1000px|Image: 1000 pixels]] 
[[File:Code1_2075.jpeg |1000px|Image: 1000 pixels]] 
[[File:Code2_2075.jpeg |1000px|Image: 1000 pixels]] 
[[File:Code3_2075.jpeg |1000px|Image: 1000 pixels]] 
[[File:Code4_2075.jpeg |1000px|Image: 1000 pixels]] 
[[File:Code5_2075.jpeg |1000px|Image: 1000 pixels]] 
[[File:Code6_2075.jpeg |1000px|Image: 1000 pixels]]
[[File:Code7_2075.jpeg |1000px|Image: 1000 pixels]] 

= Test Plan =

== Manual Testing Plan ==
* To check if the UI is working as expected [No broken links]
* The submissions [Files and Hyperlinks] are copied when an assignment for calibration is copied.

=== Directions for Manual Testing ===
The following steps must be performed to test the project UI: 
'''Step 1:''' Log in as an Instructor, with Username - instructor6, Password - password 
[[File:logging_in_2075.png |1000px|Image: 1000 pixels]] 

'''Step 2:''' Find an assignment with calibration submissions present, which is represented by a calibration tab on the editing page. In this case, the assignment chosen is called "Design exercise" 
[[File:editing_2075.png |1000px|Image: 1000 pixels]] 

[[File:with_calib.png |1000px|Image: 1000 pixels]] 

'''Step 3:''' Copy the assignment, by selecting the icon shown below 
[[File:copying_2075.png |1000px|Image: 1000 pixels]] 

'''Step 4:''' On inspection of the copied assignment, it is observed that the calibration assignments have been copied over. 
[[File:copied_2075.png |1000px|Image: 1000 pixels]] 

'''Step 5:''' In the similar way, if the calibration tab has any files attached by the reviewers, then the files would get copied along with the participant details. Below is an assignment in which one participant has submitted a file named review.txt in calibration. 
[[File:orgde.png]] <be>

'''Step 6:''' As the assignment has a file in calibration tab, even the copy of the assignment will have the same file with same content copied over to the calibration tab. Below is the copied assignment's calibration tab containing review.txt created by the participant in original design exercise 
[[File:copde.png]] <be>

== Video illustrating changes ==
[https://www.youtube.com/watch?v=cyhy2mVXcPM&feature=youtu.be '''E2075 Video Link''']

== RSpec Testing Plan ==
Calibration checks were added to the assignments_contoller_spec.rb

[[File:Test1_2075.png |1000px|Image: 1000 pixels]] 
[[File:Test2_2075.png |1000px|Image: 1000 pixels]] 

= Useful Links =
*[http://152.46.18.202:8080/ Server running changes implemented under E2075]
*[https://github.com/mounikaprakash/expertiza GitHub repo with changes made under E2075]
*[https://github.com/expertiza/expertiza Expertiza on GitHub]
*[http://expertiza.ncsu.edu/ The live Expertiza website]
*[http://research.csc.ncsu.edu/efg/expertiza Expertiza project Details]

= Team Information =
* Nischal Badarinath Kashyap
* Mounika Bachu
* Akshay Podila
* Dhanraj Raghunathan

File:Originalde.png

2020-11-24T03:40:46Z

Nkashya: Nkashya uploaded a new version of File:Originalde.png

File:Copiedde.png

2020-11-24T03:40:13Z

Nkashya:

File:Originalde.png

2020-11-24T03:39:55Z

Nkashya:

CSC/ECE 517 Fall 2020 - E2075. calibration submissions should be copied along with calibration assignments

2020-11-24T03:39:27Z

Nkashya:

This wiki page describes the changes made under E2075, to ensure calibration submissions are copied along with calibration assignments for CSC/ECE 517, Fall 2020.

__TOC__

== About Expertiza ==
Expertiza is an open source project based on Ruby on Rails framework, created and maintained by the joint efforts of students and faculty at North Carolina State University.

It allows the instructors to create new assignments and customize new or existing assignments. Expertiza also allows an instructor to create a list of topics the students can sign up for. Students can form teams on the web application to work on various projects and assignments together. Additionally, students can peer review each other's submissions allowing them to improve upon their work. Expertiza supports submission across various document types, including the URLs and wiki pages.

= Introduction =

The Expertiza project allows "calibration assignments" to be performed where students are asked to review work that has also been reviewed by a member of the course staff. Calibration is the term used for rectifying, or checking or determining something. In the context of this project, a 'Calibrated review' is one which is performed by a student, so that (s)he can verify their work by comparing it with the instructor's response for the same assignment. If the student’s review “resembles” the staff-member’s review, then the student is presumed to be a competent reviewer. Since calibration reviews are meant as reference for better performance of peer reviews (which are performed later), they are not graded.

= Problem Statement =

== Project Purpose ==
Calibration submissions should be copied along with calibration assignments.

== Issue in current implementation ==
On creating a copy of a previous assignment, say for example Design Exercise, Fall '20 for the Fall '21 semester - the calibration assignments associated with it are not copied over. The instructor is required to impersonate extra participants, and submit work on behalf of each of the extra participants. This is obviously extra trouble, and it would be a lot more convenient if an instructor didn’t have to resubmit the same calibration submissions over and over, every semester. 

'''The following steps were taken to test the aforementioned issues:'''

'''Step 1:''' On copying the Design exercise assignment 
[[File:copy_2075.png]] 

'''Step 2:''' The original file contains the following calibration reviews 
[[File:cali_a_2075.png]] 

'''Step 3:''' However, the copy doesn't contain any of the calibrated reviews 
[[File:cali_b_2075.png]] 

= Implementation =
==MVC==

The project is implemented in Ruby on Rails that uses MVC architecture. We have three separate modules namely User Interface, Database Model and Control Flow(Model, View and Controller).

==Principle==

We tend to reuse the already existing functionalities and data to our design. The calibration reviews that are present in the previous exercise will be copied into the newly created exercise which would prevent the instructor to perform additional tasks of performing reviews repeatedly. This would also prevent code duplication and additional memory usage.

== Design ==
The following must be added to the current implementation:

* Participants with 'View' and 'Edit' actions in the calibration tab are copied over to the new version, as they are considered calibration submissions
* All hyperlinks and files associated with the above mentioned participants are copied over as well
* Participants with the 'Begin' action are not copied over
* A check is put in place to make sure that these steps are taken only for copying assignments with calibration reviews. This is signified by a calibration tab in the tool bar, on the edit page.

==Difference between Previous Implementation and Identified Solution ==

===Previous Implementation===

[[File:um20201.png]]

===Identified Implementation===

[[File:um20221.png]]

== Files Involved ==
* '''app/models/assignment_form.rb'''
* '''app/views/assignments/edit/_calibration.html.erb'''
* ''' db/schema.rb'''

== Changes in code ==
All changes mentioned below have been made in app/models/assignment_form.rb

[[File:Code_2075.jpeg |1000px|Image: 1000 pixels]] 
[[File:Code1_2075.jpeg |1000px|Image: 1000 pixels]] 
[[File:Code2_2075.jpeg |1000px|Image: 1000 pixels]] 
[[File:Code3_2075.jpeg |1000px|Image: 1000 pixels]] 
[[File:Code4_2075.jpeg |1000px|Image: 1000 pixels]] 
[[File:Code5_2075.jpeg |1000px|Image: 1000 pixels]] 
[[File:Code6_2075.jpeg |1000px|Image: 1000 pixels]]
[[File:Code7_2075.jpeg |1000px|Image: 1000 pixels]] 

= Test Plan =

== Manual Testing Plan ==
* To check if the UI is working as expected [No broken links]
* The submissions [Files and Hyperlinks] are copied when an assignment for calibration is copied.

=== Directions for Manual Testing ===
The following steps must be performed to test the project UI: 
'''Step 1:''' Log in as an Instructor, with Username - instructor6, Password - password 
[[File:logging_in_2075.png |1000px|Image: 1000 pixels]] 

'''Step 2:''' Find an assignment with calibration submissions present, which is represented by a calibration tab on the editing page. In this case, the assignment chosen is called "Design exercise" 
[[File:editing_2075.png |1000px|Image: 1000 pixels]] 

[[File:with_calib.png |1000px|Image: 1000 pixels]] 

'''Step 3:''' Copy the assignment, by selecting the icon shown below 
[[File:copying_2075.png |1000px|Image: 1000 pixels]] 

'''Step 4:''' On inspection of the copied assignment, it is observed that the calibration assignments have been copied over. 
[[File:copied_2075.png |1000px|Image: 1000 pixels]] 

'''Step 5:''' In the similar way, if the calibration tab has any files attached by the reviewers, then the files would get copied along with the participant details. Below is an assignment in which one participant has submitted a file named review.txt in calibration. 
[[File:originalde.png |1000px|Image: 1000 pixels]] <be>

'''Step 6:''' As the assignment has a file in calibration tab, even the copy of the assignment will have the same file with same content copied over to the calibration tab. Below is the copied assignment's calibration tab containing review.txt created by the participant in original design exercise 
[[File:copiedde.png |1000px|Image: 1000 pixels]] <be>

== Video illustrating changes ==
[https://www.youtube.com/watch?v=cyhy2mVXcPM&feature=youtu.be '''E2075 Video Link''']

== RSpec Testing Plan ==
Calibration checks were added to the assignments_contoller_spec.rb

[[File:Test1_2075.png |1000px|Image: 1000 pixels]] 
[[File:Test2_2075.png |1000px|Image: 1000 pixels]] 

= Useful Links =
*[http://152.46.18.202:8080/ Server running changes implemented under E2075]
*[https://github.com/mounikaprakash/expertiza GitHub repo with changes made under E2075]
*[https://github.com/expertiza/expertiza Expertiza on GitHub]
*[http://expertiza.ncsu.edu/ The live Expertiza website]
*[http://research.csc.ncsu.edu/efg/expertiza Expertiza project Details]

= Team Information =
* Nischal Badarinath Kashyap
* Mounika Bachu
* Akshay Podila
* Dhanraj Raghunathan

CSC/ECE 517 Fall 2020 - E2075. calibration submissions should be copied along with calibration assignments

2020-10-29T03:22:12Z

Nkashya:

This wiki page describes the changes made under E2075, to ensure calibration submissions are copied along with calibration assignments for CSC/ECE 517, Fall 2020.

__TOC__

== About Expertiza ==
Expertiza is an open source project based on Ruby on Rails framework, created and maintained by the joint efforts of students and faculty at North Carolina State University.

It allows the instructors to create new assignments and customize new or existing assignments. Expertiza also allows an instructor to create a list of topics the students can sign up for. Students can form teams on the web application to work on various projects and assignments together. Additionally, students can peer review each other's submissions allowing them to improve upon their work. Expertiza supports submission across various document types, including the URLs and wiki pages.

= Introduction =

The Expertiza project allows "calibration assignments" to be performed where students are asked to review work that has also been reviewed by a member of the course staff. Calibration is the term used for rectifying, or checking or determining something. In the context of this project, a 'Calibrated review' is one which is performed by a student, so that (s)he can verify their work by comparing it with the instructor's response for the same assignment. If the student’s review “resembles” the staff-member’s review, then the student is presumed to be a competent reviewer. Since calibration reviews are meant as reference for better performance of peer reviews (which are performed later), they are not graded.

= Problem Statement =

== Project Purpose ==
Calibration submissions should be copied along with calibration assignments.

== Issue in current implementation ==
On creating a copy of a previous assignment, say for example Design Exercise, Fall '20 for the Fall '21 semester - the calibration assignments associated with it are not copied over. The instructor is required to impersonate extra participants, and submit work on behalf of each of the extra participants. This is obviously extra trouble, and it would be a lot more convenient if an instructor didn’t have to resubmit the same calibration submissions over and over, every semester. 

'''The following steps were taken to test the aforementioned issues:'''

'''Step 1:''' On copying the Design exercise assignment 
[[File:copy_2075.png]] 

'''Step 2:''' The original file contains the following calibration reviews 
[[File:cali_a_2075.png]] 

'''Step 3:''' However, the copy doesn't contain any of the calibrated reviews 
[[File:cali_b_2075.png]] 

= Implementation =
==MVC==

The project is implemented in Ruby on Rails that uses MVC architecture. We have three separate modules namely User Interface, Database Model and Control Flow(Model, View and Controller).

==Principle==

We tend to reuse the already existing functionalities and data to our design. The calibration reviews that are present in the previous exercise will be copied into the newly created exercise which would prevent the intructor to perform additional tasks of performing reviews repeatedly. This would also prevent code duplication and additional memory usage.

== Proposed Design ==
The following must be added to the current implementation:

* The same extra participants in the assignment, which are used as calibration assignments are copied over to the newly copied directory
* The URLs and/or files that were submitted to the previous assignment must be copied over as well
* Test cases to check if the above-mentioned steps work as required

[More on the design pattern if any, ER/ UML diagrams to be updated as the project progresses]

== Files Involved ==
* '''submission_records_controller.rb'''
* '''index.html.erb''' in expertiza/app/views/submission_records

==Difference between Previous Implementation and Proposed Solution ==

===Previous Implementation===

[[File:um20201.png]]

===Proposed Implementation===

[[File:um20221.png]]

== Proposed Solution ==

* Find the hyper link submitted in the submission_records table for the Original exercise. Use the link and insert it into the content attribute for the new copy over exercise when the instructor creates a duplicate
* If the submissions were in file format, then make a new copy of the file into the directory path structure and use this as the reference pointer in the table for the new copy over exercise.

= Test Plan =

=== Manual Testing Plan ===
* The UI is working as expected [No broken links]
* The submissions [Files and Hyperlinks] are copied when an assignment for calibration is copied.

=== Directions for Manual Testing ===
* Go to the testing server [VCL Instance] and log in with the credentials - username: 'instructor6'; password: 'password'
* Go to an existing assignment (say A1) that you want to setup calibration for
** Select the '''copy''' button (generates A2)
** Toggle onto the calibration tab of the original directory (A1) and check the files present inside it
** Now, select the copied directory (A2)
** On the calibrations tab, check whether the copied submissions [Files and URLs] are present.
** Expected Outcome : All the calibrated assignments in the original exercise must also be present in the new copy over exercise.

== RSpec Testing Plan ==
=== RSpec test to check ===
* Validation of the models
* Sanity and basic functionality of controllers
** This involves essentially checking if the copied calibration's corresponding model has entries for the submissions

=== Directions for RSpec Testing ===
* Run the following commands:
** For controllers: rspec spec/controllers/
** For models: rspec spec/models/

= Useful Links =
*[https://github.com/expertiza/expertiza Expertiza on GitHub]
*[http://expertiza.ncsu.edu/ The live Expertiza website]
*[http://research.csc.ncsu.edu/efg/expertiza Expertiza project Details]

= Team Information =
* Nischal Badarinath Kashyap
* Mounika Bachu
* Akshay Podila
* Dhanraj Raghunathan

File:Um20221.png

2020-10-29T03:20:50Z

Nkashya:

File:Um20201.png

2020-10-29T03:20:36Z

Nkashya:

CSC/ECE 517 Fall 2020 - E2075. calibration submissions should be copied along with calibration assignments

2020-10-29T03:20:23Z

Nkashya:

This wiki page describes the changes made under E2075, to ensure calibration submissions are copied along with calibration assignments for CSC/ECE 517, Fall 2020.

__TOC__

== About Expertiza ==
Expertiza is an open source project based on Ruby on Rails framework, created and maintained by the joint efforts of students and faculty at North Carolina State University.

It allows the instructors to create new assignments and customize new or existing assignments. Expertiza also allows an instructor to create a list of topics the students can sign up for. Students can form teams on the web application to work on various projects and assignments together. Additionally, students can peer review each other's submissions allowing them to improve upon their work. Expertiza supports submission across various document types, including the URLs and wiki pages.

= Introduction =

The Expertiza project allows "calibration assignments" to be performed where students are asked to review work that has also been reviewed by a member of the course staff. Calibration is the term used for rectifying, or checking or determining something. In the context of this project, a 'Calibrated review' is one which is performed by a student, so that (s)he can verify their work by comparing it with the instructor's response for the same assignment. If the student’s review “resembles” the staff-member’s review, then the student is presumed to be a competent reviewer. Since calibration reviews are meant as reference for better performance of peer reviews (which are performed later), they are not graded.

= Problem Statement =

== Project Purpose ==
Calibration submissions should be copied along with calibration assignments.

== Issue in current implementation ==
On creating a copy of a previous assignment, say for example Design Exercise, Fall '20 for the Fall '21 semester - the calibration assignments associated with it are not copied over. The instructor is required to impersonate extra participants, and submit work on behalf of each of the extra participants. This is obviously extra trouble, and it would be a lot more convenient if an instructor didn’t have to resubmit the same calibration submissions over and over, every semester. 

'''The following steps were taken to test the aforementioned issues:'''

'''Step 1:''' On copying the Design exercise assignment 
[[File:copy_2075.png]] 

'''Step 2:''' The original file contains the following calibration reviews 
[[File:cali_a_2075.png]] 

'''Step 3:''' However, the copy doesn't contain any of the calibrated reviews 
[[File:cali_b_2075.png]] 

= Implementation =
==MVC==

The project is implemented in Ruby on Rails that uses MVC architecture. We have three separate modules namely User Interface, Database Model and Control Flow(Model, View and Controller).

==Principle==

We tend to reuse the already existing functionalities and data to our design. The calibration reviews that are present in the previous exercise will be copied into the newly created exercise which would prevent the intructor to perform additional tasks of performing reviews repeatedly. This would also prevent code duplication and additional memory usage.

== Proposed Design ==
The following must be added to the current implementation:

* The same extra participants in the assignment, which are used as calibration assignments are copied over to the newly copied directory
* The URLs and/or files that were submitted to the previous assignment must be copied over as well
* Test cases to check if the above-mentioned steps work as required

[More on the design pattern if any, ER/ UML diagrams to be updated as the project progresses]

== Files Involved ==
* '''submission_records_controller.rb'''
* '''index.html.erb''' in expertiza/app/views/submission_records

==Difference between Previous Implementation and Proposed Solution ==

'''Previous Implementation'''

[[File:um20201.png]]

'''Proposed Implementation'''

[[File:um20221.png]]

== Proposed Solution ==

* Find the hyper link submitted in the submission_records table for the Original exercise. Use the link and insert it into the content attribute for the new copy over exercise when the instructor creates a duplicate
* If the submissions were in file format, then make a new copy of the file into the directory path structure and use this as the reference pointer in the table for the new copy over exercise.

= Test Plan =

=== Manual Testing Plan ===
* The UI is working as expected [No broken links]
* The submissions [Files and Hyperlinks] are copied when an assignment for calibration is copied.

=== Directions for Manual Testing ===
* Go to the testing server [VCL Instance] and log in with the credentials - username: 'instructor6'; password: 'password'
* Go to an existing assignment (say A1) that you want to setup calibration for
** Select the '''copy''' button (generates A2)
** Toggle onto the calibration tab of the original directory (A1) and check the files present inside it
** Now, select the copied directory (A2)
** On the calibrations tab, check whether the copied submissions [Files and URLs] are present.
** Expected Outcome : All the calibrated assignments in the original exercise must also be present in the new copy over exercise.

== RSpec Testing Plan ==
=== RSpec test to check ===
* Validation of the models
* Sanity and basic functionality of controllers
** This involves essentially checking if the copied calibration's corresponding model has entries for the submissions

=== Directions for RSpec Testing ===
* Run the following commands:
** For controllers: rspec spec/controllers/
** For models: rspec spec/models/

= Useful Links =
*[https://github.com/expertiza/expertiza Expertiza on GitHub]
*[http://expertiza.ncsu.edu/ The live Expertiza website]
*[http://research.csc.ncsu.edu/efg/expertiza Expertiza project Details]

= Team Information =
* Nischal Badarinath Kashyap
* Mounika Bachu
* Akshay Podila
* Dhanraj Raghunathan

File:Uml20201.png

2020-10-29T03:19:10Z

Nkashya:

CSC/ECE 517 Fall 2020 - E2075. calibration submissions should be copied along with calibration assignments

2020-10-29T03:15:33Z

Nkashya:

This wiki page describes the changes made under E2075, to ensure calibration submissions are copied along with calibration assignments for CSC/ECE 517, Fall 2020.

__TOC__

== About Expertiza ==
Expertiza is an open source project based on Ruby on Rails framework, created and maintained by the joint efforts of students and faculty at North Carolina State University.

It allows the instructors to create new assignments and customize new or existing assignments. Expertiza also allows an instructor to create a list of topics the students can sign up for. Students can form teams on the web application to work on various projects and assignments together. Additionally, students can peer review each other's submissions allowing them to improve upon their work. Expertiza supports submission across various document types, including the URLs and wiki pages.

= Introduction =

The Expertiza project allows "calibration assignments" to be performed where students are asked to review work that has also been reviewed by a member of the course staff. Calibration is the term used for rectifying, or checking or determining something. In the context of this project, a 'Calibrated review' is one which is performed by a student, so that (s)he can verify their work by comparing it with the instructor's response for the same assignment. If the student’s review “resembles” the staff-member’s review, then the student is presumed to be a competent reviewer. Since calibration reviews are meant as reference for better performance of peer reviews (which are performed later), they are not graded.

= Problem Statement =

== Project Purpose ==
Calibration submissions should be copied along with calibration assignments.

== Issue in current implementation ==
On creating a copy of a previous assignment, say for example Design Exercise, Fall '20 for the Fall '21 semester - the calibration assignments associated with it are not copied over. The instructor is required to impersonate extra participants, and submit work on behalf of each of the extra participants. This is obviously extra trouble, and it would be a lot more convenient if an instructor didn’t have to resubmit the same calibration submissions over and over, every semester. 

'''The following steps were taken to test the aforementioned issues:'''

'''Step 1:''' On copying the Design exercise assignment 
[[File:copy_2075.png]] 

'''Step 2:''' The original file contains the following calibration reviews 
[[File:cali_a_2075.png]] 

'''Step 3:''' However, the copy doesn't contain any of the calibrated reviews 
[[File:cali_b_2075.png]] 

= Implementation =
==MVC==

The project is implemented in Ruby on Rails that uses MVC architecture. We have three separate modules namely User Interface, Database Model and Control Flow(Model, View and Controller).

==Principle==

We tend to reuse the already existing functionalities and data to our design. The calibration reviews that are present in the previous exercise will be copied into the newly created exercise which would prevent the intructor to perform additional tasks of performing reviews repeatedly. This would also prevent code duplication and additional memory usage.

== Proposed Design ==
The following must be added to the current implementation:

* The same extra participants in the assignment, which are used as calibration assignments are copied over to the newly copied directory
* The URLs and/or files that were submitted to the previous assignment must be copied over as well
* Test cases to check if the above-mentioned steps work as required

[More on the design pattern if any, ER/ UML diagrams to be updated as the project progresses]

== Files Involved ==
* '''submission_records_controller.rb'''
* '''index.html.erb''' in expertiza/app/views/submission_records

==Difference between Previous Implementation and Proposed Solution ==

'''Previous Implementation'''

[[File:uml20201.png]]

'''Proposed Implementation'''

[[File:futimp.png]]

== Proposed Solution ==

* Find the hyper link submitted in the submission_records table for the Original exercise. Use the link and insert it into the content attribute for the new copy over exercise when the instructor creates a duplicate
* If the submissions were in file format, then make a new copy of the file into the directory path structure and use this as the reference pointer in the table for the new copy over exercise.

= Test Plan =

=== Manual Testing Plan ===
* The UI is working as expected [No broken links]
* The submissions [Files and Hyperlinks] are copied when an assignment for calibration is copied.

=== Directions for Manual Testing ===
* Go to the testing server [VCL Instance] and log in with the credentials - username: 'instructor6'; password: 'password'
* Go to an existing assignment (say A1) that you want to setup calibration for
** Select the '''copy''' button (generates A2)
** Toggle onto the calibration tab of the original directory (A1) and check the files present inside it
** Now, select the copied directory (A2)
** On the calibrations tab, check whether the copied submissions [Files and URLs] are present.
** Expected Outcome : All the calibrated assignments in the original exercise must also be present in the new copy over exercise.

== RSpec Testing Plan ==
=== RSpec test to check ===
* Validation of the models
* Sanity and basic functionality of controllers
** This involves essentially checking if the copied calibration's corresponding model has entries for the submissions

=== Directions for RSpec Testing ===
* Run the following commands:
** For controllers: rspec spec/controllers/
** For models: rspec spec/models/

= Useful Links =
*[https://github.com/expertiza/expertiza Expertiza on GitHub]
*[http://expertiza.ncsu.edu/ The live Expertiza website]
*[http://research.csc.ncsu.edu/efg/expertiza Expertiza project Details]

= Team Information =
* Nischal Badarinath Kashyap
* Mounika Bachu
* Akshay Podila
* Dhanraj Raghunathan

CSC/ECE 517 Fall 2020 - E2075. calibration submissions should be copied along with calibration assignments

2020-10-29T03:12:45Z

Nkashya:

This wiki page describes the changes made under E2075, to ensure calibration submissions are copied along with calibration assignments for CSC/ECE 517, Fall 2020.

__TOC__

== About Expertiza ==
Expertiza is an open source project based on Ruby on Rails framework, created and maintained by the joint efforts of students and faculty at North Carolina State University.

It allows the instructors to create new assignments and customize new or existing assignments. Expertiza also allows an instructor to create a list of topics the students can sign up for. Students can form teams on the web application to work on various projects and assignments together. Additionally, students can peer review each other's submissions allowing them to improve upon their work. Expertiza supports submission across various document types, including the URLs and wiki pages.

= Introduction =

The Expertiza project allows "calibration assignments" to be performed where students are asked to review work that has also been reviewed by a member of the course staff. Calibration is the term used for rectifying, or checking or determining something. In the context of this project, a 'Calibrated review' is one which is performed by a student, so that (s)he can verify their work by comparing it with the instructor's response for the same assignment. If the student’s review “resembles” the staff-member’s review, then the student is presumed to be a competent reviewer. Since calibration reviews are meant as reference for better performance of peer reviews (which are performed later), they are not graded.

= Problem Statement =

== Project Purpose ==
Calibration submissions should be copied along with calibration assignments.

== Issue in current implementation ==
On creating a copy of a previous assignment, say for example Design Exercise, Fall '20 for the Fall '21 semester - the calibration assignments associated with it are not copied over. The instructor is required to impersonate extra participants, and submit work on behalf of each of the extra participants. This is obviously extra trouble, and it would be a lot more convenient if an instructor didn’t have to resubmit the same calibration submissions over and over, every semester. 

'''The following steps were taken to test the aforementioned issues:'''

'''Step 1:''' On copying the Design exercise assignment 
[[File:copy_2075.png]] 

'''Step 2:''' The original file contains the following calibration reviews 
[[File:cali_a_2075.png]] 

'''Step 3:''' However, the copy doesn't contain any of the calibrated reviews 
[[File:cali_b_2075.png]] 

= Implementation =
==MVC==

The project is implemented in Ruby on Rails that uses MVC architecture. We have three separate modules namely User Interface, Database Model and Control Flow(Model, View and Controller).

==Principle==

We tend to reuse the already existing functionalities and data to our design. The calibration reviews that are present in the previous exercise will be copied into the newly created exercise which would prevent the intructor to perform additional tasks of performing reviews repeatedly. This would also prevent code duplication and additional memory usage.

== Proposed Design ==
The following must be added to the current implementation:

* The same extra participants in the assignment, which are used as calibration assignments are copied over to the newly copied directory
* The URLs and/or files that were submitted to the previous assignment must be copied over as well
* Test cases to check if the above-mentioned steps work as required

[More on the design pattern if any, ER/ UML diagrams to be updated as the project progresses]

== Files Involved ==
* '''submission_records_controller.rb'''
* '''index.html.erb''' in expertiza/app/views/submission_records

==Difference between Previous Implementation and Proposed Solution ==

'''Previous Implementation'''

'''Proposed Implementation'''

[[File:futimp.png]]

== Proposed Solution ==

* Find the hyper link submitted in the submission_records table for the Original exercise. Use the link and insert it into the content attribute for the new copy over exercise when the instructor creates a duplicate
* If the submissions were in file format, then make a new copy of the file into the directory path structure and use this as the reference pointer in the table for the new copy over exercise.

= Test Plan =

=== Manual Testing Plan ===
* The UI is working as expected [No broken links]
* The submissions [Files and Hyperlinks] are copied when an assignment for calibration is copied.

=== Directions for Manual Testing ===
* Go to the testing server [VCL Instance] and log in with the credentials - username: 'instructor6'; password: 'password'
* Go to an existing assignment (say A1) that you want to setup calibration for
** Select the '''copy''' button (generates A2)
** Toggle onto the calibration tab of the original directory (A1) and check the files present inside it
** Now, select the copied directory (A2)
** On the calibrations tab, check whether the copied submissions [Files and URLs] are present.
** Expected Outcome : All the calibrated assignments in the original exercise must also be present in the new copy over exercise.

== RSpec Testing Plan ==
=== RSpec test to check ===
* Validation of the models
* Sanity and basic functionality of controllers
** This involves essentially checking if the copied calibration's corresponding model has entries for the submissions

=== Directions for RSpec Testing ===
* Run the following commands:
** For controllers: rspec spec/controllers/
** For models: rspec spec/models/

= Useful Links =
*[https://github.com/expertiza/expertiza Expertiza on GitHub]
*[http://expertiza.ncsu.edu/ The live Expertiza website]
*[http://research.csc.ncsu.edu/efg/expertiza Expertiza project Details]

= Team Information =
* Nischal Badarinath Kashyap
* Mounika Bachu
* Akshay Podila
* Dhanraj Raghunathan

File:Uml2075.png

2020-10-29T03:11:26Z

Nkashya:

CSC/ECE 517 Fall 2020 - E2075. calibration submissions should be copied along with calibration assignments

2020-10-29T00:06:01Z

Nkashya:

This wiki page describes the changes made under E2075, to ensure calibration submissions are copied along with calibration assignments for CSC/ECE 517, Fall 2020.

__TOC__

== About Expertiza ==
Expertiza is an open source project based on Ruby on Rails framework, created and maintained by the joint efforts of students and faculty at North Carolina State University.

It allows the instructors to create new assignments and customize new or existing assignments. Expertiza also allows an instructor to create a list of topics the students can sign up for. Students can form teams on the web application to work on various projects and assignments together. Additionally, students can peer review each other's submissions allowing them to improve upon their work. Expertiza supports submission across various document types, including the URLs and wiki pages.

= Introduction =

The Expertiza project allows "calibration assignments" to be performed where students are asked to review work that has also been reviewed by a member of the course staff. Calibration is the term used for rectifying, or checking or determining something. In the context of this project, a 'Calibrated review' is one which is performed by a student, so that (s)he can verify their work by comparing it with the instructor's response for the same assignment. If the student’s review “resembles” the staff-member’s review, then the student is presumed to be a competent reviewer. Since calibration reviews are meant as reference for better performance of peer reviews (which are performed later), they are not graded.

= Problem Statement =

== Project Purpose ==
Calibration submissions should be copied along with calibration assignments.

== Issue in current implementation ==
On creating a copy of a previous assignment, say for example Design Exercise, Fall '20 for the Fall '21 semester - the calibration assignments associated with it are not copied over. The instructor is required to impersonate extra participants, and submit work on behalf of each of the extra participants. This is obviously extra trouble, and it would be a lot more convenient if an instructor didn’t have to resubmit the same calibration submissions over and over, every semester. 

'''The following steps were taken to test the aforementioned issues:'''

'''Step 1:''' On copying the Design exercise assignment 
[[File:copy_2075.png]] 

'''Step 2:''' The original file contains the following calibration reviews 
[[File:cali_a_2075.png]] 

'''Step 3:''' However, the copy doesn't contain any of the calibrated reviews 
[[File:cali_b_2075.png]] 

= Implementation =
==MVC==

The project is implemented in Ruby on Rails that uses MVC architecture. We have three separate modules namely User Interface, Database Model and Control Flow(Model, View and Controller).

==Principle==

We tend to reuse the already existing functionalities and data to our design. The calibration reviews that are present in the previous exercise will be copied into the newly created exercise which would prevent the intructor to perform additional tasks of performing reviews repeatedly. This would also prevent code duplication and additional memory usage.

== Proposed Design ==
The following must be added to the current implementation:

* The same extra participants in the assignment, which are used as calibration assignments are copied over to the newly copied directory
* The URLs and/or files that were submitted to the previous assignment must be copied over as well
* Test cases to check if the above-mentioned steps work as required

[More on the design pattern if any, ER/ UML diagrams to be updated as the project progresses]

== Files Involved ==
* '''submission_records_controller.rb'''
* '''index.html.erb''' in expertiza/app/views/submission_records

==Difference between Previous Implementation and Proposed Solution ==

'''Previous Implementation'''

[[File:Preimp.png]]

'''Proposed Implementation'''

[[File:futimp.png]]

== Proposed Solution ==

* Find the hyper link submitted in the submission_records table for the Original exercise. Use the link and insert it into the content attribute for the new copy over exercise when the instructor creates a duplicate
* If the submissions were in file format, then make a new copy of the file into the directory path structure and use this as the reference pointer in the table for the new copy over exercise.

= Test Plan =

=== Manual Testing Plan ===
* The UI is working as expected [No broken links]
* The submissions [Files and Hyperlinks] are copied when an assignment for calibration is copied.

=== Directions for Manual Testing ===
* Go to the testing server [VCL Instance] and log in with the credentials - username: 'instructor6'; password: 'password'
* Go to an existing assignment (say A1) that you want to setup calibration for
** Select the '''copy''' button (generates A2)
** Toggle onto the calibration tab of the original directory (A1) and check the files present inside it
** Now, select the copied directory (A2)
** On the calibrations tab, check whether the copied submissions [Files and URLs] are present.
** Expected Outcome : All the calibrated assignments in the original exercise must also be present in the new copy over exercise.

== RSpec Testing Plan ==
=== RSpec test to check ===
* Validation of the models
* Sanity and basic functionality of controllers
** This involves essentially checking if the copied calibration's corresponding model has entries for the submissions

=== Directions for RSpec Testing ===
* Run the following commands:
** For controllers: rspec spec/controllers/
** For models: rspec spec/models/

= Useful Links =
*[https://github.com/expertiza/expertiza Expertiza on GitHub]
*[http://expertiza.ncsu.edu/ The live Expertiza website]
*[http://research.csc.ncsu.edu/efg/expertiza Expertiza project Details]

= Team Information =
* Nischal Badarinath Kashyap
* Mounika Bachu
* Akshay Podila
* Dhanraj Raghunathan

CSC/ECE 517 Fall 2020 - E2075. calibration submissions should be copied along with calibration assignments

2020-10-29T00:05:22Z

Nkashya:

This wiki page describes the changes made under E2075, to ensure calibration submissions are copied along with calibration assignments for CSC/ECE 517, Fall 2020.

__TOC__

== About Expertiza ==
Expertiza is an open source project based on Ruby on Rails framework, created and maintained by the joint efforts of students and faculty at North Carolina State University.

It allows the instructors to create new assignments and customize new or existing assignments. Expertiza also allows an instructor to create a list of topics the students can sign up for. Students can form teams on the web application to work on various projects and assignments together. Additionally, students can peer review each other's submissions allowing them to improve upon their work. Expertiza supports submission across various document types, including the URLs and wiki pages.

= Introduction =

The Expertiza project allows "calibration assignments" to be performed where students are asked to review work that has also been reviewed by a member of the course staff. Calibration is the term used for rectifying, or checking or determining something. In the context of this project, a 'Calibrated review' is one which is performed by a student, so that (s)he can verify their work by comparing it with the instructor's response for the same assignment. If the student’s review “resembles” the staff-member’s review, then the student is presumed to be a competent reviewer. Since calibration reviews are meant as reference for better performance of peer reviews (which are performed later), they are not graded.

= Problem Statement =

== Project Purpose ==
Calibration submissions should be copied along with calibration assignments.

== Issue in current implementation ==
On creating a copy of a previous assignment, say for example Design Exercise, Fall '20 for the Fall '21 semester - the calibration assignments associated with it are not copied over. The instructor is required to impersonate extra participants, and submit work on behalf of each of the extra participants. This is obviously extra trouble, and it would be a lot more convenient if an instructor didn’t have to resubmit the same calibration submissions over and over, every semester. 

'''The following steps were taken to test the aforementioned issues:'''

'''Step 1:''' On copying the Design exercise assignment 
[[File:copy_2075.png]] 

'''Step 2:''' The original file contains the following calibration reviews 
[[File:cali_a_2075.png]] 

'''Step 3:''' However, the copy doesn't contain any of the calibrated reviews 
[[File:cali_b_2075.png]] 

= Implementation =
==MVC==

The project is implemented in Ruby on Rails that uses MVC architecture. We have three separate modules namely User Interface, Database Model and Control Flow(Model, View and Controller).

==Principle==

We tend to reuse the already existing functionalities and data to our design. The calibration reviews that are present in the previous exercise will be copied into the newly created exercise which would prevent the intructor to perform additional tasks of performing reviews repeatedly. This would also prevent code duplication and additional memory usage.

== Proposed Design ==
The following must be added to the current implementation:

* The same extra participants in the assignment, which are used as calibration assignments are copied over to the newly copied directory
* The URLs and/or files that were submitted to the previous assignment must be copied over as well
* Test cases to check if the above-mentioned steps work as required

[More on the design pattern if any, ER/ UML diagrams to be updated as the project progresses]

== Files Involved ==
* '''submission_records_controller.rb'''
* '''index.html.erb''' in expertiza/app/views/submission_records

==Difference between Previous Implementation and Proposed Solution ==

'''Previous Implementation'''

[[File:Preimp.png]]

'''Proposed Implementation'''

[[File:futimp.png]]

== Proposed Solution ==

* Find the hyper link submitted in the submission_records table for the Original exercise. Use the link and insert it into the content attribute for the new copy over exercise when the instructor creates a duplicate
* If the submissions were in file format, then make a new copy of the file into the directory path structure and use this as the reference pointer in the table for the new copy over exercise.

= Test Plan =

=== Manual Testing Plan ===
* The UI is working as expected [No broken links]
* The submissions [Files and Hyperlinks] are copied when an assignment for calibration is copied.

=== Directions for Manual Testing ===
* Go to the testing server [VCL Instance] and log in with the credentials - username: 'instructor6'; password: 'password'
* Go to an existing assignment (say A1) that you want to setup calibration for
** Select the '''copy''' button (generates A2)
** Toggle onto the calibration tab of the original directory (A1) and check the files present inside it
** Now, select the copied directory (A2)
** On the calibrations tab, check whether the copied submissions [Files and URLs] are present.
** Expected Outcome : All the calibrated assignments in the original exercise must also be present in the new copy over exercise.

== RSpec Testing Plan ==
RSpec test to check:
* Validation of the models
* Sanity and basic functionality of controllers
** This involves essentially checking if the copied calibration's corresponding model has entries for the submissions

=== Directions for RSpec Testing ===
* Run the following commands:
** For controllers: rspec spec/controllers/
** For models: rspec spec/models/

= Useful Links =
*[https://github.com/expertiza/expertiza Expertiza on GitHub]
*[http://expertiza.ncsu.edu/ The live Expertiza website]
*[http://research.csc.ncsu.edu/efg/expertiza Expertiza project Details]

= Team Information =
* Nischal Badarinath Kashyap
* Mounika Bachu
* Akshay Podila
* Dhanraj Raghunathan

CSC/ECE 517 Fall 2020 - E2075. calibration submissions should be copied along with calibration assignments

2020-10-29T00:03:30Z

Nkashya:

This wiki page describes the changes made under E2075, to ensure calibration submissions are copied along with calibration assignments for CSC/ECE 517, Fall 2020.

__TOC__

== About Expertiza ==
Expertiza is an open source project based on Ruby on Rails framework, created and maintained by the joint efforts of students and faculty at North Carolina State University.

It allows the instructors to create new assignments and customize new or existing assignments. Expertiza also allows an instructor to create a list of topics the students can sign up for. Students can form teams on the web application to work on various projects and assignments together. Additionally, students can peer review each other's submissions allowing them to improve upon their work. Expertiza supports submission across various document types, including the URLs and wiki pages.

= Introduction =

The Expertiza project allows "calibration assignments" to be performed where students are asked to review work that has also been reviewed by a member of the course staff. Calibration is the term used for rectifying, or checking or determining something. In the context of this project, a 'Calibrated review' is one which is performed by a student, so that (s)he can verify their work by comparing it with the instructor's response for the same assignment. If the student’s review “resembles” the staff-member’s review, then the student is presumed to be a competent reviewer. Since calibration reviews are meant as reference for better performance of peer reviews (which are performed later), they are not graded.

= Problem Statement =

== Project Purpose ==
Calibration submissions should be copied along with calibration assignments.

== Issue in current implementation ==
On creating a copy of a previous assignment, say for example Design Exercise, Fall '20 for the Fall '21 semester - the calibration assignments associated with it are not copied over. The instructor is required to impersonate extra participants, and submit work on behalf of each of the extra participants. This is obviously extra trouble, and it would be a lot more convenient if an instructor didn’t have to resubmit the same calibration submissions over and over, every semester. 

'''The following steps were taken to test the aforementioned issues:'''

'''Step 1:''' On copying the Design exercise assignment 
[[File:copy_2075.png]] 

'''Step 2:''' The original file contains the following calibration reviews 
[[File:cali_a_2075.png]] 

'''Step 3:''' However, the copy doesn't contain any of the calibrated reviews 
[[File:cali_b_2075.png]] 

= Implementation =
==MVC==

The project is implemented in Ruby on Rails that uses MVC architecture. We have three separate modules namely User Interface, Database Model and Control Flow(Model, View and Controller).

==Principle==

We tend to reuse the already existing functionalities and data to our design. The calibration reviews that are present in the previous exercise will be copied into the newly created exercise which would prevent the intructor to perform additional tasks of performing reviews repeatedly. This would also prevent code duplication and additional memory usage.

== Proposed Design ==
The following must be added to the current implementation:

* The same extra participants in the assignment, which are used as calibration assignments are copied over to the newly copied directory
* The URLs and/or files that were submitted to the previous assignment must be copied over as well
* Test cases to check if the above-mentioned steps work as required

[More on the design pattern if any, ER/ UML diagrams to be updated as the project progresses]

== Files Involved ==
* '''submission_records_controller.rb'''
* '''index.html.erb''' in expertiza/app/views/submission_records

==Difference between Previous Implementation and Proposed Solution ==

'''Previous Implementation'''

[[File:Preimp.png]]

'''Proposed Implementation'''

[[File:futimp.png]]

== Proposed Solution ==

* Find the hyper link submitted in the submission_records table for the Original exercise. Use the link and insert it into the content attribute for the new copy over exercise when the instructor creates a duplicate
* If the submissions were in file format, then make a new copy of the file into the directory path structure and use this as the reference pointer in the table for the new copy over exercise.

= Test Plan =

=== Manual Testing Plan ===
Manual test to check if:
* The UI is working as expected [No broken links]
* The submissions [Files and Hyperlinks] are copied when an assignment for calibration is copied.

=== Directions for Manual Testing ===
* Go to the testing server [VCL Instance] and log in with the credentials - username: 'instructor6'; password: 'password'
* Go to an existing assignment (say A1) that you want to setup calibration for
** Select the '''copy''' button (generates A2)
** Toggle onto the calibration tab of the original directory (A1) and check the files present inside it
** Now, select the copied directory (A2)
** On the calibrations tab, check whether the copied submissions [Files and URLs] are present.
** Expected Outcome : All the calibrated assignments in the original exercise must also be present in the new copy over exercise.

== RSpec Testing Plan ==
RSpec test to check:
* Validation of the models
* Sanity and basic functionality of controllers
** This involves essentially checking if the copied calibration's corresponding model has entries for the submissions

=== Directions for RSpec Testing ===
* Run the following commands:
** For controllers: rspec spec/controllers/
** For models: rspec spec/models/

= Useful Links =
*[https://github.com/expertiza/expertiza Expertiza on GitHub]
*[http://expertiza.ncsu.edu/ The live Expertiza website]
*[http://research.csc.ncsu.edu/efg/expertiza Expertiza project Details]

= Team Information =
* Nischal Badarinath Kashyap
* Mounika Bachu
* Akshay Podila
* Dhanraj Raghunathan

CSC/ECE 517 Fall 2020 - E2075. calibration submissions should be copied along with calibration assignments

2020-10-29T00:02:43Z

Nkashya:

This wiki page describes the changes made under E2075, to ensure calibration submissions are copied along with calibration assignments for CSC/ECE 517, Fall 2020.

__TOC__

== About Expertiza ==
Expertiza is an open source project based on Ruby on Rails framework, created and maintained by the joint efforts of students and faculty at North Carolina State University.

It allows the instructors to create new assignments and customize new or existing assignments. Expertiza also allows an instructor to create a list of topics the students can sign up for. Students can form teams on the web application to work on various projects and assignments together. Additionally, students can peer review each other's submissions allowing them to improve upon their work. Expertiza supports submission across various document types, including the URLs and wiki pages.

= Introduction =

The Expertiza project allows "calibration assignments" to be performed where students are asked to review work that has also been reviewed by a member of the course staff. Calibration is the term used for rectifying, or checking or determining something. In the context of this project, a 'Calibrated review' is one which is performed by a student, so that (s)he can verify their work by comparing it with the instructor's response for the same assignment. If the student’s review “resembles” the staff-member’s review, then the student is presumed to be a competent reviewer. Since calibration reviews are meant as reference for better performance of peer reviews (which are performed later), they are not graded.

= Problem Statement =

== Project Purpose ==
Calibration submissions should be copied along with calibration assignments.

== Issue in current implementation ==
On creating a copy of a previous assignment, say for example Design Exercise, Fall '20 for the Fall '21 semester - the calibration assignments associated with it are not copied over. The instructor is required to impersonate extra participants, and submit work on behalf of each of the extra participants. This is obviously extra trouble, and it would be a lot more convenient if an instructor didn’t have to resubmit the same calibration submissions over and over, every semester. 

'''The following steps were taken to test the aforementioned issues:'''

'''Step 1:''' On copying the Design exercise assignment 
[[File:copy_2075.png]] 

'''Step 2:''' The original file contains the following calibration reviews 
[[File:cali_a_2075.png]] 

'''Step 3:''' However, the copy doesn't contain any of the calibrated reviews 
[[File:cali_b_2075.png]] 

= Implementation =
==MVC==

The project is implemented in Ruby on Rails that uses MVC architecture. We have three separate modules namely User Interface, Database Model and Control Flow(Model, View and Controller).

==Principle==

We tend to reuse the already existing functionalities and data to our design. The calibration reviews that are present in the previous exercise will be copied into the newly created exercise which would prevent the intructor to perform additional tasks of performing reviews repeatedly. This would also prevent code duplication and additional memory usage.

== Proposed Design ==
The following must be added to the current implementation:

* The same extra participants in the assignment, which are used as calibration assignments are copied over to the newly copied directory
* The URLs and/or files that were submitted to the previous assignment must be copied over as well
* Test cases to check if the above-mentioned steps work as required

[More on the design pattern if any, ER/ UML diagrams to be updated as the project progresses]

== Files Involved ==
* '''submission_records_controller.rb'''
* '''index.html.erb''' in expertiza/app/views/submission_records

==Difference between Previous Implementation and Proposed Solution ==

'''Previous Implementation'''

[[File:Preimp.png]]

'''Proposed Implementation'''

[[File:futimp.png]]

== Proposed Solution ==

* Find the hyper link submitted in the submission_records table for the Original exercise. Use the link and insert it into the content attribute for the new copy over exercise when the instructor creates a duplicate
* If the submissions were in file format, then make a new copy of the file into the directory path structure and use this as the reference pointer in the table for the new copy over exercise.

= Test Plan =

== Manual Testing Plan ==
Manual test to check if:
* The UI is working as expected [No broken links]
* The submissions [Files and Hyperlinks] are copied when an assignment for calibration is copied.

=== Directions for Manual Testing ===
* Go to the testing server [VCL Instance] and log in with the credentials - username: 'instructor6'; password: 'password'
* Go to an existing assignment (say A1) that you want to setup calibration for
** Select the '''copy''' button (generates A2)
** Toggle onto the calibration tab of the original directory (A1) and check the files present inside it
** Now, select the copied directory (A2)
** On the calibrations tab, check whether the copied submissions [Files and URLs] are present.
** Expected Outcome : All the calibrated assignments in the original exercise must also be present in the new copy over exercise.

== RSpec Testing Plan ==
RSpec test to check:
* Validation of the models
* Sanity and basic functionality of controllers
** This involves essentially checking if the copied calibration's corresponding model has entries for the submissions

=== Directions for RSpec Testing ===
* Run the following commands:
** For controllers: rspec spec/controllers/
** For models: rspec spec/models/

= Useful Links =
*[https://github.com/expertiza/expertiza Expertiza on GitHub]
*[http://expertiza.ncsu.edu/ The live Expertiza website]
*[http://research.csc.ncsu.edu/efg/expertiza Expertiza project Details]

= Team Information =
* Nischal Badarinath Kashyap
* Mounika Bachu
* Akshay Podila
* Dhanraj Raghunathan

CSC/ECE 517 Fall 2020 - E2075. calibration submissions should be copied along with calibration assignments

2020-10-28T21:30:41Z

Nkashya:

This wiki page describes the changes made under E2075, to ensure calibration submissions are copied along with calibration assignments for CSC/ECE 517, Fall 2020.

__TOC__

== About Expertiza ==
Expertiza is an open source project based on Ruby on Rails framework, created and maintained by the joint efforts of students and faculty at North Carolina State University.

It allows the instructors to create new assignments and customize new or existing assignments. Expertiza also allows an instructor to create a list of topics the students can sign up for. Students can form teams on the web application to work on various projects and assignments together. Additionally, students can peer review each other's submissions allowing them to improve upon their work. Expertiza supports submission across various document types, including the URLs and wiki pages.

= Introduction =

The Expertiza project allows "calibration assignments" to be performed where students are asked to review work that has also been reviewed by a member of the course staff. Calibration is the term used for rectifying, or checking or determining something. In the context of this project, a 'Calibrated review' is one which is performed by a student, so that (s)he can verify their work by comparing it with the instructor's response for the same assignment. If the student’s review “resembles” the staff-member’s review, then the student is presumed to be a competent reviewer. Since calibration reviews are meant as reference for better performance of peer reviews (which are performed later), they are not graded.

= Problem Statement =

== Project Purpose ==
Calibration submissions should be copied along with calibration assignments.

== Issue in current implementation ==
On creating a copy of a previous assignment, say for example Design Exercise, Fall '20 for the Fall '21 semester - the calibration assignments associated with it are not copied over. The instructor is required to impersonate extra participants, and submit work on behalf of each of the extra participants. This is obviously extra trouble, and it would be a lot more convenient if an instructor didn’t have to resubmit the same calibration submissions over and over, every semester. 

'''The following steps were taken to test the aforementioned issues:'''

'''Step 1:''' On copying the Design exercise assignment 
[[File:copy_2075.png]] 

'''Step 2:''' The original file contains the following calibration reviews 
[[File:cali_a_2075.png]] 

'''Step 3:''' However, the copy doesn't contain any of the calibrated reviews 
[[File:cali_b_2075.png]] 

= Implementation =
==MVC==

The project is implemented in Ruby on Rails that uses MVC architecture. We have three separate modules namely User Interface, Database Model and Control Flow(Model, View and Controller).

==Principle==

We tend to reuse the already existing functionalities and data to our design. The calibration reviews that are present in the previous exercise will be copied into the newly created exercise which would prevent the intructor to perform additional tasks of performing reviews repeatedly. This would also prevent code duplication and additional memory usage.

== Proposed Design ==
The following must be added to the current implementation:

* The same extra participants in the assignment, which are used as calibration assignments are copied over to the newly copied directory
* The URLs and/or files that were submitted to the previous assignment must be copied over as well
* Test cases to check if the above-mentioned steps work as required

[More on the design pattern if any, ER/ UML diagrams to be updated as the project progresses]

== Files Involved ==
* '''submission_records_controller.rb'''
* '''index.html.erb''' in expertiza/app/views/submission_records

==Difference between Previous Implementation and Proposed Solution ==

'''Previous Implementation'''

[[File:Preimp.png]]

'''Proposed Implementation'''

[[File:futimp.png]]

== Proposed Solution ==

* In the entire database check for tables which store the URL of the submitted student's work. The table which stores it is Submissions_Records
* The URL from this table should be copied and updated to the database table which stores calibration results.

= Test Plan =

== Manual Testing Plan ==
Manual test to check if:
* The UI is working as expected [No broken links]
* The submissions [Files and Hyperlinks] are copied when an assignment for calibration is copied.

=== Directions for Manual Testing ===
* Go to the testing server [VCL Instance] and log in with the credentials - username: 'instructor6'; password: 'password'
* Go to an existing assignment (say A1) that you want to setup calibration for
** Select the '''copy''' button (generates A2)
** Toggle onto the calibration tab of the original directory (A1) and check the files present inside it
** Now, select the copied directory (A2)
** On the calibrations tab, check whether the copied submissions [Files and URLs] are present.

== RSpec Testing Plan ==
RSpec test to check:
* Validation of the models
* Sanity and basic functionality of controllers
** This involves essentially checking if the copied calibration's corresponding model has entries for the submissions

=== Directions for RSpec Testing ===
* Run the following commands:
** For controllers: rspec spec/controllers/
** For models: rspec spec/models/

= Useful Links =
*[https://github.com/expertiza/expertiza Expertiza on GitHub]
*[http://expertiza.ncsu.edu/ The live Expertiza website]
*[http://research.csc.ncsu.edu/efg/expertiza Expertiza project Details]

= Team Information =
* Nischal Kashyap
* Mounika Bachu
* Akshay Podila
* Dhanraj Raghunathan

File:Futimp.png

2020-10-28T08:38:16Z

Nkashya:

CSC/ECE 517 Fall 2020 - E2075. calibration submissions should be copied along with calibration assignments

2020-10-28T08:38:01Z

Nkashya:

This wiki page describes the changes made under E2075, to ensure calibration submissions are copied along with calibration assignments for CSC/ECE 517, Fall 2020.

__TOC__

== About Expertiza ==
Expertiza is an open source project based on Ruby on Rails framework, created and maintained by the joint efforts of students and faculty at North Carolina State University.

It allows the instructors to create new assignments and customize new or existing assignments. Expertiza also allows an instructor to create a list of topics the students can sign up for. Students can form teams on the web application to work on various projects and assignments together. Additionally, students can peer review each other's submissions allowing them to improve upon their work. Expertiza supports submission across various document types, including the URLs and wiki pages.

= Introduction =

The Expertiza project allows "calibration assignments" to be performed where students are asked to review work that has also been reviewed by a member of the course staff. Calibration is the term used for rectifying, or checking or determining something. In the context of this project, a 'Calibrated review' is one which is performed by a student, so that (s)he can verify their work by comparing it with the instructor's response for the same assignment. If the student’s review “resembles” the staff-member’s review, then the student is presumed to be a competent reviewer. Since calibration reviews are meant as reference for better performance of peer reviews (which are performed later), they are not graded.

= Problem Statement =

== Project Purpose ==
Calibration submissions should be copied along with calibration assignments.

== Issue in current implementation ==
On creating a copy of a previous assignment, say for example Design Exercise, Fall '20 for the Fall '21 semester - the calibration assignments associated with it are not copied over. The instructor is required to impersonate extra participants, and submit work on behalf of each of the extra participants. This is obviously extra trouble, and it would be a lot more convenient if an instructor didn’t have to resubmit the same calibration submissions over and over, every semester. 

'''The following steps were taken to test the aforementioned issues:'''

'''Step 1:''' On copying the Design exercise assignment 
[[File:copy_2075.png]] 

'''Step 2:''' The original file contains the following calibration reviews 
[[File:cali_a_2075.png]] 

'''Step 3:''' However, the copy doesn't contain any of the calibrated reviews 
[[File:cali_b_2075.png]] 

==Difference between Previous Implementation and this Project's Implementation ==
Previous Implementation
[[File:Preimp.png]]

This project's Implementation
[[File:futimp.png]]

= Implementation =
==MVC==

The project is implemented in Ruby on Rails that uses MVC architecture. We have three separate modules namely User Interface, Database Model and Control Flow(Model, View and Controller).

==Principle==

We tend to reuse the already existing functionalities and data to our design. The calibration reviews that are present in the previous exercise will be copied into the newly created exercise which would prevent the intructor to perform additional tasks of performing reviews repeatedly. This would also prevent code duplication and additional memory usage.

== Proposed Design ==
The following must be added to the current implementation:

* The same extra participants in the assignment, which are used as calibration assignments are copied over to the newly copied directory
* The URLs and/or files that were submitted to the previous assignment must be copied over as well
* Test cases to check if the above-mentioned steps work as required

[More on the design pattern if any, ER/ UML diagrams to be updated as the project progresses]

== Files Involved ==
* '''submission_records_controller.rb'''
* '''index.html.erb''' in expertiza/app/views/submission_records

= Test Plan =

== Manual Testing Plan ==
Manual test to check if:
* The UI is working as expected [No broken links]
* The submissions [Files and Hyperlinks] are copied when an assignment for calibration is copied.

=== Directions for Manual Testing ===
* Go to the testing server [VCL Instance] and log in with the credentials - username: 'instructor6'; password: 'password'
* Go to an existing assignment (say A1) that you want to setup calibration for
** Select the '''copy''' button (generates A2)
** Toggle onto the calibration tab of the original directory (A1) and check the files present inside it
** Now, select the copied directory (A2)
** On the calibrations tab, check whether the copied submissions [Files and URLs] are present.

== RSpec Testing Plan ==
RSpec test to check:
* Validation of the models
* Sanity and basic functionality of controllers
** This involves essentially checking if the copied calibration's corresponding model has entries for the submissions

=== Directions for RSpec Testing ===
* Run the following commands:
** For controllers: rspec spec/controllers/
** For models: rspec spec/models/

= Useful Links =
*[https://github.com/expertiza/expertiza Expertiza on GitHub]
*[http://expertiza.ncsu.edu/ The live Expertiza website]
*[http://research.csc.ncsu.edu/efg/expertiza Expertiza project Details]

= Team Information =
* Nischal Kashyap
* Mounika Bachu
* Akshay Podila
* Dhanraj Raghunathan

File:Preimp.png

2020-10-28T08:32:47Z

Nkashya:

CSC/ECE 517 Fall 2020 - E2075. calibration submissions should be copied along with calibration assignments

2020-10-28T08:32:34Z

Nkashya:

This wiki page describes the changes made under E2075, to ensure calibration submissions are copied along with calibration assignments for CSC/ECE 517, Fall 2020.

__TOC__

== About Expertiza ==
Expertiza is an open source project based on Ruby on Rails framework, created and maintained by the joint efforts of students and faculty at North Carolina State University.

It allows the instructors to create new assignments and customize new or existing assignments. Expertiza also allows an instructor to create a list of topics the students can sign up for. Students can form teams on the web application to work on various projects and assignments together. Additionally, students can peer review each other's submissions allowing them to improve upon their work. Expertiza supports submission across various document types, including the URLs and wiki pages.

= Introduction =

The Expertiza project allows "calibration assignments" to be performed where students are asked to review work that has also been reviewed by a member of the course staff. Calibration is the term used for rectifying, or checking or determining something. In the context of this project, a 'Calibrated review' is one which is performed by a student, so that (s)he can verify their work by comparing it with the instructor's response for the same assignment. If the student’s review “resembles” the staff-member’s review, then the student is presumed to be a competent reviewer. Since calibration reviews are meant as reference for better performance of peer reviews (which are performed later), they are not graded.

= Problem Statement =

== Project Purpose ==
Calibration submissions should be copied along with calibration assignments.

== Issue in current implementation ==
On creating a copy of a previous assignment, say for example Design Exercise, Fall '20 for the Fall '21 semester - the calibration assignments associated with it are not copied over. The instructor is required to impersonate extra participants, and submit work on behalf of each of the extra participants. This is obviously extra trouble, and it would be a lot more convenient if an instructor didn’t have to resubmit the same calibration submissions over and over, every semester. 

'''The following steps were taken to test the aforementioned issues:'''

'''Step 1:''' On copying the Design exercise assignment 
[[File:copy_2075.png]] 

'''Step 2:''' The original file contains the following calibration reviews 
[[File:cali_a_2075.png]] 

'''Step 3:''' However, the copy doesn't contain any of the calibrated reviews 
[[File:cali_b_2075.png]] 

==Difference between Previous Implementation and our desired plan ==
Previous Implementation
[[File:Preimp.png]]

= Implementation =
==MVC==

The project is implemented in Ruby on Rails that uses MVC architecture. We have three separate modules namely User Interface, Database Model and Control Flow(Model, View and Controller).

==Principle==

We tend to reuse the already existing functionalities and data to our design. The calibration reviews that are present in the previous exercise will be copied into the newly created exercise which would prevent the intructor to perform additional tasks of performing reviews repeatedly. This would also prevent code duplication and additional memory usage.

== Proposed Design ==
The following must be added to the current implementation:

* The same extra participants in the assignment, which are used as calibration assignments are copied over to the newly copied directory
* The URLs and/or files that were submitted to the previous assignment must be copied over as well
* Test cases to check if the above-mentioned steps work as required

[More on the design pattern if any, ER/ UML diagrams to be updated as the project progresses]

== Files Involved ==
* '''submission_records_controller.rb'''
* '''index.html.erb''' in expertiza/app/views/submission_records

= Test Plan =

== Manual Testing Plan ==
Manual test to check if:
* The UI is working as expected [No broken links]
* The submissions [Files and Hyperlinks] are copied when an assignment for calibration is copied.

=== Directions for Manual Testing ===
* Go to the testing server [VCL Instance] and log in with the credentials - username: 'instructor6'; password: 'password'
* Go to an existing assignment (say A1) that you want to setup calibration for
** Select the '''copy''' button (generates A2)
** Toggle onto the calibration tab of the original directory (A1) and check the files present inside it
** Now, select the copied directory (A2)
** On the calibrations tab, check whether the copied submissions [Files and URLs] are present.

== RSpec Testing Plan ==
RSpec test to check:
* Validation of the models
* Sanity and basic functionality of controllers
** This involves essentially checking if the copied calibration's corresponding model has entries for the submissions

=== Directions for RSpec Testing ===
* Run the following commands:
** For controllers: rspec spec/controllers/
** For models: rspec spec/models/

= Useful Links =
*[https://github.com/expertiza/expertiza Expertiza on GitHub]
*[http://expertiza.ncsu.edu/ The live Expertiza website]
*[http://research.csc.ncsu.edu/efg/expertiza Expertiza project Details]

= Team Information =
* Nischal Kashyap
* Mounika Bachu
* Akshay Podila
* Dhanraj Raghunathan

File:Previmp.png

2020-10-28T08:26:30Z

Nkashya:

CSC/ECE 517 Fall 2020 - E2075. calibration submissions should be copied along with calibration assignments

2020-10-28T08:26:16Z

Nkashya:

This wiki page describes the changes made under E2075, to ensure calibration submissions are copied along with calibration assignments for CSC/ECE 517, Fall 2020.

__TOC__

== About Expertiza ==
Expertiza is an open source project based on Ruby on Rails framework, created and maintained by the joint efforts of students and faculty at North Carolina State University.

It allows the instructors to create new assignments and customize new or existing assignments. Expertiza also allows an instructor to create a list of topics the students can sign up for. Students can form teams on the web application to work on various projects and assignments together. Additionally, students can peer review each other's submissions allowing them to improve upon their work. Expertiza supports submission across various document types, including the URLs and wiki pages.

= Introduction =

The Expertiza project allows "calibration assignments" to be performed where students are asked to review work that has also been reviewed by a member of the course staff. Calibration is the term used for rectifying, or checking or determining something. In the context of this project, a 'Calibrated review' is one which is performed by a student, so that (s)he can verify their work by comparing it with the instructor's response for the same assignment. If the student’s review “resembles” the staff-member’s review, then the student is presumed to be a competent reviewer. Since calibration reviews are meant as reference for better performance of peer reviews (which are performed later), they are not graded.

= Problem Statement =

== Project Purpose ==
Calibration submissions should be copied along with calibration assignments.

== Issue in current implementation ==
On creating a copy of a previous assignment, say for example Design Exercise, Fall '20 for the Fall '21 semester - the calibration assignments associated with it are not copied over. The instructor is required to impersonate extra participants, and submit work on behalf of each of the extra participants. This is obviously extra trouble, and it would be a lot more convenient if an instructor didn’t have to resubmit the same calibration submissions over and over, every semester. 

'''The following steps were taken to test the aforementioned issues:'''

'''Step 1:''' On copying the Design exercise assignment 
[[File:copy_2075.png]] 

'''Step 2:''' The original file contains the following calibration reviews 
[[File:cali_a_2075.png]] 

'''Step 3:''' However, the copy doesn't contain any of the calibrated reviews 
[[File:cali_b_2075.png]] 

==Difference between Previous Implementation and our desired plan ==
Previous Implementation
[[File:Previmp.png]]

= Implementation =
==MVC==

The project is implemented in Ruby on Rails that uses MVC architecture. We have three separate modules namely User Interface, Database Model and Control Flow(Model, View and Controller).

==Principle==

We tend to reuse the already existing functionalities and data to our design. The calibration reviews that are present in the previous exercise will be copied into the newly created exercise which would prevent the intructor to perform additional tasks of performing reviews repeatedly. This would also prevent code duplication and additional memory usage.

== Proposed Design ==
The following must be added to the current implementation:

* The same extra participants in the assignment, which are used as calibration assignments are copied over to the newly copied directory
* The URLs and/or files that were submitted to the previous assignment must be copied over as well
* Test cases to check if the above-mentioned steps work as required

[More on the design pattern if any, ER/ UML diagrams to be updated as the project progresses]

== Files Involved ==
* '''submission_records_controller.rb'''
* '''index.html.erb''' in expertiza/app/views/submission_records

= Test Plan =

== Manual Testing Plan ==
Manual test to check if:
* The UI is working as expected [No broken links]
* The submissions [Files and Hyperlinks] are copied when an assignment for calibration is copied.

=== Directions for Manual Testing ===
* Go to the testing server [VCL Instance] and log in with the credentials - username: 'instructor6'; password: 'password'
* Go to an existing assignment (say A1) that you want to setup calibration for
** Select the '''copy''' button (generates A2)
** Toggle onto the calibration tab of the original directory (A1) and check the files present inside it
** Now, select the copied directory (A2)
** On the calibrations tab, check whether the copied submissions [Files and URLs] are present.

== RSpec Testing Plan ==
RSpec test to check:
* Validation of the models
* Sanity and basic functionality of controllers
** This involves essentially checking if the copied calibration's corresponding model has entries for the submissions

=== Directions for RSpec Testing ===
* Run the following commands:
** For controllers: rspec spec/controllers/
** For models: rspec spec/models/

= Useful Links =
*[https://github.com/expertiza/expertiza Expertiza on GitHub]
*[http://expertiza.ncsu.edu/ The live Expertiza website]
*[http://research.csc.ncsu.edu/efg/expertiza Expertiza project Details]

= Team Information =
* Nischal Kashyap
* Mounika Bachu
* Akshay Podila
* Dhanraj Raghunathan

File:Pic1.png

2020-10-28T08:25:39Z

Nkashya: Nkashya uploaded a new version of File:Pic1.png

CSC/ECE 517 Fall 2020 - E2075. calibration submissions should be copied along with calibration assignments

2020-10-28T08:25:06Z

Nkashya:

This wiki page describes the changes made under E2075, to ensure calibration submissions are copied along with calibration assignments for CSC/ECE 517, Fall 2020.

__TOC__

== About Expertiza ==
Expertiza is an open source project based on Ruby on Rails framework, created and maintained by the joint efforts of students and faculty at North Carolina State University.

It allows the instructors to create new assignments and customize new or existing assignments. Expertiza also allows an instructor to create a list of topics the students can sign up for. Students can form teams on the web application to work on various projects and assignments together. Additionally, students can peer review each other's submissions allowing them to improve upon their work. Expertiza supports submission across various document types, including the URLs and wiki pages.

= Introduction =

The Expertiza project allows "calibration assignments" to be performed where students are asked to review work that has also been reviewed by a member of the course staff. Calibration is the term used for rectifying, or checking or determining something. In the context of this project, a 'Calibrated review' is one which is performed by a student, so that (s)he can verify their work by comparing it with the instructor's response for the same assignment. If the student’s review “resembles” the staff-member’s review, then the student is presumed to be a competent reviewer. Since calibration reviews are meant as reference for better performance of peer reviews (which are performed later), they are not graded.

= Problem Statement =

== Project Purpose ==
Calibration submissions should be copied along with calibration assignments.

== Issue in current implementation ==
On creating a copy of a previous assignment, say for example Design Exercise, Fall '20 for the Fall '21 semester - the calibration assignments associated with it are not copied over. The instructor is required to impersonate extra participants, and submit work on behalf of each of the extra participants. This is obviously extra trouble, and it would be a lot more convenient if an instructor didn’t have to resubmit the same calibration submissions over and over, every semester. 

'''The following steps were taken to test the aforementioned issues:'''

'''Step 1:''' On copying the Design exercise assignment 
[[File:copy_2075.png]] 

'''Step 2:''' The original file contains the following calibration reviews 
[[File:cali_a_2075.png]] 

'''Step 3:''' However, the copy doesn't contain any of the calibrated reviews 
[[File:cali_b_2075.png]] 

==Difference between Previous Implementation and our desired plan ==
Previous Implementation
[[File:Pic1.png]]

= Implementation =
==MVC==

The project is implemented in Ruby on Rails that uses MVC architecture. We have three separate modules namely User Interface, Database Model and Control Flow(Model, View and Controller).

==Principle==

We tend to reuse the already existing functionalities and data to our design. The calibration reviews that are present in the previous exercise will be copied into the newly created exercise which would prevent the intructor to perform additional tasks of performing reviews repeatedly. This would also prevent code duplication and additional memory usage.

== Proposed Design ==
The following must be added to the current implementation:

* The same extra participants in the assignment, which are used as calibration assignments are copied over to the newly copied directory
* The URLs and/or files that were submitted to the previous assignment must be copied over as well
* Test cases to check if the above-mentioned steps work as required

[More on the design pattern if any, ER/ UML diagrams to be updated as the project progresses]

== Files Involved ==
* '''submission_records_controller.rb'''
* '''index.html.erb''' in expertiza/app/views/submission_records

= Test Plan =

== Manual Testing Plan ==
Manual test to check if:
* The UI is working as expected [No broken links]
* The submissions [Files and Hyperlinks] are copied when an assignment for calibration is copied.

=== Directions for Manual Testing ===
* Go to the testing server [VCL Instance] and log in with the credentials - username: 'instructor6'; password: 'password'
* Go to an existing assignment (say A1) that you want to setup calibration for
** Select the '''copy''' button (generates A2)
** Toggle onto the calibration tab of the original directory (A1) and check the files present inside it
** Now, select the copied directory (A2)
** On the calibrations tab, check whether the copied submissions [Files and URLs] are present.

== RSpec Testing Plan ==
RSpec test to check:
* Validation of the models
* Sanity and basic functionality of controllers
** This involves essentially checking if the copied calibration's corresponding model has entries for the submissions

=== Directions for RSpec Testing ===
* Run the following commands:
** For controllers: rspec spec/controllers/
** For models: rspec spec/models/

= Useful Links =
*[https://github.com/expertiza/expertiza Expertiza on GitHub]
*[http://expertiza.ncsu.edu/ The live Expertiza website]
*[http://research.csc.ncsu.edu/efg/expertiza Expertiza project Details]

= Team Information =
* Nischal Kashyap
* Mounika Bachu
* Akshay Podila
* Dhanraj Raghunathan

CSC/ECE 517 Fall 2020 - E2075. calibration submissions should be copied along with calibration assignments

2020-10-28T08:23:07Z

Nkashya:

This wiki page describes the changes made under E2075, to ensure calibration submissions are copied along with calibration assignments for CSC/ECE 517, Fall 2020.

__TOC__

== About Expertiza ==
Expertiza is an open source project based on Ruby on Rails framework, created and maintained by the joint efforts of students and faculty at North Carolina State University.

It allows the instructors to create new assignments and customize new or existing assignments. Expertiza also allows an instructor to create a list of topics the students can sign up for. Students can form teams on the web application to work on various projects and assignments together. Additionally, students can peer review each other's submissions allowing them to improve upon their work. Expertiza supports submission across various document types, including the URLs and wiki pages.

= Introduction =

The Expertiza project allows "calibration assignments" to be performed where students are asked to review work that has also been reviewed by a member of the course staff. Calibration is the term used for rectifying, or checking or determining something. In the context of this project, a 'Calibrated review' is one which is performed by a student, so that (s)he can verify their work by comparing it with the instructor's response for the same assignment. If the student’s review “resembles” the staff-member’s review, then the student is presumed to be a competent reviewer. Since calibration reviews are meant as reference for better performance of peer reviews (which are performed later), they are not graded.

= Problem Statement =

== Project Purpose ==
Calibration submissions should be copied along with calibration assignments.

== Issue in current implementation ==
On creating a copy of a previous assignment, say for example Design Exercise, Fall '20 for the Fall '21 semester - the calibration assignments associated with it are not copied over. The instructor is required to impersonate extra participants, and submit work on behalf of each of the extra participants. This is obviously extra trouble, and it would be a lot more convenient if an instructor didn’t have to resubmit the same calibration submissions over and over, every semester. 

'''The following steps were taken to test the aforementioned issues:'''

'''Step 1:''' On copying the Design exercise assignment 
[[File:copy_2075.png]] 

'''Step 2:''' The original file contains the following calibration reviews 
[[File:cali_a_2075.png]] 

'''Step 3:''' However, the copy doesn't contain any of the calibrated reviews 
[[File:cali_b_2075.png]] 

==Difference between Previous Implementation and our desired plan ==

= Implementation =
==MVC==

The project is implemented in Ruby on Rails that uses MVC architecture. We have three separate modules namely User Interface, Database Model and Control Flow(Model, View and Controller).

==Principle==

We tend to reuse the already existing functionalities and data to our design. The calibration reviews that are present in the previous exercise will be copied into the newly created exercise which would prevent the intructor to perform additional tasks of performing reviews repeatedly. This would also prevent code duplication and additional memory usage.

== Proposed Design ==
The following must be added to the current implementation:

* The same extra participants in the assignment, which are used as calibration assignments are copied over to the newly copied directory
* The URLs and/or files that were submitted to the previous assignment must be copied over as well
* Test cases to check if the above-mentioned steps work as required

[More on the design pattern if any, ER/ UML diagrams to be updated as the project progresses]

== Files Involved ==
* '''submission_records_controller.rb'''
* '''index.html.erb''' in expertiza/app/views/submission_records

= Test Plan =

== Manual Testing Plan ==
Manual test to check if:
* The UI is working as expected [No broken links]
* The submissions [Files and Hyperlinks] are copied when an assignment for calibration is copied.

=== Directions for Manual Testing ===
* Go to the testing server [VCL Instance] and log in with the credentials - username: 'instructor6'; password: 'password'
* Go to an existing assignment (say A1) that you want to setup calibration for
** Select the '''copy''' button (generates A2)
** Toggle onto the calibration tab of the original directory (A1) and check the files present inside it
** Now, select the copied directory (A2)
** On the calibrations tab, check whether the copied submissions [Files and URLs] are present.

== RSpec Testing Plan ==
RSpec test to check:
* Validation of the models
* Sanity and basic functionality of controllers
** This involves essentially checking if the copied calibration's corresponding model has entries for the submissions

=== Directions for RSpec Testing ===
* Run the following commands:
** For controllers: rspec spec/controllers/
** For models: rspec spec/models/

= Useful Links =
*[https://github.com/expertiza/expertiza Expertiza on GitHub]
*[http://expertiza.ncsu.edu/ The live Expertiza website]
*[http://research.csc.ncsu.edu/efg/expertiza Expertiza project Details]

= Team Information =
* Nischal Kashyap
* Mounika Bachu
* Akshay Podila
* Dhanraj Raghunathan

CSC/ECE 517 Fall 2020 - E2075. calibration submissions should be copied along with calibration assignments

2020-10-28T07:56:15Z

Nkashya:

This wiki page describes the changes made under E2075, to ensure calibration submissions are copied along with calibration assignments for CSC/ECE 517, Fall 2020.

__TOC__

== About Expertiza ==
Expertiza is an open source project based on Ruby on Rails framework, created and maintained by the joint efforts of students and faculty at North Carolina State University.

It allows the instructors to create new assignments and customize new or existing assignments. Expertiza also allows an instructor to create a list of topics the students can sign up for. Students can form teams on the web application to work on various projects and assignments together. Additionally, students can peer review each other's submissions allowing them to improve upon their work. Expertiza supports submission across various document types, including the URLs and wiki pages.

= Introduction =

The Expertiza project allows "calibration assignments" to be performed where students are asked to review work that has also been reviewed by a member of the course staff. Calibration is the term used for rectifying, or checking or determining something. In the context of this project, a 'Calibrated review' is one which is performed by a student, so that (s)he can verify their work by comparing it with the instructor's response for the same assignment. If the student’s review “resembles” the staff-member’s review, then the student is presumed to be a competent reviewer. Since calibration reviews are meant as reference for better performance of peer reviews (which are performed later), they are not graded.

= Problem Statement =

== Project Purpose ==
Calibration submissions should be copied along with calibration assignments.

== Issue in current implementation ==
On creating a copy of a previous assignment, say for example Design Exercise, Fall '20 for the Fall '21 semester - the calibration assignments associated with it are not copied over. The instructor is required to impersonate extra participants, and submit work on behalf of each of the extra participants. This is obviously extra trouble, and it would be a lot more convenient if an instructor didn’t have to resubmit the same calibration submissions over and over, every semester. 

'''The following steps were taken to test the aforementioned issues:'''

'''Step 1:''' On copying the Design exercise assignment 
[[File:copy_2075.png]] 

'''Step 2:''' The original file contains the following calibration reviews 
[[File:cali_a_2075.png]] 

'''Step 3:''' However, the copy doesn't contain any of the calibrated reviews 
[[File:cali_b_2075.png]] 

= Implementation =
==MVC==

The project is implemented in Ruby on Rails that uses MVC architecture. We have three separate modules namely User Interface, Database Model and Control Flow(Model, View and Controller).

==Principle==

We tend to reuse the already existing functionalities and data to our design. The calibration reviews that are present in the previous exercise will be copied into the newly created exercise which would prevent the intructor to perform additional tasks of performing reviews repeatedly. This would also prevent code duplication and additional memory usage.

== Proposed Design ==
The following must be added to the current implementation:

* The same extra participants in the assignment, which are used as calibration assignments are copied over to the newly copied directory
* The URLs and/or files that were submitted to the previous assignment must be copied over as well
* Test cases to check if the above-mentioned steps work as required

[More on the design pattern if any, ER/ UML diagrams to be updated as the project progresses]

== Files Involved ==
* '''submission_records_controller.rb'''
* '''index.html.erb''' in expertiza/app/views/submission_records

= Test Plan =

== Manual Testing Plan ==
Manual test to check if:
* The UI is working as expected [No broken links]
* The submissions [Files and Hyperlinks] are copied when an assignment for calibration is copied.

=== Directions for Manual Testing ===
* Go to the testing server [VCL Instance] and log in with the credentials - username: 'instructor6'; password: 'password'
* Go to an existing assignment (say A1) that you want to setup calibration for
** Select the '''copy''' button (generates A2)
** Toggle onto the calibration tab of the original directory (A1) and check the files present inside it
** Now, select the copied directory (A2)
** On the calibrations tab, check whether the copied submissions [Files and URLs] are present.

== RSpec Testing Plan ==
RSpec test to check:
* Validation of the models
* Sanity and basic functionality of controllers
** This involves essentially checking if the copied calibration's corresponding model has entries for the submissions

=== Directions for RSpec Testing ===
* Run the following commands:
** For controllers: rspec spec/controllers/
** For models: rspec spec/models/

= Useful Links =
*[https://github.com/expertiza/expertiza Expertiza on GitHub]
*[http://expertiza.ncsu.edu/ The live Expertiza website]
*[http://research.csc.ncsu.edu/efg/expertiza Expertiza project Details]

= Team Information =
* Nischal Kashyap
* Mounika Bachu
* Akshay Podila
* Dhanraj Raghunathan

CSC/ECE 517 Fall 2020 - E2075. calibration submissions should be copied along with calibration assignments

2020-10-28T04:50:29Z

Nkashya:

This wiki page describes the changes made under E2075, to ensure calibration submissions are copied along with calibration assignments for CSC/ECE 517, Fall 2020.

__TOC__

== About Expertiza ==
Expertiza is an open source project based on Ruby on Rails framework, created and maintained by the joint efforts of students and faculty at North Carolina State University.

It allows the instructors to create new assignments and customize new or existing assignments. Expertiza also allows an instructor to create a list of topics the students can sign up for. Students can form teams on the web application to work on various projects and assignments together. Additionally, students can peer review each other's submissions allowing them to improve upon their work. Expertiza supports submission across various document types, including the URLs and wiki pages.

= Introduction =

The Expertiza project allows "calibration assignments" to be performed where students are asked to review work that has also been reviewed by a member of the course staff. Calibration is the term used for rectifying, or checking or determining something. In the context of this project, a 'Calibrated review' is one which is performed by a student, so that (s)he can verify their work by comparing it with the instructor's response for the same assignment. If the student’s review “resembles” the staff-member’s review, then the student is presumed to be a competent reviewer. Since calibration reviews are meant as reference for better performance of peer reviews (which are performed later), they are not graded.

= Problem Statement =

== Goal ==
Calibration submissions should be copied along with calibration assignments.

== Issue in current implementation ==
On creating a copy of a previous assignment, say for example Design Exercise, Fall '20 for the Fall '21 semester - the calibration assignments associated with it are not copied over. The instructor is required to impersonate extra participants, and submit work on behalf of each of the extra participants. This is obviously extra trouble, and it would be a lot more convenient if an instructor didn’t have to resubmit the same calibration submissions over and over, every semester. 

'''The following steps were taken to test the aforementioned issues:'''

'''Step 1:''' On copying the Design exercise assignment 
[[File:copy_2075.png]] 

'''Step 2:''' The original file contains the following calibration reviews 
[[File:cali_a_2075.png]] 

'''Step 3:''' However, the copy doesn't contain any of the calibrated reviews 
[[File:cali_b_2075.png]] 

= Implementation =
==MVC==

The project is implemented in Ruby on Rails that uses MVC architecture. We have three separate modules namely User Interface, Database Model and Control Flow(Model, View and Controller).

==Principle==

We tend to reuse the already existing functionalities and data to our design. The calibration reviews that are present in the previous exercise will be copied into the newly created exercise which would prevent the intructor to perform additional tasks of performing reviews repeatedly. This would also prevent code duplication and additional memory usage.

== Proposed Design ==
The following must be added to the current implementation:

* The same extra participants in the assignment, which are used as calibration assignments are copied over to the newly copied directory
* The URLs and/or files that were submitted to the previous assignment must be copied over as well
* Test cases to check if the above-mentioned steps work as required

[More on the design pattern if any, ER/ UML diagrams to be updated as the project progresses]

== Files Involved ==
* '''submission_records_controller.rb'''
* '''index.html.erb''' in expertiza/app/views/submission_records

= Test Plan =

== Manual Testing Plan ==
Manual test to check if:
* The UI is working as expected [No broken links]
* The submissions [Files and Hyperlinks] are copied when an assignment for calibration is copied.

=== Directions for Manual Testing ===
* Go to the testing server [VCL Instance] and log in with the credentials - username: 'instructor6'; password: 'password'
* Go to an existing assignment (say A1) that you want to setup calibration for
** Select the '''copy''' button (generates A2)
** Toggle onto the calibration tab of the original directory (A1) and check the files present inside it
** Now, select the copied directory (A2)
** On the calibrations tab, check whether the copied submissions [Files and URLs] are present.

== RSpec Testing Plan ==
RSpec test to check:
* Validation of the models
* Sanity and basic functionality of controllers
** This involves essentially checking if the copied calibration's corresponding model has entries for the submissions

=== Directions for RSpec Testing ===
* Run the following commands:
** For controllers: rspec spec/controllers/
** For models: rspec spec/models/

= Useful Links =
*[https://github.com/expertiza/expertiza Expertiza on GitHub]
*[http://expertiza.ncsu.edu/ The live Expertiza website]
*[http://research.csc.ncsu.edu/efg/expertiza Expertiza project Details]

= Team Information =
* Nischal Kashyap
* Mounika Bachu
* Akshay Podila
* Dhanraj Raghunathan

CSC/ECE 517 Fall 2020 - E2075. calibration submissions should be copied along with calibration assignments

2020-10-28T04:36:37Z

Nkashya:

CSC/ECE 517 Fall 2020 - E2075. calibration submissions should be copied along with calibration assignments

2020-10-28T04:34:41Z

Nkashya:

File:Impr3.png

2020-10-19T23:45:55Z

Nkashya:

File:Impr2.png

2020-10-19T23:45:23Z

Nkashya:

File:Impr1.png

2020-10-19T23:45:06Z

Nkashya:

CSC/ECE 517 Fall 2020 - E2056 Account Request Controller.rb

2020-10-19T23:44:48Z

Nkashya:

This wiki page is for the description of E2056.
=='''Introduction'''==
Prospective users are allowed to request Expertiza accounts over the web. When they are requested, the super-admin receives an email, and can go and approve or reject the request. The requester is then emailed as to whether the account has been approved, and if so, receives login credentials.

===Team Members===
* Sumitosh Pal (spal3)
* Mounika Bachu (mbachu)
* Nischal Badarinath Kashyap (nkashya)

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

===Issues===
The implementation is tedious to use, since all account requests since the beginning of time appear on the request page, and the super-admin needs to scroll to the bottom to find the current request. The requests can be approved/rejected only one at a time due to form design which can be improved. Also, the method names are quite nonstandard, when a lot of the methods have standard CRUD functionality.

The steps to reach the Pending Account Request Page is as follows:

1. Log in as an admin or superadmin.
* User Name: super_administrator2
* Password: password

2. Select Administration->show, which will bring up a list of features.

3. Click on “Pending Requests” from among the list of features to open the page containing requests from instructor/students.

The admin or super admin can see a list of requests made by students and instructor in chronological order which means that the recent requests are at the bottom of the page. This makes the process cumbersome because any operation on newly created requests would be at the bottom of the page. Also requests can be handled only one at a time due to radio button forms format. Moreover, the code has places that are inconsistent with DRY principles and require some refactoring to make them more standardized.

===Improvements for code readability===
1. Use authorization utilities from helper modules in action_allowed? to maintain code consistency.

2. Commenting on the method foreign to explain the purpose of this method.

3. Refactoring methods such as request_new and make the method more CRUD like.

4. Commenting on sections in create_requested_user_record which is a fairly long method, and includes several steps for creation of users which are not transparent.

===Improvements for UI===
1. Split the page into two components - a. Current(by default) b. History(Processed requests)
- Current: Displays only pending requests and in Last In First order.
- History: Displays all requests other than pending which are accepted or rejected by the admin.

2. Collapse all self introductions in requests to display them in one line and expand them on click for easier interaction.

3. Paginate the list to display only 10 results per page.

=='''Test Plan'''==
There is an existing rspec file corresponding to the account_request_controller. The changes made in code involve renaming a lot of existing variables and adding a lot of comments for methods, so most of the existing tests are modified instead of creating new ones.

===Manual Testing===
1. Beside "Home", click "Administration", then click "Show" and in Show click "Pending Requests".

2. Two tabs named Current and History are present.

3. Click on tab named "Current". It displays all the requests which are "Under Review" status and needs to be approved or rejected.

4. A checkbox is present right beside every request and you can select either all the requests which need to be accepted or all the requests which need to be rejected and click on "accept" or "reject" button. When you click on "Accept" button, all the requests selected will be accepted and will be moved from Current tab to History tab. Chicking "Reject" button, rejects all the requests selected and will move in a similar fashion.

5. Select tab named "History". It displays all the requests which are "Approved" or "Rejected" in reverse chronological order.

===RSpec Test===

In spec/controllers/account_request_controller_spec.rb we modified 6 test cases

MODIFIED
* input selection is nil
* input status is Approved
* input status is Approved but save fails
* input status is Rejected
* input status is Rejected but save fails
* create a new page for request

ADDED
* list_pending_requested_finalized .

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

First, we modified method named "request_new" to "new" which creates a new request.

# test case to create a new page for requests
context "#new" do
it '1' do
allow(Role).to receive(:find_by).with(name: 'instructor').and_return('instructor')
params = {role: 'instructor'}
post :new, params
expect(response).to render_template(:new)
end
end

2) list_pending_requested_finalized is clicked
# context "#list_pending_requested_finalized" do
it 'test list_pending_requested_finalized view' do
stub_current_user(super_admin, super_admin.role.name, super_admin.role)
get :list_pending_requested_finalized
expect(response).to render_template(:list_pending_requested_finalized)
end
end

3) Modified the existing check with the new params.
[[File:testing_spec_approved.jpg]]

[[File:testing_spec_approved2.jpg]]

[[File:testing_spec_approved3.jpg]]

=='''Solution'''==

===Create User Requested Record===
The function is designed to receive the information of the User who seeks the permission to access the website. The information is saved into the AccountRequest Model. The task was to split the function into different methods due to it being too verbose or write comments into the code. We chose to add comments into the function as splitting up would be inefficient.

[[File:Picture1.png]]

[[File:Picture2.png]]

===Splitting up the Views===
The task was to design a logic to the existing code such that the administrator would be able to see requests in two different views as in 'Under Review' or 'Approved/Rejected'. An additional function 'list_pending_request_finalized' was added that would filter the requests into 'Approved/Rejected' and the original 'list_pending_request' that filters the requests with 'Under Review' status. By default the requests are ordered in descending order with respect to updated_time with the status - 'Under Review'.

[[File:Picture3.png]]

[[File:Picture4.png]]

===Refactoring the code===
In the account_request_controller_spec.rb file we found a few of typing errors and have corrected and committed as part of this project specification.

[[File:Picture5.png]]

===Refactoring Methods===
The task was to rename the method names which are inappropriate and to rename CRUD like functions such as Request_new to CRUD function names.
[[File:solutionnew.png]]

===Method Commenting===
The method named "Foreign" is ambiguous and Method commenting is done describing the function and its parameters.
[[File:solutionforeign.png]]

===Adapting Authorization Utilities===
The method action_allowed? has been updated to replace the existing code which used non standard code to check user privileges. Instead, the authorization_helper.rb methods that were added as part of project E1915 has been adapted to maintain code readability.
[[File:action_allowed.jpg]]

===Reverse Chronology and Pagination===
The initial query receives all the requests from the database containing AccountRequest table without any form of order. This query that is being passed the list of requests has been modified in order to receive list in descending order of timestamp for updated_at field to show the recently changed requests at the top of list.
The gem 'will_paginate' is used to access pagination features in pending request page in order to display only specific number of requests at a time for ease of navigation. Using the method "paginate", the number of results per page can be set. Also the corresponding paginate tab is added in the html page for navigating between pages.
[[File:list_pending_requested.jpg]]

===Limit Self Introduction===
The list contains a field called "Self Introduction" in which the user writes a short description about themselves. This field can sometimes be large depending on how new requesting users modify it. To keep the view standardized, a limiter has been added to keep the display intact and expand/collapse the column on clicking it. For this we added a jquery plugin in layouts/application.html.erb
- <script type="text/javascript" src="https://www.viralpatel.net/demo/jquery/jquery.shorten.1.0.js"></script>
And the views/account_request/list_pending_requested.html.erb and views/account_request/list_pending_requested_finalized.html.erb are modified as well.
[[File:expand_collapse.jpg]]

=='''Result'''==

===How the UI was initially===

[[File:Picture9_E2056.png]]

===Our Improvement===

We can see that we have two tabs named Current and History and in Current we can see all the requests which are in "Under Review" status and which needs to be either Approved or Rejected. It only displays 10 requests on each page for readability.

[[File:Picture6_E2056.png]]
[[File:Picture7_E2056.png]]

All the check boxes which needs to be approved can be selected at once and get approved after clicking the approve button.

[[File:impr1.png]]

All the files which got approved are displayed above and gets moved to History tab. Same happens with Rejecting requests.

[[File:impr2.png]]

In the history tab, All the files which got approved are added to the previous requests which got approved or rejected. It only displays 10 requests on each page for readability.

[[File:impr3.png]]

In the requests table the column Self Introduction has a "more" link that lets the user expand the column to view overall content inside it and a "less" to collapse it back to original.

[[File:imp4.png]]

File:Imp1.png

2020-10-19T23:43:39Z

Nkashya: Nkashya uploaded a new version of File:Imp1.png

CSC/ECE 517 Fall 2020 - E2056 Account Request Controller.rb

2020-10-19T23:39:03Z

Nkashya:

This wiki page is for the description of E2056.
=='''Introduction'''==
Prospective users are allowed to request Expertiza accounts over the web. When they are requested, the super-admin receives an email, and can go and approve or reject the request. The requester is then emailed as to whether the account has been approved, and if so, receives login credentials.

===Team Members===
* Sumitosh Pal (spal3)
* Mounika Bachu (mbachu)
* Nischal Badarinath Kashyap (nkashya)

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

===Issues===
The implementation is tedious to use, since all account requests since the beginning of time appear on the request page, and the super-admin needs to scroll to the bottom to find the current request. The requests can be approved/rejected only one at a time due to form design which can be improved. Also, the method names are quite nonstandard, when a lot of the methods have standard CRUD functionality.

The steps to reach the Pending Account Request Page is as follows:

1. Log in as an admin or superadmin.
* User Name: super_administrator2
* Password: password

2. Select Administration->show, which will bring up a list of features.

3. Click on “Pending Requests” from among the list of features to open the page containing requests from instructor/students.

The admin or super admin can see a list of requests made by students and instructor in chronological order which means that the recent requests are at the bottom of the page. This makes the process cumbersome because any operation on newly created requests would be at the bottom of the page. Also requests can be handled only one at a time due to radio button forms format. Moreover, the code has places that are inconsistent with DRY principles and require some refactoring to make them more standardized.

===Improvements for code readability===
1. Use authorization utilities from helper modules in action_allowed? to maintain code consistency.

2. Commenting on the method foreign to explain the purpose of this method.

3. Refactoring methods such as request_new and make the method more CRUD like.

4. Commenting on sections in create_requested_user_record which is a fairly long method, and includes several steps for creation of users which are not transparent.

===Improvements for UI===
1. Split the page into two components - a. Current(by default) b. History(Processed requests)
- Current: Displays only pending requests and in Last In First order.
- History: Displays all requests other than pending which are accepted or rejected by the admin.

2. Collapse all self introductions in requests to display them in one line and expand them on click for easier interaction.

3. Paginate the list to display only 10 results per page.

=='''Test Plan'''==
There is an existing rspec file corresponding to the account_request_controller. The changes made in code involve renaming a lot of existing variables and adding a lot of comments for methods, so most of the existing tests are modified instead of creating new ones.

===Manual Testing===
1. Beside "Home", click "Administration", then click "Show" and in Show click "Pending Requests".

2. Two tabs named Current and History are present.

3. Click on tab named "Current". It displays all the requests which are "Under Review" status and needs to be approved or rejected.

4. A checkbox is present right beside every request and you can select either all the requests which need to be accepted or all the requests which need to be rejected and click on "accept" or "reject" button. When you click on "Accept" button, all the requests selected will be accepted and will be moved from Current tab to History tab. Chicking "Reject" button, rejects all the requests selected and will move in a similar fashion.

5. Select tab named "History". It displays all the requests which are "Approved" or "Rejected" in reverse chronological order.

===RSpec Test===

In spec/controllers/account_request_controller_spec.rb we modified 6 test cases

MODIFIED
* input selection is nil
* input status is Approved
* input status is Approved but save fails
* input status is Rejected
* input status is Rejected but save fails
* create a new page for request

ADDED
* list_pending_requested_finalized .

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

First, we modified method named "request_new" to "new" which creates a new request.

# test case to create a new page for requests
context "#new" do
it '1' do
allow(Role).to receive(:find_by).with(name: 'instructor').and_return('instructor')
params = {role: 'instructor'}
post :new, params
expect(response).to render_template(:new)
end
end

2) list_pending_requested_finalized is clicked
# context "#list_pending_requested_finalized" do
it 'test list_pending_requested_finalized view' do
stub_current_user(super_admin, super_admin.role.name, super_admin.role)
get :list_pending_requested_finalized
expect(response).to render_template(:list_pending_requested_finalized)
end
end

3) Modified the existing check with the new params.
[[File:testing_spec_approved.jpg]]

[[File:testing_spec_approved2.jpg]]

[[File:testing_spec_approved3.jpg]]

=='''Solution'''==

===Create User Requested Record===
The function is designed to receive the information of the User who seeks the permission to access the website. The information is saved into the AccountRequest Model. The task was to split the function into different methods due to it being too verbose or write comments into the code. We chose to add comments into the function as splitting up would be inefficient.

[[File:Picture1.png]]

[[File:Picture2.png]]

===Splitting up the Views===
The task was to design a logic to the existing code such that the administrator would be able to see requests in two different views as in 'Under Review' or 'Approved/Rejected'. An additional function 'list_pending_request_finalized' was added that would filter the requests into 'Approved/Rejected' and the original 'list_pending_request' that filters the requests with 'Under Review' status. By default the requests are ordered in descending order with respect to updated_time with the status - 'Under Review'.

[[File:Picture3.png]]

[[File:Picture4.png]]

===Refactoring the code===
In the account_request_controller_spec.rb file we found a few of typing errors and have corrected and committed as part of this project specification.

[[File:Picture5.png]]

===Refactoring Methods===
The task was to rename the method names which are inappropriate and to rename CRUD like functions such as Request_new to CRUD function names.
[[File:solutionnew.png]]

===Method Commenting===
The method named "Foreign" is ambiguous and Method commenting is done describing the function and its parameters.
[[File:solutionforeign.png]]

===Adapting Authorization Utilities===
The method action_allowed? has been updated to replace the existing code which used non standard code to check user privileges. Instead, the authorization_helper.rb methods that were added as part of project E1915 has been adapted to maintain code readability.
[[File:action_allowed.jpg]]

===Reverse Chronology and Pagination===
The initial query receives all the requests from the database containing AccountRequest table without any form of order. This query that is being passed the list of requests has been modified in order to receive list in descending order of timestamp for updated_at field to show the recently changed requests at the top of list.
The gem 'will_paginate' is used to access pagination features in pending request page in order to display only specific number of requests at a time for ease of navigation. Using the method "paginate", the number of results per page can be set. Also the corresponding paginate tab is added in the html page for navigating between pages.
[[File:list_pending_requested.jpg]]

===Limit Self Introduction===
The list contains a field called "Self Introduction" in which the user writes a short description about themselves. This field can sometimes be large depending on how new requesting users modify it. To keep the view standardized, a limiter has been added to keep the display intact and expand/collapse the column on clicking it. For this we added a jquery plugin in layouts/application.html.erb
- <script type="text/javascript" src="https://www.viralpatel.net/demo/jquery/jquery.shorten.1.0.js"></script>
And the views/account_request/list_pending_requested.html.erb and views/account_request/list_pending_requested_finalized.html.erb are modified as well.
[[File:expand_collapse.jpg]]

=='''Result'''==

===How the UI was initially===

[[File:Picture9_E2056.png]]

===Our Improvement===

We can see that we have two tabs named Current and History and in Current we can see all the requests which are in "Under Review" status and which needs to be either Approved or Rejected. It only displays 10 requests on each page for readability.

[[File:Picture6_E2056.png]]
[[File:Picture7_E2056.png]]

All the check boxes which needs to be approved can be selected at once and get approved after clicking the approve button.

[[File:imp1.png]]

All the files which got approved are displayed above and gets moved to History tab. Same happens with Rejecting requests.

[[File:imp2.png]]

In the history tab, All the files which got approved are added to the previous requests which got approved or rejected. It only displays 10 requests on each page for readability.

[[File:imp3.png]]

In the requests table the column Self Introduction has a "more" link that lets the user expand the column to view overall content inside it and a "less" to collapse it back to original.

[[File:imp4.png]]

CSC/ECE 517 Fall 2020 - E2056 Account Request Controller.rb

2020-10-19T23:37:36Z

Nkashya:

This wiki page is for the description of E2056.
=='''Introduction'''==
Prospective users are allowed to request Expertiza accounts over the web. When they are requested, the super-admin receives an email, and can go and approve or reject the request. The requester is then emailed as to whether the account has been approved, and if so, receives login credentials.

===Team Members===
* Sumitosh Pal (spal3)
* Mounika Bachu (mbachu)
* Nischal Badarinath Kashyap (nkashya)

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

===Issues===
The implementation is tedious to use, since all account requests since the beginning of time appear on the request page, and the super-admin needs to scroll to the bottom to find the current request. The requests can be approved/rejected only one at a time due to form design which can be improved. Also, the method names are quite nonstandard, when a lot of the methods have standard CRUD functionality.

The steps to reach the Pending Account Request Page is as follows:

1. Log in as an admin or superadmin.
* User Name: super_administrator2
* Password: password

2. Select Administration->show, which will bring up a list of features.

3. Click on “Pending Requests” from among the list of features to open the page containing requests from instructor/students.

The admin or super admin can see a list of requests made by students and instructor in chronological order which means that the recent requests are at the bottom of the page. This makes the process cumbersome because any operation on newly created requests would be at the bottom of the page. Also requests can be handled only one at a time due to radio button forms format. Moreover, the code has places that are inconsistent with DRY principles and require some refactoring to make them more standardized.

===Improvements for code readability===
1. Use authorization utilities from helper modules in action_allowed? to maintain code consistency.

2. Commenting on the method foreign to explain the purpose of this method.

3. Refactoring methods such as request_new and make the method more CRUD like.

4. Commenting on sections in create_requested_user_record which is a fairly long method, and includes several steps for creation of users which are not transparent.

===Improvements for UI===
1. Split the page into two components - a. Current(by default) b. History(Processed requests)
- Current: Displays only pending requests and in Last In First order.
- History: Displays all requests other than pending which are accepted or rejected by the admin.

2. Collapse all self introductions in requests to display them in one line and expand them on click for easier interaction.

3. Paginate the list to display only 10 results per page.

=='''Test Plan'''==
There is an existing rspec file corresponding to the account_request_controller. The changes made in code involve renaming a lot of existing variables and adding a lot of comments for methods, so most of the existing tests are modified instead of creating new ones.

===Manual Testing===
1. Beside "Home", click "Administration", then click "Show" and in Show click "Pending Requests".

2. Two tabs named Current and History are present.

3. Click on tab named "Current". It displays all the requests which are "Under Review" status and needs to be approved or rejected.

4. A checkbox is present right beside every request and you can select either all the requests which need to be accepted or all the requests which need to be rejected and click on "accept" or "reject" button. When you click on "Accept" button, all the requests selected will be accepted and will be moved from Current tab to History tab. Chicking "Reject" button, rejects all the requests selected and will move in a similar fashion.

5. Select tab named "History". It displays all the requests which are "Approved" or "Rejected" in reverse chronological order.

===RSpec Test===

In spec/controllers/account_request_controller_spec.rb we modified 6 test cases

MODIFIED
* input selection is nil
* input status is Approved
* input status is Approved but save fails
* input status is Rejected
* input status is Rejected but save fails
* create a new page for request

ADDED
* list_pending_requested_finalized .

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

First, we modified method named "request_new" to "new" which creates a new request.

# test case to create a new page for requests
context "#new" do
it '1' do
allow(Role).to receive(:find_by).with(name: 'instructor').and_return('instructor')
params = {role: 'instructor'}
post :new, params
expect(response).to render_template(:new)
end
end

2) list_pending_requested_finalized is clicked
# context "#list_pending_requested_finalized" do
it 'test list_pending_requested_finalized view' do
stub_current_user(super_admin, super_admin.role.name, super_admin.role)
get :list_pending_requested_finalized
expect(response).to render_template(:list_pending_requested_finalized)
end
end

3) Modified the existing check with the new params.
[[File:testing_spec_approved.jpg]]

[[File:testing_spec_approved2.jpg]]

[[File:testing_spec_approved3.jpg]]

=='''Solution'''==

===Create User Requested Record===
The function is designed to receive the information of the User who seeks the permission to access the website. The information is saved into the AccountRequest Model. The task was to split the function into different methods due to it being too verbose or write comments into the code. We chose to add comments into the function as splitting up would be inefficient.

[[File:Picture1.png]]

[[File:Picture2.png]]

===Splitting up the Views===
The task was to design a logic to the existing code such that the administrator would be able to see requests in two different views as in 'Under Review' or 'Approved/Rejected'. An additional function 'list_pending_request_finalized' was added that would filter the requests into 'Approved/Rejected' and the original 'list_pending_request' that filters the requests with 'Under Review' status. By default the requests are ordered in descending order with respect to updated_time with the status - 'Under Review'.

[[File:Picture3.png]]

[[File:Picture4.png]]

===Refactoring the code===
In the account_request_controller_spec.rb file we found a few of typing errors and have corrected and committed as part of this project specification.

===Refactoring Methods===
The task was to rename the method names which are inappropriate and to rename CRUD like functions such as Request_new to CRUD function names.
[[File:solutionnew.png]]

===Method Commenting===
The method named "Foreign" is ambiguous and Method commenting is done describing the function and its parameters.
[[File:solutionforeign.png]]

===Adapting Authorization Utilities===
The method action_allowed? has been updated to replace the existing code which used non standard code to check user privileges. Instead, the authorization_helper.rb methods that were added as part of project E1915 has been adapted to maintain code readability.
[[File:action_allowed.jpg]]

===Reverse Chronology and Pagination===
The initial query receives all the requests from the database containing AccountRequest table without any form of order. This query that is being passed the list of requests has been modified in order to receive list in descending order of timestamp for updated_at field to show the recently changed requests at the top of list.
The gem 'will_paginate' is used to access pagination features in pending request page in order to display only specific number of requests at a time for ease of navigation. Using the method "paginate", the number of results per page can be set. Also the corresponding paginate tab is added in the html page for navigating between pages.
[[File:list_pending_requested.jpg]]

===Limit Self Introduction===
The list contains a field called "Self Introduction" in which the user writes a short description about themselves. This field can sometimes be large depending on how new requesting users modify it. To keep the view standardized, a limiter has been added to keep the display intact and expand/collapse the column on clicking it. For this we added a jquery plugin in layouts/application.html.erb
- <script type="text/javascript" src="https://www.viralpatel.net/demo/jquery/jquery.shorten.1.0.js"></script>
And the views/account_request/list_pending_requested.html.erb and views/account_request/list_pending_requested_finalized.html.erb are modified as well.
[[File:expand_collapse.jpg]]

=='''Result'''==

===How the UI was initially===

[[File:Picture9_E2056.png]]

===Our Improvement===

We can see that we have two tabs named Current and History and in Current we can see all the requests which are in "Under Review" status and which needs to be either Approved or Rejected. It only displays 10 requests on each page for readability.

[[File:Picture6_E2056.png]]
[[File:Picture7_E2056.png]]

All the check boxes which needs to be approved can be selected at once and get approved after clicking the approve button.

[[File:imp1.png]]

All the files which got approved are displayed above and gets moved to History tab. Same happens with Rejecting requests.

[[File:imp2.png]]

In the history tab, All the files which got approved are added to the previous requests which got approved or rejected. It only displays 10 requests on each page for readability.

[[File:imp3.png]]

In the requests table the column Self Introduction has a "more" link that lets the user expand the column to view overall content inside it and a "less" to collapse it back to original.

[[File:imp4.png]]

CSC/ECE 517 Fall 2020 - E2056 Account Request Controller.rb

2020-10-19T23:36:02Z

Nkashya:

This wiki page is for the description of E2056.
=='''Introduction'''==
Prospective users are allowed to request Expertiza accounts over the web. When they are requested, the super-admin receives an email, and can go and approve or reject the request. The requester is then emailed as to whether the account has been approved, and if so, receives login credentials.

===Team Members===
* Sumitosh Pal (spal3)
* Mounika Bachu (mbachu)
* Nischal Badarinath Kashyap (nkashya)

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

===Issues===
The implementation is tedious to use, since all account requests since the beginning of time appear on the request page, and the super-admin needs to scroll to the bottom to find the current request. The requests can be approved/rejected only one at a time due to form design which can be improved. Also, the method names are quite nonstandard, when a lot of the methods have standard CRUD functionality.

The steps to reach the Pending Account Request Page is as follows:

1. Log in as an admin or superadmin.
* User Name: super_administrator2
* Password: password

2. Select Administration->show, which will bring up a list of features.

3. Click on “Pending Requests” from among the list of features to open the page containing requests from instructor/students.

The admin or super admin can see a list of requests made by students and instructor in chronological order which means that the recent requests are at the bottom of the page. This makes the process cumbersome because any operation on newly created requests would be at the bottom of the page. Also requests can be handled only one at a time due to radio button forms format. Moreover, the code has places that are inconsistent with DRY principles and require some refactoring to make them more standardized.

===Improvements for code readability===
1. Use authorization utilities from helper modules in action_allowed? to maintain code consistency.

2. Commenting on the method foreign to explain the purpose of this method.

3. Refactoring methods such as request_new and make the method more CRUD like.

4. Commenting on sections in create_requested_user_record which is a fairly long method, and includes several steps for creation of users which are not transparent.

===Improvements for UI===
1. Split the page into two components - a. Current(by default) b. History(Processed requests)
- Current: Displays only pending requests and in Last In First order.
- History: Displays all requests other than pending which are accepted or rejected by the admin.

2. Collapse all self introductions in requests to display them in one line and expand them on click for easier interaction.

3. Paginate the list to display only 10 results per page.

=='''Test Plan'''==
There is an existing rspec file corresponding to the account_request_controller. The changes made in code involve renaming a lot of existing variables and adding a lot of comments for methods, so most of the existing tests are modified instead of creating new ones.

===Manual Testing===
1. Beside "Home", click "Administration", then click "Show" and in Show click "Pending Requests".

2. Two tabs named Current and History are present.

3. Click on tab named "Current". It displays all the requests which are "Under Review" status and needs to be approved or rejected.

4. A checkbox is present right beside every request and you can select either all the requests which need to be accepted or all the requests which need to be rejected and click on "accept" or "reject" button. When you click on "Accept" button, all the requests selected will be accepted and will be moved from Current tab to History tab. Chicking "Reject" button, rejects all the requests selected and will move in a similar fashion.

5. Select tab named "History". It displays all the requests which are "Approved" or "Rejected" in reverse chronological order.

===RSpec Test===

In spec/controllers/account_request_controller_spec.rb we modified 6 test cases

MODIFIED
* input selection is nil
* input status is Approved
* input status is Approved but save fails
* input status is Rejected
* input status is Rejected but save fails
* create a new page for request

ADDED
* list_pending_requested_finalized .

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

First, we modified method named "request_new" to "new" which creates a new request.

# test case to create a new page for requests
context "#new" do
it '1' do
allow(Role).to receive(:find_by).with(name: 'instructor').and_return('instructor')
params = {role: 'instructor'}
post :new, params
expect(response).to render_template(:new)
end
end

2) list_pending_requested_finalized is clicked
# context "#list_pending_requested_finalized" do
it 'test list_pending_requested_finalized view' do
stub_current_user(super_admin, super_admin.role.name, super_admin.role)
get :list_pending_requested_finalized
expect(response).to render_template(:list_pending_requested_finalized)
end
end

3) Modified the existing check with the new params.
[[File:testing_spec_approved.jpg]]

[[File:testing_spec_approved2.jpg]]

[[File:testing_spec_approved3.jpg]]

=='''Solution'''==

===Create User Requested Record===
The function is designed to receive the information of the User who seeks the permission to access the website. The information is saved into the AccountRequest Model. The task was to split the function into different methods due to it being too verbose or write comments into the code. We chose to add comments into the function as splitting up would be inefficient.

===Splitting up the Views===
The task was to design a logic to the existing code such that the administrator would be able to see requests in two different views as in 'Under Review' or 'Approved/Rejected'. An additional function 'list_pending_request_finalized' was added that would filter the requests into 'Approved/Rejected' and the original 'list_pending_request' that filters the requests with 'Under Review' status. By default the requests are ordered in descending order with respect to updated_time with the status - 'Under Review'.

===Refactoring the code===
In the account_request_controller_spec.rb file we found a few of typing errors and have corrected and committed as part of this project specification.

===Refactoring Methods===
The task was to rename the method names which are inappropriate and to rename CRUD like functions such as Request_new to CRUD function names.
[[File:solutionnew.png]]

===Method Commenting===
The method named "Foreign" is ambiguous and Method commenting is done describing the function and its parameters.
[[File:solutionforeign.png]]

===Adapting Authorization Utilities===
The method action_allowed? has been updated to replace the existing code which used non standard code to check user privileges. Instead, the authorization_helper.rb methods that were added as part of project E1915 has been adapted to maintain code readability.
[[File:action_allowed.jpg]]

===Reverse Chronology and Pagination===
The initial query receives all the requests from the database containing AccountRequest table without any form of order. This query that is being passed the list of requests has been modified in order to receive list in descending order of timestamp for updated_at field to show the recently changed requests at the top of list.
The gem 'will_paginate' is used to access pagination features in pending request page in order to display only specific number of requests at a time for ease of navigation. Using the method "paginate", the number of results per page can be set. Also the corresponding paginate tab is added in the html page for navigating between pages.
[[File:list_pending_requested.jpg]]

===Limit Self Introduction===
The list contains a field called "Self Introduction" in which the user writes a short description about themselves. This field can sometimes be large depending on how new requesting users modify it. To keep the view standardized, a limiter has been added to keep the display intact and expand/collapse the column on clicking it. For this we added a jquery plugin in layouts/application.html.erb
- <script type="text/javascript" src="https://www.viralpatel.net/demo/jquery/jquery.shorten.1.0.js"></script>
And the views/account_request/list_pending_requested.html.erb and views/account_request/list_pending_requested_finalized.html.erb are modified as well.
[[File:expand_collapse.jpg]]

=='''Result'''==

===How the UI was initially===

[[File:Picture9_E2056.png]]

===Our Improvement===

We can see that we have two tabs named Current and History and in Current we can see all the requests which are in "Under Review" status and which needs to be either Approved or Rejected. It only displays 10 requests on each page for readability.

[[File:Picture6_E2056.png]]
[[File:Picture7_E2056.png]]

All the check boxes which needs to be approved can be selected at once and get approved after clicking the approve button.

[[File:imp1.png]]

All the files which got approved are displayed above and gets moved to History tab. Same happens with Rejecting requests.

[[File:imp2.png]]

In the history tab, All the files which got approved are added to the previous requests which got approved or rejected. It only displays 10 requests on each page for readability.

[[File:imp3.png]]

In the requests table the column Self Introduction has a "more" link that lets the user expand the column to view overall content inside it and a "less" to collapse it back to original.

[[File:imp4.png]]

=='''Code Snippets'''==

===Create User Requested Record===
[[File:Picture1.png]]

[[File:Picture2.png]]

===Splitting up the Views===

[[File:Picture3.png]]
[[File:Picture4.png]]

===RSpec Test Changes===
[[File:Picture5.png]]