CSC/ECE 517 Fall 2018/E1872 Track Time Students Look At Other Submissions

From Expertiza_Wiki
Revision as of 23:44, 13 November 2018 by Ppvasude (talk | contribs)
Jump to navigation Jump to search

Introduction

The expertiza project takes advantage of peer-review among students to allow them to learn from each other. To track the review time that each student spend on each submitted resources is meaningful for instructors to study and improve the teaching experience. The previous team working on the E1791 project has solved part of such problems by tracking the active time of windows opened from the submitted links by till the window is closed or gives a periodic pop up to ask if the user is still reviewing. And thus records the end time. It is done using mature third-party APIs to record link review time.

In this project, we require to autosave the reviews given timely to avoid re-writing of the reviews in case of erroneously closing the window.

Also, once the reviews are submitted, the review report page has a link to review details page which contains the above statistics. It becomes inconvenient to click on those links again and again to check the details. We will be merging the data of the details page on the current report page.

To accomplish this goal, here are the general solutions designed and implemented in this project:

  • Designed a database schema for logging the time a reviewer spend on a submission
  • Designed and implemented dynamic partial components using Javascript and Ruby to open students’ submissions in new windows to view online
  • Used DOM to control the windows holding review submission files or links, and record the open and close time.
  • Modify Review report (views/review_mapping/_review_report.html.erb) to show the total and detailed time spent on each review submissions with visualization.


Database schema design


For this project, the table submission_viewing_events stores all the time needed for each review submission event. The application records reviewer_id and reviewee_id, source_link for submitted links or file names, as well as time start_at and end_at, then store them in the table.


Objective of project: Objective 1:

The details of time spent on every assignment is displayed separately on the reviewer report page. As this is inconvenient we have to display all the statistics on the review report page.

Proposed Solution: Objective 2 :

    • Addition of one more column to the existing view of review_mapping/_review_report.html.erb called 'Review Details'.
    • Review statistics will include all the statistics for each review done by a student.
    • In this column we will provide each project the student has reviewed and the corresponding time spent on reviewing this project, separated by a ':'. Eg. Fix Import Issues : 15.26 mins.
    • We will do this by getting the reviewer id then using the ResponseMap we will get the ResponseTime using the mapId from the ResponseMap


Files needed to be changed: review_mapping/_review_report.html.erb


Objective 2: Implement the auto-save feature after a fixed interval of time.

Proposed Solution:

Files need to be changed: