Expertiza_Wiki - User contributions [en]

CSC/ECE 517 Fall 2016/E1688. Send feedback to support + tree display improvement

2016-12-13T22:42:16Z

Sndesai: Changing Contant to Expertiza

== '''Introduction to Expertiza''' ==

Expertiza is an open source software to create reusable learning objects through peer reviewing of team projects and submission of project design documents. In the final project, there are two major changes that will help in improving user experience.

=='''Purpose'''==

The purpose of this project is:
===Provide a new UI which allows users to send emails to expertiza support Background===
This feature will help expertiza users to achieve faster resolution to the problems they face. A new UI support needs to be given to enable them to directly send the issues they face to expertiza support through email.

===A single “actions” icon with a pop up panel in place of the currently existing “action” icons on tree display===
The purpose of this enhancement is to reduce the wastage of space on the Manage Assignments page.

=='''Background'''==
===Provide a new UI which allows users to send emails to expertiza support Background===
The current implementation of expertiza does not provide any feature for users to send feedback in case they face any problem. This new feature allows a user to send a complaint or feedback to expertiza support via email. Captcha needs to be implemented so as to prevent the abuse of the this feature.

===A single “actions” icon with a pop up panel in place of the currently existing “action” icons on tree display===
Currently the data to be displayed for each assignment takes 2 lines whereas the “actions” icons are taking up 3 or 4 lines for display. This is a wastage of space on the screen.

[[File:treeDisplay.jpg]]

=='''Product Requirements'''==

===Provide a new UI which allows users to send emails to expertiza support Background===
This design unit includes following tasks:

1. Provide ‘Expertiza Support’ button on top of website. 
2. Create a feedback support form page which should be available to all the users including unauthenticated users. 
3. The form page should have fields for email Id for fetching email id of the user facing issue, a description input box where user can describe the steps for reproducing the issue. 
4. This form should have field email auto filled with email on user profile if the user has logged in. 
5. This form should provide random captcha to prevent abuse of this feature. 
6. Submitting this feedback form page should trigger email to “[[expertiza-support@lists.ncsu.edu]]”. 
7. The project should provide User with an acknowledgment saying email has been seen and Expertiza Support will try to fix the issue as soon as possible. 

===A single “actions” icon with a pop up panel in place of the currently existing “action” icons on tree display===
To eliminate the extra space on Manage Assignments page because of less data and more “actions” icons, we will replace all the “actions” icons with a single “actions” icon embedded with a pop up panel. So when a user clicks on this new “actions” icon, it will throw a pop up containing all these previous “actions” icons and the user can select one of them to invoke one of these actions (edit, delete, add participant, create teams, etc...).

===Mouse hover on ''Help'' should not make it invisible===
We changed the css to black so on mouse hover ''Help'' doesn't become invisible.
 
[[File:Help.png]]

=='''Use Cases'''==
==='''Provide a new UI which allows users to send emails to expertiza support Background'''===
*'''Input:''' User clicks on Expertiza Support and issue description and captcha as input. The email id is auto-filled from the user profile.
*'''Type of Input:''' Feedback Form
*'''Source of Input:''' User interface
*'''Processing:''' Validate input fields and form submit
*'''Outputs:''' Email sent to Expertiza support and acknowledgement displayed to user.

[[File:UseCaseDiagram.jpg]]

==='''A single “actions” icon with a pop up panel in place of the currently existing “action” icons on tree display'''===
Provide a new icon in “actions” on tree display, then when you click on this new icon a new popup appears. This popup has all the previous “actions”
*'''Input:''' User clicks on new icon
*'''Description:''' new popup appears with all actions in it
*'''Type of Input:''' Click on the new icon
*'''Source of Input:''' User interface
*'''Processing:''' Create popup
*'''Outputs:''' Pop up Panel displaying all the previous “actions” icons for the user to choose from.

=='''Design Pattern'''==
===Provide a new UI which allows users to send emails to expertiza support Background===
'''Model''': send_sync_message method with expertiza_support_helper(new helper class defining the body of email) will be responsible for sending email to expertiza support. 
'''Controller''': Feedback form submission should call MailerHelper’s send_sync_message method with the appropriate parameters specifying that an expertiza user is facing some issue. 
'''View''': A new expertiza contact support form to be created with fields email id, description of issue, captcha and submit button.

 
 
[[File:Feedback.png]]

 

===A single “actions” icon with a pop up panel in place of the currently existing “action” icons on tree display===
A UI change replacing displaying tree with an icon. On click event will create a pop up panel. User selection will trigger the appropriate action(this functionality will not be changed).
 
'''View''': Instead of displaying all the "actions" icons, we will replace this code to display a single "actions" icon with an embedded pop up panel.
 
 
[[File:Actiona1.png]]
 
 
[[File:Actions2.png]]

=='''Testing Plan'''==

==='''Provide a new UI which allows users to send emails to expertiza support Background'''===
*'''T.1: ''' Contact Support’ button should be seen to all the users (even unauthenticated).
*'''T.2: ''' For unauthenticated users, clicking on ‘Contact Support’ should redirect to feedback support form page with blank email id field, description and captcha
*'''T.3: ''' For authenticated users, clicking on ‘Contact Support’ should redirect to feedback support form page with email id auto-filled with email on their profile, description and captcha.
*'''T.4: ''' Before form submission, none of the fields should be blank. Appropriate blank error message should be shown otherwise.
*'''T.5: ''' Captcha should be random on every page load. Error message saying ‘incorrect captcha’ should be shown in case user fails to provide the same text of captcha.
*'''T.6: ''' Email should be received to Expertiza support “expertiza-support@lists.ncsu.edu” on the form submission and the user should get an acknowledgement of email received.

==='''A single “actions” icon with a pop up panel in place of the currently existing “action” icons on tree display'''===
*'''T.1: ''' Ensure that when a user click on the new “actions” icon, it throws a pop up panel with all the old “actions” icons.
*'''T.2: ''' Ensure that Edit icon redirects the user to edit assignment view.
*'''T.3: ''' Ensure that Delete icon deletes the assignment.
*'''T.4: ''' Ensure that Add TA icon redirects the user to Add TA view.
*'''T.5: ''' Ensure that Add Participant icon redirects the user to Add Participant view.
*'''T.6: ''' Ensure that Create Teams icon redirects the user to Create Teams view.
*'''T.7: ''' Ensure that Create Assignment icon redirects the user to Create Assignment view.
*'''T.8: ''' Ensure that 360 assessment dashboard icon redirect user to One_course_all_assignments page of assessment360 view.
*'''T.9: ''' Ensure that Copy icon redirects user to Edit course page.
*'''T.10: ''' Ensure that Make public icon redirects user to the tree display page.

CSC/ECE 517 Fall 2016/E1688. Send feedback to support + tree display improvement

2016-12-13T21:50:43Z

Sndesai: Adding css changes

== '''Introduction to Expertiza''' ==

Expertiza is an open source software to create reusable learning objects through peer reviewing of team projects and submission of project design documents. In the final project, there are two major changes that will help in improving user experience.

=='''Purpose'''==

The purpose of this project is:
===Provide a new UI which allows users to send emails to expertiza support Background===
This feature will help expertiza users to achieve faster resolution to the problems they face. A new UI support needs to be given to enable them to directly send the issues they face to expertiza support through email.

===A single “actions” icon with a pop up panel in place of the currently existing “action” icons on tree display===
The purpose of this enhancement is to reduce the wastage of space on the Manage Assignments page.

=='''Background'''==
===Provide a new UI which allows users to send emails to expertiza support Background===
The current implementation of expertiza does not provide any feature for users to send feedback in case they face any problem. This new feature allows a user to send a complaint or feedback to expertiza support via email. Captcha needs to be implemented so as to prevent the abuse of the this feature.

