Expertiza_Wiki - User contributions [en]

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

2018-12-18T04:06:49Z

Hshah3: /* Proposed Solutions and Implementation */

== '''Introduction''' ==

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

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

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

=== Current scenario ===

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

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

[[File: Submissions_instr.jpeg | center]]

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

[[File: Grades_view_team_current.png | center]]

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

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

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

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

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

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

[[File:Latest_screen_instructor.JPG]]
[[File:Ins_TA_Review.png]]

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

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

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

[[File:Score_hover.png]]

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

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

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

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

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

'''More testing:'''

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

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

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

== '''References''' ==

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

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

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

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

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

2018-12-18T04:02:32Z

Hshah3: /* Proposed Solutions and Implementation */

== '''Introduction''' ==

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

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

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

=== Current scenario ===

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

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

[[File: Submissions_instr.jpeg | center]]

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

[[File: Grades_view_team_current.png | center]]

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

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

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

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

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

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

[[File:Latest_screen_instructor.JPG]]
[[File:Ins_TA_Review.png]]

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

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

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

[[File:Score_hover.png]]

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

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

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

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

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

'''More testing:'''

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

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

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

== '''References''' ==

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

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

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

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

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

2018-12-18T03:57:27Z

Hshah3: /* Proposed Solutions and Implementation */

== '''Introduction''' ==

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

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

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

=== Current scenario ===

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

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

[[File: Submissions_instr.jpeg | center]]

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

[[File: Grades_view_team_current.png | center]]

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

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

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

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

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

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

[[File:latest_screen_instructor.jpg]]
[[File:Ins_TA_Review.png]]

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

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

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

[[File:Score_hover.png]]

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

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

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

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

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

'''More testing:'''

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

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

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

== '''References''' ==

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

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

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

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

File:Latest screen instructor.JPG

2018-12-18T03:48:40Z

Hshah3:

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

2018-12-18T03:37:35Z

Hshah3: /* Proposed Solutions and Implementation */

== '''Introduction''' ==

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

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

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

=== Current scenario ===

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

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

[[File: Submissions_instr.jpeg | center]]

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

[[File: Grades_view_team_current.png | center]]

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

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

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

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

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

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

[[File:Ins_TA_Review.png]]

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

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

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

[[File:Score_hover.png]]

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

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

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

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

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

'''More testing:'''

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

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

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

== '''References''' ==

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

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

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

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

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

2018-11-21T04:29:50Z

Hshah3: /* Proposed Solutions and Implementation */

== '''Introduction''' ==

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

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

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

=== Current scenario ===

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

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

[[File: Submissions_instr.jpeg | center]]

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

[[File: Grades_view_team_current.png | center]]

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

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

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

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

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

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

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

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

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

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

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

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

'''More testing:'''

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

== '''References''' ==

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

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

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

E1843 Issues Related To Deadlines

2018-11-10T00:07:30Z

Hshah3: /* References */

This wiki page is for the description of changes made under E1843- Issues Related to Topic Deadlines OSS assignment for Fall 2018, CSC/ECE 517.

== '''About Expertiza''' ==

Expertiza is an open source project based on Ruby on Rails framework and the code is available on Github. Expertiza allows the instructor to create new assignments as well as edit new or existing assignments. Instructors can also create a list of topics the students can sign up for and specify deadlines for completion of various tasks. Students can form teams in Expertiza to work on various projects and assignments as well as peer review other students' submissions. Expertiza supports submission across various document types, including the URLs Wiki pages.

== '''Issues in the Current Project''' ==

1.There is no deadline that specifies when a team can drop their topics. Due to this, few problems occur: The team might drop a topic later on which is close to the submission date and this results in topic not being assigned to any other team on time such that they can submit their assignment. Also, if one team was wait listed for the same topic which the other team dropped closer to the submission deadline, then the first wait-listed team will be assigned to the dropped topic which is not desirable as they might be working on their assigned topic for long time.

2.There are different topics on which students can work during different times. This type of assignment is known as Staggered- deadline assignment in which different topics have different submission and review deadlines. For these assignments too, there is a need for "Drop Topics Deadline". In the current implementation, the drop topic deadline is same for all the topics in a Staggered Deadline assignment which is not desirable.

== '''Corrections made in the New Project''' ==

1. The instructor can specify a Drop Topic deadline date now. After a drop topic deadline passes, the "X"(signup option) in the Sign-Up sheet disables so that the student cannot drop the topic and the wait-list for that topic is cleared, which will resolve the issue of the topic being assigned to a wait-listed team very close to the submission deadline.

2. Staggered deadline assignments now have different drop deadlines for different topics in that assignment.The above resolution also works for Staggered Deadlines Assignment

== '''Files modified in Current Project''' ==

1. app/controllers/assignments_controller.rb

2. app/controllers/sign_up_sheet_controller.rb

3. app/models/student_task.rb

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

5. app/views/sign_up_sheet/_add_signup_topics_staggered.html.erb

6. app/views/sign_up_sheet/_due_dates.html.erb

== '''Current Implementation''' ==

1. Clearing the waitlist after Drop Deadline passes is implemented in sign_up_sheet_controller.rb where it is checked if the current time is greater than the time mentioned in Drop deadline. If the deadline has been passed, the 'update_is_waitlisted' method of SignedUpTeam model is called to delete all the waitlisted teams for that topic.
2. Changes are made in Assignments View to add an additional column for Drop-Topic Deadline for Staggered Deadlines Assignment. The code snippets for corresponding changes in controllers and models are as below:

(i) app/controllers/sign_up_sheet_controller.rb

if !topic_id1.nil? and !@drop_topic_deadline1.nil? and Time.now > @drop_topic_deadline1.due_at
SignedUpTeam.update_is_waitlisted(topic_id1.topic_id,team_id) end

(ii) The 'update_is_waitlisted' method is implemented in app/models/signed_up_team.rb as follows:

def self.update_is_waitlisted(topic_i)
topic_id1 = SignedUpTeam.where(team_id: team_id).first
if @assignment.staggered_deadline?
@drop_topic_deadline1 = TopicDueDate.where(parent_id: topic_id1.topic_id, deadline_type_id: 6).first rescue nil end
due_dates = params[:due_date]
topics = SignUpTopic.where(assignment_id: params[:assignment_id])
review_rounds = assignment.num_review_rounds
topics.each_with_index do |topic, index|
for i in 1..review_rounds
@topic_drop_topic_due_date = due_dates[topics[index].id.to_s + '_drop_topic_' + i.to_s + '_due_date']
if assignment.due_dates.select {|due_date| due_date.deadline_type_id == 6 }.nil?
@assignment_drop_topic_due_date = DateTime.parse(@assignment_drop_topic_due_dates[i - 1].due_at.to_s).strftime("%Y-%m-%d %H:%M")
end
end

(iii) app/helpers/sign_up_sheet_helper.rb

if assignment_due_dates.length == 0
assignment_due_dates = @assignment_submission_due_dates
end

(iv) app/models/student_task.rb

def self.get_due_date_data(assignment, timeline_list, participant)
if assignment.staggered_deadline?
team_id = participant.team.try(:id)
topic_id1 = SignedUpTeam.where(team_id: team_id).first
if !topic_id1.nil?
topic_due_date = TopicDueDate.where(parent_id: topic_id1.topic_id, deadline_type_id: 6).first rescue nil
timeline = {label: ('Drop Topic Deadline').humanize}
timeline[:updated_at] = topic_due_date.due_at.strftime('%a, %d %b %Y %H:%M')
timeline_list << timeline
end
end
assignment.due_dates.each do |dd|
timeline = {label: (dd.deadline_type.name + ' Deadline').humanize}
unless dd.due_at.nil?
timeline[:updated_at] = dd.due_at.strftime('%a, %d %b %Y %H:%M')
timeline_list << timeline
end
end
end

(v) app/views/assignments/edit.html.erb

<% if @assignment_form.assignment.staggered_deadline == true %>
<%= render partial: '/sign_up_sheet/add_signup_topics_staggered', locals: {review_rounds: @review_rounds, assignment_submission_due_dates: @assignment_submission_due_dates, assignment_review_due_dates: @assignment_review_due_dates, assignment_drop_topic_due_dates: @assignment_drop_topic_due_dates} %>
<% else %>
<%= render '/sign_up_sheet/add_signup_topics' %>
<% end %>

(vi) app/views/sign_up_sheet/_add_signup_topics_staggered.html.erb

<%= form_tag :controller => 'sign_up_sheet', :action => 'save_topic_deadlines', :assignment_id => @assignment.id do %>

 <%= render :partial => '/sign_up_sheet/due_dates', :locals => {review_rounds: review_rounds, assignment_submission_due_dates: assignment_submission_due_dates, assignment_review_due_dates: assignment_review_due_dates, assignment_drop_topic_due_dates: assignment_drop_topic_due_dates} %>
<% end %>

(vii) app/views/sign_up_sheet/_due_dates.html.erb

<tr>
<th>Drop deadline</th>
<%for i in 2..review_rounds%>
<td><%= @assignment.sign_up_topics[i].topic_name %></td>
<% for review_round in 1..review_rounds %>
<% topic_id = @assignment.sign_up_topics[i].id %>
<%if review_round == 1 %>
<td><%= text_field :due_date, (topic_id.to_s + '_drop_topic_' + review_round.to_s + '_due_date').to_s, size: 20, value: check_topic_due_date_value(assignment_drop_topic_due_dates, topic_id, 6, review_round) %></td>
<td><%= text_field :due_date, (topic_id.to_s + '_submission_' + review_round.to_s + '_due_date').to_s, size: 20, value: check_topic_due_date_value(assignment_submission_due_dates, topic_id, 1, review_round) %></td>
<td><%= text_field :due_date, (topic_id.to_s + '_review_' + review_round.to_s + '_due_date').to_s, size: 20, value: check_topic_due_date_value(assignment_review_due_dates, topic_id, 2, review_round) %></td>
<%else%>
<td><%= text_field :due_date, (topic_id.to_s + '_submission_' + review_round.to_s + '_due_date').to_s, size: 20, value: check_topic_due_date_value(assignment_submission_due_dates, topic_id, 1, review_round) %></td>
<td><%= text_field :due_date, (topic_id.to_s + '_review_' + review_round.to_s + '_due_date').to_s, size: 20, value: check_topic_due_date_value(assignment_review_due_dates, topic_id, 2, review_round) %></td> <%end%> <%end%>
</tr>
<%end%>

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

It was discussed that project does not require any Unit Test cases to be implemented as the changes are mostly visible in views.

== '''References''' ==

1. Expertiza on GITHUB: https://github.com/expertiza/expertiza

2. GitHub Project Repository Fork: https://github.com/harshshah949494/expertiza

3. The live Expertiza website : https://drive.google.com/open?id=1jUwbeeiI2KaIH3l0C7FD0QHgBL6PVwF1

4. Demo link: https://drive.google.com/open?id=1jUwbeeiI2KaIH3l0C7FD0QHgBL6PVwF1

5. Expertiza project documentation wiki: http://wiki.expertiza.ncsu.edu/index.php?title=E1843_Issues_Related_To_Deadlines&action=edit&section=7

E1843 Issues Related To Deadlines

2018-11-10T00:05:30Z

Hshah3: /* References */

This wiki page is for the description of changes made under E1843- Issues Related to Topic Deadlines OSS assignment for Fall 2018, CSC/ECE 517.

== '''About Expertiza''' ==

Expertiza is an open source project based on Ruby on Rails framework and the code is available on Github. Expertiza allows the instructor to create new assignments as well as edit new or existing assignments. Instructors can also create a list of topics the students can sign up for and specify deadlines for completion of various tasks. Students can form teams in Expertiza to work on various projects and assignments as well as peer review other students' submissions. Expertiza supports submission across various document types, including the URLs Wiki pages.

== '''Issues in the Current Project''' ==

1.There is no deadline that specifies when a team can drop their topics. Due to this, few problems occur: The team might drop a topic later on which is close to the submission date and this results in topic not being assigned to any other team on time such that they can submit their assignment. Also, if one team was wait listed for the same topic which the other team dropped closer to the submission deadline, then the first wait-listed team will be assigned to the dropped topic which is not desirable as they might be working on their assigned topic for long time.

2.There are different topics on which students can work during different times. This type of assignment is known as Staggered- deadline assignment in which different topics have different submission and review deadlines. For these assignments too, there is a need for "Drop Topics Deadline". In the current implementation, the drop topic deadline is same for all the topics in a Staggered Deadline assignment which is not desirable.

== '''Corrections made in the New Project''' ==

1. The instructor can specify a Drop Topic deadline date now. After a drop topic deadline passes, the "X"(signup option) in the Sign-Up sheet disables so that the student cannot drop the topic and the wait-list for that topic is cleared, which will resolve the issue of the topic being assigned to a wait-listed team very close to the submission deadline.

2. Staggered deadline assignments now have different drop deadlines for different topics in that assignment.The above resolution also works for Staggered Deadlines Assignment

== '''Files modified in Current Project''' ==

1. app/controllers/assignments_controller.rb

2. app/controllers/sign_up_sheet_controller.rb

3. app/models/student_task.rb

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

5. app/views/sign_up_sheet/_add_signup_topics_staggered.html.erb

6. app/views/sign_up_sheet/_due_dates.html.erb

== '''Current Implementation''' ==

1. Clearing the waitlist after Drop Deadline passes is implemented in sign_up_sheet_controller.rb where it is checked if the current time is greater than the time mentioned in Drop deadline. If the deadline has been passed, the 'update_is_waitlisted' method of SignedUpTeam model is called to delete all the waitlisted teams for that topic.
2. Changes are made in Assignments View to add an additional column for Drop-Topic Deadline for Staggered Deadlines Assignment. The code snippets for corresponding changes in controllers and models are as below:

(i) app/controllers/sign_up_sheet_controller.rb

if !topic_id1.nil? and !@drop_topic_deadline1.nil? and Time.now > @drop_topic_deadline1.due_at
SignedUpTeam.update_is_waitlisted(topic_id1.topic_id,team_id) end

(ii) The 'update_is_waitlisted' method is implemented in app/models/signed_up_team.rb as follows:

def self.update_is_waitlisted(topic_i)
topic_id1 = SignedUpTeam.where(team_id: team_id).first
if @assignment.staggered_deadline?
@drop_topic_deadline1 = TopicDueDate.where(parent_id: topic_id1.topic_id, deadline_type_id: 6).first rescue nil end
due_dates = params[:due_date]
topics = SignUpTopic.where(assignment_id: params[:assignment_id])
review_rounds = assignment.num_review_rounds
topics.each_with_index do |topic, index|
for i in 1..review_rounds
@topic_drop_topic_due_date = due_dates[topics[index].id.to_s + '_drop_topic_' + i.to_s + '_due_date']
if assignment.due_dates.select {|due_date| due_date.deadline_type_id == 6 }.nil?
@assignment_drop_topic_due_date = DateTime.parse(@assignment_drop_topic_due_dates[i - 1].due_at.to_s).strftime("%Y-%m-%d %H:%M")
end
end

(iii) app/helpers/sign_up_sheet_helper.rb

if assignment_due_dates.length == 0
assignment_due_dates = @assignment_submission_due_dates
end

(iv) app/models/student_task.rb

def self.get_due_date_data(assignment, timeline_list, participant)
if assignment.staggered_deadline?
team_id = participant.team.try(:id)
topic_id1 = SignedUpTeam.where(team_id: team_id).first
if !topic_id1.nil?
topic_due_date = TopicDueDate.where(parent_id: topic_id1.topic_id, deadline_type_id: 6).first rescue nil
timeline = {label: ('Drop Topic Deadline').humanize}
timeline[:updated_at] = topic_due_date.due_at.strftime('%a, %d %b %Y %H:%M')
timeline_list << timeline
end
end
assignment.due_dates.each do |dd|
timeline = {label: (dd.deadline_type.name + ' Deadline').humanize}
unless dd.due_at.nil?
timeline[:updated_at] = dd.due_at.strftime('%a, %d %b %Y %H:%M')
timeline_list << timeline
end
end
end

(v) app/views/assignments/edit.html.erb

<% if @assignment_form.assignment.staggered_deadline == true %>
<%= render partial: '/sign_up_sheet/add_signup_topics_staggered', locals: {review_rounds: @review_rounds, assignment_submission_due_dates: @assignment_submission_due_dates, assignment_review_due_dates: @assignment_review_due_dates, assignment_drop_topic_due_dates: @assignment_drop_topic_due_dates} %>
<% else %>
<%= render '/sign_up_sheet/add_signup_topics' %>
<% end %>

(vi) app/views/sign_up_sheet/_add_signup_topics_staggered.html.erb

<%= form_tag :controller => 'sign_up_sheet', :action => 'save_topic_deadlines', :assignment_id => @assignment.id do %>

 <%= render :partial => '/sign_up_sheet/due_dates', :locals => {review_rounds: review_rounds, assignment_submission_due_dates: assignment_submission_due_dates, assignment_review_due_dates: assignment_review_due_dates, assignment_drop_topic_due_dates: assignment_drop_topic_due_dates} %>
<% end %>

(vii) app/views/sign_up_sheet/_due_dates.html.erb

<tr>
<th>Drop deadline</th>
<%for i in 2..review_rounds%>
<td><%= @assignment.sign_up_topics[i].topic_name %></td>
<% for review_round in 1..review_rounds %>
<% topic_id = @assignment.sign_up_topics[i].id %>
<%if review_round == 1 %>
<td><%= text_field :due_date, (topic_id.to_s + '_drop_topic_' + review_round.to_s + '_due_date').to_s, size: 20, value: check_topic_due_date_value(assignment_drop_topic_due_dates, topic_id, 6, review_round) %></td>
<td><%= text_field :due_date, (topic_id.to_s + '_submission_' + review_round.to_s + '_due_date').to_s, size: 20, value: check_topic_due_date_value(assignment_submission_due_dates, topic_id, 1, review_round) %></td>
<td><%= text_field :due_date, (topic_id.to_s + '_review_' + review_round.to_s + '_due_date').to_s, size: 20, value: check_topic_due_date_value(assignment_review_due_dates, topic_id, 2, review_round) %></td>
<%else%>
<td><%= text_field :due_date, (topic_id.to_s + '_submission_' + review_round.to_s + '_due_date').to_s, size: 20, value: check_topic_due_date_value(assignment_submission_due_dates, topic_id, 1, review_round) %></td>
<td><%= text_field :due_date, (topic_id.to_s + '_review_' + review_round.to_s + '_due_date').to_s, size: 20, value: check_topic_due_date_value(assignment_review_due_dates, topic_id, 2, review_round) %></td> <%end%> <%end%>
</tr>
<%end%>

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

It was discussed that project does not require any Unit Test cases to be implemented as the changes are mostly visible in views.

== '''References''' ==

1. Expertiza on

2. GitHub Project Repository [Fork]https://github.com/harshshah949494/expertiza

3. The live Expertiza website

4. Demo link

5. Expertiza project documentation wiki

E1843 Issues Related To Deadlines

2018-11-10T00:05:02Z

Hshah3: /* References */

This wiki page is for the description of changes made under E1843- Issues Related to Topic Deadlines OSS assignment for Fall 2018, CSC/ECE 517.

== '''About Expertiza''' ==

Expertiza is an open source project based on Ruby on Rails framework and the code is available on Github. Expertiza allows the instructor to create new assignments as well as edit new or existing assignments. Instructors can also create a list of topics the students can sign up for and specify deadlines for completion of various tasks. Students can form teams in Expertiza to work on various projects and assignments as well as peer review other students' submissions. Expertiza supports submission across various document types, including the URLs Wiki pages.

== '''Issues in the Current Project''' ==

1.There is no deadline that specifies when a team can drop their topics. Due to this, few problems occur: The team might drop a topic later on which is close to the submission date and this results in topic not being assigned to any other team on time such that they can submit their assignment. Also, if one team was wait listed for the same topic which the other team dropped closer to the submission deadline, then the first wait-listed team will be assigned to the dropped topic which is not desirable as they might be working on their assigned topic for long time.

2.There are different topics on which students can work during different times. This type of assignment is known as Staggered- deadline assignment in which different topics have different submission and review deadlines. For these assignments too, there is a need for "Drop Topics Deadline". In the current implementation, the drop topic deadline is same for all the topics in a Staggered Deadline assignment which is not desirable.

== '''Corrections made in the New Project''' ==

1. The instructor can specify a Drop Topic deadline date now. After a drop topic deadline passes, the "X"(signup option) in the Sign-Up sheet disables so that the student cannot drop the topic and the wait-list for that topic is cleared, which will resolve the issue of the topic being assigned to a wait-listed team very close to the submission deadline.

2. Staggered deadline assignments now have different drop deadlines for different topics in that assignment.The above resolution also works for Staggered Deadlines Assignment

== '''Files modified in Current Project''' ==

1. app/controllers/assignments_controller.rb

2. app/controllers/sign_up_sheet_controller.rb

3. app/models/student_task.rb

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

5. app/views/sign_up_sheet/_add_signup_topics_staggered.html.erb

6. app/views/sign_up_sheet/_due_dates.html.erb

== '''Current Implementation''' ==

1. Clearing the waitlist after Drop Deadline passes is implemented in sign_up_sheet_controller.rb where it is checked if the current time is greater than the time mentioned in Drop deadline. If the deadline has been passed, the 'update_is_waitlisted' method of SignedUpTeam model is called to delete all the waitlisted teams for that topic.
2. Changes are made in Assignments View to add an additional column for Drop-Topic Deadline for Staggered Deadlines Assignment. The code snippets for corresponding changes in controllers and models are as below:

(i) app/controllers/sign_up_sheet_controller.rb

if !topic_id1.nil? and !@drop_topic_deadline1.nil? and Time.now > @drop_topic_deadline1.due_at
SignedUpTeam.update_is_waitlisted(topic_id1.topic_id,team_id) end

(ii) The 'update_is_waitlisted' method is implemented in app/models/signed_up_team.rb as follows:

def self.update_is_waitlisted(topic_i)
topic_id1 = SignedUpTeam.where(team_id: team_id).first
if @assignment.staggered_deadline?
@drop_topic_deadline1 = TopicDueDate.where(parent_id: topic_id1.topic_id, deadline_type_id: 6).first rescue nil end
due_dates = params[:due_date]
topics = SignUpTopic.where(assignment_id: params[:assignment_id])
review_rounds = assignment.num_review_rounds
topics.each_with_index do |topic, index|
for i in 1..review_rounds
@topic_drop_topic_due_date = due_dates[topics[index].id.to_s + '_drop_topic_' + i.to_s + '_due_date']
if assignment.due_dates.select {|due_date| due_date.deadline_type_id == 6 }.nil?
@assignment_drop_topic_due_date = DateTime.parse(@assignment_drop_topic_due_dates[i - 1].due_at.to_s).strftime("%Y-%m-%d %H:%M")
end
end

(iii) app/helpers/sign_up_sheet_helper.rb

if assignment_due_dates.length == 0
assignment_due_dates = @assignment_submission_due_dates
end

(iv) app/models/student_task.rb

def self.get_due_date_data(assignment, timeline_list, participant)
if assignment.staggered_deadline?
team_id = participant.team.try(:id)
topic_id1 = SignedUpTeam.where(team_id: team_id).first
if !topic_id1.nil?
topic_due_date = TopicDueDate.where(parent_id: topic_id1.topic_id, deadline_type_id: 6).first rescue nil
timeline = {label: ('Drop Topic Deadline').humanize}
timeline[:updated_at] = topic_due_date.due_at.strftime('%a, %d %b %Y %H:%M')
timeline_list << timeline
end
end
assignment.due_dates.each do |dd|
timeline = {label: (dd.deadline_type.name + ' Deadline').humanize}
unless dd.due_at.nil?
timeline[:updated_at] = dd.due_at.strftime('%a, %d %b %Y %H:%M')
timeline_list << timeline
end
end
end

(v) app/views/assignments/edit.html.erb

<% if @assignment_form.assignment.staggered_deadline == true %>
<%= render partial: '/sign_up_sheet/add_signup_topics_staggered', locals: {review_rounds: @review_rounds, assignment_submission_due_dates: @assignment_submission_due_dates, assignment_review_due_dates: @assignment_review_due_dates, assignment_drop_topic_due_dates: @assignment_drop_topic_due_dates} %>
<% else %>
<%= render '/sign_up_sheet/add_signup_topics' %>
<% end %>

(vi) app/views/sign_up_sheet/_add_signup_topics_staggered.html.erb

<%= form_tag :controller => 'sign_up_sheet', :action => 'save_topic_deadlines', :assignment_id => @assignment.id do %>

 <%= render :partial => '/sign_up_sheet/due_dates', :locals => {review_rounds: review_rounds, assignment_submission_due_dates: assignment_submission_due_dates, assignment_review_due_dates: assignment_review_due_dates, assignment_drop_topic_due_dates: assignment_drop_topic_due_dates} %>
<% end %>

(vii) app/views/sign_up_sheet/_due_dates.html.erb

<tr>
<th>Drop deadline</th>
<%for i in 2..review_rounds%>
<td><%= @assignment.sign_up_topics[i].topic_name %></td>
<% for review_round in 1..review_rounds %>
<% topic_id = @assignment.sign_up_topics[i].id %>
<%if review_round == 1 %>
<td><%= text_field :due_date, (topic_id.to_s + '_drop_topic_' + review_round.to_s + '_due_date').to_s, size: 20, value: check_topic_due_date_value(assignment_drop_topic_due_dates, topic_id, 6, review_round) %></td>
<td><%= text_field :due_date, (topic_id.to_s + '_submission_' + review_round.to_s + '_due_date').to_s, size: 20, value: check_topic_due_date_value(assignment_submission_due_dates, topic_id, 1, review_round) %></td>
<td><%= text_field :due_date, (topic_id.to_s + '_review_' + review_round.to_s + '_due_date').to_s, size: 20, value: check_topic_due_date_value(assignment_review_due_dates, topic_id, 2, review_round) %></td>
<%else%>
<td><%= text_field :due_date, (topic_id.to_s + '_submission_' + review_round.to_s + '_due_date').to_s, size: 20, value: check_topic_due_date_value(assignment_submission_due_dates, topic_id, 1, review_round) %></td>
<td><%= text_field :due_date, (topic_id.to_s + '_review_' + review_round.to_s + '_due_date').to_s, size: 20, value: check_topic_due_date_value(assignment_review_due_dates, topic_id, 2, review_round) %></td> <%end%> <%end%>
</tr>
<%end%>

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

It was discussed that project does not require any Unit Test cases to be implemented as the changes are mostly visible in views.

== '''References''' ==

1. Expertiza on

