Expertiza_Wiki - User contributions [en]

CSC/ECE 517 Fall 2016/E1680. Improve survey functionality

2016-11-20T18:48:23Z

Dssathe: /* Structure */

=='''Introduction to Expertiza'''==
The Expertiza project is software to create reusable learning objects through peer review. It also supports team projects, and the submission of almost any document type, including URLs and wiki pages. 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. Expertiza, in other words, gives a very simple web interface for assignment management for both the students as well as instructors.

=='''Problem Statement'''==
==='''Overview'''===
Expertiza should be able to distribute surveys to the users. The survey can be one of the following:
1. Course survey (all the participants of the course can take it).
2. Global survey (all the users in Expertiza can take it).
<br>
The survey can also be targeted (the admin can specify a group of people who will receive this survey).
<br>
The three kinds of surveys in this project are:
*1. survey_questionnaire.rb
*2. global_survey_questionnaire.rb
*3. course_evaluation_questionnaire.rb.

==='''Constraints'''===
* Survey questionnaire should be a subclass of questionnaire.
* The creation, editing, filling in, and checking that all the questions have been answered survey should be similar to the procedure used for other types of questionnaires (e.g. peer-review questionnaires).
* There should be a page to see the distribution of results for any question.
* We should use the same controller method to take the survey as to fill in the peer-review, namely, response_controller.
* We should use the same code to display the existing survey responses as to display the responses in peer reviews.
* For each course or assignment, the admin/instructor should be able to create a survey and have some (or all) of the participants receive the survey.
* When a user is assigned to take part in a survey, a survey_participant record should be created for that user in the participants table.
==='''Existing Models, Views and Controllers'''===
Survey questionnaire, Global Survey questionnaire and course_evaluation_questionnaire are the existing models which are subclasses of questionnaire. Their
display types are survey, global survey and course evaluation respectively. The controller file present currently is survey_controller.rb. Its
functionalities include-
* Action can only be taken by Instructor, Teaching Assistant and Administrator.
* Surveys can be assigned with the help of an assignment id.
A survey view file is also present to assign or list the surveys.

=='''Proposed Design'''==
==='''Structure'''===
In our design we have three kinds of survey-
* survey_questionnaire
* global_survey_questionnaire
* course_evaluation_questionnaire
These models should be made as subclasses of the class survey. By using the concept of polymorphism, survey is made a subclass of survey_questionnaire as many kinds of survey_questionnaire can exist and by using polymorphism, the code can be made more efficient. Survey_questionnaire is then a subclass of questionnaire. Complete refactoring is needed as the existing code is inefficient.

[[File:Class_diagram_new.PNG | center]]

=== '''Distribution of results''' ===

* There will be a page to see the distribution of results for any question (e.g., how many people answered “1”, how many answered “2”, etc.).
* This page will not only be designed for surveys, but also for other types of questionnaires (E.g. this view be able to show the score distribution for a question in other types of questionnaires, no matter whether it is a survey question like “how much do you like the course?” or a peer-review question like “how well did the author test the code?”)
<br>
'''Proposed Implementation'''

The required page for this implementation would look like this:

[[File:Distribution_of_results.PNG]]

* Our page to see the distribution of results for any question would render a similar Bar graph
* showing the no of people who answered a choice amongst the options.
* The vertical axis would show the no of people.
* The horizontal axis will show the possible answers to the question.
* To implement this in Expertise we can use JQPlot Rails or some other graph plotting plugin.

The ''JQuery'' code might look like
[[File:Code_snippet.PNG]]

* We will have to integrate the Jquery plugin and create a .erb file in views which will have similar
* Jquery code to render a bar graph based on the data provided.

==='''Taking the survey'''===
* There is a constraint that the survey has to be filled in using the same controller method as used for filling in peer review, namely response_controller. Also, the same code has to be used to display the existing survey responses as to display the responses in peer review.
* The response_controller can be used to make sure that the survey can be taken only once by each user, depending upon the survey type and the users who are allowed to access (can be listed using 'action_allowed?'). The answers can be saved using the 'saving' method. Also, the responses can be viewed once, the survey is submitted.

==='''Adding Participants to the survey:'''===

* Instructor or admin both can add survey for any course or assignment

* The creator would be able to select the participants based on the scope of the survey, that is, all the students or all the Expertiza users or specific group of people.

==='''Adding all the global questionnaire questions:'''===

* There would be a generic set of questions which will be included in global_survey_questionnaire.
* These questions will be by default added to every survey the user creates.
* But, creator will be able to omit them with one ‘checkbox’ button (Or, we can have specific selections for each of the questions to be included).
* Or, there can be option of separating the global survey and course survey. The quiz taker will take the global survey first and then the course survey.

==='''Adding the data to database:'''===

* For each participant added by the creator of the survey, a database entry would be made in participant table along with appropriate details.
=='''Files to be modified:'''==
==='''Controllers'''===
*app/controllers/survey_deployment_controller.rb
*app/controllers/statistics_controller.rb
*app/controllers/course_evaluation_controller.rb
*app/controllers/survey_controller.rb
==='''Models'''===
*app/models/global_survey_questionnaire.rb
*app/models/survey_questionnaire.rb
*app/models/survey_deployment.rb
*app/models/metasurvey.rb
*app/helpers/survey_helper.rb
*app/models/survey_participant.rb
*app/models/survey_response.rb
*app/helpers/survey_response_helper.rb
==='''Views'''===
*app/views/survey_deployment/
*app/views/statistics/
*app/views/survey_response/
*app/views/survey
=='''Testing'''==
==='''Testing using UI'''===

'''Login as instructor:'''<br>
1. Use credentials username: instructor6, password:password.<br>
2. Click on Manage -> Questionnaires-> Survey / Global Survey/ Course evaluation.<br>
3. Create a new Survey/ Global Survey/ Course evaluation filling in the parameters asked for.<br>
[[File:Procedure expertiza.PNG]]

'''Login as student:'''<br>
1. The course survey is for all the students, whereas the global survey is for a few random students using Expertiza.<br>
2. Take the survey visible through your account.

==='''RSpec Testing'''===
On implementing the survey functionality, we plan to include the following tests:<br>
1. The survey is submitted only if all the questions are answered.<br>
2. There is a record created in the participant table for that user as asked for implementation in the design specifications.<br>
3. The student added by the instructor for the survey, receives the survey.

File:Class diagram new.PNG

2016-11-20T18:47:32Z

Dssathe:

File:Class diagram.PNG

2016-11-20T18:45:39Z

Dssathe: uploaded a new version of "File:Class diagram.PNG"

File:Class diagram.PNG

2016-11-20T18:45:07Z

Dssathe: uploaded a new version of "File:Class diagram.PNG"

CSC/ECE 517 Fall 2016/E1680. Improve survey functionality

2016-11-14T04:50:19Z

Dssathe: /* Structure */

=='''Introduction to Expertiza'''==
The Expertiza project is software to create reusable learning objects through peer review. It also supports team projects, and the submission of almost any document type, including URLs and wiki pages. 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. Expertiza, in other words, gives a very simple web interface for assignment management for both the students as well as instructors.

=='''Problem Statement'''==
==='''Overview'''===
Expertiza should be able to distribute surveys to the users. The survey can be one of the following:
1. Course survey (all the participants of the course can take it).
2. Global survey (all the users in Expertiza can take it).
<br>
The survey can also be targeted (the admin can specify a group of people who will receive this survey).
<br>
The three kinds of surveys in this project are:
*1. survey_questionnaire.rb
*2. global_survey_questionnaire.rb
*3. course_evaluation_questionnaire.rb.
==='''Constraints'''===
* Survey questionnaire should be a subclass of questionnaire.
* The creation, editing, filling in, and checking that all the questions have been answered survey should be similar to the procedure used for other types of questionnaires (e.g. peer-review questionnaires).
* There should be a page to see the distribution of results for any question.
* We should use the same controller method to take the survey as to fill in the peer-review, namely, response_controller.
* We should use the same code to display the existing survey responses as to display the responses in peer reviews.
* For each course or assignment, the admin/instructor should be able to create a survey and have some (or all) of the participants receive the survey.
* When a user is assigned to take part in a survey, a survey_participant record should be created for that user in the participants table.
==='''Existing Models, Views and Controllers'''===
Survey questionnaire, Global Survey questionnaire and course_evaluation_questionnaire are the existing models which are subclasses of questionnaire. Their
display types are survey, global survey and course evaluation respectively. The controller file present currently is survey_controller.rb. Its
functionalities include-
* Action can only be taken by Instructor, Teaching Assistant and Administrator.
* Surveys can be assigned with the help of an assignment id.
A survey view file is also present to assign or list the surveys.

=='''Proposed Design'''==
==='''Structure'''===
In our design we have three kinds of survey-
* survey_questionnaire
* global_survey_questionnaire
* course_evaluation_questionnaire
These models should be made as subclasses of the class survey. By using the concept of polymorphism, survey is made a subclass of survey_questionnaire as many kinds of survey_questionnaire can exist and by using polymorphism, the code can be made more efficient. Survey_questionnaire is then a subclass of questionnaire. Complete refactoring is needed as the existing code is inefficient.

[[File:Class_diagram.PNG | center]]

=== '''Distribution of results''' ===

* There will be a page to see the distribution of results for any question (e.g., how many people answered “1”, how many answered “2”, etc.).
* This page will not only be designed for surveys, but also for other types of questionnaires (E.g. this view be able to show the score distribution for a question in other types of questionnaires, no matter whether it is a survey question like “how much do you like the course?” or a peer-review question like “how well did the author test the code?”)
<br>
'''Proposed Implementation'''

The required page for this implementation would look like this:

[[File:Distribution_of_results.PNG]]

* Our page to see the distribution of results for any question would render a similar Bar graph
* showing the no of people who answered a choice amongst the options.
* The vertical axis would show the no of people.
* The horizontal axis will show the possible answers to the question.
* To implement this in Expertise we can use JQPlot Rails or some other graph plotting plugin.

The ''JQuery'' code might look like
[[File:Code_snippet.PNG]]

* We will have to integrate the Jquery plugin and create a .erb file in views which will have similar
* Jquery code to render a bar graph based on the data provided.

==='''Taking the survey'''===
* There is a constraint that the survey has to be filled in using the same controller method as used for filling in peer review, namely response_controller. Also, the same code has to be used to display the existing survey responses as to display the responses in peer review.
* The response_controller can be used to make sure that the survey can be taken only once by each user, depending upon the survey type and the users who are allowed to access (can be listed using 'action_allowed?'). The answers can be saved using the 'saving' method. Also, the responses can be viewed once, the survey is submitted.

==='''Adding Participants to the survey:'''===

* Instructor or admin both can add survey for any course or assignment

* The creator would be able to select the participants based on the scope of the survey, that is, all the students or all the Expertiza users or specific group of people.

==='''Adding all the global questionnaire questions:'''===

* There would be a generic set of questions which will be included in global_survey_questionnaire.
* These questions will be by default added to every survey the user creates.
* But, creator will be able to omit them with one ‘checkbox’ button (Or, we can have specific selections for each of the questions to be included).
* Or, there can be option of separating the global survey and course survey. The quiz taker will take the global survey first and then the course survey.

==='''Adding the data to database:'''===

* For each participant added by the creator of the survey, a database entry would be made in participant table along with appropriate details.
=='''Files to be modified:'''==
==='''Controllers'''===
*app/controllers/survey_deployment_controller.rb
*app/controllers/statistics_controller.rb
*app/controllers/course_evaluation_controller.rb
*app/controllers/survey_controller.rb
==='''Models'''===
*app/models/global_survey_questionnaire.rb
*app/models/survey_questionnaire.rb
*app/models/survey_deployment.rb
*app/models/metasurvey.rb
*app/helpers/survey_helper.rb
*app/models/survey_participant.rb
*app/models/survey_response.rb
*app/helpers/survey_response_helper.rb
==='''Views'''===
*app/views/survey_deployment/
*app/views/statistics/
*app/views/survey_response/
*app/views/survey

File:Class diagram.PNG

2016-11-14T04:48:09Z

Dssathe: uploaded a new version of "File:Class diagram.PNG"

CSC/ECE 517 Fall 2016/E1680. Improve survey functionality

2016-11-14T04:44:51Z

Dssathe: /* Structure */

=='''Introduction to Expertiza'''==
The Expertiza project is software to create reusable learning objects through peer review. It also supports team projects, and the submission of almost any document type, including URLs and wiki pages. 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. Expertiza, in other words, gives a very simple web interface for assignment management for both the students as well as instructors.

=='''Problem Statement'''==
==='''Overview'''===
Expertiza should be able to distribute surveys to the users. The survey can be one of the following:
1. Course survey (all the participants of the course can take it).
2. Global survey (all the users in Expertiza can take it).
<br>
The survey can also be targeted (the admin can specify a group of people who will receive this survey).
<br>
The three kinds of surveys in this project are:
*1. survey_questionnaire.rb
*2. global_survey_questionnaire.rb
*3. course_evaluation_questionnaire.rb.
==='''Constraints'''===
* Survey questionnaire should be a subclass of questionnaire.
* The creation, editing, filling in, and checking that all the questions have been answered survey should be similar to the procedure used for other types of questionnaires (e.g. peer-review questionnaires).
* There should be a page to see the distribution of results for any question.
* We should use the same controller method to take the survey as to fill in the peer-review, namely, response_controller.
* We should use the same code to display the existing survey responses as to display the responses in peer reviews.
* For each course or assignment, the admin/instructor should be able to create a survey and have some (or all) of the participants receive the survey.
* When a user is assigned to take part in a survey, a survey_participant record should be created for that user in the participants table.
==='''Existing Models, Views and Controllers'''===
Survey questionnaire, Global Survey questionnaire and course_evaluation_questionnaire are the existing models which are subclasses of questionnaire. Their
display types are survey, global survey and course evaluation respectively. The controller file present currently is survey_controller.rb. Its
functionalities include-
* Action can only be taken by Instructor, Teaching Assistant and Administrator.
* Surveys can be assigned with the help of an assignment id.
A survey view file is also present to assign or list the surveys.

=='''Proposed Design'''==
==='''Structure'''===
In our design we have three kinds of survey-
* survey_questionnaire
* global_survey_questionnaire
* course_evaluation_questionnaire
These models should be made as subclasses of the class survey. By using the concept of polymorphism, survey is made a subclass of survey_questionnaire as many kinds of survey_questionnaire can exist and by using polymorphism, the code can be made more efficient. Survey_questionnaire is then a subclass of questionnaire. Complete refactoring is needed as the existing code is inefficient.
[[File:Class_diagram.PNG]]

=== '''Distribution of results''' ===

* There will be a page to see the distribution of results for any question (e.g., how many people answered “1”, how many answered “2”, etc.).
* This page will not only be designed for surveys, but also for other types of questionnaires (E.g. this view be able to show the score distribution for a question in other types of questionnaires, no matter whether it is a survey question like “how much do you like the course?” or a peer-review question like “how well did the author test the code?”)
<br>
'''Proposed Implementation'''

The required page for this implementation would look like this:

[[File:Distribution_of_results.PNG]]

* Our page to see the distribution of results for any question would render a similar Bar graph
* showing the no of people who answered a choice amongst the options.
* The vertical axis would show the no of people.
* The horizontal axis will show the possible answers to the question.
* To implement this in Expertise we can use JQPlot Rails or some other graph plotting plugin.

The ''JQuery'' code might look like
[[File:Code_snippet.PNG]]

* We will have to integrate the Jquery plugin and create a .erb file in views which will have similar
* Jquery code to render a bar graph based on the data provided.

==='''Taking the survey'''===
* There is a constraint that the survey has to be filled in using the same controller method as used for filling in peer review, namely response_controller. Also, the same code has to be used to display the existing survey responses as to display the responses in peer review.
* The response_controller can be used to make sure that the survey can be taken only once by each user, depending upon the survey type and the users who are allowed to access (can be listed using 'action_allowed?'). The answers can be saved using the 'saving' method. Also, the responses can be viewed once, the survey is submitted.

==='''Adding Participants to the survey:'''===

* Instructor or admin both can add survey for any course or assignment

* The creator would be able to select the participants based on the scope of the survey, that is, all the students or all the Expertiza users or specific group of people.

==='''Adding all the global questionnaire questions:'''===

* There would be a generic set of questions which will be included in global_survey_questionnaire.
* These questions will be by default added to every survey the user creates.
* But, creator will be able to omit them with one ‘checkbox’ button (Or, we can have specific selections for each of the questions to be included).
* Or, there can be option of separating the global survey and course survey. The quiz taker will take the global survey first and then the course survey.

==='''Adding the data to database:'''===

* For each participant added by the creator of the survey, a database entry would be made in participant table along with appropriate details.
=='''Files to be modified:'''==
==='''Controllers'''===
*app/controllers/survey_deployment_controller.rb
*app/controllers/statistics_controller.rb
*app/controllers/course_evaluation_controller.rb
*app/controllers/survey_controller.rb
==='''Models'''===
*app/models/global_survey_questionnaire.rb
*app/models/survey_questionnaire.rb
*app/models/survey_deployment.rb
*app/models/metasurvey.rb
*app/helpers/survey_helper.rb
*app/models/survey_participant.rb
*app/models/survey_response.rb
*app/helpers/survey_response_helper.rb
==='''Views'''===
*app/views/survey_deployment/
*app/views/statistics/
*app/views/survey_response/
*app/views/survey

File:Class diagram.PNG

2016-11-14T04:43:58Z

Dssathe:

CSC/ECE 517 Fall 2016/E1680. Improve survey functionality

2016-11-10T00:14:34Z

Dssathe: /* Design */

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

=='''Background'''==

==='''Classes involved:'''===

==='''Goal'''===
Expertiza should be able to distribute surveys to the users. The survey can be one of the following:
1. Course survey (all the participants of the course can take it).
2. Global survey (all the users in Expertiza can take it).
<br>
The survey can also be targeted (the admin can specify a group of people who will receive this survey).
<br>
The three kinds of surveys in this project are:
*1. survey_questionnaire.rb
*2. global_survey_questionnaire.rb
*3. course_evaluation_questionnaire.rb.

Survey questionnaire should be a subclass of questionnaire.
The creation, editing, filling in, and checking that all the questions have been answered survey should be similar to the procedure used for other types of questionnaires (e.g. peer-review questionnaires).
There should be a page to see the distribution of results for any question (e.g., how many people answered “1”, how many answered “2”, etc.). This page should not only be designed for surveys, but also for other types of questionnaires. (E.g. this view be able to show the score distribution for a question in other types of questionnaires, no matter whether it is a survey question like “how much do you like the course?” or a peer-review question like “how well did the author test the code?”)
<br>
We should use the same controller method to take the survey as to fill in the peer-review, namely, response_controller.
We should use the same code to display the existing survey responses as to display the responses in peer reviews.
<br>
For each course or assignment, the admin/instructor should be able to create a survey and have some (or all) of the participants receive the survey.
When a user is assigned to take part in a survey, a survey_participant record should be created for that user in the participants table.

=='''Issues'''==

== '''Design''' ==

Requirement

There should be a page to see the distribution of results for any question (e.g., how many people answered “1”, how many answered “2”, etc.).
This page should not only be designed for surveys, but also for other types of questionnaires.
(E.g. this view be able to show the score distribution for a question in other types of questionnaires, no
matter whether it is a survey question like “how much do you like the course?” or a peer-review question like
“how well did the author test the code?”)

Proposed Implementation

The required page for this implementation would look like this:

[[File:Distribution_of_results.PNG]]

Our page to see the distribution of results for any question would render a similar Bar graph
showing the no of people who answered a choice amongst the options.
The vertical axis would show the no of people.
The horizontal axis will show the possible answers to the question.
To implement this in Expertise we can use JQPlot Rails or some other graph plotting plugin.

The ''JQuery'' code might look like
[[File:Code_snippet.PNG]]

We will have to integrate the Jquery plugin and create a .erb file in views which will have similar
Jquery code to render a bar graph based on the data provided.

=='''Updates'''==

=='''Files to be modified:'''==
==='''Controllers'''===

*app/controllers/survey_deployment_controller.rb
*app/controllers/statistics_controller.rb
*app/controllers/course_evaluation_controller.rb
*app/controllers/survey_controller.rb

==='''Models'''===

*app/models/global_survey_questionnaire.rb
*app/models/survey_questionnaire.rb
*app/models/survey_deployment.rb
*app/models/metasurvey.rb
*app/helpers/survey_helper.rb
*app/models/survey_participant.rb
*app/models/survey_response.rb
*app/helpers/survey_response_helper.rb

==='''Views'''===
*app/views/survey_deployment/
*app/views/statistics/
*app/views/survey_response/
*app/views/survey

== '''Testing Details''' ==

File:Code snippet.PNG

2016-11-10T00:11:43Z

Dssathe:

CSC/ECE 517 Fall 2016/E1680. Improve survey functionality

2016-11-10T00:08:54Z

Dssathe: /* Design */

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

=='''Background'''==

==='''Classes involved:'''===

==='''Goal'''===
Expertiza should be able to distribute surveys to the users. The survey can be one of the following:
1. Course survey (all the participants of the course can take it).
2. Global survey (all the users in Expertiza can take it).
<br>
The survey can also be targeted (the admin can specify a group of people who will receive this survey).
<br>
The three kinds of surveys in this project are:
*1. survey_questionnaire.rb
*2. global_survey_questionnaire.rb
*3. course_evaluation_questionnaire.rb.

Survey questionnaire should be a subclass of questionnaire.
The creation, editing, filling in, and checking that all the questions have been answered survey should be similar to the procedure used for other types of questionnaires (e.g. peer-review questionnaires).
There should be a page to see the distribution of results for any question (e.g., how many people answered “1”, how many answered “2”, etc.). This page should not only be designed for surveys, but also for other types of questionnaires. (E.g. this view be able to show the score distribution for a question in other types of questionnaires, no matter whether it is a survey question like “how much do you like the course?” or a peer-review question like “how well did the author test the code?”)
<br>
We should use the same controller method to take the survey as to fill in the peer-review, namely, response_controller.
We should use the same code to display the existing survey responses as to display the responses in peer reviews.
<br>
For each course or assignment, the admin/instructor should be able to create a survey and have some (or all) of the participants receive the survey.
When a user is assigned to take part in a survey, a survey_participant record should be created for that user in the participants table.

=='''Issues'''==

== '''Design''' ==

Problem Statement

There should be a page to see the distribution of results for any question (e.g., how many people answered “1”, how many answered “2”, etc.). This page should not only be designed for surveys, but also for other types of questionnaires. (E.g. this view be able to show the score distribution for a question in other types of questionnaires, no matter whether it is a survey question like “how much do you like the course?” or a peer-review question like “how well did the author test the code?”)

Proposed Implementation

The required page for this implementation would look like this:

Our page to see the distribution of results for any question would render a similar Bar graph showing the no of people who answered a choice amongst the options.
The vertical axis would show the no of people.
The horizontal axis will show the possible answers to the question.
To implement this in Expertise we can use JQPlot Rails or some other graph plotting plugin.

The JQuery code might look like

We will have to integrate the Jquery plugin and create a .erb file in views which will have similar Jquery code to render a bar graph based on the data provided.

=='''Updates'''==

=='''Files to be modified:'''==
==='''Controllers'''===

*app/controllers/survey_deployment_controller.rb
*app/controllers/statistics_controller.rb
*app/controllers/course_evaluation_controller.rb
*app/controllers/survey_controller.rb

==='''Models'''===

*app/models/global_survey_questionnaire.rb
*app/models/survey_questionnaire.rb
*app/models/survey_deployment.rb
*app/models/metasurvey.rb
*app/helpers/survey_helper.rb
*app/models/survey_participant.rb
*app/models/survey_response.rb
*app/helpers/survey_response_helper.rb

==='''Views'''===
*app/views/survey_deployment/
*app/views/statistics/
*app/views/survey_response/
*app/views/survey

== '''Testing Details''' ==

File:Distribution of results.PNG

2016-11-10T00:07:38Z

Dssathe:

CSC/ECE 517 Fall 2016/E1680. Improve survey functionality

2016-11-08T23:13:11Z

Dssathe: /* Files modified: */

CSC/ECE 517 Fall 2016/E1654. Improve date-picker and deadlines

2016-10-29T22:36:05Z

Dssathe: /* Testing from UI */

This wiki page is for the description of changes made under E1654/Improve date-picker and deadlines OSS assignment for Fall 2016, CSC/ECE 517.

== About Expertiza ==
[http://wiki.expertiza.ncsu.edu/index.php/Main_Page#Expertiza Expertiza] is a [https://en.wikipedia.org/wiki/Ruby_on_Rails Ruby on Rails] application made by the joint contribution of Professors and Students of [https://en.wikipedia.org/wiki/North_Carolina_State_University North Carolina State University]. It is used by the Professor ,Teaching Assistants and students of a particular course to manage their respective responsibilities with respect to that course. Professor can enlist a new assignment or project, set/update the deadline to submit it , grant publishing rights to a user and more. The Teaching Assistants can including other things update the review scores of the students, view the submissions etc. The students can view information about all the assignments due and submitted.Students can form teams in Expertiza to work on various projects and assignments.Students can also review other students' submissions and the performance of their teammates. Expertiza supports submissions across various document types, including the URLs and wiki pages.

== Problem Statement ==

The [https://en.wikipedia.org/wiki/North_Carolina_State_University Date-picker] allows the instructor to set deadlines for the assignments and peer reviews.

1) The current date-picker doesn't let you change dates easily. When you try to edit a deadline, Unless you spell it out to the minute, it changes the deadline to the current time.

2) While testing, the instructors very often want to test an assignment in, say, the submission or review phase, even after the assignment is complete. In order to do this, we need to change several due dates from the User Interface. This process needs to be simplified.

== Expected Resolution ==

1) Fix the date time picker bug in _due_dates.html.erb.

2) Find a more user-friendly [https://en.wikipedia.org/wiki/JQuery JQuery] [https://en.wikipedia.org/wiki/Date_Picker date-time picker] that supports time zones and allow users to define deadline by date and time (hour), if the bug is not fixed in the existing implementation.

3) [https://en.wikipedia.org/wiki/Time_zone Time-zone] should be automatically picked from users timezone preference.

4) Allow users to set all due dates ahead by x days, and the algorithm calculates the exact date and time.

== Previous Implementation and Problems ==

Problem 1:

In the previous implementation for Expertiza, the professors observed that when they wanted to change the date for submission or review deadline for any project or assignment, Expertiza was not able to handle it properly. As in, when the professor tries to change the date - a calendar pops out but then the calendar should point at the date already in the text box.But this was not implemented as it was picking the date of the system and the professor had to go through a cumbersome process to change the date. And even when any date was not selected the field used to get updated by current date and time.

Reason: In the back end , the date picker used was not able to read the date properly from the text box because of date format mismatch. We observed that if we resolve the mismatch in the date formats , this problem could be solved.

[[File:E1654.png]][[File: 2 automatically picks current time.png]]

Problem 2:

When there is a requirement which asks for the professor to change the due dates of assignments or projects, (s)he had to change several dates from the front end one by one which was a very time-consuming and ineffective method.

Reason: In the previous implementation , there was no functionality which allowed the professor to change dates for multiple projects,assignments without manually entering a new date in each text box or selecting each date using the date picker. We observed that we need to add a functionality where the professor can simply select the assignments/projects for which (s)he wants to update the deadline and input the number of days he wants to extend the deadline and by a click of a single button (s)he can change multiple deadlines.

[[File: 3 when clicked without setting a time.png ]][[File:4 extra feature as requested in the mail.png]]

== New Implementation ==

We made two major changes.

Change 1 - We have changed the date picker implementation. As stated, the date picker was not functioning properly. If, while changing the date in the text box , no changes were made, the picker defaulted to the system date instead of the previous date in the text box. The reason for this was a mismatch in the date formats. We made corrections to the code and resolved this mismatch. Now, the date picker is working as per the requirement. It is able to read the date in the text box and there is no mismatch in the date formats.

The code below formats the date in a format which datepicker expects. Which removes the Bug in the system which was causing wierd behavior of the Datepicker

html += '<td align="center" class="due_date_due_at">' + '<input id="datetimepicker_' + element_id +
'" name="assignment_form[due_date][][due_at]" type="text" style="width: 140px;text-align:center;" value="'
+ due_at.substr(0, 16) + '">' + '</td>';
html += '<td align="center" class="due_date_due_at" width="5%">' + '<input id="use_updator_' + element_id +
'" type="checkbox" name="updatorCheck" style="width: 20px">' + '</td>';

Change 2 - We simplified the process of changing the due dates of submissions for multiple projects/assignments. It was accomplished by adding check box in front of each assignment. Suppose there are 5 submissions on the page. And the professor wants to adjust the due dates of assignments 1,3 and 5 by 4 days. Then, he will check the check boxes for submissions 1,3 and 5 and increase from 0 to 4 in the number of days. On clicking save, the dates of all the 3 submissions 1,3 and 5 will be increased by 4. While coding , we have checked for the adjustment in the months and years as well keeping in mind some months have 28,29,30 or 31 days with an year being a [https://en.wikipedia.org/wiki/Leap_year leap year] or not.

[[File:Screenshot from 2016-10-28 18_06_58.png]] [[File:Screenshot from 2016-10-28 18 07 21.png]]

The Code below contains jQuery Functions which are called on click of "Show/Hide Date Updater", "+", and "-" button.

jQuery("#set_rounds").click(function() {
changeReviewRounds();
event.preventDefault(); // Prevent link from following its href
});
//Hide date updater
$("#date_updater_inner").hide();
//This on-click function toggles date updater div
jQuery("#show_date_updater").click(function() {
$("#date_updater_inner").toggle();
});
//The functions below update the required parameter for the assignments that have their check-boxes marked for updation.
//This function adds days to the date
jQuery("#addDays_btn").click(function() {
addDaysOrMonth(1, "days");
event.preventDefault();
});
//This function removes days from the date
jQuery("#subDays_btn").click(function() {
addDaysOrMonth(-1, "days");
event.preventDefault();
});

[[File:Screenshot from 2016-10-28 18 07 34.png]] [[File:Screenshot from 2016-10-28 18 07 54.png]]

The Function Below is a generic Function which can be used to Increment/Decrement Days and Months written in jQuery

function addDaysOrMonth(mul, type) {
var days = parseInt($('#days').val(), 10); // days variable stores the number of days to change the deadline
var months = parseInt($('#months').val(), 10); // days variable stores the number of days to change the deadline
for (var i = 1; i < jQuery('#due_dates_table>tbody>tr:not(#due_date_heading)').length / 2; i++) {
if ($('#use_updator_review_round_' + i).is(':checked')) {
var date = $('#datetimepicker_review_round_' + i).val().split("/");
// curDate reads the date currently in the field
var curDate = new Date(parseInt(date[0], 10), parseInt(date[1], 10) - 1, parseInt(date[2].split(" ")[0], 10));
if (type == "days") { //checks if type is date then sets dates
curDate.setDate(curDate.getDate() + (days * mul)); //sets the date
} else {
curDate.setMonth(curDate.getMonth() + (months * mul)); //sets the months
}
$("#datetimepicker_review_round_" + i).val(curDate.getFullYear() + "/" + (curDate.getMonth() + 1) + "/" + curDate.getDate() + " " + date[2].split(" ")[1]);
}
if ($('#use_updator_submission_round_' + i).is(':checked')) {
var date = $('#datetimepicker_submission_round_' + i).val().split("/");
var curDate = new Date(parseInt(date[0], 10), parseInt(date[1], 10) - 1, parseInt(date[2].split(" ")[0], 10));
if (type == "days") {
curDate.setDate(curDate.getDate() + (days * mul));
} else {
curDate.setMonth(curDate.getMonth() + (months * mul));
}
$("#datetimepicker_submission_round_" + i).val(curDate.getFullYear() + "/" + (curDate.getMonth() + 1) + "/" + curDate.getDate() + " " + date[2].split(" ")[1]);
}
}
}

[[File:Screenshot from 2016-10-28 18 08 05.png]]

==Testing from UI==

The changes made by us in the code can be tested using the below tests :

1. Navigate to Editing Assignments page with the following URL after logging in:

http://0.0.0.0:3000/assignments/772/edit ( Project deployment in progress )

Expectation: page renders properly.

2. After logging in as an instructor, Perform the following: change the due dates for an assignment. Go to the text field to change the dates, and without changing the date click on any whitespace. In the current production version of expertiza, the second action resulted in the current date and time being filled in the date and time section.

Expectation: Dates can be easily assigned and the system does not default to a standard on leaving it blank.

3. For incrementing/decrementing the number of days allotted for an assignment, click on the show/hide date updater button to reveal the updater widget.
check mark all those assignments that need to be updated and enter the number of days in the text field.
Press Plus to increase and Minus to decrease the number of days allotted for the assignments.

Expectation: Dates are updated as per requirement, month and year rollovers are taken care of.

== Pull Request ==
Here is our [https://github.com/expertiza/expertiza/pull/810 pull request]. In the link you can see all the changes made in the back end made to fix the date picker bug and implement additional functionalities to update deadlines.

== References ==

1 http://wiki.expertiza.ncsu.edu/index.php/CSC/ECE_517_Fall_2015/oss_E1553_AAJ

2 http://www.w3schools.com/jquery/

3 http://www.w3schools.com/js/

CSC/ECE 517 Fall 2016/E1654. Improve date-picker and deadlines

2016-10-29T04:49:59Z

Dssathe: /* Pull Request */

This wiki page is for the description of changes made under E1654/Improve date-picker and deadlines OSS assignment for Fall 2016, CSC/ECE 517.

== About Expertiza ==
[http://wiki.expertiza.ncsu.edu/index.php/Main_Page#Expertiza Expertiza] is a [https://en.wikipedia.org/wiki/Ruby_on_Rails Ruby on Rails] application made by the joint contribution of Professors and Students of [https://en.wikipedia.org/wiki/North_Carolina_State_University North Carolina State University]. It is used by the Professor ,Teaching Assistants and students of a particular course to manage their respective responsibilities with respect to that course. Professor can enlist a new assignment or project, set/update the deadline to submit it , grant publishing rights to a user and more. The Teaching Assistants can including other things update the review scores of the students, view the submissions etc. The students can view information about all the assignments due and submitted.Students can form teams in Expertiza to work on various projects and assignments.Students can also review other students' submissions and the performance of their teammates. Expertiza supports submissions across various document types, including the URLs and wiki pages.

== Problem Statement ==

The [https://en.wikipedia.org/wiki/North_Carolina_State_University Date-picker] allows the instructor to set deadlines for the assignments and peer reviews.

1) The current date-picker doesn't let you change dates easily. When you try to edit a deadline, Unless you spell it out to the minute, it changes the deadline to the current time.

2) While testing, the instructors very often want to test an assignment in, say, the submission or review phase, even after the assignment is complete. In order to do this, we need to change several due dates from the User Interface. This process needs to be simplified.

== Expected Resolution ==

1) Fix the date time picker bug in _due_dates.html.erb.

2) Find a more user-friendly [https://en.wikipedia.org/wiki/JQuery JQuery] [https://en.wikipedia.org/wiki/Date_Picker date-time picker] that supports time zones and allow users to define deadline by date and time (hour), if the bug is not fixed in the existing implementation.

3) [https://en.wikipedia.org/wiki/Time_zone Time-zone] should be automatically picked from users timezone preference.

4) Allow users to set all due dates ahead by x days, and the algorithm calculates the exact date and time.

== Previous Implementation and Problems ==

Problem 1:

In the previous implementation for Expertiza, the professors observed that when they wanted to change the date for submission or review deadline for any project or assignment, Expertiza was not able to handle it properly. As in, when the professor tries to change the date - a calendar pops out but then the calendar should point at the date already in the text box.But this was not implemented as it was picking the date of the system and the professor had to go through a cumbersome process to change the date. And even when any date was not selected the field used to get updated by current date and time.

Reason: In the back end , the date picker used was not able to read the date properly from the text box because of date format mismatch. We observed that if we resolve the mismatch in the date formats , this problem could be solved.

[[File:E1654.png]][[File: 2 automatically picks current time.png]]

Problem 2:

When there is a requirement which asks for the professor to change the due dates of assignments or projects, (s)he had to change several dates from the front end one by one which was a very time-consuming and ineffective method.

Reason: In the previous implementation , there was no functionality which allowed the professor to change dates for multiple projects,assignments without manually entering a new date in each text box or selecting each date using the date picker. We observed that we need to add a functionality where the professor can simply select the assignments/projects for which (s)he wants to update the deadline and input the number of days he wants to extend the deadline and by a click of a single button (s)he can change multiple deadlines.

[[File: 3 when clicked without setting a time.png ]][[File:4 extra feature as requested in the mail.png]]

== New Implementation ==

We made two major changes.

Change 1 - We have changed the date picker implementation. As stated, the date picker was not functioning properly. If, while changing the date in the text box , no changes were made, the picker defaulted to the system date instead of the previous date in the text box. The reason for this was a mismatch in the date formats. We made corrections to the code and resolved this mismatch. Now, the date picker is working as per the requirement. It is able to read the date in the text box and there is no mismatch in the date formats.

The code below formats the date in a format which datepicker expects. Which removes the Bug in the system which was causing wierd behavior of the Datepicker

html += '<td align="center" class="due_date_due_at">' + '<input id="datetimepicker_' + element_id +
'" name="assignment_form[due_date][][due_at]" type="text" style="width: 140px;text-align:center;" value="'
+ due_at.substr(0, 16) + '">' + '</td>';
html += '<td align="center" class="due_date_due_at" width="5%">' + '<input id="use_updator_' + element_id +
'" type="checkbox" name="updatorCheck" style="width: 20px">' + '</td>';

Change 2 - We simplified the process of changing the due dates of submissions for multiple projects/assignments. It was accomplished by adding check box in front of each assignment. Suppose there are 5 submissions on the page. And the professor wants to adjust the due dates of assignments 1,3 and 5 by 4 days. Then, he will check the check boxes for submissions 1,3 and 5 and increase from 0 to 4 in the number of days. On clicking save, the dates of all the 3 submissions 1,3 and 5 will be increased by 4. While coding , we have checked for the adjustment in the months and years as well keeping in mind some months have 28,29,30 or 31 days with an year being a [https://en.wikipedia.org/wiki/Leap_year leap year] or not.

[[File:Screenshot from 2016-10-28 18_06_58.png]] [[File:Screenshot from 2016-10-28 18 07 21.png]]

The Code below contains jQuery Functions which are called on click of "Show/Hide Date Updater", "+", and "-" button.

jQuery("#set_rounds").click(function() {
changeReviewRounds();
event.preventDefault(); // Prevent link from following its href
});
//Hide date updater
$("#date_updater_inner").hide();
//This on-click function toggles date updater div
jQuery("#show_date_updater").click(function() {
$("#date_updater_inner").toggle();
});
//The functions below update the required parameter for the assignments that have their check-boxes marked for updation.
//This function adds days to the date
jQuery("#addDays_btn").click(function() {
addDaysOrMonth(1, "days");
event.preventDefault();
});
//This function removes days from the date
jQuery("#subDays_btn").click(function() {
addDaysOrMonth(-1, "days");
event.preventDefault();
});

[[File:Screenshot from 2016-10-28 18 07 34.png]] [[File:Screenshot from 2016-10-28 18 07 54.png]]

The Function Below is a generic Function which can be used to Increment/Decrement Days and Months written in jQuery

function addDaysOrMonth(mul, type) {
var days = parseInt($('#days').val(), 10); // days variable stores the number of days to change the deadline
var months = parseInt($('#months').val(), 10); // days variable stores the number of days to change the deadline
for (var i = 1; i < jQuery('#due_dates_table>tbody>tr:not(#due_date_heading)').length / 2; i++) {
if ($('#use_updator_review_round_' + i).is(':checked')) {
var date = $('#datetimepicker_review_round_' + i).val().split("/");
// curDate reads the date currently in the field
var curDate = new Date(parseInt(date[0], 10), parseInt(date[1], 10) - 1, parseInt(date[2].split(" ")[0], 10));
if (type == "days") { //checks if type is date then sets dates
curDate.setDate(curDate.getDate() + (days * mul)); //sets the date
} else {
curDate.setMonth(curDate.getMonth() + (months * mul)); //sets the months
}
$("#datetimepicker_review_round_" + i).val(curDate.getFullYear() + "/" + (curDate.getMonth() + 1) + "/" + curDate.getDate() + " " + date[2].split(" ")[1]);
}
if ($('#use_updator_submission_round_' + i).is(':checked')) {
var date = $('#datetimepicker_submission_round_' + i).val().split("/");
var curDate = new Date(parseInt(date[0], 10), parseInt(date[1], 10) - 1, parseInt(date[2].split(" ")[0], 10));
if (type == "days") {
curDate.setDate(curDate.getDate() + (days * mul));
} else {
curDate.setMonth(curDate.getMonth() + (months * mul));
}
$("#datetimepicker_submission_round_" + i).val(curDate.getFullYear() + "/" + (curDate.getMonth() + 1) + "/" + curDate.getDate() + " " + date[2].split(" ")[1]);
}
}
}

[[File:Screenshot from 2016-10-28 18 08 05.png]]

==Testing from UI==

The changes made by us in the code can be tested using the below tests :

1. Navigate to Editing Assignments page with the following URL after logging in:

http://0.0.0.0:3000/assignments/772/edit

Expectation: page renders properly.

2. After logging in as an instructor, Perform the following: change the due dates for an assignment. Go to the text field to change the dates, and without changing the date click on any whitespace. In the current production version of expertiza, the second action resulted in the current date and time being filled in the date and time section.

Expectation: Dates can be easily assigned and the system does not default to a standard on leaving it blank.

3. For incrementing/decrementing the number of days allotted for an assignment, click on the show/hide date updater button to reveal the updater widget.
check mark all those assignments that need to be updated and enter the number of days in the text field.
Press Plus to increase and Minus to decrease the number of days allotted for the assignments.

Expectation: Dates are updated as per requirement, month and year rollovers are taken care of.

== Pull Request ==
Here is our [https://github.com/expertiza/expertiza/pull/810 pull request]. In the link you can see all the changes made in the back end made to fix the date picker bug and implement additional functionalities to update deadlines.

== References ==

1 http://wiki.expertiza.ncsu.edu/index.php/CSC/ECE_517_Fall_2015/oss_E1553_AAJ

2 http://www.w3schools.com/jquery/

3 http://www.w3schools.com/js/

CSC/ECE 517 Fall 2016/E1654. Improve date-picker and deadlines

2016-10-29T03:11:12Z

Dssathe: /* New Implementation */

This wiki page is for the description of changes made under E1654/Improve date-picker and deadlines OSS assignment for Fall 2016, CSC/ECE 517.

== About Expertiza ==
[http://wiki.expertiza.ncsu.edu/index.php/Main_Page#Expertiza Expertiza] is a [https://en.wikipedia.org/wiki/Ruby_on_Rails Ruby on Rails] application made by the joint contribution of Professors and Students of [https://en.wikipedia.org/wiki/North_Carolina_State_University North Carolina State University]. It is used by the Professor ,Teaching Assistants and students of a particular course to manage their respective responsibilities with respect to that course. Professor can enlist a new assignment or project, set/update the deadline to submit it , grant publishing rights to a user and more. The Teaching Assistants can including other things update the review scores of the students, view the submissions etc. The students can view information about all the assignments due and submitted.Students can form teams in Expertiza to work on various projects and assignments.Students can also review other students' submissions and the performance of their teammates. Expertiza supports submissions across various document types, including the URLs and wiki pages.

== Problem Statement ==

The [https://en.wikipedia.org/wiki/North_Carolina_State_University Date-picker] allows the instructor to set deadlines for the assignments and peer reviews.

1) The current date-picker doesn't let you change dates easily. When you try to edit a deadline, Unless you spell it out to the minute, it changes the deadline to the current time.

2) While testing, the instructors very often want to test an assignment in, say, the submission or review phase, even after the assignment is complete. In order to do this, we need to change several due dates from the User Interface. This process needs to be simplified.

== Expected Resolution ==

1) Fix the date time picker bug in _due_dates.html.erb.

2) Find a more user-friendly [https://en.wikipedia.org/wiki/JQuery JQuery] [https://en.wikipedia.org/wiki/Date_Picker date-time picker] that supports time zones and allow users to define deadline by date and time (hour), if the bug is not fixed in the existing implementation.

3) [https://en.wikipedia.org/wiki/Time_zone Time-zone] should be automatically picked from users timezone preference.

4) Allow users to set all due dates ahead by x days, and the algorithm calculates the exact date and time.

== Previous Implementation and Problems ==

Problem 1:

In the previous implementation for Expertiza, the professors observed that when they wanted to change the date for submission or review deadline for any project or assignment, Expertiza was not able to handle it properly. As in, when the professor tries to change the date - a calendar pops out but then the calendar should point at the date already in the text box.But this was not implemented as it was picking the date of the system and the professor had to go through a cumbersome process to change the date. And even when any date was not selected the field used to get updated by current date and time.

Reason: In the back end , the date picker used was not able to read the date properly from the text box because of date format mismatch. We observed that if we resolve the mismatch in the date formats , this problem could be solved.

[[File:E1654.png]][[File: 2 automatically picks current time.png]]

Problem 2:

When there is a requirement which asks for the professor to change the due dates of assignments or projects, (s)he had to change several dates from the front end one by one which was a very time-consuming and ineffective method.

Reason: In the previous implementation , there was no functionality which allowed the professor to change dates for multiple projects,assignments without manually entering a new date in each text box or selecting each date using the date picker. We observed that we need to add a functionality where the professor can simply select the assignments/projects for which (s)he wants to update the deadline and input the number of days he wants to extend the deadline and by a click of a single button (s)he can change multiple deadlines.

[[File: 3 when clicked without setting a time.png ]][[File:4 extra feature as requested in the mail.png]]

== New Implementation ==

We made two major changes.

Change 1 - We have changed the date picker implementation. As stated, the date picker was not functioning properly. If, while changing the date in the text box , no changes were made, the picker defaulted to the system date instead of the previous date in the text box. The reason for this was a mismatch in the date formats. We made corrections to the code and resolved this mismatch. Now, the date picker is working as per the requirement. It is able to read the date in the text box and there is no mismatch in the date formats.

The code below formats the date in a format which datepicker expects. Which removes the Bug in the system which was causing wierd behavior of the Datepicker

html += '<td align="center" class="due_date_due_at">' + '<input id="datetimepicker_' + element_id +
'" name="assignment_form[due_date][][due_at]" type="text" style="width: 140px;text-align:center;" value="'
+ due_at.substr(0, 16) + '">' + '</td>';
html += '<td align="center" class="due_date_due_at" width="5%">' + '<input id="use_updator_' + element_id +
'" type="checkbox" name="updatorCheck" style="width: 20px">' + '</td>';

Change 2 - We simplified the process of changing the due dates of submissions for multiple projects/assignments. It was accomplished by adding check box in front of each assignment. Suppose there are 5 submissions on the page. And the professor wants to adjust the due dates of assignments 1,3 and 5 by 4 days. Then, he will check the check boxes for submissions 1,3 and 5 and increase from 0 to 4 in the number of days. On clicking save, the dates of all the 3 submissions 1,3 and 5 will be increased by 4. While coding , we have checked for the adjustment in the months and years as well keeping in mind some months have 28,29,30 or 31 days with an year being a [https://en.wikipedia.org/wiki/Leap_year leap year] or not.

[[File:Screenshot from 2016-10-28 18_06_58.png]] [[File:Screenshot from 2016-10-28 18 07 21.png]]

The Code below contains jQuery Functions which are called on click of "Show/Hide Date Updater", "+", and "-" button.

jQuery("#set_rounds").click(function() {
changeReviewRounds();
event.preventDefault(); // Prevent link from following its href
});
//Hide date updater
$("#date_updater_inner").hide();
//This on-click function toggles date updater div
jQuery("#show_date_updater").click(function() {
$("#date_updater_inner").toggle();
});
//The functions below update the required parameter for the assignments that have their check-boxes marked for updation.
//This function adds days to the date
jQuery("#addDays_btn").click(function() {
addDaysOrMonth(1, "days");
event.preventDefault();
});
//This function removes days from the date
jQuery("#subDays_btn").click(function() {
addDaysOrMonth(-1, "days");
event.preventDefault();
});

[[File:Screenshot from 2016-10-28 18 07 34.png]] [[File:Screenshot from 2016-10-28 18 07 54.png]]

The Function Below is a generic Function which can be used to Increment/Decrement Days and Months written in jQuery

function addDaysOrMonth(mul, type) {
var days = parseInt($('#days').val(), 10); // days variable stores the number of days to change the deadline
var months = parseInt($('#months').val(), 10); // days variable stores the number of days to change the deadline
for (var i = 1; i < jQuery('#due_dates_table>tbody>tr:not(#due_date_heading)').length / 2; i++) {
if ($('#use_updator_review_round_' + i).is(':checked')) {
var date = $('#datetimepicker_review_round_' + i).val().split("/");
// curDate reads the date currently in the field
var curDate = new Date(parseInt(date[0], 10), parseInt(date[1], 10) - 1, parseInt(date[2].split(" ")[0], 10));
if (type == "days") { //checks if type is date then sets dates
curDate.setDate(curDate.getDate() + (days * mul)); //sets the date
} else {
curDate.setMonth(curDate.getMonth() + (months * mul)); //sets the months
}
$("#datetimepicker_review_round_" + i).val(curDate.getFullYear() + "/" + (curDate.getMonth() + 1) + "/" + curDate.getDate() + " " + date[2].split(" ")[1]);
}
if ($('#use_updator_submission_round_' + i).is(':checked')) {
var date = $('#datetimepicker_submission_round_' + i).val().split("/");
var curDate = new Date(parseInt(date[0], 10), parseInt(date[1], 10) - 1, parseInt(date[2].split(" ")[0], 10));
if (type == "days") {
curDate.setDate(curDate.getDate() + (days * mul));
} else {
curDate.setMonth(curDate.getMonth() + (months * mul));
}
$("#datetimepicker_submission_round_" + i).val(curDate.getFullYear() + "/" + (curDate.getMonth() + 1) + "/" + curDate.getDate() + " " + date[2].split(" ")[1]);
}
}
}

[[File:Screenshot from 2016-10-28 18 08 05.png]]

==Testing from UI==

The changes made by us in the code can be tested using the below tests :

1. Navigate to Editing Assignments page with the following URL after logging in:

http://0.0.0.0:3000/assignments/772/edit

Expectation: page renders properly.

2. After logging in as an instructor, Perform the following: change the due dates for an assignment. Go to the text field to change the dates, and without changing the date click on any whitespace. In the current production version of expertiza, the second action resulted in the current date and time being filled in the date and time section.

Expectation: Dates can be easily assigned and the system does not default to a standard on leaving it blank.

3. For incrementing/decrementing the number of days allotted for an assignment, click on the show/hide date updater button to reveal the updater widget.
check mark all those assignments that need to be updated and enter the number of days in the text field.
Press Plus to increase and Minus to decrease the number of days allotted for the assignments.

Expectation: Dates are updated as per requirement, month and year rollovers are taken care of.

== Pull Request ==
Here is our [https://github.com/expertiza/expertiza/pull/760 pull request]. In the link you can see all the changes made in the back end made to fix the date picker bug and implement additional functionalities to update deadlines.

== References ==

1 http://wiki.expertiza.ncsu.edu/index.php/CSC/ECE_517_Fall_2015/oss_E1553_AAJ

2 http://www.w3schools.com/jquery/

3 http://www.w3schools.com/js/

CSC/ECE 517 Fall 2016/E1654. Improve date-picker and deadlines

2016-10-29T03:09:55Z

Dssathe: /* New Implementation */

This wiki page is for the description of changes made under E1654/Improve date-picker and deadlines OSS assignment for Fall 2016, CSC/ECE 517.

== About Expertiza ==
[http://wiki.expertiza.ncsu.edu/index.php/Main_Page#Expertiza Expertiza] is a [https://en.wikipedia.org/wiki/Ruby_on_Rails Ruby on Rails] application made by the joint contribution of Professors and Students of [https://en.wikipedia.org/wiki/North_Carolina_State_University North Carolina State University]. It is used by the Professor ,Teaching Assistants and students of a particular course to manage their respective responsibilities with respect to that course. Professor can enlist a new assignment or project, set/update the deadline to submit it , grant publishing rights to a user and more. The Teaching Assistants can including other things update the review scores of the students, view the submissions etc. The students can view information about all the assignments due and submitted.Students can form teams in Expertiza to work on various projects and assignments.Students can also review other students' submissions and the performance of their teammates. Expertiza supports submissions across various document types, including the URLs and wiki pages.

== Problem Statement ==

The [https://en.wikipedia.org/wiki/North_Carolina_State_University Date-picker] allows the instructor to set deadlines for the assignments and peer reviews.

1) The current date-picker doesn't let you change dates easily. When you try to edit a deadline, Unless you spell it out to the minute, it changes the deadline to the current time.

2) While testing, the instructors very often want to test an assignment in, say, the submission or review phase, even after the assignment is complete. In order to do this, we need to change several due dates from the User Interface. This process needs to be simplified.

== Expected Resolution ==

1) Fix the date time picker bug in _due_dates.html.erb.

2) Find a more user-friendly [https://en.wikipedia.org/wiki/JQuery JQuery] [https://en.wikipedia.org/wiki/Date_Picker date-time picker] that supports time zones and allow users to define deadline by date and time (hour), if the bug is not fixed in the existing implementation.

3) [https://en.wikipedia.org/wiki/Time_zone Time-zone] should be automatically picked from users timezone preference.

4) Allow users to set all due dates ahead by x days, and the algorithm calculates the exact date and time.

== Previous Implementation and Problems ==

Problem 1:

In the previous implementation for Expertiza, the professors observed that when they wanted to change the date for submission or review deadline for any project or assignment, Expertiza was not able to handle it properly. As in, when the professor tries to change the date - a calendar pops out but then the calendar should point at the date already in the text box.But this was not implemented as it was picking the date of the system and the professor had to go through a cumbersome process to change the date. And even when any date was not selected the field used to get updated by current date and time.

Reason: In the back end , the date picker used was not able to read the date properly from the text box because of date format mismatch. We observed that if we resolve the mismatch in the date formats , this problem could be solved.

[[File:E1654.png]][[File: 2 automatically picks current time.png]]

Problem 2:

When there is a requirement which asks for the professor to change the due dates of assignments or projects, (s)he had to change several dates from the front end one by one which was a very time-consuming and ineffective method.

Reason: In the previous implementation , there was no functionality which allowed the professor to change dates for multiple projects,assignments without manually entering a new date in each text box or selecting each date using the date picker. We observed that we need to add a functionality where the professor can simply select the assignments/projects for which (s)he wants to update the deadline and input the number of days he wants to extend the deadline and by a click of a single button (s)he can change multiple deadlines.

[[File: 3 when clicked without setting a time.png ]][[File:4 extra feature as requested in the mail.png]]

== New Implementation ==

We made two major changes.

Change 1 - We have changed the date picker implementation. As stated, the date picker was not functioning properly. If, while changing the date in the text box , no changes were made, the picker defaulted to the system date instead of the previous date in the text box. The reason for this was a mismatch in the date formats. We made corrections to the code and resolved this mismatch. Now, the date picker is working as per the requirement. It is able to read the date in the text box and there is no mismatch in the date formats.

The code below formats the date in a format which datepicker expects. Which removes the Bug in the system which was causing wierd behavior of the Datepicker

html += '<td align="center" class="due_date_due_at">' + '<input id="datetimepicker_' + element_id +
'" name="assignment_form[due_date][][due_at]" type="text" style="width: 140px;text-align:center;" value="'
+ due_at.substr(0, 16) + '">' + '</td>';
html += '<td align="center" class="due_date_due_at" width="5%">' + '<input id="use_updator_' + element_id +
'" type="checkbox" name="updatorCheck" style="width: 20px">' + '</td>';

