Expertiza_Wiki - User contributions [en]

CSC/ECE 517 Fall 2016 E1678: Review configuration options

2016-12-02T22:41:31Z

Ssdeshp5: /* Design */

=Introduction=
Expertiza is an online system that is used by students to view/submit assignments and review others' work. Expertiza also provides tools to visualize the scores and gauge the improvements made during the course semester. It also facilitates and monitors team projects. It is targeted at educational and non-profit organizations. The project is funded by the National Software Foundation (NSF), NCSU Learning in a Technology-Rich Environment (LITRE) program, the NCSU Faculty Center for Teaching and Learning, the NCSU STEM Initiative, and the Center for Advanced Computing and Communication.
Expertiza is an open-source project with the source code available as a public repository on GitHub. It is developed using Ruby on Rails and is increasingly becoming robust thanks to the innumerable bugs being fixed by the community. The project has a micro-blog on SourceForge where the developer community report bugs and document updates.

=Task Description=
==Requirement 1==
===Problem===
Expertiza has two kinds of review strategies, as specified in the Review Strategy tab of assignment creation:
;Auto-selected: Reviews are not preassigned, but when a student comes to do a review, (s)he can select from the reviews that are available at that point.
;Instructor-selected:
Instructor decides in advance who reviews whom.Until now, when the strategy is auto-selected, there has been no maximum on the number of reviews a student could select. So students can review as many topics as they want.

===Requirement===
Set a maximum on the number of reviews a student can choose with auto-selected reviewing. Implement a maximum, and allow the instructor to set that maximum via a checkbox asking whether there is a maximum, and if the box is checked, a textbox to specify what the maximum number should be.If there is a maximum, and a reviewer has already selected the maximum number of reviews, the button that allows selecting an additional review should be disabled.

===Design===
This requirement needs changes to the instructor view and student’s review page. These are small changes to the existing code. So we didn’t find any design pattern which can be used as part of requirement.
;Instructor view changes
:While creating the assignment, instructor should be able to specify maximum on the number of reviews done by each student. Assignment related configurations are handled by '''edit''' method in the '''assignment_controller'''. This method gathers all the information and calls '''edit''' view to display results. We added checkbox for this selection under '''Review Strategy''' tab of instructor view. If the instructor selects this checkbox, he’ll be prompted to enter the value for the maximum reviews allowed for each student. This threshold value is stored in '''num_reviews''' column of '''Assignment''' table. All these codes are part of '''assignments/edit/review_strategy''' file since it displays all the elements in '''Review strategy''' tab. Controller stores these values in '''assignments''' database. There are no changes to assignments controller. Instructor view looks as shown below.

[[File:R1iview.png |frame|upright=0.5|center|Requirement 1 - Instructor View Changes]]
;Student Topic Review page changes:
:Students review topics page is displayed by '''list''' method of '''Student_review_controller'''. We added a check in the controller to see if the chosen number of topics exceeds the value set by the instructor. Topic selection will be disabled in '''views/student_review/_set_dynamic_review.html.erb''' file if the selected number of topics exceeds configured maximum value as shown below.

[[File:Stview.png |frame|upright=0.5|center|Requirement 1 - Student View Changes]]

==Requirement 2==
===Problem===
Current behaviour of expertiza doesn’t allow the students to drop the reviews. If the student selects some topic and want to drop for some reason, he/she need to contact instructor to drop that review.

===Requirement===
Allow students to drop reviews. When a student has selected a review, there should be a button allowing the student to drop the review. But student should only be able drop a review if the review has not already been submitted.

===Design===
;Student Topic Review page changes:
:Students review topics page is displayed by list method of '''Student_review_controller'''. '''List.html.erb''' file calls '''/views/student_review/_responses.html.erb''' partial to display already selected topics. Add a delete symbol to the review topics if the assignment stage is not '''“finished”''' and review is '''“not submitted”'''.

[[File:Drop.png |frame|upright=0.5|center|Requirement 2 - Allow students to drop reviews]]
[[File:Drop1.png |frame|upright=0.5|center|Requirement 2 - Allow students to drop reviews only if Review has not been submitted.]]

;Student_review_controller changes:
:Add destroy method to student_review controller. This method should track down the corresponding response map for the topic that needs to be dropped and then delete it.

==Requirement 3==
===Problem===
While creating the assignments instructor can allow students to see their teammate score by selecting '''Show teammate reviews?''' checkbox. But this option shows both the scores and teammate reviews on the '''grades/view_my_score''' page.

===Requirement===
Instructor should get finer level control to specify these options like '''show only teammate reviews and not scores''', '''show only teammate scores but not reviews''', '''Don’t show anything'''

===Design===
There is already existing code to display and hide the teammate reviews. This requirement doesn’t need any design patterns since we need to modify small portion of the existing code.
;Instructor view changes
:General tab of assignment creation has '''"show teammate reviews ?"''' option. We replaced this option with two options. '''"show teammate scores ?"''' , '''"show teammate reviews?"'''. '''"Show teammate reviews ?"''' checkbox value is stored in '''show_teammate_reviews''' column in the '''Assignments''' table. We added one more boolean column '''show_teammate_score''' to hold the selection value of '''"show teammate scores ?"''' option. This is how instructor view will change after implementation.
[[File:Iview.png |frame|upright=0.5|center|Requirement 3 - Instructor View Changes]]

;Changes to students view score page:
:Code to display teammate reviews and scores is present in the '''/views/grades/view_my_scores''' file. We added a code to selectively display scores and reviews based on the boolean variables ( show_teammate_reviews, show_teammate_score) present in the Assignments database table. If the instructor only selects '''show teammate scores?''' student will be able to see aggregate teammate score as shown below.
[[File:Sscore.png |frame|upright=0.5|center|Requirement 3 - Show aggregate teammate scores]]
Students will be able to see only reviews if the instructor selects '''show teammate reviews ?''' during assignment creation.
[[File:Rstudent.png |frame|upright=0.5|center|Requirement 3 -Show only teammate reviews]]
Students will be able to see both the score and teammate reviews if the instructors checks both boxes from assignment configuration page.

==Requirement 4==
===Problem===
There is no option that lets reviewers see others’ reviews of the same work after they submit their review of that work.

===Requirement===
Implement an option that lets reviewers see others’ reviews of the same work, after they submit their review of that work. This could help reviewers learn from other reviewers of the same work.

===Design===
This option should be specified in a reasonable way on the Create Assignment page. So we didn’t find any design pattern which can be used as part of requirement 4.

;Instructor view changes:
:While creating the assignment, instructor should be able to specify if students should be allowed to see reviews done by other students for the same work. Assignment related configurations are handled by '''edit''' method in the '''assignment_controllers'''. This method gathers all the information and calls '''edit''' view to display results.We are planning to add checkbox '''show_other_reviews''' for this selection under '''General''' tab of instructor view. If the instructor selects this checkbox, this feature will be active for the assignment. The checkbox will be added in the "assignments/edit/_general" file since It displays all the elements in '''General''' tab. '''show_other_reviews''' will be a hidden form field that stores the value of this checkbox that is finally persisted in '''assignments''' database.

;Changes to student_response controller and views:
:The ''View'' link displays the submitted/in progress reviews of the student and is handled by the list action of the StudentReviewController (student_review_controller.rb) and the associated list view is "/views/student_review/list.html.erb" file. We plan to add another link ''View Other Reviews'' to the partial '''_reponses''' view. This link would be visible only if the '''show_other_reviews''' option has been enabled by the instructor. This link would be next to each of the Review Topics submitted by the student for the current round of that assignment. Clicking this link would be handled by an action '''other_reviews''' of the '''reponse_controller'''(response_controller.rb). After fetching some necessary query parameters the action method would filter responses submitted by other students for that topic and round, exclude the response of the logged in student and set some instance variables. These instance variables would be displayed in the new view '''other_reviews''' in (views/response/other_reviews.erb).

==Requirement 5==
===Problem===
The existing implementation of expertiza doesn’t provide a student the option to not see review scores or the text feedback. Sometimes a student might just want to see the scores and not the reviews and other times might want to see the reviews and not the scores. The ability to turn off either one is not provided by expertiza.

===Requirement===
When a student signs in there should be an option that allows the students to change the review score settings. The students will be provided with options of choosing either viewing only the review score or viewing only the text feedback or viewing both.

===Design===
;Student View Scores page changes:
:Student review scores is displayed in the View Score page and the /views/grades/view_my_score.html.erb file handles this operation. In this view we plan to provide a dropdown list in which the student can select if he/she wants to view scores only, view feedback only or both. The default setting will be to view both.
;Grades Controller changes:
:The view_my_score method in the grades controller performs the task of retrieving the scores and feedback from the database and also does various additional functions like calculating average, etc. In this method, based on the option chosen by the student either only scores or text feedback or both will be retreived. If the student does not explicitly specify any option then both the scores and feedback will be fetched.

CSC/ECE 517 Fall 2016 E1678: Review configuration options

2016-12-02T22:40:36Z

Ssdeshp5: /* Design */

=Introduction=
Expertiza is an online system that is used by students to view/submit assignments and review others' work. Expertiza also provides tools to visualize the scores and gauge the improvements made during the course semester. It also facilitates and monitors team projects. It is targeted at educational and non-profit organizations. The project is funded by the National Software Foundation (NSF), NCSU Learning in a Technology-Rich Environment (LITRE) program, the NCSU Faculty Center for Teaching and Learning, the NCSU STEM Initiative, and the Center for Advanced Computing and Communication.
Expertiza is an open-source project with the source code available as a public repository on GitHub. It is developed using Ruby on Rails and is increasingly becoming robust thanks to the innumerable bugs being fixed by the community. The project has a micro-blog on SourceForge where the developer community report bugs and document updates.

=Task Description=
==Requirement 1==
===Problem===
Expertiza has two kinds of review strategies, as specified in the Review Strategy tab of assignment creation:
;Auto-selected: Reviews are not preassigned, but when a student comes to do a review, (s)he can select from the reviews that are available at that point.
;Instructor-selected:
Instructor decides in advance who reviews whom.Until now, when the strategy is auto-selected, there has been no maximum on the number of reviews a student could select. So students can review as many topics as they want.

===Requirement===
Set a maximum on the number of reviews a student can choose with auto-selected reviewing. Implement a maximum, and allow the instructor to set that maximum via a checkbox asking whether there is a maximum, and if the box is checked, a textbox to specify what the maximum number should be.If there is a maximum, and a reviewer has already selected the maximum number of reviews, the button that allows selecting an additional review should be disabled.

===Design===
This requirement needs changes to the instructor view and student’s review page. These are small changes to the existing code. So we didn’t find any design pattern which can be used as part of requirement.
;Instructor view changes
:While creating the assignment, instructor should be able to specify maximum on the number of reviews done by each student. Assignment related configurations are handled by '''edit''' method in the '''assignment_controller'''. This method gathers all the information and calls '''edit''' view to display results. We added checkbox for this selection under '''Review Strategy''' tab of instructor view. If the instructor selects this checkbox, he’ll be prompted to enter the value for the maximum reviews allowed for each student. This threshold value is stored in '''num_reviews''' column of '''Assignment''' table. All these codes are part of '''assignments/edit/review_strategy''' file since it displays all the elements in '''Review strategy''' tab. Controller stores these values in '''assignments''' database. There are no changes to assignments controller. Instructor view looks as shown below.

[[File:R1iview.png |frame|upright=0.5|center|Requirement 1 - Instructor View Changes]]
;Student Topic Review page changes:
:Students review topics page is displayed by '''list''' method of '''Student_review_controller'''. We added a check in the controller to see if the chosen number of topics exceeds the value set by the instructor. Topic selection will be disabled in '''views/student_review/_set_dynamic_review.html.erb''' file if the selected number of topics exceeds configured maximum value as shown below.

[[File:Stview.png |frame|upright=0.5|center|Requirement 1 - Student View Changes]]

==Requirement 2==
===Problem===
Current behaviour of expertiza doesn’t allow the students to drop the reviews. If the student selects some topic and want to drop for some reason, he/she need to contact instructor to drop that review.

===Requirement===
Allow students to drop reviews. When a student has selected a review, there should be a button allowing the student to drop the review. But student should only be able drop a review if the review has not already been submitted.

===Design===
;Student Topic Review page changes:
:Students review topics page is displayed by list method of '''Student_review_controller'''. '''List.html.erb''' file calls '''/views/student_review/_responses.html.erb''' partial to display already selected topics. Add a delete symbol to the review topics if the assignment stage is not '''“finished”''' and review is '''“not submitted”'''.

[[File:Drop.png |frame|upright=0.5|center|Requirement 2 - Allow students to drop reviews if Review has not been submitted.]]

;Student_review_controller changes:
:Add destroy method to student_review controller. This method should track down the corresponding response map for the topic that needs to be dropped and then delete it.

==Requirement 3==
===Problem===
While creating the assignments instructor can allow students to see their teammate score by selecting '''Show teammate reviews?''' checkbox. But this option shows both the scores and teammate reviews on the '''grades/view_my_score''' page.

===Requirement===
Instructor should get finer level control to specify these options like '''show only teammate reviews and not scores''', '''show only teammate scores but not reviews''', '''Don’t show anything'''

===Design===
There is already existing code to display and hide the teammate reviews. This requirement doesn’t need any design patterns since we need to modify small portion of the existing code.
;Instructor view changes
:General tab of assignment creation has '''"show teammate reviews ?"''' option. We replaced this option with two options. '''"show teammate scores ?"''' , '''"show teammate reviews?"'''. '''"Show teammate reviews ?"''' checkbox value is stored in '''show_teammate_reviews''' column in the '''Assignments''' table. We added one more boolean column '''show_teammate_score''' to hold the selection value of '''"show teammate scores ?"''' option. This is how instructor view will change after implementation.
[[File:Iview.png |frame|upright=0.5|center|Requirement 3 - Instructor View Changes]]

;Changes to students view score page:
:Code to display teammate reviews and scores is present in the '''/views/grades/view_my_scores''' file. We added a code to selectively display scores and reviews based on the boolean variables ( show_teammate_reviews, show_teammate_score) present in the Assignments database table. If the instructor only selects '''show teammate scores?''' student will be able to see aggregate teammate score as shown below.
[[File:Sscore.png |frame|upright=0.5|center|Requirement 3 - Show aggregate teammate scores]]
Students will be able to see only reviews if the instructor selects '''show teammate reviews ?''' during assignment creation.
[[File:Rstudent.png |frame|upright=0.5|center|Requirement 3 -Show only teammate reviews]]
Students will be able to see both the score and teammate reviews if the instructors checks both boxes from assignment configuration page.

==Requirement 4==
===Problem===
There is no option that lets reviewers see others’ reviews of the same work after they submit their review of that work.

===Requirement===
Implement an option that lets reviewers see others’ reviews of the same work, after they submit their review of that work. This could help reviewers learn from other reviewers of the same work.

===Design===
This option should be specified in a reasonable way on the Create Assignment page. So we didn’t find any design pattern which can be used as part of requirement 4.

;Instructor view changes:
:While creating the assignment, instructor should be able to specify if students should be allowed to see reviews done by other students for the same work. Assignment related configurations are handled by '''edit''' method in the '''assignment_controllers'''. This method gathers all the information and calls '''edit''' view to display results.We are planning to add checkbox '''show_other_reviews''' for this selection under '''General''' tab of instructor view. If the instructor selects this checkbox, this feature will be active for the assignment. The checkbox will be added in the "assignments/edit/_general" file since It displays all the elements in '''General''' tab. '''show_other_reviews''' will be a hidden form field that stores the value of this checkbox that is finally persisted in '''assignments''' database.

;Changes to student_response controller and views:
:The ''View'' link displays the submitted/in progress reviews of the student and is handled by the list action of the StudentReviewController (student_review_controller.rb) and the associated list view is "/views/student_review/list.html.erb" file. We plan to add another link ''View Other Reviews'' to the partial '''_reponses''' view. This link would be visible only if the '''show_other_reviews''' option has been enabled by the instructor. This link would be next to each of the Review Topics submitted by the student for the current round of that assignment. Clicking this link would be handled by an action '''other_reviews''' of the '''reponse_controller'''(response_controller.rb). After fetching some necessary query parameters the action method would filter responses submitted by other students for that topic and round, exclude the response of the logged in student and set some instance variables. These instance variables would be displayed in the new view '''other_reviews''' in (views/response/other_reviews.erb).

==Requirement 5==
===Problem===
The existing implementation of expertiza doesn’t provide a student the option to not see review scores or the text feedback. Sometimes a student might just want to see the scores and not the reviews and other times might want to see the reviews and not the scores. The ability to turn off either one is not provided by expertiza.

===Requirement===
When a student signs in there should be an option that allows the students to change the review score settings. The students will be provided with options of choosing either viewing only the review score or viewing only the text feedback or viewing both.

===Design===
;Student View Scores page changes:
:Student review scores is displayed in the View Score page and the /views/grades/view_my_score.html.erb file handles this operation. In this view we plan to provide a dropdown list in which the student can select if he/she wants to view scores only, view feedback only or both. The default setting will be to view both.
;Grades Controller changes:
:The view_my_score method in the grades controller performs the task of retrieving the scores and feedback from the database and also does various additional functions like calculating average, etc. In this method, based on the option chosen by the student either only scores or text feedback or both will be retreived. If the student does not explicitly specify any option then both the scores and feedback will be fetched.

File:Drop1.png

2016-12-02T22:40:21Z

Ssdeshp5: Drop Review option is available if review is saved but not submitted

Drop Review option is available if review is saved but not submitted

CSC/ECE 517 Fall 2016 E1678: Review configuration options

2016-12-02T22:38:29Z

Ssdeshp5: /* Requirement 2 */

=Introduction=
Expertiza is an online system that is used by students to view/submit assignments and review others' work. Expertiza also provides tools to visualize the scores and gauge the improvements made during the course semester. It also facilitates and monitors team projects. It is targeted at educational and non-profit organizations. The project is funded by the National Software Foundation (NSF), NCSU Learning in a Technology-Rich Environment (LITRE) program, the NCSU Faculty Center for Teaching and Learning, the NCSU STEM Initiative, and the Center for Advanced Computing and Communication.
Expertiza is an open-source project with the source code available as a public repository on GitHub. It is developed using Ruby on Rails and is increasingly becoming robust thanks to the innumerable bugs being fixed by the community. The project has a micro-blog on SourceForge where the developer community report bugs and document updates.

=Task Description=
==Requirement 1==
===Problem===
Expertiza has two kinds of review strategies, as specified in the Review Strategy tab of assignment creation:
;Auto-selected: Reviews are not preassigned, but when a student comes to do a review, (s)he can select from the reviews that are available at that point.
;Instructor-selected:
Instructor decides in advance who reviews whom.Until now, when the strategy is auto-selected, there has been no maximum on the number of reviews a student could select. So students can review as many topics as they want.

===Requirement===
Set a maximum on the number of reviews a student can choose with auto-selected reviewing. Implement a maximum, and allow the instructor to set that maximum via a checkbox asking whether there is a maximum, and if the box is checked, a textbox to specify what the maximum number should be.If there is a maximum, and a reviewer has already selected the maximum number of reviews, the button that allows selecting an additional review should be disabled.

===Design===
This requirement needs changes to the instructor view and student’s review page. These are small changes to the existing code. So we didn’t find any design pattern which can be used as part of requirement.
;Instructor view changes
:While creating the assignment, instructor should be able to specify maximum on the number of reviews done by each student. Assignment related configurations are handled by '''edit''' method in the '''assignment_controller'''. This method gathers all the information and calls '''edit''' view to display results. We added checkbox for this selection under '''Review Strategy''' tab of instructor view. If the instructor selects this checkbox, he’ll be prompted to enter the value for the maximum reviews allowed for each student. This threshold value is stored in '''num_reviews''' column of '''Assignment''' table. All these codes are part of '''assignments/edit/review_strategy''' file since it displays all the elements in '''Review strategy''' tab. Controller stores these values in '''assignments''' database. There are no changes to assignments controller. Instructor view looks as shown below.

[[File:R1iview.png |frame|upright=0.5|center|Requirement 1 - Instructor View Changes]]
;Student Topic Review page changes:
:Students review topics page is displayed by '''list''' method of '''Student_review_controller'''. We added a check in the controller to see if the chosen number of topics exceeds the value set by the instructor. Topic selection will be disabled in '''views/student_review/_set_dynamic_review.html.erb''' file if the selected number of topics exceeds configured maximum value as shown below.

[[File:Stview.png |frame|upright=0.5|center|Requirement 1 - Student View Changes]]

==Requirement 2==
===Problem===
Current behaviour of expertiza doesn’t allow the students to drop the reviews. If the student selects some topic and want to drop for some reason, he/she need to contact instructor to drop that review.

===Requirement===
Allow students to drop reviews. When a student has selected a review, there should be a button allowing the student to drop the review. But student should only be able drop a review if the review has not already been submitted.

===Design===
;Student Topic Review page changes:
:Students review topics page is displayed by list method of '''Student_review_controller'''. '''List.html.erb''' file calls '''/views/student_review/_responses.html.erb''' partial to display already selected topics. Add a delete symbol to the review topics if the assignment stage is not '''“finished”''' and review is '''“not submitted”'''.

[[File:Drop.png |frame|upright=0.5|center|Requirement 2 - Allow students to drop reviews.]]

;Student_review_controller changes:
:Add destroy method to student_review controller. This method should track down the corresponding response map for the topic that needs to be dropped and then delete it.

==Requirement 3==
===Problem===
While creating the assignments instructor can allow students to see their teammate score by selecting '''Show teammate reviews?''' checkbox. But this option shows both the scores and teammate reviews on the '''grades/view_my_score''' page.

===Requirement===
Instructor should get finer level control to specify these options like '''show only teammate reviews and not scores''', '''show only teammate scores but not reviews''', '''Don’t show anything'''

===Design===
There is already existing code to display and hide the teammate reviews. This requirement doesn’t need any design patterns since we need to modify small portion of the existing code.
;Instructor view changes
:General tab of assignment creation has '''"show teammate reviews ?"''' option. We replaced this option with two options. '''"show teammate scores ?"''' , '''"show teammate reviews?"'''. '''"Show teammate reviews ?"''' checkbox value is stored in '''show_teammate_reviews''' column in the '''Assignments''' table. We added one more boolean column '''show_teammate_score''' to hold the selection value of '''"show teammate scores ?"''' option. This is how instructor view will change after implementation.
[[File:Iview.png |frame|upright=0.5|center|Requirement 3 - Instructor View Changes]]

;Changes to students view score page:
:Code to display teammate reviews and scores is present in the '''/views/grades/view_my_scores''' file. We added a code to selectively display scores and reviews based on the boolean variables ( show_teammate_reviews, show_teammate_score) present in the Assignments database table. If the instructor only selects '''show teammate scores?''' student will be able to see aggregate teammate score as shown below.
[[File:Sscore.png |frame|upright=0.5|center|Requirement 3 - Show aggregate teammate scores]]
Students will be able to see only reviews if the instructor selects '''show teammate reviews ?''' during assignment creation.
[[File:Rstudent.png |frame|upright=0.5|center|Requirement 3 -Show only teammate reviews]]
Students will be able to see both the score and teammate reviews if the instructors checks both boxes from assignment configuration page.

==Requirement 4==
===Problem===
There is no option that lets reviewers see others’ reviews of the same work after they submit their review of that work.

===Requirement===
Implement an option that lets reviewers see others’ reviews of the same work, after they submit their review of that work. This could help reviewers learn from other reviewers of the same work.

===Design===
This option should be specified in a reasonable way on the Create Assignment page. So we didn’t find any design pattern which can be used as part of requirement 4.

;Instructor view changes:
:While creating the assignment, instructor should be able to specify if students should be allowed to see reviews done by other students for the same work. Assignment related configurations are handled by '''edit''' method in the '''assignment_controllers'''. This method gathers all the information and calls '''edit''' view to display results.We are planning to add checkbox '''show_other_reviews''' for this selection under '''General''' tab of instructor view. If the instructor selects this checkbox, this feature will be active for the assignment. The checkbox will be added in the "assignments/edit/_general" file since It displays all the elements in '''General''' tab. '''show_other_reviews''' will be a hidden form field that stores the value of this checkbox that is finally persisted in '''assignments''' database.

;Changes to student_response controller and views:
:The ''View'' link displays the submitted/in progress reviews of the student and is handled by the list action of the StudentReviewController (student_review_controller.rb) and the associated list view is "/views/student_review/list.html.erb" file. We plan to add another link ''View Other Reviews'' to the partial '''_reponses''' view. This link would be visible only if the '''show_other_reviews''' option has been enabled by the instructor. This link would be next to each of the Review Topics submitted by the student for the current round of that assignment. Clicking this link would be handled by an action '''other_reviews''' of the '''reponse_controller'''(response_controller.rb). After fetching some necessary query parameters the action method would filter responses submitted by other students for that topic and round, exclude the response of the logged in student and set some instance variables. These instance variables would be displayed in the new view '''other_reviews''' in (views/response/other_reviews.erb).

==Requirement 5==
===Problem===
The existing implementation of expertiza doesn’t provide a student the option to not see review scores or the text feedback. Sometimes a student might just want to see the scores and not the reviews and other times might want to see the reviews and not the scores. The ability to turn off either one is not provided by expertiza.

===Requirement===
When a student signs in there should be an option that allows the students to change the review score settings. The students will be provided with options of choosing either viewing only the review score or viewing only the text feedback or viewing both.

===Design===
;Student View Scores page changes:
:Student review scores is displayed in the View Score page and the /views/grades/view_my_score.html.erb file handles this operation. In this view we plan to provide a dropdown list in which the student can select if he/she wants to view scores only, view feedback only or both. The default setting will be to view both.
;Grades Controller changes:
:The view_my_score method in the grades controller performs the task of retrieving the scores and feedback from the database and also does various additional functions like calculating average, etc. In this method, based on the option chosen by the student either only scores or text feedback or both will be retreived. If the student does not explicitly specify any option then both the scores and feedback will be fetched.

File:Drop.png

2016-12-02T22:36:15Z

Ssdeshp5: uploaded a new version of "File:Drop.png": Review can be dropped only when review is not submitted.

File:Drop.png

2016-12-02T22:32:21Z

Ssdeshp5: uploaded a new version of "File:Drop.png": Drop Review Option is available only when the review is not submitted and stage is not 'Finished'

CSC/ECE 517 Fall 2016 E1678: Review configuration options

2016-12-01T18:56:26Z

Ssdeshp5: /* Design */

=Introduction=
Expertiza is an online system that is used by students to view/submit assignments and review others' work. Expertiza also provides tools to visualize the scores and gauge the improvements made during the course semester. It also facilitates and monitors team projects. It is targeted at educational and non-profit organizations. The project is funded by the National Software Foundation (NSF), NCSU Learning in a Technology-Rich Environment (LITRE) program, the NCSU Faculty Center for Teaching and Learning, the NCSU STEM Initiative, and the Center for Advanced Computing and Communication.
Expertiza is an open-source project with the source code available as a public repository on GitHub. It is developed using Ruby on Rails and is increasingly becoming robust thanks to the innumerable bugs being fixed by the community. The project has a micro-blog on SourceForge where the developer community report bugs and document updates.

=Task Description=
==Requirement 1==
===Problem===
Expertiza has two kinds of review strategies, as specified in the Review Strategy tab of assignment creation:
;Auto-selected: Reviews are not preassigned, but when a student comes to do a review, (s)he can select from the reviews that are available at that point.
;Instructor-selected:
Instructor decides in advance who reviews whom.Until now, when the strategy is auto-selected, there has been no maximum on the number of reviews a student could select. So students can review as many topics as they want.

