Changes to the Teacher app to make rubrics work more consistently
|Excellent - All items complete; extra polish; sprinkles on top||5|
|Satisfactory - All items complete||3|
|Unsatisfactory - Incomplete||1|
In our school, rubrics are mostly used to assess student performance on clinical tasks - observational assessments, not assessments of submitted works. We have many faculty grading each assignment, so there is a strong need for them to see the rating descriptions (which will hopefully improve inter-rater reliability). They may also need to move back and forth between browser- and app-based grading. So it's very important that the two formats mirror each other as much as possible.
Student A has completed her clinical case. Grader Q pulls out her phone, opens the Canvas Teacher app, and IMMEDIATELY (not after 10 seconds) sees her list of courses. She navigates to the correct course/assignment/student and swipes up to see the grading rubric. She taps the "Expand all" button and now sees the rubric as a modified grid, with all descriptions written out in full. The "top level" rating is listed at the top or left of each list, just like on the browser-based view. She taps each criteria she wants to select, then clicks "Done."
- Please select from one or more categories below.
- DO NOT delete 'cmug mobile idea' tag, but add your own, including Canvas Student, Canvas Teacher, or Canvas Parent.
Thanks for the idea! Or should I say, ideas! I some feedback.
Item #1: I don't necessarily have this issue, but I don't have a ton of items to grade, so maybe it's a scale issue. This is definitely something that should be reported to Canvas Support.
Item 2: I agree, anywhere you can be consistent with the web, I'd love to see it.
Item 3: I think this is purely a design decision. I would bet the "long press" to view rubric descriptions was made purely to have the information fit on a smartphone - a tablet would be fine. I'm not sure I'd change the current design completely, so I would like to see the ability for teachers to expand all the descriptions instead of relying on a long press. I'm totally for this!
One more thought. I think items 2 and 3 should be their own ideas since they do have different functions. As for item 1, this is a potential app performance issue and should be reported rather than added as an idea.