Expertiza_Wiki - User contributions [en]

CSC/ECE 517 Fall 2018/E1872 Track Time Students Look At Other Submissions

2018-12-07T05:25:47Z

Nuachary: /* Objective of project */

'''
== Introduction ==

'''

The expertiza project takes advantage of peer-review among students to allow them to learn from each other. To track the review time that each student spend on each submitted resources is meaningful for instructors to study and improve the teaching experience. The previous team working on the project has solved part of such problems by tracking the active time of windows opened from the submitted links by till the window is closed or gives a periodic pop up to ask if the user is still reviewing. And thus records the end time. It is done using mature third-party APIs to record link review time.

In this project, we require to conglomerate the details of each review given by a student on the existing Review Report page.
This will ease the task for the instructor to get the insights of a review on one single page in order to grade the student based on his/her review.

To accomplish this goal, here are the general solutions designed and implemented in this project:

* Designed and implemented toggle view component using Javascript and Ruby to open students’ reviews inside the review report table

* Used DOM to calculate and display the total time spent on the review per round.

* Modify Review report (views/review_mapping/_review_report.html.erb) to show the total and detailed time spent on each review submissions.

'''

== Flowchart ==

[[File:E1791_niharika.png]]

[[File:Review_time_flowchart_(1).png]]

== Objective of project ==

'''Objective 1:'''

The details of time spent on every assignment is displayed separately on the reviewer report page. As this is inconvenient we have to display all the statistics on the review report page.

'''Proposed Solution:'''

* We have added a link below the student ID in the first column of the review report page for each assignment.
* This is a toggle-able link and is available to each student details uniquely as shows below:

[[File:Image_(4).png]]

* Clicking on the link will toggle between showing/hiding a new column containing the review details to the table.

[[File:Image_(1).png]]

* The table contains the details regarding the team reviewed, round number of the review, total time spent on reviewing and time spent reviewing each link in the submission.

[[File:Image_(3).png]]

Files needed to be changed:

review_mapping/_review_report.html.erb

== Design ==
'''Files Changed:'''

review_mapping/_review_report.html.erb -
This is the file for the review report. We have added the functionality of a toggle link below each student id in the first column. Clicking on this link will display the details of the reviews done by this student. On clicking again the details will disappear, giving the user the flexibility of viewing these details if need be.
The design makes use of the following models:
* Participant
* ResponseMap
* ResponseTime
* Assignment
* Team

First we fetch all the reviews done by the student by providing the user_id of the student to Participant which gives us the set of reviews done by that user. Then we iterate through these reviews. As reviews are based on the number of review rounds in the Assignment, we fetch the total number of review rounds for the current assignment from the Assignment model by fetching the current Assignment object using assignment id and then accessing the 'round_of_reviews' property of the object. The details of each review like the reviewer_id, reviewee_id , reviewed_object_id is stored in the ResponseMap model. We fetch the ResponseMap set for each such review from the ResponseMap by giving it reviewer_id and reviewed_object_id as the assignment id.
Now we iterate through this set of ResponseMaps. The data for the link reviewed and the time taken for each link is in ResponseTime model which is linked to the ResponseMap through map_id. We make use of this and for each ResponseMap we put in a loop to get all possible ResponseTime for every link reviewed by the student. Finally we display this whole thing in the form of a table with the headers:
* Team Reviewed : This is the team reviewed by the student. We get the team name by passing reviewee_id found in each ResponseMap to the Team model.
* Total Time(mins) : This is the total time spent by the student in reviewing this team. We have written custom Javascript functions to calculate total time by adding time spent on individual links.
* Round : This is the review round number for which this review has been performed.
* Links : This will give you a list of links one after the other which the student has reviewed. These links are found as entries in the ResponseTime model with other information as well.
* Time spent per link (mins) : This is the time spent in reviewing each link. Again we have written functions in embedded Ruby to calculate time in mins using the start and end times of reviewing this link.

'''Algorithm:'''
<pre>
1.Fetch all reviews of student from Participant by providing user_id of student

2.For a review in the reviews list do

a. Fetch all response maps associations by providing reviewer_id as review.id and reviewed_object_id as the Assignment.id

b.Fetch the number of review rounds needed by the assignment from Assignment model

c.For each response map in the response map list do

i. For each round from 1 to number of rounds do

1. Initialize map_total_time=0

2. Fetch the response time set from ResponseTime model by providing map_id as map.id and round number

3. Initialize a count variable which will keep count of links. count = 0.

4. For each link entry in the response time set do

a. If current link is the first link being considered do

i. Print team being reviewed name using Team model and id as reviewee_id

ii. Keep an empty space with id as map.id+””+roundNumber for uniqueness

iii. Print the round

b. Else

i. Print an empty space

ii. Print an empty space

iii. Print an empty space

c. Get the time spent on the link by subtracting start time and end time. Convert the time to mins by dividing by 60.

d. Add it to map_total_time which keeps tab of sum of time spent on all links

e. Print link time

5. Increment count

6. Set the value of map_total_time in the block with id=map.id+roundNumber using innerHtml in 4-a-ii
</pre>

== Test Plan ==

'''UI and Manual Testing:'''

Steps:
Login as Instructor -
<pre>
username: instructor6
password: password
</pre>
1. Create an assignment and make sure it currently has its 'Review' phase going on.

2. Add participants to the assignment and remember their names or ids.

3. Logout

Login as Student who is added to the assignment -
<pre>
username: studentXXXX
password: password
</pre>
1. Go to the newly added assignment in your pending tasks(the pending task should be that of reviewing).

2. Ask for a team to review.

3. Go to each link submitted by this team and review it. If needed, note down the time spent on each link.

4. Logout.

Login as Instructor -
<pre>
username: instructor6
password: password
</pre>
1. Navigate to the 'Review Report' page of the assignment.

2. Search for the above student in the table.

3. Click on the link named 'Review time spent on task' below the student name.

Expected - A new column should be added to the table with the information regarding the reviewed team and the time spent per link and in total.

CSC/ECE 517 Fall 2018/E1872 Track Time Students Look At Other Submissions

2018-12-07T05:24:39Z

Nuachary: /* Objective of project */

'''
== Introduction ==

'''

The expertiza project takes advantage of peer-review among students to allow them to learn from each other. To track the review time that each student spend on each submitted resources is meaningful for instructors to study and improve the teaching experience. The previous team working on the project has solved part of such problems by tracking the active time of windows opened from the submitted links by till the window is closed or gives a periodic pop up to ask if the user is still reviewing. And thus records the end time. It is done using mature third-party APIs to record link review time.

In this project, we require to conglomerate the details of each review given by a student on the existing Review Report page.
This will ease the task for the instructor to get the insights of a review on one single page in order to grade the student based on his/her review.

To accomplish this goal, here are the general solutions designed and implemented in this project:

* Designed and implemented toggle view component using Javascript and Ruby to open students’ reviews inside the review report table

* Used DOM to calculate and display the total time spent on the review per round.

* Modify Review report (views/review_mapping/_review_report.html.erb) to show the total and detailed time spent on each review submissions.

'''

== Flowchart ==

[[File:E1791_niharika.png]]

== Objective of project ==

'''Objective 1:'''

The details of time spent on every assignment is displayed separately on the reviewer report page. As this is inconvenient we have to display all the statistics on the review report page.

'''Proposed Solution:'''

* We have added a link below the student ID in the first column of the review report page for each assignment.
* This is a toggle-able link and is available to each student details uniquely as shows below:

[[File:Image_(4).png]]

* Clicking on the link will toggle between showing/hiding a new column containing the review details to the table.

[[File:Image_(1).png]]

* The table contains the details regarding the team reviewed, round number of the review, total time spent on reviewing and time spent reviewing each link in the submission.

[[File:Image_(3).png]]

Files needed to be changed:

review_mapping/_review_report.html.erb

[[File:Review_time_flowchart_(1).png]]

== Design ==
'''Files Changed:'''

review_mapping/_review_report.html.erb -
This is the file for the review report. We have added the functionality of a toggle link below each student id in the first column. Clicking on this link will display the details of the reviews done by this student. On clicking again the details will disappear, giving the user the flexibility of viewing these details if need be.
The design makes use of the following models:
* Participant
* ResponseMap
* ResponseTime
* Assignment
* Team

First we fetch all the reviews done by the student by providing the user_id of the student to Participant which gives us the set of reviews done by that user. Then we iterate through these reviews. As reviews are based on the number of review rounds in the Assignment, we fetch the total number of review rounds for the current assignment from the Assignment model by fetching the current Assignment object using assignment id and then accessing the 'round_of_reviews' property of the object. The details of each review like the reviewer_id, reviewee_id , reviewed_object_id is stored in the ResponseMap model. We fetch the ResponseMap set for each such review from the ResponseMap by giving it reviewer_id and reviewed_object_id as the assignment id.
Now we iterate through this set of ResponseMaps. The data for the link reviewed and the time taken for each link is in ResponseTime model which is linked to the ResponseMap through map_id. We make use of this and for each ResponseMap we put in a loop to get all possible ResponseTime for every link reviewed by the student. Finally we display this whole thing in the form of a table with the headers:
* Team Reviewed : This is the team reviewed by the student. We get the team name by passing reviewee_id found in each ResponseMap to the Team model.
* Total Time(mins) : This is the total time spent by the student in reviewing this team. We have written custom Javascript functions to calculate total time by adding time spent on individual links.
* Round : This is the review round number for which this review has been performed.
* Links : This will give you a list of links one after the other which the student has reviewed. These links are found as entries in the ResponseTime model with other information as well.
* Time spent per link (mins) : This is the time spent in reviewing each link. Again we have written functions in embedded Ruby to calculate time in mins using the start and end times of reviewing this link.