===Requirement===
Set a maximum on the number of reviews a student can choose with auto-selected reviewing. Implement a maximum, and allow the instructor to set that maximum via a checkbox asking whether there is a maximum, and if the box is checked, a textbox to specify what the maximum number should be.If there is a maximum, and a reviewer has already selected the maximum number of reviews, the button that allows selecting an additional review should be disabled.

===Design===
This requirement needs changes to the instructor view and student’s review page. These are small changes to the existing code. So we didn’t find any design pattern which can be used as part of requirement.
;Instructor view changes
:While creating the assignment, instructor should be able to specify maximum on the number of reviews done by each student. Assignment related configurations are handled by '''edit''' method in the assignment_controllers. This method gathers all the information and calls '''edit''' view to display results. We are planning to add checkbox for this selection under '''Review Strategy''' tab of instructor view. If the instructor selects this checkbox, he’ll be prompted to enter the value for the maximum reviews allowed for each student. We need to fill this value in '''num_reviews''' column of Assignment model. All these codes will be added in '''assignments/edit/review_strategy''' file since it displays all the elements in '''Review strategy''' tab. Controller stores these values in '''assignments''' database. There are no changes assignments controller. This is how instructor view looks after implementation.

[[File:R1iview.png |frame|upright=0.5|center|Requirement 1 - Instructor View Changes]]
;Student Topic Review page changes:
:Students review topics page is displayed by list method of '''Student_review_controller'''. Add a check in the controller to see if the chosen number of topics exceeds the value set by the instructor. Disable topic selection in '''views/student_review/_set_dynamic_review.html.erb''' file if the selected number of topics exceeds configured maximum value as shown below.

[[File:Stview.png |frame|upright=0.5|center|Requirement 1 - Student View Changes]]

==Requirement 2==
===Problem===
Current behaviour of expertiza doesn’t allow the students to drop the reviews. If the student selects some topic and want to drop for some reason, he/she need to contact instructor to drop that review.

===Requirement===
Allow students to drop reviews. When a student has selected a review, there should be a button allowing the student to drop the review. But student should only be able drop a review if the review has not already been submitted.

===Design===
;Student Topic Review page changes:
:Students review topics page is displayed by list method of '''Student_review_controller'''. '''List.html.erb''' file calls '''/views/student_review/_responses.html.erb''' partial to display already selected topics. Add a delete symbol to the review topics if the assignment stage is not '''“finished”''' and review is '''“not submitted”'''.

[[File:DropReview.jpeg |frame|upright=0.5|center|Requirement 2 - Allow students to drop reviews.]]

;Student_review_controller changes:
:Add destroy method to student_review controller. This method should track down the corresponding response map for the topic that needs to be dropped and then delete it.

==Requirement 3==
===Problem===
While creating the assignments instructor can allow students to see their teammate score by selecting '''Show teammate reviews?''' checkbox. But this option shows both the scores and teammate reviews on the '''grades/view_my_score''' page.

===Requirement===
Instructor should get finer level control to specify these options like '''show only teammate reviews and not scores''', '''show only teammate scores but not reviews''', '''Don’t show anything'''

===Design===
There is already existing code to display and hide the teammate reviews. This requirement doesn’t need any design patterns since we need to modify small portion of the existing code.
;Instructor view changes
:General tab of assignment creation has '''"show teammate reviews ?"''' option. Replace this option with two options. '''"show teammate scores ?"''' , '''"show teammate reviews?"'''. '''"Show teammate reviews ?"''' value will be stored in '''show_teammate_reviews''' column in the '''Assignments''' table. We will add one more boolean column '''show_teammate_score''' to hold the selection value of '''"show teammate scores ?"''' option. This is how instructor view will change after implementation.
[[File:Iview.png |frame|upright=0.5|center|Requirement 3 - Instructor View Changes]]

;Changes to students view score page:
:Code to display teammate reviews and scores is present in the '''/views/grades/view_my_scores''' file. We will add a code to selectively display scores and reviews based on the boolean variables ( show_teammate_reviews, show_teammate_score) present in the Assignments database table. If the instructor only selects '''show teammate scores?''' student will be able to see aggregate teammate score as shown below.
[[File:Sscore.png |frame|upright=0.5|center|Requirement 3 - Show aggregate teammate scores]]
Students will be able to see only reviews if the instructor selects '''show teammate reviews ?''' during assignment creation.
[[File:Rstudent.png |frame|upright=0.5|center|Requirement 3 -Show only teammate reviews]]
Students will be able to see both the score and teammate reviews if the instructors checks both boxes from assignment configuration page.

==Requirement 4==
===Problem===
There is no option that lets reviewers see others’ reviews of the same work after they submit their review of that work.

===Requirement===
Implement an option that lets reviewers see others’ reviews of the same work, after they submit their review of that work. This could help reviewers learn from other reviewers of the same work.

===Design===
This option should be specified in a reasonable way on the Create Assignment page. So we didn’t find any design pattern which can be used as part of requirement 4.

;Instructor view changes:
:While creating the assignment, instructor should be able to specify if students should be allowed to see reviews done by other students for the same work. Assignment related configurations are handled by '''edit''' method in the '''assignment_controllers'''. This method gathers all the information and calls '''edit''' view to display results.We are planning to add checkbox '''show_other_reviews''' for this selection under '''General''' tab of instructor view. If the instructor selects this checkbox, this feature will be active for the assignment. The checkbox will be added in the "assignments/edit/_general" file since It displays all the elements in '''General''' tab. '''show_other_reviews''' will be a hidden form field that stores the value of this checkbox that is finally persisted in '''assignments''' database.

;Changes to student_response controller and views:
:The ''View'' link displays the submitted/in progress reviews of the student and is handled by the list action of the StudentReviewController (student_review_controller.rb) and the associated list view is "/views/student_review/list.html.erb" file. We plan to add another link ''View Other Reviews'' to the partial '''_reponses''' view. This link would be visible only if the '''show_other_reviews''' option has been enabled by the instructor. This link would be next to each of the Review Topics submitted by the student for the current round of that assignment. Clicking this link would be handled by an action '''other_reviews''' of the '''reponse_controller'''(response_controller.rb). After fetching some necessary query parameters the action method would filter responses submitted by other students for that topic and round, exclude the response of the logged in student and set some instance variables. These instance variables would be displayed in the new view '''other_reviews''' in (views/response/other_reviews.erb).

==Requirement 5==
===Problem===
The existing implementation of expertiza doesn’t provide a student the option to not see review scores or the text feedback. Sometimes a student might just want to see the scores and not the reviews and other times might want to see the reviews and not the scores. The ability to turn off either one is not provided by expertiza.

===Requirement===
When a student signs in there should be an option that allows the students to change the review score settings. The students will be provided with options of choosing either viewing only the review score or viewing only the text feedback or viewing both.

===Design===
;Student View Scores page changes:
:Student review scores is displayed in the View Score page and the /views/grades/view_my_score.html.erb file handles this operation. In this view we plan to provide a dropdown list in which the student can select if he/she wants to view scores only, view feedback only or both. The default setting will be to view both.
;Grades Controller changes:
:The view_my_score method in the grades controller performs the task of retrieving the scores and feedback from the database and also does various additional functions like calculating average, etc. In this method, based on the option chosen by the student either only scores or text feedback or both will be retreived. If the student does not explicitly specify any option then both the scores and feedback will be fetched.

CSC/ECE 517 Fall 2016 E1678: Review configuration options

2016-11-14T20:16:45Z

Ssdeshp5: Added Image to show drop review functionality

=Introduction=
Expertiza is an online system that is used by students to view/submit assignments and review others' work. Expertiza also provides tools to visualize the scores and gauge the improvements made during the course semester. It also facilitates and monitors team projects. It is targeted at educational and non-profit organizations. The project is funded by the National Software Foundation (NSF), NCSU Learning in a Technology-Rich Environment (LITRE) program, the NCSU Faculty Center for Teaching and Learning, the NCSU STEM Initiative, and the Center for Advanced Computing and Communication.
Expertiza is an open-source project with the source code available as a public repository on GitHub. It is developed using Ruby on Rails and is increasingly becoming robust thanks to the innumerable bugs being fixed by the community. The project has a micro-blog on SourceForge where the developer community report bugs and document updates.

=Task Description=
==Requirement 1==
===Problem===
Expertiza has two kinds of review strategies, as specified in the Review Strategy tab of assignment creation:
;Auto-selected: Reviews are not preassigned, but when a student comes to do a review, (s)he can select from the reviews that are available at that point.
;Instructor-selected:
Instructor decides in advance who reviews whom.Until now, when the strategy is auto-selected, there has been no maximum on the number of reviews a student could select. So students can review as many topics as they want.

===Requirement===
Set a maximum on the number of reviews a student can choose with auto-selected reviewing. Implement a maximum, and allow the instructor to set that maximum via a checkbox asking whether there is a maximum, and if the box is checked, a textbox to specify what the maximum number should be.If there is a maximum, and a reviewer has already selected the maximum number of reviews, the button that allows selecting an additional review should be disabled.

===Design===
This requirement needs changes to the instructor view and student’s review page. These are small changes to the existing code. So we didn’t find any design pattern which can be used as part of requirement.
;Instructor view changes
:While creating the assignment, instructor should be able to specify maximum on the number of reviews done by each student. Assignment related configurations are handled by '''edit''' method in the assignment_controllers. This method gathers all the information and calls '''edit''' view to display results. We are planning to add checkbox for this selection under '''Review Strategy''' tab of instructor view. If the instructor selects this checkbox, he’ll be prompted to enter the value for the maximum reviews allowed for each student. We need to fill this value in '''num_reviews''' column of Assignment model. All these codes will be added in '''assignments/edit/review_strategy''' file since it displays all the elements in '''Review strategy''' tab. Controller stores these values in '''assignments''' database. There are no changes assignments controller. This is how instructor view looks after implementation.

[[File:R1iview.png |frame|upright=0.5|center|Requirement 1 - Instructor View Changes]]
;Student Topic Review page changes:
:Students review topics page is displayed by list method of '''Student_review_controller'''. Add a check in the controller to see if the chosen number of topics exceeds the value set by the instructor. Disable topic selection in '''views/student_review/_set_dynamic_review.html.erb''' file if the selected number of topics exceeds configured maximum value as shown below.

[[File:Stview.png |frame|upright=0.5|center|Requirement 1 - Student View Changes]]

==Requirement 2==
===Problem===
Current behaviour of expertiza doesn’t allow the students to drop the reviews. If the student selects some topic and want to drop for some reason, he/she need to contact instructor to drop that review.

===Requirement===
Allow students to drop reviews. When a student has selected a review, there should be a button allowing the student to drop the review. But student should only be able drop a review if the review has not already been submitted.

===Design===
;Student Topic Review page changes:
:Students review topics page is displayed by list method of '''Student_review_controller'''. '''List.html.erb''' file calls '''/views/student_review/_responses.html.erb''' partial to display already selected topics. Add a delete symbol to the review topics if the assignment stage is not '''“finished”''' and review is '''“not submitted”'''.

[[File:DropReview.jpeg |frame|upright=0.5|center|Requirement 2 - Allow students to drop reviews.]]

;Student_review_controller changes:
:Add destroy method to student_review controller. This method should delete signed up topic for the user/team from '''signed_up_teams''' table. And also it deletes all the non submitted responses from '''response_maps''' table recorded by that team so far.

==Requirement 3==
===Problem===
While creating the assignments instructor can allow students to see their teammate score by selecting '''Show teammate reviews?''' checkbox. But this option shows both the scores and teammate reviews on the '''grades/view_my_score''' page.

===Requirement===
Instructor should get finer level control to specify these options like '''show only teammate reviews and not scores''', '''show only teammate scores but not reviews''', '''Don’t show anything'''

===Design===
There is already existing code to display and hide the teammate reviews. This requirement doesn’t need any design patterns since we need to modify small portion of the existing code.
;Instructor view changes
:General tab of assignment creation has '''"show teammate reviews ?"''' option. Replace this option with two options. '''"show teammate scores ?"''' , '''"show teammate reviews?"'''. '''"Show teammate reviews ?"''' value will be stored in '''show_teammate_reviews''' column in the '''Assignments''' table. We will add one more boolean column '''show_teammate_score''' to hold the selection value of '''"show teammate scores ?"''' option. This is how instructor view will change after implementation.
[[File:Iview.png |frame|upright=0.5|center|Requirement 3 - Instructor View Changes]]

;Changes to students view score page:
:Code to display teammate reviews and scores is present in the '''/views/grades/view_my_scores''' file. We will add a code to selectively display scores and reviews based on the boolean variables ( show_teammate_reviews, show_teammate_score) present in the Assignments database table. If the instructor only selects '''show teammate scores?''' student will be able to see aggregate teammate score as shown below.
[[File:Sscore.png |frame|upright=0.5|center|Requirement 3 - Show aggregate teammate scores]]
Students will be able to see only reviews if the instructor selects '''show teammate reviews ?''' during assignment creation.
[[File:Rstudent.png |frame|upright=0.5|center|Requirement 3 -Show only teammate reviews]]
Students will be able to see both the score and teammate reviews if the instructors checks both boxes from assignment configuration page.

==Requirement 4==
===Problem===
There is no option that lets reviewers see others’ reviews of the same work after they submit their review of that work.

===Requirement===
Implement an option that lets reviewers see others’ reviews of the same work, after they submit their review of that work. This could help reviewers learn from other reviewers of the same work.

===Design===
This option should be specified in a reasonable way on the Create Assignment page. So we didn’t find any design pattern which can be used as part of requirement 4.

