Evaluate & Feedback

Summary

Portfolio evaluation and feedback may be solicited, iterative, open to specified group(s), or incorporated into a workflow, and could be either structured or unstructured.

User Stories

Presentation Feedback & Evaluation

Jane Student has completed one page of her portfolio presentation, and would like feedback from her instructor as to whether or not it is on track. She selects feedback is requested.
Joe Instructor receives an email notificationand review's Jane's work. She seems to need a lot of guidance, so he provides inline comments explaining where she needs more work.
Jane Student receives an email notification, reads the inline feedback, and proceeds to complete her work. She marks the work as locked and completed.
Joe Instructor receives an email notification and reviews Jane's work. It is much improved, and adds an Unstructured Global Evaluation before marking his evaluation is complete.
Fred Advisor receives an email notification and reviews Janes work and Joe's evaluation comments. He fills out a Structured Evaluation form and then marks his evaluation as complete.
Jane Student now receives notification that her work has been evaluated. She reads both evaluations.

Functional Details

Both Feedback and Evaluations can be defined as one of the following types:

Structured Feedback/Evaluation
Unstructured Global Feedback/Evaluation
Unstructured Inline Feedback/Evaluation

Structured Feedback/Evaluation leverages a Structured Data Widget (e.g. form) as it's basic building block (also used in presentation and workflow pages).

Unstructured Global Feedback/Evaluation leverages a framework as the "Reflect anywhere" , using a "relates-to" attribute attachable to all Sakai objects.

Unstructured Inline Feedback/Evaluation may leverage a framework such as is used by Etherpad.

All feedback and evaluations will employ an optional notification mechanism (e.g. email) to alert students of new feedback/evaluations and to alert evaluations of content that is ready for evaluation.

Evaluations may optionally be "blind", where the evaluator does not know the student's identity.

Evaluations may optionally be "hidden", where the student cannot read the evaluation until released to the student.

Multiple Evaluations may optionally be configured, where one evaluation is handed off to another evaluator (and so on), until the last evaluator completes the evaluation process.

Configuring Evaluation and Feedback decision trees must balance flexibility against undo complexity. One approach would be to define a Evaluation and Feedback "Template" with presets for the following options:

Feedback Type(s): [Structured | Unstructured-Global | Unstructured-Inline ]
Evaluation Type(s): [Structured | Unstructured-Global | Unstructured-Inline ]
Student Notification of Feedback: [ opt-in | opt-out ] [ email | SMS | ... ]
Evaluator Notification of Content: [ opt-in | opt-out ] [ email | SMS | ...]
Student option to solicit feedback: [ from none | from all | from specified groups ]
Student option to receive feedback: [ from none | from all | from specified groups ]
Blind Evaluation: [ true | false ]
Hidden Evaluation: [ true | false ]
Evaluations: [ from none | from specified user | from specified groups | multiple (ordered list) ]

Diagrams & Mockups

This diagram describes the workflow for evaluations and feedback:

Implementation Details

How to implement structured rich-text feedback and evaluations -- especially when integrated with structured form widgets (rich text widget within a rich-text page doesn't make much sense). Note same problem as noted for structured rich-text feedback and reflections.