Expertiza_Wiki - User contributions [en]

CSC/ECE 517 Fall 2016 E1687 Instructor account creation over the web

2016-12-04T23:07:53Z

Ckonda:

'''E1687. Instructor Account Creation Over the Web'''

This page gives a detail of the final project of creating an instructor account over the web in Expertiza.

== '''Introduction''' ==
Expertiza is a Ruby on Rails based open source project. The main motive of this project is to make learning more effective through peer review. This website is a result of combined effort of both students and faculty at NC State, and is used not just by this university but also in many other universities. The website allows students to form teams and work on various projects listed by the instructor and also suggest new topics that seem interesting, though they can opt not to work on them. It also makes it easy for the instructor to add a new topic to an assignment/project, create a new project and add students to it. The time spent by TAs and instructor is greatly reduced. The key feature is peer review, where the students can review the work of others and provide feedback. This helps in improving the existing work and also provides a new way to learn. There isn’t any restriction on the format of submission as it accepts any form of submission varying from URL to wiki pages, which isn’t a common feature in other websites.

== '''Problem Statement''' ==
In Expertiza, user and instructor accounts are currently created by existing super administrators, instructors or TAs. For new users to access the system and experiment the features offered by Expertiza, a “demo-like” feature needs to implemented. The following are the set of requirements that needs to be catered with this feature:
#Allow people to request instructor accounts over the web. This feature should also have security features such as Captchas to help avoid account creation by bots.
#When a user account is created over the web, the super-admin should get e-mail regarding the same and also the user should be notified upon approval/denial (if denied, then reason should be specified).
#Currently, Expertiza consists of a lot of entities that can be made publicly visible to all other users in the system. But, accounts created this way should not be able to see existing public features, until the super-admin manually gives them permission to view public courses, assignments, and questionnaires.
#A user who creates an account over the web should be pointed to an instruction page and/or video on how to create an assignment and register students for it, etc.

=='''Implementation'''==
The following solutions shall be addressing the problems discussed above.
===Problem 1===
Once a user wants to register and try the features of Expertiza, upon opening the website, one can register by filling up the form and click the register button. There is a captcha that shall be shown below, to make sure that it isn't any bot that is accessing. It provides security to the application.

===Problem 2===
Once the user requests for an account creation, the super admin receives a mail informing about the request with the name of the requested user. The super admin shall then, look for the details of the user in the Requests tab and can either approve/decline the request. Once the super admin approves the user request, the user gets a mail notifying the same. If the request is rejected, then the reason should be mentioned in the reason tab of the form. But there is no mail sent to the user regarding that.

===Problem 3===
There shall be a flash message saying, “Login denied. Needs permission from super admin” that can be seen on the login page if an unregistered user tries to access the features of Expertiza. This helps in removing the access to few publicly visible features as it denies access completely.

===Problem 4===
Once the user account is approved by the super admin and the user tries to login upon notification, he/she shall be redirected to an “Instructions” page on successful login.

This page shall contain the video tutorials explaining various features of Expertiza and also on how to access them.

=='''Files changed'''==
The following are the list of files that were created/edited throughout the project.
* views/auth/_login.html.erb
* views/users/request_new.html.erb
* views/users/review.html
* views/instructions/home.html.erb
* views/users/edit.html.erb
* views/mailer/request_user_message.html.erb
* views/users/new.html.erb
* views/users/_password.html.erb
* views/users/_user.html.erb
* users_controller.rb
* routes.rb
* models
* mailer_helper.rb
* mailer.rb
* models/requested_user.rb
* config/initializers/recaptcha.rb

In '''_login.html.erb''' a new button called Request Sign Up was added for the new users to register. The register page will look as above. On clicking '''Request sign up''', a user will be redirected to a page like below:

[[File:login_screen.png]]

User will have to fill up all the required details and request a signup.
When a super administrator logins to his account he can go to '''Manage/users/review requested users''' menu as shown below
[[File:Approval_new2.png]]

Super Admin can either approve/reject a user. The view for this page would be as shown below.
[[File:req_approval_table.png]]

In addition to the above files a new file in instructions, named home.html.erb is created which will have all the videos explaining how Expertiza works.

In '''users_controller.rb''' we will be having two new methods. One method (request_user_create) to the new user to request for an account in Expertiza and also mail all the super admins about the new user request. Other method (create_approved_user) is for the super admin to either approve or reject the user request and send a mail to the requested user if his/her account is created. The mail also contains a password for the user to login.

The codes for each method are:

<pre>
def request_user_create
#TODO: Do not allow duplicates
#TODO: All fields should be entered
@user = RequestedUser.new(user_params)
@user.institution_id = params[:user][:institution_id]
@user.status = 'Under Review'
#The super admin receives a mail about a new user request with the user name
if verify_recaptcha(model: @user) && @user.save
@super_users = User.joins(:role).where('roles.name' =>'Super-Administrator');
@super_users.each do |super_user|
prepared_mail = MailerHelper.send_mail_to_all_super_users(super_user,@user, "New account Request")
prepared_mail.deliver
end
flash[:success] = "User signup for \"#{@user.name}\" has been successfully requested. "
redirect_to '/instructions/home'
else
flash[:error] = "Error requesting sign up "
redirect_to :controller => 'users', :action => 'request_new', :role=>"Student"
end
end

</pre>

<pre>
def create_approved_user
@user = RequestedUser.find params[:id]
@user.status=params[:status]
@user.reason=params[:reason]
if @user.status.nil?
flash[:error] = "Please Approve or Reject before submitting"
elsif @user.update_attributes(params[:user])
flash[:success] = "The user \"#{@user.name}\" has been successfully updated."
end
if @user.status=="Approved"
check = User.find_by_name(@user.name)
@usernew = User.new()
@usernew.name = @user.name
@usernew.role_id = @user.role_id
@usernew.institution_id = @user.institution_id
@usernew.fullname = @user.fullname
@usernew.email = @user.email
# record the person who created this new user
@usernew.parent_id = session[:user].id
# set the user's timezone to its parent's
@usernew.timezonepref = User.find(@usernew.parent_id).timezonepref

if @usernew.save
password = @usernew.reset_password # the password is reset
# Mail is sent to the user with a new password
prepared_mail = MailerHelper.send_mail_to_user(@usernew, "Your Expertiza account and password
have been created.", "user_welcome", password)
prepared_mail.deliver
flash[:success] = "A new password has been sent to new user's e-mail address."
if @usernew.role.name == "Instructor" or @usernew.role.name == "Administrator"
AssignmentQuestionnaire.create(user_id: @user.id)
end
undo_link("The user \"#{@user.name}\" has been successfully created. ")
else
foreign
end
else
if @user.status=="Rejected"
#If the user request has been rejected, a flash message is shown and redirected to review page
if @user.update_columns(reason: params[:reason], status: params[:status])
flash[:success] = "The user \"#{@user.name}\" has been Rejected."
redirect_to action: 'review'
return
else
flash[:error] = "Error processing request."
end
end

end
redirect_to action: 'review'
end
</pre>

=='''Database Changes'''==

We have created a new table called '''requested_users''' with table description that is similar to '''users'''. The status column, which isn't present in the users tables indicates the approval/rejection of the request of the user. The description of the table is as follows:

[[File:Requested_user_db.png‎ ]]

=='''Screencast'''==

Screencast [https://youtu.be/4HAs8jhbkw4 link] to our demonstration

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

We will be testing each of the functionality separately.

1. Test all views - will be testing if '''_login.html.erb''' and '''Request_new.html.erb''' are rendered properly.

2. Test all controller methods. New test cases will be included for each case:
* Does '''create_approved_user''' actually create a new user
* Does '''request_user_create''' actually not create a new user request

3. Test the model '''requested_user''' so that no invalid entries (blank email ID, blank name etc.) are accepted.

4. Test the mailer to verify if the body, subject, the mail id sent to/from are correctly functioning.

CSC/ECE 517 Fall 2016 E1687 Instructor account creation over the web

2016-12-04T23:07:00Z

Ckonda:

'''E1687. Instructor Account Creation Over the Web'''

This page gives a detail of the final project of creating an instructor account over the web in Expertiza.

== '''Introduction''' ==
Expertiza is a Ruby on Rails based open source project. The main motive of this project is to make learning more effective through peer review. This website is a result of combined effort of both students and faculty at NC State, and is used not just by this university but also in many other universities. The website allows students to form teams and work on various projects listed by the instructor and also suggest new topics that seem interesting, though they can opt not to work on them. It also makes it easy for the instructor to add a new topic to an assignment/project, create a new project and add students to it. The time spent by TAs and instructor is greatly reduced. The key feature is peer review, where the students can review the work of others and provide feedback. This helps in improving the existing work and also provides a new way to learn. There isn’t any restriction on the format of submission as it accepts any form of submission varying from URL to wiki pages, which isn’t a common feature in other websites.

== '''Problem Statement''' ==
In Expertiza, user and instructor accounts are currently created by existing super administrators, instructors or TAs. For new users to access the system and experiment the features offered by Expertiza, a “demo-like” feature needs to implemented. The following are the set of requirements that needs to be catered with this feature:
#Allow people to request instructor accounts over the web. This feature should also have security features such as Captchas to help avoid account creation by bots.
#When a user account is created over the web, the super-admin should get e-mail regarding the same and also the user should be notified upon approval/denial (if denied, then reason should be specified).
#Currently, Expertiza consists of a lot of entities that can be made publicly visible to all other users in the system. But, accounts created this way should not be able to see existing public features, until the super-admin manually gives them permission to view public courses, assignments, and questionnaires.
#A user who creates an account over the web should be pointed to an instruction page and/or video on how to create an assignment and register students for it, etc.

=='''Implementation'''==
The following solutions shall be addressing the problems discussed above.
===Problem 1===
Once a user wants to register and try the features of Expertiza, upon opening the website, one can register by filling up the form and click the register button. There is a captcha that shall be shown below, to make sure that it isn't any bot that is accessing. It provides security to the application.

===Problem 2===
Once the user requests for an account creation, the super admin receives a mail informing about the request with the name of the requested user. The super admin shall then, look for the details of the user in the Requests tab and can either approve/decline the request. Once the super admin approves the user request, the user gets a mail notifying the same. If the request is rejected, then the reason should be mentioned in the reason tab of the form. But there is no mail sent to the user regarding that.

===Problem 3===
There shall be a flash message saying, “Login denied. Needs permission from super admin” that can be seen on the login page if an unregistered user tries to access the features of Expertiza. This helps in removing the access to few publicly visible features as it denies access completely.

===Problem 4===
Once the user account is approved by the super admin and the user tries to login upon notification, he/she shall be redirected to an “Instructions” page on successful login.

This page shall contain the video tutorials explaining various features of Expertiza and also on how to access them.

=='''Files changed'''==
The following are the list of files that were created/edited throughout the project.
* views/auth/_login.html.erb
* views/users/request_new.html.erb
* views/users/review.html
* views/instructions/home.html.erb
* views/users/edit.html.erb
* views/mailer/request_user_message.html.erb
* views/users/new.html.erb
* views/users/_password.html.erb
* views/users/_user.html.erb
* users_controller.rb
* routes.rb
* models
* mailer_helper.rb
* mailer.rb
* models/requested_user.rb
* config/initializers/recaptcha.rb

In '''_login.html.erb''' a new button called Request Sign Up was added for the new users to register. The register page will look as above. On clicking '''Request sign up''', a user will be redirected to a page like below:

[[File:login_screen.png]]

User will have to fill up all the required details and request a signup.
When a super administrator logins to his account he can go to '''Manage/users/review requested users''' menu as shown below
[[File:Approval_new2.png]]

Super Admin can either approve/reject a user. The view for this page would be as shown below.
[[File:req_approval_table.png]]

In addition to the above files a new file in instructions, named home.html.erb is created which will have all the videos explaining how Expertiza works.

In '''users_controller.rb''' we will be having two new methods. One method (request_user_create) to the new user to request for an account in Expertiza and also mail all the super admins about the new user request. Other method (create_approved_user) is for the super admin to either approve or reject the user request and send a mail to the requested user if his/her account is created. The mail also contains a password for the user to login.

The codes for each method are:

<pre>
def request_user_create
#TODO: Do not allow duplicates
#TODO: All fields should be entered
@user = RequestedUser.new(user_params)
@user.institution_id = params[:user][:institution_id]
@user.status = 'Under Review'
#The super admin receives a mail about a new user request with the user name
if verify_recaptcha(model: @user) && @user.save
@super_users = User.joins(:role).where('roles.name' =>'Super-Administrator');
@super_users.each do |super_user|
prepared_mail = MailerHelper.send_mail_to_all_super_users(super_user,@user, "New account Request")
prepared_mail.deliver
end
flash[:success] = "User signup for \"#{@user.name}\" has been successfully requested. "
redirect_to '/instructions/home'
else
flash[:error] = "Error requesting sign up "
redirect_to :controller => 'users', :action => 'request_new', :role=>"Student"
end
end

</pre>

<pre>
def create_approved_user
@user = RequestedUser.find params[:id]
@user.status=params[:status]
@user.reason=params[:reason]
if @user.status.nil?
flash[:error] = "Please Approve or Reject before submitting"
elsif @user.update_attributes(params[:user])
flash[:success] = "The user \"#{@user.name}\" has been successfully updated."
end
if @user.status=="Approved"
check = User.find_by_name(@user.name)
@usernew = User.new()
@usernew.name = @user.name
@usernew.role_id = @user.role_id
@usernew.institution_id = @user.institution_id
@usernew.fullname = @user.fullname
@usernew.email = @user.email
# record the person who created this new user
@usernew.parent_id = session[:user].id
# set the user's timezone to its parent's
@usernew.timezonepref = User.find(@usernew.parent_id).timezonepref

if @usernew.save
password = @usernew.reset_password # the password is reset
# Mail is sent to the user with a new password
prepared_mail = MailerHelper.send_mail_to_user(@usernew, "Your Expertiza account and password
have been created.", "user_welcome", password)
prepared_mail.deliver
flash[:success] = "A new password has been sent to new user's e-mail address."
if @usernew.role.name == "Instructor" or @usernew.role.name == "Administrator"
AssignmentQuestionnaire.create(user_id: @user.id)
end
undo_link("The user \"#{@user.name}\" has been successfully created. ")
else
foreign
end
else
if @user.status=="Rejected"
#If the user request has been rejected, a flash message is shown and redirected to review page
if @user.update_columns(reason: params[:reason], status: params[:status])
flash[:success] = "The user \"#{@user.name}\" has been Rejected."
redirect_to action: 'review'
return
else
flash[:error] = "Error processing request."
end
end

end
redirect_to action: 'review'
end
</pre>

=='''Database Changes'''==

We have created a new table called '''requested_users''' with table description that is similar to '''users'''. The status column, which isn't present in the users tables indicates the approval/rejection of the request of the user. The description of the table is as follows:

[[File:Requested_user_db.png‎ ]]

=='''Screencast'''==

https://youtu.be/4HAs8jhbkw4

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

We will be testing each of the functionality separately.

1. Test all views - will be testing if '''_login.html.erb''' and '''Request_new.html.erb''' are rendered properly.

2. Test all controller methods. New test cases will be included for each case:
* Does '''create_approved_user''' actually create a new user
* Does '''request_user_create''' actually not create a new user request

3. Test the model '''requested_user''' so that no invalid entries (blank email ID, blank name etc.) are accepted.

4. Test the mailer to verify if the body, subject, the mail id sent to/from are correctly functioning.

CSC/ECE 517 Fall 2016 E1687 Instructor account creation over the web

2016-12-04T22:56:53Z

Ckonda: /* Files changed */

'''E1687. Instructor Account Creation Over the Web'''

This page gives a detail of the final project of creating an instructor account over the web in Expertiza.

== '''Introduction''' ==
Expertiza is a Ruby on Rails based open source project. The main motive of this project is to make learning more effective through peer review. This website is a result of combined effort of both students and faculty at NC State, and is used not just by this university but also in many other universities. The website allows students to form teams and work on various projects listed by the instructor and also suggest new topics that seem interesting, though they can opt not to work on them. It also makes it easy for the instructor to add a new topic to an assignment/project, create a new project and add students to it. The time spent by TAs and instructor is greatly reduced. The key feature is peer review, where the students can review the work of others and provide feedback. This helps in improving the existing work and also provides a new way to learn. There isn’t any restriction on the format of submission as it accepts any form of submission varying from URL to wiki pages, which isn’t a common feature in other websites.

== '''Problem Statement''' ==
In Expertiza, user and instructor accounts are currently created by existing super administrators, instructors or TAs. For new users to access the system and experiment the features offered by Expertiza, a “demo-like” feature needs to implemented. The following are the set of requirements that needs to be catered with this feature:
#Allow people to request instructor accounts over the web. This feature should also have security features such as Captchas to help avoid account creation by bots.
#When a user account is created over the web, the super-admin should get e-mail regarding the same and also the user should be notified upon approval/denial (if denied, then reason should be specified).
#Currently, Expertiza consists of a lot of entities that can be made publicly visible to all other users in the system. But, accounts created this way should not be able to see existing public features, until the super-admin manually gives them permission to view public courses, assignments, and questionnaires.
#A user who creates an account over the web should be pointed to an instruction page and/or video on how to create an assignment and register students for it, etc.

=='''Implementation'''==
The following solutions shall be addressing the problems discussed above.
===Problem 1===
Once a user wants to register and try the features of Expertiza, upon opening the website, one can register by filling up the form and click the register button. There is a captcha that shall be shown below, to make sure that it isn't any bot that is accessing. It provides security to the application.

===Problem 2===
Once the user requests for an account creation, the super admin receives a mail informing about the request with the name of the requested user. The super admin shall then, look for the details of the user in the Requests tab and can either approve/decline the request. Once the super admin approves the user request, the user gets a mail notifying the same. If the request is rejected, then the reason should be mentioned in the reason tab of the form. But there is no mail sent to the user regarding that.

===Problem 3===
There shall be a flash message saying, “Login denied. Needs permission from super admin” that can be seen on the login page if an unregistered user tries to access the features of Expertiza. This helps in removing the access to few publicly visible features as it denies access completely.

===Problem 4===
Once the user account is approved by the super admin and the user tries to login upon notification, he/she shall be redirected to an “Instructions” page on successful login.

This page shall contain the video tutorials explaining various features of Expertiza and also on how to access them.

=='''Files changed'''==
The following are the list of files that were created/edited throughout the project.
* views/auth/_login.html.erb
* views/users/request_new.html.erb
* views/users/review.html
* views/instructions/home.html.erb
* views/users/edit.html.erb
* views/mailer/request_user_message.html.erb
* views/users/new.html.erb
* views/users/_password.html.erb
* views/users/_user.html.erb
* users_controller.rb
* routes.rb
* models
* mailer_helper.rb
* mailer.rb
* models/requested_user.rb
* config/initializers/recaptcha.rb

In '''_login.html.erb''' a new button called Request Sign Up was added for the new users to register. The register page will look as above. On clicking '''Request sign up''', a user will be redirected to a page like below:

[[File:login_screen.png]]

User will have to fill up all the required details and request a signup.
When a super administrator logins to his account he can go to '''Manage/users/review requested users''' menu as shown below
[[File:Approval_new2.png]]

Super Admin can either approve/reject a user. The view for this page would be as shown below.
[[File:req_approval_table.png]]

In addition to the above files a new file in instructions, named home.html.erb is created which will have all the videos explaining how Expertiza works.

In '''users_controller.rb''' we will be having two new methods. One method (request_user_create) to the new user to request for an account in Expertiza and also mail all the super admins about the new user request. Other method (create_approved_user) is for the super admin to either approve or reject the user request and send a mail to the requested user if his/her account is created. The mail also contains a password for the user to login.

The codes for each method are:

<pre>
def request_user_create
#TODO: Do not allow duplicates
#TODO: All fields should be entered
@user = RequestedUser.new(user_params)
@user.institution_id = params[:user][:institution_id]
@user.status = 'Under Review'
#The super admin receives a mail about a new user request with the user name
if verify_recaptcha(model: @user) && @user.save
@super_users = User.joins(:role).where('roles.name' =>'Super-Administrator');
@super_users.each do |super_user|
prepared_mail = MailerHelper.send_mail_to_all_super_users(super_user,@user, "New account Request")
prepared_mail.deliver
end
flash[:success] = "User signup for \"#{@user.name}\" has been successfully requested. "
redirect_to '/instructions/home'
else
flash[:error] = "Error requesting sign up "
redirect_to :controller => 'users', :action => 'request_new', :role=>"Student"
end
end

</pre>

<pre>
def create_approved_user
@user = RequestedUser.find params[:id]
@user.status=params[:status]
@user.reason=params[:reason]
if @user.status.nil?
flash[:error] = "Please Approve or Reject before submitting"
elsif @user.update_attributes(params[:user])
flash[:success] = "The user \"#{@user.name}\" has been successfully updated."
end
if @user.status=="Approved"
check = User.find_by_name(@user.name)
@usernew = User.new()
@usernew.name = @user.name
@usernew.role_id = @user.role_id
@usernew.institution_id = @user.institution_id
@usernew.fullname = @user.fullname
@usernew.email = @user.email
# record the person who created this new user
@usernew.parent_id = session[:user].id
# set the user's timezone to its parent's
@usernew.timezonepref = User.find(@usernew.parent_id).timezonepref

if @usernew.save
password = @usernew.reset_password # the password is reset
# Mail is sent to the user with a new password
prepared_mail = MailerHelper.send_mail_to_user(@usernew, "Your Expertiza account and password
have been created.", "user_welcome", password)
prepared_mail.deliver
flash[:success] = "A new password has been sent to new user's e-mail address."
if @usernew.role.name == "Instructor" or @usernew.role.name == "Administrator"
AssignmentQuestionnaire.create(user_id: @user.id)
end
undo_link("The user \"#{@user.name}\" has been successfully created. ")
else
foreign
end
else
if @user.status=="Rejected"
#If the user request has been rejected, a flash message is shown and redirected to review page
if @user.update_columns(reason: params[:reason], status: params[:status])
flash[:success] = "The user \"#{@user.name}\" has been Rejected."
redirect_to action: 'review'
return
else
flash[:error] = "Error processing request."
end
end

end
redirect_to action: 'review'
end
</pre>

=='''Database Changes'''==

We have created a new table called '''requested_users''' with table description that is similar to '''users'''. The status column, which isn't present in the users tables indicates the approval/rejection of the request of the user. The description of the table is as follows:

[[File:Requested_user_db.png‎ ]]

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

We will be testing each of the functionality separately.

1. Test all views - will be testing if '''_login.html.erb''' and '''Request_new.html.erb''' are rendered properly.

2. Test all controller methods. New test cases will be included for each case:
* Does '''create_approved_user''' actually create a new user
* Does '''request_user_create''' actually not create a new user request

3. Test the model '''requested_user''' so that no invalid entries (blank email ID, blank name etc.) are accepted.

4. Test the mailer to verify if the body, subject, the mail id sent to/from are correctly functioning.

File:Approval new2.png

2016-12-04T22:56:47Z

Ckonda:

CSC/ECE 517 Fall 2016/E1657. Introduce a Student View for instructors

2016-11-20T05:12:20Z

Ckonda: /* Implementation */

__TOC__
'''NOTE: The pull request will not pass the build.Its not due to our changes but due to some unrelated test failure. '''
==Background==
[http://expertiza.ncsu.edu/ Expertiza] is a web based open source peer reviewing tool based on [http://rubyonrails.org/ Ruby on Rails] developed and maintained by current and past students of [https://en.wikipedia.org/wiki/North_Carolina_State_University North Carolina State University], Raleigh. Students will be able to manage all their project submissions, project teamups, topic selections etc. Few of the notable features include:
* Instructor can control most of the stuff that is related to each course.
* Student can control who he/she wants to team up with etc.
* They can provide feedback to each of the topics.
* Instructor can make use of the various submission phases available.
== Introduction ==
Our project is to introduce a Student view to the instructors.The goal of this project is to provide instructor with a functionality using which an instructor can switch to student view and see how the student view looks like. The instructor will also be able to go to future date and see how student view looks like in future date.

==Project Requirements==
* Introduce a "Student View Button" on Instructors UI to switch to student view.
* Introduce a Revert to instructor View" on Instructor's Student UI
* Time travel in Student View.

==Working==
On the right top, left to the logout button , anyone having access to view as instructor gets a textbox and a button saying "Student View". in-order to view as a student you have to type in the students ID and press '''Student View''' button. You can exactly see what the student's page looks like. 
[[File:HomeKN6.jpg]]
 
If you need to revert back to instructor view you just have to leave the text box empty and press the '''Revert''' button. This takes you to the instructors view again. Else if you need another students view, just type in the students ID and press '''Revert'''. 
[[File:HomeKN3.jpg]]
 
We also have implemented a time travel feature where you can go to a particular date and see what a student see on that day. You can find this feature as soon as you go to a student ID. You have to select a day you need to travel to, type in the student ID and submit. Boom! you got he student view as on the date given. 
[[File:HomeKN4.jpg]]

==Implementation==
* Introduce a "Switch to Student View Button" on Instructors UI
:A 'Student View' button was added in the top right portion of menu-bar for instructor. This button allows instructor to see the student view. This button is linked to impersonate action of [https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/controllers/impersonate_controller.rb Impersonate_controller]. The button was simply added in menu-bar view. When the button is clicked, it calls <code>impersonate</code> method in <code>impersonate controller</code> which loads new view as student for provided student id. 

:Required changes in 1 files : 
:[https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/views/shared/_navigation.html.erb navigation.html] 
<pre>
<% if current_user.role.name == "Instructor" or current_user.role.name == "Administrator"%>
<%= form_for :user, url: '/impersonate/impersonate' do |f| %>
<TABLE>
<TR>
<TD><%= f.text_field :name, {:size => 10,:class => 'form-control input-sm',
:autocomplete => "off",placeholder: "User ID"} %></TD>
<TD><%= f.submit 'Student View', :class=>"btn btn-primary input-sm"%></TD>
</TR>
</TABLE>
<% end %>
<% end %>
</pre>
:If student ID is not provided, the system will randomly select an student ID from all the students in the database, and impersonate the selected student view. This is useful when the instructor doesn't remember the specific student ID.
:Required changes in 1 file : 
:[https://github.com/chaitanya91k/expertiza/blob/master/app/controllers/impersonate_controller.rb Impersonate_controller.rb] 
<pre>
if params[:user][:name]==""
students = User.all.where(role_id: Role.student)
user = students[rand(students.length)]
until original_user.can_impersonate? user
user = students[rand(students.length)]
end
end
</pre>
* Introduce a Revert to instructor View" on Instructor's Student UI
:Once instructor impersonate to a student view, a Revert button appears which when clicked revert back to instructor view from impersonated student view. Once the student view is loaded by instructor,<code>session[:superuser]</code> is set and based on this flag a revert button will be displayed. 

* Time travel in Student View.
:Required changes in 4 files : 
:[https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/views/shared/_navigation.html.erb navigation.html] 
<div class="field">
<%= f.date_field :goto_date, :order => [:month,:day, :year],:value => Date.today %>
</div>
:First, we introduced a date box where you can select a date from the UI. 
[https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/controllers/impersonate_controller.rb Impersonate_controller] 
if !params[:impersonate][:goto_date].empty?
User.goto_date=params[:impersonate][:goto_date]
end
:In this controller, we took the value from UI and store the same in User model. 
:[https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/models/user.rb user.rb] 
attr_accessible :goto_date
def self.goto_date=(val)
@goto_date=val
end
def self.goto_date
@goto_date
end
:The value from the above controller is stored in Users model object (not instance) as goto_date. Thus you can access this date through out the sessions. 
:[https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/models/due_date.rb due_date.rb] 

def self.get_next_due_date(assignment_id, topic_id = nil)
(User.goto_date.nil?)? goto_date = Time.now : goto_date = (User.goto_date)
if Assignment.find(assignment_id).staggered_deadline?
next_due_date = TopicDueDate.where(['parent_id = ? and due_at >= ?', topic_id, Time.now]).first
next_due_date = TopicDueDate.where(['parent_id = ? and due_at >= ?', topic_id, goto_date]).first
topic_due_date_size = TopicDueDate.where(parent_id: topic_id).size
following_assignment_due_dates = AssignmentDueDate.where(parent_id: assignment_id)[topic_due_date_size..-1]
following_assignment_due_dates.each do |assignment_due_date|
if assignment_due_date.due_at >= Time.now
if assignment_due_date.due_at >= goto_date
next_due_date = assignment_due_date
break
end
end
end
else
next_due_date = AssignmentDueDate.where(['parent_id = ? && due_at >= ?', assignment_id, Time.now]).first
next_due_date = AssignmentDueDate.where(['parent_id = ? && due_at >= ?', assignment_id, goto_date]).first
end
next_due_date
end

:When ever the system calculates due dates, the time is taken from goto_date that we have stored above in Users model. 

==Testing via UI==
* Login in as Instructor.
*Create assignment. I have created one with name Test_Changes with submission deadline Nov 09 and review Deadline Nov 14. Add all the student in course for this assignment. 
[[File:Svk1.jpg]] 
 
 
*Switch to student view. Once switched to student view you can see the assignment with submission deadline Nov 09.
[[File:Sv2N.jpg]] 
 
 
*Go to future date and view the assignment list. I went to Nov 10 in future and we can see that the current phase for our assignment is review. 
[[File:Svk3N.jpg]] 
[[File:Svk4N.jpg]]

==Why These Changes?==
* Requirement: Add a “student view” button for instructors.
:As we were required to add a button , it makes more sense to add a similar button used across the application. Thus we choose class="btn btn-primary" for buttons and :class => 'form-control input-sm' for textboxes.

* Requirement: Introduce a revert button to go back to instructor:
:After an instructor enters a student ID of a student and enters student view, there should be a way to go back to instructors . Thus we have introduced a revert button. Also if the instructor wants to go to a different student’s view he should be able to do so as well. Making these two tasks possible with single textbox and button was better instead of an extra button to go back to instructors view. Now to go back to instructors view, instructor has to leave the textbox blank and click “revert”, if the instructor wants to go to a different student’s view he just need to enter the new student’s id and click on “revert”.

* Requirement: View on specific date:
:We decided to include a date box which on clicked on the date field a data picker pops up. We have added this picker as it makes sense to just click on which date instead of typing the whole date.

==Repository==
[https://github.com/chaitanya91k/expertiza Expertiza Github link]
==Screencast==
Screencast [https://youtu.be/WrJm6csM3mo link] to our demonstration

CSC/ECE 517 Fall 2016 E1687 Instructor account creation over the web

2016-11-15T20:14:09Z

Ckonda: /* Test Plan */

'''E1687. Instructor Account Creation Over the Web'''

This page gives a detail of the final project of creating an instructor account over the web in Expertiza.

== '''Introduction''' ==
Expertiza is a Ruby on Rails based open source project. The main motive of this project is to make learning more effective through peer review. This website is a result of combined effort of both students and faculty at NC State, and is used not just by this university but also in many other universities. The website allows students to form teams and work on various projects listed by the instructor and also suggest new topics that seem interesting, though they can opt not to work on them. It also makes it easy for the instructor to add a new topic to an assignment/project, create a new project and add students to it. The time spent by TAs and instructor is greatly reduced. The key feature is peer review, where the students can review the work of others and provide feedback. This helps in improving the existing work and also provides a new way to learn. There isn’t any restriction on the format of submission as it accepts any form of submission varying from URL to wiki pages, which isn’t a common feature in other websites.

== '''Problem Statement''' ==
In Expertiza, user and instructor accounts are currently created by existing super administrators, instructors or TAs. For new users to access the system and experiment the features offered by Expertiza, a “demo-like” feature needs to implemented. The following are the set of requirements that needs to be catered with this feature:
#Allow people to request instructor accounts over the web. This feature should also have security features such as Captchas to help avoid account creation by bots.
#When a user account is created over the web, the super-admin should get e-mail regarding the same and also the user should be notified upon approval/denial (if denied, then reason should be specified).
#Currently, Expertiza consists of a lot of entities that can be made publicly visible to all other users in the system. But, accounts created this way should not be able to see existing public features, until the super-admin manually gives them permission to view public courses, assignments, and questionnaires.
#A user who creates an account over the web should be pointed to an instruction page and/or video on how to create an assignment and register students for it, etc.

=='''Implementation'''==
The following solutions shall be addressing the problems discussed above.
===Problem 1===
Once a user wants to register and try the features of Expertiza, upon opening the website, one can register through the “Demo” button. So the first page would look something similar to the figure below.

Clicking on “Demo” shall redirect to another page where the user enters his/her credentials. These shall be sent to the super admin for approval/denial of the account once the user clicks on “Register” button. This is also secured through captcha feature as shown below.

===Problem 2===
Once the user requests for an account creation, the super admin should be receiving a mail informing about the request (need not have the user name/id). The super admin shall then, look for the details of the user in the Requests tab and can either approve/decline the request. The UI would be as follows:
As soon as the super admin performs an action, the user is notified about the same. But the reason is mentioned in the mail if the account has been rejected.

===Problem 3===
There shall be a flash message saying, “Login denied. Needs permission from super admin” that can be seen on the login page if an unregistered user tries to access the features of Expertiza. This helps in removing the access to few publicly visible features as it denies access completely.

===Problem 4===
Once the user account is approved by the super admin and the user tries to login upon notification, he/she shall be redirected to an “Instructions” page on successful login.

This page shall contain the video tutorials explaining various features of Expertiza and also n how to access them.

=='''Views changed'''==
The following are the list of files that shall be edited throughout the project.
[[File:Sign_up.png]]

'''_login.html.erb''' add new button called Request Sign Up
The welcome page will look as above. On clicking '''request sign up''', a user will be redirected to a page like below:
'''Request_new.html.erb''' which renders partial view - '''_user.html.erb'''
[[File:Requestuserckonda.png]]

User will be able to fill up all the required details and request a signup.
When a super administrator logins to his account he can go to '''Request/reject users''' menu as shown below
[[File:Approval_new.png]]

Super Admin can either approve/reject a user. The page will look like below(''' approve.html.erb'''):

[[File:Approve.png]]

In addition to the above files a new file called Instructions.html.erb which will have all the videos and instructions on how Expertiza works.

In '''users_controller.rb''' we will be having two new methods:

1. '''request_list'''

def request_list
user = session[:user]
role = user.role
all_users = request_user.get_requested_user_list
letter = params[:letter]
session[:letter] = letter
if letter.nil?
letter = all_users.first.name[0, 1].downcase unless all_users.empty?
end
@letters = []
@per_page = 1
@per_page = if params[:paginate_show]
params[:num_users]
elsif params[:from_letter]
1
else
params[:num_users]
end
@requested_users = paginate_list all_users
@letters = ('A'..'Z').to_a
end
2. '''approve_user'''

def approve_user
# will be calling create method with required parameters and setting the status in request_users table to approved.
# apter the user is created, email is sent to user.
end

3. '''reject_user'''

def reject_user
#will set the status in request_users to reject and send an email to user about the same.
end

=='''Database Changes'''==

We will be creating a new table called '''request_users''' with table description that is similar to '''users'''
Below is the table description of '''users''' table.
[[File:Users.png]]

Our '''request_users''' will also be having a new column called '''status''' which describes that the user is approved or rejected.

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

We will be testing each of the functionality separately.

1. Test all views

will be testing if '''_login.html.erb''', '''Request_new.html.erb''' and ''' approve.html.erb''' are rendered properly.

2. Test all controller methods.

New test cases will be included for each case:
a) Does '''request_list''' method gives the proper list of requested users?
b) Does '''approve_user''' actually create a new user
c) Does '''reject_user''' actually not create a new user and change the status properly.
d) Also test cases where the functions should not work.

CSC/ECE 517 Fall 2016 E1687 Instructor account creation over the web

File:Approve.png

2016-11-15T03:26:19Z

Ckonda:

CSC/ECE 517 Fall 2016/E1657. Introduce a Student View for instructors

2016-11-04T23:20:09Z

Ckonda:

__TOC__
'''NOTE: The pull request will not pass the build.Its not due to our changes but due to some unrelated test failure. '''
==Background==
[http://expertiza.ncsu.edu/ Expertiza] is a web based open source peer reviewing tool based on [http://rubyonrails.org/ Ruby on Rails] developed and maintained by current and past students of [https://en.wikipedia.org/wiki/North_Carolina_State_University North Carolina State University], Raleigh. Students will be able to manage all their project submissions, project teamups, topic selections etc. Few of the notable features include:
* Instructor can control most of the stuff that is related to each course.
* Student can control who he/she wants to team up with etc.
* They can provide feedback to each of the topics.
* Instructor can make use of the various submission phases available.
== Introduction ==
Our project is to introduce a Student view to the instructors.The goal of this project is to provide instructor with a functionality using which an instructor can switch to student view and see how the student view looks like. The instructor will also be able to go to future date and see how student view looks like in future date.

==Project Requirements==
* Introduce a "Student View Button" on Instructors UI to switch to student view.
* Introduce a Revert to instructor View" on Instructor's Student UI
* Time travel in Student View.

==Working==
On the right top, left to the logout button , anyone having access to view as instructor gets a textbox and a button saying "Student View". in-order to view as a student you have to type in the students ID and press '''Student View''' button. You can exactly see what the student's page looks like.
[[File:HomeK6.jpg]]
 
If you need to revert back to instructor view you just have to leave the text box empty and press the '''Revert''' button. This takes you to the instructors view again. Else if you need another students view, just type in the students ID and press '''Revert'''.
[[File:HomeK3.jpg]]
 
We also have implemented a time travel feature where you can go to a particular date and see what a student see on that day. You can find this feature as soon as you go to a student ID. You have to select a day you need to travel to, type in the student ID and submit. Boom! you got he student view as on the date given.
[[File:HomeK4.jpg]]

==Implementation==
* Introduce a "Switch to Student View Button" on Instructors UI
:A 'Student View' button was added in the top right portion of menu-bar for instructor. This button allows instructor to see the student view. This button is linked to impersonate action of [https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/controllers/impersonate_controller.rb Impersonate_controller]. The button was simply added in menu-bar view. When the button is clicked, it calls <code>impersonate</code> method in <code>impersonate controller</code> which loads new view as student for provided student id. 

:Required changes in 1 files : 
:[https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/views/shared/_navigation.html.erb navigation.html] 
<pre>
<% if current_user.role.name == "Instructor" or current_user.role.name == "Administrator"%>
<%= form_for :user, url: '/impersonate/impersonate' do |f| %>
<TABLE>
<TR>
<TD><%= f.text_field :name, {:size => 10,:class => 'form-control input-sm', :autocomplete => "off",placeholder: "User ID"} %></TD>
<TD><%= f.submit 'Student View', :class=>"btn btn-primary input-sm"%></TD>
</TR>
</TABLE>
<% end %>
<% end %>
</pre>
* Introduce a Revert to instructor View" on Instructor's Student UI
:Once instructor impersonate to a student view, a Revert button appears which when clicked revert back to instructor view from impersonated student view. Once the student view is loaded by instructor,<code>session[:superuser]</code> is set and based on this flag a revert button will be displayed. 

* Time travel in Student View.
:Required changes in 4 files : 
:[https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/views/shared/_navigation.html.erb navigation.html] 
<div class="field">
<%= f.date_field :goto_date, :order => [:month,:day, :year],:value => Date.today %>
</div>
:First, we introduced a date box where you can select a date from the UI. 
[https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/controllers/impersonate_controller.rb Impersonate_controller] 
if !params[:impersonate][:goto_date].empty?
User.goto_date=params[:impersonate][:goto_date]
end
:In this controller, we took the value from UI and store the same in User model. 
:[https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/models/user.rb user.rb] 
attr_accessible :goto_date
def self.goto_date=(val)
@goto_date=val
end
def self.goto_date
@goto_date
end
:The value from the above controller is stored in Users model object (not instance) as goto_date. Thus you can access this date through out the sessions. 
:[https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/models/due_date.rb due_date.rb] 

def self.get_next_due_date(assignment_id, topic_id = nil)
(User.goto_date.nil?)? goto_date = Time.now : goto_date = (User.goto_date)
if Assignment.find(assignment_id).staggered_deadline?
next_due_date = TopicDueDate.where(['parent_id = ? and due_at >= ?', topic_id, Time.now]).first
next_due_date = TopicDueDate.where(['parent_id = ? and due_at >= ?', topic_id, goto_date]).first
topic_due_date_size = TopicDueDate.where(parent_id: topic_id).size
following_assignment_due_dates = AssignmentDueDate.where(parent_id: assignment_id)[topic_due_date_size..-1]
following_assignment_due_dates.each do |assignment_due_date|
if assignment_due_date.due_at >= Time.now
if assignment_due_date.due_at >= goto_date
next_due_date = assignment_due_date
break
end
end
end
else
next_due_date = AssignmentDueDate.where(['parent_id = ? && due_at >= ?', assignment_id, Time.now]).first
next_due_date = AssignmentDueDate.where(['parent_id = ? && due_at >= ?', assignment_id, goto_date]).first
end
next_due_date
end

:When ever the system calculates due dates, the time is taken from goto_date that we have stored above in Users model. 

==Testing via UI==
* Login in as Instructor.
*Create assignment. I have created one with name Test_Changes with submission deadline Nov 09 and review Deadline Nov 14. Add all the student in course for this assignment
[[File:Svk1.jpg]] 
 
 
*Switch to student view. Once switched to student view you can see the assignment with submission deadline Nov 09.
[[File:Sv2.jpg]] 
 
 
*Go to future date and view the assignment list. I went to Nov 10 in future and we can see that the current phase for our assignment is review.
[[File:Svk3.jpg]] 
[[File:Svk4.jpg]]

==Why These Changes?==
* Requirement: Add a “student view” button for instructors.
:As we were required to add a button , it makes more sense to add a similar button used across the application. Thus we choose class="btn btn-primary" for buttons and :class => 'form-control input-sm' for textboxes.

* Requirement: Introduce a revert button to go back to instructor:
:After an instructor enters a student ID of a student and enters student view, there should be a way to go back to instructors . Thus we have introduced a revert button. Also if the instructor wants to go to a different student’s view he should be able to do so as well. Making these two tasks possible with single textbox and button was better instead of an extra button to go back to instructors view. Now to go back to instructors view, instructor has to leave the textbox blank and click “revert”, if the instructor wants to go to a different student’s view he just need to enter the new student’s id and click on “revert”.

* Requirement: View on specific date:
:We decided to include a date box which on clicked on the date field a data picker pops up. We have added this picker as it makes sense to just click on which date instead of typing the whole date.

==Repository==
[https://github.com/chaitanya91k/expertiza Expertiza Github link]
==Screencast==
Screencast [https://youtu.be/WrJm6csM3mo link] to our demonstration

CSC/ECE 517 Fall 2016/E1657. Introduce a Student View for instructors

2016-11-04T23:19:34Z

Ckonda:

'''NOTE: The pull request will not pass the build.Its not due to our changes but due to some unrelated test failure.'''
__TOC__

==Background==
[http://expertiza.ncsu.edu/ Expertiza] is a web based open source peer reviewing tool based on [http://rubyonrails.org/ Ruby on Rails] developed and maintained by current and past students of [https://en.wikipedia.org/wiki/North_Carolina_State_University North Carolina State University], Raleigh. Students will be able to manage all their project submissions, project teamups, topic selections etc. Few of the notable features include:
* Instructor can control most of the stuff that is related to each course.
* Student can control who he/she wants to team up with etc.
* They can provide feedback to each of the topics.
* Instructor can make use of the various submission phases available.
== Introduction ==
Our project is to introduce a Student view to the instructors.The goal of this project is to provide instructor with a functionality using which an instructor can switch to student view and see how the student view looks like. The instructor will also be able to go to future date and see how student view looks like in future date.

==Project Requirements==
* Introduce a "Student View Button" on Instructors UI to switch to student view.
* Introduce a Revert to instructor View" on Instructor's Student UI
* Time travel in Student View.

==Working==
On the right top, left to the logout button , anyone having access to view as instructor gets a textbox and a button saying "Student View". in-order to view as a student you have to type in the students ID and press '''Student View''' button. You can exactly see what the student's page looks like.
[[File:HomeK6.jpg]]
 
If you need to revert back to instructor view you just have to leave the text box empty and press the '''Revert''' button. This takes you to the instructors view again. Else if you need another students view, just type in the students ID and press '''Revert'''.
[[File:HomeK3.jpg]]
 
We also have implemented a time travel feature where you can go to a particular date and see what a student see on that day. You can find this feature as soon as you go to a student ID. You have to select a day you need to travel to, type in the student ID and submit. Boom! you got he student view as on the date given.
[[File:HomeK4.jpg]]

==Implementation==
* Introduce a "Switch to Student View Button" on Instructors UI
:A 'Student View' button was added in the top right portion of menu-bar for instructor. This button allows instructor to see the student view. This button is linked to impersonate action of [https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/controllers/impersonate_controller.rb Impersonate_controller]. The button was simply added in menu-bar view. When the button is clicked, it calls <code>impersonate</code> method in <code>impersonate controller</code> which loads new view as student for provided student id. 

:Required changes in 1 files : 
:[https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/views/shared/_navigation.html.erb navigation.html] 
<pre>
<% if current_user.role.name == "Instructor" or current_user.role.name == "Administrator"%>
<%= form_for :user, url: '/impersonate/impersonate' do |f| %>
<TABLE>
<TR>
<TD><%= f.text_field :name, {:size => 10,:class => 'form-control input-sm', :autocomplete => "off",placeholder: "User ID"} %></TD>
<TD><%= f.submit 'Student View', :class=>"btn btn-primary input-sm"%></TD>
</TR>
</TABLE>
<% end %>
<% end %>
</pre>
* Introduce a Revert to instructor View" on Instructor's Student UI
:Once instructor impersonate to a student view, a Revert button appears which when clicked revert back to instructor view from impersonated student view. Once the student view is loaded by instructor,<code>session[:superuser]</code> is set and based on this flag a revert button will be displayed. 

* Time travel in Student View.
:Required changes in 4 files : 
:[https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/views/shared/_navigation.html.erb navigation.html] 
<div class="field">
<%= f.date_field :goto_date, :order => [:month,:day, :year],:value => Date.today %>
</div>
:First, we introduced a date box where you can select a date from the UI. 
[https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/controllers/impersonate_controller.rb Impersonate_controller] 
if !params[:impersonate][:goto_date].empty?
User.goto_date=params[:impersonate][:goto_date]
end
:In this controller, we took the value from UI and store the same in User model. 
:[https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/models/user.rb user.rb] 
attr_accessible :goto_date
def self.goto_date=(val)
@goto_date=val
end
def self.goto_date
@goto_date
end
:The value from the above controller is stored in Users model object (not instance) as goto_date. Thus you can access this date through out the sessions. 
:[https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/models/due_date.rb due_date.rb] 

def self.get_next_due_date(assignment_id, topic_id = nil)
(User.goto_date.nil?)? goto_date = Time.now : goto_date = (User.goto_date)
if Assignment.find(assignment_id).staggered_deadline?
next_due_date = TopicDueDate.where(['parent_id = ? and due_at >= ?', topic_id, Time.now]).first
next_due_date = TopicDueDate.where(['parent_id = ? and due_at >= ?', topic_id, goto_date]).first
topic_due_date_size = TopicDueDate.where(parent_id: topic_id).size
following_assignment_due_dates = AssignmentDueDate.where(parent_id: assignment_id)[topic_due_date_size..-1]
following_assignment_due_dates.each do |assignment_due_date|
if assignment_due_date.due_at >= Time.now
if assignment_due_date.due_at >= goto_date
next_due_date = assignment_due_date
break
end
end
end
else
next_due_date = AssignmentDueDate.where(['parent_id = ? && due_at >= ?', assignment_id, Time.now]).first
next_due_date = AssignmentDueDate.where(['parent_id = ? && due_at >= ?', assignment_id, goto_date]).first
end
next_due_date
end

:When ever the system calculates due dates, the time is taken from goto_date that we have stored above in Users model. 

==Testing via UI==
* Login in as Instructor.
*Create assignment. I have created one with name Test_Changes with submission deadline Nov 09 and review Deadline Nov 14. Add all the student in course for this assignment
[[File:Svk1.jpg]] 
 
 
*Switch to student view. Once switched to student view you can see the assignment with submission deadline Nov 09.
[[File:Sv2.jpg]] 
 
 
*Go to future date and view the assignment list. I went to Nov 10 in future and we can see that the current phase for our assignment is review.
[[File:Svk3.jpg]] 
[[File:Svk4.jpg]]

==Why These Changes?==
* Requirement: Add a “student view” button for instructors.
:As we were required to add a button , it makes more sense to add a similar button used across the application. Thus we choose class="btn btn-primary" for buttons and :class => 'form-control input-sm' for textboxes.

* Requirement: Introduce a revert button to go back to instructor:
:After an instructor enters a student ID of a student and enters student view, there should be a way to go back to instructors . Thus we have introduced a revert button. Also if the instructor wants to go to a different student’s view he should be able to do so as well. Making these two tasks possible with single textbox and button was better instead of an extra button to go back to instructors view. Now to go back to instructors view, instructor has to leave the textbox blank and click “revert”, if the instructor wants to go to a different student’s view he just need to enter the new student’s id and click on “revert”.

* Requirement: View on specific date:
:We decided to include a date box which on clicked on the date field a data picker pops up. We have added this picker as it makes sense to just click on which date instead of typing the whole date.

==Repository==
[https://github.com/chaitanya91k/expertiza Expertiza Github link]
==Screencast==
Screencast [https://youtu.be/WrJm6csM3mo link] to our demonstration

CSC/ECE 517 Fall 2016/E1657. Introduce a Student View for instructors

2016-11-04T23:19:15Z

Ckonda:

'''Note: The pull request will not pass the build.Its not due to our changes but due to some unrelated test failure.'''
__TOC__

==Background==
[http://expertiza.ncsu.edu/ Expertiza] is a web based open source peer reviewing tool based on [http://rubyonrails.org/ Ruby on Rails] developed and maintained by current and past students of [https://en.wikipedia.org/wiki/North_Carolina_State_University North Carolina State University], Raleigh. Students will be able to manage all their project submissions, project teamups, topic selections etc. Few of the notable features include:
* Instructor can control most of the stuff that is related to each course.
* Student can control who he/she wants to team up with etc.
* They can provide feedback to each of the topics.
* Instructor can make use of the various submission phases available.
== Introduction ==
Our project is to introduce a Student view to the instructors.The goal of this project is to provide instructor with a functionality using which an instructor can switch to student view and see how the student view looks like. The instructor will also be able to go to future date and see how student view looks like in future date.

==Project Requirements==
* Introduce a "Student View Button" on Instructors UI to switch to student view.
* Introduce a Revert to instructor View" on Instructor's Student UI
* Time travel in Student View.

==Working==
On the right top, left to the logout button , anyone having access to view as instructor gets a textbox and a button saying "Student View". in-order to view as a student you have to type in the students ID and press '''Student View''' button. You can exactly see what the student's page looks like.
[[File:HomeK6.jpg]]
 
If you need to revert back to instructor view you just have to leave the text box empty and press the '''Revert''' button. This takes you to the instructors view again. Else if you need another students view, just type in the students ID and press '''Revert'''.
[[File:HomeK3.jpg]]
 
We also have implemented a time travel feature where you can go to a particular date and see what a student see on that day. You can find this feature as soon as you go to a student ID. You have to select a day you need to travel to, type in the student ID and submit. Boom! you got he student view as on the date given.
[[File:HomeK4.jpg]]

==Implementation==
* Introduce a "Switch to Student View Button" on Instructors UI
:A 'Student View' button was added in the top right portion of menu-bar for instructor. This button allows instructor to see the student view. This button is linked to impersonate action of [https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/controllers/impersonate_controller.rb Impersonate_controller]. The button was simply added in menu-bar view. When the button is clicked, it calls <code>impersonate</code> method in <code>impersonate controller</code> which loads new view as student for provided student id. 

:Required changes in 1 files : 
:[https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/views/shared/_navigation.html.erb navigation.html] 
<pre>
<% if current_user.role.name == "Instructor" or current_user.role.name == "Administrator"%>
<%= form_for :user, url: '/impersonate/impersonate' do |f| %>
<TABLE>
<TR>
<TD><%= f.text_field :name, {:size => 10,:class => 'form-control input-sm', :autocomplete => "off",placeholder: "User ID"} %></TD>
<TD><%= f.submit 'Student View', :class=>"btn btn-primary input-sm"%></TD>
</TR>
</TABLE>
<% end %>
<% end %>
</pre>
* Introduce a Revert to instructor View" on Instructor's Student UI
:Once instructor impersonate to a student view, a Revert button appears which when clicked revert back to instructor view from impersonated student view. Once the student view is loaded by instructor,<code>session[:superuser]</code> is set and based on this flag a revert button will be displayed. 

* Time travel in Student View.
:Required changes in 4 files : 
:[https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/views/shared/_navigation.html.erb navigation.html] 
<div class="field">
<%= f.date_field :goto_date, :order => [:month,:day, :year],:value => Date.today %>
</div>
:First, we introduced a date box where you can select a date from the UI. 
[https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/controllers/impersonate_controller.rb Impersonate_controller] 
if !params[:impersonate][:goto_date].empty?
User.goto_date=params[:impersonate][:goto_date]
end
:In this controller, we took the value from UI and store the same in User model. 
:[https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/models/user.rb user.rb] 
attr_accessible :goto_date
def self.goto_date=(val)
@goto_date=val
end
def self.goto_date
@goto_date
end
:The value from the above controller is stored in Users model object (not instance) as goto_date. Thus you can access this date through out the sessions. 
:[https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/models/due_date.rb due_date.rb] 

def self.get_next_due_date(assignment_id, topic_id = nil)
(User.goto_date.nil?)? goto_date = Time.now : goto_date = (User.goto_date)
if Assignment.find(assignment_id).staggered_deadline?
next_due_date = TopicDueDate.where(['parent_id = ? and due_at >= ?', topic_id, Time.now]).first
next_due_date = TopicDueDate.where(['parent_id = ? and due_at >= ?', topic_id, goto_date]).first
topic_due_date_size = TopicDueDate.where(parent_id: topic_id).size
following_assignment_due_dates = AssignmentDueDate.where(parent_id: assignment_id)[topic_due_date_size..-1]
following_assignment_due_dates.each do |assignment_due_date|
if assignment_due_date.due_at >= Time.now
if assignment_due_date.due_at >= goto_date
next_due_date = assignment_due_date
break
end
end
end
else
next_due_date = AssignmentDueDate.where(['parent_id = ? && due_at >= ?', assignment_id, Time.now]).first
next_due_date = AssignmentDueDate.where(['parent_id = ? && due_at >= ?', assignment_id, goto_date]).first
end
next_due_date
end

:When ever the system calculates due dates, the time is taken from goto_date that we have stored above in Users model. 

==Testing via UI==
* Login in as Instructor.
*Create assignment. I have created one with name Test_Changes with submission deadline Nov 09 and review Deadline Nov 14. Add all the student in course for this assignment
[[File:Svk1.jpg]] 
 
 
*Switch to student view. Once switched to student view you can see the assignment with submission deadline Nov 09.
[[File:Sv2.jpg]] 
 
 
*Go to future date and view the assignment list. I went to Nov 10 in future and we can see that the current phase for our assignment is review.
[[File:Svk3.jpg]] 
[[File:Svk4.jpg]]

==Why These Changes?==
* Requirement: Add a “student view” button for instructors.
:As we were required to add a button , it makes more sense to add a similar button used across the application. Thus we choose class="btn btn-primary" for buttons and :class => 'form-control input-sm' for textboxes.

* Requirement: Introduce a revert button to go back to instructor:
:After an instructor enters a student ID of a student and enters student view, there should be a way to go back to instructors . Thus we have introduced a revert button. Also if the instructor wants to go to a different student’s view he should be able to do so as well. Making these two tasks possible with single textbox and button was better instead of an extra button to go back to instructors view. Now to go back to instructors view, instructor has to leave the textbox blank and click “revert”, if the instructor wants to go to a different student’s view he just need to enter the new student’s id and click on “revert”.

* Requirement: View on specific date:
:We decided to include a date box which on clicked on the date field a data picker pops up. We have added this picker as it makes sense to just click on which date instead of typing the whole date.

==Repository==
[https://github.com/chaitanya91k/expertiza Expertiza Github link]
==Screencast==
Screencast [https://youtu.be/WrJm6csM3mo link] to our demonstration

CSC/ECE 517 Fall 2016/E1657. Introduce a Student View for instructors

2016-11-04T23:16:48Z

Ckonda: /* Screencast */

Note: The pull request will not pass the build.Its not due to our changes but due to some unrelated test failure.
__TOC__

==Background==
[http://expertiza.ncsu.edu/ Expertiza] is a web based open source peer reviewing tool based on [http://rubyonrails.org/ Ruby on Rails] developed and maintained by current and past students of [https://en.wikipedia.org/wiki/North_Carolina_State_University North Carolina State University], Raleigh. Students will be able to manage all their project submissions, project teamups, topic selections etc. Few of the notable features include:
* Instructor can control most of the stuff that is related to each course.
* Student can control who he/she wants to team up with etc.
* They can provide feedback to each of the topics.
* Instructor can make use of the various submission phases available.
== Introduction ==
Our project is to introduce a Student view to the instructors.The goal of this project is to provide instructor with a functionality using which an instructor can switch to student view and see how the student view looks like. The instructor will also be able to go to future date and see how student view looks like in future date.

==Project Requirements==
* Introduce a "Student View Button" on Instructors UI to switch to student view.
* Introduce a Revert to instructor View" on Instructor's Student UI
* Time travel in Student View.

==Working==
On the right top, left to the logout button , anyone having access to view as instructor gets a textbox and a button saying "Student View". in-order to view as a student you have to type in the students ID and press '''Student View''' button. You can exactly see what the student's page looks like.
[[File:HomeK6.jpg]]
 
If you need to revert back to instructor view you just have to leave the text box empty and press the '''Revert''' button. This takes you to the instructors view again. Else if you need another students view, just type in the students ID and press '''Revert'''.
[[File:HomeK3.jpg]]
 
We also have implemented a time travel feature where you can go to a particular date and see what a student see on that day. You can find this feature as soon as you go to a student ID. You have to select a day you need to travel to, type in the student ID and submit. Boom! you got he student view as on the date given.
[[File:HomeK4.jpg]]

==Implementation==
* Introduce a "Switch to Student View Button" on Instructors UI
:A 'Student View' button was added in the top right portion of menu-bar for instructor. This button allows instructor to see the student view. This button is linked to impersonate action of [https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/controllers/impersonate_controller.rb Impersonate_controller]. The button was simply added in menu-bar view. When the button is clicked, it calls <code>impersonate</code> method in <code>impersonate controller</code> which loads new view as student for provided student id. 

:Required changes in 1 files : 
:[https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/views/shared/_navigation.html.erb navigation.html] 
<pre>
<% if current_user.role.name == "Instructor" or current_user.role.name == "Administrator"%>
<%= form_for :user, url: '/impersonate/impersonate' do |f| %>
<TABLE>
<TR>
<TD><%= f.text_field :name, {:size => 10,:class => 'form-control input-sm', :autocomplete => "off",placeholder: "User ID"} %></TD>
<TD><%= f.submit 'Student View', :class=>"btn btn-primary input-sm"%></TD>
</TR>
</TABLE>
<% end %>
<% end %>
</pre>
* Introduce a Revert to instructor View" on Instructor's Student UI
:Once instructor impersonate to a student view, a Revert button appears which when clicked revert back to instructor view from impersonated student view. Once the student view is loaded by instructor,<code>session[:superuser]</code> is set and based on this flag a revert button will be displayed. 

* Time travel in Student View.
:Required changes in 4 files : 
:[https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/views/shared/_navigation.html.erb navigation.html] 
<div class="field">
<%= f.date_field :goto_date, :order => [:month,:day, :year],:value => Date.today %>
</div>
:First, we introduced a date box where you can select a date from the UI. 
[https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/controllers/impersonate_controller.rb Impersonate_controller] 
if !params[:impersonate][:goto_date].empty?
User.goto_date=params[:impersonate][:goto_date]
end
:In this controller, we took the value from UI and store the same in User model. 
:[https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/models/user.rb user.rb] 
attr_accessible :goto_date
def self.goto_date=(val)
@goto_date=val
end
def self.goto_date
@goto_date
end
:The value from the above controller is stored in Users model object (not instance) as goto_date. Thus you can access this date through out the sessions. 
:[https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/models/due_date.rb due_date.rb] 

def self.get_next_due_date(assignment_id, topic_id = nil)
(User.goto_date.nil?)? goto_date = Time.now : goto_date = (User.goto_date)
if Assignment.find(assignment_id).staggered_deadline?
next_due_date = TopicDueDate.where(['parent_id = ? and due_at >= ?', topic_id, Time.now]).first
next_due_date = TopicDueDate.where(['parent_id = ? and due_at >= ?', topic_id, goto_date]).first
topic_due_date_size = TopicDueDate.where(parent_id: topic_id).size
following_assignment_due_dates = AssignmentDueDate.where(parent_id: assignment_id)[topic_due_date_size..-1]
following_assignment_due_dates.each do |assignment_due_date|
if assignment_due_date.due_at >= Time.now
if assignment_due_date.due_at >= goto_date
next_due_date = assignment_due_date
break
end
end
end
else
next_due_date = AssignmentDueDate.where(['parent_id = ? && due_at >= ?', assignment_id, Time.now]).first
next_due_date = AssignmentDueDate.where(['parent_id = ? && due_at >= ?', assignment_id, goto_date]).first
end
next_due_date
end

:When ever the system calculates due dates, the time is taken from goto_date that we have stored above in Users model. 

==Testing via UI==
* Login in as Instructor.
*Create assignment. I have created one with name Test_Changes with submission deadline Nov 09 and review Deadline Nov 14. Add all the student in course for this assignment
[[File:Svk1.jpg]] 
 
 
*Switch to student view. Once switched to student view you can see the assignment with submission deadline Nov 09.
[[File:Sv2.jpg]] 
 
 
*Go to future date and view the assignment list. I went to Nov 10 in future and we can see that the current phase for our assignment is review.
[[File:Svk3.jpg]] 
[[File:Svk4.jpg]]

==Why These Changes?==
* Requirement: Add a “student view” button for instructors.
:As we were required to add a button , it makes more sense to add a similar button used across the application. Thus we choose class="btn btn-primary" for buttons and :class => 'form-control input-sm' for textboxes.

* Requirement: Introduce a revert button to go back to instructor:
:After an instructor enters a student ID of a student and enters student view, there should be a way to go back to instructors . Thus we have introduced a revert button. Also if the instructor wants to go to a different student’s view he should be able to do so as well. Making these two tasks possible with single textbox and button was better instead of an extra button to go back to instructors view. Now to go back to instructors view, instructor has to leave the textbox blank and click “revert”, if the instructor wants to go to a different student’s view he just need to enter the new student’s id and click on “revert”.

* Requirement: View on specific date:
:We decided to include a date box which on clicked on the date field a data picker pops up. We have added this picker as it makes sense to just click on which date instead of typing the whole date.

==Repository==
[https://github.com/chaitanya91k/expertiza Expertiza Github link]
==Screencast==
Screencast [https://youtu.be/WrJm6csM3mo link] to our demonstration

CSC/ECE 517 Fall 2016/E1657. Introduce a Student View for instructors

2016-11-04T22:55:48Z

Ckonda: /* Screencast */

CSC/ECE 517 Fall 2016/E1657. Introduce a Student View for instructors

2016-11-04T22:55:32Z

Ckonda:

CSC/ECE 517 Fall 2016/E1657. Introduce a Student View for instructors

2016-11-04T22:54:10Z

Ckonda: /* Why These Changes? */

CSC/ECE 517 Fall 2016/E1657. Introduce a Student View for instructors

2016-11-04T22:53:54Z

Ckonda:

CSC/ECE 517 Fall 2016/E1657. Introduce a Student View for instructors

2016-11-04T22:24:14Z

Ckonda: /* Implementation */

Note: The pull request will not pass the build.Its not due to our changes but due to some unrelated test failure.
__TOC__

==Background==
[http://expertiza.ncsu.edu/ Expertiza] is a web based open source peer reviewing tool based on [http://rubyonrails.org/ Ruby on Rails] developed and maintained by current and past students of [https://en.wikipedia.org/wiki/North_Carolina_State_University North Carolina State University], Raleigh. Students will be able to manage all their project submissions, project teamups, topic selections etc. Few of the notable features include:
* Instructor can control most of the stuff that is related to each course.
* Student can control who he/she wants to team up with etc.
* They can provide feedback to each of the topics.
* Instructor can make use of the various submission phases available.
== Introduction ==
Our project is to introduce a Student view to the instructors.The goal of this project is to provide instructor with a functionality using which an instructor can switch to student view and see how the student view looks like. The instructor will also be able to go to future date and see how student view looks like in future date.

==Project Requirements==
* Introduce a "Student View Button" on Instructors UI to switch to student view.
* Introduce a Revert to instructor View" on Instructor's Student UI
* Time travel in Student View.

==Working==
On the right top, left to the logout button , anyone having access to view as instructor gets a textbox and a button saying "Student View". in-order to view as a student you have to type in the students ID and press '''Student View''' button. You can exactly see what the student's page looks like.
[[File:HomeK6.jpg]]
 
If you need to revert back to instructor view you just have to leave the text box empty and press the '''Revert''' button. This takes you to the instructors view again. Else if you need another students view, just type in the students ID and press '''Revert'''.
[[File:HomeK3.jpg]]
 
We also have implemented a time travel feature where you can go to a particular date and see what a student see on that day. You can find this feature as soon as you go to a student ID. You have to select a day you need to travel to, type in the student ID and submit. Boom! you got he student view as on the date given.
[[File:HomeK4.jpg]]

==Implementation==
* Introduce a "Switch to Student View Button" on Instructors UI
:A 'Student View' button was added in the top right portion of menu-bar for instructor. This button allows instructor to see the student view. This button is linked to impersonate action of [https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/controllers/impersonate_controller.rb Impersonate_controller]. The button was simply added in menu-bar view. When the button is clicked, it calls <code>impersonate</code> method in <code>impersonate controller</code> which loads new view as student for provided student id. 

:Required changes in 1 files : 
:[https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/views/shared/_navigation.html.erb navigation.html] 
<pre>
<% if current_user.role.name == "Instructor" or current_user.role.name == "Administrator"%>
<%= form_for :user, url: '/impersonate/impersonate' do |f| %>
<TABLE>
<TR>
<TD><%= f.text_field :name, {:size => 10,:class => 'form-control input-sm', :autocomplete => "off",placeholder: "User ID"} %></TD>
<TD><%= f.submit 'Student View', :class=>"btn btn-primary input-sm"%></TD>
</TR>
</TABLE>
<% end %>
<% end %>
</pre>
* Introduce a Revert to instructor View" on Instructor's Student UI
:Once instructor impersonate to a student view, a Revert button appears which when clicked revert back to instructor view from impersonated student view. Once the student view is loaded by instructor,<code>session[:superuser]</code> is set and based on this flag a revert button will be displayed. 

* Time travel in Student View.
:Required changes in 4 files : 
:[https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/views/shared/_navigation.html.erb navigation.html] 
<div class="field">
<%= f.date_field :goto_date, :order => [:month,:day, :year],:value => Date.today %>
</div>
:First, we introduced a date box where you can select a date from the UI. 
[https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/controllers/impersonate_controller.rb Impersonate_controller] 
if !params[:impersonate][:goto_date].empty?
User.goto_date=params[:impersonate][:goto_date]
end
:In this controller, we took the value from UI and store the same in User model. 
:[https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/models/user.rb user.rb] 
attr_accessible :goto_date
def self.goto_date=(val)
@goto_date=val
end
def self.goto_date
@goto_date
end
:The value from the above controller is stored in Users model object (not instance) as goto_date. Thus you can access this date through out the sessions. 
:[https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/models/due_date.rb due_date.rb] 

def self.get_next_due_date(assignment_id, topic_id = nil)
(User.goto_date.nil?)? goto_date = Time.now : goto_date = (User.goto_date)
if Assignment.find(assignment_id).staggered_deadline?
next_due_date = TopicDueDate.where(['parent_id = ? and due_at >= ?', topic_id, Time.now]).first
next_due_date = TopicDueDate.where(['parent_id = ? and due_at >= ?', topic_id, goto_date]).first
topic_due_date_size = TopicDueDate.where(parent_id: topic_id).size
following_assignment_due_dates = AssignmentDueDate.where(parent_id: assignment_id)[topic_due_date_size..-1]
following_assignment_due_dates.each do |assignment_due_date|
if assignment_due_date.due_at >= Time.now
if assignment_due_date.due_at >= goto_date
next_due_date = assignment_due_date
break
end
end
end
else
next_due_date = AssignmentDueDate.where(['parent_id = ? && due_at >= ?', assignment_id, Time.now]).first
next_due_date = AssignmentDueDate.where(['parent_id = ? && due_at >= ?', assignment_id, goto_date]).first
end
next_due_date
end

:When ever the system calculates due dates, the time is taken from goto_date that we have stored above in Users model. 

==Repository==
[https://github.com/chaitanya91k/expertiza Expertiza Github link]

CSC/ECE 517 Fall 2016/E1657. Introduce a Student View for instructors

2016-11-04T22:18:54Z

Ckonda: /* Implementation */

Note: The pull request will not pass the build.Its not due to our changes but due to some unrelated test failure.
__TOC__

==Background==
[http://expertiza.ncsu.edu/ Expertiza] is a web based open source peer reviewing tool based on [http://rubyonrails.org/ Ruby on Rails] developed and maintained by current and past students of [https://en.wikipedia.org/wiki/North_Carolina_State_University North Carolina State University], Raleigh. Students will be able to manage all their project submissions, project teamups, topic selections etc. Few of the notable features include:
* Instructor can control most of the stuff that is related to each course.
* Student can control who he/she wants to team up with etc.
* They can provide feedback to each of the topics.
* Instructor can make use of the various submission phases available.
== Introduction ==
Our project is to introduce a Student view to the instructors.
==Project Requirements==
* Introduce a "Student View Button" on Instructors UI to switch to student view.
* Introduce a Revert to instructor View" on Instructor's Student UI
* Time travel in Student View.
 The goal of this project is to provide instructor with a functionality using which an instructor can switch to student view and see how the student view looks like. The instructor will also be able to go to future date and see how student view looks like in future date.

==Working==
On the right top, left to the logout button , anyone having access to view as instructor gets a textbox and a button saying "Student View". in-order to view as a student you have to type in the students ID and press '''Student View''' button. You can exactly see what the student's page looks like.
[[File:HomeK6.jpg]]
 
If you need to revert back to instructor view you just have to leave the text box empty and press the '''Revert''' button. This takes you to the instructors view again. Else if you need another students view, just type in the students ID and press '''Revert'''.
[[File:HomeK3.jpg]]
 
We also have implemented a time travel feature where you can go to a particular date and see what a student see on that day. You can find this feature as soon as you go to a student ID. You have to select a day you need to travel to, type in the student ID and submit. Boom! you got he student view as on the date given.
[[File:HomeK4.jpg]]

==Implementation==
* Introduce a "Switch to Student View Button" on Instructors UI
A 'Student View' button was added in the top right portion of menu-bar for instructor. This button allows instructor to see the student view. This button
is linked to impersonate action of [https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/controllers/impersonate_controller.rb Impersonate_controller]. The button was simply added in menu-bar view. When the button is clicked, it calls <code>impersonate</code> method in <code>impersonate controller</code> which loads new view as student for provided student id. 
Required changes in 1 files : 
[https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/views/shared/_navigation.html.erb navigation.html] 
'''''/app/views/shared/_navigation.html'''''
<pre>
<% if current_user.role.name == "Instructor" or current_user.role.name == "Administrator"%>
<%= form_for :user, url: '/impersonate/impersonate' do |f| %>
<TABLE>
<TR>
<TD><%= f.text_field :name, {:size => 10,:class => 'form-control input-sm', :autocomplete => "off",placeholder: "User ID"} %></TD>
<TD><%= f.submit 'Student View', :class=>"btn btn-primary input-sm"%></TD>
</TR>
</TABLE>
<% end %>
<% end %>
</pre>
* Introduce a Revert to instructor View" on Instructor's Student UI
Once instructor impersonate to a student view, a Revert button appears which when clicked revert back to instructor view from impersonated student view. Once the student view is loaded by instructor,<code>session[:superuser]</code> is set and based on this flag a revert button will be displayed. 

* Time travel in Student View.
Required changes in 4 files : 
[https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/views/shared/_navigation.html.erb navigation.html] 
<div class="field">
<%= f.date_field :goto_date, :order => [:month,:day, :year],:value => Date.today %>
</div>
First, we introduced a date box where you can select a date from the UI. 
[https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/controllers/impersonate_controller.rb Impersonate_controller] 
if !params[:impersonate][:goto_date].empty?
User.goto_date=params[:impersonate][:goto_date]
end
In this controller, we took the value from UI and store the same in User model. 
[https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/models/user.rb user.rb] 
class User < ActiveRecord::Base
attr_accessible :goto_date
def self.goto_date=(val)
@goto_date=val
end
def self.goto_date
@goto_date
end
The value from the above controller is stored in Users model object (not instance) as goto_date. Thus you can access this date through out the sessions. 
[https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/models/due_date.rb due_date.rb] 

def self.get_next_due_date(assignment_id, topic_id = nil)
(User.goto_date.nil?)? goto_date = Time.now : goto_date = (User.goto_date)
if Assignment.find(assignment_id).staggered_deadline?
next_due_date = TopicDueDate.where(['parent_id = ? and due_at >= ?', topic_id, Time.now]).first
next_due_date = TopicDueDate.where(['parent_id = ? and due_at >= ?', topic_id, goto_date]).first
topic_due_date_size = TopicDueDate.where(parent_id: topic_id).size
following_assignment_due_dates = AssignmentDueDate.where(parent_id: assignment_id)[topic_due_date_size..-1]
following_assignment_due_dates.each do |assignment_due_date|
if assignment_due_date.due_at >= Time.now
if assignment_due_date.due_at >= goto_date
next_due_date = assignment_due_date
break
end
end
end
else
next_due_date = AssignmentDueDate.where(['parent_id = ? && due_at >= ?', assignment_id, Time.now]).first
next_due_date = AssignmentDueDate.where(['parent_id = ? && due_at >= ?', assignment_id, goto_date]).first
end
next_due_date
end

When ever the system calculates due dates, the time is taken from goto_date that we have stored above in Users model. 

==Repository==
[https://github.com/chaitanya91k/expertiza Expertiza Github link]

CSC/ECE 517 Fall 2016/E1657. Introduce a Student View for instructors

2016-11-04T22:15:19Z

Ckonda: /* Implementation */

Note: The pull request will not pass the build.Its not due to our changes but due to some unrelated test failure.
__TOC__

==Background==
[http://expertiza.ncsu.edu/ Expertiza] is a web based open source peer reviewing tool based on [http://rubyonrails.org/ Ruby on Rails] developed and maintained by current and past students of [https://en.wikipedia.org/wiki/North_Carolina_State_University North Carolina State University], Raleigh. Students will be able to manage all their project submissions, project teamups, topic selections etc. Few of the notable features include:
* Instructor can control most of the stuff that is related to each course.
* Student can control who he/she wants to team up with etc.
* They can provide feedback to each of the topics.
* Instructor can make use of the various submission phases available.
== Introduction ==
Our project is to introduce a Student view to the instructors.
==Project Requirements==
* Introduce a "Student View Button" on Instructors UI to switch to student view.
* Introduce a Revert to instructor View" on Instructor's Student UI
* Time travel in Student View.
 The goal of this project is to provide instructor with a functionality using which an instructor can switch to student view and see how the student view looks like. The instructor will also be able to go to future date and see how student view looks like in future date.

==Working==
On the right top, left to the logout button , anyone having access to view as instructor gets a textbox and a button saying "Student View". in-order to view as a student you have to type in the students ID and press '''Student View''' button. You can exactly see what the student's page looks like.
[[File:HomeK6.jpg]]
 
If you need to revert back to instructor view you just have to leave the text box empty and press the '''Revert''' button. This takes you to the instructors view again. Else if you need another students view, just type in the students ID and press '''Revert'''.
[[File:HomeK3.jpg]]
 
We also have implemented a time travel feature where you can go to a particular date and see what a student see on that day. You can find this feature as soon as you go to a student ID. You have to select a day you need to travel to, type in the student ID and submit. Boom! you got he student view as on the date given.
[[File:HomeK4.jpg]]

==Implementation==
* Introduce a "Switch to Student View Button" on Instructors UI
A 'Student View' button was added in the top right portion of menu-bar for instructor. This button allows instructor to see the student view. This button
is linked to impersonate action of [https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/controllers/impersonate_controller.rb Impersonate_controller]. The button was simply added in menu-bar view. When the button is clicked, it calls <code>impersonate</code> method in <code>impersonate controller</code> which loads new view as student for provided student id. 
Required changes in 1 files : 
[https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/views/shared/_navigation.html.erb navigation.html] 
'''''/app/views/shared/_navigation.html'''''
<% if current_user.role.name == "Instructor" or current_user.role.name == "Administrator"%>
<%= form_for :user, url: '/impersonate/impersonate' do |f| %>
<TABLE>
<TR>
<TD><%= f.text_field :name, {:size => 10,:class => 'form-control input-sm', :autocomplete => "off",placeholder: "User ID"} %></TD>
<TD><%= f.submit 'Student View', :class=>"btn btn-primary input-sm"%></TD>
</TR>
</TABLE>
<% end %>
<% end %>

* Introduce a Revert to instructor View" on Instructor's Student UI
Once instructor impersonate to a student view, a Revert button appears which when clicked revert back to instructor view from impersonated student view. Once the student view is loaded by instructor,<code>session[:superuser]</code> is set and based on this flag a revert button will be displayed. 

* Time travel in Student View.
Required changes in 4 files : 
[https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/views/shared/_navigation.html.erb navigation.html] 
<div class="field">
<%= f.date_field :goto_date, :order => [:month,:day, :year],:value => Date.today %>
</div>
First, we introduced a date box where you can select a date from the UI. 
[https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/controllers/impersonate_controller.rb Impersonate_controller] 
if !params[:impersonate][:goto_date].empty?
User.goto_date=params[:impersonate][:goto_date]
end
In this controller, we took the value from UI and store the same in User model. 
[https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/models/user.rb user.rb] 
class User < ActiveRecord::Base
attr_accessible :goto_date
def self.goto_date=(val)
@goto_date=val
end
def self.goto_date
@goto_date
end
The value from the above controller is stored in Users model object (not instance) as goto_date. Thus you can access this date through out the sessions. 
[https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/models/due_date.rb due_date.rb] 

def self.get_next_due_date(assignment_id, topic_id = nil)
(User.goto_date.nil?)? goto_date = Time.now : goto_date = (User.goto_date)
if Assignment.find(assignment_id).staggered_deadline?
next_due_date = TopicDueDate.where(['parent_id = ? and due_at >= ?', topic_id, Time.now]).first
next_due_date = TopicDueDate.where(['parent_id = ? and due_at >= ?', topic_id, goto_date]).first
topic_due_date_size = TopicDueDate.where(parent_id: topic_id).size
following_assignment_due_dates = AssignmentDueDate.where(parent_id: assignment_id)[topic_due_date_size..-1]
following_assignment_due_dates.each do |assignment_due_date|
if assignment_due_date.due_at >= Time.now
if assignment_due_date.due_at >= goto_date
next_due_date = assignment_due_date
break
end
end
end
else
next_due_date = AssignmentDueDate.where(['parent_id = ? && due_at >= ?', assignment_id, Time.now]).first
next_due_date = AssignmentDueDate.where(['parent_id = ? && due_at >= ?', assignment_id, goto_date]).first
end
next_due_date
end

When ever the system calculates due dates, the time is taken from goto_date that we have stored above in Users model. 

==Repository==
[https://github.com/chaitanya91k/expertiza Expertiza Github link]