2. GitHub Project Repository [https://github.com/harshshah949494/expertiza}[[Fork]]

3. The live Expertiza website

4. Demo link

5. Expertiza project documentation wiki

E1843 Issues Related To Deadlines

2018-11-10T00:04:40Z

Hshah3: /* References */

This wiki page is for the description of changes made under E1843- Issues Related to Topic Deadlines OSS assignment for Fall 2018, CSC/ECE 517.

== '''About Expertiza''' ==

Expertiza is an open source project based on Ruby on Rails framework and the code is available on Github. Expertiza allows the instructor to create new assignments as well as edit new or existing assignments. Instructors can also create a list of topics the students can sign up for and specify deadlines for completion of various tasks. Students can form teams in Expertiza to work on various projects and assignments as well as peer review other students' submissions. Expertiza supports submission across various document types, including the URLs Wiki pages.

== '''Issues in the Current Project''' ==

1.There is no deadline that specifies when a team can drop their topics. Due to this, few problems occur: The team might drop a topic later on which is close to the submission date and this results in topic not being assigned to any other team on time such that they can submit their assignment. Also, if one team was wait listed for the same topic which the other team dropped closer to the submission deadline, then the first wait-listed team will be assigned to the dropped topic which is not desirable as they might be working on their assigned topic for long time.

2.There are different topics on which students can work during different times. This type of assignment is known as Staggered- deadline assignment in which different topics have different submission and review deadlines. For these assignments too, there is a need for "Drop Topics Deadline". In the current implementation, the drop topic deadline is same for all the topics in a Staggered Deadline assignment which is not desirable.

== '''Corrections made in the New Project''' ==

1. The instructor can specify a Drop Topic deadline date now. After a drop topic deadline passes, the "X"(signup option) in the Sign-Up sheet disables so that the student cannot drop the topic and the wait-list for that topic is cleared, which will resolve the issue of the topic being assigned to a wait-listed team very close to the submission deadline.

2. Staggered deadline assignments now have different drop deadlines for different topics in that assignment.The above resolution also works for Staggered Deadlines Assignment

== '''Files modified in Current Project''' ==

1. app/controllers/assignments_controller.rb

2. app/controllers/sign_up_sheet_controller.rb

3. app/models/student_task.rb

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

5. app/views/sign_up_sheet/_add_signup_topics_staggered.html.erb

6. app/views/sign_up_sheet/_due_dates.html.erb

== '''Current Implementation''' ==

1. Clearing the waitlist after Drop Deadline passes is implemented in sign_up_sheet_controller.rb where it is checked if the current time is greater than the time mentioned in Drop deadline. If the deadline has been passed, the 'update_is_waitlisted' method of SignedUpTeam model is called to delete all the waitlisted teams for that topic.
2. Changes are made in Assignments View to add an additional column for Drop-Topic Deadline for Staggered Deadlines Assignment. The code snippets for corresponding changes in controllers and models are as below:

(i) app/controllers/sign_up_sheet_controller.rb

if !topic_id1.nil? and !@drop_topic_deadline1.nil? and Time.now > @drop_topic_deadline1.due_at
SignedUpTeam.update_is_waitlisted(topic_id1.topic_id,team_id) end

(ii) The 'update_is_waitlisted' method is implemented in app/models/signed_up_team.rb as follows:

def self.update_is_waitlisted(topic_i)
topic_id1 = SignedUpTeam.where(team_id: team_id).first
if @assignment.staggered_deadline?
@drop_topic_deadline1 = TopicDueDate.where(parent_id: topic_id1.topic_id, deadline_type_id: 6).first rescue nil end
due_dates = params[:due_date]
topics = SignUpTopic.where(assignment_id: params[:assignment_id])
review_rounds = assignment.num_review_rounds
topics.each_with_index do |topic, index|
for i in 1..review_rounds
@topic_drop_topic_due_date = due_dates[topics[index].id.to_s + '_drop_topic_' + i.to_s + '_due_date']
if assignment.due_dates.select {|due_date| due_date.deadline_type_id == 6 }.nil?
@assignment_drop_topic_due_date = DateTime.parse(@assignment_drop_topic_due_dates[i - 1].due_at.to_s).strftime("%Y-%m-%d %H:%M")
end
end

(iii) app/helpers/sign_up_sheet_helper.rb

if assignment_due_dates.length == 0
assignment_due_dates = @assignment_submission_due_dates
end

(iv) app/models/student_task.rb

def self.get_due_date_data(assignment, timeline_list, participant)
if assignment.staggered_deadline?
team_id = participant.team.try(:id)
topic_id1 = SignedUpTeam.where(team_id: team_id).first
if !topic_id1.nil?
topic_due_date = TopicDueDate.where(parent_id: topic_id1.topic_id, deadline_type_id: 6).first rescue nil
timeline = {label: ('Drop Topic Deadline').humanize}
timeline[:updated_at] = topic_due_date.due_at.strftime('%a, %d %b %Y %H:%M')
timeline_list << timeline
end
end
assignment.due_dates.each do |dd|
timeline = {label: (dd.deadline_type.name + ' Deadline').humanize}
unless dd.due_at.nil?
timeline[:updated_at] = dd.due_at.strftime('%a, %d %b %Y %H:%M')
timeline_list << timeline
end
end
end

(v) app/views/assignments/edit.html.erb

<% if @assignment_form.assignment.staggered_deadline == true %>
<%= render partial: '/sign_up_sheet/add_signup_topics_staggered', locals: {review_rounds: @review_rounds, assignment_submission_due_dates: @assignment_submission_due_dates, assignment_review_due_dates: @assignment_review_due_dates, assignment_drop_topic_due_dates: @assignment_drop_topic_due_dates} %>
<% else %>
<%= render '/sign_up_sheet/add_signup_topics' %>
<% end %>

(vi) app/views/sign_up_sheet/_add_signup_topics_staggered.html.erb

<%= form_tag :controller => 'sign_up_sheet', :action => 'save_topic_deadlines', :assignment_id => @assignment.id do %>

 <%= render :partial => '/sign_up_sheet/due_dates', :locals => {review_rounds: review_rounds, assignment_submission_due_dates: assignment_submission_due_dates, assignment_review_due_dates: assignment_review_due_dates, assignment_drop_topic_due_dates: assignment_drop_topic_due_dates} %>
<% end %>

(vii) app/views/sign_up_sheet/_due_dates.html.erb

<tr>
<th>Drop deadline</th>
<%for i in 2..review_rounds%>
<td><%= @assignment.sign_up_topics[i].topic_name %></td>
<% for review_round in 1..review_rounds %>
<% topic_id = @assignment.sign_up_topics[i].id %>
<%if review_round == 1 %>
<td><%= text_field :due_date, (topic_id.to_s + '_drop_topic_' + review_round.to_s + '_due_date').to_s, size: 20, value: check_topic_due_date_value(assignment_drop_topic_due_dates, topic_id, 6, review_round) %></td>
<td><%= text_field :due_date, (topic_id.to_s + '_submission_' + review_round.to_s + '_due_date').to_s, size: 20, value: check_topic_due_date_value(assignment_submission_due_dates, topic_id, 1, review_round) %></td>
<td><%= text_field :due_date, (topic_id.to_s + '_review_' + review_round.to_s + '_due_date').to_s, size: 20, value: check_topic_due_date_value(assignment_review_due_dates, topic_id, 2, review_round) %></td>
<%else%>
<td><%= text_field :due_date, (topic_id.to_s + '_submission_' + review_round.to_s + '_due_date').to_s, size: 20, value: check_topic_due_date_value(assignment_submission_due_dates, topic_id, 1, review_round) %></td>
<td><%= text_field :due_date, (topic_id.to_s + '_review_' + review_round.to_s + '_due_date').to_s, size: 20, value: check_topic_due_date_value(assignment_review_due_dates, topic_id, 2, review_round) %></td> <%end%> <%end%>
</tr>
<%end%>

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

It was discussed that project does not require any Unit Test cases to be implemented as the changes are mostly visible in views.

== '''References''' ==

1. Expertiza on

2. GitHub Project Repository https://github.com/harshshah949494/expertiza[[Fork]]

3. The live Expertiza website

4. Demo link

5. Expertiza project documentation wiki

E1843 Issues Related To Deadlines

2018-11-09T23:57:09Z

Hshah3:

This wiki page is for the description of changes made under E1843- Issues Related to Topic Deadlines OSS assignment for Fall 2018, CSC/ECE 517.

== '''About Expertiza''' ==

Expertiza is an open source project based on Ruby on Rails framework and the code is available on Github. Expertiza allows the instructor to create new assignments as well as edit new or existing assignments. Instructors can also create a list of topics the students can sign up for and specify deadlines for completion of various tasks. Students can form teams in Expertiza to work on various projects and assignments as well as peer review other students' submissions. Expertiza supports submission across various document types, including the URLs Wiki pages.

== '''Issues in the Current Project''' ==

1.There is no deadline that specifies when a team can drop their topics. Due to this, few problems occur: The team might drop a topic later on which is close to the submission date and this results in topic not being assigned to any other team on time such that they can submit their assignment. Also, if one team was wait listed for the same topic which the other team dropped closer to the submission deadline, then the first wait-listed team will be assigned to the dropped topic which is not desirable as they might be working on their assigned topic for long time.

2.There are different topics on which students can work during different times. This type of assignment is known as Staggered- deadline assignment in which different topics have different submission and review deadlines. For these assignments too, there is a need for "Drop Topics Deadline". In the current implementation, the drop topic deadline is same for all the topics in a Staggered Deadline assignment which is not desirable.

== '''Corrections made in the New Project''' ==

1. The instructor can specify a Drop Topic deadline date now. After a drop topic deadline passes, the "X"(signup option) in the Sign-Up sheet disables so that the student cannot drop the topic and the wait-list for that topic is cleared, which will resolve the issue of the topic being assigned to a wait-listed team very close to the submission deadline.

2. Staggered deadline assignments now have different drop deadlines for different topics in that assignment.The above resolution also works for Staggered Deadlines Assignment

== '''Files modified in Current Project''' ==

1. app/controllers/assignments_controller.rb

2. app/controllers/sign_up_sheet_controller.rb

3. app/models/student_task.rb

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

5. app/views/sign_up_sheet/_add_signup_topics_staggered.html.erb

6. app/views/sign_up_sheet/_due_dates.html.erb

== '''Current Implementation''' ==

1. Clearing the waitlist after Drop Deadline passes is implemented in sign_up_sheet_controller.rb where it is checked if the current time is greater than the time mentioned in Drop deadline. If the deadline has been passed, the 'update_is_waitlisted' method of SignedUpTeam model is called to delete all the waitlisted teams for that topic.
2. Changes are made in Assignments View to add an additional column for Drop-Topic Deadline for Staggered Deadlines Assignment. The code snippets for corresponding changes in controllers and models are as below:

(i) app/controllers/sign_up_sheet_controller.rb

if !topic_id1.nil? and !@drop_topic_deadline1.nil? and Time.now > @drop_topic_deadline1.due_at
SignedUpTeam.update_is_waitlisted(topic_id1.topic_id,team_id) end

(ii) The 'update_is_waitlisted' method is implemented in app/models/signed_up_team.rb as follows:

def self.update_is_waitlisted(topic_i)
topic_id1 = SignedUpTeam.where(team_id: team_id).first
if @assignment.staggered_deadline?
@drop_topic_deadline1 = TopicDueDate.where(parent_id: topic_id1.topic_id, deadline_type_id: 6).first rescue nil end
due_dates = params[:due_date]
topics = SignUpTopic.where(assignment_id: params[:assignment_id])
review_rounds = assignment.num_review_rounds
topics.each_with_index do |topic, index|
for i in 1..review_rounds
@topic_drop_topic_due_date = due_dates[topics[index].id.to_s + '_drop_topic_' + i.to_s + '_due_date']
if assignment.due_dates.select {|due_date| due_date.deadline_type_id == 6 }.nil?
@assignment_drop_topic_due_date = DateTime.parse(@assignment_drop_topic_due_dates[i - 1].due_at.to_s).strftime("%Y-%m-%d %H:%M")
end
end

(iii) app/helpers/sign_up_sheet_helper.rb

if assignment_due_dates.length == 0
assignment_due_dates = @assignment_submission_due_dates
end

(iv) app/models/student_task.rb

def self.get_due_date_data(assignment, timeline_list, participant)
if assignment.staggered_deadline?
team_id = participant.team.try(:id)
topic_id1 = SignedUpTeam.where(team_id: team_id).first
if !topic_id1.nil?
topic_due_date = TopicDueDate.where(parent_id: topic_id1.topic_id, deadline_type_id: 6).first rescue nil
timeline = {label: ('Drop Topic Deadline').humanize}
timeline[:updated_at] = topic_due_date.due_at.strftime('%a, %d %b %Y %H:%M')
timeline_list << timeline
end
end
assignment.due_dates.each do |dd|
timeline = {label: (dd.deadline_type.name + ' Deadline').humanize}
unless dd.due_at.nil?
timeline[:updated_at] = dd.due_at.strftime('%a, %d %b %Y %H:%M')
timeline_list << timeline
end
end
end

(v) app/views/assignments/edit.html.erb

<% if @assignment_form.assignment.staggered_deadline == true %>
<%= render partial: '/sign_up_sheet/add_signup_topics_staggered', locals: {review_rounds: @review_rounds, assignment_submission_due_dates: @assignment_submission_due_dates, assignment_review_due_dates: @assignment_review_due_dates, assignment_drop_topic_due_dates: @assignment_drop_topic_due_dates} %>
<% else %>
<%= render '/sign_up_sheet/add_signup_topics' %>
<% end %>

(vi) app/views/sign_up_sheet/_add_signup_topics_staggered.html.erb

<%= form_tag :controller => 'sign_up_sheet', :action => 'save_topic_deadlines', :assignment_id => @assignment.id do %>

 <%= render :partial => '/sign_up_sheet/due_dates', :locals => {review_rounds: review_rounds, assignment_submission_due_dates: assignment_submission_due_dates, assignment_review_due_dates: assignment_review_due_dates, assignment_drop_topic_due_dates: assignment_drop_topic_due_dates} %>
<% end %>

(vii) app/views/sign_up_sheet/_due_dates.html.erb

<tr>
<th>Drop deadline</th>
<%for i in 2..review_rounds%>
<td><%= @assignment.sign_up_topics[i].topic_name %></td>
<% for review_round in 1..review_rounds %>
<% topic_id = @assignment.sign_up_topics[i].id %>
<%if review_round == 1 %>
<td><%= text_field :due_date, (topic_id.to_s + '_drop_topic_' + review_round.to_s + '_due_date').to_s, size: 20, value: check_topic_due_date_value(assignment_drop_topic_due_dates, topic_id, 6, review_round) %></td>
<td><%= text_field :due_date, (topic_id.to_s + '_submission_' + review_round.to_s + '_due_date').to_s, size: 20, value: check_topic_due_date_value(assignment_submission_due_dates, topic_id, 1, review_round) %></td>
<td><%= text_field :due_date, (topic_id.to_s + '_review_' + review_round.to_s + '_due_date').to_s, size: 20, value: check_topic_due_date_value(assignment_review_due_dates, topic_id, 2, review_round) %></td>
<%else%>
<td><%= text_field :due_date, (topic_id.to_s + '_submission_' + review_round.to_s + '_due_date').to_s, size: 20, value: check_topic_due_date_value(assignment_submission_due_dates, topic_id, 1, review_round) %></td>
<td><%= text_field :due_date, (topic_id.to_s + '_review_' + review_round.to_s + '_due_date').to_s, size: 20, value: check_topic_due_date_value(assignment_review_due_dates, topic_id, 2, review_round) %></td> <%end%> <%end%>
</tr>
<%end%>

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

It was discussed that project does not require any Unit Test cases to be implemented as the changes are mostly visible in views.

== '''References''' ==

1. Expertiza on GitHub

2. GitHub Project Repository Fork

3. The live Expertiza website

4. Demo link

5. Expertiza project documentation wiki

E1843 Issues Related To Deadlines

2018-11-09T23:53:42Z

Hshah3: /* Issues in the Current Project */

This wiki page is for the description of changes made under E1843 OSS assignment for Fall 2018, CSC/ECE 517.

== '''About Expertiza''' ==

Expertiza is an open source project based on Ruby on Rails framework and the code is available on Github. Expertiza allows the instructor to create new assignments as well as edit new or existing assignments. Instructors can also create a list of topics the students can sign up for and specify deadlines for completion of various tasks. Students can form teams in Expertiza to work on various projects and assignments as well as peer review other students' submissions. Expertiza supports submission across various document types, including the URLs Wiki pages.

== '''Issues in the Current Project''' ==

1.There is no deadline that specifies when a team can drop their topics. Due to this, few problems occur: The team might drop a topic later on which is close to the submission date and this results in topic not being assigned to any other team on time such that they can submit their assignment. Also, if one team was wait listed for the same topic which the other team dropped closer to the submission deadline, then the first wait-listed team will be assigned to the dropped topic which is not desirable as they might be working on their assigned topic for long time.

2.There are different topics on which students can work during different times. This type of assignment is known as Staggered- deadline assignment in which different topics have different submission and review deadlines. For these assignments too, there is a need for "Drop Topics Deadline". In the current implementation, the drop topic deadline is same for all the topics in a Staggered Deadline assignment which is not desirable.

== '''Corrections made in the New Project''' ==

1. The instructor can specify a Drop Topic deadline date now. After a drop topic deadline passes, the "X"(signup option) in the Sign-Up sheet disables so that the student cannot drop the topic and the wait-list for that topic is cleared, which will resolve the issue of the topic being assigned to a wait-listed team very close to the submission deadline.

2. Staggered deadline assignments now have different drop deadlines for different topics in that assignment.The above resolution also works for Staggered Deadlines Assignment

== '''Files modified in Current Project''' ==

1. app/controllers/assignments_controller.rb

2. app/controllers/sign_up_sheet_controller.rb

3. app/models/student_task.rb

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

5. app/views/sign_up_sheet/_add_signup_topics_staggered.html.erb

6. app/views/sign_up_sheet/_due_dates.html.erb

== '''Current Implementation''' ==

1. Clearing the waitlist after Drop Deadline passes is implemented in sign_up_sheet_controller.rb where it is checked if the current time is greater than the time mentioned in Drop deadline. If the deadline has been passed, the 'update_is_waitlisted' method of SignedUpTeam model is called to delete all the waitlisted teams for that topic.
2. Changes are made in Assignments View to add an additional column for Drop-Topic Deadline for Staggered Deadlines Assignment. The code snippets for corresponding changes in controllers and models are as below:

(i) app/controllers/sign_up_sheet_controller.rb

if !topic_id1.nil? and !@drop_topic_deadline1.nil? and Time.now > @drop_topic_deadline1.due_at
SignedUpTeam.update_is_waitlisted(topic_id1.topic_id,team_id) end

(ii) The 'update_is_waitlisted' method is implemented in app/models/signed_up_team.rb as follows:

def self.update_is_waitlisted(topic_i)
topic_id1 = SignedUpTeam.where(team_id: team_id).first
if @assignment.staggered_deadline?
@drop_topic_deadline1 = TopicDueDate.where(parent_id: topic_id1.topic_id, deadline_type_id: 6).first rescue nil end
due_dates = params[:due_date]
topics = SignUpTopic.where(assignment_id: params[:assignment_id])
review_rounds = assignment.num_review_rounds
topics.each_with_index do |topic, index|
for i in 1..review_rounds
@topic_drop_topic_due_date = due_dates[topics[index].id.to_s + '_drop_topic_' + i.to_s + '_due_date']
if assignment.due_dates.select {|due_date| due_date.deadline_type_id == 6 }.nil?
@assignment_drop_topic_due_date = DateTime.parse(@assignment_drop_topic_due_dates[i - 1].due_at.to_s).strftime("%Y-%m-%d %H:%M")
end
end

(iii) app/helpers/sign_up_sheet_helper.rb

if assignment_due_dates.length == 0
assignment_due_dates = @assignment_submission_due_dates
end

(iv) app/models/student_task.rb

def self.get_due_date_data(assignment, timeline_list, participant)
if assignment.staggered_deadline?
team_id = participant.team.try(:id)
topic_id1 = SignedUpTeam.where(team_id: team_id).first
if !topic_id1.nil?
topic_due_date = TopicDueDate.where(parent_id: topic_id1.topic_id, deadline_type_id: 6).first rescue nil
timeline = {label: ('Drop Topic Deadline').humanize}
timeline[:updated_at] = topic_due_date.due_at.strftime('%a, %d %b %Y %H:%M')
timeline_list << timeline
end
end
assignment.due_dates.each do |dd|
timeline = {label: (dd.deadline_type.name + ' Deadline').humanize}
unless dd.due_at.nil?
timeline[:updated_at] = dd.due_at.strftime('%a, %d %b %Y %H:%M')
timeline_list << timeline
end
end
end

(v) app/views/assignments/edit.html.erb

<% if @assignment_form.assignment.staggered_deadline == true %>
<%= render partial: '/sign_up_sheet/add_signup_topics_staggered', locals: {review_rounds: @review_rounds, assignment_submission_due_dates: @assignment_submission_due_dates, assignment_review_due_dates: @assignment_review_due_dates, assignment_drop_topic_due_dates: @assignment_drop_topic_due_dates} %>
<% else %>
<%= render '/sign_up_sheet/add_signup_topics' %>
<% end %>

(vi) app/views/sign_up_sheet/_add_signup_topics_staggered.html.erb

<%= form_tag :controller => 'sign_up_sheet', :action => 'save_topic_deadlines', :assignment_id => @assignment.id do %>

 <%= render :partial => '/sign_up_sheet/due_dates', :locals => {review_rounds: review_rounds, assignment_submission_due_dates: assignment_submission_due_dates, assignment_review_due_dates: assignment_review_due_dates, assignment_drop_topic_due_dates: assignment_drop_topic_due_dates} %>
<% end %>

(vii) app/views/sign_up_sheet/_due_dates.html.erb

<tr>
<th>Drop deadline</th>
<%for i in 2..review_rounds%>
<td><%= @assignment.sign_up_topics[i].topic_name %></td>
<% for review_round in 1..review_rounds %>
<% topic_id = @assignment.sign_up_topics[i].id %>
<%if review_round == 1 %>
<td><%= text_field :due_date, (topic_id.to_s + '_drop_topic_' + review_round.to_s + '_due_date').to_s, size: 20, value: check_topic_due_date_value(assignment_drop_topic_due_dates, topic_id, 6, review_round) %></td>
<td><%= text_field :due_date, (topic_id.to_s + '_submission_' + review_round.to_s + '_due_date').to_s, size: 20, value: check_topic_due_date_value(assignment_submission_due_dates, topic_id, 1, review_round) %></td>
<td><%= text_field :due_date, (topic_id.to_s + '_review_' + review_round.to_s + '_due_date').to_s, size: 20, value: check_topic_due_date_value(assignment_review_due_dates, topic_id, 2, review_round) %></td>
<%else%>
<td><%= text_field :due_date, (topic_id.to_s + '_submission_' + review_round.to_s + '_due_date').to_s, size: 20, value: check_topic_due_date_value(assignment_submission_due_dates, topic_id, 1, review_round) %></td>
<td><%= text_field :due_date, (topic_id.to_s + '_review_' + review_round.to_s + '_due_date').to_s, size: 20, value: check_topic_due_date_value(assignment_review_due_dates, topic_id, 2, review_round) %></td> <%end%> <%end%>
</tr>
<%end%>

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

It was discussed that project does not require any Unit Test cases to be implemented as the changes are mostly visible in views.

== '''References''' ==

1. Expertiza on GitHub

2. GitHub Project Repository Fork

3. The live Expertiza website

4. Demo link

5. Expertiza project documentation wiki

E1843 Issues Related To Deadlines

2018-11-09T23:51:37Z

Hshah3: /* Test Plan */

This wiki page is for the description of changes made under E1843 OSS assignment for Fall 2018, CSC/ECE 517.

== '''About Expertiza''' ==

Expertiza is an open source project based on Ruby on Rails framework and the code is available on Github. Expertiza allows the instructor to create new assignments as well as edit new or existing assignments. Instructors can also create a list of topics the students can sign up for and specify deadlines for completion of various tasks. Students can form teams in Expertiza to work on various projects and assignments as well as peer review other students' submissions. Expertiza supports submission across various document types, including the URLs Wiki pages.

== '''Issues in the Current Project''' ==

1.There is no deadline that specifies when a team can drop their topics. Due to this, few problems occur: The team might drop a topic later on which is close to the submission date and this results in topic not being assigned to any other team on time such that they can submit their assignment. Also, if one team was wait listed for the same topic which the other team dropped closer to the submission deadline, then the first team will be assigned to the dropped topic which is not desirable as they might be working on their assigned topic for long time.

2.There are different topics on which students can work during different times. This type of assignment is known as Staggered- deadline assignment in which different topics have different submission and review deadlines. For these assignments too, there is a need for "Drop Topics Deadline". In the current implementation, the drop topic deadline is same for all the topics in a Staggered Deadline assignment which is not desirable.

== '''Corrections made in the New Project''' ==

1. The instructor can specify a Drop Topic deadline date now. After a drop topic deadline passes, the "X"(signup option) in the Sign-Up sheet disables so that the student cannot drop the topic and the wait-list for that topic is cleared, which will resolve the issue of the topic being assigned to a wait-listed team very close to the submission deadline.

2. Staggered deadline assignments now have different drop deadlines for different topics in that assignment.The above resolution also works for Staggered Deadlines Assignment

== '''Files modified in Current Project''' ==

1. app/controllers/assignments_controller.rb

2. app/controllers/sign_up_sheet_controller.rb

3. app/models/student_task.rb

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

5. app/views/sign_up_sheet/_add_signup_topics_staggered.html.erb

6. app/views/sign_up_sheet/_due_dates.html.erb

== '''Current Implementation''' ==

1. Clearing the waitlist after Drop Deadline passes is implemented in sign_up_sheet_controller.rb where it is checked if the current time is greater than the time mentioned in Drop deadline. If the deadline has been passed, the 'update_is_waitlisted' method of SignedUpTeam model is called to delete all the waitlisted teams for that topic.
2. Changes are made in Assignments View to add an additional column for Drop-Topic Deadline for Staggered Deadlines Assignment. The code snippets for corresponding changes in controllers and models are as below:

(i) app/controllers/sign_up_sheet_controller.rb

if !topic_id1.nil? and !@drop_topic_deadline1.nil? and Time.now > @drop_topic_deadline1.due_at
SignedUpTeam.update_is_waitlisted(topic_id1.topic_id,team_id) end

(ii) The 'update_is_waitlisted' method is implemented in app/models/signed_up_team.rb as follows:

def self.update_is_waitlisted(topic_i)
topic_id1 = SignedUpTeam.where(team_id: team_id).first
if @assignment.staggered_deadline?
@drop_topic_deadline1 = TopicDueDate.where(parent_id: topic_id1.topic_id, deadline_type_id: 6).first rescue nil end
due_dates = params[:due_date]
topics = SignUpTopic.where(assignment_id: params[:assignment_id])
review_rounds = assignment.num_review_rounds
topics.each_with_index do |topic, index|
for i in 1..review_rounds
@topic_drop_topic_due_date = due_dates[topics[index].id.to_s + '_drop_topic_' + i.to_s + '_due_date']
if assignment.due_dates.select {|due_date| due_date.deadline_type_id == 6 }.nil?
@assignment_drop_topic_due_date = DateTime.parse(@assignment_drop_topic_due_dates[i - 1].due_at.to_s).strftime("%Y-%m-%d %H:%M")
end
end

(iii) app/helpers/sign_up_sheet_helper.rb

if assignment_due_dates.length == 0
assignment_due_dates = @assignment_submission_due_dates
end

(iv) app/models/student_task.rb

def self.get_due_date_data(assignment, timeline_list, participant)
if assignment.staggered_deadline?
team_id = participant.team.try(:id)
topic_id1 = SignedUpTeam.where(team_id: team_id).first
if !topic_id1.nil?
topic_due_date = TopicDueDate.where(parent_id: topic_id1.topic_id, deadline_type_id: 6).first rescue nil
timeline = {label: ('Drop Topic Deadline').humanize}
timeline[:updated_at] = topic_due_date.due_at.strftime('%a, %d %b %Y %H:%M')
timeline_list << timeline
end
end
assignment.due_dates.each do |dd|
timeline = {label: (dd.deadline_type.name + ' Deadline').humanize}
unless dd.due_at.nil?
timeline[:updated_at] = dd.due_at.strftime('%a, %d %b %Y %H:%M')
timeline_list << timeline
end
end
end

(v) app/views/assignments/edit.html.erb

<% if @assignment_form.assignment.staggered_deadline == true %>
<%= render partial: '/sign_up_sheet/add_signup_topics_staggered', locals: {review_rounds: @review_rounds, assignment_submission_due_dates: @assignment_submission_due_dates, assignment_review_due_dates: @assignment_review_due_dates, assignment_drop_topic_due_dates: @assignment_drop_topic_due_dates} %>
<% else %>
<%= render '/sign_up_sheet/add_signup_topics' %>
<% end %>

(vi) app/views/sign_up_sheet/_add_signup_topics_staggered.html.erb

<%= form_tag :controller => 'sign_up_sheet', :action => 'save_topic_deadlines', :assignment_id => @assignment.id do %>

 <%= render :partial => '/sign_up_sheet/due_dates', :locals => {review_rounds: review_rounds, assignment_submission_due_dates: assignment_submission_due_dates, assignment_review_due_dates: assignment_review_due_dates, assignment_drop_topic_due_dates: assignment_drop_topic_due_dates} %>
<% end %>

(vii) app/views/sign_up_sheet/_due_dates.html.erb

<tr>
<th>Drop deadline</th>
<%for i in 2..review_rounds%>
<td><%= @assignment.sign_up_topics[i].topic_name %></td>
<% for review_round in 1..review_rounds %>
<% topic_id = @assignment.sign_up_topics[i].id %>
<%if review_round == 1 %>
<td><%= text_field :due_date, (topic_id.to_s + '_drop_topic_' + review_round.to_s + '_due_date').to_s, size: 20, value: check_topic_due_date_value(assignment_drop_topic_due_dates, topic_id, 6, review_round) %></td>
<td><%= text_field :due_date, (topic_id.to_s + '_submission_' + review_round.to_s + '_due_date').to_s, size: 20, value: check_topic_due_date_value(assignment_submission_due_dates, topic_id, 1, review_round) %></td>
<td><%= text_field :due_date, (topic_id.to_s + '_review_' + review_round.to_s + '_due_date').to_s, size: 20, value: check_topic_due_date_value(assignment_review_due_dates, topic_id, 2, review_round) %></td>
<%else%>
<td><%= text_field :due_date, (topic_id.to_s + '_submission_' + review_round.to_s + '_due_date').to_s, size: 20, value: check_topic_due_date_value(assignment_submission_due_dates, topic_id, 1, review_round) %></td>
<td><%= text_field :due_date, (topic_id.to_s + '_review_' + review_round.to_s + '_due_date').to_s, size: 20, value: check_topic_due_date_value(assignment_review_due_dates, topic_id, 2, review_round) %></td> <%end%> <%end%>
</tr>
<%end%>

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

It was discussed that project does not require any Unit Test cases to be implemented as the changes are mostly visible in views.

== '''References''' ==

1. Expertiza on GitHub

2. GitHub Project Repository Fork

3. The live Expertiza website

4. Demo link

5. Expertiza project documentation wiki

E1843 Issues Related To Deadlines

2018-11-09T23:50:29Z

Hshah3: /* Current Implementation */

This wiki page is for the description of changes made under E1843 OSS assignment for Fall 2018, CSC/ECE 517.

== '''About Expertiza''' ==

Expertiza is an open source project based on Ruby on Rails framework and the code is available on Github. Expertiza allows the instructor to create new assignments as well as edit new or existing assignments. Instructors can also create a list of topics the students can sign up for and specify deadlines for completion of various tasks. Students can form teams in Expertiza to work on various projects and assignments as well as peer review other students' submissions. Expertiza supports submission across various document types, including the URLs Wiki pages.

== '''Issues in the Current Project''' ==

1.There is no deadline that specifies when a team can drop their topics. Due to this, few problems occur: The team might drop a topic later on which is close to the submission date and this results in topic not being assigned to any other team on time such that they can submit their assignment. Also, if one team was wait listed for the same topic which the other team dropped closer to the submission deadline, then the first team will be assigned to the dropped topic which is not desirable as they might be working on their assigned topic for long time.

2.There are different topics on which students can work during different times. This type of assignment is known as Staggered- deadline assignment in which different topics have different submission and review deadlines. For these assignments too, there is a need for "Drop Topics Deadline". In the current implementation, the drop topic deadline is same for all the topics in a Staggered Deadline assignment which is not desirable.

== '''Corrections made in the New Project''' ==

1. The instructor can specify a Drop Topic deadline date now. After a drop topic deadline passes, the "X"(signup option) in the Sign-Up sheet disables so that the student cannot drop the topic and the wait-list for that topic is cleared, which will resolve the issue of the topic being assigned to a wait-listed team very close to the submission deadline.

2. Staggered deadline assignments now have different drop deadlines for different topics in that assignment.The above resolution also works for Staggered Deadlines Assignment

== '''Files modified in Current Project''' ==

1. app/controllers/assignments_controller.rb

2. app/controllers/sign_up_sheet_controller.rb

3. app/models/student_task.rb

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

5. app/views/sign_up_sheet/_add_signup_topics_staggered.html.erb

6. app/views/sign_up_sheet/_due_dates.html.erb

== '''Current Implementation''' ==

1. Clearing the waitlist after Drop Deadline passes is implemented in sign_up_sheet_controller.rb where it is checked if the current time is greater than the time mentioned in Drop deadline. If the deadline has been passed, the 'update_is_waitlisted' method of SignedUpTeam model is called to delete all the waitlisted teams for that topic.
2. Changes are made in Assignments View to add an additional column for Drop-Topic Deadline for Staggered Deadlines Assignment. The code snippets for corresponding changes in controllers and models are as below:

(i) app/controllers/sign_up_sheet_controller.rb

if !topic_id1.nil? and !@drop_topic_deadline1.nil? and Time.now > @drop_topic_deadline1.due_at
SignedUpTeam.update_is_waitlisted(topic_id1.topic_id,team_id) end

(ii) The 'update_is_waitlisted' method is implemented in app/models/signed_up_team.rb as follows:

def self.update_is_waitlisted(topic_i)
topic_id1 = SignedUpTeam.where(team_id: team_id).first
if @assignment.staggered_deadline?
@drop_topic_deadline1 = TopicDueDate.where(parent_id: topic_id1.topic_id, deadline_type_id: 6).first rescue nil end
due_dates = params[:due_date]
topics = SignUpTopic.where(assignment_id: params[:assignment_id])
review_rounds = assignment.num_review_rounds
topics.each_with_index do |topic, index|
for i in 1..review_rounds
@topic_drop_topic_due_date = due_dates[topics[index].id.to_s + '_drop_topic_' + i.to_s + '_due_date']
if assignment.due_dates.select {|due_date| due_date.deadline_type_id == 6 }.nil?
@assignment_drop_topic_due_date = DateTime.parse(@assignment_drop_topic_due_dates[i - 1].due_at.to_s).strftime("%Y-%m-%d %H:%M")
end
end

(iii) app/helpers/sign_up_sheet_helper.rb

if assignment_due_dates.length == 0
assignment_due_dates = @assignment_submission_due_dates
end

(iv) app/models/student_task.rb

def self.get_due_date_data(assignment, timeline_list, participant)
if assignment.staggered_deadline?
team_id = participant.team.try(:id)
topic_id1 = SignedUpTeam.where(team_id: team_id).first
if !topic_id1.nil?
topic_due_date = TopicDueDate.where(parent_id: topic_id1.topic_id, deadline_type_id: 6).first rescue nil
timeline = {label: ('Drop Topic Deadline').humanize}
timeline[:updated_at] = topic_due_date.due_at.strftime('%a, %d %b %Y %H:%M')
timeline_list << timeline
end
end
assignment.due_dates.each do |dd|
timeline = {label: (dd.deadline_type.name + ' Deadline').humanize}
unless dd.due_at.nil?
timeline[:updated_at] = dd.due_at.strftime('%a, %d %b %Y %H:%M')
timeline_list << timeline
end
end
end

(v) app/views/assignments/edit.html.erb

<% if @assignment_form.assignment.staggered_deadline == true %>
<%= render partial: '/sign_up_sheet/add_signup_topics_staggered', locals: {review_rounds: @review_rounds, assignment_submission_due_dates: @assignment_submission_due_dates, assignment_review_due_dates: @assignment_review_due_dates, assignment_drop_topic_due_dates: @assignment_drop_topic_due_dates} %>
<% else %>
<%= render '/sign_up_sheet/add_signup_topics' %>
<% end %>

(vi) app/views/sign_up_sheet/_add_signup_topics_staggered.html.erb

<%= form_tag :controller => 'sign_up_sheet', :action => 'save_topic_deadlines', :assignment_id => @assignment.id do %>

 <%= render :partial => '/sign_up_sheet/due_dates', :locals => {review_rounds: review_rounds, assignment_submission_due_dates: assignment_submission_due_dates, assignment_review_due_dates: assignment_review_due_dates, assignment_drop_topic_due_dates: assignment_drop_topic_due_dates} %>
<% end %>

(vii) app/views/sign_up_sheet/_due_dates.html.erb

<tr>
<th>Drop deadline</th>
<%for i in 2..review_rounds%>
<td><%= @assignment.sign_up_topics[i].topic_name %></td>
<% for review_round in 1..review_rounds %>
<% topic_id = @assignment.sign_up_topics[i].id %>
<%if review_round == 1 %>
<td><%= text_field :due_date, (topic_id.to_s + '_drop_topic_' + review_round.to_s + '_due_date').to_s, size: 20, value: check_topic_due_date_value(assignment_drop_topic_due_dates, topic_id, 6, review_round) %></td>
<td><%= text_field :due_date, (topic_id.to_s + '_submission_' + review_round.to_s + '_due_date').to_s, size: 20, value: check_topic_due_date_value(assignment_submission_due_dates, topic_id, 1, review_round) %></td>
<td><%= text_field :due_date, (topic_id.to_s + '_review_' + review_round.to_s + '_due_date').to_s, size: 20, value: check_topic_due_date_value(assignment_review_due_dates, topic_id, 2, review_round) %></td>
<%else%>
<td><%= text_field :due_date, (topic_id.to_s + '_submission_' + review_round.to_s + '_due_date').to_s, size: 20, value: check_topic_due_date_value(assignment_submission_due_dates, topic_id, 1, review_round) %></td>
<td><%= text_field :due_date, (topic_id.to_s + '_review_' + review_round.to_s + '_due_date').to_s, size: 20, value: check_topic_due_date_value(assignment_review_due_dates, topic_id, 2, review_round) %></td> <%end%> <%end%>
</tr>
<%end%>

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

The project does not require any Unit Test cases to be implemented.

== '''References''' ==

1. Expertiza on GitHub

2. GitHub Project Repository Fork

3. The live Expertiza website

4. Demo link

5. Expertiza project documentation wiki

E1843 Issues Related To Deadlines

2018-11-09T23:45:37Z

Hshah3: /* Corrections made in the New Project */

This wiki page is for the description of changes made under E1843 OSS assignment for Fall 2018, CSC/ECE 517.

== '''About Expertiza''' ==

Expertiza is an open source project based on Ruby on Rails framework and the code is available on Github. Expertiza allows the instructor to create new assignments as well as edit new or existing assignments. Instructors can also create a list of topics the students can sign up for and specify deadlines for completion of various tasks. Students can form teams in Expertiza to work on various projects and assignments as well as peer review other students' submissions. Expertiza supports submission across various document types, including the URLs Wiki pages.

== '''Issues in the Current Project''' ==

1.There is no deadline that specifies when a team can drop their topics. Due to this, few problems occur: The team might drop a topic later on which is close to the submission date and this results in topic not being assigned to any other team on time such that they can submit their assignment. Also, if one team was wait listed for the same topic which the other team dropped closer to the submission deadline, then the first team will be assigned to the dropped topic which is not desirable as they might be working on their assigned topic for long time.

2.There are different topics on which students can work during different times. This type of assignment is known as Staggered- deadline assignment in which different topics have different submission and review deadlines. For these assignments too, there is a need for "Drop Topics Deadline". In the current implementation, the drop topic deadline is same for all the topics in a Staggered Deadline assignment which is not desirable.

== '''Corrections made in the New Project''' ==

1. The instructor can specify a Drop Topic deadline date now. After a drop topic deadline passes, the "X"(signup option) in the Sign-Up sheet disables so that the student cannot drop the topic and the wait-list for that topic is cleared, which will resolve the issue of the topic being assigned to a wait-listed team very close to the submission deadline.

2. Staggered deadline assignments now have different drop deadlines for different topics in that assignment.The above resolution also works for Staggered Deadlines Assignment

== '''Files modified in Current Project''' ==

1. app/controllers/assignments_controller.rb

2. app/controllers/sign_up_sheet_controller.rb

3. app/models/student_task.rb

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

5. app/views/sign_up_sheet/_add_signup_topics_staggered.html.erb

6. app/views/sign_up_sheet/_due_dates.html.erb

== '''Current Implementation''' ==

1. Clearing the waitlist after Drop Deadline passes is implemented in sign_up_sheet_controller.rb where it is checked if the current time is greater than the time mentioned in Drop deadline. If the deadline has been passed, the 'update_is_waitlisted' method of SignedUpTeam model is called to delete all the waitlisted teams. The code snippets for the changes made are attached below:

(i) app/controllers/sign_up_sheet_controller.rb

if !topic_id1.nil? and !@drop_topic_deadline1.nil? and Time.now > @drop_topic_deadline1.due_at
SignedUpTeam.update_is_waitlisted(topic_id1.topic_id,team_id) end

(ii) The 'update_is_waitlisted' method is implemented in app/models/signed_up_team.rb as follows:

def self.update_is_waitlisted(topic_i)
topic_id1 = SignedUpTeam.where(team_id: team_id).first
if @assignment.staggered_deadline?
@drop_topic_deadline1 = TopicDueDate.where(parent_id: topic_id1.topic_id, deadline_type_id: 6).first rescue nil end
due_dates = params[:due_date]
topics = SignUpTopic.where(assignment_id: params[:assignment_id])
review_rounds = assignment.num_review_rounds
topics.each_with_index do |topic, index|
for i in 1..review_rounds
@topic_drop_topic_due_date = due_dates[topics[index].id.to_s + '_drop_topic_' + i.to_s + '_due_date']
if assignment.due_dates.select {|due_date| due_date.deadline_type_id == 6 }.nil?
@assignment_drop_topic_due_date = DateTime.parse(@assignment_drop_topic_due_dates[i - 1].due_at.to_s).strftime("%Y-%m-%d %H:%M")
end
end

(iii) app/helpers/sign_up_sheet_helper.rb

if assignment_due_dates.length == 0
assignment_due_dates = @assignment_submission_due_dates
end

(iv) app/models/student_task.rb

def self.get_due_date_data(assignment, timeline_list, participant)
if assignment.staggered_deadline?
team_id = participant.team.try(:id)
topic_id1 = SignedUpTeam.where(team_id: team_id).first
if !topic_id1.nil?
topic_due_date = TopicDueDate.where(parent_id: topic_id1.topic_id, deadline_type_id: 6).first rescue nil
timeline = {label: ('Drop Topic Deadline').humanize}
timeline[:updated_at] = topic_due_date.due_at.strftime('%a, %d %b %Y %H:%M')
timeline_list << timeline
end
end
assignment.due_dates.each do |dd|
timeline = {label: (dd.deadline_type.name + ' Deadline').humanize}
unless dd.due_at.nil?
timeline[:updated_at] = dd.due_at.strftime('%a, %d %b %Y %H:%M')
timeline_list << timeline
end
end
end

(v) app/views/assignments/edit.html.erb

<% if @assignment_form.assignment.staggered_deadline == true %>
<%= render partial: '/sign_up_sheet/add_signup_topics_staggered', locals: {review_rounds: @review_rounds, assignment_submission_due_dates: @assignment_submission_due_dates, assignment_review_due_dates: @assignment_review_due_dates, assignment_drop_topic_due_dates: @assignment_drop_topic_due_dates} %>
<% else %>
<%= render '/sign_up_sheet/add_signup_topics' %>
<% end %>

(vi) app/views/sign_up_sheet/_add_signup_topics_staggered.html.erb

<%= form_tag :controller => 'sign_up_sheet', :action => 'save_topic_deadlines', :assignment_id => @assignment.id do %>

 <%= render :partial => '/sign_up_sheet/due_dates', :locals => {review_rounds: review_rounds, assignment_submission_due_dates: assignment_submission_due_dates, assignment_review_due_dates: assignment_review_due_dates, assignment_drop_topic_due_dates: assignment_drop_topic_due_dates} %>
<% end %>

(vii) app/views/sign_up_sheet/_due_dates.html.erb

<tr>
<th>Drop deadline</th>
<%for i in 2..review_rounds%>
<td><%= @assignment.sign_up_topics[i].topic_name %></td>
<% for review_round in 1..review_rounds %>
<% topic_id = @assignment.sign_up_topics[i].id %>
<%if review_round == 1 %>
<td><%= text_field :due_date, (topic_id.to_s + '_drop_topic_' + review_round.to_s + '_due_date').to_s, size: 20, value: check_topic_due_date_value(assignment_drop_topic_due_dates, topic_id, 6, review_round) %></td>
<td><%= text_field :due_date, (topic_id.to_s + '_submission_' + review_round.to_s + '_due_date').to_s, size: 20, value: check_topic_due_date_value(assignment_submission_due_dates, topic_id, 1, review_round) %></td>
<td><%= text_field :due_date, (topic_id.to_s + '_review_' + review_round.to_s + '_due_date').to_s, size: 20, value: check_topic_due_date_value(assignment_review_due_dates, topic_id, 2, review_round) %></td>
<%else%>
<td><%= text_field :due_date, (topic_id.to_s + '_submission_' + review_round.to_s + '_due_date').to_s, size: 20, value: check_topic_due_date_value(assignment_submission_due_dates, topic_id, 1, review_round) %></td>
<td><%= text_field :due_date, (topic_id.to_s + '_review_' + review_round.to_s + '_due_date').to_s, size: 20, value: check_topic_due_date_value(assignment_review_due_dates, topic_id, 2, review_round) %></td> <%end%> <%end%>
</tr>
<%end%>

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

The project does not require any Unit Test cases to be implemented.

== '''References''' ==

1. Expertiza on GitHub

2. GitHub Project Repository Fork

3. The live Expertiza website

4. Demo link

5. Expertiza project documentation wiki

E1843 Issues Related To Deadlines

2018-11-09T23:43:13Z

Hshah3: /* Issues in the Current Project */

This wiki page is for the description of changes made under E1843 OSS assignment for Fall 2018, CSC/ECE 517.

== '''About Expertiza''' ==

Expertiza is an open source project based on Ruby on Rails framework and the code is available on Github. Expertiza allows the instructor to create new assignments as well as edit new or existing assignments. Instructors can also create a list of topics the students can sign up for and specify deadlines for completion of various tasks. Students can form teams in Expertiza to work on various projects and assignments as well as peer review other students' submissions. Expertiza supports submission across various document types, including the URLs Wiki pages.

== '''Issues in the Current Project''' ==

1.There is no deadline that specifies when a team can drop their topics. Due to this, few problems occur: The team might drop a topic later on which is close to the submission date and this results in topic not being assigned to any other team on time such that they can submit their assignment. Also, if one team was wait listed for the same topic which the other team dropped closer to the submission deadline, then the first team will be assigned to the dropped topic which is not desirable as they might be working on their assigned topic for long time.

2.There are different topics on which students can work during different times. This type of assignment is known as Staggered- deadline assignment in which different topics have different submission and review deadlines. For these assignments too, there is a need for "Drop Topics Deadline". In the current implementation, the drop topic deadline is same for all the topics in a Staggered Deadline assignment which is not desirable.

== '''Corrections made in the New Project''' ==

1. The instructor can specify a Drop Topic deadline date now. After a drop topic deadline passes, the "X" in the Sign-Up sheet disables so that the student cannot drop the topic and the waitlist gets cleared.

2. Staggered deadline assignments now have different drop deadlines for different topics in that assignment.

== '''Files modified in Current Project''' ==

1. app/controllers/assignments_controller.rb

2. app/controllers/sign_up_sheet_controller.rb

3. app/models/student_task.rb

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

5. app/views/sign_up_sheet/_add_signup_topics_staggered.html.erb

6. app/views/sign_up_sheet/_due_dates.html.erb

== '''Current Implementation''' ==

1. Clearing the waitlist after Drop Deadline passes is implemented in sign_up_sheet_controller.rb where it is checked if the current time is greater than the time mentioned in Drop deadline. If the deadline has been passed, the 'update_is_waitlisted' method of SignedUpTeam model is called to delete all the waitlisted teams. The code snippets for the changes made are attached below:

(i) app/controllers/sign_up_sheet_controller.rb

if !topic_id1.nil? and !@drop_topic_deadline1.nil? and Time.now > @drop_topic_deadline1.due_at
SignedUpTeam.update_is_waitlisted(topic_id1.topic_id,team_id) end

(ii) The 'update_is_waitlisted' method is implemented in app/models/signed_up_team.rb as follows:

def self.update_is_waitlisted(topic_i)
topic_id1 = SignedUpTeam.where(team_id: team_id).first
if @assignment.staggered_deadline?
@drop_topic_deadline1 = TopicDueDate.where(parent_id: topic_id1.topic_id, deadline_type_id: 6).first rescue nil end
due_dates = params[:due_date]
topics = SignUpTopic.where(assignment_id: params[:assignment_id])
review_rounds = assignment.num_review_rounds
topics.each_with_index do |topic, index|
for i in 1..review_rounds
@topic_drop_topic_due_date = due_dates[topics[index].id.to_s + '_drop_topic_' + i.to_s + '_due_date']
if assignment.due_dates.select {|due_date| due_date.deadline_type_id == 6 }.nil?
@assignment_drop_topic_due_date = DateTime.parse(@assignment_drop_topic_due_dates[i - 1].due_at.to_s).strftime("%Y-%m-%d %H:%M")
end
end

(iii) app/helpers/sign_up_sheet_helper.rb

if assignment_due_dates.length == 0
assignment_due_dates = @assignment_submission_due_dates
end

(iv) app/models/student_task.rb

def self.get_due_date_data(assignment, timeline_list, participant)
if assignment.staggered_deadline?
team_id = participant.team.try(:id)
topic_id1 = SignedUpTeam.where(team_id: team_id).first
if !topic_id1.nil?
topic_due_date = TopicDueDate.where(parent_id: topic_id1.topic_id, deadline_type_id: 6).first rescue nil
timeline = {label: ('Drop Topic Deadline').humanize}
timeline[:updated_at] = topic_due_date.due_at.strftime('%a, %d %b %Y %H:%M')
timeline_list << timeline
end
end
assignment.due_dates.each do |dd|
timeline = {label: (dd.deadline_type.name + ' Deadline').humanize}
unless dd.due_at.nil?
timeline[:updated_at] = dd.due_at.strftime('%a, %d %b %Y %H:%M')
timeline_list << timeline
end
end
end

(v) app/views/assignments/edit.html.erb

<% if @assignment_form.assignment.staggered_deadline == true %>
<%= render partial: '/sign_up_sheet/add_signup_topics_staggered', locals: {review_rounds: @review_rounds, assignment_submission_due_dates: @assignment_submission_due_dates, assignment_review_due_dates: @assignment_review_due_dates, assignment_drop_topic_due_dates: @assignment_drop_topic_due_dates} %>
<% else %>
<%= render '/sign_up_sheet/add_signup_topics' %>
<% end %>

(vi) app/views/sign_up_sheet/_add_signup_topics_staggered.html.erb

<%= form_tag :controller => 'sign_up_sheet', :action => 'save_topic_deadlines', :assignment_id => @assignment.id do %>

 <%= render :partial => '/sign_up_sheet/due_dates', :locals => {review_rounds: review_rounds, assignment_submission_due_dates: assignment_submission_due_dates, assignment_review_due_dates: assignment_review_due_dates, assignment_drop_topic_due_dates: assignment_drop_topic_due_dates} %>
<% end %>

(vii) app/views/sign_up_sheet/_due_dates.html.erb

<tr>
<th>Drop deadline</th>
<%for i in 2..review_rounds%>
<td><%= @assignment.sign_up_topics[i].topic_name %></td>
<% for review_round in 1..review_rounds %>
<% topic_id = @assignment.sign_up_topics[i].id %>
<%if review_round == 1 %>
<td><%= text_field :due_date, (topic_id.to_s + '_drop_topic_' + review_round.to_s + '_due_date').to_s, size: 20, value: check_topic_due_date_value(assignment_drop_topic_due_dates, topic_id, 6, review_round) %></td>
<td><%= text_field :due_date, (topic_id.to_s + '_submission_' + review_round.to_s + '_due_date').to_s, size: 20, value: check_topic_due_date_value(assignment_submission_due_dates, topic_id, 1, review_round) %></td>
<td><%= text_field :due_date, (topic_id.to_s + '_review_' + review_round.to_s + '_due_date').to_s, size: 20, value: check_topic_due_date_value(assignment_review_due_dates, topic_id, 2, review_round) %></td>
<%else%>
<td><%= text_field :due_date, (topic_id.to_s + '_submission_' + review_round.to_s + '_due_date').to_s, size: 20, value: check_topic_due_date_value(assignment_submission_due_dates, topic_id, 1, review_round) %></td>
<td><%= text_field :due_date, (topic_id.to_s + '_review_' + review_round.to_s + '_due_date').to_s, size: 20, value: check_topic_due_date_value(assignment_review_due_dates, topic_id, 2, review_round) %></td> <%end%> <%end%>
</tr>
<%end%>

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

The project does not require any Unit Test cases to be implemented.

== '''References''' ==

1. Expertiza on GitHub

2. GitHub Project Repository Fork

3. The live Expertiza website

4. Demo link

5. Expertiza project documentation wiki