Expertiza_Wiki - User contributions [en]

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

2020-11-18T07:05:22Z

Apodila:

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]] 

== 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-18T07:04:03Z

Apodila:

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]] 

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

== RSpec Testing Plan ==
The following RSpec tests 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-18T07:03:42Z

Apodila:

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]] 

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

== RSpec Testing Plan ==
The following RSpec tests were added to the assignments_contoller_spec.rb

[[File:Test1_2075.jpeg |1000px|Image: 1000 pixels]] 
[[File:Test2_2075.jpeg |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:Test2 2075.png

2020-11-18T07:03:00Z

Apodila:

File:Test1 2075.png

2020-11-18T07:02:42Z

Apodila:

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

2020-11-18T05:52:05Z

Apodila:

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]] 

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

== 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 =
*[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-18T05:51:03Z

Apodila:

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]] 

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

== 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 =
*[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-18T05:50:18Z

Apodila:

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.png |1000px|Image: 1000 pixels]] 
[[File:Code1_2075.png |1000px|Image: 1000 pixels]] 
[[File:Code2_2075.png |1000px|Image: 1000 pixels]] 
[[File:Code3_2075.png |1000px|Image: 1000 pixels]] 
[[File:Code4_2075.png |1000px|Image: 1000 pixels]] 
[[File:Code5_2075.png |1000px|Image: 1000 pixels]] 
[[File:Code6_2075.png |1000px|Image: 1000 pixels]]
[[File:Code7_2075.png |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]] 

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

== 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 =
*[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:Code7 2075.jpeg

2020-11-18T05:49:07Z

Apodila:

File:Code6 2075.jpeg

2020-11-18T05:48:54Z

Apodila:

File:Code5 2075.jpeg

2020-11-18T05:48:35Z

Apodila:

File:Code4 2075.jpeg

2020-11-18T05:48:21Z

Apodila:

File:Code3 2075.jpeg

2020-11-18T05:48:02Z

Apodila:

File:Code2 2075.jpeg

2020-11-18T05:47:42Z

Apodila:

File:Code1 2075.jpeg

2020-11-18T05:47:24Z

Apodila:

File:Code 2075.jpeg

2020-11-18T05:46:11Z

Apodila:

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

2020-11-18T05:44:21Z

Apodila:

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

= 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]] 

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

== 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 =
*[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-18T05:32:43Z

Apodila:

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

= 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]] 

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

== 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/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-18T05:29:46Z

Apodila:

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

= 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]] 

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

== 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-11-18T05:29:04Z

Apodila:

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

= 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]] 

== Video illustrating changes ==
[https://youtu.be/497e8XQ0Jds '''E2075 Video Link''']

== 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-11-18T05:05:30Z

Apodila:

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.

== Proposed 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'''

== 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 ==
* 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]] 

== 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-11-18T04:34:01Z

Apodila:

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.

== 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

==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'''

== 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 ==
* 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]] 

== 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-11-18T04:33:46Z

Apodila:

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

==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'''

== 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 ==
* 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]] 

== 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-11-18T04:32:57Z

Apodila:

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]

==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'''

== 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 ==
* 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]] 

== 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-11-17T07:11:27Z

Apodila:

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 ==
* '''app/models/assignment_form.rb'''
* '''app/views/assignments/edit/_calibration.html.erb'''
* ''' db/schema.rb'''

==Difference between Previous Implementation and Identified Solution ==

===Previous Implementation===

[[File:um20201.png]]

===Identified 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 ==
* 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]] 

== 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-11-17T07:10:45Z

Apodila:

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 ==
* '''app/models/assignment_form.rb'''
* '''app/views/assignments/edit/_calibration.html.erb'''
* ''' db/schema.rb'''

==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 ==
* 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]] 

== 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-11-17T06:44:32Z

Apodila:

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 ==
* 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]] 

== 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-11-17T06:43:34Z

Apodila:

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 ==
* 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]] 

== 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-11-17T06:43:03Z

Apodila:

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 ==
* 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]] 

== 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-11-17T06:42:16Z

Apodila:

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 ==
* 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 |100px|Image: 100 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 |100px|Image: 100 pixels]] 

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

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

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

== 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-11-17T06:37:34Z

Apodila:

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 ==
* 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]] 

'''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]] 

[[File:with_calib.png]] 

'''Step 3:''' Copy the assignment, by selecting the icon shown below 
[[File:copying_2075.png]] 

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

== 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-11-17T06:36:13Z

Apodila:

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 ==
* 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]] 
'''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]] 
[[File:with_calib.png]] 
'''Step 3:''' Copy the assignment, by selecting the icon shown below 
[[File:copying_2075.png]] 
'''Step 4:''' On inspection of the copied assignment, it is observed that the calibration assignments have been copied over. 
[[File:copied_2075.png]] 

== 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-11-17T06:35:43Z

Apodila:

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 ==
* 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]] 
'''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]] 
[[File:with_calib.png]] 
'''Step 3:''' Copy the assignment, by selecting the icon shown below 
[[File:copying_2075.png]] 
'''Step 4:''' On inspection of the copied assignment, it is observed that the calibration assignments have been copied over. 
[[File:successful_save_2075.png]] 

== 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-11-17T06:34:44Z

Apodila:

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 ==
* 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]] 
'''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]] 
[[File:with_calib.png]] 
'''Step 3:''' Copy the assignment, by selecting the icon shown below 
[[File:copying_2075.png]] 
'''Step 4:''' On inspection of the copied assignment, it is observed that the calibration assignments have been copied over. 
[[File:successful_save_2054.JPG]] 

== 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:Editing 2075.png

2020-11-17T06:21:59Z

Apodila:

File:Copied 2075.png

2020-11-17T06:09:59Z

Apodila:

File:Copying 2075.png

2020-11-17T06:09:12Z

Apodila:

File:With calib.png

2020-11-17T06:08:25Z

Apodila:

File:Logging in 2075.png

2020-11-17T06:07:01Z

Apodila:

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

2020-10-29T04:04:41Z

Apodila:

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

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

2020-10-29T04:04:27Z

Apodila:

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

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

2020-10-28T18:18:01Z

Apodila:

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]]

= 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-28T18:17:39Z

Apodila:

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 Implementation ==

'''Previous Implementation'''

[[File:Preimp.png]]

'''Proposed Implementation'''

[[File:futimp.png]]

= 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-28T18:15:21Z

Apodila:

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 Proposed Implementation ==

'''Previous Implementation'''

[[File:Preimp.png]]

'''Proposed 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

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

2020-10-28T18:14:24Z

Apodila:

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]]

'''Proposed 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

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

2020-10-28T18:12:59Z

Apodila:

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

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

2020-10-28T04:01:34Z

Apodila:

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

2020-10-28T04:00:00Z

Apodila:

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

2020-10-28T03:58:55Z

Apodila:

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

2020-10-28T03:53:52Z

Apodila: