CSC/ECE 517 Fall 2017/E1791. Track the time that students look at the other submissions - logging improvement: Difference between revisions
(set up project wiki page) |
|||
| Line 1: | Line 1: | ||
== Introduction == | == 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 to instructors to study and improve the teach experience. However, the time tracking of specific content on these resources is not perfect in the expertiza system. The previous team working on E1705 project has solved part of such problems by tracking the active time of windows opened from the submitted links. But for the submitted files which could be downloaded for local review, there is only a rough approximation solution yet. In this project, our team is going to solve this problem as well as improving previous time tracking methods using mature third-party APIs to record link review time more accurately. To accomplish this goal, here are the tasks needed to be done: | |||
*Design a database schema for logging the time a reviewer spend on a submission; | |||
*Design and implement a solution that handles the use case, where students’ submissions are hosted on an external website using third-party APIs, e.g. gem: [https://github.com/octokit/octokit.rb Octokit] for Github use case; | |||
*Modify Review report (views/review_mapping/_review_report.html.erb) to show the time spent on each submission. | |||
== Task List == | == Task List == | ||
Revision as of 00:38, 7 November 2017
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 to instructors to study and improve the teach experience. However, the time tracking of specific content on these resources is not perfect in the expertiza system. The previous team working on E1705 project has solved part of such problems by tracking the active time of windows opened from the submitted links. But for the submitted files which could be downloaded for local review, there is only a rough approximation solution yet. In this project, our team is going to solve this problem as well as improving previous time tracking methods using mature third-party APIs to record link review time more accurately. To accomplish this goal, here are the tasks needed to be done:
- Design a database schema for logging the time a reviewer spend on a submission;
- Design and implement a solution that handles the use case, where students’ submissions are hosted on an external website using third-party APIs, e.g. gem: Octokit for Github use case;
- Modify Review report (views/review_mapping/_review_report.html.erb) to show the time spent on each submission.