===A single “actions” icon with a pop up panel in place of the currently existing “action” icons on tree display===
Currently the data to be displayed for each assignment takes 2 lines whereas the “actions” icons are taking up 3 or 4 lines for display. This is a wastage of space on the screen.

[[File:treeDisplay.jpg]]

=='''Product Requirements'''==

===Provide a new UI which allows users to send emails to expertiza support Background===
This design unit includes following tasks:

1. Provide ‘Contact Support’ button on top of website. 
2. Create a feedback support form page which should be available to all the users including unauthenticated users. 
3. The form page should have fields for email Id for fetching email id of the user facing issue, a description input box where user can describe the steps for reproducing the issue. 
4. This form should have field email auto filled with email on user profile if the user has logged in. 
5. This form should provide random captcha to prevent abuse of this feature. 
6. Submitting this feedback form page should trigger email to “[[expertiza-support@lists.ncsu.edu]]”. 
7. The project should provide User with an acknowledgment saying email has been seen and Expertiza Support will try to fix the issue as soon as possible. 

===A single “actions” icon with a pop up panel in place of the currently existing “action” icons on tree display===
To eliminate the extra space on Manage Assignments page because of less data and more “actions” icons, we will replace all the “actions” icons with a single “actions” icon embedded with a pop up panel. So when a user clicks on this new “actions” icon, it will throw a pop up containing all these previous “actions” icons and the user can select one of them to invoke one of these actions (edit, delete, add participant, create teams, etc...).

===Mouse hover on ''Help'' should not make it invisible===
We changed the css to black so on mouse hover ''Help'' doesn't become invisible.
 
[[File:Help.png]]

=='''Use Cases'''==
==='''Provide a new UI which allows users to send emails to expertiza support Background'''===
*'''Input:''' User clicks on Expertiza Support and issue description and captcha as input. The email id is auto-filled from the user profile.
*'''Type of Input:''' Feedback Form
*'''Source of Input:''' User interface
*'''Processing:''' Validate input fields and form submit
*'''Outputs:''' Email sent to Expertiza support and acknowledgement displayed to user.

[[File:UseCaseDiagram.jpg]]

==='''A single “actions” icon with a pop up panel in place of the currently existing “action” icons on tree display'''===
Provide a new icon in “actions” on tree display, then when you click on this new icon a new popup appears. This popup has all the previous “actions”
*'''Input:''' User clicks on new icon
*'''Description:''' new popup appears with all actions in it
*'''Type of Input:''' Click on the new icon
*'''Source of Input:''' User interface
*'''Processing:''' Create popup
*'''Outputs:''' Pop up Panel displaying all the previous “actions” icons for the user to choose from.

=='''Design Pattern'''==
===Provide a new UI which allows users to send emails to expertiza support Background===
'''Model''': send_sync_message method with expertiza_support_helper(new helper class defining the body of email) will be responsible for sending email to expertiza support. 
'''Controller''': Feedback form submission should call MailerHelper’s send_sync_message method with the appropriate parameters specifying that an expertiza user is facing some issue. 
'''View''': A new expertiza contact support form to be created with fields email id, description of issue, captcha and submit button.

 
 
[[File:Feedback.png]]

 

===A single “actions” icon with a pop up panel in place of the currently existing “action” icons on tree display===
A UI change replacing displaying tree with an icon. On click event will create a pop up panel. User selection will trigger the appropriate action(this functionality will not be changed).
 
'''View''': Instead of displaying all the "actions" icons, we will replace this code to display a single "actions" icon with an embedded pop up panel.
 
 
[[File:Actiona1.png]]
 
 
[[File:Actions2.png]]

=='''Testing Plan'''==

==='''Provide a new UI which allows users to send emails to expertiza support Background'''===
*'''T.1: ''' Contact Support’ button should be seen to all the users (even unauthenticated).
*'''T.2: ''' For unauthenticated users, clicking on ‘Contact Support’ should redirect to feedback support form page with blank email id field, description and captcha
*'''T.3: ''' For authenticated users, clicking on ‘Contact Support’ should redirect to feedback support form page with email id auto-filled with email on their profile, description and captcha.
*'''T.4: ''' Before form submission, none of the fields should be blank. Appropriate blank error message should be shown otherwise.
*'''T.5: ''' Captcha should be random on every page load. Error message saying ‘incorrect captcha’ should be shown in case user fails to provide the same text of captcha.
*'''T.6: ''' Email should be received to Expertiza support “expertiza-support@lists.ncsu.edu” on the form submission and the user should get an acknowledgement of email received.

==='''A single “actions” icon with a pop up panel in place of the currently existing “action” icons on tree display'''===
*'''T.1: ''' Ensure that when a user click on the new “actions” icon, it throws a pop up panel with all the old “actions” icons.
*'''T.2: ''' Ensure that Edit icon redirects the user to edit assignment view.
*'''T.3: ''' Ensure that Delete icon deletes the assignment.
*'''T.4: ''' Ensure that Add TA icon redirects the user to Add TA view.
*'''T.5: ''' Ensure that Add Participant icon redirects the user to Add Participant view.
*'''T.6: ''' Ensure that Create Teams icon redirects the user to Create Teams view.
*'''T.7: ''' Ensure that Create Assignment icon redirects the user to Create Assignment view.
*'''T.8: ''' Ensure that 360 assessment dashboard icon redirect user to One_course_all_assignments page of assessment360 view.
*'''T.9: ''' Ensure that Copy icon redirects user to Edit course page.
*'''T.10: ''' Ensure that Make public icon redirects user to the tree display page.

File:Help.png

2016-12-13T21:50:10Z

Sndesai:

CSC/ECE 517 Fall 2016/E1688. Send feedback to support + tree display improvement

2016-12-13T21:44:02Z

Sndesai: Formatting

== '''Introduction to Expertiza''' ==

Expertiza is an open source software to create reusable learning objects through peer reviewing of team projects and submission of project design documents. In the final project, there are two major changes that will help in improving user experience.

=='''Purpose'''==

The purpose of this project is:
===Provide a new UI which allows users to send emails to expertiza support Background===
This feature will help expertiza users to achieve faster resolution to the problems they face. A new UI support needs to be given to enable them to directly send the issues they face to expertiza support through email.

===A single “actions” icon with a pop up panel in place of the currently existing “action” icons on tree display===
The purpose of this enhancement is to reduce the wastage of space on the Manage Assignments page.

=='''Background'''==
===Provide a new UI which allows users to send emails to expertiza support Background===
The current implementation of expertiza does not provide any feature for users to send feedback in case they face any problem. This new feature allows a user to send a complaint or feedback to expertiza support via email. Captcha needs to be implemented so as to prevent the abuse of the this feature.

===A single “actions” icon with a pop up panel in place of the currently existing “action” icons on tree display===
Currently the data to be displayed for each assignment takes 2 lines whereas the “actions” icons are taking up 3 or 4 lines for display. This is a wastage of space on the screen.

[[File:treeDisplay.jpg]]

=='''Product Requirements'''==

===Provide a new UI which allows users to send emails to expertiza support Background===
This design unit includes following tasks:

1. Provide ‘Contact Support’ button on top of website. 
2. Create a feedback support form page which should be available to all the users including unauthenticated users. 
3. The form page should have fields for email Id for fetching email id of the user facing issue, a description input box where user can describe the steps for reproducing the issue. 
4. This form should have field email auto filled with email on user profile if the user has logged in. 
5. This form should provide random captcha to prevent abuse of this feature. 
6. Submitting this feedback form page should trigger email to “[[expertiza-support@lists.ncsu.edu]]”. 
7. The project should provide User with an acknowledgment saying email has been seen and Expertiza Support will try to fix the issue as soon as possible. 

===A single “actions” icon with a pop up panel in place of the currently existing “action” icons on tree display===
To eliminate the extra space on Manage Assignments page because of less data and more “actions” icons, we will replace all the “actions” icons with a single “actions” icon embedded with a pop up panel. So when a user clicks on this new “actions” icon, it will throw a pop up containing all these previous “actions” icons and the user can select one of them to invoke one of these actions (edit, delete, add participant, create teams, etc...).

=='''Use Cases'''==
==='''Provide a new UI which allows users to send emails to expertiza support Background'''===
*'''Input:''' User clicks on Expertiza Support and issue description and captcha as input. The email id is auto-filled from the user profile.
*'''Type of Input:''' Feedback Form
*'''Source of Input:''' User interface
*'''Processing:''' Validate input fields and form submit
*'''Outputs:''' Email sent to Expertiza support and acknowledgement displayed to user.

[[File:UseCaseDiagram.jpg]]

==='''A single “actions” icon with a pop up panel in place of the currently existing “action” icons on tree display'''===
Provide a new icon in “actions” on tree display, then when you click on this new icon a new popup appears. This popup has all the previous “actions”
*'''Input:''' User clicks on new icon
*'''Description:''' new popup appears with all actions in it
*'''Type of Input:''' Click on the new icon
*'''Source of Input:''' User interface
*'''Processing:''' Create popup
*'''Outputs:''' Pop up Panel displaying all the previous “actions” icons for the user to choose from.

=='''Design Pattern'''==
===Provide a new UI which allows users to send emails to expertiza support Background===
'''Model''': send_sync_message method with expertiza_support_helper(new helper class defining the body of email) will be responsible for sending email to expertiza support. 
'''Controller''': Feedback form submission should call MailerHelper’s send_sync_message method with the appropriate parameters specifying that an expertiza user is facing some issue. 
'''View''': A new expertiza contact support form to be created with fields email id, description of issue, captcha and submit button.

 
 
[[File:Feedback.png]]

 

===A single “actions” icon with a pop up panel in place of the currently existing “action” icons on tree display===
A UI change replacing displaying tree with an icon. On click event will create a pop up panel. User selection will trigger the appropriate action(this functionality will not be changed).
 
'''View''': Instead of displaying all the "actions" icons, we will replace this code to display a single "actions" icon with an embedded pop up panel.
 
 
[[File:Actiona1.png]]
 
 
[[File:Actions2.png]]

=='''Testing Plan'''==

==='''Provide a new UI which allows users to send emails to expertiza support Background'''===
*'''T.1: ''' Contact Support’ button should be seen to all the users (even unauthenticated).
*'''T.2: ''' For unauthenticated users, clicking on ‘Contact Support’ should redirect to feedback support form page with blank email id field, description and captcha
*'''T.3: ''' For authenticated users, clicking on ‘Contact Support’ should redirect to feedback support form page with email id auto-filled with email on their profile, description and captcha.
*'''T.4: ''' Before form submission, none of the fields should be blank. Appropriate blank error message should be shown otherwise.
*'''T.5: ''' Captcha should be random on every page load. Error message saying ‘incorrect captcha’ should be shown in case user fails to provide the same text of captcha.
*'''T.6: ''' Email should be received to Expertiza support “expertiza-support@lists.ncsu.edu” on the form submission and the user should get an acknowledgement of email received.

==='''A single “actions” icon with a pop up panel in place of the currently existing “action” icons on tree display'''===
*'''T.1: ''' Ensure that when a user click on the new “actions” icon, it throws a pop up panel with all the old “actions” icons.
*'''T.2: ''' Ensure that Edit icon redirects the user to edit assignment view.
*'''T.3: ''' Ensure that Delete icon deletes the assignment.
*'''T.4: ''' Ensure that Add TA icon redirects the user to Add TA view.
*'''T.5: ''' Ensure that Add Participant icon redirects the user to Add Participant view.
*'''T.6: ''' Ensure that Create Teams icon redirects the user to Create Teams view.
*'''T.7: ''' Ensure that Create Assignment icon redirects the user to Create Assignment view.
*'''T.8: ''' Ensure that 360 assessment dashboard icon redirect user to One_course_all_assignments page of assessment360 view.
*'''T.9: ''' Ensure that Copy icon redirects user to Edit course page.
*'''T.10: ''' Ensure that Make public icon redirects user to the tree display page.

CSC/ECE 517 Fall 2016/E1688. Send feedback to support + tree display improvement

2016-12-13T21:43:29Z

Sndesai: Adding screenshot for Feedback

== '''Introduction to Expertiza''' ==

Expertiza is an open source software to create reusable learning objects through peer reviewing of team projects and submission of project design documents. In the final project, there are two major changes that will help in improving user experience.

=='''Purpose'''==

The purpose of this project is:
===Provide a new UI which allows users to send emails to expertiza support Background===
This feature will help expertiza users to achieve faster resolution to the problems they face. A new UI support needs to be given to enable them to directly send the issues they face to expertiza support through email.

===A single “actions” icon with a pop up panel in place of the currently existing “action” icons on tree display===
The purpose of this enhancement is to reduce the wastage of space on the Manage Assignments page.

=='''Background'''==
===Provide a new UI which allows users to send emails to expertiza support Background===
The current implementation of expertiza does not provide any feature for users to send feedback in case they face any problem. This new feature allows a user to send a complaint or feedback to expertiza support via email. Captcha needs to be implemented so as to prevent the abuse of the this feature.

===A single “actions” icon with a pop up panel in place of the currently existing “action” icons on tree display===
Currently the data to be displayed for each assignment takes 2 lines whereas the “actions” icons are taking up 3 or 4 lines for display. This is a wastage of space on the screen.

[[File:treeDisplay.jpg]]

=='''Product Requirements'''==

===Provide a new UI which allows users to send emails to expertiza support Background===
This design unit includes following tasks:

1. Provide ‘Contact Support’ button on top of website. 
2. Create a feedback support form page which should be available to all the users including unauthenticated users. 
3. The form page should have fields for email Id for fetching email id of the user facing issue, a description input box where user can describe the steps for reproducing the issue. 
4. This form should have field email auto filled with email on user profile if the user has logged in. 
5. This form should provide random captcha to prevent abuse of this feature. 
6. Submitting this feedback form page should trigger email to “[[expertiza-support@lists.ncsu.edu]]”. 
7. The project should provide User with an acknowledgment saying email has been seen and Expertiza Support will try to fix the issue as soon as possible. 

===A single “actions” icon with a pop up panel in place of the currently existing “action” icons on tree display===
To eliminate the extra space on Manage Assignments page because of less data and more “actions” icons, we will replace all the “actions” icons with a single “actions” icon embedded with a pop up panel. So when a user clicks on this new “actions” icon, it will throw a pop up containing all these previous “actions” icons and the user can select one of them to invoke one of these actions (edit, delete, add participant, create teams, etc...).

=='''Use Cases'''==
==='''Provide a new UI which allows users to send emails to expertiza support Background'''===
*'''Input:''' User clicks on Expertiza Support and issue description and captcha as input. The email id is auto-filled from the user profile.
*'''Type of Input:''' Feedback Form
*'''Source of Input:''' User interface
*'''Processing:''' Validate input fields and form submit
*'''Outputs:''' Email sent to Expertiza support and acknowledgement displayed to user.

[[File:UseCaseDiagram.jpg]]

==='''A single “actions” icon with a pop up panel in place of the currently existing “action” icons on tree display'''===
Provide a new icon in “actions” on tree display, then when you click on this new icon a new popup appears. This popup has all the previous “actions”
*'''Input:''' User clicks on new icon
*'''Description:''' new popup appears with all actions in it
*'''Type of Input:''' Click on the new icon
*'''Source of Input:''' User interface
*'''Processing:''' Create popup
*'''Outputs:''' Pop up Panel displaying all the previous “actions” icons for the user to choose from.

=='''Design Pattern'''==
===Provide a new UI which allows users to send emails to expertiza support Background===
'''Model''': send_sync_message method with expertiza_support_helper(new helper class defining the body of email) will be responsible for sending email to expertiza support. 
'''Controller''': Feedback form submission should call MailerHelper’s send_sync_message method with the appropriate parameters specifying that an expertiza user is facing some issue. 
'''View''': A new expertiza contact support form to be created with fields email id, description of issue, captcha and submit button.

 
 
[[File:Feedback.png]]

===A single “actions” icon with a pop up panel in place of the currently existing “action” icons on tree display===
A UI change replacing displaying tree with an icon. On click event will create a pop up panel. User selection will trigger the appropriate action(this functionality will not be changed).
 
'''View''': Instead of displaying all the "actions" icons, we will replace this code to display a single "actions" icon with an embedded pop up panel.
 
 
[[File:Actiona1.png]]
 
 
[[File:Actions2.png]]

=='''Testing Plan'''==

==='''Provide a new UI which allows users to send emails to expertiza support Background'''===
*'''T.1: ''' Contact Support’ button should be seen to all the users (even unauthenticated).
*'''T.2: ''' For unauthenticated users, clicking on ‘Contact Support’ should redirect to feedback support form page with blank email id field, description and captcha
*'''T.3: ''' For authenticated users, clicking on ‘Contact Support’ should redirect to feedback support form page with email id auto-filled with email on their profile, description and captcha.
*'''T.4: ''' Before form submission, none of the fields should be blank. Appropriate blank error message should be shown otherwise.
*'''T.5: ''' Captcha should be random on every page load. Error message saying ‘incorrect captcha’ should be shown in case user fails to provide the same text of captcha.
*'''T.6: ''' Email should be received to Expertiza support “expertiza-support@lists.ncsu.edu” on the form submission and the user should get an acknowledgement of email received.

==='''A single “actions” icon with a pop up panel in place of the currently existing “action” icons on tree display'''===
*'''T.1: ''' Ensure that when a user click on the new “actions” icon, it throws a pop up panel with all the old “actions” icons.
*'''T.2: ''' Ensure that Edit icon redirects the user to edit assignment view.
*'''T.3: ''' Ensure that Delete icon deletes the assignment.
*'''T.4: ''' Ensure that Add TA icon redirects the user to Add TA view.
*'''T.5: ''' Ensure that Add Participant icon redirects the user to Add Participant view.
*'''T.6: ''' Ensure that Create Teams icon redirects the user to Create Teams view.
*'''T.7: ''' Ensure that Create Assignment icon redirects the user to Create Assignment view.
*'''T.8: ''' Ensure that 360 assessment dashboard icon redirect user to One_course_all_assignments page of assessment360 view.
*'''T.9: ''' Ensure that Copy icon redirects user to Edit course page.
*'''T.10: ''' Ensure that Make public icon redirects user to the tree display page.

File:Feedback.png

2016-12-13T21:43:04Z

Sndesai:

CSC/ECE 517 Fall 2016/E1688. Send feedback to support + tree display improvement

2016-12-13T21:40:20Z

Sndesai: /* A single “actions” icon with a pop up panel in place of the currently existing “action” icons on tree display */

== '''Introduction to Expertiza''' ==

Expertiza is an open source software to create reusable learning objects through peer reviewing of team projects and submission of project design documents. In the final project, there are two major changes that will help in improving user experience.

=='''Purpose'''==

The purpose of this project is:
===Provide a new UI which allows users to send emails to expertiza support Background===
This feature will help expertiza users to achieve faster resolution to the problems they face. A new UI support needs to be given to enable them to directly send the issues they face to expertiza support through email.

===A single “actions” icon with a pop up panel in place of the currently existing “action” icons on tree display===
The purpose of this enhancement is to reduce the wastage of space on the Manage Assignments page.

=='''Background'''==
===Provide a new UI which allows users to send emails to expertiza support Background===
The current implementation of expertiza does not provide any feature for users to send feedback in case they face any problem. This new feature allows a user to send a complaint or feedback to expertiza support via email. Captcha needs to be implemented so as to prevent the abuse of the this feature.

===A single “actions” icon with a pop up panel in place of the currently existing “action” icons on tree display===
Currently the data to be displayed for each assignment takes 2 lines whereas the “actions” icons are taking up 3 or 4 lines for display. This is a wastage of space on the screen.

[[File:treeDisplay.jpg]]

=='''Product Requirements'''==

===Provide a new UI which allows users to send emails to expertiza support Background===
This design unit includes following tasks:

1. Provide ‘Contact Support’ button on top of website. 
2. Create a feedback support form page which should be available to all the users including unauthenticated users. 
3. The form page should have fields for email Id for fetching email id of the user facing issue, a description input box where user can describe the steps for reproducing the issue. 
4. This form should have field email auto filled with email on user profile if the user has logged in. 
5. This form should provide random captcha to prevent abuse of this feature. 
6. Submitting this feedback form page should trigger email to “[[expertiza-support@lists.ncsu.edu]]”. 
7. The project should provide User with an acknowledgment saying email has been seen and Expertiza Support will try to fix the issue as soon as possible. 

===A single “actions” icon with a pop up panel in place of the currently existing “action” icons on tree display===
To eliminate the extra space on Manage Assignments page because of less data and more “actions” icons, we will replace all the “actions” icons with a single “actions” icon embedded with a pop up panel. So when a user clicks on this new “actions” icon, it will throw a pop up containing all these previous “actions” icons and the user can select one of them to invoke one of these actions (edit, delete, add participant, create teams, etc...).

=='''Use Cases'''==
==='''Provide a new UI which allows users to send emails to expertiza support Background'''===
*'''Input:''' User clicks on Expertiza Support and issue description and captcha as input. The email id is auto-filled from the user profile.
*'''Type of Input:''' Feedback Form
*'''Source of Input:''' User interface
*'''Processing:''' Validate input fields and form submit
*'''Outputs:''' Email sent to Expertiza support and acknowledgement displayed to user.

[[File:UseCaseDiagram.jpg]]

==='''A single “actions” icon with a pop up panel in place of the currently existing “action” icons on tree display'''===
Provide a new icon in “actions” on tree display, then when you click on this new icon a new popup appears. This popup has all the previous “actions”
*'''Input:''' User clicks on new icon
*'''Description:''' new popup appears with all actions in it
*'''Type of Input:''' Click on the new icon
*'''Source of Input:''' User interface
*'''Processing:''' Create popup
*'''Outputs:''' Pop up Panel displaying all the previous “actions” icons for the user to choose from.

=='''Design Pattern'''==
===Provide a new UI which allows users to send emails to expertiza support Background===
'''Model''': send_sync_message method with expertiza_support_helper(new helper class defining the body of email) will be responsible for sending email to expertiza support. 
'''Controller''': Feedback form submission should call MailerHelper’s send_sync_message method with the appropriate parameters specifying that an expertiza user is facing some issue. 
'''View''': A new expertiza contact support form to be created with fields email id, description of issue, captcha and submit button.

===A single “actions” icon with a pop up panel in place of the currently existing “action” icons on tree display===
A UI change replacing displaying tree with an icon. On click event will create a pop up panel. User selection will trigger the appropriate action(this functionality will not be changed).
 
'''View''': Instead of displaying all the "actions" icons, we will replace this code to display a single "actions" icon with an embedded pop up panel.
 
 
[[File:Actiona1.png]]
 
 
[[File:Actions2.png]]

=='''Testing Plan'''==

==='''Provide a new UI which allows users to send emails to expertiza support Background'''===
*'''T.1: ''' Contact Support’ button should be seen to all the users (even unauthenticated).
*'''T.2: ''' For unauthenticated users, clicking on ‘Contact Support’ should redirect to feedback support form page with blank email id field, description and captcha
*'''T.3: ''' For authenticated users, clicking on ‘Contact Support’ should redirect to feedback support form page with email id auto-filled with email on their profile, description and captcha.
*'''T.4: ''' Before form submission, none of the fields should be blank. Appropriate blank error message should be shown otherwise.
*'''T.5: ''' Captcha should be random on every page load. Error message saying ‘incorrect captcha’ should be shown in case user fails to provide the same text of captcha.
*'''T.6: ''' Email should be received to Expertiza support “expertiza-support@lists.ncsu.edu” on the form submission and the user should get an acknowledgement of email received.

==='''A single “actions” icon with a pop up panel in place of the currently existing “action” icons on tree display'''===
*'''T.1: ''' Ensure that when a user click on the new “actions” icon, it throws a pop up panel with all the old “actions” icons.
*'''T.2: ''' Ensure that Edit icon redirects the user to edit assignment view.
*'''T.3: ''' Ensure that Delete icon deletes the assignment.
*'''T.4: ''' Ensure that Add TA icon redirects the user to Add TA view.
*'''T.5: ''' Ensure that Add Participant icon redirects the user to Add Participant view.
*'''T.6: ''' Ensure that Create Teams icon redirects the user to Create Teams view.
*'''T.7: ''' Ensure that Create Assignment icon redirects the user to Create Assignment view.
*'''T.8: ''' Ensure that 360 assessment dashboard icon redirect user to One_course_all_assignments page of assessment360 view.
*'''T.9: ''' Ensure that Copy icon redirects user to Edit course page.
*'''T.10: ''' Ensure that Make public icon redirects user to the tree display page.

File:Actions2.png

2016-12-13T21:39:35Z

Sndesai:

File:Actiona1.png

2016-12-13T21:38:36Z

Sndesai:

CSC/ECE 517 Fall 2016/E1688. Send feedback to support + tree display improvement

2016-12-13T16:58:00Z

Sndesai: Removing Hide assignments as it has not been implemented.

== '''Introduction to Expertiza''' ==

Expertiza is an open source software to create reusable learning objects through peer reviewing of team projects and submission of project design documents. In the final project, there are two major changes that will help in improving user experience.

=='''Purpose'''==

The purpose of this project is:
===Provide a new UI which allows users to send emails to expertiza support Background===
This feature will help expertiza users to achieve faster resolution to the problems they face. A new UI support needs to be given to enable them to directly send the issues they face to expertiza support through email.

===A single “actions” icon with a pop up panel in place of the currently existing “action” icons on tree display===
The purpose of this enhancement is to reduce the wastage of space on the Manage Assignments page.

=='''Background'''==
===Provide a new UI which allows users to send emails to expertiza support Background===
The current implementation of expertiza does not provide any feature for users to send feedback in case they face any problem. This new feature allows a user to send a complaint or feedback to expertiza support via email. Captcha needs to be implemented so as to prevent the abuse of the this feature.

===A single “actions” icon with a pop up panel in place of the currently existing “action” icons on tree display===
Currently the data to be displayed for each assignment takes 2 lines whereas the “actions” icons are taking up 3 or 4 lines for display. This is a wastage of space on the screen.

[[File:treeDisplay.jpg]]

=='''Product Requirements'''==

===Provide a new UI which allows users to send emails to expertiza support Background===
This design unit includes following tasks:

1. Provide ‘Contact Support’ button on top of website. 
2. Create a feedback support form page which should be available to all the users including unauthenticated users. 
3. The form page should have fields for email Id for fetching email id of the user facing issue, a description input box where user can describe the steps for reproducing the issue. 
4. This form should have field email auto filled with email on user profile if the user has logged in. 
5. This form should provide random captcha to prevent abuse of this feature. 
6. Submitting this feedback form page should trigger email to “[[expertiza-support@lists.ncsu.edu]]”. 
7. The project should provide User with an acknowledgment saying email has been seen and Expertiza Support will try to fix the issue as soon as possible. 

===A single “actions” icon with a pop up panel in place of the currently existing “action” icons on tree display===
To eliminate the extra space on Manage Assignments page because of less data and more “actions” icons, we will replace all the “actions” icons with a single “actions” icon embedded with a pop up panel. So when a user clicks on this new “actions” icon, it will throw a pop up containing all these previous “actions” icons and the user can select one of them to invoke one of these actions (edit, delete, add participant, create teams, etc...).

=='''Use Cases'''==
==='''Provide a new UI which allows users to send emails to expertiza support Background'''===
*'''Input:''' User clicks on Expertiza Support and issue description and captcha as input. The email id is auto-filled from the user profile.
*'''Type of Input:''' Feedback Form
*'''Source of Input:''' User interface
*'''Processing:''' Validate input fields and form submit
*'''Outputs:''' Email sent to Expertiza support and acknowledgement displayed to user.

[[File:UseCaseDiagram.jpg]]

==='''A single “actions” icon with a pop up panel in place of the currently existing “action” icons on tree display'''===
Provide a new icon in “actions” on tree display, then when you click on this new icon a new popup appears. This popup has all the previous “actions”
*'''Input:''' User clicks on new icon
*'''Description:''' new popup appears with all actions in it
*'''Type of Input:''' Click on the new icon
*'''Source of Input:''' User interface
*'''Processing:''' Create popup
*'''Outputs:''' Pop up Panel displaying all the previous “actions” icons for the user to choose from.

=='''Design Pattern'''==
===Provide a new UI which allows users to send emails to expertiza support Background===
'''Model''': send_sync_message method with expertiza_support_helper(new helper class defining the body of email) will be responsible for sending email to expertiza support. 
'''Controller''': Feedback form submission should call MailerHelper’s send_sync_message method with the appropriate parameters specifying that an expertiza user is facing some issue. 
'''View''': A new expertiza contact support form to be created with fields email id, description of issue, captcha and submit button.

===A single “actions” icon with a pop up panel in place of the currently existing “action” icons on tree display===
A UI change replacing displaying tree with an icon. On click event will create a pop up panel. User selection will trigger the appropriate action(this functionality will not be changed).
 
'''View''': Instead of displaying all the "actions" icons, we will replace this code to display a single "actions" icon with an embedded pop up panel.

=='''Testing Plan'''==

==='''Provide a new UI which allows users to send emails to expertiza support Background'''===
*'''T.1: ''' Contact Support’ button should be seen to all the users (even unauthenticated).
*'''T.2: ''' For unauthenticated users, clicking on ‘Contact Support’ should redirect to feedback support form page with blank email id field, description and captcha
*'''T.3: ''' For authenticated users, clicking on ‘Contact Support’ should redirect to feedback support form page with email id auto-filled with email on their profile, description and captcha.
*'''T.4: ''' Before form submission, none of the fields should be blank. Appropriate blank error message should be shown otherwise.
*'''T.5: ''' Captcha should be random on every page load. Error message saying ‘incorrect captcha’ should be shown in case user fails to provide the same text of captcha.
*'''T.6: ''' Email should be received to Expertiza support “expertiza-support@lists.ncsu.edu” on the form submission and the user should get an acknowledgement of email received.

==='''A single “actions” icon with a pop up panel in place of the currently existing “action” icons on tree display'''===
*'''T.1: ''' Ensure that when a user click on the new “actions” icon, it throws a pop up panel with all the old “actions” icons.
*'''T.2: ''' Ensure that Edit icon redirects the user to edit assignment view.
*'''T.3: ''' Ensure that Delete icon deletes the assignment.
*'''T.4: ''' Ensure that Add TA icon redirects the user to Add TA view.
*'''T.5: ''' Ensure that Add Participant icon redirects the user to Add Participant view.
*'''T.6: ''' Ensure that Create Teams icon redirects the user to Create Teams view.
*'''T.7: ''' Ensure that Create Assignment icon redirects the user to Create Assignment view.
*'''T.8: ''' Ensure that 360 assessment dashboard icon redirect user to One_course_all_assignments page of assessment360 view.
*'''T.9: ''' Ensure that Copy icon redirects user to Edit course page.
*'''T.10: ''' Ensure that Make public icon redirects user to the tree display page.

