CSC/ECE 517 Spring 2024/ OSS E2400 Allow Reviewers to Bid on What to Review: Difference between revisions

From Expertiza_Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 10: Line 10:
<li>Password: password</li>
<li>Password: password</li>


=== Problem Statement ===
==Problem Statement ==


The process of reviewing plays a crucial role in the learning and improvement cycle, benefiting both the reviewer and the reviewee. Allowing reviewers to choose their topics freely can lead to more thorough reviews and increased engagement. However, the current system of assigning review topics on a first-come-first-served basis disadvantages students who are slower to sign up, preventing them from reviewing topics they are most interested in.
The process of reviewing plays a crucial role in the learning and improvement cycle, benefiting both the reviewer and the reviewee. Allowing reviewers to choose their topics freely can lead to more thorough reviews and increased engagement. However, the current system of assigning review topics on a first-come-first-served basis disadvantages students who are slower to sign up, preventing them from reviewing topics they are most interested in.
Line 20: Line 20:
As development progressed, it became evident that the prototype also contained bugs and issues preventing its operation under certain conditions. Therefore, a secondary objective emerged to rectify these problems, ensuring the feature works as intended based on the functionality demonstrated by the prior implementation.
As development progressed, it became evident that the prototype also contained bugs and issues preventing its operation under certain conditions. Therefore, a secondary objective emerged to rectify these problems, ensuring the feature works as intended based on the functionality demonstrated by the prior implementation.


=== Background ===
==Background ==
When topics are opened up for bidding, students can see how “hot” each topic is by the color it has on their topic list. However, instructors have no way to view the bidding process except by impersonating students. Furthermore, when the bidding assignment algorithm is run, there is no way to verify that it did in fact assign teams to topics they had chosen.
When topics are opened up for bidding, students can see how “hot” each topic is by the color it has on their topic list. However, instructors have no way to view the bidding process except by impersonating students. Furthermore, when the bidding assignment algorithm is run, there is no way to verify that it did in fact assign teams to topics they had chosen.

Revision as of 23:48, 23 March 2024

This wiki page provides information regarding the refactoring of E2400 review_mapping_controller.rb OSS project for Spring 2024, CSC/ECE 517

Introduction

The Expertiza project makes use of peer review to allow students to learn from one another. It's a Ruby on Rails-based open-source application. It is used by faculty and students for the management of courses and assignments for specific courses. Different screens in the manage content area of the application offer information about users, courses, assignments, questionnaires, and reviews.

A review bid is a system used in Expertiza, where students indicate their preferences for reviewing certain assignments or projects. Students bid on the tasks they prefer to review through ranking their interests. The allocation of review assignments is determined by a bidding algorithm, balancing student preferences with fair and efficient distribution.

Test Login Credentials

  • UserId: instructor6
  • Password: password
  • Problem Statement

    The process of reviewing plays a crucial role in the learning and improvement cycle, benefiting both the reviewer and the reviewee. Allowing reviewers to choose their topics freely can lead to more thorough reviews and increased engagement. However, the current system of assigning review topics on a first-come-first-served basis disadvantages students who are slower to sign up, preventing them from reviewing topics they are most interested in.

    An improved approach would be to introduce a bidding system for review topics, similar to the one used for topic selection. This system would enable students to express their preferences for topics they are keen to review. An effective bidding algorithm could ensure that all interested students receive a topic they are eager to review.

    A previous project team developed a prototype allowing students to bid on review topics of their choice. While the prototype met the functional requirements, it could not be integrated due to numerous violations of the DRY (Don't Repeat Yourself) principle. The objective now is to adapt this prototype for the current expertiza beta branch, addressing the DRY violations to allow for its integration.

    As development progressed, it became evident that the prototype also contained bugs and issues preventing its operation under certain conditions. Therefore, a secondary objective emerged to rectify these problems, ensuring the feature works as intended based on the functionality demonstrated by the prior implementation.

    Background

    When topics are opened up for bidding, students can see how “hot” each topic is by the color it has on their topic list. However, instructors have no way to view the bidding process except by impersonating students. Furthermore, when the bidding assignment algorithm is run, there is no way to verify that it did in fact assign teams to topics they had chosen.