Grade Show Work

When to Use

• User asks to grade or review “show your work” partial credit
• User wants bonus points for handwritten/uploaded math work images
• Questions have file uploads and current auto-scores below passing
• Teacher wants a dry run or report before any scores are written

When NOT to Use

• Text-only or essay grading workflows
• Full regrading of mathematical correctness
• Situations where the user wants immediate silent score changes
• Questions without uploaded files or without a visible viewworkwrap

Guardrails

⚠️ Must NOT:

• Never decrease a score. This workflow is bonus only.
• Never skip the report. Generate the full report, show it to the teacher, and wait for explicit approval before editing any scorebox input.
• Never overwrite an approved non-zero score with a lower value. Only add bonus points.
• Never exceed the question max. Cap currentScore + bonus at the displayed maximum.
• Never judge correctness instead of effort. Award for visible mathematical work, not for a correct final answer.
• Never depend on UI preview clicks to obtain files. Extract URLs from a.attach.prepped programmatically.
• Never evaluate questions without both conditions: auto-score < 4 and a visible work-upload area (.viewworkwrap).
• Never continue past 20 students in one session. Soft warning at 15, stop at 20.

Quick Start

1. Open the gbviewassess.php grading page and load or create grade-show-work-state.json.
2. Scan students, extract eligible uploads, evaluate work as +2, +1, or +0, then generate the report.
3. After teacher approval, revisit approved students, add bonus points to the right scorebox fields, and save.

Workflow

Phase 0: Resume or Start Fresh

• INPUT: A grading page URL and optional existing grade-show-work-state.json
• ACTION:
  • Read the state entry for this exact grading URL.
  • If a saved entry exists, offer resume vs. start fresh.
  • Use phase values exactly: scan while collecting recommendations, apply while writing approved bonuses.
  • Navigate with Playwriter and verify the current student by re-observing h2 and h3.
• OUTPUT: Active grading session positioned at the correct student and phase.

Phase 1: Scan Current Student in One Extraction Pass

• INPUT: Current gbviewassess.php page
• ACTION: Use one browser extraction to gather student name, assessment name, question containers, score inputs, score maxima, and file links.

Eligibility reminder: only review questions that have a visible work-upload pane (div.questionpane.viewworkwrap / .viewworkwrap), at least one uploaded file, and an auto-score below 4.

const data = await state.gradePage.evaluate(() => {
  const studentName = document.querySelector('h2')?.textContent?.trim() || '';
  const assessmentName = document.querySelector('h3')?.textContent?.trim() || '';

  const questions = Array.from(document.querySelectorAll('.bigquestionwrap')).map((wrap, qIndex) => {
    const scoreInputs = Array.from(wrap.querySelectorAll('input[id^="scorebox"]'));
    const fileLinks = Array.from(wrap.querySelectorAll('a.attach.prepped')).map((a) => ({
      url: a.href,
      filename: a.textContent.trim(),
    }));

    return {
      qIndex,
      label: wrap.querySelector('strong')?.textContent?.trim() || `Question ${qIndex + 1}`,
      hasWorkUpload: !!wrap.querySelector('.viewworkwrap'),
      scoreInputs: scoreInputs.map((input) => ({
        id: input.id,
        value: parseFloat(input.value) || 0,
        max: parseFloat((input.nextSibling?.textContent || '').trim().replace('/', '')) || 0,
      })),
      fileLinks,
    };
  });

  return { studentName, assessmentName, questions };
});

• Eligibility criteria: only keep questions where:
  • at least one score part is < 4
  • hasWorkUpload === true because a .viewworkwrap work pane is present/visible for that question
  • at least one uploaded file URL is present
• OUTPUT: Eligible question list for the current student.

Phase 2: Fetch and Evaluate Uploaded Work

• INPUT: Eligible questions from Phase 1
• ACTION:
  • Use extracted URLs directly; do not click preview toggles.
  • File URLs follow https://files.myopenmath.com/ufiles/{uid}/{filename} and do not require authentication.
  • Save each file locally, then inspect it with the environment’s media-analysis tool.
  • Award bonus based on visible effort:

• Record a short rationale and work description for each recommendation.
• Cap the proposed new score at the question max.
• OUTPUT: Per-student bonus recommendations with evidence notes.

Phase 3: Advance Through the Roster Safely

• INPUT: Current student completed in scan mode
• ACTION:
  • Click Save and Next Student.
  • Treat this as a full page navigation, not an SPA update.
  • Expect the uid URL parameter to change to the next student; the original stu parameter may disappear after navigation.
  • Wait for domcontentloaded, then verify the h2 student name changed.
  • Increment the session counter.
  • At 15 students, warn that the 20-student limit is approaching.
  • At 20 students, stop scanning, save state, and generate the interim report.
• OUTPUT: Next student loaded or session halted at the safety limit.

Phase 4: Generate the Report First

• INPUT: All scan-mode recommendations collected so far
• ACTION: Build a markdown report with:
  • assignment name, date, scanned student count
  • summary table of students/questions with current score, bonus, new score
  • detailed rationale per question
  • only students receiving +1 or +2 listed in full detail
  • students with +0 only summarized as a count instead of expanded
  • explicit approval prompt

Suggested structure:

# Partial Credit Report: {Assignment Name}

## Summary
| Student | Question | Auto-Score | Bonus | New Score | Work Shown |
|---------|----------|------------|-------|-----------|------------|

## Detailed Breakdown
| Student | Question | Work Description | Credit | Rationale |
|---------|----------|------------------|--------|-----------|

## Approval Request
Apply these bonuses? (yes / no / adjust)

• OUTPUT: Teacher-reviewable report. No score edits yet.

Phase 5: Wait for Explicit Approval

• INPUT: Completed report
• ACTION:
  • Ask the teacher whether to apply, cancel, or adjust.
  • If adjustments are requested, update the report and re-confirm.
  • If the teacher declines, stop with no score changes.
• OUTPUT: Approved final change list or a clean cancellation.

Phase 6: Apply Approved Bonuses Only

• INPUT: Teacher-approved recommendations
• ACTION:
  • Revisit each approved student URL.
  • Update the exact scorebox inputs tied to the approved question parts.
  • Re-read the value after filling to verify the bonus stuck.
  • Save changes, then update grade-show-work-state.json to phase apply with progress.

for (const update of approvedUpdates) {
  const input = state.gradePage.locator(`input#${update.scoreboxId}`);
  await input.fill('');
  await input.fill(String(update.newScore));
}

• OUTPUT: Approved bonuses saved and verified.

Error Handling

Common Mistakes

State Management

• State file: grade-show-work-state.json
• Phases:
  • scan — actively reviewing students and building recommendations
  • apply — approved changes are being written back
• Recommended entry shape: preserve enough writeback data to resume safely, including uid, studentUrl, question index, and exact scoreboxId values for approved updates.

{
  "<grading-page-url>": {
    "lastStudent": "LastName, FirstName",
    "count": 12,
    "phase": "scan",
    "report": [
      {
        "student": "LastName, FirstName",
        "uid": "7158609",
        "studentUrl": "https://example.com/gbviewassess.php?cid=1&aid=2&uid=7158609",
        "questions": [
          {
            "index": 0,
            "label": "Question 1.",
            "scoreboxId": "scorebox0-0",
            "currentScore": 2,
            "maxScore": 5,
            "bonus": 2,
            "newScore": 4,
            "rationale": "Substantial work shown"
          }
        ]
      }
    ],
    "timestamp": "2026-03-15T12:00:00Z"
  }
}

• Save after each student during scan mode and after each applied student during apply mode.

Selectors / References

Core DOM selectors

Full selector reference

Score input ID convention

• Single-part question: scorebox{qIndex}
• Multipart question: scorebox{qIndex}-{partIndex}
• Both question index and part index are 0-based.

Max score extraction

const input = document.getElementById('scorebox0');
const maxScore = parseFloat(input.nextSibling.textContent.trim().replace('/', ''));

File URL facts

• Host: files.myopenmath.com
• Pattern: /ufiles/{uid}/{filename}
• Authentication: none required for direct fetch
• Typical image shape: resized upload (often .jpg) suitable for vision review
• Other possible extensions: .png, .pdf, .jpeg, .heic

Preview toggle facts

• span.videoembedbtn#fileembedbtnN[role="button"] is a span-based control, not a real button.
• Preview text usually flips from [+] to [-] when expanded.
• Inline preview images use IDs like img#fileiframefileembedbtnN.

Navigation fact

• Save and Next Student performs full page navigation; always re-observe the page after clicking it.