CSC/ECE 517 Fall 2016 E1709 Visualizations for instructors - Revision history

Akshetty: /* Implementation */

2016-12-07T03:45:23Z

Implementation

← Older revision		Revision as of 03:45, 7 December 2016
Line 62:		Line 62:
	* We have taken the data from ReviewResponseMap, FeedbackResponseMap, AssignmentParticipant, Response models.		* We have taken the data from ReviewResponseMap, FeedbackResponseMap, AssignmentParticipant, Response models.
	* From ReviewResponseMap and AssignmentParticipant, for each reviewer we will get number of reviews completed, length of reviews, summary of reviews and whether reviewers had added a file or link for their review.		* From ReviewResponseMap and AssignmentParticipant, for each reviewer we will get number of reviews completed, length of reviews, summary of reviews and whether reviewers had added a file or link for their review.
	* From FeedbackResponseMap and Response, we will get the number of author feedbacks given to a reviewer. Using this we will get the average feedback score for a particular reviewer from all the feedbacks.		* From FeedbackResponseMap and Response, we will get the number of author feedbacks given to a reviewer. Using this we will get the average feedback score for a particular reviewer from all the feedbacks. For this we created a new method called as "get_author_feedback_score_hash", that will return a hash consisting of reviewer id and round number as composite key and the score for each round as value.
	For this we created a new method called as "get_author_feedback_score_hash", that will return a hash consisting of reviewer id and round number as composite key and the score for each round as value.
	* All the above data will be rendered in "/app/views/_review_report.html.erb".		* All the above data will be rendered in "/app/views/_review_report.html.erb".
	*Hyperlinks are provided where necessary, so that the instructor can view additional details. For e.g. to view review summary or author feedback summary.		*Hyperlinks are provided where necessary, so that the instructor can view additional details. For e.g. to view review summary or author feedback summary.

Akshetty: Added more points for implementation.

2016-12-07T03:43:10Z

Added more points for implementation.

← Older revision		Revision as of 03:43, 7 December 2016
Line 54:		Line 54:

	* A new metric filter is provided so that the instructor can select the average author feedback, average length of comments, check and open the file if it is added by the reviewer.		* A new metric filter is provided so that the instructor can select the average author feedback, average length of comments, check and open the file if it is added by the reviewer.
	* For the above implementation we have modified the following files: /app/views/_review_report.html.erb, app/controller/review_mapping_controller.rb, app/helper/review_mapping_helper.rb.		* For the above implementation we have modified the following files:
			**/app/views/review_mapping/_review_report.html.erb
			**/app/views/review_mapping/_searchbox.html.erb
			**app/controller/review_mapping_controller.rb
			**app/helper/review_mapping_helper.rb
	* The instructor can now also sort the reviewer by the name.		* The instructor can now also sort the reviewer by the name.
	* We have taken the data from ReviewResponseMap, FeedbackResponseMap, AssignmentParticipant models.		* We have taken the data from ReviewResponseMap, FeedbackResponseMap, AssignmentParticipant, Response models.
	* From ReviewResponseMap and AssignmentParticipant, for each reviewer we will get number of reviews completed, length of reviews, summary of reviews and whether reviewers had added a file or link for their review.		* From ReviewResponseMap and AssignmentParticipant, for each reviewer we will get number of reviews completed, length of reviews, summary of reviews and whether reviewers had added a file or link for their review.
	* From FeedbackResponseMap, we will get author feedback ~~summary~~ and the ~~total~~ score ~~that author gave~~ for ~~the particular reviewer~~.		* From FeedbackResponseMap and Response, we will get the number of author feedbacks given to a reviewer. Using this we will get the average feedback score for a particular reviewer from all the feedbacks.
			For this we created a new method called as "get_author_feedback_score_hash", that will return a hash consisting of reviewer id and round number as composite key and the score for each round as value.
	* All the above data will be rendered in "/app/views/_review_report.html.erb".		* All the above data will be rendered in "/app/views/_review_report.html.erb".
	*Hyperlinks are provided where necessary, so that the instructor can view additional details. For e.g. to view review summary or author feedback summary.		*Hyperlinks are provided where necessary, so that the instructor can view additional details. For e.g. to view review summary or author feedback summary.

Mshaikh: /* Implementation */

2016-12-03T05:12:48Z

Implementation

← Older revision		Revision as of 05:12, 3 December 2016
Line 56:		Line 56:
	* For the above implementation we have modified the following files: /app/views/_review_report.html.erb, app/controller/review_mapping_controller.rb, app/helper/review_mapping_helper.rb.		* For the above implementation we have modified the following files: /app/views/_review_report.html.erb, app/controller/review_mapping_controller.rb, app/helper/review_mapping_helper.rb.
	* The instructor can now also sort the reviewer by the name.		* The instructor can now also sort the reviewer by the name.
	** We have taken the data from ReviewResponseMap, FeedbackResponseMap, AssignmentParticipant models.		* We have taken the data from ReviewResponseMap, FeedbackResponseMap, AssignmentParticipant models.
	** From ReviewResponseMap and AssignmentParticipant, for each reviewer we will get number of reviews completed, length of reviews, summary of reviews and whether reviewers had added a file or link for their review.		* From ReviewResponseMap and AssignmentParticipant, for each reviewer we will get number of reviews completed, length of reviews, summary of reviews and whether reviewers had added a file or link for their review.
	** From FeedbackResponseMap, we will get author feedback summary and the total score that author gave for the particular reviewer.		* From FeedbackResponseMap, we will get author feedback summary and the total score that author gave for the particular reviewer.
	* All the above data will be rendered in "/app/views/_review_report.html.erb".		* All the above data will be rendered in "/app/views/_review_report.html.erb".
	*Hyperlinks are provided where necessary, so that the instructor can view additional details. For e.g. to view review summary or author feedback summary.		*Hyperlinks are provided where necessary, so that the instructor can view additional details. For e.g. to view review summary or author feedback summary.

Mshaikh: /* Pull Request and Demo */

2016-12-03T05:12:22Z

Pull Request and Demo

← Older revision		Revision as of 05:12, 3 December 2016
Line 63:		Line 63:

	==== Pull Request and Demo ====		==== Pull Request and Demo ====

			The demo for the Review report can be seen here: https://www.youtube.com/watch?v=mRgT9vdIizk
			The pull request is here: https://github.com/expertiza/expertiza/pull/870.

	=== Class Performance Report ===		=== Class Performance Report ===

Mshaikh: /* Pull Request and Demo */

2016-12-03T05:11:59Z

Pull Request and Demo

← Older revision		Revision as of 05:11, 3 December 2016
Line 112:		Line 112:

	==== Pull Request and Demo ====		==== Pull Request and Demo ====

	~~The demo for the Review report can be seen here: https://www.youtube.com/watch?v=mRgT9vdIizk~~
	~~The pull request is here: https://github.com/expertiza/expertiza/pull/870.~~

	The demo for the class performance report can be seen here: https://youtu.be/_fp4YYCgY2w		The demo for the class performance report can be seen here: https://youtu.be/_fp4YYCgY2w

Mshaikh: /* Implementation */

2016-12-03T05:11:32Z

Implementation

← Older revision		Revision as of 05:11, 3 December 2016
Line 61:		Line 61:
	* All the above data will be rendered in "/app/views/_review_report.html.erb".		* All the above data will be rendered in "/app/views/_review_report.html.erb".
	*Hyperlinks are provided where necessary, so that the instructor can view additional details. For e.g. to view review summary or author feedback summary.		*Hyperlinks are provided where necessary, so that the instructor can view additional details. For e.g. to view review summary or author feedback summary.

	~~==== Implementation ====~~

	==== Pull Request and Demo ====		==== Pull Request and Demo ====

Mshaikh: /* Mockups(Final Versions) */

2016-12-03T05:10:43Z

Mockups(Final Versions)

← Older revision		Revision as of 05:10, 3 December 2016
Line 73:		Line 73:


	==== ~~Mockups(~~Final ~~Versions)~~ ====		==== Final Design ====
	* The instructor can view the class performance on assignments by clicking on the graph icon on the assignments page as shown below.		* The instructor can view the class performance on assignments by clicking on the graph icon on the assignments page as shown below.