CSC/ECE 517 Fall 2016/E1688. Send feedback to support + tree display improvement

2016-11-09T16:37:38Z

Sndesai: Setting up Doc framework and adding Hide Assignment nodes content

== '''Introduction to Expertiza''' ==

Expertiza is an open source software to create reusable learning objects through peer review supporting team projects and submission of project documents. In the final project, there are two major changes that will help in improving user experience.

=='''Purpose'''==

The purpose of this project is:
==='''Provide a new UI which allows users to send emails to expertiza support Background'''===
==='''A single “actions” icon with a pop up panel in place of the currently existing “action” icons on tree display'''===
The purpose of this enhancement is to reduce the wastage of space on the Manage Assignments page.

==='''Hide all assignment nodes on tree display'''===
The purpose of this enhancement is to give a way for the user to hide all assignment nodes on tree display.

=='''Background'''==
==='''Provide a new UI which allows users to send emails to expertiza support Background'''===
==='''A single “actions” icon with a pop up panel in place of the currently existing “action” icons on tree display'''===
==='''Hide all assignment nodes on tree display'''===
When a user clicks on any of the course node in My Courses, it opens up a tree display listing all the assignments available for this particular course node. There doesn’t exist a way to hide the assignment nodes after displaying them.

=='''Product Requirements'''==
==='''Provide a new UI which allows users to send emails to expertiza support Background'''===
==='''A single “actions” icon with a pop up panel in place of the currently existing “action” icons on tree display'''===
==='''Hide all assignment nodes on tree display'''===
My courses shows a list of all course nodes. Clicking on one of these nodes opens up a list of assignment nodes related to the course node. This requirement will add the functionality to allow a user to hide this list of assignment nodes after displaying them. So after getting the expanded view of assignment nodes, we will provide an extra functionality to the user to hide these assignment nodes which invokes a hide action on assignment nodes.

=='''Use Cases'''==
==='''Provide a new UI which allows users to send emails to expertiza support Background'''===
==='''A single “actions” icon with a pop up panel in place of the currently existing “action” icons on tree display'''===
==='''Hide all assignment nodes on tree display'''===
Input: User clicks on Hide link on Course nodes page.
 
Description: Hide the expanded view of Assignment nodes on Course nodes page.
 
Type of Input: Click on the Hide link.
 
Source of Input: User interface
 
Processing: Invoke the Hide Assignment nodes action on Course nodes page.
 
Output: Only Course nodes are listed.

=='''Testing Plan'''==
==='''Provide a new UI which allows users to send emails to expertiza support Background'''===
==='''A single “actions” icon with a pop up panel in place of the currently existing “action” icons on tree display'''===
==='''Hide all assignment nodes on tree display'''===
'''T.1''' Ensure that when a user clicks on the Hide button/link to hide the assignment nodes, the view only displays course nodes and not the related list of assignment nodes.

CSC/ECE 517 Fall 2016/E1652 Fix teammate advertisements and requests to join a team

2016-11-04T20:57:00Z

Sndesai: Adding issue 421

=='''Peer Review Information'''==

For users intending to view the deployed Expertiza associated with this assignment, the credentials are below:
* Instructor login: username -> instructor6, password -> password
* Student login: username -> student6420, password -> password
* Student login: username -> student6361, password -> password

=='''Introduction to Expertiza'''==

Expertiza is a peer review system where the students can submit their work and do reviews on fellow students’ work. Expertiza is an open source project and is based on “Ruby on Rails” framework. Expertiza facilitates easy creation of assignments and a list of topics for the same. It allows students to suggest a topic for an assignment as well. Students can form teams and invite other students to join their team for various assignments. Moreover, students can post team advertisements and describe the qualities they are looking for in their team members and other students can respond to the same. Expertiza overall gives a simple web interface for assignment management for both the students as well as instructors.

=='''Background'''==

In Expertiza, there are teammate advertisement, invitation and join team request features which facilitate students to form teams. Teammate advertisement works only for assignments with topics. The topic holders can create advertisement and a trumpet icon will show on the signup sheet page. If one respond to the advertisement, a join team request will be created and the topic holder can see it on “Your team” page. After a student get a team and the team is not full, (s)he should also be able to send invitations to others.

=='''Issues'''==

All commits have been done from a single machine using id sndesai92 but all team members have worked on the project.

Team members: 
1. Saloni Desai 
2. Shriyansh Yadav 
3. Vaibhav Shinde 

===Issue 312: ===
When a student gets accepted by a team, all the other join team requests/pending invitations should be removed.
 
'''Current Scenario :'''When a student gets accepted by a team, all other join team requests/pending invitations are still shown on his page and their corresponding entries in the database.
 
'''Fix:'''
 
'''Files Changed'''
 
''app/controllers/invitation_controller.rb''
[[File:Invitation_controller.png]]
 
If a student accepts an invite and that add was successful to the database, we call ''remove_pending_invitations()'' passing the ''student’s user_id'' and the current ''assignment_id'' to be deleted from the list of pending invitations.
Similarly, we call ''remove_pending_join_team_requests()'' passing the ''participant_id'' as a parameter. ''Participant_id'' is fetched from the ''Participant'' table which gives data on which all students participate in a particular assignment.
''remove_pending_invitations()'' and ''remove_pending_join_team_requests()'' methods are defined in ''models/invitation.rb'' and ''models/join_team_request.rb'' as these methods are manipulating the database and it has to handled by the models while controller simply invokes these methods.
 
 
''app/models/invitation.rb''
 
[[File:Invitation_model.png]]
 
''remove_pending_invitations()'' looks for all entries in the ''Invitation'' database that matches the ''student_id'' and an ''assignment_id'' and has a ''reply_status'' as ''waiting'' and destroys all of them.
 
 
''app/models/join_team_request.rb''
 
[[File:Join_team request_model.png]]
 
''remove_pending_join_team_requests()'' looks for all entries in the ''JoinTeamRequest'' database where a matching ''participant_id'' and the ''status'' is ''pending'' and deletes all those entries.
===Issue 311: ===
When one respond to an advertisement, (s)he should only be able to respond once.
 
'''Current scenario:''' A student can respond to an advertisement any number of times.
 
'''Fix:'''
 
'''Files Changed'''
 
''app/controllers/join_team_requests_controller.rb''
 
[[File:Join_team_request_controller.png]]
 
We check if the join request initiated by a student is a ''firstRequest?''. If it is a ''firstRequest?'' we allow the student to save the join request to the database else we flash a note saying the student has already responded to this particular advertisement once.
 
''app/models/join_team_request.rb''
 
[[File:Join_team_request_model1.png]]
 
''firstRequest?'' method fetches all entries from ''JoinTeamRequest'' table with a matching ''team_id'' and ''participant_id''. If the number of entries returned by this query is less than 1 means the student is requesting a join team request for the first time.
===Issue 227: ===
If user A got a topic and user B got no topic, then A join B’s team, A’s topic be be dropped and A and B end up with a new team with no topic. This issue should be handle carefully because we cannot simply add B to A’s team (imagine, if A has teammate X and B has teammate Y...). One of a potential fix is that, for assignment w/ topics, one cannot not post an ad unless (s)he holds a topic, similarly, one cannot sent invitations unless (s)he holds a topic.
 
'''Current Scenario:''' A student cannot create a team advertisement without a topic but can invite other students to join his/her team without a topic.
 
'''Fix:'''
 
'''Files Changed'''
 
''app/views/student_teams/view.html.erb''
 
[[File:Student_teams_view.png]]
 
Here we give access to the invite people link if and only if the team is not full and the student has a topic.
===Issue 5: ===
If the last member leaves the team, all the records will be deleted (like sign_up_topics, reviews done on this teams work, etc). We have to respect the decision of the students when they leave. But the team record should not be deleted if this team’s work has already got reviewed.
 