Change 2 - We simplified the process of changing the due dates of submissions for multiple projects/assignments. It was accomplished by adding check box in front of each assignment. Suppose there are 5 submissions on the page. And the professor wants to adjust the due dates of assignments 1,3 and 5 by 4 days. Then, he will check the check boxes for submissions 1,3 and 5 and increase from 0 to 4 in the number of days. On clicking save, the dates of all the 3 submissions 1,3 and 5 will be increased by 4. While coding , we have checked for the adjustment in the months and years as well keeping in mind some months have 28,29,30 or 31 days with an year being a [https://en.wikipedia.org/wiki/Leap_year leap year] or not.

[[File:Screenshot from 2016-10-28 18_06_58.png]] [[File:Screenshot from 2016-10-28 18 07 21.png]]

The Code below contains jQuery Functions which are called on click of "Show/Hide Date Updater", "+", and "-" button.

jQuery("#set_rounds").click(function() {
changeReviewRounds();
event.preventDefault(); // Prevent link from following its href
});
//Hide date updater
$("#date_updater_inner").hide();
//This on-click function toggles date updater div
jQuery("#show_date_updater").click(function() {
$("#date_updater_inner").toggle();
});
//The functions below update the required parameter for the assignments that have their check-boxes marked for updation.
//This function adds days to the date
jQuery("#addDays_btn").click(function() {
addDaysOrMonth(1, "days");
event.preventDefault();
});
//This function removes days from the date
jQuery("#subDays_btn").click(function() {
addDaysOrMonth(-1, "days");
event.preventDefault();
});

[[File:Screenshot from 2016-10-28 18 07 34.png]] [[File:Screenshot from 2016-10-28 18 07 54.png]]

The Function Below is a generic Function which can be used to Increment/Decrement Days and Months written in jQuery

function addDaysOrMonth(mul, type) {
var days = parseInt($('#days').val(), 10); // days variable stores the number of days to change the deadline
var months = parseInt($('#months').val(), 10); // days variable stores the number of days to change the deadline
for (var i = 1; i < jQuery('#due_dates_table>tbody>tr:not(#due_date_heading)').length / 2; i++) {
if ($('#use_updator_review_round_' + i).is(':checked')) {
var date = $('#datetimepicker_review_round_' + i).val().split("/");
// curDate reads the date currently in the field
var curDate = new Date(parseInt(date[0], 10), parseInt(date[1], 10) - 1, parseInt(date[2].split(" ")[0], 10));
if (type == "days") { //checks if type is date then sets dates
curDate.setDate(curDate.getDate() + (days * mul)); //sets the date
} else {
curDate.setMonth(curDate.getMonth() + (months * mul)); //sets the months
}
$("#datetimepicker_review_round_" + i).val(curDate.getFullYear() + "/" + (curDate.getMonth() + 1) + "/" + curDate.getDate() + " " + date[2].split(" ")[1]);
}
if ($('#use_updator_submission_round_' + i).is(':checked')) {
var date = $('#datetimepicker_submission_round_' + i).val().split("/");
var curDate = new Date(parseInt(date[0], 10), parseInt(date[1], 10) - 1, parseInt(date[2].split(" ")[0], 10));
if (type == "days") {
curDate.setDate(curDate.getDate() + (days * mul));
} else {
curDate.setMonth(curDate.getMonth() + (months * mul));
}
$("#datetimepicker_submission_round_" + i).val(curDate.getFullYear() + "/" + (curDate.getMonth() + 1) + "/" + curDate.getDate() + " " + date[2].split(" ")[1]);
}
}
}

[[File:Screenshot from 2016-10-28 18 08 05.png]]

==Testing from UI==

The changes made by us in the code can be tested using the below tests :

1. Navigate to Editing Assignments page with the following URL after logging in:

http://0.0.0.0:3000/assignments/772/edit

Expectation: page renders properly.

2. After logging in as an instructor, Perform the following: change the due dates for an assignment. Go to the text field to change the dates, and without changing the date click on any whitespace. In the current production version of expertiza, the second action resulted in the current date and time being filled in the date and time section.

Expectation: Dates can be easily assigned and the system does not default to a standard on leaving it blank.

3. For incrementing/decrementing the number of days allotted for an assignment, click on the show/hide date updater button to reveal the updater widget.
check mark all those assignments that need to be updated and enter the number of days in the text field.
Press Plus to increase and Minus to decrease the number of days allotted for the assignments.

Expectation: Dates are updated as per requirement, month and year rollovers are taken care of.

== Pull Request ==
Here is our [https://github.com/expertiza/expertiza/pull/760 pull request]. In the link you can see all the changes made in the back end made to fix the date picker bug and implement additional functionalities to update deadlines.

== References ==

1 http://wiki.expertiza.ncsu.edu/index.php/CSC/ECE_517_Fall_2015/oss_E1553_AAJ

2 http://www.w3schools.com/jquery/

3 http://www.w3schools.com/js/

CSC/ECE 517 Fall 2016/E1654. Improve date-picker and deadlines

2016-10-29T02:58:42Z

Dssathe: /* Previous Implementation and Problems */

This wiki page is for the description of changes made under E1654/Improve date-picker and deadlines OSS assignment for Fall 2016, CSC/ECE 517.

== About Expertiza ==
[http://wiki.expertiza.ncsu.edu/index.php/Main_Page#Expertiza Expertiza] is a [https://en.wikipedia.org/wiki/Ruby_on_Rails Ruby on Rails] application made by the joint contribution of Professors and Students of [https://en.wikipedia.org/wiki/North_Carolina_State_University North Carolina State University]. It is used by the Professor ,Teaching Assistants and students of a particular course to manage their respective responsibilities with respect to that course. Professor can enlist a new assignment or project, set/update the deadline to submit it , grant publishing rights to a user and more. The Teaching Assistants can including other things update the review scores of the students, view the submissions etc. The students can view information about all the assignments due and submitted.Students can form teams in Expertiza to work on various projects and assignments.Students can also review other students' submissions and the performance of their teammates. Expertiza supports submissions across various document types, including the URLs and wiki pages.

== Problem Statement ==

The [https://en.wikipedia.org/wiki/North_Carolina_State_University Date-picker] allows the instructor to set deadlines for the assignments and peer reviews.

1) The current date-picker doesn't let you change dates easily. When you try to edit a deadline, Unless you spell it out to the minute, it changes the deadline to the current time.

2) While testing, the instructors very often want to test an assignment in, say, the submission or review phase, even after the assignment is complete. In order to do this, we need to change several due dates from the User Interface. This process needs to be simplified.

== Expected Resolution ==

1) Fix the date time picker bug in _due_dates.html.erb.

2) Find a more user-friendly [https://en.wikipedia.org/wiki/JQuery JQuery] [https://en.wikipedia.org/wiki/Date_Picker date-time picker] that supports time zones and allow users to define deadline by date and time (hour), if the bug is not fixed in the existing implementation.

3) [https://en.wikipedia.org/wiki/Time_zone Time-zone] should be automatically picked from users timezone preference.

4) Allow users to set all due dates ahead by x days, and the algorithm calculates the exact date and time.

== Previous Implementation and Problems ==

Problem 1:

In the previous implementation for Expertiza, the professors observed that when they wanted to change the date for submission or review deadline for any project or assignment, Expertiza was not able to handle it properly. As in, when the professor tries to change the date - a calendar pops out but then the calendar should point at the date already in the text box.But this was not implemented as it was picking the date of the system and the professor had to go through a cumbersome process to change the date. And even when any date was not selected the field used to get updated by current date and time.

Reason: In the back end , the date picker used was not able to read the date properly from the text box because of date format mismatch. We observed that if we resolve the mismatch in the date formats , this problem could be solved.

[[File:E1654.png]][[File: 2 automatically picks current time.png]]

Problem 2:

When there is a requirement which asks for the professor to change the due dates of assignments or projects, (s)he had to change several dates from the front end one by one which was a very time-consuming and ineffective method.

Reason: In the previous implementation , there was no functionality which allowed the professor to change dates for multiple projects,assignments without manually entering a new date in each text box or selecting each date using the date picker. We observed that we need to add a functionality where the professor can simply select the assignments/projects for which (s)he wants to update the deadline and input the number of days he wants to extend the deadline and by a click of a single button (s)he can change multiple deadlines.

[[File: 3 when clicked without setting a time.png ]][[File:4 extra feature as requested in the mail.png]]

== New Implementation ==

We made two major changes.

Change 1 - We have changed the date picker implementation. As stated, the date picker was not functioning properly. If, while changing the date in the text box , no changes were made, the picker defaulted to the system date instead of the previous date in the text box. The reason for this was a mismatch in the date formats. We made corrections to the code and resolved this mismatch. Now, the date picker is working as per the requirement. It is able to read the date in the text box and there is no mismatch in the date formats.

html += '<td align="center" class="due_date_due_at">' + '<input id="datetimepicker_' + element_id +
'" name="assignment_form[due_date][][due_at]" type="text" style="width: 140px;text-align:center;" value="'
+ due_at.substr(0, 16) + '">' + '</td>';
html += '<td align="center" class="due_date_due_at" width="5%">' + '<input id="use_updator_' + element_id +
'" type="checkbox" name="updatorCheck" style="width: 20px">' + '</td>';

Change 2 - We simplified the process of changing the due dates of submissions for multiple projects/assignments. It was accomplished by adding check box in front of each assignment. Suppose there are 5 submissions on the page. And the professor wants to adjust the due dates of assignments 1,3 and 5 by 4 days. Then, he will check the check boxes for submissions 1,3 and 5 and increase from 0 to 4 in the number of days. On clicking save, the dates of all the 3 submissions 1,3 and 5 will be increased by 4. While coding , we have checked for the adjustment in the months and years as well keeping in mind some months have 28,29,30 or 31 days with an year being a [https://en.wikipedia.org/wiki/Leap_year leap year] or not.

jQuery("#set_rounds").click(function() {
changeReviewRounds();
event.preventDefault(); // Prevent link from following its href
});
//E1654. Improve date-picker and deadlines Code change starts
//Hide date updater
$("#date_updater_inner").hide();
//This on-click function toggles date updater div
jQuery("#show_date_updater").click(function() {
$("#date_updater_inner").toggle();
});
//The functions below update the required parameter for the assignments that have their check-boxes marked for updation.
//This function adds days to the date
jQuery("#addDays_btn").click(function() {
addDaysOrMonth(1, "days");
event.preventDefault();
});
//This function removes days from the date
jQuery("#subDays_btn").click(function() {
addDaysOrMonth(-1, "days");
event.preventDefault();
});

[[File:Screenshot from 2016-10-28 18_06_58.png]] [[File:Screenshot from 2016-10-28 18 07 21.png]]

function addDaysOrMonth(mul, type) {
var days = parseInt($('#days').val(), 10); // days variable stores the number of days to change the deadline
var months = parseInt($('#months').val(), 10); // days variable stores the number of days to change the deadline
for (var i = 1; i < jQuery('#due_dates_table>tbody>tr:not(#due_date_heading)').length / 2; i++) {
if ($('#use_updator_review_round_' + i).is(':checked')) {
var date = $('#datetimepicker_review_round_' + i).val().split("/");
// curDate reads the date currently in the field
var curDate = new Date(parseInt(date[0], 10), parseInt(date[1], 10) - 1, parseInt(date[2].split(" ")[0], 10));
if (type == "days") { //checks if type is date then sets dates
curDate.setDate(curDate.getDate() + (days * mul)); //sets the date
} else {
curDate.setMonth(curDate.getMonth() + (months * mul)); //sets the months
}
$("#datetimepicker_review_round_" + i).val(curDate.getFullYear() + "/" + (curDate.getMonth() + 1) + "/" + curDate.getDate() + " " + date[2].split(" ")[1]);
}
if ($('#use_updator_submission_round_' + i).is(':checked')) {
var date = $('#datetimepicker_submission_round_' + i).val().split("/");
var curDate = new Date(parseInt(date[0], 10), parseInt(date[1], 10) - 1, parseInt(date[2].split(" ")[0], 10));
if (type == "days") {
curDate.setDate(curDate.getDate() + (days * mul));
} else {
curDate.setMonth(curDate.getMonth() + (months * mul));
}
$("#datetimepicker_submission_round_" + i).val(curDate.getFullYear() + "/" + (curDate.getMonth() + 1) + "/" + curDate.getDate() + " " + date[2].split(" ")[1]);
}
}
}

[[File:Screenshot from 2016-10-28 18 07 34.png]] [[File:Screenshot from 2016-10-28 18 07 54.png]]

[[File:Screenshot from 2016-10-28 18 08 05.png]]

==Testing from UI==

The changes made by us in the code can be tested using the below tests :

1. Navigate to Editing Assignments page with the following URL after logging in:

http://0.0.0.0:3000/assignments/772/edit

Expectation: page renders properly.

2. After logging in as an instructor, Perform the following: change the due dates for an assignment. Go to the text field to change the dates, and without changing the date click on any whitespace. In the current production version of expertiza, the second action resulted in the current date and time being filled in the date and time section.

Expectation: Dates can be easily assigned and the system does not default to a standard on leaving it blank.

3. For incrementing/decrementing the number of days allotted for an assignment, click on the show/hide date updater button to reveal the updater widget.
check mark all those assignments that need to be updated and enter the number of days in the text field.
Press Plus to increase and Minus to decrease the number of days allotted for the assignments.

Expectation: Dates are updated as per requirement, month and year rollovers are taken care of.

== Pull Request ==
Here is our [https://github.com/expertiza/expertiza/pull/760 pull request]. In the link you can see all the changes made in the back end made to fix the date picker bug and implement additional functionalities to update deadlines.

== References ==

1 http://wiki.expertiza.ncsu.edu/index.php/CSC/ECE_517_Fall_2015/oss_E1553_AAJ

2 http://www.w3schools.com/jquery/

3 http://www.w3schools.com/js/

CSC/ECE 517 Fall 2016/E1654. Improve date-picker and deadlines

2016-10-28T23:44:58Z

Dssathe: /* Previous Implementation and Problems */

This wiki page is for the description of changes made under E1654/Improve date-picker and deadlines OSS assignment for Fall 2016, CSC/ECE 517.

== About Expertiza ==
Expertiza is a Ruby on Rails application made by the joint contribution of Professors and Students of North Carolina State University. It is used by the Professor ,Teaching Assistants and students of a particular course to manage their respective responsibilities with respect to that course. Professor can enlist a new assignment or project, set/update the deadline to submit it , grant publishing rights to a user and more. The Teaching Assistants can including other things update the review scores of the students, view the submissions etc. The students can view information about all the assignments due and submitted.Students can form teams in Expertiza to work on various projects and assignments.Students can also review other students' submissions and the performance of their teammates. Expertiza supports submissions across various document types, including the URLs and wiki pages.

== Problem Statement ==

The Date-picker allows the instructor to set deadlines for the assignments and peer reviews.

1) The current date-picker doesn't let you change dates easily. When you try to edit a deadline, Unless you spell it out to the minute, it changes the deadline to the current time.

2) While testing, the instructors very often want to test an assignment in, say, the submission or review phase, even after the assignment is complete. In order to do this, we need to change several due dates from the User Interface. This process needs to be simplified.

