CSC/ECE 517 Fall 2016 E1685: UI changes for review and score reports

Introduction

Expertiza<ref>https://expertiza.ncsu.edu/</ref> is an open-source web application to create re-usable learning objects through peer-reviews to facilitate incremental learning. Students can submit learning objects such as articles, wiki pages, repository links and with the help of peer reviews, improve them. The project has been developed using the Ruby on Rails<ref>https://en.wikipedia.org/wiki/Ruby_on_Rails</ref> framework and is supported by the National Science Foundation.

Project Description

Purpose and Scope

Expertiza assignments are based on a peer review system where the instructor creates rubrics for an assignment through questionnaires which students use to review other students' submissions. The author of the submission is given an opportunity to provide feedback about these reviews. Expertiza displays reviews (i) to the team who was reviewed, and (ii) to the reviewer. A student user can see all the reviews of his/her team’s project. The instructor can see all the reviews of everyone’s project. The instructor also has access to a Review report, which shows, for each reviewer, all the reviews that (s)he wrote. Both score report and review report use different code so UI is non-orthogonal, it would be great if we can follow same UI structure for both score and review report which also reduce the DRY problems. There is no functionality for user to search between reviews of particular project, such a functionality will help user to search through all reviews for specific problem they are trying to focus on.

Task Description

The project requires completion of the following tasks:

Task-1

• A single way of displaying reviews that would be visible to students (reviews that they did, and reviews that their team received), and instructors (reviews that each team received, sorted by team; and reviews that each student did, sorted by student)

For student view the UI is consistent in displaying reviews they have done and reviews they have received but for instructor's view the summary report and review report both follow different UI and have different code. To make the UI consistent we have decided to choose the UI design of review report as base and modify the UI design for summary report. This will allow us to use the same code for both reports thereby following DRY principle.

Task-2

• Add button/link to hide and expand all the reviews.

Below is the mock-up image of how functionality will look after implementations

Task-3

• Create a tabbed view for each review view type : Heat map, Overall statistics, Individual reviews

Task-4

• Make review feedback more readable by changing UI or background color.

Task-5

• Add search box to search between reviews for particular string for a specific project(Student's view) or for specific user(Instructor's view).

References

<references/>