'''Current Scenario:''' If the last member leaves a team, the entire team is destroyed and a destroy on team creates a ripple effect thus destroying all the work done by this team.
 
'''Fix:'''
'''Files changed'''
 
''app/controllers/student_teams_controller.rb''
 
[[File:Student_teams_controller.png]]
 
 
''app/models/response_map.rb''
 
[[File:Response_map.png]]
 
===Issue 421: This issue is already fixed as stated by the current scenario. ===
The advertisement does not work properly when there are 2 teams posting advertisements on the same topic. 
'''Current Scenario:''' When 2 students post team advertisements for the same topic and a third student clicks on team advertisements, it shows both students' team advertisements.
 
 

=='''Testing Manually via UI'''==
 
'''Testing fix for Issue 312 :'''
 
Step 1: Login as an instructor. Create a new assignment (Assignment1) and related sign up topics (Topic1, Topic2, Topic3) and add atleast 4 students as participants. (student1, student2, student3, student4)
 
Step 2: Login as student1. Sign up for Topic1 for Assignment1. Create a team advertisement.
 
Step 3: Login as student2. Sign up for Topic2 for Assignment1. Create a team advertisement.
 
Step 4: Login as student3. Sign up for Topic3 for Assignment1. Invite student4 to join your team.
 
Step 5: Login as student4 and respond to student1 and student2’s team advertisements.
 
Step 6: Login as student1. Invite student4 from the response received to your team advertisement.
 
Step 7: Login as student4. Accept student1 invitation.
 
Outcome:
This should delete pending team request send to student2 and delete the join team request sent by student3.
 
 
==='''Testing fix for Issue 311:'''===
 
Step 1: Login as an instructor and create a new assignment (Assignment1) and related sign up topics (Topic1,Topic2) and add students (student1,student2) as participants.
 
Step 2: Login as student1 and sign up for Topic1 for Assignment1 and create a team advertisement for the same.
 
Step 3: Login as student2 and respond to student1’s team advertisement for Assignment1.
 
Step 4: Now as student2 again try to respond to student1’s team advertisement.
 
Outcome:
This should flash a message saying you have already responded to this team advertisement.
 
 
'''Testing fix for Issue 227:'''
 
Step 1: Login as an instructor and create a new assignment(Assignment1) and related sign up topics (Topic1,Topic2) and add students(student1,student2) as participants.
 
Step 2: Login as student1 and before signing up for a topic go to your team’s page.
 
Outcome:
It shouldn’t allow you to invite other people to join your team or create advertisements unless you have a topic assigned to you.
 
 

'''Issue 5''' cannot be tested from the UI as the team is not visible from the UI but still the entries in the databases are preserved if the team;s work is reviewed and the last member of the team leaves the team.

=='''References'''==

#[https://github.com/expertiza/expertiza Expertiza on GitHub]
#[http://research.csc.ncsu.edu/efg/expertiza Details of the Expertiza Project]
#[http://bit.ly/myexpertiza Demo link]

CSC/ECE 517 Fall 2016/E1652 Fix teammate advertisements and requests to join a team

2016-11-04T19:38:10Z

Sndesai: Adding how to manually test the fixes

=='''Peer Review Information'''==

For users intending to view the deployed Expertiza associated with this assignment, the credentials are below:
* Instructor login: username -> instructor6, password -> password
* Student login: username -> student6420, password -> password
* Student login: username -> student6361, password -> password

=='''Introduction to Expertiza'''==

Expertiza is a peer review system where the students can submit their work and do reviews on fellow students’ work. Expertiza is an open source project and is based on “Ruby on Rails” framework. Expertiza facilitates easy creation of assignments and a list of topics for the same. It allows students to suggest a topic for an assignment as well. Students can form teams and invite other students to join their team for various assignments. Moreover, students can post team advertisements and describe the qualities they are looking for in their team members and other students can respond to the same. Expertiza overall gives a simple web interface for assignment management for both the students as well as instructors.

=='''Background'''==

In Expertiza, there are teammate advertisement, invitation and join team request features which facilitate students to form teams. Teammate advertisement works only for assignments with topics. The topic holders can create advertisement and a trumpet icon will show on the signup sheet page. If one respond to the advertisement, a join team request will be created and the topic holder can see it on “Your team” page. After a student get a team and the team is not full, (s)he should also be able to send invitations to others.

=='''Issues'''==

All commits have been done from a single machine using id sndesai92 but all team members have worked on the project.

Team members: 
1. Saloni Desai 
2. Shriyansh Yadav 
3. Vaibhav Shinde 

===Issue 312: ===
When a student gets accepted by a team, all the other join team requests/pending invitations should be removed.
 
'''Current Scenario :'''When a student gets accepted by a team, all other join team requests/pending invitations are still shown on his page and their corresponding entries in the database.
 
'''Fix:'''
 
'''Files Changed'''
 
''app/controllers/invitation_controller.rb''
[[File:Invitation_controller.png]]
 
If a student accepts an invite and that add was successful to the database, we call ''remove_pending_invitations()'' passing the ''student’s user_id'' and the current ''assignment_id'' to be deleted from the list of pending invitations.
Similarly, we call ''remove_pending_join_team_requests()'' passing the ''participant_id'' as a parameter. ''Participant_id'' is fetched from the ''Participant'' table which gives data on which all students participate in a particular assignment.
''remove_pending_invitations()'' and ''remove_pending_join_team_requests()'' methods are defined in ''models/invitation.rb'' and ''models/join_team_request.rb'' as these methods are manipulating the database and it has to handled by the models while controller simply invokes these methods.
 
 
''app/models/invitation.rb''
 
[[File:Invitation_model.png]]
 
''remove_pending_invitations()'' looks for all entries in the ''Invitation'' database that matches the ''student_id'' and an ''assignment_id'' and has a ''reply_status'' as ''waiting'' and destroys all of them.
 
 
''app/models/join_team_request.rb''
 
[[File:Join_team request_model.png]]
 
''remove_pending_join_team_requests()'' looks for all entries in the ''JoinTeamRequest'' database where a matching ''participant_id'' and the ''status'' is ''pending'' and deletes all those entries.
===Issue 311: ===
When one respond to an advertisement, (s)he should only be able to respond once.
 
'''Current scenario:''' A student can respond to an advertisement any number of times.
 
'''Fix:'''
 
'''Files Changed'''
 
''app/controllers/join_team_requests_controller.rb''
 
[[File:Join_team_request_controller.png]]
 
We check if the join request initiated by a student is a ''firstRequest?''. If it is a ''firstRequest?'' we allow the student to save the join request to the database else we flash a note saying the student has already responded to this particular advertisement once.
 
''app/models/join_team_request.rb''
 
[[File:Join_team_request_model1.png]]
 
''firstRequest?'' method fetches all entries from ''JoinTeamRequest'' table with a matching ''team_id'' and ''participant_id''. If the number of entries returned by this query is less than 1 means the student is requesting a join team request for the first time.
===Issue 227: ===
If user A got a topic and user B got no topic, then A join B’s team, A’s topic be be dropped and A and B end up with a new team with no topic. This issue should be handle carefully because we cannot simply add B to A’s team (imagine, if A has teammate X and B has teammate Y...). One of a potential fix is that, for assignment w/ topics, one cannot not post an ad unless (s)he holds a topic, similarly, one cannot sent invitations unless (s)he holds a topic.
 
'''Current Scenario:''' A student cannot create a team advertisement without a topic but can invite other students to join his/her team without a topic.
 
'''Fix:'''
 
'''Files Changed'''
 
''app/views/student_teams/view.html.erb''
 
[[File:Student_teams_view.png]]
 
Here we give access to the invite people link if and only if the team is not full and the student has a topic.
===Issue 5: ===
If the last member leaves the team, all the records will be deleted (like sign_up_topics, reviews done on this teams work, etc). We have to respect the decision of the students when they leave. But the team record should not be deleted if this team’s work has already got reviewed.
 