'''Algorithm:'''
<pre>
1.Fetch all reviews of student from Participant by providing user_id of student

2.For a review in the reviews list do

a. Fetch all response maps associations by providing reviewer_id as review.id and reviewed_object_id as the Assignment.id

b.Fetch the number of review rounds needed by the assignment from Assignment model

c.For each response map in the response map list do

i. For each round from 1 to number of rounds do

1. Initialize map_total_time=0

2. Fetch the response time set from ResponseTime model by providing map_id as map.id and round number

3. Initialize a count variable which will keep count of links. count = 0.

4. For each link entry in the response time set do

a. If current link is the first link being considered do

i. Print team being reviewed name using Team model and id as reviewee_id

ii. Keep an empty space with id as map.id+””+roundNumber for uniqueness

iii. Print the round

b. Else

i. Print an empty space

ii. Print an empty space

iii. Print an empty space

c. Get the time spent on the link by subtracting start time and end time. Convert the time to mins by dividing by 60.

d. Add it to map_total_time which keeps tab of sum of time spent on all links

e. Print link time

5. Increment count

6. Set the value of map_total_time in the block with id=map.id+roundNumber using innerHtml in 4-a-ii
</pre>

== Test Plan ==

'''UI and Manual Testing:'''

Steps:
Login as Instructor -
<pre>
username: instructor6
password: password
</pre>
1. Create an assignment and make sure it currently has its 'Review' phase going on.

2. Add participants to the assignment and remember their names or ids.

3. Logout

Login as Student who is added to the assignment -
<pre>
username: studentXXXX
password: password
</pre>
1. Go to the newly added assignment in your pending tasks(the pending task should be that of reviewing).

2. Ask for a team to review.

3. Go to each link submitted by this team and review it. If needed, note down the time spent on each link.

4. Logout.

Login as Instructor -
<pre>
username: instructor6
password: password
</pre>
1. Navigate to the 'Review Report' page of the assignment.

2. Search for the above student in the table.

3. Click on the link named 'Review time spent on task' below the student name.

Expected - A new column should be added to the table with the information regarding the reviewed team and the time spent per link and in total.

CSC/ECE 517 Fall 2018/E1872 Track Time Students Look At Other Submissions

2018-12-07T05:23:37Z

Nuachary: /* Objective of project */

'''
== Introduction ==

'''

The expertiza project takes advantage of peer-review among students to allow them to learn from each other. To track the review time that each student spend on each submitted resources is meaningful for instructors to study and improve the teaching experience. The previous team working on the project has solved part of such problems by tracking the active time of windows opened from the submitted links by till the window is closed or gives a periodic pop up to ask if the user is still reviewing. And thus records the end time. It is done using mature third-party APIs to record link review time.

In this project, we require to conglomerate the details of each review given by a student on the existing Review Report page.
This will ease the task for the instructor to get the insights of a review on one single page in order to grade the student based on his/her review.

To accomplish this goal, here are the general solutions designed and implemented in this project:

* Designed and implemented toggle view component using Javascript and Ruby to open students’ reviews inside the review report table

* Used DOM to calculate and display the total time spent on the review per round.

* Modify Review report (views/review_mapping/_review_report.html.erb) to show the total and detailed time spent on each review submissions.

'''

== Flowchart ==

[[File:E1791_niharika.png]]

== Objective of project ==

'''Objective 1:'''

The details of time spent on every assignment is displayed separately on the reviewer report page. As this is inconvenient we have to display all the statistics on the review report page.

'''Proposed Solution:'''

* We have added a link below the student ID in the first column of the review report page for each assignment.
* This is a toggle-able link and is available to each student details uniquely as shows below:

[[File:Image_(4).png]]
[[File:Image_(3).png]]
[[File:Image_(1).png]]

<snap for per student>

* Clicking on the link will toggle between showing/hiding a new column containing the review details to the table.
* The table contains the details regarding the team reviewed, round number of the review, total time spent on reviewing and time spent reviewing each link in the submission.

<snap for response time table>

Files needed to be changed:

review_mapping/_review_report.html.erb

[[File:Review_time_flowchart_(1).png]]

== Design ==
'''Files Changed:'''

review_mapping/_review_report.html.erb -
This is the file for the review report. We have added the functionality of a toggle link below each student id in the first column. Clicking on this link will display the details of the reviews done by this student. On clicking again the details will disappear, giving the user the flexibility of viewing these details if need be.
The design makes use of the following models:
* Participant
* ResponseMap
* ResponseTime
* Assignment
* Team

First we fetch all the reviews done by the student by providing the user_id of the student to Participant which gives us the set of reviews done by that user. Then we iterate through these reviews. As reviews are based on the number of review rounds in the Assignment, we fetch the total number of review rounds for the current assignment from the Assignment model by fetching the current Assignment object using assignment id and then accessing the 'round_of_reviews' property of the object. The details of each review like the reviewer_id, reviewee_id , reviewed_object_id is stored in the ResponseMap model. We fetch the ResponseMap set for each such review from the ResponseMap by giving it reviewer_id and reviewed_object_id as the assignment id.
Now we iterate through this set of ResponseMaps. The data for the link reviewed and the time taken for each link is in ResponseTime model which is linked to the ResponseMap through map_id. We make use of this and for each ResponseMap we put in a loop to get all possible ResponseTime for every link reviewed by the student. Finally we display this whole thing in the form of a table with the headers:
* Team Reviewed : This is the team reviewed by the student. We get the team name by passing reviewee_id found in each ResponseMap to the Team model.
* Total Time(mins) : This is the total time spent by the student in reviewing this team. We have written custom Javascript functions to calculate total time by adding time spent on individual links.
* Round : This is the review round number for which this review has been performed.
* Links : This will give you a list of links one after the other which the student has reviewed. These links are found as entries in the ResponseTime model with other information as well.
* Time spent per link (mins) : This is the time spent in reviewing each link. Again we have written functions in embedded Ruby to calculate time in mins using the start and end times of reviewing this link.

'''Algorithm:'''
<pre>
1.Fetch all reviews of student from Participant by providing user_id of student

2.For a review in the reviews list do

a. Fetch all response maps associations by providing reviewer_id as review.id and reviewed_object_id as the Assignment.id

b.Fetch the number of review rounds needed by the assignment from Assignment model

c.For each response map in the response map list do

i. For each round from 1 to number of rounds do

1. Initialize map_total_time=0

2. Fetch the response time set from ResponseTime model by providing map_id as map.id and round number

3. Initialize a count variable which will keep count of links. count = 0.

4. For each link entry in the response time set do

a. If current link is the first link being considered do

i. Print team being reviewed name using Team model and id as reviewee_id

ii. Keep an empty space with id as map.id+””+roundNumber for uniqueness

iii. Print the round

b. Else

i. Print an empty space

ii. Print an empty space

iii. Print an empty space

c. Get the time spent on the link by subtracting start time and end time. Convert the time to mins by dividing by 60.

d. Add it to map_total_time which keeps tab of sum of time spent on all links

e. Print link time

5. Increment count

6. Set the value of map_total_time in the block with id=map.id+roundNumber using innerHtml in 4-a-ii
</pre>

== Test Plan ==

'''UI and Manual Testing:'''

Steps:
Login as Instructor -
<pre>
username: instructor6
password: password
</pre>
1. Create an assignment and make sure it currently has its 'Review' phase going on.

2. Add participants to the assignment and remember their names or ids.

3. Logout

Login as Student who is added to the assignment -
<pre>
username: studentXXXX
password: password
</pre>
1. Go to the newly added assignment in your pending tasks(the pending task should be that of reviewing).

2. Ask for a team to review.

3. Go to each link submitted by this team and review it. If needed, note down the time spent on each link.

4. Logout.

Login as Instructor -
<pre>
username: instructor6
password: password
</pre>
1. Navigate to the 'Review Report' page of the assignment.

2. Search for the above student in the table.

3. Click on the link named 'Review time spent on task' below the student name.

Expected - A new column should be added to the table with the information regarding the reviewed team and the time spent per link and in total.

CSC/ECE 517 Fall 2018/E1872 Track Time Students Look At Other Submissions

2018-12-07T05:23:17Z

Nuachary: /* Objective of project */

'''
== Introduction ==

'''

The expertiza project takes advantage of peer-review among students to allow them to learn from each other. To track the review time that each student spend on each submitted resources is meaningful for instructors to study and improve the teaching experience. The previous team working on the project has solved part of such problems by tracking the active time of windows opened from the submitted links by till the window is closed or gives a periodic pop up to ask if the user is still reviewing. And thus records the end time. It is done using mature third-party APIs to record link review time.

In this project, we require to conglomerate the details of each review given by a student on the existing Review Report page.
This will ease the task for the instructor to get the insights of a review on one single page in order to grade the student based on his/her review.

To accomplish this goal, here are the general solutions designed and implemented in this project:

* Designed and implemented toggle view component using Javascript and Ruby to open students’ reviews inside the review report table

* Used DOM to calculate and display the total time spent on the review per round.

* Modify Review report (views/review_mapping/_review_report.html.erb) to show the total and detailed time spent on each review submissions.

'''

== Flowchart ==

[[File:E1791_niharika.png]]

== Objective of project ==

'''Objective 1:'''

The details of time spent on every assignment is displayed separately on the reviewer report page. As this is inconvenient we have to display all the statistics on the review report page.

'''Proposed Solution:'''

* We have added a link below the student ID in the first column of the review report page for each assignment.
* This is a toggle-able link and is available to each student details uniquely as shows below:

[[File:Image_(3).png]]
[[File:Image_(1).png]]

<snap for per student>

* Clicking on the link will toggle between showing/hiding a new column containing the review details to the table.
* The table contains the details regarding the team reviewed, round number of the review, total time spent on reviewing and time spent reviewing each link in the submission.

<snap for response time table>

Files needed to be changed:

review_mapping/_review_report.html.erb

[[File:Review_time_flowchart_(1).png]]

== Design ==
'''Files Changed:'''

review_mapping/_review_report.html.erb -
This is the file for the review report. We have added the functionality of a toggle link below each student id in the first column. Clicking on this link will display the details of the reviews done by this student. On clicking again the details will disappear, giving the user the flexibility of viewing these details if need be.
The design makes use of the following models:
* Participant
* ResponseMap
* ResponseTime
* Assignment
* Team

First we fetch all the reviews done by the student by providing the user_id of the student to Participant which gives us the set of reviews done by that user. Then we iterate through these reviews. As reviews are based on the number of review rounds in the Assignment, we fetch the total number of review rounds for the current assignment from the Assignment model by fetching the current Assignment object using assignment id and then accessing the 'round_of_reviews' property of the object. The details of each review like the reviewer_id, reviewee_id , reviewed_object_id is stored in the ResponseMap model. We fetch the ResponseMap set for each such review from the ResponseMap by giving it reviewer_id and reviewed_object_id as the assignment id.
Now we iterate through this set of ResponseMaps. The data for the link reviewed and the time taken for each link is in ResponseTime model which is linked to the ResponseMap through map_id. We make use of this and for each ResponseMap we put in a loop to get all possible ResponseTime for every link reviewed by the student. Finally we display this whole thing in the form of a table with the headers:
* Team Reviewed : This is the team reviewed by the student. We get the team name by passing reviewee_id found in each ResponseMap to the Team model.
* Total Time(mins) : This is the total time spent by the student in reviewing this team. We have written custom Javascript functions to calculate total time by adding time spent on individual links.
* Round : This is the review round number for which this review has been performed.
* Links : This will give you a list of links one after the other which the student has reviewed. These links are found as entries in the ResponseTime model with other information as well.
* Time spent per link (mins) : This is the time spent in reviewing each link. Again we have written functions in embedded Ruby to calculate time in mins using the start and end times of reviewing this link.

'''Algorithm:'''
<pre>
1.Fetch all reviews of student from Participant by providing user_id of student

2.For a review in the reviews list do

a. Fetch all response maps associations by providing reviewer_id as review.id and reviewed_object_id as the Assignment.id

b.Fetch the number of review rounds needed by the assignment from Assignment model

c.For each response map in the response map list do

i. For each round from 1 to number of rounds do

1. Initialize map_total_time=0

2. Fetch the response time set from ResponseTime model by providing map_id as map.id and round number

3. Initialize a count variable which will keep count of links. count = 0.

4. For each link entry in the response time set do

a. If current link is the first link being considered do

i. Print team being reviewed name using Team model and id as reviewee_id

ii. Keep an empty space with id as map.id+””+roundNumber for uniqueness

iii. Print the round

b. Else

i. Print an empty space

ii. Print an empty space

iii. Print an empty space

c. Get the time spent on the link by subtracting start time and end time. Convert the time to mins by dividing by 60.

d. Add it to map_total_time which keeps tab of sum of time spent on all links

e. Print link time

5. Increment count

6. Set the value of map_total_time in the block with id=map.id+roundNumber using innerHtml in 4-a-ii
</pre>

== Test Plan ==

'''UI and Manual Testing:'''

Steps:
Login as Instructor -
<pre>
username: instructor6
password: password
</pre>
1. Create an assignment and make sure it currently has its 'Review' phase going on.

2. Add participants to the assignment and remember their names or ids.

3. Logout

Login as Student who is added to the assignment -
<pre>
username: studentXXXX
password: password
</pre>
1. Go to the newly added assignment in your pending tasks(the pending task should be that of reviewing).

2. Ask for a team to review.

3. Go to each link submitted by this team and review it. If needed, note down the time spent on each link.

4. Logout.

Login as Instructor -
<pre>
username: instructor6
password: password
</pre>
1. Navigate to the 'Review Report' page of the assignment.

2. Search for the above student in the table.

3. Click on the link named 'Review time spent on task' below the student name.

Expected - A new column should be added to the table with the information regarding the reviewed team and the time spent per link and in total.

CSC/ECE 517 Fall 2018/E1872 Track Time Students Look At Other Submissions

2018-12-07T05:23:01Z

Nuachary: /* Objective of project */

'''
== Introduction ==

'''

The expertiza project takes advantage of peer-review among students to allow them to learn from each other. To track the review time that each student spend on each submitted resources is meaningful for instructors to study and improve the teaching experience. The previous team working on the project has solved part of such problems by tracking the active time of windows opened from the submitted links by till the window is closed or gives a periodic pop up to ask if the user is still reviewing. And thus records the end time. It is done using mature third-party APIs to record link review time.

In this project, we require to conglomerate the details of each review given by a student on the existing Review Report page.
This will ease the task for the instructor to get the insights of a review on one single page in order to grade the student based on his/her review.

To accomplish this goal, here are the general solutions designed and implemented in this project:

* Designed and implemented toggle view component using Javascript and Ruby to open students’ reviews inside the review report table

* Used DOM to calculate and display the total time spent on the review per round.

* Modify Review report (views/review_mapping/_review_report.html.erb) to show the total and detailed time spent on each review submissions.

'''

== Flowchart ==

[[File:E1791_niharika.png]]

== Objective of project ==

'''Objective 1:'''

The details of time spent on every assignment is displayed separately on the reviewer report page. As this is inconvenient we have to display all the statistics on the review report page.

'''Proposed Solution:'''

* We have added a link below the student ID in the first column of the review report page for each assignment.
* This is a toggle-able link and is available to each student details uniquely as shows below:

[[File:Image_(2).png]]
[[File:Image_(1).png]]

<snap for per student>

* Clicking on the link will toggle between showing/hiding a new column containing the review details to the table.
* The table contains the details regarding the team reviewed, round number of the review, total time spent on reviewing and time spent reviewing each link in the submission.

<snap for response time table>

Files needed to be changed:

review_mapping/_review_report.html.erb

[[File:Review_time_flowchart_(1).png]]

== Design ==
'''Files Changed:'''

review_mapping/_review_report.html.erb -
This is the file for the review report. We have added the functionality of a toggle link below each student id in the first column. Clicking on this link will display the details of the reviews done by this student. On clicking again the details will disappear, giving the user the flexibility of viewing these details if need be.
The design makes use of the following models:
* Participant
* ResponseMap
* ResponseTime
* Assignment
* Team

First we fetch all the reviews done by the student by providing the user_id of the student to Participant which gives us the set of reviews done by that user. Then we iterate through these reviews. As reviews are based on the number of review rounds in the Assignment, we fetch the total number of review rounds for the current assignment from the Assignment model by fetching the current Assignment object using assignment id and then accessing the 'round_of_reviews' property of the object. The details of each review like the reviewer_id, reviewee_id , reviewed_object_id is stored in the ResponseMap model. We fetch the ResponseMap set for each such review from the ResponseMap by giving it reviewer_id and reviewed_object_id as the assignment id.
Now we iterate through this set of ResponseMaps. The data for the link reviewed and the time taken for each link is in ResponseTime model which is linked to the ResponseMap through map_id. We make use of this and for each ResponseMap we put in a loop to get all possible ResponseTime for every link reviewed by the student. Finally we display this whole thing in the form of a table with the headers:
* Team Reviewed : This is the team reviewed by the student. We get the team name by passing reviewee_id found in each ResponseMap to the Team model.
* Total Time(mins) : This is the total time spent by the student in reviewing this team. We have written custom Javascript functions to calculate total time by adding time spent on individual links.
* Round : This is the review round number for which this review has been performed.
* Links : This will give you a list of links one after the other which the student has reviewed. These links are found as entries in the ResponseTime model with other information as well.
* Time spent per link (mins) : This is the time spent in reviewing each link. Again we have written functions in embedded Ruby to calculate time in mins using the start and end times of reviewing this link.

'''Algorithm:'''
<pre>
1.Fetch all reviews of student from Participant by providing user_id of student

2.For a review in the reviews list do

a. Fetch all response maps associations by providing reviewer_id as review.id and reviewed_object_id as the Assignment.id

b.Fetch the number of review rounds needed by the assignment from Assignment model

c.For each response map in the response map list do

i. For each round from 1 to number of rounds do

1. Initialize map_total_time=0

2. Fetch the response time set from ResponseTime model by providing map_id as map.id and round number

3. Initialize a count variable which will keep count of links. count = 0.

4. For each link entry in the response time set do

a. If current link is the first link being considered do

i. Print team being reviewed name using Team model and id as reviewee_id

ii. Keep an empty space with id as map.id+””+roundNumber for uniqueness

iii. Print the round

b. Else

i. Print an empty space

ii. Print an empty space

iii. Print an empty space

c. Get the time spent on the link by subtracting start time and end time. Convert the time to mins by dividing by 60.

d. Add it to map_total_time which keeps tab of sum of time spent on all links

e. Print link time

5. Increment count

6. Set the value of map_total_time in the block with id=map.id+roundNumber using innerHtml in 4-a-ii
</pre>

== Test Plan ==

'''UI and Manual Testing:'''

Steps:
Login as Instructor -
<pre>
username: instructor6
password: password
</pre>
1. Create an assignment and make sure it currently has its 'Review' phase going on.

2. Add participants to the assignment and remember their names or ids.

3. Logout

Login as Student who is added to the assignment -
<pre>
username: studentXXXX
password: password
</pre>
1. Go to the newly added assignment in your pending tasks(the pending task should be that of reviewing).

2. Ask for a team to review.

3. Go to each link submitted by this team and review it. If needed, note down the time spent on each link.

4. Logout.

Login as Instructor -
<pre>
username: instructor6
password: password
</pre>
1. Navigate to the 'Review Report' page of the assignment.

2. Search for the above student in the table.

3. Click on the link named 'Review time spent on task' below the student name.

Expected - A new column should be added to the table with the information regarding the reviewed team and the time spent per link and in total.

CSC/ECE 517 Fall 2018/E1872 Track Time Students Look At Other Submissions

2018-12-07T05:21:44Z

Nuachary: /* Objective of project */

'''
== Introduction ==

'''

The expertiza project takes advantage of peer-review among students to allow them to learn from each other. To track the review time that each student spend on each submitted resources is meaningful for instructors to study and improve the teaching experience. The previous team working on the project has solved part of such problems by tracking the active time of windows opened from the submitted links by till the window is closed or gives a periodic pop up to ask if the user is still reviewing. And thus records the end time. It is done using mature third-party APIs to record link review time.

In this project, we require to conglomerate the details of each review given by a student on the existing Review Report page.
This will ease the task for the instructor to get the insights of a review on one single page in order to grade the student based on his/her review.

To accomplish this goal, here are the general solutions designed and implemented in this project:

* Designed and implemented toggle view component using Javascript and Ruby to open students’ reviews inside the review report table

* Used DOM to calculate and display the total time spent on the review per round.

* Modify Review report (views/review_mapping/_review_report.html.erb) to show the total and detailed time spent on each review submissions.

'''

== Flowchart ==

[[File:E1791_niharika.png]]

== Objective of project ==

'''Objective 1:'''

The details of time spent on every assignment is displayed separately on the reviewer report page. As this is inconvenient we have to display all the statistics on the review report page.

'''Proposed Solution:'''

* We have added a link below the student ID in the first column of the review report page for each assignment.
* This is a toggle-able link and is available to each student details uniquely as shows below:

[[File:Image_(1).png]]

<snap for per student>

* Clicking on the link will toggle between showing/hiding a new column containing the review details to the table.
* The table contains the details regarding the team reviewed, round number of the review, total time spent on reviewing and time spent reviewing each link in the submission.

<snap for response time table>

Files needed to be changed:

review_mapping/_review_report.html.erb

[[File:Review_time_flowchart_(1).png]]

== Design ==
'''Files Changed:'''

review_mapping/_review_report.html.erb -
This is the file for the review report. We have added the functionality of a toggle link below each student id in the first column. Clicking on this link will display the details of the reviews done by this student. On clicking again the details will disappear, giving the user the flexibility of viewing these details if need be.
The design makes use of the following models:
* Participant
* ResponseMap
* ResponseTime
* Assignment
* Team

First we fetch all the reviews done by the student by providing the user_id of the student to Participant which gives us the set of reviews done by that user. Then we iterate through these reviews. As reviews are based on the number of review rounds in the Assignment, we fetch the total number of review rounds for the current assignment from the Assignment model by fetching the current Assignment object using assignment id and then accessing the 'round_of_reviews' property of the object. The details of each review like the reviewer_id, reviewee_id , reviewed_object_id is stored in the ResponseMap model. We fetch the ResponseMap set for each such review from the ResponseMap by giving it reviewer_id and reviewed_object_id as the assignment id.
Now we iterate through this set of ResponseMaps. The data for the link reviewed and the time taken for each link is in ResponseTime model which is linked to the ResponseMap through map_id. We make use of this and for each ResponseMap we put in a loop to get all possible ResponseTime for every link reviewed by the student. Finally we display this whole thing in the form of a table with the headers:
* Team Reviewed : This is the team reviewed by the student. We get the team name by passing reviewee_id found in each ResponseMap to the Team model.
* Total Time(mins) : This is the total time spent by the student in reviewing this team. We have written custom Javascript functions to calculate total time by adding time spent on individual links.
* Round : This is the review round number for which this review has been performed.
* Links : This will give you a list of links one after the other which the student has reviewed. These links are found as entries in the ResponseTime model with other information as well.
* Time spent per link (mins) : This is the time spent in reviewing each link. Again we have written functions in embedded Ruby to calculate time in mins using the start and end times of reviewing this link.

'''Algorithm:'''
<pre>
1.Fetch all reviews of student from Participant by providing user_id of student

2.For a review in the reviews list do

a. Fetch all response maps associations by providing reviewer_id as review.id and reviewed_object_id as the Assignment.id

b.Fetch the number of review rounds needed by the assignment from Assignment model

c.For each response map in the response map list do

i. For each round from 1 to number of rounds do

1. Initialize map_total_time=0

2. Fetch the response time set from ResponseTime model by providing map_id as map.id and round number

3. Initialize a count variable which will keep count of links. count = 0.

4. For each link entry in the response time set do

a. If current link is the first link being considered do

i. Print team being reviewed name using Team model and id as reviewee_id

ii. Keep an empty space with id as map.id+””+roundNumber for uniqueness

iii. Print the round

b. Else

i. Print an empty space

ii. Print an empty space

iii. Print an empty space

c. Get the time spent on the link by subtracting start time and end time. Convert the time to mins by dividing by 60.

d. Add it to map_total_time which keeps tab of sum of time spent on all links

e. Print link time

5. Increment count

6. Set the value of map_total_time in the block with id=map.id+roundNumber using innerHtml in 4-a-ii
</pre>

== Test Plan ==

'''UI and Manual Testing:'''

Steps:
Login as Instructor -
<pre>
username: instructor6
password: password
</pre>
1. Create an assignment and make sure it currently has its 'Review' phase going on.

2. Add participants to the assignment and remember their names or ids.

3. Logout

Login as Student who is added to the assignment -
<pre>
username: studentXXXX
password: password
</pre>
1. Go to the newly added assignment in your pending tasks(the pending task should be that of reviewing).

2. Ask for a team to review.

3. Go to each link submitted by this team and review it. If needed, note down the time spent on each link.

4. Logout.

Login as Instructor -
<pre>
username: instructor6
password: password
</pre>
1. Navigate to the 'Review Report' page of the assignment.

2. Search for the above student in the table.

3. Click on the link named 'Review time spent on task' below the student name.

Expected - A new column should be added to the table with the information regarding the reviewed team and the time spent per link and in total.

CSC/ECE 517 Fall 2018/E1872 Track Time Students Look At Other Submissions

2018-12-07T05:21:31Z

Nuachary: /* Objective of project */

'''
== Introduction ==

'''

The expertiza project takes advantage of peer-review among students to allow them to learn from each other. To track the review time that each student spend on each submitted resources is meaningful for instructors to study and improve the teaching experience. The previous team working on the project has solved part of such problems by tracking the active time of windows opened from the submitted links by till the window is closed or gives a periodic pop up to ask if the user is still reviewing. And thus records the end time. It is done using mature third-party APIs to record link review time.

In this project, we require to conglomerate the details of each review given by a student on the existing Review Report page.
This will ease the task for the instructor to get the insights of a review on one single page in order to grade the student based on his/her review.

To accomplish this goal, here are the general solutions designed and implemented in this project:

* Designed and implemented toggle view component using Javascript and Ruby to open students’ reviews inside the review report table

* Used DOM to calculate and display the total time spent on the review per round.

* Modify Review report (views/review_mapping/_review_report.html.erb) to show the total and detailed time spent on each review submissions.

'''

== Flowchart ==

[[File:E1791_niharika.png]]

== Objective of project ==

'''Objective 1:'''

The details of time spent on every assignment is displayed separately on the reviewer report page. As this is inconvenient we have to display all the statistics on the review report page.

'''Proposed Solution:'''

* We have added a link below the student ID in the first column of the review report page for each assignment.
* This is a toggle-able link and is available to each student details uniquely as shows below:

[[File:Image_(1).png.png]]

<snap for per student>

* Clicking on the link will toggle between showing/hiding a new column containing the review details to the table.
* The table contains the details regarding the team reviewed, round number of the review, total time spent on reviewing and time spent reviewing each link in the submission.

<snap for response time table>

Files needed to be changed:

review_mapping/_review_report.html.erb

[[File:Review_time_flowchart_(1).png]]

== Design ==
'''Files Changed:'''

review_mapping/_review_report.html.erb -
This is the file for the review report. We have added the functionality of a toggle link below each student id in the first column. Clicking on this link will display the details of the reviews done by this student. On clicking again the details will disappear, giving the user the flexibility of viewing these details if need be.
The design makes use of the following models:
* Participant
* ResponseMap
* ResponseTime
* Assignment
* Team

First we fetch all the reviews done by the student by providing the user_id of the student to Participant which gives us the set of reviews done by that user. Then we iterate through these reviews. As reviews are based on the number of review rounds in the Assignment, we fetch the total number of review rounds for the current assignment from the Assignment model by fetching the current Assignment object using assignment id and then accessing the 'round_of_reviews' property of the object. The details of each review like the reviewer_id, reviewee_id , reviewed_object_id is stored in the ResponseMap model. We fetch the ResponseMap set for each such review from the ResponseMap by giving it reviewer_id and reviewed_object_id as the assignment id.
Now we iterate through this set of ResponseMaps. The data for the link reviewed and the time taken for each link is in ResponseTime model which is linked to the ResponseMap through map_id. We make use of this and for each ResponseMap we put in a loop to get all possible ResponseTime for every link reviewed by the student. Finally we display this whole thing in the form of a table with the headers:
* Team Reviewed : This is the team reviewed by the student. We get the team name by passing reviewee_id found in each ResponseMap to the Team model.
* Total Time(mins) : This is the total time spent by the student in reviewing this team. We have written custom Javascript functions to calculate total time by adding time spent on individual links.
* Round : This is the review round number for which this review has been performed.
* Links : This will give you a list of links one after the other which the student has reviewed. These links are found as entries in the ResponseTime model with other information as well.
* Time spent per link (mins) : This is the time spent in reviewing each link. Again we have written functions in embedded Ruby to calculate time in mins using the start and end times of reviewing this link.

'''Algorithm:'''
<pre>
1.Fetch all reviews of student from Participant by providing user_id of student

2.For a review in the reviews list do

a. Fetch all response maps associations by providing reviewer_id as review.id and reviewed_object_id as the Assignment.id

b.Fetch the number of review rounds needed by the assignment from Assignment model

c.For each response map in the response map list do

i. For each round from 1 to number of rounds do

1. Initialize map_total_time=0

2. Fetch the response time set from ResponseTime model by providing map_id as map.id and round number

3. Initialize a count variable which will keep count of links. count = 0.

4. For each link entry in the response time set do

a. If current link is the first link being considered do

i. Print team being reviewed name using Team model and id as reviewee_id

ii. Keep an empty space with id as map.id+””+roundNumber for uniqueness

iii. Print the round

b. Else

i. Print an empty space

ii. Print an empty space

iii. Print an empty space

c. Get the time spent on the link by subtracting start time and end time. Convert the time to mins by dividing by 60.

d. Add it to map_total_time which keeps tab of sum of time spent on all links

e. Print link time

5. Increment count

6. Set the value of map_total_time in the block with id=map.id+roundNumber using innerHtml in 4-a-ii
</pre>

== Test Plan ==

'''UI and Manual Testing:'''

Steps:
Login as Instructor -
<pre>
username: instructor6
password: password
</pre>
1. Create an assignment and make sure it currently has its 'Review' phase going on.

2. Add participants to the assignment and remember their names or ids.

3. Logout

Login as Student who is added to the assignment -
<pre>
username: studentXXXX
password: password
</pre>
1. Go to the newly added assignment in your pending tasks(the pending task should be that of reviewing).

2. Ask for a team to review.

3. Go to each link submitted by this team and review it. If needed, note down the time spent on each link.

4. Logout.

Login as Instructor -
<pre>
username: instructor6
password: password
</pre>
1. Navigate to the 'Review Report' page of the assignment.

2. Search for the above student in the table.

3. Click on the link named 'Review time spent on task' below the student name.

Expected - A new column should be added to the table with the information regarding the reviewed team and the time spent per link and in total.

CSC/ECE 517 Fall 2018/E1872 Track Time Students Look At Other Submissions

2018-12-06T21:24:43Z

Nuachary: /* Objective of project */

File:Image (1).png

2018-12-06T19:45:20Z

Nuachary:

File:Image (3).png

2018-12-06T19:45:09Z

Nuachary:

File:Image (4).png

2018-12-06T19:44:55Z

Nuachary:

CSC/ECE 517 Fall 2018/E1872 Track Time Students Look At Other Submissions

2018-12-06T19:26:26Z

Nuachary: /* Objective of project */

CSC/ECE 517 Fall 2018/E1872 Track Time Students Look At Other Submissions

2018-12-06T19:22:51Z

Nuachary: /* Objective of project */

CSC/ECE 517 Fall 2018/E1872 Track Time Students Look At Other Submissions

2018-12-06T18:56:07Z

Nuachary: /* Objective of project */

CSC/ECE 517 Fall 2018/E1872 Track Time Students Look At Other Submissions

2018-12-06T18:32:19Z

Nuachary: /* Objective of project */

CSC/ECE 517 Fall 2018/E1872 Track Time Students Look At Other Submissions

2018-12-06T18:28:35Z

Nuachary: /* Objective of project */

CSC/ECE 517 Fall 2018/E1872 Track Time Students Look At Other Submissions

2018-12-06T18:28:17Z

Nuachary: /* Flowchart: */

CSC/ECE 517 Fall 2018/E1872 Track Time Students Look At Other Submissions

2018-12-06T18:28:01Z

Nuachary: /* Flowchart: */

File:Review time flowchart (1).png

2018-12-06T18:25:55Z

Nuachary:

CSC/ECE 517 Fall 2018/E1872 Track Time Students Look At Other Submissions

2018-12-06T18:23:52Z

Nuachary: /* Flowchart: */

File:Niharika8915 img2.png

2018-12-06T18:22:18Z

Nuachary:

CSC/ECE 517 Fall 2018/E1872 Track Time Students Look At Other Submissions

2018-12-06T18:21:04Z

Nuachary: /* Objective of project */

CSC/ECE 517 Fall 2018/E1872 Track Time Students Look At Other Submissions

2018-12-06T18:20:18Z

Nuachary: /* Objective of project */

File:Review time flowchart.png

2018-12-06T18:15:25Z

Nuachary:

CSC/ECE 517 Fall 2018/E1872 Track Time Students Look At Other Submissions

2018-11-14T00:25:33Z

Nuachary: /* Database schema design */

CSC/ECE 517 Fall 2018/E1872 Track Time Students Look At Other Submissions

2018-11-14T00:24:44Z

Nuachary: /* Database schema design */

CSC/ECE 517 Fall 2018/E1872 Track Time Students Look At Other Submissions

2018-11-14T00:24:13Z

Nuachary: /* Database schema design */

File:E1791 niharika.png

2018-11-14T00:21:59Z

Nuachary:

CSC/ECE 517 Fall 2018/E1872 Track Time Students Look At Other Submissions

2018-11-14T00:19:27Z

Nuachary: /* Database schema design */

CSC/ECE 517 Fall 2018/E1872 Track Time Students Look At Other Submissions

2018-11-14T00:18:22Z

Nuachary: /* Database schema design */

CSC/ECE 517 Fall 2018/E1872 Track Time Students Look At Other Submissions

2018-11-14T00:17:37Z

Nuachary: /* Database schema design */

CSC/ECE 517 Fall 2018/E1872 Track Time Students Look At Other Submissions

2018-11-14T00:17:11Z

Nuachary: /* Database schema design */

CSC/ECE 517 Fall 2018/E1872 Track Time Students Look At Other Submissions

2018-11-14T00:16:34Z

Nuachary: /* Database schema design */

CSC/ECE 517 Fall 2018/E1872 Track Time Students Look At Other Submissions

2018-11-14T00:15:49Z

Nuachary: /* Database schema design */

CSC/ECE 517 Fall 2018/E1872 Track Time Students Look At Other Submissions

2018-11-13T23:34:35Z

Nuachary: /* Database schema design */

CSC/ECE 517 Fall 2018/E1872 Track Time Students Look At Other Submissions

2018-11-13T23:09:44Z

Nuachary:

CSC/ECE 517 Fall 2018/E1872 Track Time Students Look At Other Submissions

2018-11-13T23:02:34Z

Nuachary:

'''Introduction'''
----

The expertiza project takes advantage of peer-review among students to allow them to learn from each other. To track the review time that each student spend on each submitted resources is meaningful for instructors to study and improve the teaching experience. The previous team working on the E1791 project has solved part of such problems by tracking the active time of windows opened from the submitted links by till the window is closed or gives a periodic pop up to ask if the user is still reviewing. And thus records the end time. It is done using mature third-party APIs to record link review time.

In this project, we require to autosave the reviews given timely to avoid re-writing of the reviews in case of erroneously closing the window.

Also, once the reviews are submitted, the review report page has a link to review details page which contains the above statistics. It becomes inconvenient to click on those links again and again to check the details. We will be merging the data of the details page on the current report page.

To accomplish this goal, here are the general solutions designed and implemented in this project:

* Designed a database schema for logging the time a reviewer spend on a submission

* Designed and implemented dynamic partial components using Javascript and Ruby to open students’ submissions in new windows to view online

* Used DOM to control the windows holding review submission files or links, and record the open and close time.

* Modify Review report (views/review_mapping/_review_report.html.erb) to show the total and detailed time spent on each review submissions with visualization.

'''Database schema design'''

For this project, the table submission_viewing_events stores all the time needed for each review submission event. The application records reviewer_id and
reviewee_id, source_link for submitted links or file names, as well as time start_at and end_at, then store them in the table.

[[File:E1791db_2018.jpg]]

CSC/ECE 517 Fall 2018/E1872 Track Time Students Look At Other Submissions

2018-11-13T23:00:57Z

Nuachary:

'''Introduction'''
----

The expertiza project takes advantage of peer-review among students to allow them to learn from each other. To track the review time that each student spend on each submitted resources is meaningful for instructors to study and improve the teaching experience. The previous team working on the E1791 project has solved part of such problems by tracking the active time of windows opened from the submitted links by till the window is closed or gives a periodic pop up to ask if the user is still reviewing. And thus records the end time. It is done using mature third-party APIs to record link review time.

In this project, we require to autosave the reviews given timely to avoid re-writing of the reviews in case of erroneously closing the window.

Also, once the reviews are submitted, the review report page has a link to review details page which contains the above statistics. It becomes inconvenient to click on those links again and again to check the details. We will be merging the data of the details page on the current report page.

To accomplish this goal, here are the general solutions designed and implemented in this project:

 Designed a database schema for logging the time a reviewer spend on a submission

 Designed and implemented dynamic partial components using Javascript and Ruby to open students’ submissions in new windows to view online

 Used DOM to control the windows holding review submission files or links, and record the open and close time.

 Modify Review report (views/review_mapping/_review_report.html.erb) to show the total and detailed time spent on each review submissions with visualization.

'''Database schema design'''

For this project, the table submission_viewing_events stores all the time needed for each review submission event. The application records reviewer_id and
reviewee_id, source_link for submitted links or file names, as well as time start_at and end_at, then store them in the table.

[[File:E1791db_2018.jpg]]

File:E1791db 2018.jpg

2018-11-13T22:58:01Z

Nuachary:

CSC/ECE 517 Fall 2018/E1872 Track Time Students Look At Other Submissions

2018-11-13T22:51:41Z

Nuachary:

'''Introduction'''
----

The expertiza project takes advantage of peer-review among students to allow them to learn from each other. To track the review time that each student spend on each submitted resources is meaningful for instructors to study and improve the teaching experience. The previous team working on the E1791 project has solved part of such problems by tracking the active time of windows opened from the submitted links by till the window is closed or gives a periodic pop up to ask if the user is still reviewing. And thus records the end time. It is done using mature third-party APIs to record link review time.

In this project, we require to autosave the reviews given timely to avoid re-writing of the reviews in case of erroneously closing the window.

Also, once the reviews are submitted, the review report page has a link to review details page which contains the above statistics. It becomes inconvenient to click on those links again and again to check the details. We will be merging the data of the details page on the current report page.

 Designed a database schema for logging the time a reviewer spend on a submission
----

 Designed and implemented dynamic partial components using Javascript and Ruby to open students’ submissions in new windows to view online
----

 Used DOM to control the windows holding review submission files or links, and record the open and close time.
----

 Modify Review report (views/review_mapping/_review_report.html.erb) to show the total and detailed time spent on each review submissions with visualization.
----

'''Database schema design'''

For this project, the table submission_viewing_events stores all the time needed for each review submission event. The application records reviewer_id and
reviewee_id, source_link for submitted links or file names, as well as time start_at and end_at, then store them in the table.

[[File:E1791db_Fall18.jpg]]

File:E1791 Fall18db.jpg

2018-11-13T22:49:08Z

Nuachary:

CSC/ECE 517 Fall 2018/E1872 Track Time Students Look At Other Submissions

2018-11-13T22:46:25Z

Nuachary:

Database shema design

For this project, the table submission_viewing_events stores all the time needed for each review submission event. The application records reviewer_id and
reviewee_id, source_link for submitted links or file names, as well as time start_at and end_at, then store them in the table.

CSC/ECE 517 Fall 2018/E1872 Track Time Students Look At Other Submissions

2018-11-13T22:46:11Z

Nuachary:

Database shcema design

For this project, the table submission_viewing_events stores all the time needed for each review submission event. The application records reviewer_id and
reviewee_id, source_link for submitted links or file names, as well as time start_at and end_at, then store them in the table.

CSC/ECE 517 Fall 2018/E1872 Track Time Students Look At Other Submissions

2018-11-13T22:45:46Z

Nuachary: Created page with "Database shcema design For this project, the table submission_viewing_events stores all the time needed for each review submission event. The application records reviewer_id an..."

Database shcema design

For this project, the table submission_viewing_events stores all the time needed for each review submission event. The application records reviewer_id and reviewee_id, source_link for submitted links or file names, as well as time start_at and end_at, then store them in the table.

E1838 Project Red

2018-11-09T23:59:12Z

Nuachary: /* Issue #391 */

==Introduction==
==='''Problem Statement'''===
In Expertiza, if the instructor doesn’t specify the assignment directory for a submission, the directory defaults to the home directory. This can lead to multiple assignment submissions being in the same place and creating confusion. The aim of the project if to handle all the scenarios that can arise when the instructor is not specifying any directory name.

=='''Issues to be fixed'''==

Issue #391: In Expertiza, if the instructor doesn’t specify the assignment directory for a submission, the directory defaults to the home directory. This can lead to multiple assignment submissions being in the same place and creating confusion. Please take a look at the Github issue for suggestions on how to solve this.

Issue #1190: An issue with conflicting directories for copied assignments was fixed. You need to write the test to verify that this issue doesn’t recur. This test should check that the assignment directories for copied assignments are distinct from the original directories.

Issue #1201: Expertiza has the feature to auto generate the directory names for submissions from the assignment name. However, this may be concerning if two assignments have the same name, in which case the submission folders would be the same and this would again create a problem. This needs to be fixed.

----

=='''Modified Files'''==

1) /app/views/submitted_content/_submitted_files.html.erb

2) /app/controllers/assignment_controller.rb

3) /app/views/assignments/edit/_general.html.erb
----

=='''Approach taken to resolve the issues'''==

==='''Issue #391 '''===

