CSC/ECE 517 Spring 2021 - E2110. Regulate changing of rubrics while projects are in progress

From Expertiza_Wiki
Revision as of 22:53, 26 March 2021 by Nnhimes (talk | contribs)
Jump to navigation Jump to search

Members

  • Nicholas Himes
  • Surya Makthal
  • Jordan Boerger
  • Sai Krishna Wupadrashta Dhinakara Subrahmanya

Project Description

While setting up an assignment, the instructor will be asked to choose different kinds of rubrics. Any of these rubrics can later be edited or changed to a different rubric. A problem arises when an assignment is underway (students have already started reviewing) and a rubric is edited or changed. Some students started reviewing with the old rubric and the rest of the students who had not started a review will be presented with the updated rubric. This usually happens when an assignment is copied from a previous year and the rubrics are not updated to match the current topic. It could be at a later point that the instructor/TA realizes this and changes it.

If the instructor does edit or change a rubric while an assignment is in progress: If the change affects only the wording of a particular rubric item (e.g., to clarify the statement), no action is necessary. If a rubric is replaced, or the items/questions are changed, then all the reviews that have been done need to be redone. The system should then email the previously done reviews to the reviewer and delete the response object and all associated answer objects. (However, the response_map should not be changed.)



This project was done in Fall 2019. However, it was not tested thoroughly. That is the purpose of our team's work in Spring 2021.

Planned Work (Design Document)

We will write comprehensive tests and fix any bugs in the code written already for changing rubrics while projects are in progress.

Some known issues already have been identified:

  • If you are in the active period, you get a message that if you remove a question, there should be a confirmation prompt/alert prompted to the instructor.(This is because the remove happens from a completely diff. place in the code where it is not so convenient.)
  • Email functionality is not checked, beyond the right arguments being passed. The team had problems when calling the mailer function.
  • However, reviewers can still edit their reviews, but all text for the questions has been deleted. (No, actually, these are different qq. than the reviewer answered before.)
  • If you only edit qq. on the review, you can’t edit the review (if it has been submitted), but you can view it.
  • Method find_review_period may well be redundant, though they say it is not. Find deadlines does exist, but they say not finding a particular deadline.
  • The method that finds the last assgt. that uses a rubric needs a method comment.
  • As the reviews are getting deleted, this feature has to be tested thoroughly. The tests written are not thorugh and does not verify the rows deleted
  • If Minor change, when the student hasn't submitted, what would happen?
  • Are additional comments deleted? Might be a good idea to keep the additional comments and delete the rest of the answers. In the future, deleted based on each anser rather than the questionnaire can be an option