Peer Evaluation/Copyright MCQ e-learning activity

Knowledge of copyright

 * Learner demonstrates knowledge of the basics of copyright by developing two multiple choice questions covering two or more dimensions of scope, ownership, rights, exceptions or transfer of rights evidenced by identifying the correct answer and feedback justifications to the correct and incorrect answers.

Utility of the teaching / learning resource

 * Learner achieves acceptable quality of questions by adhering to the majority of best practice recommendations for developing multiple choice questions.

Peer support

 * Learner provides peer-learning support by objectively evaluating a minimum of three of the same e-Learning activities of fellow students as assigned by the peer evaluation system.

Assessment items and rubric
Is the content of the post related to ? Yes / No -- .

Example of rubric using a 1- 10 scale (for each criterion provide optional comment field):

Overall rating of the post: Unsatisfactory; Acceptable; Excellent

General comments .

Implications for design of the Peer evaluation system

 * 1) Evaluator must have access to the rubric (possible implementation: link to wiki page which contains the rubric)
 * 2) Educator should be encouraged to include competency statements ie what the learner should be able to do with the respective evaluation. (possible implementation: included as a subheading on the wiki page which contains the rubric.)
 * 3) Where a Likert point scale is used - I think its important that we can specify bands of achievement (eg Not achieved, Achieved and Merritt). I think the system should cater for 3 to maximum of 4 bands (eg Not achieved, Achieved, Merritt and Excellence) with the ability to assign the likert points to the bands, eg Achieved is 5 - 6 inclusive.)
 * 4) It would be useful to have a optional text field for comments on each major criterion - do we need to restrict the number of characters? While encouraging tweet sized feedback, perhaps setting the limit around 300 characters would be better. (Take a look at the WENotes implementation which counts down character usage for reusable code in a widget prototype.)