Enforce Valid Values in Peer Review Rubric Scores

[mfbutner]

When a student is assigned a peer review with a rubric attached, there is nothing to enforce that a student enters valid values. Students can

1. Submit a value larger than the maximum for a criteria
2. Submit a negative value for a criteria
3. If using fixed criteria scores, not ranges, the student can submit a value between categories
4. If you are expecting whole numbers to be entered, there is nothing to enforce this

Here is an example of a rubric filled out by a student that canvas accepts because no checking is done on the values the student enters. 

• The first entry is both a decimal value and outside of any of the 3 scoring criteria, violating points 3 and 4
• The second entry is negative, which violates point 2
• The last value is above the maximum, which violates point 1

So giving the students a rubric to fill out in a Peer Review seems pointless because there is nothing in Canvas that forces the student to follow the rubric they are given.

What I want is something that enforces that the students enter valid values when filling out the rubric. 

[tim_kato]

This is causing problems at UBC's business school. We are experiencing a closely related problem. It turns out students can enter non-numerical values, such as text. If a student enters this type of invalid data into a rubric (i.e. I entered the text “A”), then there is an error in the rubric, and the student sees that the “peer review is not finished yet”. But when the page is refreshed, the peer review is considered complete. This undermines the effectiveness and robustness of the peer review tool, similar to the example cited by Matthew here.  @erica_hill  - do you have further comments here?

[erica_hill]

Comments from Instructure

As part of the new Ideas & Themes process, all ideas in Idea Conversations were reviewed by the Product Team. Any Idea that was associated with an identified theme was moved to the new Idea & Themes space. Any Idea that was not part of the move is being marked as Archived. This will preserve the history of the conversations while also letting Community members know that Instructure will not explore the request at this time.