-> When the instructor has not specified a directory path, there is no directory where the files can be stored.
-> Hence we allow only links to be submitted in such an assignment.
-> In the view of submitted content controller we disabled the button to upload files in such assignment where the directory path is null.
-> We displayed the message 'Fie submissions are disabled' whenever anyone tries to upload files to such assignment.

Pseudo Code:
Added following logic in /app/views/submitted_content/_submitted_files.html.erb

<% if @assignment.directory_path != "" %>
<% puts "Assign Directory: #{@assignment.directory_path}" %>
<%= submit_tag 'Upload file', class: 'btn btn-default' %>
<% else %>
<%= 'File Submissions are disabled' %>
<%end%>

Explanation:
If the assignment directory path is specified by the instructor then the button to upload files will be displayed else the warning message 'File submissions are disabled will be displayed'.

==='''Issue #1201'''===
Expertiza has the feature to auto generate the directory names for submissions from the assignment name. However, this may be concerning if two assignments have the same name, in which case the submission folders would be the same and this would again create a problem.

Approach taken to solve the issue:
Logic for Auto generation of the directory names:
Append assignment_name, assignment_id, course_id to make the directory name unique.

Files modified:

/app/controllers/assignment_controller.rb

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

1) /app/views/assignments/edit/_general.html.erb

Pseudo code:

<td><input type="checkbox" name="assignment_form[check_validate]" /> File submissions are allowed? </td>

Explanation: Added a checkbox in the view for creating an assignment. An instructor can select if file submissions are allowed. If he selects 'yes' then if the instructor has given an empty directory path, the name of the directory for the assignment will be auto generated.

2) /app/controllers/assignment_controller.rb

if quesparams[:assignment][:directory_path] == "" and quesparams[:check_validate] == "on"
quesparams[:assignment][:directory_path] = "#{quesparams[:assignment][:name]}_#{quesparams[:assignment][:id]}_#{quesparams[:assignment][:course_id]}"
end

Explanation: If the check box is checked, it will pass the value "on" to the assignment controller and the directory name will be auto generated.

[[File:Blank_Diagram.jpeg]]

==''' How to Test '''==

Link to ScreenCast Bug #391 : https://youtu.be/OVVknOBkG6Y

Link to ScreenCast Bug #404 : https://youtu.be/uvnamlY2

==''' Test Plan'''==
=='''issue #391 and issue #1201 '''==

Steps to test Issue #391 and #1201

1) Login as Instructor

2) Click on Manage , select assignments.

3) New public assignment/ New private assignment

4) Fill in the details

5) Select if you want to allow file submissions

6) If 'yes', then file directory name will be auto generated as 'assignment_name'_'assignment_id'_'course_name'

7) If 'no'

8) Login as a student and you can see that only links can be submitted and file submissions are disabled since the directory is not specified

==''' Automated tests for Issue #1190 '''==

Following RSPEC Code is added to assignments_controller_spec.rb:

The below code RSPEC snippet tests for the issue where in the assignment which is duplicated does not have the same directory for submissions as the original assignment.

context 'when new assignment directory is same as old' do
it 'should show an error and redirect to assignments#edit page' do
allow(new_assignment).to receive(:save).and_return(true)
allow(Assignment).to receive(:find).with(2).and_return(new_assignment)
params = {id: 1}
get :copy, params
expect(flash[:note]).to eq("Warning: The submission directory for the copy of this assignment will be the same as the submission directory "\
"for the existing assignment. This will allow student submissions to one assignment to overwrite submissions to the other assignment. "\
"If you do not want this to happen, change the submission directory in the new copy of the assignment.")
expect(flash[:error]).to eq('The assignment was not able to be copied. Please check the original assignment for missing information.')
expect(response).to redirect_to('/tree_display/list')
end

E1838 Project Red

2018-11-09T23:58:26Z

Nuachary: /* issue #391 and issue #1201 */

E1838 Project Red

2018-11-09T23:56:58Z

Nuachary: /* Automated tests for Issue #1190 */

==Introduction==
==='''Problem Statement'''===
In Expertiza, if the instructor doesn’t specify the assignment directory for a submission, the directory defaults to the home directory. This can lead to multiple assignment submissions being in the same place and creating confusion. The aim of the project if to handle all the scenarios that can arise when the instructor is not specifying any directory name.

=='''Issues to be fixed'''==

Issue #391: In Expertiza, if the instructor doesn’t specify the assignment directory for a submission, the directory defaults to the home directory. This can lead to multiple assignment submissions being in the same place and creating confusion. Please take a look at the Github issue for suggestions on how to solve this.

Issue #1190: An issue with conflicting directories for copied assignments was fixed. You need to write the test to verify that this issue doesn’t recur. This test should check that the assignment directories for copied assignments are distinct from the original directories.

Issue #1201: Expertiza has the feature to auto generate the directory names for submissions from the assignment name. However, this may be concerning if two assignments have the same name, in which case the submission folders would be the same and this would again create a problem. This needs to be fixed.

----

=='''Modified Files'''==

1) /app/views/submitted_content/_submitted_files.html.erb

2) /app/controllers/assignment_controller.rb

3) /app/views/assignments/edit/_general.html.erb
----

=='''Approach taken to resolve the issues'''==

==='''Issue #391 '''===

-> When the instructor has not specified a directory path, there is no directory where the files can be stored.
-> Hence we allow only links to be submitted in such an assignment.
-> In the view of submitted content controller we disabled the button to upload files in such assignment where the directory path is null.
-> We displayed the message 'Fie submissions are disabled' whenever anyone tries to upload files to such assignment.

Pseudo Code:
Added following logic in /app/views/submitted_content/_submitted_files.html.erb

<% if @assignment.directory_path != "" %>
<% puts "Assign Directory: #{@assignment.directory_path}" %>
<%= submit_tag 'Upload file', class: 'btn btn-default' %>
<% else %>
<%= 'File Submissions are disabled' %>
<%end%>

Explanation:
If the assignment directory path is specified by the instructor then the button to upload files will be displayed else the warning message 'File submissions are disabled will be displayed'.

==='''Issue #1201'''===
Expertiza has the feature to auto generate the directory names for submissions from the assignment name. However, this may be concerning if two assignments have the same name, in which case the submission folders would be the same and this would again create a problem.

Approach taken to solve the issue:
Logic for Auto generation of the directory names:
Append assignment_name, assignment_id, course_id to make the directory name unique.

Files modified:

/app/controllers/assignment_controller.rb

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

1) /app/views/assignments/edit/_general.html.erb

Pseudo code:

<td><input type="checkbox" name="assignment_form[check_validate]" /> File submissions are allowed? </td>

Explanation: Added a checkbox in the view for creating an assignment. An instructor can select if file submissions are allowed. If he selects 'yes' then if the instructor has given an empty directory path, the name of the directory for the assignment will be auto generated.

2) /app/controllers/assignment_controller.rb

if quesparams[:assignment][:directory_path] == "" and quesparams[:check_validate] == "on"
quesparams[:assignment][:directory_path] = "#{quesparams[:assignment][:name]}_#{quesparams[:assignment][:id]}_#{quesparams[:assignment][:course_id]}"
end

Explanation: If the check box is checked, it will pass the value "on" to the assignment controller and the directory name will be auto generated.

[[File:Blank_Diagram.jpeg]]

==''' How to Test '''==

Link to ScreenCast Bug #391 : https://youtu.be/OVVknOBkG6Y

Link to ScreenCast Bug #404 : https://youtu.be/uvnamlY2

==''' Test Plan'''==
=='''issue #391 and issue #1201 '''==

Steps to test Issue #391 and #1201

1) Login as Instructor

2) Click on Manage , select assignments.

3) New public assignment/ New private assignment

4) Fill in the details

5) Select if you want to allow file submissions

6) If 'yes', then file directory name will be auto generated as assignment_name+assignment_id+course_name

7) If 'no'

8) Login as a student and you can see that only links can be submitted and file submissions are disabled since the directory is not specified

==''' Automated tests for Issue #1190 '''==

Following RSPEC Code is added to assignments_controller_spec.rb:

The below code RSPEC snippet tests for the issue where in the assignment which is duplicated does not have the same directory for submissions as the original assignment.

context 'when new assignment directory is same as old' do
it 'should show an error and redirect to assignments#edit page' do
allow(new_assignment).to receive(:save).and_return(true)
allow(Assignment).to receive(:find).with(2).and_return(new_assignment)
params = {id: 1}
get :copy, params
expect(flash[:note]).to eq("Warning: The submission directory for the copy of this assignment will be the same as the submission directory "\
"for the existing assignment. This will allow student submissions to one assignment to overwrite submissions to the other assignment. "\
"If you do not want this to happen, change the submission directory in the new copy of the assignment.")
expect(flash[:error]).to eq('The assignment was not able to be copied. Please check the original assignment for missing information.')
expect(response).to redirect_to('/tree_display/list')
end

E1838 Project Red

2018-11-09T23:56:24Z

Nuachary:

==Introduction==
==='''Problem Statement'''===
In Expertiza, if the instructor doesn’t specify the assignment directory for a submission, the directory defaults to the home directory. This can lead to multiple assignment submissions being in the same place and creating confusion. The aim of the project if to handle all the scenarios that can arise when the instructor is not specifying any directory name.

=='''Issues to be fixed'''==

Issue #391: In Expertiza, if the instructor doesn’t specify the assignment directory for a submission, the directory defaults to the home directory. This can lead to multiple assignment submissions being in the same place and creating confusion. Please take a look at the Github issue for suggestions on how to solve this.

Issue #1190: An issue with conflicting directories for copied assignments was fixed. You need to write the test to verify that this issue doesn’t recur. This test should check that the assignment directories for copied assignments are distinct from the original directories.

Issue #1201: Expertiza has the feature to auto generate the directory names for submissions from the assignment name. However, this may be concerning if two assignments have the same name, in which case the submission folders would be the same and this would again create a problem. This needs to be fixed.

----

=='''Modified Files'''==

1) /app/views/submitted_content/_submitted_files.html.erb

2) /app/controllers/assignment_controller.rb

3) /app/views/assignments/edit/_general.html.erb
----

=='''Approach taken to resolve the issues'''==

==='''Issue #391 '''===

-> When the instructor has not specified a directory path, there is no directory where the files can be stored.
-> Hence we allow only links to be submitted in such an assignment.
-> In the view of submitted content controller we disabled the button to upload files in such assignment where the directory path is null.
-> We displayed the message 'Fie submissions are disabled' whenever anyone tries to upload files to such assignment.

Pseudo Code:
Added following logic in /app/views/submitted_content/_submitted_files.html.erb

<% if @assignment.directory_path != "" %>
<% puts "Assign Directory: #{@assignment.directory_path}" %>
<%= submit_tag 'Upload file', class: 'btn btn-default' %>
<% else %>
<%= 'File Submissions are disabled' %>
<%end%>

Explanation:
If the assignment directory path is specified by the instructor then the button to upload files will be displayed else the warning message 'File submissions are disabled will be displayed'.

==='''Issue #1201'''===
Expertiza has the feature to auto generate the directory names for submissions from the assignment name. However, this may be concerning if two assignments have the same name, in which case the submission folders would be the same and this would again create a problem.

Approach taken to solve the issue:
Logic for Auto generation of the directory names:
Append assignment_name, assignment_id, course_id to make the directory name unique.

Files modified:

/app/controllers/assignment_controller.rb

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

1) /app/views/assignments/edit/_general.html.erb

Pseudo code:

<td><input type="checkbox" name="assignment_form[check_validate]" /> File submissions are allowed? </td>

Explanation: Added a checkbox in the view for creating an assignment. An instructor can select if file submissions are allowed. If he selects 'yes' then if the instructor has given an empty directory path, the name of the directory for the assignment will be auto generated.

2) /app/controllers/assignment_controller.rb

if quesparams[:assignment][:directory_path] == "" and quesparams[:check_validate] == "on"
quesparams[:assignment][:directory_path] = "#{quesparams[:assignment][:name]}_#{quesparams[:assignment][:id]}_#{quesparams[:assignment][:course_id]}"
end

Explanation: If the check box is checked, it will pass the value "on" to the assignment controller and the directory name will be auto generated.

[[File:Blank_Diagram.jpeg]]

==''' How to Test '''==

Link to ScreenCast Bug #391 : https://youtu.be/OVVknOBkG6Y

Link to ScreenCast Bug #404 : https://youtu.be/uvnamlY2

==''' Test Plan'''==
=='''issue #391 and issue #1201 '''==

Steps to test Issue #391 and #1201

1) Login as Instructor

2) Click on Manage , select assignments.

3) New public assignment/ New private assignment

4) Fill in the details

5) Select if you want to allow file submissions

6) If 'yes', then file directory name will be auto generated as assignment_name+assignment_id+course_name

7) If 'no'

8) Login as a student and you can see that only links can be submitted and file submissions are disabled since the directory is not specified

==''' Automated tests for Issue #1190 '''==

Following RSPEC Code is added to assignments_controller_spec.rb:

The below code RSPEC snippet tests for the issue where in the assignment which is duplicated does not have the same directory for submissions as the original assignment.

context 'when new assignment directory is same as old' do
it 'should show an error and redirect to assignments#edit page' do
allow(new_assignment).to receive(:save).and_return(true)
allow(Assignment).to receive(:find).with(2).and_return(new_assignment)
params = {id: 1}
get :copy, params

expect(flash[:note]).to eq("Warning: The submission directory for the copy of this assignment will be the same as the submission directory "\
"for the existing assignment. This will allow student submissions to one assignment to overwrite submissions to the other assignment. "\
"If you do not want this to happen, change the submission directory in the new copy of the assignment.")
expect(flash[:error]).to eq('The assignment was not able to be copied. Please check the original assignment for missing information.')
expect(response).to redirect_to('/tree_display/list')

end

E1838 Project Red

2018-11-08T23:46:28Z

Nuachary: /* Issue #1201 */

==Introduction==
==='''Problem Statement'''===
In Expertiza, if the instructor doesn’t specify the assignment directory for a submission, the directory defaults to the home directory. This can lead to multiple assignment submissions being in the same place and creating confusion. The aim of the project if to handle all the scenarios that can arise when the instructor is not specifying any directory name.

=='''Issues to be fixed'''==

Issue #391: In Expertiza, if the instructor doesn’t specify the assignment directory for a submission, the directory defaults to the home directory. This can lead to multiple assignment submissions being in the same place and creating confusion. Please take a look at the Github issue for suggestions on how to solve this.

Issue #1190: An issue with conflicting directories for copied assignments was fixed. You need to write the test to verify that this issue doesn’t recur. This test should check that the assignment directories for copied assignments are distinct from the original directories.

Issue #1201: Expertiza has the feature to auto generate the directory names for submissions from the assignment name. However, this may be concerning if two assignments have the same name, in which case the submission folders would be the same and this would again create a problem. This needs to be fixed.

----

=='''Modified Files'''==

1) /app/views/submitted_content/_submitted_files.html.erb

2) /app/controllers/assignment_controller.rb

3) /app/views/assignments/edit/_general.html.erb
----

=='''Approach taken to resolve the issues'''==

==='''Issue #391 '''===

-> When the instructor has not specified a directory path, there is no directory where the files can be stored.
-> Hence we allow only links to be submitted in such an assignment.
-> In the view of submitted content controller we disabled the button to upload files in such assignment where the directory path is null.
-> We displayed the message 'Fie submissions are disabled' whenever anyone tries to upload files to such assignment.

Pseudo Code:
Added following logic in /app/views/submitted_content/_submitted_files.html.erb

<% if @assignment.directory_path != "" %>
<% puts "Assign Directory: #{@assignment.directory_path}" %>
<%= submit_tag 'Upload file', class: 'btn btn-default' %>
<% else %>
<%= 'File Submissions are disabled' %>
<%end%>

Explanation:
If the assignment directory path is specified by the instructor then the button to upload files will be displayed else the warning message 'File submissions are disabled will be displayed'.

==='''Issue #1201'''===
Expertiza has the feature to auto generate the directory names for submissions from the assignment name. However, this may be concerning if two assignments have the same name, in which case the submission folders would be the same and this would again create a problem.

Approach taken to solve the issue:
Logic for Auto generation of the directory names:
Append assignment_name, assignment_id, course_id to make the directory name unique.

Files modified:

/app/controllers/assignment_controller.rb

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

1) /app/views/assignments/edit/_general.html.erb

Pseudo code:

<td><input type="checkbox" name="assignment_form[check_validate]" /> File submissions are allowed? </td>

Explanation: Added a checkbox in the view for creating an assignment. An instructor can select if file submissions are allowed. If he selects 'yes' then if the instructor has given an empty directory path, the name of the directory for the assignment will be auto generated.

2) /app/controllers/assignment_controller.rb

if quesparams[:assignment][:directory_path] == "" and quesparams[:check_validate] == "on"
quesparams[:assignment][:directory_path] = "#{quesparams[:assignment][:name]}_#{quesparams[:assignment][:id]}_#{quesparams[:assignment][:course_id]}"
end

Explanation: If the check box is checked, it will pass the value "on" to the assignment controller and the directory name will be auto generated.

[[File:Blank_Diagram.jpeg]]

==''' How to Test '''==

Link to ScreenCast Bug #391 : https://youtu.be/OVVknOBkG6Y

Link to ScreenCast Bug #404 : https://youtu.be/uvnamlY2

==''' Test Plan'''==
=='''issue #391 and issue #1201 '''==

Steps to test Issue #391 and #1201

1) Login as Instructor

2) Click on Manage , select assignments.

3) New public assignment/ New private assignment

4) Fill in the details

5) Select if you want to allow file submissions

6) If 'yes', then file directory name will be auto generated as assignment_name+assignment_id+course_name

7) If 'no'

8) Login as a student and you can see that only links can be submitted and file submissions are disabled since the directory is not specified

==''' Automated tests for Issue #391 and #404 '''==

Following RSPEC Code is added to assignment_spec.rb:

1) To check if the directory storage path specified by the user is a part of any other submissions directory we check if the assignment.directory_path is a part of any existing directory path:
1)describe 'check_directory_path' do:
2) it 'returns false if directory path already in use' do:
3) @assignment = create(:assignment)
4) expect(@assignment.check_directory_path).to eql(false)
5) end
6)end

2) To check that an assignment object cannot be saved until a submission directory path is provided for that assignment:

1)it 'is not valid without directory_path' do
2) assignment.directory_path = nil
3) assignment.should_not be_valid
4)end

3) To check if after assigning course to an assignment is the directory path updated to contain the course path:

1)it 'should contain course in path name' do
2) @assignment = create(:assignment)
3) @assignment.directory_path = Course.first.directory_path.to_s + "/finaltest"
4) expect(@assignment.directory_path).to include(Course.first.directory_path)
5)end
** To test the changes clone the following repository https://github.com/daxamin/expertiza .

E1838 Project Red

2018-11-08T23:46:15Z

Nuachary: /* Issue #1201 */

==Introduction==
==='''Problem Statement'''===
In Expertiza, if the instructor doesn’t specify the assignment directory for a submission, the directory defaults to the home directory. This can lead to multiple assignment submissions being in the same place and creating confusion. The aim of the project if to handle all the scenarios that can arise when the instructor is not specifying any directory name.

=='''Issues to be fixed'''==

Issue #391: In Expertiza, if the instructor doesn’t specify the assignment directory for a submission, the directory defaults to the home directory. This can lead to multiple assignment submissions being in the same place and creating confusion. Please take a look at the Github issue for suggestions on how to solve this.

Issue #1190: An issue with conflicting directories for copied assignments was fixed. You need to write the test to verify that this issue doesn’t recur. This test should check that the assignment directories for copied assignments are distinct from the original directories.

Issue #1201: Expertiza has the feature to auto generate the directory names for submissions from the assignment name. However, this may be concerning if two assignments have the same name, in which case the submission folders would be the same and this would again create a problem. This needs to be fixed.

----

=='''Modified Files'''==

1) /app/views/submitted_content/_submitted_files.html.erb

2) /app/controllers/assignment_controller.rb

3) /app/views/assignments/edit/_general.html.erb
----

=='''Approach taken to resolve the issues'''==

==='''Issue #391 '''===

-> When the instructor has not specified a directory path, there is no directory where the files can be stored.
-> Hence we allow only links to be submitted in such an assignment.
-> In the view of submitted content controller we disabled the button to upload files in such assignment where the directory path is null.
-> We displayed the message 'Fie submissions are disabled' whenever anyone tries to upload files to such assignment.

Pseudo Code:
Added following logic in /app/views/submitted_content/_submitted_files.html.erb

<% if @assignment.directory_path != "" %>
<% puts "Assign Directory: #{@assignment.directory_path}" %>
<%= submit_tag 'Upload file', class: 'btn btn-default' %>
<% else %>
<%= 'File Submissions are disabled' %>
<%end%>

Explanation:
If the assignment directory path is specified by the instructor then the button to upload files will be displayed else the warning message 'File submissions are disabled will be displayed'.

==='''Issue #1201'''===
Expertiza has the feature to auto generate the directory names for submissions from the assignment name. However, this may be concerning if two assignments have the same name, in which case the submission folders would be the same and this would again create a problem.

Approach taken to solve the issue:
Logic for Auto generation of the directory names:
Append assignment_name, assignment_id, course_id to make the directory name unique.

Files modified:

/app/controllers/assignment_controller.rb

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

1) /app/views/assignments/edit/_general.html.erb

Pseudo code:

<td><input type="checkbox" name="assignment_form[check_validate]" /> File submissions are allowed? </td>

Explanation: Added a checkbox in the view for creating an assignment. An instructor can select if file submissions are allowed. If he selects 'yes' then if the instructor has given an empty directory path, the name of the directory for the assignment will be auto generated.

2) /app/controllers/assignment_controller.rb

if quesparams[:assignment][:directory_path] == "" and quesparams[:check_validate] == "on"
quesparams[:assignment][:directory_path] = "#{quesparams[:assignment][:name]}_#{quesparams[:assignment][:id]}_#{quesparams[:assignment][:course_id]}"
end

Explanation: If the check box is checked, it will pass the value "on" to the assignment controller and the directory name will be auto generated.

[[File:Blank_Diagram.jpeg]]

==''' How to Test '''==

Link to ScreenCast Bug #391 : https://youtu.be/OVVknOBkG6Y

Link to ScreenCast Bug #404 : https://youtu.be/uvnamlY2

==''' Test Plan'''==
=='''issue #391 and issue #1201 '''==

Steps to test Issue #391 and #1201

1) Login as Instructor

2) Click on Manage , select assignments.

3) New public assignment/ New private assignment

4) Fill in the details

5) Select if you want to allow file submissions

6) If 'yes', then file directory name will be auto generated as assignment_name+assignment_id+course_name

7) If 'no'

8) Login as a student and you can see that only links can be submitted and file submissions are disabled since the directory is not specified

==''' Automated tests for Issue #391 and #404 '''==

Following RSPEC Code is added to assignment_spec.rb:

1) To check if the directory storage path specified by the user is a part of any other submissions directory we check if the assignment.directory_path is a part of any existing directory path:
1)describe 'check_directory_path' do:
2) it 'returns false if directory path already in use' do:
3) @assignment = create(:assignment)
4) expect(@assignment.check_directory_path).to eql(false)
5) end
6)end

2) To check that an assignment object cannot be saved until a submission directory path is provided for that assignment:

1)it 'is not valid without directory_path' do
2) assignment.directory_path = nil
3) assignment.should_not be_valid
4)end

3) To check if after assigning course to an assignment is the directory path updated to contain the course path:

1)it 'should contain course in path name' do
2) @assignment = create(:assignment)
3) @assignment.directory_path = Course.first.directory_path.to_s + "/finaltest"
4) expect(@assignment.directory_path).to include(Course.first.directory_path)
5)end
** To test the changes clone the following repository https://github.com/daxamin/expertiza .