;Instructor view changes:
:While creating the assignment, instructor should be able to specify if students should be allowed to see reviews done by other students for the same work. Assignment related configurations are handled by '''edit''' method in the '''assignment_controllers'''. This method gathers all the information and calls '''edit''' view to display results.We are planning to add checkbox for this selection under '''Review Strategy''' tab of instructor view. If the instructor selects this checkbox, this feature will be active for the assignment.All these codes will be added in "assignments/edit/review_strategy" file since It displays all the elements in '''Review strategy''' tab. Controller will have an instance variable that stores the value of this checkbox that finally is stored in '''assignments''' database.

;Changes to student_review controller and views:
:Code that displays the student reviews is handled by the list action of the '''StudentReviewController''' (student_review_controller.rb) and the associated list view is "/views/student_review/list.html.erb" file. The '''@metareview_mappings''' refers to the reviews submitted by the student. We will check if the checkbox is checked for the assignment and if yes, will create another instance variable in the list action of the controller that queries reviews submitted for the same work by other students. We will also add a block of code in the list view that renders this data returned by this instance variable.

==Requirement 5==
===Problem===
The existing implementation of expertiza doesn’t provide a student the option to not see review scores or the text feedback. Sometimes a student might just want to see the scores and not the reviews and other times might want to see the reviews and not the scores. The ability to turn off either one is not provided by expertiza.

===Requirement===
When a student signs in there should be an option that allows the students to change the review score settings. The students will be provided with options of choosing either viewing only the review score or viewing only the text feedback or viewing both.

===Design===
;Student View Scores page changes:
:Student review scores is displayed in the View Score page and the /views/grades/view_my_score.html.erb file handles this operation. In this view we plan to provide a dropdown list in which the student can select if he/she wants to view scores only, view feedback only or both. The default setting will be to view both.
;Grades Controller changes:
:The view_my_score method in the grades controller performs the task of retrieving the scores and feedback from the database and also does various additional functions like calculating average, etc. In this method, based on the option chosen by the student either only scores or text feedback or both will be retreived. If the student does not explicitly specify any option then both the scores and feedback will be fetched.

File:DropReview.jpeg

2016-11-14T20:13:49Z

Ssdeshp5:

CSC/ECE 517 Fall 2016 E1678: Review configuration options

2016-11-09T19:30:09Z

Ssdeshp5: /* Design */

CSC/ECE 517 Fall 2016 E1678: Review configuration options

2016-11-09T19:29:18Z

Ssdeshp5: Added design for dropping reviews

CSC/ECE 517 Fall 2016/oss E1649 KPS

2016-11-04T00:03:13Z

Ssdeshp5: /* New Implementation */

==Expertiza==
Expertiza is an Open Source Software project developed by NCSU. It allows the instructor to create assignments as well as modify existing assignments. Students can signup for topics in an assignment and can submit articles, codes, web-sites etc. It is a web application built on Ruby on Rails framework. It also allows students to review the submissions that have been made other students.

==Current Implementation==
In the current implementation only the students can sign up for topics. Because of this, no higher authority (e.g instructor) can control the signups in a straightforward manner. If the instructor wishes to assign a particular topic to a team or remove a team from a particular topic then the instructor has to impersonate that student and sign up for the topic. Due, to the current implementation, you can neither handle the mistakes in signups , nor make modifications to the existing signups without impersonation.

==New Implementation==
The new implementation allows an instructor to assign a particular topic to a team as well as remove a team from a topic.This functionality has been added in views/sign_up_sheet/_all_actions.html.erb which now has a '+' sign to assign a topic to a particular user. If the instructor clicks on this, then a view will appear which takes in the username of a student to be added. When the box is filled out and the “add” button clicked, then the indicated user’s team is signed up for the topic. If there are no slots available for that topic then the team will be put on the waiting list. There is also a 'X' sign that will help the instructor to remove a team from a topic.

Some of the scenarios where the instructor might wish to add a team would be if the sign up deadline has passed, or if the instructor has decided to update the maximum number of teams allowed to choose a particular topic. The instructor might want to drop a team from the topic if the team doesn't want to proceed with the same topic for the assignment. With the new implementation, Instructors/Teaching Assistants do not need to go through the trouble of impersonating a student in order to add or drop their team from topics.

We have chosen the nested if-else approach because there were many scenarios , all of which required us to take different actions.
Changes were made in the following files -
* controllers/sign_up_sheet_controller.rb
* views/sign_up_sheet/_all_actions.html.erb
* views/sign_up_sheet/assign_topic.html.erb
* views/sign_up_sheet/remove_topic.html.erb

Functions added to implement functionality :-
* update_team
* assign_topic
* remove_team
* remove_topic

In the sign_up_sheet controller, two major methods were added:

===update_team===
This method allows an admin user to add a team to a particular topic, based on the username of any member of said team. If the number of teams already assigned to the topic is greater than or equal to the maximum number of teams allowed to pick the topic, the new team is added to the waitlist.
If a team was previously assigned a topic, and are then added by an admin to a new topic, their association with the old topic is deleted, and the required changes to the waitlist of topics are made as well.
The system will throw an error if the username of an invalid user is used to search for teams associated with the user.
The system checks that the topic is not being assigned again to the same team that has the topic.

===remove_team===
This method allows the admin to remove teams from a given topic, based on the username of a team member. First, a check is done to ensure that the team is indeed associated with the given topic. If this is the case, the entry is deleted from the table sign_up_teams, and the corresponding changes are made to the waitlist as well.