'''Current Scenario:''' If the last member leaves a team, the entire team is destroyed and a destroy on team creates a ripple effect thus destroying all the work done by this team.
 
'''Fix:'''
'''Files changed'''
 
''app/controllers/student_teams_controller.rb''
 
[[File:Student_teams_controller.png]]
 
 
''app/models/response_map.rb''
 
[[File:Response_map.png]]
 
 

=='''Testing Manually via UI'''==
'''Testing fix for Issue 312 :'''
 
Step 1: Login as an instructor and create a new assignment (Assignment1) and related sign up topics (Topic1, Topic2, Topic3) and add atleast 4 students as participants. (student1, student2, student3, student4)
 
Step 2: Login as student1 and sign up for Topic1 for Assignment1 and create a team advertisement.
 
Step 3: Login as student2 and sign up for Topic2 for Assignment1 and create a team advertisement.
 
Step 4: Login as student3 and sign up for Topic3 for Assignment1 and invite student4 to join your team.
 
Step 5: Login as student4 and respond to student1 and student2’s team advertisements.
 
Step 6: Login as student1 invite student4 from the response received to your team advertisement.
 
Step 7: Login as student4 and accept student1 invitation. This should delete pending team request send to student2 and delete the join team request sent by student3.
 
 
'''Testing fix for Issue 311:'''
 
Step 1: Login as an instructor and create a new assignment (Assignment1) and related sign up topics (Topic1,Topic2) and add students (student1,student2) as participants.
 
Step 2: Login as student1 and sign up for Topic1 for Assignment1 and create a team advertisement for the same.
 
Step 3: Login as student2 and respond to student1’s team advertisement for Assignment1.
 
Step 4: Now as student2 again try to respond to student1’s team advertisement. This should flash a message saying you have already responded to this team advertisement.
 
 
'''Testing fix for Issue 227:'''
 
Step 1: Login as an instructor and create a new assignment(Assignment1) and related sign up topics (Topic1,Topic2) and add students(student1,student2) as participants.
 
Step 2: Login as student1 and before signing up for a topic go to your team’s page. It shouldn’t allow you to invite other people to join your team or create advertisements unless you have a topic assigned to you.
 
 

'''Issue 5''' cannot be tested from the UI as the team is not visible from the UI but still the entries in the databases are preserved if the team;s work is reviewed and the last member of the team leaves the team.

=='''References'''==

#[https://github.com/expertiza/expertiza Expertiza on GitHub]
#[http://research.csc.ncsu.edu/efg/expertiza Details of the Expertiza Project]
#[http://bit.ly/myexpertiza Demo link]

CSC/ECE 517 Fall 2016/E1652 Fix teammate advertisements and requests to join a team

2016-10-28T19:12:36Z

Sndesai: Adding code snippets for all issues fixed.

==='''Introduction to Expertiza'''===

----

Expertiza is a peer review system where the students can submit their work and do reviews on fellow students’ work. Expertiza is an open source project and is based on “Ruby on Rails” framework. Expertiza facilitates easy creation of assignments and a list of topics for the same. It allows students to suggest a topic for an assignment as well. Students can form teams and invite other students to join their team for various assignments. Moreover, students can post team advertisements and describe the qualities they are looking for in their team members and other students can respond to the same. Expertiza overall gives a simple web interface for assignment management for both the students as well as instructors.

==='''Background'''===

----

In Expertiza, there are teammate advertisement, invitation and join team request features which facilitate students to form teams. Teammate advertisement works only for assignments with topics. The topic holders can create advertisement and a trumpet icon will show on the signup sheet page. If one respond to the advertisement, a join team request will be created and the topic holder can see it on “Your team” page. After a student get a team and the team is not full, (s)he should also be able to send invitations to others.

==='''Issues'''===
----
'''Issue 312 :''' When a student gets accepted by a team, all the other join team requests/pending invitations should be removed.
 
'''Current Scenario :'''When a student gets accepted by a team, all other join team requests/pending invitations are still shown on his page and their corresponding entries in the database.
 
'''Fix:'''
 
'''Files Changed'''
 
''app/controllers/invitation_controller.rb''
[[File:Invitation_controller.png]]
 
If a student accepts an invite and that add was successful to the database, we call ''remove_pending_invitations()'' passing the ''student’s user_id'' and the current ''assignment_id'' to be deleted from the list of pending invitations.
Similarly, we call ''remove_pending_join_team_requests()'' passing the ''participant_id'' as a parameter. ''Participant_id'' is fetched from the ''Participant'' table which gives data on which all students participate in a particular assignment.
''remove_pending_invitations()'' and ''remove_pending_join_team_requests()'' methods are defined in ''models/invitation.rb'' and ''models/join_team_request.rb'' as these methods are manipulating the database and it has to handled by the models while controller simply invokes these methods.
 
 
''app/models/invitation.rb''
 
[[File:Invitation_model.png]]
 
''remove_pending_invitations()'' looks for all entries in the ''Invitation'' database that matches the ''student_id'' and an ''assignment_id'' and has a ''reply_status'' as ''waiting'' and destroys all of them.
 
 
''app/models/join_team_request.rb''
 
[[File:Join_team request_model.png]]
 
''remove_pending_join_team_requests()'' looks for all entries in the ''JoinTeamRequest'' database where a matching ''participant_id'' and the ''status'' is ''pending'' and deletes all those entries.
 
 
'''Issue 311:'''
 
''app/controllers/join_team_requests_controller.rb''
 
[[File:Join_team_request_controller.png]]
 
''app/models/join_team_request.rb''
 
[[File:Join_team_request_model1.png]]
 
 
'''Issue 227:'''
 
''app/views/student_teams/view.html.erb''
 
[[File:Student_teams_view.png]]
 
 
'''Issue 5:'''
 
''app/controllers/student_teams_controller.rb''
 
[[File:Student_teams_controller.png]]
 
 
''app/models/response_map.rb''
 
[[File:Response_map.png]]

File:Response map.png

2016-10-28T19:10:14Z

Sndesai:

File:Student teams controller.png

2016-10-28T19:09:30Z

Sndesai:

File:Student teams view.png

2016-10-28T19:08:21Z

Sndesai:

File:Join team request model1.png

2016-10-28T19:07:02Z

Sndesai:

File:Join team request controller.png

2016-10-28T19:06:23Z

Sndesai:

CSC/ECE 517 Fall 2016/E1652 Fix teammate advertisements and requests to join a team

2016-10-28T19:03:37Z

Sndesai: Adding documentation for issue 312

File:Join team request model.png

2016-10-28T19:01:10Z

Sndesai:

File:Invitation model.png

2016-10-28T18:58:36Z

Sndesai:

File:Invitation controller.png

2016-10-28T18:54:55Z

Sndesai:

CSC/ECE 517 Fall 2016/E1652 Fix teammate advertisements and requests to join a team

2016-10-28T18:39:51Z

Sndesai: Adding a background for team advertisements

===Introduction to Expertiza===

----

Expertiza is a peer review system where the students can submit their work and do reviews on fellow students’ work. Expertiza is an open source project and is based on “Ruby on Rails” framework. Expertiza facilitates easy creation of assignments and a list of topics for the same. It allows students to suggest a topic for an assignment as well. Students can form teams and invite other students to join their team for various assignments. Moreover, students can post team advertisements and describe the qualities they are looking for in their team members and other students can respond to the same. Expertiza overall gives a simple web interface for assignment management for both the students as well as instructors.

===Background===

----

In Expertiza, there are teammate advertisement, invitation and join team request features which facilitate students to form teams. Teammate advertisement works only for assignments with topics. The topic holders can create advertisement and a trumpet icon will show on the signup sheet page. If one respond to the advertisement, a join team request will be created and the topic holder can see it on “Your team” page. After a student get a team and the team is not full, (s)he should also be able to send invitations to others.