Expertiza_Wiki - User contributions [en]

E1934 - Grading Audit Trail

2019-05-01T14:28:17Z

Amody: /* Reference */

=='''Introduction'''==

===Problem Statement===
After an instructor gave a grade to an assignment, there is no way to track who gave the grade.
A grading audit trail must be created and the following information needs to be stored:
:1. When a grade is assigned by an instructor, there needs to be an indication of who did it and when it was done.
:2. Comments previously provided by other instructors must also be preserved.

This information needs to be stored every time an instructor edits a grade/comment and clicks the save button.

Currently, there are two places need to add grading audit trail:
:1. '''Review grade''': Log in as instructor -> Manage -> Assignments -> View Review Report
:2. '''Submission grade''': Log in as instructor -> Manage -> Assignments -> View submissions

=='''Proposed Solution'''==

===Design===
We created a database called grading_history in the system which stores elements of instructor id, assignment id, grade type, student id, grade, comment, and timestamp.

We used MVC design to create a model, a controller, and a view for both of '''Review Grade''' and '''Submission Grade'''.

:Model: grading_history.rb. Has a list of attributes contains instructor id, assignment id, grade type, student id, grade, comment, and timestamp.
:Controller: grading_history_controller.rb. Saves a new entry into the database every time a review grade or submission grade is saved
:View: index_html.erb. Displays current submission or review's grading history. An existing example of this is a submission record in the system.

We modified grades controller, so that every time, a grade is submitted or edited, grading_history_controller.rb will call a method to create an entry saves into the database.

===Expected View===

==== The list submission page with the new "grade history" option====
[[Image: E1869-Screenshot-1.jpg|50]]

==== The review report page with the new "grade history" option====
[[File:E1869-Screenshot-2.jpg]]

==== Grade history for a given team====
[[File:E1869-Screenshot-3.jpg]]

===Diagram===
[[File:E1869_Grading_Audit_Trails_UML.jpg]]

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

Functional testing:

1. Test if SubmissionGradeHistory.create is being called when a submission grade is changed.
spec/controllers/grades_controller_spec.rb

2. Test if ReviewGradeHistory.create is being called when a submission grade is changed.
spec/controllers/review_mapping_controller_spec.rb

3. Test if GradeHistory.where is being called when grading history button is clicked.
spec/controllers/grading_histories_controller_test.rb

Feature Testing:

1. Test if the grading history is visible and shown in chronological order
spec/features/grade_histories_spec.rb
spec/features/helpers/grade_histories_helper.rb

===Code Changes===

==Files Modified==
*app/controllers/grades_controller.rb
'''
Creates a Grading History Record for every Submission grade edited by the instructor for a Team.
'''

*app/controllers/review_mapping_controller.rb
'''

Creates a Grading History Record for every Review grade edited by the instructor for a Student.
'''

* app/views/assignments/list_submissions.html.erb
'''
Add code to support view changes for Grade Record
'''

* app/views/reports/_review_report.html.erb
'''
Add code to support view changes for Grade Record
'''

==Files Added==

*app/controllers/grading_histories_controller.rb
'''
Calls the grading history view after validating Submission and Review Type.

'''

*app/models/grading_history.rb
'''
Model for Grading History.
'''

*app/models/review_grading_history.rb
'''
Model containing specifics of Review Grading History. Inherits Grading History.
'''

*app/models/submission_grading_history.rb
'''
Model containing specifics of Submission Grading History. Inherits Grading History.
'''

*app/views/grading_history/index_html.erb

'''
This is a view for grading audit trail, it will display all grading histories of a submission/review
'''

*spec/features/grade_histories_spec.rb

'''
Feature test to check if the grades appear in chronological order
'''

*spec/features/helpers/grade_histories_helper.rb

'''
Helper file to facilitate the above mentioned feature test.
'''

=='''Reference'''==
[https://expertiza.ncsu.edu/ Expertiza]

[http://wiki.expertiza.ncsu.edu/index.php/CSC/E1869_GRADING_AUDIT_TRAIL Previous Project Documentation]

[https://youtu.be/yyxX_kRYxLc Screencast]

[http://wiki.expertiza.ncsu.edu/index.php/Main_Page Expertiza_wiki]

[http://wiki.expertiza.ncsu.edu/index.php/Expertiza_documentation Expertiza Documentation]

[https://github.com/expertiza/expertiza Expertiza Github]

E1934 - Grading Audit Trail

2019-04-13T02:27:54Z

Amody:

=='''Introduction'''==

===Problem Statement===
After an instructor gave a grade to an assignment, there is no way to track who gave the grade.
A grading audit trail must be created and the following information needs to be stored:
:1. When a grade is assigned by an instructor, there needs to be an indication of who did it and when it was done.
:2. Comments previously provided by other instructors must also be preserved.

This information needs to be stored every time an instructor edits a grade/comment and clicks the save button.

Currently, there are two places need to add grading audit trail:
:1. '''Review grade''': Log in as instructor -> Manage -> Assignments -> View Review Report
:2. '''Submission grade''': Log in as instructor -> Manage -> Assignments -> View submissions

=='''Previous Work'''==
The team that worked previously was able to achieve the task fully. They were able to create a record when the grade of a student was changed. It also recorded a timestamp with it. There were able to complete all the assigned functionalities. The issue that was found is that any TA, an instructor was able to change the grade of a student which should not have been the case.

We plan to overcome this by adding a method which checks whether the logged in instructor/TA is of the same course and then allow him to carry out the tasks.

=='''Proposed Solution'''==

===Design===
We plan to create a database called grading_history in the system which stores elements of instructor id, assignment id, grade type, student id, grade, comment, and timestamp.

We will use MVC design to create a model, a controller, and a view for both of '''Review Grade''' and '''Submission Grade'''.

:Model: grading_history.rb. Has a list of attributes contains instructor id, assignment id, grade type, student id, grade, comment, and timestamp.
:Controller: grading_history_controller.rb. Saves a new entry into the database every time a review grade or submission grade is saved
:View: index_html.erb. Displays current submission or review's grading history. An existing example of this is a submission record in the system.

We will also need to modify grades controller, so that every time, a grade is submitted or edited, grading_history_controller.rb will call a method to create an entry saves into the database.

===Expected View===

==== The list submission page with the new "grade history" option====
[[Image: E1869-Screenshot-1.jpg|50]]

==== The review report page with the new "grade history" option====
[[File:E1869-Screenshot-2.jpg]]

==== Grade history for a given team====
[[File:E1869-Screenshot-3.jpg]]

===Diagram===
[[File:E1869_Grading_Audit_Trails_UML.jpg]]

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

Functional testing:

1. Test if SubmissionGradeHistory.create is being called when a submission grade is changed.
spec/controllers/grades_controller_spec.rb

2. Test if ReviewGradeHistory.create is being called when a submission grade is changed.
spec/controllers/review_mapping_controller_spec.rb

3. Test if GradeHistory.where is being called when grading history button is clicked.
spec/controllers/grading_histories_controller_test.rb

===Code Changes===

==Files to be Modified==
*app/controllers/grades_controller.rb
'''
Creates a Grading History Record for every Submission grade edited by the instructor for a Team.
'''

*app/controllers/review_mapping_controller.rb
'''

Creates a Grading History Record for every Review grade edited by the instructor for a Student.
'''

* app/views/assignments/list_submissions.html.erb
'''
Add code to support view changes for Grade Record
'''

* app/views/review_mapping/_review_report.html.erb
'''
Add code to support view changes for Grade Record
'''

==Files to be Added==

*app/controllers/grading_histories_controller.rb
'''
Calls the grading history view after validating Submission and Review Type.

'''

*app/models/grading_history.rb
'''
Model for Grading History.
'''

*app/models/review_grading_history.rb
'''
Model containing specifics of Review Grading History. Inherits Grading History.
'''

*app/models/submission_grading_history.rb
'''
Model containing specifics of Submission Grading History. Inherits Grading History.
'''

*app/views/grading_history/index_html.erb

'''
This is a view for grading audit trail, it will display all grading histories of a submission/review
'''

=='''Reference'''==
[https://expertiza.ncsu.edu/ Expertiza]

[http://wiki.expertiza.ncsu.edu/index.php/CSC/E1869_GRADING_AUDIT_TRAIL Previous Project Documentation]

[http://wiki.expertiza.ncsu.edu/index.php/Main_Page Expertiza_wiki]

[http://wiki.expertiza.ncsu.edu/index.php/Expertiza_documentation Expertiza Documentation]

[https://github.com/expertiza/expertiza Expertiza Github]

File:E1934-Screenshot-1.png

2019-04-13T02:19:09Z

Amody:

CSC/ECE 517 Spring 2019

2019-04-08T15:54:27Z

Amody:

*[[CSC/ECE 517 Spring 2019 - Project E1905. Refactor questionnaires_controller.rb]]
*[[CSC/ECE 517 Spring 2019 - Project E1916. Fix Code Climate issues in controllers with names beginning with A through N]]
*[[CSC/ECE 517 Spring 2019 - Project E1906. Refactor stage deadlines in Assignment.rb]]
*[[CSC/ECE 517 Spring 2019 - Project M1901 Implement missing WebAudio automation support]]
*[[CSC/ECE 517 Spring 2019 - Project E1917. Fix Code Climate issues in controllers with names beginning with P through Z]]
*[[CSC/ECE 517 Spring 2019 - Project E1921. Write tests for popup controller.rb]]
*[[CSC/ECE 517 Spring 2019 - M1902 Refactor bluetooth support for better maintainability]]
*[[CSC/ECE 517 Spring 2019 - E1922. Write tests for assessment360 controller.rb]]
*[[CSC/ECE 517 Spring 2019 - Project E1907 Refactor response controller]]
*[[CSC/ECE_517_Spring_2019_-_Project_E1903._Create_quiz_questionnaires_controller.rb]]
*[[CSC/ECE_517_Spring_2019_-_Project_E1913. Refactor_review_mapping_helper.rb]]
*[[CSC/ECE_517_Spring_2019_-_E1919_CodeClimate_Issues]]
*[[CSC/ECE_517_Spring_2019_-_Project_E1912. Export_Tagged_Comments]]
*[[CSC/ECE_517_Spring_2019/E1927_Let_Course_Staff_as_Well_as_Students_Do_Reviews]]
*[[E1911_Refactor_Criterion]]
*[[E1934 - Grading Audit Trail]]
*[[CSC/ECE 517 Spring 2019 - Project E1925. Refactor E1858. Github metrics integration]]

E1934 - Grading Audit Trail

2019-04-08T15:24:19Z

Amody: /* Reference */

=='''Introduction'''==

===Problem Statement===
After an instructor gave a grade to an assignment, there is no way to track who gave the grade.
A grading audit trail must be created and the following information needs to be stored:
:1. When a grade is assigned by an instructor, there needs to be an indication of who did it and when it was done.
:2. Comments previously provided by other instructors must also be preserved.

This information needs to be stored every time an instructor edits a grade/comment and clicks the save button.

Currently, there are two places need to add grading audit trail:
:1. '''Review grade''': Log in as instructor -> Manage -> Assignments -> View Review Report
:2. '''Submission grade''': Log in as instructor -> Manage -> Assignments -> View submissions

=='''Proposed Solution'''==

===Design===
We plan to create a database called grading_history in the system which stores elements of instructor id, assignment id, grade type, student id, grade, comment, and timestamp.

We will use MVC design to create a model, a controller, and a view for both of '''Review Grade''' and '''Submission Grade'''.

:Model: grading_history.rb. Has a list of attributes contains instructor id, assignment id, grade type, student id, grade, comment, and timestamp.
:Controller: grading_history_controller.rb. Saves a new entry into the database every time a review grade or submission grade is saved
:View: index_html.erb. Displays current submission or review's grading history. An existing example of this is a submission record in the system.

We will also need to modify grades controller, so that every time, a grade is submitted or edited, grading_history_controller.rb will call a method to create an entry saves into the database.

===Expected View===

==== The list submission page with the new "grade history" option====
[[Image: E1869-Screenshot-1.jpg|50]]

==== The review report page with the new "grade history" option====
[[File:E1869-Screenshot-2.jpg]]

==== Grade history for a given team====
[[File:E1869-Screenshot-3.jpg]]

===Diagram===
[[File:E1869_Grading_Audit_Trails_UML.jpg]]

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

Functional testing:

1. Test if SubmissionGradeHistory.create is being called when a submission grade is changed.
spec/controllers/grades_controller_spec.rb

2. Test if ReviewGradeHistory.create is being called when a submission grade is changed.
spec/controllers/review_mapping_controller_spec.rb

3. Test if GradeHistory.where is being called when grading history button is clicked.
spec/controllers/grading_histories_controller_test.rb

===Code Changes===

==Files to be Modified==
*app/controllers/grades_controller.rb
'''
Creates a Grading History Record for every Submission grade edited by the instructor for a Team.
'''

*app/controllers/review_mapping_controller.rb
'''

Creates a Grading History Record for every Review grade edited by the instructor for a Student.
'''

* app/views/assignments/list_submissions.html.erb
'''
Add code to support view changes for Grade Record
'''

* app/views/review_mapping/_review_report.html.erb
'''
Add code to support view changes for Grade Record
'''

==Files to be Added==

*app/controllers/grading_histories_controller.rb
'''
Calls the grading history view after validaing Submission and Review Type.

'''

*app/models/grading_history.rb
'''
Model for Grading History.
'''

*app/models/review_grading_history.rb
'''
Model containing specifics of Review Grading History. Inherits Grading History.
'''

*app/models/submission_grading_history.rb
'''
Model containing specifics of Submission Grading History. Inherits Grading History.
'''

*app/views/grading_history/index_html.erb

'''
This is a view for grading audit trail, it will display all grading histories of a submission/review
'''

=='''Reference'''==
[https://expertiza.ncsu.edu/ Expertiza]

[http://wiki.expertiza.ncsu.edu/index.php/CSC/E1869_GRADING_AUDIT_TRAIL Previous Project Documentation]

[http://wiki.expertiza.ncsu.edu/index.php/Main_Page Expertiza_wiki]

[http://wiki.expertiza.ncsu.edu/index.php/Expertiza_documentation Expertiza Documentation]

[https://github.com/expertiza/expertiza Expertiza Github]

E1934 - Grading Audit Trail

2019-04-08T15:23:41Z

Amody: Created page with "=='''Introduction'''== ===Problem Statement=== After an instructor gave a grade to an assignment, there is no way to track who gave the grade. A grading audit trail must be crea..."

=='''Introduction'''==

===Problem Statement===
After an instructor gave a grade to an assignment, there is no way to track who gave the grade.
A grading audit trail must be created and the following information needs to be stored:
:1. When a grade is assigned by an instructor, there needs to be an indication of who did it and when it was done.
:2. Comments previously provided by other instructors must also be preserved.

This information needs to be stored every time an instructor edits a grade/comment and clicks the save button.

Currently, there are two places need to add grading audit trail:
:1. '''Review grade''': Log in as instructor -> Manage -> Assignments -> View Review Report
:2. '''Submission grade''': Log in as instructor -> Manage -> Assignments -> View submissions

=='''Proposed Solution'''==

===Design===
We plan to create a database called grading_history in the system which stores elements of instructor id, assignment id, grade type, student id, grade, comment, and timestamp.

We will use MVC design to create a model, a controller, and a view for both of '''Review Grade''' and '''Submission Grade'''.

:Model: grading_history.rb. Has a list of attributes contains instructor id, assignment id, grade type, student id, grade, comment, and timestamp.
:Controller: grading_history_controller.rb. Saves a new entry into the database every time a review grade or submission grade is saved
:View: index_html.erb. Displays current submission or review's grading history. An existing example of this is a submission record in the system.

We will also need to modify grades controller, so that every time, a grade is submitted or edited, grading_history_controller.rb will call a method to create an entry saves into the database.

===Expected View===

==== The list submission page with the new "grade history" option====
[[Image: E1869-Screenshot-1.jpg|50]]

==== The review report page with the new "grade history" option====
[[File:E1869-Screenshot-2.jpg]]

==== Grade history for a given team====
[[File:E1869-Screenshot-3.jpg]]

===Diagram===
[[File:E1869_Grading_Audit_Trails_UML.jpg]]

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

Functional testing:

1. Test if SubmissionGradeHistory.create is being called when a submission grade is changed.
spec/controllers/grades_controller_spec.rb

2. Test if ReviewGradeHistory.create is being called when a submission grade is changed.
spec/controllers/review_mapping_controller_spec.rb

3. Test if GradeHistory.where is being called when grading history button is clicked.
spec/controllers/grading_histories_controller_test.rb

===Code Changes===

==Files to be Modified==
*app/controllers/grades_controller.rb
'''
Creates a Grading History Record for every Submission grade edited by the instructor for a Team.
'''

*app/controllers/review_mapping_controller.rb
'''

Creates a Grading History Record for every Review grade edited by the instructor for a Student.
'''

* app/views/assignments/list_submissions.html.erb
'''
Add code to support view changes for Grade Record
'''

* app/views/review_mapping/_review_report.html.erb
'''
Add code to support view changes for Grade Record
'''

==Files to be Added==

*app/controllers/grading_histories_controller.rb
'''
Calls the grading history view after validaing Submission and Review Type.

'''

*app/models/grading_history.rb
'''
Model for Grading History.
'''

*app/models/review_grading_history.rb
'''
Model containing specifics of Review Grading History. Inherits Grading History.
'''

*app/models/submission_grading_history.rb
'''
Model containing specifics of Submission Grading History. Inherits Grading History.
'''

*app/views/grading_history/index_html.erb

'''
This is a view for grading audit trail, it will display all grading histories of a submission/review
'''

=='''Reference'''==
[https://expertiza.ncsu.edu/ Expertiza]

[http://wiki.expertiza.ncsu.edu/index.php/CSC/E1869_GRADING_AUDIT_TRAIL]

[http://wiki.expertiza.ncsu.edu/index.php/Main_Page Expertiza_wiki]

[http://wiki.expertiza.ncsu.edu/index.php/Expertiza_documentation Expertiza Documentation]

[https://github.com/expertiza/expertiza Expertiza Github]

CSC/ECE 517 Spring 2019 - Project E1912. Export Tagged Comments

2019-04-02T23:52:53Z

Amody: /* Code and Snapshots */

==Introduction==
===About Expertiza===
Expertiza is an Open Source Web Application Software managed by National Science Foundation. Expertiza is used by many courses including CSC 517 for assignment management. It has functionalities such as peer reviews, teammate reviews and tagging reviews in which students can provide feedback on other's work which helps peer in better developing the project.

===Motivation===
The Expertiza team currently had to manually fire queries in the database in order to get the tag submissions made by an individual user(student) on each review for a particular assignment. In this way, the team got the data from the entire class, which was then used to feed the Machine Learning algorithms. But many times it used to happen that students made random tags and the ML algorithm was not able to make good predictions out of it, hence in order to solve this issue a new idea was proposed as to select on the students which did not create outliers in the predictions and hence, therefore, it is a good proposal.

===Tasks Identified===
In order to perform this task following files were identified where the code hasbeen added.
* In _answer_tagging_report.html.erb view, a button is added for exporting the student's tagged values
* A checkbox for each row has been added in order to select students whose tags are to be exported(By default all will be selected).
* A method is written in export_file_controller.rb controller named export_tags that exports the CSV file.

==Implementation==
The workflow diagram of our implementation is shown here:

[[File:E1912flow.png]]

We have added a default select all checkbox under ''Report tags done by each user'' which enables student selection for exporting tags in the CSV file. We have added a column for the checkbox and a button named '''Export''' which on click generates the CSV file.

[[File:Eb1912Export.png]]

Below is the snippet of the same view ''_answer_tagging_report.html.erb ''

<pre>
<%= form_tag(export_tags, method: 'put',:id => 'tst') do %>
<div id="tab-summary">
<h4 align="center">Summary for each user</h4>
<table class="table table-striped sortable">
<thead>
<tr>
<th class="sorter-true">Username</th>
<th class="sorter-true">Name</th>
<th class="sorter-true">Percentage of tags done</th>
<th class="sorter-true"># tags done</th>
<th class="sorter-true"># tags not done</th>
<th class="sorter-true"># possible tags to do<img src='/assets/info.png' title='Number of answers that fulfil the prerequisite setup for each
tags (Answer of certain question types and has a length of greater than the threshold).'/></th>
<th>Tags export</th>
</tr>
</thead>
<% @user_tagging_report.each do |key, val| %>
<tr>
<td><%= val.user.name(session[:ip]) %></td>
<td><%= val.user.fullname(session[:ip]) %></td>
<td><%= val.percentage.to_s %>%</td>
<td><%= val.no_tagged.to_s %></td>
<td><%= val.no_not_tagged.to_s %></td>
<td><%= val.no_tagable %></td>
<td><%= check_box_tag 'names[]', val.user.name(session[:ip]), true %></td>
</tr>
<% end %>
</table>
</div>
<%= submit_tag "Export",:value => 'Export' ,:form => 'tst',method: 'put' %>
<% end %>
</pre>

==Screencast==
# [https://drive.google.com/open?id=1B65_N3bWwPlSyiXMhXzXypKvKLN09g0r Here] is the link to a screen recording on how to access the functionality and export the CSV file.

==Code and Snapshots==

We have written a method inside the ''export_file_controller.rb''. Once this method is called it queries on the ''name'' array passed from the view and exports the CSV file with the required data. The attributes named variable stores what all data is needed from their respective table and only that data is dumped into CSV.

<pre>
def export_tags
@user_ids = User.where("name IN (?)", params[:names])
@students = AnswerTag.select('answers.*, answer_tags.*').joins(:answer).where("answer_tags.answer_id = answers.id and answer_tags.user_id IN (?)", @user_ids.pluck(:id))
attributes = %w[user_id tag_prompt_deployment_id comments value]

csv_data = CSV.generate(col_sep: ",") do |csv|
csv << attributes
@students.each do |item|
csv << item.attributes.values_at(*attributes)
end
end
filename = "Tags"

send_data csv_data,
type: 'text/csv; charset=iso-8859-1; header=present',
disposition: "attachment; filename=#{filename}.csv"

end
</pre>

The output file has '''user_id, tag_prompt_deployment_id, comments and value'''. We can see that some comments are repeated it is because every review that is received has at least 1 tag for it. Hence we see the repetition. The value column has -1, 0 and 1 as No, not answered and Yes meaning respectively.

[[File:Eb1912csv.png]]

==Test==
The code was written for adding functionality such that selected students data can be dumped into a CSV file. A valid test case for this would be if nothing is selected and still the export button was clicked it would not dump any data into CSV file. The data is well structured so there would not be any scenario that a NULL data will be dumped. Every column will have its value in every row.

==Design==
The functionality for our project was to implement exporting of tagged comments from the Expertiza system. For this, we will approach the project by using the delegation pattern to add exporting capabilities to the export file controller for exporting tags.

==Teammates==
Mentor - Harsh Agrawal

* Aishwarya Subramanian (asubram7)
* Dyuti De (dde)
* Ankit Mody (amody)

==References==
# [https://github.com/expertiza/expertiza Github Repository for Expertiza]
# [http://wiki.expertiza.ncsu.edu/index.php/Documentation_on_Database_Tables Expertiza Documentation on Database Tables]
# [https://guides.rubyonrails.org/api_app.html Rails Guide Documentation]

CSC/ECE 517 Spring 2019 - Project E1912. Export Tagged Comments

2019-04-02T23:52:02Z

Amody:

==Introduction==
===About Expertiza===
Expertiza is an Open Source Web Application Software managed by National Science Foundation. Expertiza is used by many courses including CSC 517 for assignment management. It has functionalities such as peer reviews, teammate reviews and tagging reviews in which students can provide feedback on other's work which helps peer in better developing the project.

===Motivation===
The Expertiza team currently had to manually fire queries in the database in order to get the tag submissions made by an individual user(student) on each review for a particular assignment. In this way, the team got the data from the entire class, which was then used to feed the Machine Learning algorithms. But many times it used to happen that students made random tags and the ML algorithm was not able to make good predictions out of it, hence in order to solve this issue a new idea was proposed as to select on the students which did not create outliers in the predictions and hence, therefore, it is a good proposal.

===Tasks Identified===
In order to perform this task following files were identified where the code hasbeen added.
* In _answer_tagging_report.html.erb view, a button is added for exporting the student's tagged values
* A checkbox for each row has been added in order to select students whose tags are to be exported(By default all will be selected).
* A method is written in export_file_controller.rb controller named export_tags that exports the CSV file.

==Implementation==
The workflow diagram of our implementation is shown here:

[[File:E1912flow.png]]

We have added a default select all checkbox under ''Report tags done by each user'' which enables student selection for exporting tags in the CSV file. We have added a column for the checkbox and a button named '''Export''' which on click generates the CSV file.

[[File:Eb1912Export.png]]

Below is the snippet of the same view ''_answer_tagging_report.html.erb ''

<pre>
<%= form_tag(export_tags, method: 'put',:id => 'tst') do %>
<div id="tab-summary">
<h4 align="center">Summary for each user</h4>
<table class="table table-striped sortable">
<thead>
<tr>
<th class="sorter-true">Username</th>
<th class="sorter-true">Name</th>
<th class="sorter-true">Percentage of tags done</th>
<th class="sorter-true"># tags done</th>
<th class="sorter-true"># tags not done</th>
<th class="sorter-true"># possible tags to do<img src='/assets/info.png' title='Number of answers that fulfil the prerequisite setup for each
tags (Answer of certain question types and has a length of greater than the threshold).'/></th>
<th>Tags export</th>
</tr>
</thead>
<% @user_tagging_report.each do |key, val| %>
<tr>
<td><%= val.user.name(session[:ip]) %></td>
<td><%= val.user.fullname(session[:ip]) %></td>
<td><%= val.percentage.to_s %>%</td>
<td><%= val.no_tagged.to_s %></td>
<td><%= val.no_not_tagged.to_s %></td>
<td><%= val.no_tagable %></td>
<td><%= check_box_tag 'names[]', val.user.name(session[:ip]), true %></td>
</tr>
<% end %>
</table>
</div>
<%= submit_tag "Export",:value => 'Export' ,:form => 'tst',method: 'put' %>
<% end %>
</pre>

==Screencast==
# [https://drive.google.com/open?id=1B65_N3bWwPlSyiXMhXzXypKvKLN09g0r Here] is the link to a screen recording on how to access the functionality and export the CSV file.

==Code and Snapshots==

We have written a method inside the ''export_file_controller.rb''. Once this method is called it queries on the ''name'' array passed from the view and exports the CSV file with the required data.

<pre>
def export_tags
@user_ids = User.where("name IN (?)", params[:names])
@students = AnswerTag.select('answers.*, answer_tags.*').joins(:answer).where("answer_tags.answer_id = answers.id and answer_tags.user_id IN (?)", @user_ids.pluck(:id))
attributes = %w[user_id tag_prompt_deployment_id comments value]

csv_data = CSV.generate(col_sep: ",") do |csv|
csv << attributes
@students.each do |item|
csv << item.attributes.values_at(*attributes)
end
end
filename = "Tags"

send_data csv_data,
type: 'text/csv; charset=iso-8859-1; header=present',
disposition: "attachment; filename=#{filename}.csv"

end
</pre>

The output file has '''user_id, tag_prompt_deployment_id, comments and value'''. We can see that some comments are repeated it is because every review that is received has at least 1 tag for it. Hence we see the repetition. The value column has -1, 0 and 1 as No, not answered and Yes meaning respectively.

[[File:Eb1912csv.png]]

==Test==
The code was written for adding functionality such that selected students data can be dumped into a CSV file. A valid test case for this would be if nothing is selected and still the export button was clicked it would not dump any data into CSV file. The data is well structured so there would not be any scenario that a NULL data will be dumped. Every column will have its value in every row.

==Design==
The functionality for our project was to implement exporting of tagged comments from the Expertiza system. For this, we will approach the project by using the delegation pattern to add exporting capabilities to the export file controller for exporting tags.

==Teammates==
Mentor - Harsh Agrawal

* Aishwarya Subramanian (asubram7)
* Dyuti De (dde)
* Ankit Mody (amody)

==References==
# [https://github.com/expertiza/expertiza Github Repository for Expertiza]
# [http://wiki.expertiza.ncsu.edu/index.php/Documentation_on_Database_Tables Expertiza Documentation on Database Tables]
# [https://guides.rubyonrails.org/api_app.html Rails Guide Documentation]

CSC/ECE 517 Spring 2019

2019-04-02T00:13:45Z

Amody:

CSC/ECE 517 Spring 2019 - Project E1912. Export Tagged Comments

2019-04-02T00:11:07Z

Amody: Created page with "==Introduction== ===About Expertiza=== Expertiza is an Open Source Web Application Software managed by National Science Foundation. Expertiza is used by many courses including CS..."

==Introduction==
===About Expertiza===
Expertiza is an Open Source Web Application Software managed by National Science Foundation. Expertiza is used by many courses including CSC 517 for assignment management. It has functionalities such as peer reviews, teammate reviews and tagging reviews in which students can provide feedback on other's work which helps peer in better developing the project.

===Motivation===
The Expertiza team currently had to manually fire queries in the database in order to get the tag submissions made by an individual user(student) on each review for a particular assignment. In this way, the team got the data from the entire class, which was then used to feed the Machine Learning algorithms. But many times it used to happen that students made random tags and the ML algorithm was not able to make good predictions out of it, hence in order to solve this issue a new idea was proposed as to select on the students which did not create outliers in the predictions and hence, therefore, it is a good proposal.

===Tasks Identified===
In order to perform this task following files were identified where the code hasbeen added.
* In _answer_tagging_report.html.erb view, a button is added for exporting the student's tagged values
* A checkbox for each row has been added in order to select students whose tags are to be exported(By default all will be selected).
* A method is written in export_file_controller.rb controller named export_tags that exports the CSV file.

==Implementation==
The workflow diagram of our implementation is shown here:

[[File:E1912flow.png]]

We have added a default select all checkbox under ''Report tags done by each user'' which enables student selection for exporting tags in the CSV file. We have added a column for the checkbox and a button named '''Export''' which on click generates the CSV file.

[[File:Eb1912Export.png]]

Below is the snippet of the same view ''_answer_tagging_report.html.erb ''

<pre>
<%= form_tag(export_tags, method: 'put',:id => 'tst') do %>
<div id="tab-summary">
<h4 align="center">Summary for each user</h4>
<table class="table table-striped sortable">
<thead>
<tr>
<th class="sorter-true">Username</th>
<th class="sorter-true">Name</th>
<th class="sorter-true">Percentage of tags done</th>
<th class="sorter-true"># tags done</th>
<th class="sorter-true"># tags not done</th>
<th class="sorter-true"># possible tags to do<img src='/assets/info.png' title='Number of answers that fulfil the prerequisite setup for each
tags (Answer of certain question types and has a length of greater than the threshold).'/></th>
<th>Tags export</th>
</tr>
</thead>
<% @user_tagging_report.each do |key, val| %>
<tr>
<td><%= val.user.name(session[:ip]) %></td>
<td><%= val.user.fullname(session[:ip]) %></td>
<td><%= val.percentage.to_s %>%</td>
<td><%= val.no_tagged.to_s %></td>
<td><%= val.no_not_tagged.to_s %></td>
<td><%= val.no_tagable %></td>
<td><%= check_box_tag 'names[]', val.user.name(session[:ip]), true %></td>
</tr>
<% end %>
</table>
</div>
<%= submit_tag "Export",:value => 'Export' ,:form => 'tst',method: 'put' %>
<% end %>
</pre>

==Screen Record==
# [https://drive.google.com/open?id=1B65_N3bWwPlSyiXMhXzXypKvKLN09g0r Here] is the link to a screen recording on how to access the functionality and export the CSV file.

==Code and Snapshots==

We have written a method inside the ''export_file_controller.rb''. Once this method is called it queries on the ''name'' array passed from the view and exports the CSV file with the required data.

<pre>
def export_tags
@user_ids = User.where("name IN (?)", params[:names])
@students = AnswerTag.select('answers.*, answer_tags.*').joins(:answer).where("answer_tags.answer_id = answers.id and answer_tags.user_id IN (?)", @user_ids.pluck(:id))
attributes = %w[user_id tag_prompt_deployment_id comments value]

csv_data = CSV.generate(col_sep: ",") do |csv|
csv << attributes
@students.each do |item|
csv << item.attributes.values_at(*attributes)
end
end
filename = "Tags"

send_data csv_data,
type: 'text/csv; charset=iso-8859-1; header=present',
disposition: "attachment; filename=#{filename}.csv"

end
</pre>

The output file has '''user_id, tag_prompt_deployment_id, comments and value'''. We can see that some comments are repeated it is because every review that is received has at least 1 tag for it. Hence we see the repetition. The value column has -1, 0 and 1 as No, not answered and Yes meaning respectively.

[[File:Eb1912csv.png]]

==Design==
The functionality for our project was to implement exporting of tagged comments from the Expertiza system. For this, we will approach the project by using the delegation pattern to add exporting capabilities to the export file controller for exporting tags.

==Teammates==
Mentor - Harsh Agrawal

* Aishwarya Subramanian (asubram7)
* Dyuti De (dde)
* Ankit Mody (amody)

==References==
# [https://github.com/expertiza/expertiza Github Repository for Expertiza]
# [http://wiki.expertiza.ncsu.edu/index.php/Documentation_on_Database_Tables Expertiza Documentation on Database Tables]
# [https://guides.rubyonrails.org/api_app.html Rails Guide Documentation]

E1912 Export Tags

2019-04-01T23:55:17Z

Amody: /* Design Pattern */

==Introduction==
===About Expertiza===
Expertiza is an Open Source Web Application Software managed by National Science Foundation. Expertiza is used by many courses including CSC 517 for assignment management. It has functionalities such as peer reviews, teammate reviews and tagging reviews in which students can provide feedback on other's work which helps peer in better developing the project.

===Motivation===
The Expertiza team currently had to manually fire queries in the database in order to get the tag submissions made by an individual user(student) on each review for a particular assignment. In this way, the team got the data from the entire class, which was then used to feed the Machine Learning algorithms. But many times it used to happen that students made random tags and the ML algorithm was not able to make good predictions out of it, hence in order to solve this issue a new idea was proposed as to select on the students which did not create outliers in the predictions and hence, therefore, it is a good proposal.

===Tasks Identified===
In order to perform this task following files were identified where the code hasbeen added.
* In _answer_tagging_report.html.erb view, a button is added for exporting the student's tagged values
* A checkbox for each row has been added in order to select students whose tags are to be exported(By default all will be selected).
* A method is written in export_file_controller.rb controller named export_tags that exports the CSV file.

==Implementation==
We have added a default select all checkbox under ''Report tags done by each user'' which enables student selection for exporting tags in the CSV file. We have added a column for the checkbox and a button named '''Export''' which on click generates the CSV file.

[[File:Eb1912Export.png]]

Below is the snippet of the same view ''_answer_tagging_report.html.erb ''

<pre>
<%= form_tag(export_tags, method: 'put',:id => 'tst') do %>
<div id="tab-summary">
<h4 align="center">Summary for each user</h4>
<table class="table table-striped sortable">
<thead>
<tr>
<th class="sorter-true">Username</th>
<th class="sorter-true">Name</th>
<th class="sorter-true">Percentage of tags done</th>
<th class="sorter-true"># tags done</th>
<th class="sorter-true"># tags not done</th>
<th class="sorter-true"># possible tags to do<img src='/assets/info.png' title='Number of answers that fulfil the prerequisite setup for each
tags (Answer of certain question types and has a length of greater than the threshold).'/></th>
<th>Tags export</th>
</tr>
</thead>
<% @user_tagging_report.each do |key, val| %>
<tr>
<td><%= val.user.name(session[:ip]) %></td>
<td><%= val.user.fullname(session[:ip]) %></td>
<td><%= val.percentage.to_s %>%</td>
<td><%= val.no_tagged.to_s %></td>
<td><%= val.no_not_tagged.to_s %></td>
<td><%= val.no_tagable %></td>
<td><%= check_box_tag 'names[]', val.user.name(session[:ip]), true %></td>
</tr>
<% end %>
</table>
</div>
<%= submit_tag "Export",:value => 'Export' ,:form => 'tst',method: 'put' %>
<% end %>
</pre>

==Screen Record==
# [https://drive.google.com/open?id=1B65_N3bWwPlSyiXMhXzXypKvKLN09g0r Here] is the link to a screen recording on how to access the functionality and export the CSV file.

==Code and Snapshots==

We have written a method inside the ''export_file_controller.rb''. Once this method is called it queries on the ''name'' array passed from the view and exports the CSV file with the required data.

<pre>
def export_tags
@user_ids = User.where("name IN (?)", params[:names])
@students = AnswerTag.select('answers.*, answer_tags.*').joins(:answer).where("answer_tags.answer_id = answers.id and answer_tags.user_id IN (?)", @user_ids.pluck(:id))
attributes = %w[user_id tag_prompt_deployment_id comments value]

csv_data = CSV.generate(col_sep: ",") do |csv|
csv << attributes
@students.each do |item|
csv << item.attributes.values_at(*attributes)
end
end
filename = "Tags"

send_data csv_data,
type: 'text/csv; charset=iso-8859-1; header=present',
disposition: "attachment; filename=#{filename}.csv"

end
</pre>

The output file has '''user_id, tag_prompt_deployment_id, comments and value'''. We can see that some comments are repeated it is because every review that is received has at least 1 tag for it. Hence we see the repetition. The value column has -1, 0 and 1 as No, not answered and Yes meaning respectively.

[[File:Eb1912csv.png]]

==Design==
The functionality for our project was to implement exporting of tagged comments from the Expertiza system. For this, we will approach the project by using the delegation pattern to add exporting capabilities to the export file controller for exporting tags.

==Teammates==
Mentor - Harsh Agrawal

* Aishwarya Subramanian (asubram7)
* Dyuti De (dde)
* Ankit Mody (amody)

==References==
# [https://github.com/expertiza/expertiza Github Repository for Expertiza]
# [http://wiki.expertiza.ncsu.edu/index.php/Documentation_on_Database_Tables Expertiza Documentation on Database Tables]
# [https://guides.rubyonrails.org/api_app.html Rails Guide Documentation]

E1912 Export Tags

2019-04-01T23:44:57Z

Amody:

==Introduction==
===About Expertiza===
Expertiza is an Open Source Web Application Software managed by National Science Foundation. Expertiza is used by many courses including CSC 517 for assignment management. It has functionalities such as peer reviews, teammate reviews and tagging reviews in which students can provide feedback on other's work which helps peer in better developing the project.

===Motivation===
The Expertiza team currently had to manually fire queries in the database in order to get the tag submissions made by an individual user(student) on each review for a particular assignment. In this way, the team got the data from the entire class, which was then used to feed the Machine Learning algorithms. But many times it used to happen that students made random tags and the ML algorithm was not able to make good predictions out of it, hence in order to solve this issue a new idea was proposed as to select on the students which did not create outliers in the predictions and hence, therefore, it is a good proposal.

===Tasks Identified===
In order to perform this task following files were identified where the code hasbeen added.
* In _answer_tagging_report.html.erb view, a button is added for exporting the student's tagged values
* A checkbox for each row has been added in order to select students whose tags are to be exported(By default all will be selected).
* A method is written in export_file_controller.rb controller named export_tags that exports the CSV file.

==Implementation==
We have added a default select all checkbox under ''Report tags done by each user'' which enables student selection for exporting tags in the CSV file. We have added a column for the checkbox and a button named '''Export''' which on click generates the CSV file.

[[File:Eb1912Export.png]]

Below is the snippet of the same view ''_answer_tagging_report.html.erb ''

<pre>
<%= form_tag(export_tags, method: 'put',:id => 'tst') do %>
<div id="tab-summary">
<h4 align="center">Summary for each user</h4>
<table class="table table-striped sortable">
<thead>
<tr>
<th class="sorter-true">Username</th>
<th class="sorter-true">Name</th>
<th class="sorter-true">Percentage of tags done</th>
<th class="sorter-true"># tags done</th>
<th class="sorter-true"># tags not done</th>
<th class="sorter-true"># possible tags to do<img src='/assets/info.png' title='Number of answers that fulfil the prerequisite setup for each
tags (Answer of certain question types and has a length of greater than the threshold).'/></th>
<th>Tags export</th>
</tr>
</thead>
<% @user_tagging_report.each do |key, val| %>
<tr>
<td><%= val.user.name(session[:ip]) %></td>
<td><%= val.user.fullname(session[:ip]) %></td>
<td><%= val.percentage.to_s %>%</td>
<td><%= val.no_tagged.to_s %></td>
<td><%= val.no_not_tagged.to_s %></td>
<td><%= val.no_tagable %></td>
<td><%= check_box_tag 'names[]', val.user.name(session[:ip]), true %></td>
</tr>
<% end %>
</table>
</div>
<%= submit_tag "Export",:value => 'Export' ,:form => 'tst',method: 'put' %>
<% end %>
</pre>

==Screen Record==
# [https://drive.google.com/open?id=1B65_N3bWwPlSyiXMhXzXypKvKLN09g0r Here] is the link to a screen recording on how to access the functionality and export the CSV file.

==Code and Snapshots==

We have written a method inside the ''export_file_controller.rb''. Once this method is called it queries on the ''name'' array passed from the view and exports the CSV file with the required data.

<pre>
def export_tags
@user_ids = User.where("name IN (?)", params[:names])
@students = AnswerTag.select('answers.*, answer_tags.*').joins(:answer).where("answer_tags.answer_id = answers.id and answer_tags.user_id IN (?)", @user_ids.pluck(:id))
attributes = %w[user_id tag_prompt_deployment_id comments value]

csv_data = CSV.generate(col_sep: ",") do |csv|
csv << attributes
@students.each do |item|
csv << item.attributes.values_at(*attributes)
end
end
filename = "Tags"

send_data csv_data,
type: 'text/csv; charset=iso-8859-1; header=present',
disposition: "attachment; filename=#{filename}.csv"

end
</pre>

The output file has '''user_id, tag_prompt_deployment_id, comments and value'''. We can see that some comments are repeated it is because every review that is received has at least 1 tag for it. Hence we see the repetition. The value column has -1, 0 and 1 as No, not answered and Yes meaning respectively.

[[File:Eb1912csv.png]]

==Design Pattern==
Delegation

==Teammates==
Mentor - Harsh Agrawal

* Aishwarya Subramanian (asubram7)
* Dyuti De (dde)
* Ankit Mody (amody)

==References==
# [https://github.com/expertiza/expertiza Github Repository for Expertiza]
# [http://wiki.expertiza.ncsu.edu/index.php/Documentation_on_Database_Tables Expertiza Documentation on Database Tables]
# [https://guides.rubyonrails.org/api_app.html Rails Guide Documentation]

E1912 Export Tags

2019-04-01T22:54:08Z

Amody: /* Screen Record */

==Introduction==
===About Expertiza===
Expertiza is an Open Source Web Application Software managed by National Science Foundation. Expertiza is used by many courses including CSC 517 for assignment management. It has functionalities such as peer reviews, teammate reviews and tagging reviews in which students can provide feedback on other's work which helps peer in better developing the project.

===Motivation===
The Expertiza team currently had to manually fire queries in the database in order to get the tag submissions made by an individual user(student) on each review for a particular assignment. In this way, the team got the data from the entire class, which was then used to feed the Machine Learning algorithms. But many times it used to happen that students made random tags and the ML algorithm was not able to make good predictions out of it, hence in order to solve this issue a new idea was proposed as to select on the students which did not create outliers in the predictions and hence, therefore, it is a good proposal.

===Tasks Identified===
In order to perform this task following files were identified where the code hasbeen added.
* In _answer_tagging_report.html.erb view, a button is added for exporting the student's tagged values
* A checkbox for each row has been added in order to select students whose tags are to be exported(By default all will be selected).
* A method is written in export_file_controller.rb controller named export_tags that exports the CSV file.

==Implementation==
We have added a default select all checkbox under ''Report tags done by each user'' which enables student selection for exporting tags in the CSV file. We have added a column for the checkbox and a button named '''Export''' which on click generates the CSV file.

[[File:Eb1912Export.png]]

Below is the snippet of the same view ''_answer_tagging_report.html.erb ''

<pre>
<%= form_tag(export_tags, method: 'put',:id => 'tst') do %>
<div id="tab-summary">
<h4 align="center">Summary for each user</h4>
<table class="table table-striped sortable">
<thead>
<tr>
<th class="sorter-true">Username</th>
<th class="sorter-true">Name</th>
<th class="sorter-true">Percentage of tags done</th>
<th class="sorter-true"># tags done</th>
<th class="sorter-true"># tags not done</th>
<th class="sorter-true"># possible tags to do<img src='/assets/info.png' title='Number of answers that fulfil the prerequisite setup for each
tags (Answer of certain question types and has a length of greater than the threshold).'/></th>
<th>Tags export</th>
</tr>
</thead>
<% @user_tagging_report.each do |key, val| %>
<tr>
<td><%= val.user.name(session[:ip]) %></td>
<td><%= val.user.fullname(session[:ip]) %></td>
<td><%= val.percentage.to_s %>%</td>
<td><%= val.no_tagged.to_s %></td>
<td><%= val.no_not_tagged.to_s %></td>
<td><%= val.no_tagable %></td>
<td><%= check_box_tag 'names[]', val.user.name(session[:ip]), true %></td>
</tr>
<% end %>
</table>
</div>
<%= submit_tag "Export",:value => 'Export' ,:form => 'tst',method: 'put' %>
<% end %>
</pre>

==Screen Record==
# [https://drive.google.com/open?id=1B65_N3bWwPlSyiXMhXzXypKvKLN09g0r Here] is the link to a screen recording on how to access the functionality and export the CSV file.

==Code and Snapshots==

We have written a method inside the ''export_file_controller.rb''. Once this method is called it queries on the ''name'' array passed from the view and exports the CSV file with the required data.

<pre>
def export_tags
@user_ids = User.where("name IN (?)", params[:names])
@students = AnswerTag.select('answers.*, answer_tags.*').joins(:answer).where("answer_tags.answer_id = answers.id and answer_tags.user_id IN (?)", @user_ids.pluck(:id))
attributes = %w[user_id tag_prompt_deployment_id comments value]

csv_data = CSV.generate(col_sep: ",") do |csv|
csv << attributes
@students.each do |item|
csv << item.attributes.values_at(*attributes)
end
end
filename = "Tags"

send_data csv_data,
type: 'text/csv; charset=iso-8859-1; header=present',
disposition: "attachment; filename=#{filename}.csv"

end
</pre>

The output file has '''user_id, tag_prompt_deployment_id, comments and value'''. We can see that some comments are repeated it is because every review that is received has at least 1 tag for it. Hence we see the repetition. The value column has -1, 0 and 1 as No, not answered and Yes meaning respectively.

[[File:Eb1912csv.png]]

==Teammates==
Mentor - Harsh Agrawal

* Aishwarya Subramanian (asubram7)
* Dyuti De (dde)
* Ankit Mody (amody)

==References==
# [https://github.com/expertiza/expertiza Github Repository for Expertiza]
# [http://wiki.expertiza.ncsu.edu/index.php/Documentation_on_Database_Tables Expertiza Documentation on Database Tables]
# [https://guides.rubyonrails.org/api_app.html Rails Guide Documentation]

E1912 Export Tags

2019-04-01T22:51:45Z

Amody:

==Introduction==
===About Expertiza===
Expertiza is an Open Source Web Application Software managed by National Science Foundation. Expertiza is used by many courses including CSC 517 for assignment management. It has functionalities such as peer reviews, teammate reviews and tagging reviews in which students can provide feedback on other's work which helps peer in better developing the project.

===Motivation===
The Expertiza team currently had to manually fire queries in the database in order to get the tag submissions made by an individual user(student) on each review for a particular assignment. In this way, the team got the data from the entire class, which was then used to feed the Machine Learning algorithms. But many times it used to happen that students made random tags and the ML algorithm was not able to make good predictions out of it, hence in order to solve this issue a new idea was proposed as to select on the students which did not create outliers in the predictions and hence, therefore, it is a good proposal.

===Tasks Identified===
In order to perform this task following files were identified where the code hasbeen added.
* In _answer_tagging_report.html.erb view, a button is added for exporting the student's tagged values
* A checkbox for each row has been added in order to select students whose tags are to be exported(By default all will be selected).
* A method is written in export_file_controller.rb controller named export_tags that exports the CSV file.

==Implementation==
We have added a default select all checkbox under ''Report tags done by each user'' which enables student selection for exporting tags in the CSV file. We have added a column for the checkbox and a button named '''Export''' which on click generates the CSV file.

[[File:Eb1912Export.png]]

Below is the snippet of the same view ''_answer_tagging_report.html.erb ''

<pre>
<%= form_tag(export_tags, method: 'put',:id => 'tst') do %>
<div id="tab-summary">
<h4 align="center">Summary for each user</h4>
<table class="table table-striped sortable">
<thead>
<tr>
<th class="sorter-true">Username</th>
<th class="sorter-true">Name</th>
<th class="sorter-true">Percentage of tags done</th>
<th class="sorter-true"># tags done</th>
<th class="sorter-true"># tags not done</th>
<th class="sorter-true"># possible tags to do<img src='/assets/info.png' title='Number of answers that fulfil the prerequisite setup for each
tags (Answer of certain question types and has a length of greater than the threshold).'/></th>
<th>Tags export</th>
</tr>
</thead>
<% @user_tagging_report.each do |key, val| %>
<tr>
<td><%= val.user.name(session[:ip]) %></td>
<td><%= val.user.fullname(session[:ip]) %></td>
<td><%= val.percentage.to_s %>%</td>
<td><%= val.no_tagged.to_s %></td>
<td><%= val.no_not_tagged.to_s %></td>
<td><%= val.no_tagable %></td>
<td><%= check_box_tag 'names[]', val.user.name(session[:ip]), true %></td>
</tr>
<% end %>
</table>
</div>
<%= submit_tag "Export",:value => 'Export' ,:form => 'tst',method: 'put' %>
<% end %>
</pre>

==Screen Record==
[https://drive.google.com/open?id=1B65_N3bWwPlSyiXMhXzXypKvKLN09g0r] Here is the link to a screen recording on how to access the functionality.

==Code and Snapshots==

We have written a method inside the ''export_file_controller.rb''. Once this method is called it queries on the ''name'' array passed from the view and exports the CSV file with the required data.

<pre>
def export_tags
@user_ids = User.where("name IN (?)", params[:names])
@students = AnswerTag.select('answers.*, answer_tags.*').joins(:answer).where("answer_tags.answer_id = answers.id and answer_tags.user_id IN (?)", @user_ids.pluck(:id))
attributes = %w[user_id tag_prompt_deployment_id comments value]

csv_data = CSV.generate(col_sep: ",") do |csv|
csv << attributes
@students.each do |item|
csv << item.attributes.values_at(*attributes)
end
end
filename = "Tags"

send_data csv_data,
type: 'text/csv; charset=iso-8859-1; header=present',
disposition: "attachment; filename=#{filename}.csv"

end
</pre>

The output file has '''user_id, tag_prompt_deployment_id, comments and value'''. We can see that some comments are repeated it is because every review that is received has at least 1 tag for it. Hence we see the repetition. The value column has -1, 0 and 1 as No, not answered and Yes meaning respectively.

[[File:Eb1912csv.png]]

==Teammates==
Mentor - Harsh Agrawal

* Aishwarya Subramanian (asubram7)
* Dyuti De (dde)
* Ankit Mody (amody)

==References==
# [https://github.com/expertiza/expertiza Github Repository for Expertiza]
# [http://wiki.expertiza.ncsu.edu/index.php/Documentation_on_Database_Tables Expertiza Documentation on Database Tables]
# [https://guides.rubyonrails.org/api_app.html Rails Guide Documentation]

E1912 Export Tags

2019-04-01T22:42:34Z

Amody: /* Implementation */

==Introduction==
===About Expertiza===
Expertiza is an Open Source Web Application Software managed by National Science Foundation. Expertiza is used by many courses including CSC 517 for assignment management. It has functionalities such as peer reviews, teammate reviews and tagging reviews in which students can provide feedback on other's work which helps peer in better developing the project.

===Motivation===
The Expertiza team currently had to manually fire queries in the database in order to get the tag submissions made by an individual user(student) on each review for a particular assignment. In this way, the team got the data from the entire class, which was then used to feed the Machine Learning algorithms. But many times it used to happen that students made random tags and the ML algorithm was not able to make good predictions out of it, hence in order to solve this issue a new idea was proposed as to select on the students which did not create outliers in the predictions and hence, therefore, it is a good proposal.

===Tasks Identified===
In order to perform this task following files were identified where the code hasbeen added.
* In _answer_tagging_report.html.erb view, a button is added for exporting the student's tagged values
* A checkbox for each row has been added in order to select students whose tags are to be exported(By default all will be selected).
* A method is written in export_file_controller.rb controller named export_tags that exports the CSV file.

==Implementation==
We have added a default select all checkbox under ''Report tags done by each user'' which enables student selection for exporting tags in the CSV file. We have added a column for the checkbox and a button named '''Export''' which on click generates the CSV file.

[[File:Eb1912Export.png]]

Below is the snippet of the same view ''_answer_tagging_report.html.erb ''

<pre>
<%= form_tag(export_tags, method: 'put',:id => 'tst') do %>
<div id="tab-summary">
<h4 align="center">Summary for each user</h4>
<table class="table table-striped sortable">
<thead>
<tr>
<th class="sorter-true">Username</th>
<th class="sorter-true">Name</th>
<th class="sorter-true">Percentage of tags done</th>
<th class="sorter-true"># tags done</th>
<th class="sorter-true"># tags not done</th>
<th class="sorter-true"># possible tags to do<img src='/assets/info.png' title='Number of answers that fulfil the prerequisite setup for each
tags (Answer of certain question types and has a length of greater than the threshold).'/></th>
<th>Tags export</th>
</tr>
</thead>
<% @user_tagging_report.each do |key, val| %>
<tr>
<td><%= val.user.name(session[:ip]) %></td>
<td><%= val.user.fullname(session[:ip]) %></td>
<td><%= val.percentage.to_s %>%</td>
<td><%= val.no_tagged.to_s %></td>
<td><%= val.no_not_tagged.to_s %></td>
<td><%= val.no_tagable %></td>
<td><%= check_box_tag 'names[]', val.user.name(session[:ip]), true %></td>
</tr>
<% end %>
</table>
</div>
<%= submit_tag "Export",:value => 'Export' ,:form => 'tst',method: 'put' %>
<% end %>
</pre>

==Code and Snapshots==

We have written a method inside the ''export_file_controller.rb''. Once this method is called it queries on the ''name'' array passed from the view and exports the CSV file with the required data.

<pre>
def export_tags
@user_ids = User.where("name IN (?)", params[:names])
@students = AnswerTag.select('answers.*, answer_tags.*').joins(:answer).where("answer_tags.answer_id = answers.id and answer_tags.user_id IN (?)", @user_ids.pluck(:id))
attributes = %w[user_id tag_prompt_deployment_id comments value]

csv_data = CSV.generate(col_sep: ",") do |csv|
csv << attributes
@students.each do |item|
csv << item.attributes.values_at(*attributes)
end
end
filename = "Tags"

send_data csv_data,
type: 'text/csv; charset=iso-8859-1; header=present',
disposition: "attachment; filename=#{filename}.csv"

end
</pre>

The output file has '''user_id, tag_prompt_deployment_id, comments and value'''. We can see that some comments are repeated it is because every review that is received has at least 1 tag for it. Hence we see the repetition. The value column has -1, 0 and 1 as No, not answered and Yes meaning respectively.

[[File:Eb1912csv.png]]

==Teammates==
Mentor - Harsh Agrawal

* Aishwarya Subramanian (asubram7)
* Dyuti De (dde)
* Ankit Mody (amody)

==References==
# [https://github.com/expertiza/expertiza Github Repository for Expertiza]
# [http://wiki.expertiza.ncsu.edu/index.php/Documentation_on_Database_Tables Expertiza Documentation on Database Tables]
# [https://guides.rubyonrails.org/api_app.html Rails Guide Documentation]

E1912 Export Tags

2019-04-01T22:41:46Z

Amody: /* Definition, Demo code and snapshots */

==Introduction==
===About Expertiza===
Expertiza is an Open Source Web Application Software managed by National Science Foundation. Expertiza is used by many courses including CSC 517 for assignment management. It has functionalities such as peer reviews, teammate reviews and tagging reviews in which students can provide feedback on other's work which helps peer in better developing the project.

===Motivation===
The Expertiza team currently had to manually fire queries in the database in order to get the tag submissions made by an individual user(student) on each review for a particular assignment. In this way, the team got the data from the entire class, which was then used to feed the Machine Learning algorithms. But many times it used to happen that students made random tags and the ML algorithm was not able to make good predictions out of it, hence in order to solve this issue a new idea was proposed as to select on the students which did not create outliers in the predictions and hence, therefore, it is a good proposal.

===Tasks Identified===
In order to perform this task following files were identified where the code hasbeen added.
* In _answer_tagging_report.html.erb view, a button is added for exporting the student's tagged values
* A checkbox for each row has been added in order to select students whose tags are to be exported(By default all will be selected).
* A method is written in export_file_controller.rb controller named export_tags that exports the CSV file.

==Implementation==
We have added a default select all checkbox under ''Report tags done by each user'' which enables student selection for exporting tags in the CSV file. We have added a column for the checkbox and a button named '''Export''' which on click generates the CSV file.

[[File:Eb1912Export.png]]

Below is the snippet of same view ''_answer_tagging_report.html.erb ''.

<pre>
<%= form_tag(export_tags, method: 'put',:id => 'tst') do %>
<div id="tab-summary">
<h4 align="center">Summary for each user</h4>
<table class="table table-striped sortable">
<thead>
<tr>
<th class="sorter-true">Username</th>
<th class="sorter-true">Name</th>
<th class="sorter-true">Percentage of tags done</th>
<th class="sorter-true"># tags done</th>
<th class="sorter-true"># tags not done</th>
<th class="sorter-true"># possible tags to do<img src='/assets/info.png' title='Number of answers that fulfil the prerequisite setup for each
tags (Answer of certain question types and has a length of greater than the threshold).'/></th>
<th>Tags export</th>
</tr>
</thead>
<% @user_tagging_report.each do |key, val| %>
<tr>
<td><%= val.user.name(session[:ip]) %></td>
<td><%= val.user.fullname(session[:ip]) %></td>
<td><%= val.percentage.to_s %>%</td>
<td><%= val.no_tagged.to_s %></td>
<td><%= val.no_not_tagged.to_s %></td>
<td><%= val.no_tagable %></td>
<td><%= check_box_tag 'names[]', val.user.name(session[:ip]), true %></td>
</tr>
<% end %>
</table>
</div>
<%= submit_tag "Export",:value => 'Export' ,:form => 'tst',method: 'put' %>
<% end %>
</pre>

==Code and Snapshots==

We have written a method inside the ''export_file_controller.rb''. Once this method is called it queries on the ''name'' array passed from the view and exports the CSV file with the required data.

<pre>
def export_tags
@user_ids = User.where("name IN (?)", params[:names])
@students = AnswerTag.select('answers.*, answer_tags.*').joins(:answer).where("answer_tags.answer_id = answers.id and answer_tags.user_id IN (?)", @user_ids.pluck(:id))
attributes = %w[user_id tag_prompt_deployment_id comments value]

csv_data = CSV.generate(col_sep: ",") do |csv|
csv << attributes
@students.each do |item|
csv << item.attributes.values_at(*attributes)
end
end
filename = "Tags"

send_data csv_data,
type: 'text/csv; charset=iso-8859-1; header=present',
disposition: "attachment; filename=#{filename}.csv"

end
</pre>

The output file has '''user_id, tag_prompt_deployment_id, comments and value'''. We can see that some comments are repeated it is because every review that is received has at least 1 tag for it. Hence we see the repetition. The value column has -1, 0 and 1 as No, not answered and Yes meaning respectively.

[[File:Eb1912csv.png]]

==Teammates==
Mentor - Harsh Agrawal

* Aishwarya Subramanian (asubram7)
* Dyuti De (dde)
* Ankit Mody (amody)

==References==
# [https://github.com/expertiza/expertiza Github Repository for Expertiza]
# [http://wiki.expertiza.ncsu.edu/index.php/Documentation_on_Database_Tables Expertiza Documentation on Database Tables]
# [https://guides.rubyonrails.org/api_app.html Rails Guide Documentation]

E1912 Export Tags

2019-04-01T22:35:48Z

Amody: /* Implementation */

==Introduction==
===About Expertiza===
Expertiza is an Open Source Web Application Software managed by National Science Foundation. Expertiza is used by many courses including CSC 517 for assignment management. It has functionalities such as peer reviews, teammate reviews and tagging reviews in which students can provide feedback on other's work which helps peer in better developing the project.

===Motivation===
The Expertiza team currently had to manually fire queries in the database in order to get the tag submissions made by an individual user(student) on each review for a particular assignment. In this way, the team got the data from the entire class, which was then used to feed the Machine Learning algorithms. But many times it used to happen that students made random tags and the ML algorithm was not able to make good predictions out of it, hence in order to solve this issue a new idea was proposed as to select on the students which did not create outliers in the predictions and hence, therefore, it is a good proposal.

===Tasks Identified===
In order to perform this task following files were identified where the code hasbeen added.
* In _answer_tagging_report.html.erb view, a button is added for exporting the student's tagged values
* A checkbox for each row has been added in order to select students whose tags are to be exported(By default all will be selected).
* A method is written in export_file_controller.rb controller named export_tags that exports the CSV file.

==Implementation==
We have added a default select all checkbox under ''Report tags done by each user'' which enables student selection for exporting tags in the CSV file. We have added a column for the checkbox and a button named '''Export''' which on click generates the CSV file.

[[File:Eb1912Export.png]]

Below is the snippet of same view ''_answer_tagging_report.html.erb ''.

<pre>
<%= form_tag(export_tags, method: 'put',:id => 'tst') do %>
<div id="tab-summary">
<h4 align="center">Summary for each user</h4>
<table class="table table-striped sortable">
<thead>
<tr>
<th class="sorter-true">Username</th>
<th class="sorter-true">Name</th>
<th class="sorter-true">Percentage of tags done</th>
<th class="sorter-true"># tags done</th>
<th class="sorter-true"># tags not done</th>
<th class="sorter-true"># possible tags to do<img src='/assets/info.png' title='Number of answers that fulfil the prerequisite setup for each
tags (Answer of certain question types and has a length of greater than the threshold).'/></th>
<th>Tags export</th>
</tr>
</thead>
<% @user_tagging_report.each do |key, val| %>
<tr>
<td><%= val.user.name(session[:ip]) %></td>
<td><%= val.user.fullname(session[:ip]) %></td>
<td><%= val.percentage.to_s %>%</td>
<td><%= val.no_tagged.to_s %></td>
<td><%= val.no_not_tagged.to_s %></td>
<td><%= val.no_tagable %></td>
<td><%= check_box_tag 'names[]', val.user.name(session[:ip]), true %></td>
</tr>
<% end %>
</table>
</div>
<%= submit_tag "Export",:value => 'Export' ,:form => 'tst',method: 'put' %>
<% end %>
</pre>

==Definition, Demo code and snapshots==

We have written a method inside the ''export_file_controller.rb''. Once this method is called it queries on the ''name'' array passed from the view and exports the CSV file with the required data.

<pre>
def export_tags
@user_ids = User.where("name IN (?)", params[:names])
@students = AnswerTag.select('answers.*, answer_tags.*').joins(:answer).where("answer_tags.answer_id = answers.id and answer_tags.user_id IN (?)", @user_ids.pluck(:id))
attributes = %w[user_id tag_prompt_deployment_id comments value]

csv_data = CSV.generate(col_sep: ",") do |csv|
csv << attributes
@students.each do |item|
csv << item.attributes.values_at(*attributes)
end
end
filename = "Tags"

send_data csv_data,
type: 'text/csv; charset=iso-8859-1; header=present',
disposition: "attachment; filename=#{filename}.csv"

end
</pre>

The output file has '''user_id, tag_prompt_deployment_id, comments and value'''. We can see that some comments are repeated it is because every review that is received has at least 1 tag for it. Hence we see the repetition. The value column has -1, 0 and 1 as No, not answered and Yes meaning respectively.

[[File:Eb1912csv.png]]

==Teammates==
Mentor - Harsh Agrawal

* Aishwarya Subramanian (asubram7)
* Dyuti De (dde)
* Ankit Mody (amody)

==References==
# [https://github.com/expertiza/expertiza Github Repository for Expertiza]
# [http://wiki.expertiza.ncsu.edu/index.php/Documentation_on_Database_Tables Expertiza Documentation on Database Tables]
# [https://guides.rubyonrails.org/api_app.html Rails Guide Documentation]

E1912 Export Tags

2019-04-01T22:08:45Z

Amody: /* Implementation */

==Introduction==
===About Expertiza===
Expertiza is an Open Source Web Application Software managed by National Science Foundation. Expertiza is used by many courses including CSC 517 for assignment management. It has functionalities such as peer reviews, teammate reviews and tagging reviews in which students can provide feedback on other's work which helps peer in better developing the project.

===Motivation===
The Expertiza team currently had to manually fire queries in the database in order to get the tag submissions made by an individual user(student) on each review for a particular assignment. In this way, the team got the data from the entire class, which was then used to feed the Machine Learning algorithms. But many times it used to happen that students made random tags and the ML algorithm was not able to make good predictions out of it, hence in order to solve this issue a new idea was proposed as to select on the students which did not create outliers in the predictions and hence, therefore, it is a good proposal.

===Tasks Identified===
In order to perform this task following files were identified where the code hasbeen added.
* In _answer_tagging_report.html.erb view, a button is added for exporting the student's tagged values
* A checkbox for each row has been added in order to select students whose tags are to be exported(By default all will be selected).
* A method is written in export_file_controller.rb controller named export_tags that exports the CSV file.

==Implementation==
We have added a default select all checkbox under ''Report tags done by each user'' which enables student selection for exporting tags in the CSV file. We have added a column for the checkbox and a button named '''Export''' which on click generates the CSV file.

[[File:Eb1912Export.png]]

Below is the snippet of same view ''_answer_tagging_report.html.erb ''.

<pre>
<%= form_tag(export_tags, method: 'put',:id => 'tst') do %>
<div id="tab-summary">
<h4 align="center">Summary for each user</h4>
<table class="table table-striped sortable">
<thead>
<tr>
<th class="sorter-true">Username</th>
<th class="sorter-true">Name</th>
<th class="sorter-true">Percentage of tags done</th>
<th class="sorter-true"># tags done</th>
<th class="sorter-true"># tags not done</th>
<th class="sorter-true"># possible tags to do<img src='/assets/info.png' title='Number of answers that fulfil the prerequisite setup for each tags (Answer of certain question types and has a length of greater than the threshold).'/></th>
<th>Tags export</th>
</tr>
</thead>
<% @user_tagging_report.each do |key, val| %>
<tr>
<td><%= val.user.name(session[:ip]) %></td>
<td><%= val.user.fullname(session[:ip]) %></td>
<td><%= val.percentage.to_s %>%</td>
<td><%= val.no_tagged.to_s %></td>
<td><%= val.no_not_tagged.to_s %></td>
<td><%= val.no_tagable %></td>
<td><%= check_box_tag 'names[]', val.user.name(session[:ip]), true %></td>
</tr>
<% end %>
</table>
</div>
<%= submit_tag "Export",:value => 'Export' ,:form => 'tst',method: 'put' %>
<% end %>
</pre>

==Definition, Demo code and snapshots==

We have written a method inside the ''export_file_controller.rb''. Once this method is called it queries on the ''name'' array passed from the view and exports the CSV file with the required data.

<pre>
def export_tags
@user_ids = User.where("name IN (?)", params[:names])
@students = AnswerTag.select('answers.*, answer_tags.*').joins(:answer).where("answer_tags.answer_id = answers.id and answer_tags.user_id IN (?)", @user_ids.pluck(:id))
attributes = %w[user_id tag_prompt_deployment_id comments value]

csv_data = CSV.generate(col_sep: ",") do |csv|
csv << attributes
@students.each do |item|
csv << item.attributes.values_at(*attributes)
end
end
filename = "Tags"

send_data csv_data,
type: 'text/csv; charset=iso-8859-1; header=present',
disposition: "attachment; filename=#{filename}.csv"

end
</pre>

The output file has '''user_id, tag_prompt_deployment_id, comments and value'''. We can see that some comments are repeated it is because every review that is received has at least 1 tag for it. Hence we see the repetition. The value column has -1, 0 and 1 as No, not answered and Yes meaning respectively.

[[File:Eb1912csv.png]]

==Teammates==
Mentor - Harsh Agrawal

* Aishwarya Subramanian (asubram7)
* Dyuti De (dde)
* Ankit Mody (amody)

==References==
# [https://github.com/expertiza/expertiza Github Repository for Expertiza]
# [http://wiki.expertiza.ncsu.edu/index.php/Documentation_on_Database_Tables Expertiza Documentation on Database Tables]
# [https://guides.rubyonrails.org/api_app.html Rails Guide Documentation]

E1912 Export Tags

2019-04-01T22:07:26Z

Amody: /* Definition, Demo code and snapshots */

E1912 Export Tags

2019-04-01T17:28:53Z

Amody: /* Definition, Demo code and snapshots */

E1912 Export Tags

2019-04-01T17:19:39Z

Amody: /* Implementation */

E1912 Export Tags

2019-04-01T16:57:24Z

Amody: /* Tasks Identified */

E1912 Export Tags

2019-04-01T16:55:55Z

Amody: /* Tasks Identified */

E1912 Export Tags

2019-03-25T14:37:07Z

Amody: /* Future work */

E1912 Export Tags

2019-03-25T14:30:31Z

Amody: /* Teammates */

E1912 Export Tags

2019-03-25T14:30:16Z

Amody: /* Definition, Demo code and snapshots */

E1912 Export Tags

2019-03-25T14:29:56Z

Amody: /* Teammates */

E1912 Export Tags

2019-03-25T14:29:41Z

Amody: /* Teammates */

E1912 Export Tags

2019-03-25T14:27:54Z

Amody: /* Implementation */

E1912 Export Tags

2019-03-25T14:25:52Z

Amody: /* Tasks Identified */

E1912 Export Tags

2019-03-25T14:23:36Z

Amody: /* Motivation - (drawback and solution) */