You can view our Pull Request [https://github.com/expertiza/expertiza/pull/794 here].

==Functionality==

[[File:Previous_View.png]][[File:New_View.png]]

Two additional icons have been added in the Actions column. The ‘green plus’ icon allows you to add a team to the current topic.
Clicking on the icon redirects you to a form, where the admin is required to enter the username of the person whose team he wishes to add.
[[File:Add_Team.png|centre]]

Clicking submit then redirects back to the original page, with a flash message containing the status of the operation.
[[File:Team_Added.png|centre]]

In case the topic has already been assigned the maximum number of teams, the new team is added to the waitlist.
[[File:Waitlisting.png|centre]]

The 'red cross' icon is used to remove a team from the given topic. Clicking on it takes the admin to a form, where he is required to enter the username of one of the team members belonging to the team that is to be removed. Submitting the form redirects the user back to the original page, with a flash message indicating the status of the remove operation.

[[File:Remove_Team.png|centre]]

==Scope for Improvement==
The system can take in individual users who don't have a team or topic and can add him/her to the existing teams that are enrolled for the topic.

==References==
#[https://github.com/expertiza/expertiza Expertiza on GitHub]
#[http://expertiza.ncsu.edu/ The live Expertiza website]
#[http://wiki.expertiza.ncsu.edu/index.php/Main_Page Expertiza wiki]

CSC/ECE 517 Fall 2016/oss E1649 KPS

2016-10-28T22:47:08Z

Ssdeshp5: /* New Implementation */

==Expertiza==
Expertiza is an Open Source Software project developed by NCSU. It allows the instructor to create assignments as well as modify existing assignments. Students can signup for topics in an assignment and can submit articles, codes, web-sites etc. It is a web application built on Ruby on Rails framework. It also allows students to review the submissions that have been made other students.

==Current Implementation==
In the current implementation only the students can sign up for topics. Because of this, no higher authority (e.g instructor) can control the signups in a straightforward manner. If the instructor wishes to assign a particular topic to a team or remove a team from a particular topic then the instructor has to impersonate that student and sign up for the topic. Due, to the current implementation, you can neither handle the mistakes in signups , nor make modifications to the existing signups without impersonation.

==New Implementation==
The new implementation allows an instructor to assign a particular topic to a team as well as remove a team from a topic.This functionality has been added in views/sign_up_sheet/_all_actions.html.erb which now has a '+' sign to assign a topic to a particular user. If the instructor clicks on this, then a view will appear which takes in the username of a student to be added. When the box is filled out and the “add” button clicked, then the indicated user’s team is signed up for the topic. If there are no slots available for that topic then the team will be put on the waiting list. There is also a 'X' sign that will help the instructor to remove a team from a topic.

Some of the scenarios where the instructor might wish to add a team would be if the sign up deadline has passed, or if the instructor has decided to update the maximum number of teams allowed to choose a particular topic. The instructor might want to drop a team from the topic if the team doesn't want to proceed with the same topic for the assignment. With the new implementation, Instructors/Teaching Assistants do not need to go through the trouble of impersonating a student in order to add or drop their team from topics.

Changes were made in the following files -
* controllers/sign_up_sheet_controller.rb
* views/sign_up_sheet/_all_actions.html.erb
* views/sign_up_sheet/assign_topic.html.erb
* views/sign_up_sheet/remove_topic.html.erb

Functions added to implement functionality :-
* update_team
* assign_topic
* remove_team
* remove_topic

In the sign_up_sheet controller, two major methods were added:

===update_team===
This method allows an admin user to add a team to a particular topic, based on the username of any member of said team. If the number of teams already assigned to the topic is greater than or equal to the maximum number of teams allowed to pick the topic, the new team is added to the waitlist.
If a team was previously assigned a topic, and are then added by an admin to a new topic, their association with the old topic is deleted, and the required changes to the waitlist of topics are made as well.
The system will throw an error if the username of an invalid user is used to search for teams associated with the user.
The system checks that the topic is not being assigned again to the same team that has the topic.

===remove_team===
This method allows the admin to remove teams from a given topic, based on the username of a team member. First, a check is done to ensure that the team is indeed associated with the given topic. If this is the case, the entry is deleted from the table sign_up_teams, and the corresponding changes are made to the waitlist as well.

You can view our Pull Request [https://github.com/expertiza/expertiza/pull/794 here].

==Functionality==

[[File:Previous_View.png]][[File:New_View.png]]

Two additional icons have been added in the Actions column. The ‘green plus’ icon allows you to add a team to the current topic.
Clicking on the icon redirects you to a form, where the admin is required to enter the username of the person whose team he wishes to add.
[[File:Add_Team.png|centre]]

Clicking submit then redirects back to the original page, with a flash message containing the status of the operation.
[[File:Team_Added.png|centre]]

In case the topic has already been assigned the maximum number of teams, the new team is added to the waitlist.
[[File:Waitlisting.png|centre]]

The 'red cross' icon is used to remove a team from the given topic. Clicking on it takes the admin to a form, where he is required to enter the username of one of the team members belonging to the team that is to be removed. Submitting the form redirects the user back to the original page, with a flash message indicating the status of the remove operation.

[[File:Remove_Team.png|centre]]

==Scope for Improvement==
The system can take in individual users who don't have a team or topic and can add him/her to the existing teams that are enrolled for the topic.

==References==
#[https://github.com/expertiza/expertiza Expertiza on GitHub]
#[http://expertiza.ncsu.edu/ The live Expertiza website]
#[http://wiki.expertiza.ncsu.edu/index.php/Main_Page Expertiza wiki]

CSC/ECE 517 Fall 2016/oss E1649 KPS

2016-10-28T22:07:23Z

Ssdeshp5:

==Expertiza==
Expertiza is an Open Source Software project developed by NCSU. It allows the instructor to create assignments as well as modify existing assignments. Students can signup for topics in an assignment and can submit articles, codes, web-sites etc. It is a web application built on Ruby on Rails framework. It also allows students to review the submissions that have been made other students.

==Current Implementation==
In the current implementation only the students can sign up for topics. Because of this, no higher authority (e.g instructor) can control the signups in a straightforward manner. If the instructor wishes to assign a particular topic to a team or remove a team from a particular topic then the instructor has to impersonate that student and sign up for the topic. Due, to the current implementation, you can neither handle the mistakes in signups , nor make modifications to the existing signups without impersonation.

==New Implementation==
The new implementation allows an instructor to assign a particular topic to a team as well as remove a team from a topic.This functionality has been added in views/sign_up_sheet/_all_actions.html.erb which now has a '+' sign to assign a topic to a particular user. If the instructor clicks on this, then a view will appear which takes in the username of a student to be added. When the box is filled out and the “add” button clicked, then the indicated user’s team is signed up for the topic. If there are no slots available for that topic then the team will be put on the waiting list. There is also a 'X' sign that will help the instructor to remove a team from a topic.

Some of the scenarios where the instructor might wish to add a team would be if the sign up deadline has passed, or if the instructor has decided to update the maximum number of teams allowed to choose a particular topic. The instructor might want to drop a team from the topic if the team doesn't want to proceed with the same topic for the assignment. With the new implementation, Instructors/Teaching Assistants do not need to go through the trouble of impersonating a student in order to add or drop their team from topics.

Changes were made in the following files -
* controllers/sign_up_sheet_controller.rb
* views/sign_up_sheet/_all_actions.html.erb
* views/sign_up_sheet/assign_topic.html.erb
* views/sign_up_sheet/remove_topic.html.erb

Functions added to implement functionality :-
* update_team
* assign_topic
* remove_team
* remove_topic

In the sign_up_sheet controller, two major methods were added:

===update_team===
This method allows an admin user to add a team to a particular topic, based on the username of any member of said team. If the number of teams already assigned to the topic is greater than or equal to the maximum number of teams allowed to pick the topic, the new team is added to the waitlist.
If a team was previously assigned a topic, and are then added by an admin to a new topic, their association with the old topic is deleted, and the required changes to the waitlist of topics are made as well.
The system will throw an error if the username of an invalid user is used to search for teams associated with the user.
The system checks that the topic is not being assigned again to the same team that has the topic.

===remove_team===
This method allows the admin to remove teams from a given topic, based on the username of a team member. First, a check is done to ensure that the team is indeed associated with the given topic. If this is the case, the entry is deleted from the table sign_up_teams, and the corresponding changes are made to the waitlist as well.

You can view our Pull Request [https://github.com/expertiza/expertiza/pull/789 here].

==Functionality==

[[File:Previous_View.png]][[File:New_View.png]]

Two additional icons have been added in the Actions column. The ‘green plus’ icon allows you to add a team to the current topic.
Clicking on the icon redirects you to a form, where the admin is required to enter the username of the person whose team he wishes to add.
[[File:Add_Team.png|centre]]

Clicking submit then redirects back to the original page, with a flash message containing the status of the operation.
[[File:Team_Added.png|centre]]

In case the topic has already been assigned the maximum number of teams, the new team is added to the waitlist.
[[File:Waitlisting.png|centre]]

The 'red cross' icon is used to remove a team from the given topic. Clicking on it takes the admin to a form, where he is required to enter the username of one of the team members belonging to the team that is to be removed. Submitting the form redirects the user back to the original page, with a flash message indicating the status of the remove operation.

[[File:Remove_Team.png|centre]]

==Scope for Improvement==
The system can take in individual users who don't have a team or topic and can add him/her to the existing teams that are enrolled for the topic.

==References==
#[https://github.com/expertiza/expertiza Expertiza on GitHub]
#[http://expertiza.ncsu.edu/ The live Expertiza website]
#[http://wiki.expertiza.ncsu.edu/index.php/Main_Page Expertiza wiki]

CSC/ECE 517 Fall 2016/oss E1649 KPS

2016-10-28T21:51:17Z

Ssdeshp5:

==Expertiza==
Expertiza is an Open Source Software project developed by NCSU. It allows the instructor to create assignments as well as modify existing assignments. Students can signup for topics in an assignment and can submit articles, codes, web-sites etc. It is a web application built on Ruby on Rails framework. It also allows students to review the submissions that have been made other students.

==Current Implementation==
In the current implementation only the students can sign up for topics. Because of this, no higher authority (e.g instructor) can control the signups in a straightforward manner. If the instructor wishes to assign a particular topic to a team or remove a team from a particular topic then the instructor has to impersonate that student and sign up for the topic. Due, to the current implementation, you can neither handle the mistakes in signups , nor make modifications to the existing signups without impersonation.

==New Implementation==
The new implementation allows an instructor to assign a particular topic to a team as well as remove a team from a topic.This functionality has been added in views/sign_up_sheet/_all_actions.html.erb which now has a '+' sign to assign a topic to a particular user. If the instructor clicks on this, then a view will appear which takes in the username of a student to be added. When the box is filled out and the “add” button clicked, then the indicated user’s team is signed up for the topic. If there are no slots available for that topic then the team will be put on the waiting list. There is also a 'X' sign that will help the instructor to remove a team from a topic.

Some of the scenarios where the instructor might wish to add a team would be if the sign up deadline has passed, or if the instructor has decided to update the maximum number of teams allowed to choose a particular topic. The instructor might want to drop a team from the topic if the team doesn't want to proceed with the same topic for the assignment. With the new implementation, Instructors/Teaching Assistants do not need to go through the trouble of impersonating a student in order to add or drop their team from topics.

Changes were made in the following files -
* controllers/sign_up_sheet_controller.rb
* views/sign_up_sheet/_all_actions.html.erb
* views/sign_up_sheet/assign_topic.html.erb
* views/sign_up_sheet/remove_topic.html.erb

Functions added to implement functionality :-
* update_team
* assign_topic
* remove_team
* remove_topic

In the sign_up_sheet controller, two major methods were added:

===update_team===
This method allows an admin user to add a team to a particular topic, based on the username of any member of said team. If the number of teams already assigned to the topic is greater than or equal to the maximum number of teams allowed to pick the topic, the new team is added to the waitlist.
If a team was previously assigned a topic, and are then added by an admin to a new topic, their association with the old topic is deleted, and the required changes to the waitlist of topics are made as well.
The system will throw an error if the username of an invalid user is used to search for teams associated with the user.
The system checks that the topic is not being assigned again to the same team that has the topic.

===remove_team===
This method allows the admin to remove teams from a given topic, based on the username of a team member. First, a check is done to ensure that the team is indeed associated with the given topic. If this is the case, the entry is deleted from the table sign_up_teams, and the corresponding changes are made to the waitlist as well.

You can view our Pull Request [https://github.com/expertiza/expertiza/pull/785 here].

==Functionality==

[[File:Previous_View.png]][[File:New_View.png]]

Two additional icons have been added in the Actions column. The ‘green plus’ icon allows you to add a team to the current topic.
Clicking on the icon redirects you to a form, where the admin is required to enter the username of the person whose team he wishes to add.
[[File:Add_Team.png|centre]]

Clicking submit then redirects back to the original page, with a flash message containing the status of the operation.
[[File:Team_Added.png|centre]]

In case the topic has already been assigned the maximum number of teams, the new team is added to the waitlist.
[[File:Waitlisting.png|centre]]

The 'red cross' icon is used to remove a team from the given topic. Clicking on it takes the admin to a form, where he is required to enter the username of one of the team members belonging to the team that is to be removed. Submitting the form redirects the user back to the original page, with a flash message indicating the status of the remove operation.

[[File:Remove_Team.png|centre]]

==Scope for Improvement==
The system can take in individual users who don't have a team or topic and can add him/her to the existing teams that are enrolled for the topic.

==References==
#[https://github.com/expertiza/expertiza Expertiza on GitHub]
#[http://expertiza.ncsu.edu/ The live Expertiza website]
#[http://wiki.expertiza.ncsu.edu/index.php/Main_Page Expertiza wiki]

CSC/ECE 517 Fall 2016/oss E1649 KPS

2016-10-28T21:49:44Z

Ssdeshp5: /* New Implementation [https://github.com/expertiza/expertiza/pull/785] */

==Expertiza==
Expertiza is an Open Source Software project developed by NCSU. It allows the instructor to create assignments as well as modify existing assignments. Students can signup for topics in an assignment and can submit articles, codes, web-sites etc. It is a web application built on Ruby on Rails framework. It also allows students to review the submissions that have been made other students.

==Current Implementation==
In the current implementation only the students can sign up for topics. Because of this, no higher authority (e.g instructor) can control the signups in a straightforward manner. If the instructor wishes to assign a particular topic to a team or remove a team from a particular topic then the instructor has to impersonate that student and sign up for the topic. Due, to the current implementation, you can neither handle the mistakes in signups , nor make modifications to the existing signups without impersonation.

==New Implementation==
The new implementation allows an instructor to assign a particular topic to a team as well as remove a team from a topic.This functionality has been added in views/sign_up_sheet/_all_actions.html.erb which now has a '+' sign to assign a topic to a particular user. If the instructor clicks on this, then a view will appear which takes in the username of a student to be added. When the box is filled out and the “add” button clicked, then the indicated user’s team is signed up for the topic. If there are no slots available for that topic then the team will be put on the waiting list. There is also a 'X' sign that will help the instructor to remove a team from a topic.

Some of the scenarios where the instructor might wish to add a team would be if the sign up deadline has passed, or if the instructor has decided to update the maximum number of teams allowed to choose a particular topic. The instructor might want to drop a team from the topic if the team doesn't want to proceed with the same topic for the assignment. With the new implementation, Instructors/Teaching Assistants do not need to go through the trouble of impersonating a student in order to add or drop their team from topics.

Changes were made in the following files -
* controllers/sign_up_sheet_controller.rb
* views/sign_up_sheet/_all_actions.html.erb
* views/sign_up_sheet/assign_topic.html.erb
* views/sign_up_sheet/remove_topic.html.erb

Functions added to implement functionality :-
* update_team
* assign_topic
* remove_team
* remove_topic

In the sign_up_sheet controller, two major methods were added:

===update_team===
This method allows an admin user to add a team to a particular topic, based on the username of any member of said team. If the number of teams already assigned to the topic is greater than or equal to the maximum number of teams allowed to pick the topic, the new team is added to the waitlist.
If a team was previously assigned a topic, and are then added by an admin to a new topic, their association with the old topic is deleted, and the required changes to the waitlist of topics are made as well.
The system will throw an error if the username of an invalid user is used to search for teams associated with the user.
The system checks that the topic is not being assigned again to the same team that has the topic.

===remove_team===
This method allows the admin to remove teams from a given topic, based on the username of a team member. First, a check is done to ensure that the team is indeed associated with the given topic. If this is the case, the entry is deleted from the table sign_up_teams, and the corresponding changes are made to the waitlist as well.

You can view our Pull Request at [[https://github.com/expertiza/expertiza/pull/785]].

==Functionality==

[[File:Previous_View.png]][[File:New_View.png]]

Two additional icons have been added in the Actions column. The ‘green plus’ icon allows you to add a team to the current topic.
Clicking on the icon redirects you to a form, where the admin is required to enter the username of the person whose team he wishes to add.
[[File:Add_Team.png|centre]]

Clicking submit then redirects back to the original page, with a flash message containing the status of the operation.
[[File:Team_Added.png|centre]]

In case the topic has already been assigned the maximum number of teams, the new team is added to the waitlist.
[[File:Waitlisting.png|centre]]

The 'red cross' icon is used to remove a team from the given topic. Clicking on it takes the admin to a form, where he is required to enter the username of one of the team members belonging to the team that is to be removed. Submitting the form redirects the user back to the original page, with a flash message indicating the status of the remove operation.

[[File:Remove_Team.png|centre]]

==Scope for Improvement==
The system can take in individual users who don't have a team or topic and can add him/her to the existing teams that are enrolled for the topic.

==References==
#[https://github.com/expertiza/expertiza Expertiza on GitHub]
#[http://expertiza.ncsu.edu/ The live Expertiza website]
#[http://wiki.expertiza.ncsu.edu/index.php/Main_Page Expertiza wiki]

CSC/ECE 517 Fall 2016/oss E1649 KPS

2016-10-28T21:47:23Z

Ssdeshp5: /* Current Implementation */

==Expertiza==
Expertiza is an Open Source Software project developed by NCSU. It allows the instructor to create assignments as well as modify existing assignments. Students can signup for topics in an assignment and can submit articles, codes, web-sites etc. It is a web application built on Ruby on Rails framework. It also allows students to review the submissions that have been made other students.

==Current Implementation==
In the current implementation only the students can sign up for topics. Because of this, no higher authority (e.g instructor) can control the signups in a straightforward manner. If the instructor wishes to assign a particular topic to a team or remove a team from a particular topic then the instructor has to impersonate that student and sign up for the topic. Due, to the current implementation, you can neither handle the mistakes in signups , nor make modifications to the existing signups without impersonation.

==New Implementation <small><small>[https://github.com/expertiza/expertiza/pull/785]</small></small>==
The new implementation allows an instructor to assign a particular topic to a team as well as remove a team from a topic.This functionality has been added in views/sign_up_sheet/_all_actions.html.erb which now has a '+' sign to assign a topic to a particular user. If the instructor clicks on this, then a view will appear which takes in the username of a student to be added. When the box is filled out and the “add” button clicked, then the indicated user’s team is signed up for the topic. If there are no slots available for that topic then the team will be put on the waiting list. There is also a 'X' sign that will help the instructor to remove a team from a topic.

Some of the scenarios where the instructor might wish to add a team would be if the sign up deadline has passed, or if the instructor has decided to update the maximum number of teams allowed to choose a particular topic. The instructor might want to drop a team from the topic if the team doesn't want to proceed with the same topic for the assignment. With the new implementation, Instructors/Teaching Assistants do not need to go through the trouble of impersonating a student in order to add or drop their team from topics.

Changes were made in the following files -
* controllers/sign_up_sheet_controller.rb
* views/sign_up_sheet/_all_actions.html.erb
* views/sign_up_sheet/assign_topic.html.erb
* views/sign_up_sheet/remove_topic.html.erb

Functions added to implement functionality :-
* update_team
* assign_topic
* remove_team
* remove_topic

In the sign_up_sheet controller, two major methods were added:

===update_team===
This method allows an admin user to add a team to a particular topic, based on the username of any member of said team. If the number of teams already assigned to the topic is greater than or equal to the maximum number of teams allowed to pick the topic, the new team is added to the waitlist.
If a team was previously assigned a topic, and are then added by an admin to a new topic, their association with the old topic is deleted, and the required changes to the waitlist of topics are made as well.
The system will throw an error if the username of an invalid user is used to search for teams associated with the user.
The system checks that the topic is not being assigned again to the same team that has the topic.

===remove_team===
This method allows the admin to remove teams from a given topic, based on the username of a team member. First, a check is done to ensure that the team is indeed associated with the given topic. If this is the case, the entry is deleted from the table sign_up_teams, and the corresponding changes are made to the waitlist as well.

==Functionality==

[[File:Previous_View.png]][[File:New_View.png]]

Two additional icons have been added in the Actions column. The ‘green plus’ icon allows you to add a team to the current topic.
Clicking on the icon redirects you to a form, where the admin is required to enter the username of the person whose team he wishes to add.
[[File:Add_Team.png|centre]]

Clicking submit then redirects back to the original page, with a flash message containing the status of the operation.
[[File:Team_Added.png|centre]]

In case the topic has already been assigned the maximum number of teams, the new team is added to the waitlist.
[[File:Waitlisting.png|centre]]

The 'red cross' icon is used to remove a team from the given topic. Clicking on it takes the admin to a form, where he is required to enter the username of one of the team members belonging to the team that is to be removed. Submitting the form redirects the user back to the original page, with a flash message indicating the status of the remove operation.

[[File:Remove_Team.png|centre]]

==Scope for Improvement==
The system can take in individual users who don't have a team or topic and can add him/her to the existing teams that are enrolled for the topic.

==References==
#[https://github.com/expertiza/expertiza Expertiza on GitHub]
#[http://expertiza.ncsu.edu/ The live Expertiza website]
#[http://wiki.expertiza.ncsu.edu/index.php/Main_Page Expertiza wiki]

CSC/ECE 517 Fall 2016/oss E1649 KPS

2016-10-28T21:46:19Z

Ssdeshp5:

==Expertiza==
Expertiza is an Open Source Software project developed by NCSU. It allows the instructor to create assignments as well as modify existing assignments. Students can signup for topics in an assignment and can submit articles, codes, web-sites etc. It is a web application built on Ruby on Rails framework. It also allows students to review the submissions that have been made other students.

==Current Implementation==
In the current implementation only the students can sign up for topics. Because of this, no higher authority (e.g instructor) can control the signups in a straightforward manner. If the instructor wishes to assign a particular topic to a team or remove a team from a particular topic then the instructor has to impersonate that student and sign up for the topic. Due, to the current implementation, you can neither handle the mistakes in signups , nor make modifications to the existing signups without impersonation.

==New Implementation== [https://github.com/expertiza/expertiza/pull/785]
The new implementation allows an instructor to assign a particular topic to a team as well as remove a team from a topic.This functionality has been added in views/sign_up_sheet/_all_actions.html.erb which now has a '+' sign to assign a topic to a particular user. If the instructor clicks on this, then a view will appear which takes in the username of a student to be added. When the box is filled out and the “add” button clicked, then the indicated user’s team is signed up for the topic. If there are no slots available for that topic then the team will be put on the waiting list. There is also a 'X' sign that will help the instructor to remove a team from a topic.

Some of the scenarios where the instructor might wish to add a team would be if the sign up deadline has passed, or if the instructor has decided to update the maximum number of teams allowed to choose a particular topic. The instructor might want to drop a team from the topic if the team doesn't want to proceed with the same topic for the assignment. With the new implementation, Instructors/Teaching Assistants do not need to go through the trouble of impersonating a student in order to add or drop their team from topics.

Changes were made in the following files -
* controllers/sign_up_sheet_controller.rb
* views/sign_up_sheet/_all_actions.html.erb
* views/sign_up_sheet/assign_topic.html.erb
* views/sign_up_sheet/remove_topic.html.erb

Functions added to implement functionality :-
* update_team
* assign_topic
* remove_team
* remove_topic

In the sign_up_sheet controller, two major methods were added:

===update_team===
This method allows an admin user to add a team to a particular topic, based on the username of any member of said team. If the number of teams already assigned to the topic is greater than or equal to the maximum number of teams allowed to pick the topic, the new team is added to the waitlist.
If a team was previously assigned a topic, and are then added by an admin to a new topic, their association with the old topic is deleted, and the required changes to the waitlist of topics are made as well.
The system will throw an error if the username of an invalid user is used to search for teams associated with the user.
The system checks that the topic is not being assigned again to the same team that has the topic.

===remove_team===
This method allows the admin to remove teams from a given topic, based on the username of a team member. First, a check is done to ensure that the team is indeed associated with the given topic. If this is the case, the entry is deleted from the table sign_up_teams, and the corresponding changes are made to the waitlist as well.

==Functionality==

[[File:Previous_View.png]][[File:New_View.png]]

Two additional icons have been added in the Actions column. The ‘green plus’ icon allows you to add a team to the current topic.
Clicking on the icon redirects you to a form, where the admin is required to enter the username of the person whose team he wishes to add.
[[File:Add_Team.png|centre]]

Clicking submit then redirects back to the original page, with a flash message containing the status of the operation.
[[File:Team_Added.png|centre]]

In case the topic has already been assigned the maximum number of teams, the new team is added to the waitlist.
[[File:Waitlisting.png|centre]]

The 'red cross' icon is used to remove a team from the given topic. Clicking on it takes the admin to a form, where he is required to enter the username of one of the team members belonging to the team that is to be removed. Submitting the form redirects the user back to the original page, with a flash message indicating the status of the remove operation.

[[File:Remove_Team.png|centre]]

==Scope for Improvement==
The system can take in individual users who don't have a team or topic and can add him/her to the existing teams that are enrolled for the topic.

==References==
#[https://github.com/expertiza/expertiza Expertiza on GitHub]
#[http://expertiza.ncsu.edu/ The live Expertiza website]
#[http://wiki.expertiza.ncsu.edu/index.php/Main_Page Expertiza wiki]

CSC/ECE 517 Fall 2016/oss E1649 KPS

2016-10-28T21:40:31Z

Ssdeshp5:

==Expertiza==
Expertiza is an Open Source Software project developed by NCSU. It allows the instructor to create assignments as well as modify existing assignments. Students can signup for topics in an assignment and can submit articles, codes, web-sites etc. It is a web application built on Ruby on Rails framework. It also allows students to review the submissions that have been made other students.

==Current Implementation==
In the current implementation only the students can sign up for topics. Because of this, no higher authority (e.g instructor) can control the signups in a straightforward manner. If the instructor wishes to assign a particular topic to a team or remove a team from a particular topic then the instructor has to impersonate that student and sign up for the topic. Due, to the current implementation, you can neither handle the mistakes in signups , nor make modifications to the existing signups without impersonation.

==New Implementation==
The new implementation allows an instructor to assign a particular topic to a team as well as remove a team from a topic.This functionality has been added in views/sign_up_sheet/_all_actions.html.erb which now has a '+' sign to assign a topic to a particular user. If the instructor clicks on this, then a view will appear which takes in the username of a student to be added. When the box is filled out and the “add” button clicked, then the indicated user’s team is signed up for the topic. If there are no slots available for that topic then the team will be put on the waiting list. There is also a 'X' sign that will help the instructor to remove a team from a topic.

Some of the scenarios where the instructor might wish to add a team would be if the sign up deadline has passed, or if the instructor has decided to update the maximum number of teams allowed to choose a particular topic. The instructor might want to drop a team from the topic if the team doesn't want to proceed with the same topic for the assignment. With the new implementation, Instructors/Teaching Assistants do not need to go through the trouble of impersonating a student in order to add or drop their team from topics.

Changes were made in the following files -
* controllers/sign_up_sheet_controller.rb
* views/sign_up_sheet/_all_actions.html.erb
* views/sign_up_sheet/assign_topic.html.erb
* views/sign_up_sheet/remove_topic.html.erb

Functions added to implement functionality :-
* update_team
* assign_topic
* remove_team
* remove_topic

In the sign_up_sheet controller, two major methods were added:

===update_team===
This method allows an admin user to add a team to a particular topic, based on the username of any member of said team. If the number of teams already assigned to the topic is greater than or equal to the maximum number of teams allowed to pick the topic, the new team is added to the waitlist.
If a team was previously assigned a topic, and are then added by an admin to a new topic, their association with the old topic is deleted, and the required changes to the waitlist of topics are made as well.
The system will throw an error if the username of an invalid user is used to search for teams associated with the user.
The system checks that the topic is not being assigned again to the same team that has the topic.

===remove_team===
This method allows the admin to remove teams from a given topic, based on the username of a team member. First, a check is done to ensure that the team is indeed associated with the given topic. If this is the case, the entry is deleted from the table sign_up_teams, and the corresponding changes are made to the waitlist as well.

==Functionality==

[[File:Previous_View.png]][[File:New_View.png]]

Two additional icons have been added in the Actions column. The ‘green plus’ icon allows you to add a team to the current topic.
Clicking on the icon redirects you to a form, where the admin is required to enter the username of the person whose team he wishes to add.
[[File:Add_Team.png|centre]]

Clicking submit then redirects back to the original page, with a flash message containing the status of the operation.
[[File:Team_Added.png|centre]]

In case the topic has already been assigned the maximum number of teams, the new team is added to the waitlist.
[[File:Waitlisting.png|centre]]

The 'red cross' icon is used to remove a team from the given topic. Clicking on it takes the admin to a form, where he is required to enter the username of one of the team members belonging to the team that is to be removed. Submitting the form redirects the user back to the original page, with a flash message indicating the status of the remove operation.

[[File:Remove_Team.png|centre]]

==Scope for Improvement==
The system can take in individual users who don't have a team or topic and can add him/her to the existing teams that are enrolled for the topic.

==References==
#[https://github.com/expertiza/expertiza Expertiza on GitHub]
#[http://expertiza.ncsu.edu/ The live Expertiza website]
#[http://wiki.expertiza.ncsu.edu/index.php/Main_Page Expertiza wiki]

CSC/ECE 517 Fall 2016/oss E1649 KPS

2016-10-28T21:33:11Z

Ssdeshp5: /* Problem Statement : Allow instructor to sign students up for topics and drop them */

==Expertiza==
Expertiza is an Open Source Software project developed by NCSU through which students can submit and peer-review learning objects such as articles, codes, web-sites etc. It is a web application built on Ruby on Rails framework.

==Current Implementation==
In the current implementation only the students can sign up for topics. Because of this, no higher authority (e.g instructor) can control the signups in a straightforward manner. If the instructor wishes to assign a particular topic to a team or remove a team from a particular topic then the instructor has to impersonate that student and sign up for the topic. Due, to the current implementation, you can neither handle the mistakes in signups , nor make modifications to the existing signups without impersonation.

==New Implementation==
The new implementation allows an instructor to assign a particular topic to a team as well as remove a team from a topic.This functionality has been added in views/sign_up_sheet/_all_actions.html.erb which now has a '+' sign to assign a topic to a particular user. If the instructor clicks on this, then a view will appear which takes in the username of a student to be added. When the box is filled out and the “search” button clicked, then the indicated user’s team is signed up for the topic. If there are no slots available for that topic then the team will be put on the waiting list. There is also a 'X' sign that will help the instructor to remove a team from a topic.

Some of the scenarios where the instructor might wish to add a team would be if the sign up deadline has passed, or if the instructor has decided to update the maximum number of teams allowed to choose a particular topic. The instructor might want to drop a team from the topic if the team doesn't want to proceed with the same topic for the assignment. With the new implementation, Instructors/Teaching Assistants do not need to go through the trouble of impersonating a student in order to add or drop their team from topics.

Changes were made in the following files -
* controllers/sign_up_sheet_controller.rb
* views/sign_up_sheet/_all_actions.html.erb
* views/sign_up_sheet/assign_topic.html.erb
* views/sign_up_sheet/remove_topic.html.erb

Functions added to implement functionality :-
* update_team
* assign_topic
* remove_team
* remove_topic

In the sign_up_sheet controller, two major methods were added:

===update_team===
This method allows an admin user to add a team to a particular topic, based on the username of any member of said team. If the number of teams already assigned to the topic is greater than or equal to the maximum number of teams allowed to pick the topic, the new team is added to the waitlist.
If a team was previously assigned a topic, and are then added by an admin to a new topic, their association with the old topic is deleted, and the required changes to the waitlist of topics are made as well.
The system will throw an error if the username of an invalid user is used to search for teams associated with the user.
The system checks that the topic is not being assigned again to the same team that has the topic.

===remove_team===
This method allows the admin to remove teams from a given topic, based on the username of a team member. First, a check is done to ensure that the team is indeed associated with the given topic. If this is the case, the entry is deleted from the table sign_up_teams, and the corresponding changes are made to the waitlist as well.

==Functionality==

[[File:Previous_View.png]][[File:New_View.png]]

Two additional icons have been added in the Actions column. The ‘green plus’ icon allows you to add a team to the current topic.
Clicking on the icon redirects you to a form, where the admin is required to enter the username of the person whose team he wishes to add.
[[File:Add_Team.png|centre]]

Clicking submit then redirects back to the original page, with a flash message containing the status of the operation.
[[File:Team_Added.png|centre]]

In case the topic has already been assigned the maximum number of teams, the new team is added to the waitlist.
[[File:Waitlisting.png|centre]]

The 'red cross' icon is used to remove a team from the given topic. Clicking on it takes the admin to a form, where he is required to enter the username of one of the team members belonging to the team that is to be removed. Submitting the form redirects the user back to the original page, with a flash message indicating the status of the remove operation.

[[File:Remove_Team.png|centre]]

==Scope for Improvement==
The system can take in individual users who don't have a team or topic and can add him/her to the existing teams that are enrolled for the topic.

==References==
#[https://github.com/expertiza/expertiza Expertiza on GitHub]
#[http://expertiza.ncsu.edu/ The live Expertiza website]
#[http://wiki.expertiza.ncsu.edu/index.php/Main_Page Expertiza wiki]

CSC/ECE 517 Fall 2016/oss E1649 KPS

2016-10-28T21:26:47Z

Ssdeshp5: /* Expertiza */

==Expertiza==
Expertiza is an Open Source Software project developed by NCSU through which students can submit and peer-review learning objects such as articles, codes, web-sites etc. It is a web application built on Ruby on Rails framework.

==Problem Statement : Allow instructor to sign students up for topics and drop them==
In the current implementation only the students can sign up for topics. Because of this, no higher authority (e.g instructor) can control the signups in a straightforward manner. If the instructor wishes to assign a particular topic to a team or remove a team from a particular topic then the instructor has to impersonate that student and sign up for the topic. Due, to the current implementation, you can neither handle the mistakes in signups , nor make modifications to the existing signups without impersonation.

==New Implementation==
The new implementation allows an instructor to assign a particular topic to a team as well as remove a team from a topic.This functionality has been added in views/sign_up_sheet/_all_actions.html.erb which now has a '+' sign to assign a topic to a particular user. If the instructor clicks on this, then a view will appear which takes in the username of a student to be added. When the box is filled out and the “search” button clicked, then the indicated user’s team is signed up for the topic. If there are no slots available for that topic then the team will be put on the waiting list. There is also a 'X' sign that will help the instructor to remove a team from a topic.

Some of the scenarios where the instructor might wish to add a team would be if the sign up deadline has passed, or if the instructor has decided to update the maximum number of teams allowed to choose a particular topic. The instructor might want to drop a team from the topic if the team doesn't want to proceed with the same topic for the assignment. With the new implementation, Instructors/Teaching Assistants do not need to go through the trouble of impersonating a student in order to add or drop their team from topics.

Changes were made in the following files -
* controllers/sign_up_sheet_controller.rb
* views/sign_up_sheet/_all_actions.html.erb
* views/sign_up_sheet/assign_topic.html.erb
* views/sign_up_sheet/remove_topic.html.erb

Functions added to implement functionality :-
* update_team
* assign_topic
* remove_team
* remove_topic

In the sign_up_sheet controller, two major methods were added:

===update_team===
This method allows an admin user to add a team to a particular topic, based on the username of any member of said team. If the number of teams already assigned to the topic is greater than or equal to the maximum number of teams allowed to pick the topic, the new team is added to the waitlist.
If a team was previously assigned a topic, and are then added by an admin to a new topic, their association with the old topic is deleted, and the required changes to the waitlist of topics are made as well.
The system will throw an error if the username of an invalid user is used to search for teams associated with the user.
The system checks that the topic is not being assigned again to the same team that has the topic.

===remove_team===
This method allows the admin to remove teams from a given topic, based on the username of a team member. First, a check is done to ensure that the team is indeed associated with the given topic. If this is the case, the entry is deleted from the table sign_up_teams, and the corresponding changes are made to the waitlist as well.

==Functionality==

[[File:Previous_View.png]][[File:New_View.png]]

Two additional icons have been added in the Actions column. The ‘green plus’ icon allows you to add a team to the current topic.
Clicking on the icon redirects you to a form, where the admin is required to enter the username of the person whose team he wishes to add.
[[File:Add_Team.png|centre]]

Clicking submit then redirects back to the original page, with a flash message containing the status of the operation.
[[File:Team_Added.png|centre]]

In case the topic has already been assigned the maximum number of teams, the new team is added to the waitlist.
[[File:Waitlisting.png|centre]]

The 'red cross' icon is used to remove a team from the given topic. Clicking on it takes the admin to a form, where he is required to enter the username of one of the team members belonging to the team that is to be removed. Submitting the form redirects the user back to the original page, with a flash message indicating the status of the remove operation.

[[File:Remove_Team.png|centre]]

==Scope for Improvement==
The system can take in individual users who don't have a team or topic and can add him/her to the existing teams that are enrolled for the topic.

==References==
#[https://github.com/expertiza/expertiza Expertiza on GitHub]
#[http://expertiza.ncsu.edu/ The live Expertiza website]
#[http://wiki.expertiza.ncsu.edu/index.php/Main_Page Expertiza wiki]

CSC/ECE 517 Fall 2016/oss E1649 KPS

2016-10-28T21:17:47Z

Ssdeshp5:

==Expertiza==
Expertiza is an open source project based on Ruby on Rails framework. It is an efficient assignment management portal that allows instructor to create new assignments as well modify existing assignments which in turn have multiple topics for which students can sign up for. Students can form teams in Expertiza to work on the assignments and Expertiza also provides functionality to advertise for team members. Students can peer review other submissions and provide feedback about the same.

==Problem Statement : Allow instructor to sign students up for topics and drop them==
In the current implementation only the students can sign up for topics. Because of this, no higher authority (e.g instructor) can control the signups in a straightforward manner. If the instructor wishes to assign a particular topic to a team or remove a team from a particular topic then the instructor has to impersonate that student and sign up for the topic. Due, to the current implementation, you can neither handle the mistakes in signups , nor make modifications to the existing signups without impersonation.

==New Implementation==
The new implementation allows an instructor to assign a particular topic to a team as well as remove a team from a topic.This functionality has been added in views/sign_up_sheet/_all_actions.html.erb which now has a '+' sign to assign a topic to a particular user. If the instructor clicks on this, then a view will appear which takes in the username of a student to be added. When the box is filled out and the “search” button clicked, then the indicated user’s team is signed up for the topic. If there are no slots available for that topic then the team will be put on the waiting list. There is also a 'X' sign that will help the instructor to remove a team from a topic.

Some of the scenarios where the instructor might wish to add a team would be if the sign up deadline has passed, or if the instructor has decided to update the maximum number of teams allowed to choose a particular topic. The instructor might want to drop a team from the topic if the team doesn't want to proceed with the same topic for the assignment. With the new implementation, Instructors/Teaching Assistants do not need to go through the trouble of impersonating a student in order to add or drop their team from topics.

Changes were made in the following files -
* controllers/sign_up_sheet_controller.rb
* views/sign_up_sheet/_all_actions.html.erb
* views/sign_up_sheet/assign_topic.html.erb
* views/sign_up_sheet/remove_topic.html.erb

Functions added to implement functionality :-
* update_team
* assign_topic
* remove_team
* remove_topic

In the sign_up_sheet controller, two major methods were added:

===update_team===
This method allows an admin user to add a team to a particular topic, based on the username of any member of said team. If the number of teams already assigned to the topic is greater than or equal to the maximum number of teams allowed to pick the topic, the new team is added to the waitlist.
If a team was previously assigned a topic, and are then added by an admin to a new topic, their association with the old topic is deleted, and the required changes to the waitlist of topics are made as well.
The system will throw an error if the username of an invalid user is used to search for teams associated with the user.
The system checks that the topic is not being assigned again to the same team that has the topic.

===remove_team===
This method allows the admin to remove teams from a given topic, based on the username of a team member. First, a check is done to ensure that the team is indeed associated with the given topic. If this is the case, the entry is deleted from the table sign_up_teams, and the corresponding changes are made to the waitlist as well.

==Functionality==

[[File:Previous_View.png]][[File:New_View.png]]

Two additional icons have been added in the Actions column. The ‘green plus’ icon allows you to add a team to the current topic.
Clicking on the icon redirects you to a form, where the admin is required to enter the username of the person whose team he wishes to add.
[[File:Add_Team.png|centre]]

Clicking submit then redirects back to the original page, with a flash message containing the status of the operation.
[[File:Team_Added.png|centre]]

In case the topic has already been assigned the maximum number of teams, the new team is added to the waitlist.
[[File:Waitlisting.png|centre]]

The 'red cross' icon is used to remove a team from the given topic. Clicking on it takes the admin to a form, where he is required to enter the username of one of the team members belonging to the team that is to be removed. Submitting the form redirects the user back to the original page, with a flash message indicating the status of the remove operation.

[[File:Remove_Team.png|centre]]

==Scope for Improvement==
The system can take in individual users who don't have a team or topic and can add him/her to the existing teams that are enrolled for the topic.

==References==
#[https://github.com/expertiza/expertiza Expertiza on GitHub]
#[http://expertiza.ncsu.edu/ The live Expertiza website]
#[http://wiki.expertiza.ncsu.edu/index.php/Main_Page Expertiza wiki]

CSC/ECE 517 Fall 2016

2016-10-28T21:14:44Z

Ssdeshp5: /* Writing Assignments 2 */

[http://www.example.com link title]==Calibration Assignment Submissions==
*[[Calibration Assignment Submission (Firebrick JS)]]
*[[Calibration Assignment Submission (Active Job)]]
==Writing Assignments 2==
*[[CSC/ECE 517 Fall 2016/E1666. Test team functionality]]
*[[CSC/ECE 517 Fall 2016/E1643. Refactor Suggestion controller]]
*[[CSC/ECE 517 Fall 2016/E1631. Refactoring Bidding Interface]]
*[[CSC/ECE 517 Fall 2016/E1674.Refactor leaderboard.rb and write unit tests]]
*[[CSC/ECE 517 Fall 2016/E1668.Test e-mailing functionality]]
*[[CSC/ECE 517 Fall 2016/E1658. Refractor lottery_controller.rb and write integration tests]]
*[[CSC/ECE 517 Fall 2016/E1660. Review requirements and thresholds]]
*[[CSC/ECE 517 Fall 2016/E1650. Sort instructor views alphabetically by default]]
*[[CSC/ECE 517 Fall 2016/E1644. Refactor and test Teams Controller]]
*[[CSC/ECE 517 Fall 2016/E1659. Refactor on_the_fly_calc.rb]]
*[[CSC/ECE 517 Fall 2016/E1657. Introduce a Student View for instructors]]
*[[CSC/ECE 517 Fall 2016/E1653. Fix and improve rubric criteria]]
*[[CSC/ECE 517 Fall 2016/E1642. Refactor review_response_map.rb]]
*[[CSC/ECE 517 Fall 2016/E1666. Test team functionality]]
*[[CSC/ECE_517_Fall_2016/E1654. Improve_date-picker_and_deadlines]]
*[[CSC/ECE_517_Fall_2016/E1652 Fix teammate advertisements and requests to join a team ]]
*[[CSC/ECE_517_Fall_2016/E1662. UI issues/fixes]]
*[[CSC/ECE_517_Fall_2016/E1673. Refactor question_type.rb]]
*[[CSC/ECE_517_Fall_2016/E1675. Timestamp for student file & hyperlink submissions]]

CSC/ECE 517 Fall 2016

2016-10-28T21:13:58Z

Ssdeshp5: /* Writing Assignments 2 */

CSC/ECE 517 Fall 2016/oss E1649 KPS

2016-10-28T21:08:58Z

Ssdeshp5: Added scope for improvement

==Expertiza==
Expertiza is an open source project based on Ruby on Rails framework. It is an efficient assignment management portal that allows instructor to create new assignments as well modify existing assignments which in turn have multiple topics for which students can sign up for. Students can form teams in Expertiza to work on the assignments and Expertiza also provides functionality to advertise for team members. Students can peer review other submissions and provide feedback about the same.

==Current Implementation==
In the current implementation only the students can sign up for topics. Because of this, no higher authority (e.g instructor) can control the signups in a straightforward manner. If the instructor wishes to assign a particular topic to a team or remove a team from a particular topic then the instructor has to impersonate that student and sign up for the topic. Due, to the current implementation, you can neither handle the mistakes in signups , nor make modifications to the existing signups without impersonation.

==New Implementation==
The new implementation allows an instructor to assign a particular topic to a team as well as remove a team from a topic.This functionality has been added in views/sign_up_sheet/_all_actions.html.erb which now has a '+' sign to assign a topic to a particular user. If the instructor clicks on this, then a view will appear which takes in the username of a student to be added. When the box is filled out and the “search” button clicked, then the indicated user’s team is signed up for the topic. If there are no slots available for that topic then the team will be put on the waiting list. There is also a 'X' sign that will help the instructor to remove a team from a topic.

Some of the scenarios where the instructor might wish to add a team would be if the sign up deadline has passed, or if the instructor has decided to update the maximum number of teams allowed to choose a particular topic. The instructor might want to drop a team from the topic if the team doesn't want to proceed with the same topic for the assignment. With the new implementation, Instructors/Teaching Assistants do not need to go through the trouble of impersonating a student in order to add or drop their team from topics.

Changes were made in the following files -
* controllers/sign_up_sheet_controller.rb
* views/sign_up_sheet/_all_actions.html.erb
* views/sign_up_sheet/assign_topic.html.erb
* views/sign_up_sheet/remove_topic.html.erb

Functions added to implement functionality :-
* update_team
* assign_topic
* remove_team
* remove_topic

In the sign_up_sheet controller, two major methods were added:

===update_team===
This method allows an admin user to add a team to a particular topic, based on the username of any member of said team. If the number of teams already assigned to the topic is greater than or equal to the maximum number of teams allowed to pick the topic, the new team is added to the waitlist.
If a team was previously assigned a topic, and are then added by an admin to a new topic, their association with the old topic is deleted, and the required changes to the waitlist of topics are made as well.
The system will throw an error if the username of an invalid user is used to search for teams associated with the user.
The system checks that the topic is not being assigned again to the same team that has the topic.

===remove_team===
This method allows the admin to remove teams from a given topic, based on the username of a team member. First, a check is done to ensure that the team is indeed associated with the given topic. If this is the case, the entry is deleted from the table sign_up_teams, and the corresponding changes are made to the waitlist as well.

==Functionality==

[[File:Previous_View.png]][[File:New_View.png]]

Two additional icons have been added in the Actions column. The ‘green plus’ icon allows you to add a team to the current topic.
Clicking on the icon redirects you to a form, where the admin is required to enter the username of the person whose team he wishes to add.
[[File:Add_Team.png|centre]]

Clicking submit then redirects back to the original page, with a flash message containing the status of the operation.
[[File:Team_Added.png|centre]]

In case the topic has already been assigned the maximum number of teams, the new team is added to the waitlist.
[[File:Waitlisting.png|centre]]

The 'red cross' icon is used to remove a team from the given topic. Clicking on it takes the admin to a form, where he is required to enter the username of one of the team members belonging to the team that is to be removed. Submitting the form redirects the user back to the original page, with a flash message indicating the status of the remove operation.

[[File:Remove_Team.png|centre]]

==Scope for Improvement==
The system can take in individual users who don't have a team or topic and can add him/her to the existing teams that are enrolled for the topic.

CSC/ECE 517 Fall 2016/oss E1649 KPS

2016-10-28T21:00:49Z

Ssdeshp5: Added About Expertiza

==Expertiza==
Expertiza is an open source project based on Ruby on Rails framework. It is an efficient assignment management portal that allows instructor to create new assignments as well modify existing assignments which in turn have multiple topics for which students can sign up for. Students can form teams in Expertiza to work on the assignments and Expertiza also provides functionality to advertise for team members. Students can peer review other submissions and provide feedback about the same.

==Current Implementation==
In the current implementation only the students can sign up for topics. Because of this, no higher authority (e.g instructor) can control the signups in a straightforward manner. If the instructor wishes to assign a particular topic to a team or remove a team from a particular topic then the instructor has to impersonate that student and sign up for the topic. Due, to the current implementation, you can neither handle the mistakes in signups , nor make modifications to the existing signups without impersonation.

==New Implementation==
The new implementation allows an instructor to assign a particular topic to a team as well as remove a team from a topic.This functionality has been added in views/sign_up_sheet/_all_actions.html.erb which now has a '+' sign to assign a topic to a particular user. If the instructor clicks on this, then a view will appear which takes in the username of a student to be added. When the box is filled out and the “search” button clicked, then the indicated user’s team is signed up for the topic. If there are no slots available for that topic then the team will be put on the waiting list. There is also a 'X' sign that will help the instructor to remove a team from a topic.

Some of the scenarios where the instructor might wish to add a team would be if the sign up deadline has passed, or if the instructor has decided to update the maximum number of teams allowed to choose a particular topic. The instructor might want to drop a team from the topic if the team doesn't want to proceed with the same topic for the assignment. With the new implementation, Instructors/Teaching Assistants do not need to go through the trouble of impersonating a student in order to add or drop their team from topics.

Changes were made in the following files -
* controllers/sign_up_sheet_controller.rb
* views/sign_up_sheet/_all_actions.html.erb
* views/sign_up_sheet/assign_topic.html.erb
* views/sign_up_sheet/remove_topic.html.erb

Functions added to implement functionality :-
* update_team
* assign_topic
* remove_team
* remove_topic

In the sign_up_sheet controller, two major methods were added:

===update_team===
This method allows an admin user to add a team to a particular topic, based on the username of any member of said team. If the number of teams already assigned to the topic is greater than or equal to the maximum number of teams allowed to pick the topic, the new team is added to the waitlist.
If a team was previously assigned a topic, and are then added by an admin to a new topic, their association with the old topic is deleted, and the required changes to the waitlist of topics are made as well.
The system will throw an error if the username of an invalid user is used to search for teams associated with the user.
The system checks that the topic is not being assigned again to the same team that has the topic.

===remove_team===
This method allows the admin to remove teams from a given topic, based on the username of a team member. First, a check is done to ensure that the team is indeed associated with the given topic. If this is the case, the entry is deleted from the table sign_up_teams, and the corresponding changes are made to the waitlist as well.

==Functionality==

[[File:Previous_View.png]][[File:New_View.png]]

[[File:Team_Added.png]] [[File:Waitlisting.png]]

[[File:Remove_Team.png]]

Two additional icons have been added in the something column. The ‘green plus’ icon allows you to add a team to the current topic.
Clicking on the icon redirects you to a form, where the admin is required to enter the username of the person whose team he wishes to add.

Clicking submit then redirects back to the original page, with a flash message containing the status of the operation, as well as the cause in case of a failure.
image_form_addteam, image_mainpage_success

The 'red cross' icon is used to remove a team from the given topic. Clicking on it takes the admin to a form, where he is required to enter the username of one of the team members belonging to the team that is to be removed. Submitting the form redirects the user back to the original page, with a flash message indicating the status of the remove operation.

image_form_removeteam, image_mainpage_success

CSC/ECE 517 Fall 2016/oss E1649 KPS

2016-10-28T20:50:31Z

Ssdeshp5: Modified new implementation

==Current Implementation==
In the current implementation only the students can sign up for topics. Because of this, no higher authority (e.g instructor) can control the signups in a straightforward manner. If the instructor wishes to assign a particular topic to a team or remove a team from a particular topic then the instructor has to impersonate that student and sign up for the topic. Due, to the current implementation, you can neither handle the mistakes in signups , nor make modifications to the existing signups without impersonation.

==New Implementation==
The new implementation allows an instructor to assign a particular topic to a team as well as remove a team from a topic.This functionality has been added in views/sign_up_sheet/_all_actions.html.erb which now has a '+' sign to assign a topic to a particular user. If the instructor clicks on this, then a view will appear which takes in the username of a student to be added. When the box is filled out and the “search” button clicked, then the indicated user’s team is signed up for the topic. If there are no slots available for that topic then the team will be put on the waiting list. There is also a 'X' sign that will help the instructor to remove a team from a topic.

Some of the scenarios where the instructor might wish to add a team would be if the sign up deadline has passed, or if the instructor has decided to update the maximum number of teams allowed to choose a particular topic. The instructor might want to drop a team from the topic if the team doesn't want to proceed with the same topic for the assignment. With the new implementation, Instructors/Teaching Assistants do not need to go through the trouble of impersonating a student in order to add or drop their team from topics.

Changes were made in the following files -
* controllers/sign_up_sheet_controller.rb
* views/sign_up_sheet/_all_actions.html.erb
* views/sign_up_sheet/assign_topic.html.erb
* views/sign_up_sheet/remove_topic.html.erb

Functions added to implement functionality :-
* update_team
* assign_topic
* remove_team
* remove_topic

In the sign_up_sheet controller, two major methods were added:

===update_team===
This method allows an admin user to add a team to a particular topic, based on the username of any member of said team. If the number of teams already assigned to the topic is greater than or equal to the maximum number of teams allowed to pick the topic, the new team is added to the waitlist.
If a team was previously assigned a topic, and are then added by an admin to a new topic, their association with the old topic is deleted, and the required changes to the waitlist of topics are made as well.
The system will throw an error if the username of an invalid user is used to search for teams associated with the user.
The system checks that the topic is not being assigned again to the same team that has the topic.

===remove_team===
This method allows the admin to remove teams from a given topic, based on the username of a team member. First, a check is done to ensure that the team is indeed associated with the given topic. If this is the case, the entry is deleted from the table sign_up_teams, and the corresponding changes are made to the waitlist as well.

==Functionality==

[[File:Previous_View.png]][[File:New_View.png]]

[[File:Team_Added.png]] [[File:Waitlisting.png]]

[[File:Remove_Team.png]]

Two additional icons have been added in the something column. The ‘green plus’ icon allows you to add a team to the current topic.
Clicking on the icon redirects you to a form, where the admin is required to enter the username of the person whose team he wishes to add.

Clicking submit then redirects back to the original page, with a flash message containing the status of the operation, as well as the cause in case of a failure.
image_form_addteam, image_mainpage_success

The 'red cross' icon is used to remove a team from the given topic. Clicking on it takes the admin to a form, where he is required to enter the username of one of the team members belonging to the team that is to be removed. Submitting the form redirects the user back to the original page, with a flash message indicating the status of the remove operation.

image_form_removeteam, image_mainpage_success

CSC/ECE 517 Fall 2016/oss E1649 KPS

2016-10-28T20:44:11Z

Ssdeshp5: Added current implementation

==Current Implementation==
In the current implementation only the students can sign up for topics. Because of this, no higher authority (e.g instructor) can control the signups. If the instructor wishes to assign a particular topic to a team or remove a team from a particular topic then the instructor has to impersonate that student and sign up for the topic.
Due, to the current implementation, you can neither handle the mistakes in signups , nor make modifications to the existing signups without impersonation.

==New Implementation==
The new implementation allows an instructor to assign a particular topic to a team as well as remove a team from a topic.This functionality has been added in views/sign_up_sheet/_all_actions.html.erb which now has a '+' sign to assign a topic to a particular user. If the instructor clicks on this, then a view will appear which takes in the username of a student to be added. When the box is filled out and the “search” button clicked, then the indicated user’s team is signed up for the topic. If there are no slots available for that topic then the team will be put on the waiting list. There is also a 'X' sign that will help the instructor to remove a team from a topic.

Some of the scenarios where the instructor might wish to add a team would be if the sign up deadline has passed, or if the instructor has decided to update the maximum number of teams allowed to choose a particular topic. The instructor might want to drop a team from the topic if the team doesn't want to proceed with the same topic for the assignment. With the new implementation, Instructors/Teaching Assistants do not need to go through the trouble of impersonating a student in order to add or drop their team from topics.

Changes were made in the following files -
* controllers/sign_up_sheet_controller.rb
* views/sign_up_sheet/_all_actions.html.erb
* views/sign_up_sheet/assign_topic.html.erb
* views/sign_up_sheet/remove_topic.html.erb

Functions added to implement functionality :-
* update_team
* assign_topic
* remove_team
* remove_topic

In the sign_up_sheet controller, two major methods were added:

===update_team===
This method allows an admin user to add a team to a particular topic, based on the username of any member of said team. If the number of teams already assigned to the topic is greater than or equal to the maximum number of teams allowed to pick the topic, the new team is added to the waitlist.
If a team was previously assigned a topic, and are then added by an admin to a new topic, their association with the old topic is deleted, and the required changes to the waitlist of topics are made as well.
The system will throw an error if the username of an invalid user is used to search for teams associated with the user.

===remove_team===
This method allows the admin to remove teams from a given topic, based on the username of a team member. First, a check is done to ensure that the team is indeed associated with the given topic. If this is the case, the entry is deleted from the table sign_up_teams, and the corresponding changes are made to the waitlist as well.

==Functionality==

[[File:Previous_View.png]][[File:New_View.png]]

Two additional icons have been added in the something column. The ‘green plus’ icon allows you to add a team to the current topic.
Clicking on the icon redirects you to a form, where the admin is required to enter the username of the person whose team he wishes to add.

Clicking submit then redirects back to the original page, with a flash message containing the status of the operation, as well as the cause in case of a failure.
image_form_addteam, image_mainpage_success

The 'red cross' icon is used to remove a team from the given topic. Clicking on it takes the admin to a form, where he is required to enter the username of one of the team members belonging to the team that is to be removed. Submitting the form redirects the user back to the original page, with a flash message indicating the status of the remove operation.

image_form_removeteam, image_mainpage_success

CSC/ECE 517 Fall 2016/oss E1649 KPS

2016-10-28T20:41:36Z

Ssdeshp5: Added information about new implementation

==New Implementation==
The new implementation allows an instructor to assign a particular topic to a team as well as remove a team from a topic.This functionality has been added in views/sign_up_sheet/_all_actions.html.erb which now has a '+' sign to assign a topic to a particular user. If the instructor clicks on this, then a view will appear which takes in the username of a student to be added. When the box is filled out and the “search” button clicked, then the indicated user’s team is signed up for the topic. If there are no slots available for that topic then the team will be put on the waiting list. There is also a 'X' sign that will help the instructor to remove a team from a topic.

Some of the scenarios where the instructor might wish to add a team would be if the sign up deadline has passed, or if the instructor has decided to update the maximum number of teams allowed to choose a particular topic. The instructor might want to drop a team from the topic if the team doesn't want to proceed with the same topic for the assignment. With the new implementation, Instructors/Teaching Assistants do not need to go through the trouble of impersonating a student in order to add or drop their team from topics.

Changes were made in the following files -
* controllers/sign_up_sheet_controller.rb
* views/sign_up_sheet/_all_actions.html.erb
* views/sign_up_sheet/assign_topic.html.erb
* views/sign_up_sheet/remove_topic.html.erb

Functions added to implement functionality :-
* update_team
* assign_topic
* remove_team
* remove_topic

In the sign_up_sheet controller, two major methods were added:

===update_team===
This method allows an admin user to add a team to a particular topic, based on the username of any member of said team. If the number of teams already assigned to the topic is greater than or equal to the maximum number of teams allowed to pick the topic, the new team is added to the waitlist.
If a team was previously assigned a topic, and are then added by an admin to a new topic, their association with the old topic is deleted, and the required changes to the waitlist of topics are made as well.
The system will throw an error if the username of an invalid user is used to search for teams associated with the user.

===remove_team===
This method allows the admin to remove teams from a given topic, based on the username of a team member. First, a check is done to ensure that the team is indeed associated with the given topic. If this is the case, the entry is deleted from the table sign_up_teams, and the corresponding changes are made to the waitlist as well.

==Functionality==

[[File:Previous_View.png]][[File:New_View.png]]

Two additional icons have been added in the something column. The ‘green plus’ icon allows you to add a team to the current topic.
Clicking on the icon redirects you to a form, where the admin is required to enter the username of the person whose team he wishes to add.

Clicking submit then redirects back to the original page, with a flash message containing the status of the operation, as well as the cause in case of a failure.
image_form_addteam, image_mainpage_success

The 'red cross' icon is used to remove a team from the given topic. Clicking on it takes the admin to a form, where he is required to enter the username of one of the team members belonging to the team that is to be removed. Submitting the form redirects the user back to the original page, with a flash message indicating the status of the remove operation.

image_form_removeteam, image_mainpage_success

CSC/ECE 517 Fall 2016/oss E1649 KPS

2016-10-28T20:19:02Z

Ssdeshp5: Edited New Implementation

==New Implementation==
The new implementation allows an instructor to assign a particular topic to a team as well as remove a team from a topic. Some of the scenarios where the instructor might wish to add a team would be if the sign up deadline has passed, or if the instructor has decided to update the maximum number of teams allowed to choose a particular topic.

With the new implementation, Instructors/Teaching Assistants do not need to go through the trouble of impersonating a student in order to add or drop their team from topics.

Changes were made in the following files -
* controllers/sign_up_sheet_controller.rb
* views/sign_up_sheet/_all_actions.html.erb
* views/sign_up_sheet/assign_topic.html.erb
* views/sign_up_sheet/remove_topic.html.erb

In the sign_up_sheet controller, two major methods were added:

===update_team===
This method allows an admin user to add a team to a particular topic, based on the username of any member of said team. If the number of teams already assigned to the topic is greater than or equal to the maximum number of teams allowed to pick the topic, the new team is added to the waitlist.
If a team was previously assigned a topic, and are then added by an admin to a new topic, their association with the old topic is deleted, and the required changes to the waitlist of topics are made as well.
The system will throw an error if the username of an invalid user is used to search for teams associated with the user.

===remove_team===
This method allows the admin to remove teams from a given topic, based on the username of a team member. First, a check is done to ensure that the team is indeed associated with the given topic. If this is the case, the entry is deleted from the table sign_up_teams, and the corresponding changes are made to the waitlist as well.

==Functionality==

[[File:New_View.png|centre]]

2 additional icons have been added in the something column. The ‘green plus’ icon allows you to add a team to the current topic.
Clicking on the icon redirects you to a form, where the admin is required to enter the username of the person whose team he wishes to add.

Clicking submit then redirects back to the original page, with a flash message containing the status of the operation, as well as the cause in case of a failure.
image_form_addteam, image_mainpage_success

The 'red cross' icon is used to remove a team from the given topic. Clicking on it takes the admin to a form, where he is required to enter the username of one of the team members belonging to the team that is to be removed. Submitting the form redirects the user back to the original page, with a flash message indicating the status of the remove operation.

image_form_removeteam, image_mainpage_success