Skip to content

Report incomplete scanned exam groups#8051

Draft
akarki2005 wants to merge 3 commits into
MarkUsProject:masterfrom
akarki2005:report-incomplete-scanned-exam-groups
Draft

Report incomplete scanned exam groups#8051
akarki2005 wants to merge 3 commits into
MarkUsProject:masterfrom
akarki2005:report-incomplete-scanned-exam-groups

Conversation

@akarki2005

@akarki2005 akarki2005 commented Jul 9, 2026

Copy link
Copy Markdown
Contributor

Proposed Changes

Currently the exam scan log only surfaces per-page errors after scanning a batch of exam PDFs. There's no way to tell, at a glance, which student groups had all their pages successfully matched versus which are still missing pages.

This PR adds a per-group completion status to the scan log:

  • Backend (exam_templates_controller.rb): while building the page-level error data, also aggregate pages by group_id and mark a group complete if any of its pages has a status containing 'Saved to complete directory'. This is returned as a new group_data array alongside the existing page_data.
  • Frontend (exam_scan_log_table.jsx): add a new ExamScanGroupsTable sub-component, rendered under a "Papers found" heading next to the existing "Pending errors" table, showing each group's name and a Complete/Incomplete status.

Fixes #6511.

Type of Change

(Write an X or a brief description next to the type or types that best describe your changes.)

Type Applies?
🚨 Breaking change (fix or feature that would cause existing functionality to change)
New feature (non-breaking change that adds functionality)
🐛 Bug fix (non-breaking change that fixes an issue) X
🎨 User interface change (change to user interface; provide screenshots)
♻️ Refactoring (internal change to codebase, without changing functionality)
🚦 Test update (change that only adds or modifies tests)
📦 Dependency update (change that updates a dependency)
📖 Documentation update (change that updates documentation)
🔧 Internal (change that only affects developers or continuous integration)

Checklist

(Complete each of the following items for your pull request. Indicate that you have completed an item by changing the [ ] into a [x] in the raw text, or by clicking on the checkbox in the rendered description on GitHub.)

Before opening your pull request:

  • I have performed a self-review of my changes.
    • Check that all changed files included in this pull request are intentional changes.
    • Check that all changes are relevant to the purpose of this pull request, as described above.
  • I have added tests for my changes, if applicable.
    • This is required for all bug fixes and new features.
  • [N/A] I have updated the project documentation, if applicable.
    • This is required for new features.
  • [N/A] If this is my first contribution, I have added myself to the list of contributors.

After opening your pull request:

  • I have updated the project Changelog (this is required for all changes).
  • I have verified that the pre-commit.ci checks have passed.
  • I have verified that the CI tests have passed.
  • I have reviewed the test coverage changes reported by Coveralls.
  • I have requested a review from a project maintainer.

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.

better detection and reporting of scanned exams for groups

1 participant