Contributions and Class Review

Contributions shows each person's work in a project: the items they created and changed, their relationships, diagrams, comments and approvals, and when they worked. It links to the work itself, so you can read it before you judge it. The counts show activity, not the quality of the work.

Instructors of a class organization also get Class Review: assignments with due dates, a baseline of every group project at each due date, each student's work, and a roll-up for the gradebook.

How to use it

See each member's work

1. Open the project. Press ⌘K / Ctrl+K and choose Contributions, or click Share and then See each member's contributions.
2. The table has one row per member: Items created, Items changed, Relationships, Diagrams, Comments, Approvals, Active days and Last activity. Under each name, the classes they worked on are listed, for example "Requirement 12 · Action 4".
3. Click a row. You see the member's work:
   • Items by class: created and changed, per class.
   • Items created and Items changed, each with a link to the item, its class, the number of changes and the last change.
   • Documents the member worked on (a document counts when they created or changed the document or one of its items).
   • Relationships, each as source, relationship and target with the items' current names (for example "Filter water → verified by → Log flow").
   • Diagrams and whiteboards, Comments and Approvals.
   • Item history: the history records under the member's name, with the fields that changed.
4. Click ← All members to go back.

Print or export

• Print / PDF on a member's page opens the print dialog. Choose Save as PDF to keep a copy for one student.
• Export (Excel) writes one sheet with every member and one sheet per member with their counts by class.
• Export (CSV) writes the members table.

Set an assignment due date (instructors)

1. Open Organization Settings → Class Review, or press ⌘K / Ctrl+K and choose Class Review.
2. Under Assignments, click + New Assignment. Enter a name, such as "Concept Review", the due date and the time in your time zone. Click Add Assignment.
3. At that moment the server takes a baseline of every project of the organization: each member's counts and a version of the project. The status changes from Scheduled to Baselines taken.

Change… renames an assignment, or moves its due date while it has not passed. Remove deletes the assignment and its comparison; the versions kept at the due date stay in each project's history.

Compare with a due date

1. In Contributions (or a group project in Class Review), choose the assignment under Compare with.
2. Each count shows its value as of the due date in parentheses where it differs. After due date counts the changes made later.
3. On a member's page, work changed later is marked Changed after due date with the date; work added later is marked Added after due date.

Review a group project without joining it (instructors)

In Class Review → Group projects, click a project. You see its members and each member's work, as above. Instructors do not need to be members of the project: item names open a preview with the item's text and comments.

Export the class roll-up (instructors)

Under Class roll-up, optionally choose an assignment under Compare with, then click Export (Excel) or Export (CSV). The Excel file has one sheet with every student across the groups (with their email address for your gradebook), one sheet per group and one sheet per student. With an assignment, it adds the counts at the due date and the changes after it.

Ask AI for a summary

On a member's page, the ✦ AI control (in Class Review, Summarize Work…) writes a few paragraphs about the recorded activity: what parts of the model the person worked on and when. The summary is marked AI-written. It is not a grade and does not judge the quality of the work. It follows the organization's AI setting: when an org admin turns AI off, the summary is not available.

Who sees what

Site administrators get nothing extra here. Viewing another person's work, exporting the class roll-up and changing assignments are recorded in the audit log. Class Review needs an organization with class status (see Administration); make TAs org admins of the class organization.

How the counts are made

• Every change a page sends is stored with its author's account and the time the server received it. Holarch keeps a per-person index of these changes, so the counts stay after the change log is compacted. Times are the server's receive times: work saved offline counts when it reaches the server. Work from before the index started counts where the item history names a member.
• An item counts as created by the person who created it and as changed for anyone else who changed it later. Items that were deleted are not counted; the number of items a person created that are now deleted shows on their page.
• A change is one action, such as an edit, a new item or a comment, however many fields it touches. Active days are the days with at least one change, in your time zone.