Mshaikh: /* Implementation Thoughts */

2016-12-03T05:10:17Z

Implementation Thoughts

← Older revision		Revision as of 05:10, 3 December 2016
Line 49:		Line 49:
	[[File:Expertiza1.png]]		[[File:Expertiza1.png]]

	==== Implementation ~~Thoughts~~ ====		==== Implementation ====

	This report is an ~~integration~~ of ~~two preexisting reports "Review"and "Author Feedback". Thus we will be reusing a lot of components with addition of few~~.		This report is an enhancement of the review report.

	* A new ~~option will be~~ provided in the ~~dropdown called as "Review~~ and ~~Author Feedback Report"~~.		* A new metric filter is provided so that the instructor can select the average author feedback, average length of comments, check and open the file if it is added by the reviewer.
	* ~~On submitting this form~~, ~~the user is redirected to action "response_report" in~~ controller ~~"ReviewMappingController"~~.		* For the above implementation we have modified the following files: /app/views/_review_report.html.erb, app/controller/review_mapping_controller.rb, app/helper/review_mapping_helper.rb.
	* ~~We will add new case for our requirement~~.		* The instructor can now also sort the reviewer by the name.
	** We ~~will require~~ data from ReviewResponseMap, FeedbackResponseMap, AssignmentParticipant models.		** We have taken the data from ReviewResponseMap, FeedbackResponseMap, AssignmentParticipant models.
	** From ReviewResponseMap and AssignmentParticipant, for each reviewer we will get number of reviews completed, length of reviews, summary of reviews and whether reviewers had added a file or link for their review.		** From ReviewResponseMap and AssignmentParticipant, for each reviewer we will get number of reviews completed, length of reviews, summary of reviews and whether reviewers had added a file or link for their review.
	** From FeedbackResponseMap, we will get author feedback summary and the total score that author gave for the particular reviewer.		** From FeedbackResponseMap, we will get author feedback summary and the total score that author gave for the particular reviewer.
	* All the above data will be rendered ~~using a new partial "_response_and_feedback.html.erb"~~ in "/app/views/~~review_mapping". This partial is called from "response_report~~.html.~~haml~~".		* All the above data will be rendered in "/app/views/_review_report.html.erb".
	* In a similar tabular format for Review/ Author feedback report, we will show the data in a table.		*Hyperlinks are provided where necessary, so that the instructor can view additional details. For e.g. to view review summary or author feedback summary.
	*Hyperlinks ~~will be~~ provided where necessary, so instructor can view additional details. For e.g. to view review summary or author feedback summary.

	==== Implementation ====		==== Implementation ====

Mshaikh: /* Mockups */

2016-12-03T04:47:09Z

Mockups

← Older revision		Revision as of 04:47, 3 December 2016
Line 44:		Line 44:


	==== ~~Mockups~~ ====		==== Final Design====
	* When the ~~author~~ will select the review ~~and author feedback~~, it will show him the screen shown below.		* When the instructor will select the show review report, it will show him the screen shown below.

	[[File:~~Mockup1~~.png]]		[[File:Expertiza1.png]]

	==== Implementation Thoughts ====		==== Implementation Thoughts ====

Mshaikh: /* Pull Request and Demo */

2016-12-03T04:43:27Z

Pull Request and Demo

← Older revision		Revision as of 04:43, 3 December 2016
Line 117:		Line 117:

	The demo for the Review report can be seen here: https://www.youtube.com/watch?v=mRgT9vdIizk		The demo for the Review report can be seen here: https://www.youtube.com/watch?v=mRgT9vdIizk
	The pull request is here: https://github.com/expertiza/expertiza/pull/870		The pull request is here: https://github.com/expertiza/expertiza/pull/870.

	The demo for the class performance report can be seen here: https://youtu.be/_fp4YYCgY2w		The demo for the class performance report can be seen here: https://youtu.be/_fp4YYCgY2w
	The pull request is here: https://github.com/expertiza/expertiza/pull/861		The pull request is here: https://github.com/expertiza/expertiza/pull/861