== Expected Resolution ==

1) Fix the date time picker bug in _due_dates.html.erb.

2) Find a more user-friendly JQuery date-time picker that supports time zones and allow users to define deadline by date and time (hour), if the bug is not fixed in the existing implementation.

3) Time-zone should be automatically picked from users timezone preference.

4) Allow users to set all due dates ahead by x days, and the algorithm calculates the exact date and time.

== Previous Implementation and Problems ==

Problem 1:

In the previous implementation for Expertiza, the professors observed that when they wanted to change the date for submission or review deadline for any project or assignment, Expertiza was not able to handle it properly. As in, when the professor tries to change the date - a calendar pops out but then the calendar should point at the date already in the text box.But this was not implemented as it was picking the date of the system and the professor had to go through a cumbersome process to change the date. And even when any date was not selected the field used to get updated by current date and time.
Reason: In the back end , the date picker used was not able to read the date properly from the text box because of date format mismatch. We observed that if we resolve the mismatch in the date formats , this problem could be solved.

Problem 2:

When there is a requirement which asks for the professor to change the due dates of assignments or projects, (s)he had to change several dates from the front end one by one which was a very time-consuming and ineffective method.
Reason: In the previous implementation , there was no functionality which allowed the professor to change dates for multiple projects,assignments without manually entering a new date in each text box or selecting each date using the datepicker. We observed that we need to add a functionality where the professor can simply select the assignments/projects for which (s)he wants to update the deadline and input the number of days he wants to extend the deadline and by a click of a single button (s)he can change multiple deadlines.

== Changes Made and Issues Resolved ==
We made two major changes.
Change 1 - We improved the date picker implementation. As stated, the date picker was not functioning properly,that is, while changing the date in the text box it was pointing to the system date instead of the date in text box. Reason was the mismatch in the date formats. We made corrections in the code and resolved the mismatch.Now , the date picker is working perfectly fine. It is able to read the date in the text box and there is no mismatch in the date formats.
Change 2 - We simplified the process of changing the due dates of submissions for multiple projects/assignments. It was accomplished by adding check box in front of each assignment. Suppose there are 5 submissions on the page. And the professor wants to adjust the due dates of assignments 1,3 and 5 by 4 days. Then, he will check the check boxes for submissions 1,3 and 5 and increase from 0 to 4 in the number of days. On clicking save, the dates of all the 3 submissions 1,3 and 5 will be increased by 4. While coding , we have checked for the adjustment in the months and years as well keeping in mind some months have 28,29,30 or 31 days with an year being a leap year or not.

==Testing from UI==
Following are a few test cases with respect to our code changes that can be tried from UI:

1. To go to versions index page, type in the following url after logging in:
http://152.46.16.81:3000/versions

2. After logging in as student/instructor or admin : Try accessing the new, create, edit, update actions. These actions are not allowed to any of the users.
http://152.46.16.81:3000/versions/new
This calls the new action. In the current production version of expertiza, it is unhandled and application gives a default 404 page.

3. Another feature that can be tested from UI is Pagination. Try searching for a user's versions and see if the results are paginated or not. Search here:
http://152.46.16.81:3000/versions/search

4. Visit the same URL as step 3, you should see only the students under that instructor in

== Pull Request ==
Here is our [https://github.com/expertiza/expertiza/pull/760 pull request]. In the link you can see all the changes made in the back end made to fix the date picker bug and implement additional functionalities to update deadlines.

== References ==

CSC/ECE 517 Fall 2016/E1654. Improve date-picker and deadlines

2016-10-28T23:43:56Z

Dssathe: /* Previous Implementation and Problems */

This wiki page is for the description of changes made under E1654/Improve date-picker and deadlines OSS assignment for Fall 2016, CSC/ECE 517.

== About Expertiza ==
Expertiza is a Ruby on Rails application made by the joint contribution of Professors and Students of North Carolina State University. It is used by the Professor ,Teaching Assistants and students of a particular course to manage their respective responsibilities with respect to that course. Professor can enlist a new assignment or project, set/update the deadline to submit it , grant publishing rights to a user and more. The Teaching Assistants can including other things update the review scores of the students, view the submissions etc. The students can view information about all the assignments due and submitted.Students can form teams in Expertiza to work on various projects and assignments.Students can also review other students' submissions and the performance of their teammates. Expertiza supports submissions across various document types, including the URLs and wiki pages.

== Problem Statement ==

The Date-picker allows the instructor to set deadlines for the assignments and peer reviews.

1) The current date-picker doesn't let you change dates easily. When you try to edit a deadline, Unless you spell it out to the minute, it changes the deadline to the current time.

2) While testing, the instructors very often want to test an assignment in, say, the submission or review phase, even after the assignment is complete. In order to do this, we need to change several due dates from the User Interface. This process needs to be simplified.

== Expected Resolution ==

1) Fix the date time picker bug in _due_dates.html.erb.

2) Find a more user-friendly JQuery date-time picker that supports time zones and allow users to define deadline by date and time (hour), if the bug is not fixed in the existing implementation.

3) Time-zone should be automatically picked from users timezone preference.

4) Allow users to set all due dates ahead by x days, and the algorithm calculates the exact date and time.

== Previous Implementation and Problems ==

Problem 1:
In the previous implementation for Expertiza, the professors observed that when they wanted to change the date for submission or review deadline for any project or assignment, Expertiza was not able to handle it properly. As in, when the professor tries to change the date - a calendar pops out but then the calendar should point at the date already in the text box.But this was not implemented as it was picking the date of the system and the professor had to go through a cumbersome process to change the date. And even when any date was not selected the field used to get updated by current date and time.
Reason: In the back end , the date picker used was not able to read the date properly from the text box because of date format mismatch. We observed that if we resolve the mismatch in the date formats , this problem could be solved.

Problem 2:
When there is a requirement which asks for the professor to change the due dates of assignments or projects, (s)he had to change several dates from the front end one by one which was a very time-consuming and ineffective method.
Reason: In the previous implementation , there was no functionality which allowed the professor to change dates for multiple projects,assignments without manually entering a new date in each text box or selecting each date using the datepicker. We observed that we need to add a functionality where the professor can simply select the assignments/projects for which (s)he wants to update the deadline and input the number of days he wants to extend the deadline and by a click of a single button (s)he can change multiple deadlines.

== Changes Made and Issues Resolved ==
We made two major changes.
Change 1 - We improved the date picker implementation. As stated, the date picker was not functioning properly,that is, while changing the date in the text box it was pointing to the system date instead of the date in text box. Reason was the mismatch in the date formats. We made corrections in the code and resolved the mismatch.Now , the date picker is working perfectly fine. It is able to read the date in the text box and there is no mismatch in the date formats.
Change 2 - We simplified the process of changing the due dates of submissions for multiple projects/assignments. It was accomplished by adding check box in front of each assignment. Suppose there are 5 submissions on the page. And the professor wants to adjust the due dates of assignments 1,3 and 5 by 4 days. Then, he will check the check boxes for submissions 1,3 and 5 and increase from 0 to 4 in the number of days. On clicking save, the dates of all the 3 submissions 1,3 and 5 will be increased by 4. While coding , we have checked for the adjustment in the months and years as well keeping in mind some months have 28,29,30 or 31 days with an year being a leap year or not.

==Testing from UI==
Following are a few test cases with respect to our code changes that can be tried from UI:

1. To go to versions index page, type in the following url after logging in:
http://152.46.16.81:3000/versions

2. After logging in as student/instructor or admin : Try accessing the new, create, edit, update actions. These actions are not allowed to any of the users.
http://152.46.16.81:3000/versions/new
This calls the new action. In the current production version of expertiza, it is unhandled and application gives a default 404 page.

3. Another feature that can be tested from UI is Pagination. Try searching for a user's versions and see if the results are paginated or not. Search here:
http://152.46.16.81:3000/versions/search

4. Visit the same URL as step 3, you should see only the students under that instructor in

== Pull Request ==
Here is our [https://github.com/expertiza/expertiza/pull/760 pull request]. In the link you can see all the changes made in the back end made to fix the date picker bug and implement additional functionalities to update deadlines.

== References ==