Contribution measurement
A per-member picture of who did the work, built from the work itself, with no forms to fill in.
As a group writes a document or builds a deck, Dwixel attributes each contribution to the person who made it. The result is a live, per-member view of who is doing what, drawn from the work rather than from anyone’s opinion of it.
Measured from real work, not a survey
Nobody fills in a contribution form. The signal comes from the editing itself: authored text, edits and revisions, comments, and structural work, each attributed to a member as it happens. This matters because edit history can legitimately ground an assessment of participation, provided it is interpreted rather than blindly counted. 1
Quality over volume
Counting edits rewards the wrong thing. Research on collaborative writing found that what reflects real, accepted contribution is the content that survives revision, not the number of edits a person made. 2 Dwixel is built on that principle:
- ·Large pasted bursts are detected and de-credited, so dropping in a block of text (or AI output) does not register as authoring it.
- ·Contribution leans toward authored text that survives later revision.
- ·Editing and curation are counted as their own kind of work, not mistaken for fresh writing.
- ·Comments are weighted by substance rather than counted one for one.
Deterministic and explainable
There is no opaque model deciding a student’s share. The scoring rules are fixed and inspectable, which is the only honest basis for anything that touches a grade. It also addresses a documented risk of trace-based metrics: that the inferences drawn from them can be invalid if the method is a black box. 3
Students see their own data
Every student can see their own contribution profile and how it is calculated. Measurement is something done with the group, not to it, and the transparency is part of what makes it fair. Contribution is presented as a profile with the attributed history behind it, in the spirit of tools that show who did what over time rather than reducing it to one unexplained number. 4
References
- 1.Trentin, G. (2009). Using a wiki to evaluate individual contribution to a collaborative learning project. Journal of Computer Assisted Learning, 25(1), 43–55. Link ↗
- 2.Viégas, F. B., Wattenberg, M., & Dave, K. (2004). Studying cooperation and conflict between authors with history flow visualizations. Proc. ACM CHI Conference on Human Factors in Computing Systems (CHI ’04), 575–582. Link ↗
- 3.Hakimi, L., Eynon, R., & Murphy, V. A. (2021). The ethics of using digital trace data in education: A thematic review of the research landscape. Review of Educational Research, 91(5), 671–717. Link ↗
- 4.Wang, D., Olson, J. S., Zhang, J., Nguyen, T., & Olson, G. M. (2015). DocuViz: Visualizing collaborative writing. Proc. ACM CHI Conference on Human Factors in Computing Systems (CHI ’15), 1865–1874. Link ↗