CSC/ECE 517 Fall 2016/E1698. Instructor/student control of anonymity + group-based reviewing

From Expertiza_Wiki
Revision as of 22:58, 7 November 2016 by Bkasliw (talk | contribs)
Jump to navigation Jump to search

E1698: Instructor/student control of anonymity + group-based reviewing

Introduction to Expertiza

Expertiza is a peer review system which provides incremental learning from the class. This project has been developed together by faculty and students using Ruby on Rails framework. Expertiza allows the instructor to create, edit and delete assignments, create new assignment topics, assign them to a particular class or selected students, have students work on teams and then review each other's assignments at the end. For the students, they can signup for topics, form teams, and submit their projects and assignments. Students then review the work done by other students and give suggestions to improve. Teams after reviews are allotted scores and they can refer to the peer comments to further improve their work. It also supports submission of different file types as well as URLs for assignments.

Problem Statement

The scenario: An instructor using Expertiza wants to do an experiment comparing anonymous review with identified (non-anonymous) review. And in general, there is quite a bit of research interest in the implications of anonymity in student interactions. In this experiment,

Approx ½ the class will conduct two rounds of formative reviews in small groups (4-5 students/group). The groups will stay the same for both rounds. The students in the groups should be able to see who they are reviewing and who is reviewing them. For the non-anonymous groups, I'd like the students to be able to request group members, so I would want to be able to have some control, perhaps with an option to use random assignment to groups if they had no preference for group members. Approx ½ the class will conduct two rounds of formative reviews anonymously (using the normal method we used this fall)

What needs to be done: The Review Strategy tab of assignment creation needs have a new checkbox for anonymous reviews, which would be checked by default. If it is checked, student views would be the same as at present. If it is not checked, students would see their reviewers and grades in the same way as the instructor now sees them; thus, instead of seeing “Reviewer 1”, “Reviewer 2”, the student might see, “Anthony Adams”, “Bessie Brown”, etc.

The code for displaying names obviously already exists, because it is used in the instructor views. Implement the changes in an elegant way; for example, instead of checking multiple times in the view to determine whether the reviewer’s (or author’s) real name is to be displayed, try to send a message to a model class that will “do the right thing.” This may involve creating separate model classes for anonymous and identified review, so that messages could be sent polymorphically. It’s hard for me to know, without studying the code, whether this would simplify the code or clutter it, but please give some thought to what is the clearest and most robust way to code both anonymous & identified reviews, from the student’s and the instructor’s perspective.

The other piece of the project is to enable review within groups, which means that every student in a group will review every other student in the group (but no students outside the group). This can be configured on the Review Strategy tab when the review strategy is set to “Instructor-Selected”. Under the “Set number of reviews done by each student” box, there could be another one, “Review done in groups of [ ] students”, where “[ ]” is a small text box. There should also be an information button describing how group-based review works.

I don’t know if it would be needed for next semester, but we’d also like to allow the instructor to assign each of the assignment participants to a particular group. Decide what would be a good way to specify that.

Another feature that would be useful is to allow students to toggle their anonymity by setting a field in their profile. So if someone wanted to be anonymous in an assignment that was not otherwise anonymous, they could set that field.

Design

Key People

Developers

  • Bhavesh Kasliwal
  • Bhavya Bansal
  • Chinmoy Baruah
  • Rishabh Sinha

Mentor

  • Ed Gehringer