Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

E1799 develop #1094

Closed
wants to merge 39 commits into from
Closed

E1799 develop #1094

wants to merge 39 commits into from

Conversation

ragabala
Copy link

E1799. Improve self-review Link peer review & self-review to derive grades
Team Members: Bhavik Patel, Amulya Varote, Arpita Shekhar, Ragavendran Balakrishnan
Mentor: Qaiss Khan Alokozai

What it does: Currently, it is possible to check the “Allow self-review” box on the Review Strategy tab of assignment creation, and then an author will be asked to review his/her own submission in addition to the submissions of others. But as currently implemented, nothing is done with the scores on these self-reviews.
What should be done:
It should be possible to see self-review scores juxtaposed with peer-review scores. Design a way to show them in the regular “View Scores” page and the alternate (heat-map) view. They should be shown amidst the other reviews, but in a way that highlights them as being a different kind of review.
Then implement a way to combine self-review and peer-review scores to derive a composite score. The actual formula is not as important as it is to encapsulate the formula in a method that can easily be modified if we want to change the formula. But the basic idea is that the authors get more points as their self-reviews get closer to the scores given by the peer reviewers. So the function should take as inputs the scores given by peers to a particular rubric criterion and the score given by the author(s). The result of the formula should be displayed in a conspicuous page on the score view.
Of course, there would be no challenge in giving the same self-review scores as the peer reviewers gave if the authors could see peer-review scores before they submitted their self-reviews. So the author(s) should be required to submit their self-evaluation(s) before seeing the results of their peer evaluations.
There are substantial degrees of freedom in this project. The layout of the score display is up to you. You get to choose the formula for computing composite self-/peer-review grades. You get to design an appropriate way to aggregate self-reviews by different members of the project team. Please make these decisions, corresponding with me if you desire, and document them in your design doc, so the instructor and your peer reviewers can give you comments before you proceed to implementation.
Avoid global variables. Allow the instructor to configure weights from the UI. Also … please see papers on the SPARKPlus approach to implementing this and the screenshots from Calibrated Peer Review. These will give you ideas on how other systems approach the same issue.

@Winbobob Winbobob force-pushed the master branch 3 times, most recently from 2cc51d9 to a1b78e0 Compare November 15, 2017 21:01
@coveralls
Copy link

Coverage Status

Coverage decreased (-20.2%) to 38.638% when pulling e3c16c0 on varoteamulya:E1799_Develop into 695772b on expertiza:master.

@coveralls
Copy link

Coverage Status

Coverage decreased (-30.6%) to 28.243% when pulling 57dd183 on varoteamulya:E1799_Develop into 695772b on expertiza:master.

@coveralls
Copy link

Coverage Status

Coverage decreased (-14.08%) to 44.769% when pulling a1e79d7 on varoteamulya:E1799_Develop into 695772b on expertiza:master.

@coveralls
Copy link

Coverage Status

Coverage decreased (-14.07%) to 44.784% when pulling 33f7d18 on varoteamulya:E1799_Develop into 695772b on expertiza:master.

@coveralls
Copy link

Coverage Status

Coverage decreased (-14.08%) to 44.769% when pulling 2cc1976 on varoteamulya:E1799_Develop into 695772b on expertiza:master.

@coveralls
Copy link

Coverage Status

Coverage decreased (-14.07%) to 44.78% when pulling df82426 on varoteamulya:E1799_Develop into 695772b on expertiza:master.

@coveralls
Copy link

Coverage Status

Coverage decreased (-14.5%) to 44.314% when pulling df82426 on varoteamulya:E1799_Develop into 695772b on expertiza:master.

@coveralls
Copy link

Coverage Status

Coverage decreased (-14.09%) to 44.764% when pulling df82426 on varoteamulya:E1799_Develop into 695772b on expertiza:master.

@coveralls
Copy link

Coverage Status

Coverage decreased (-34.9%) to 23.924% when pulling d231db1 on varoteamulya:E1799_Develop into 695772b on expertiza:master.

@coveralls
Copy link

Coverage Status

Coverage decreased (-22.3%) to 36.571% when pulling 90d5815 on varoteamulya:E1799_Develop into 695772b on expertiza:master.

@coveralls
Copy link

Coverage Status

Coverage decreased (-18.2%) to 41.317% when pulling 8230c12 on varoteamulya:E1799_Develop into b382753 on expertiza:master.

@coveralls
Copy link

Coverage Status

Coverage decreased (-24.1%) to 35.342% when pulling 8230c12 on varoteamulya:E1799_Develop into b382753 on expertiza:master.

@coveralls
Copy link

Coverage Status

Coverage decreased (-19.7%) to 39.735% when pulling 8230c12 on varoteamulya:E1799_Develop into b382753 on expertiza:master.

@coveralls
Copy link

Coverage Status

Coverage decreased (-22.2%) to 37.248% when pulling 0251a50 on varoteamulya:E1799_Develop into b382753 on expertiza:master.

@coveralls
Copy link

Coverage Status

Coverage decreased (-25.6%) to 33.887% when pulling 0251a50 on varoteamulya:E1799_Develop into b382753 on expertiza:master.

@coveralls
Copy link

Coverage Status

Coverage decreased (-36.8%) to 22.637% when pulling 502a134 on varoteamulya:E1799_Develop into b382753 on expertiza:master.

@coveralls
Copy link

Coverage Status

Coverage decreased (-13.7%) to 45.785% when pulling 0df7f19 on varoteamulya:E1799_Develop into b382753 on expertiza:master.

@Winbobob Winbobob force-pushed the master branch 9 times, most recently from 965f660 to d08c1cb Compare January 14, 2018 05:24
@Winbobob Winbobob force-pushed the master branch 2 times, most recently from e813e60 to 3eafd4b Compare January 21, 2018 16:44
@Winbobob Winbobob force-pushed the master branch 2 times, most recently from a7726e0 to 4355059 Compare February 12, 2018 16:06
@Winbobob Winbobob closed this Mar 14, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants