CSC/ECE 517 Fall 2015 E1584 Send Feedback to Support: Difference between revisions

From Expertiza_Wiki
Jump to navigation Jump to search
Line 14: Line 14:
The following specifications are required in the feature :
The following specifications are required in the feature :


* The "Contact Support" feature should be present in the title bar. This should help facilitate feedback from un-logged users.
# The "Contact Support" feature should be present in the title bar. This should help facilitate feedback from un-logged users.


* Clicking on "Contact Support" should open a new page rather than a pop-up or modal dialog box. This is because this feature should be mobile-friendly.
# Clicking on "Contact Support" should open a new page rather than a pop-up or modal dialog box. This is because this feature should be mobile-friendly.


* The feedback should go expertiza-support@lists.ncsu.edu.
# The feedback should go expertiza-support@lists.ncsu.edu.


* Users should should have the facility to upload only one file in their feedback.  
# Users should should have the facility to upload only one file in their feedback.  


* The uploaded file should be either in .pdf or .png/.jpg format. Moreover the extension list should not be hard-coded. A white-list of the extensions supported, should be present in the database.   
# The uploaded file should be either in .pdf or .png/.jpg format. Moreover the extension list should not be hard-coded. A white-list of the extensions supported, should be present in the database.   


* The size of the uploaded file should not exceed 2MB.
# The size of the uploaded file should not exceed 2MB.


* To avoid attacks, the feedback form should contain a CAPTCHA.
# To avoid attacks, the feedback form should contain a CAPTCHA.


* There should be a separate method that keeps a check on multiple requests. An algorithm should be implemented to add incremental delay between consecutive requests after three trials.
# There should be a separate method that keeps a check on multiple requests. An algorithm should be implemented to add incremental delay between consecutive requests after three trials.


*
#
   
   
=== Discussion of Resolution ===
= Proposed Implementation =


We will make the following modifications to implement the chat feature:- <br>
== Mock Ups ==
 
*Create a new model which will help extract,store and validate data in the database table which contains information about the interaction between the author/s and reviewer.
 
*Edit the view which is used by the response controller to incorporate the text area input field on the review form where the reviewer can ask his/her initial query.
 
*Create a new controller which will contain methods to send emails to the author and reviewers as well as retrieve and display the chat history between the two.
 
*Create a new view which will facilitate the author to respond to the queries asked by the reviewer. The reviewer can also use this view to ask any follow up questions.
 
=== Mock-Ups ===
The sample question box would look like:
 
[[File: ARSNMockup1.JPG]]
 
An interface with the question would be displayed on opening a link from the email.
The authors can reply the query which reviewers ask.
 
[[File: ARSNMockup2.JPG]]
 
=== Design Patterns ===
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum
 
=== Database Design ===
 
[[File:DatabaseTable.jpg]]
 
The above figure shows the schema of a new table which will be created in Expertiza to store relevant information about the chat. It contains the following attributes:
* id: This attribute is auto-generated by rails when we create a table and is auto incremented with each record. It is also the primary key of our table.
* assignment_id: Stores the ID of the assignment for which the interaction between author and reviewer is taking place.
* reviewer_id: Stores the ID of the reviewer who asks the questions.
* team_id: Stores the ID of the team to which the topic belongs.
* type_flag: Flag which is used to indicate if the particular tuple contains a question or answer. It can take two values, 'Q' for question and 'A' for answer.
* content: Stores the question asked by the reviewer or the response given by the author/s depending on the value of the type flag.
 
Records for a particular interaction can be identified by using a combination of assignment_id, reviewer_id and team_id.
 
=== Use Cases ===
'''Name:''' Send a question to the author/s about their work.<br>
'''Actor:''' Reviewer. <br>
'''Description:''' The reviewer enters his question in the text area which is provided and clicks on the "Ask question" button which is provided as shown in the mock up. On clicking this button an email is sent to the author/s along which a link to answer the question.<br>
<br>
'''Name:''' Answer the question which has been asked by the reviewer.<br>
'''Actor:''' Author/s<br>
'''Description:''' The author/s click on the link received in their email and are redirected to a page where they can answer the question. Once they submit the answer, an email is sent to the reviewer notifying him/her that their question has been answered.<br>
 
=== Proposed Tests ===
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum


== Implementation ==
== Implementation ==

Revision as of 04:59, 10 November 2015

E1584. Send Feedback to Support

This is the design document for the Feedback to Support feature of Expertiza. This goal of this

Introduction

Expertiza is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). It is used in select courses at NC State and by professors at several other colleges and universities. <ref>Expertiza on GitHub</ref>

Problem Statement

The objective of this project is to allow Expertiza users to directly send their issues to Expertiza support via support form. Currently there is no support feature and the problems are passed on to the support people via instructors. The aim of this feature is faster resolution of the problems faced by the users. This feature should be available to all registered users and the users should have access to it even when they are not logged in. This feature should also allow users to send screenshots of their issues. Apart from the feedback form, a view for the support person is also required. This view would contain a collective list of all the problems. The support person would be able to change the status of the problem.

Design Specification

The following specifications are required in the feature :

  1. The "Contact Support" feature should be present in the title bar. This should help facilitate feedback from un-logged users.
  1. Clicking on "Contact Support" should open a new page rather than a pop-up or modal dialog box. This is because this feature should be mobile-friendly.
  1. The feedback should go expertiza-support@lists.ncsu.edu.
  1. Users should should have the facility to upload only one file in their feedback.
  1. The uploaded file should be either in .pdf or .png/.jpg format. Moreover the extension list should not be hard-coded. A white-list of the extensions supported, should be present in the database.
  1. The size of the uploaded file should not exceed 2MB.
  1. To avoid attacks, the feedback form should contain a CAPTCHA.
  1. There should be a separate method that keeps a check on multiple requests. An algorithm should be implemented to add incremental delay between consecutive requests after three trials.

Proposed Implementation

Mock Ups

Implementation

Files created/modified:-

  • Create a new model chat_feedback.rb
  • Create a new controller review_interactions_controller.rb
  • Create new views as discussed in the design.
  • Modify view expertiza/app/views/response/response.html.erb to incorporate text box and corresponding submit button.

Flow:-

  • The reviewer enters his question in the text area provided and clicks on the "Ask Question" button.
  • On clicking this button the appropriate method is called in review_interactions_controller.rb which sends an email to all the authors of the topic indicating that a question has been asked about their work. The email contains a link which when clicked on will redirect the author to the appropriate view where he/she can answer the question.
  • On answering the question, the reviewer receives an email indicating that his question has been answered. It also contains a link which redirects the reviewer to the appropriate view where the answer will be displayed.
  • This view also contains the chat history between the author/s and the reviewer for the entire duration of the interaction.

Suggestions for Future Improvements

  • This can be extended to a live interactive author-reviewer anonymous chat session inside the Expertiza reviews window.
  • A purging script can be developed which will clear all the interaction records every semester.

Resources

References

<references/>

Retrieved from "https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2015_E1584_Send_Feedback_to_Support&oldid=99371"