[QTI] Reusable legacy→QTI assessment-item conversion utility

Overview

Build the reusable legacy→QTI conversion — structured single/multiple selection, input, true/false → <qti-assessment-item> XML. This is the pure conversion utility; wiring it into the API endpoint (dual-read) is #6030, and the one-time global backfill is #6007.

Complexity: Medium
Target branch: unstable

Context

Legacy items store structured question/answers with legacy types; the existing pydantic models already generate QTI for choice + text-entry — the legacy-expressible set.
A uniform QTI model removes publish-time format branching and the editor's legacy-edit path ([QTI] Support legacy assessment item types in the QTI Editor #5980 becomes unnecessary).
One conversion, three consumers: the API dual-read ([QTI] Serve legacy assessment items as QTI through the API endpoint (dual-read) #6030), ricecooker ingest ([QTI] Accept QTI items through the internal API for ricecooker import #6002), and the global backfill ([QTI] Backfill all non-raw AssessmentItems to QTI items #6007).

The Change

Provide a reusable legacy→QTI conversion producing <qti-assessment-item> XML from a structured item (single/multiple selection, input, true_false).
Make it lossless: prompt, choices/answers, correctness, hints, and media survive.
Leave perseus_question items untouched — out of scope here.
Surface items that fail conversion, rather than silently dropping them.

Acceptance Criteria

A reusable conversion produces <qti-assessment-item> XML from each supported legacy type (single/multiple selection, input, true_false)
The conversion is almost lossless: prompt, choices/answers, correctness, and media survive
Each converted item validates against the QTI 3.0 XSD ([QTI] QTI 3.0 schema XML validation utilities #6005)
Items that fail conversion are surfaced, not silently dropped
Tests cover conversion per legacy type

Out of scope

Hint conversion, this will be added in follow up

AI usage

Architecture decided with the maintainer across an iterative session: blanket QTI type with the item XML in raw_data; XSD-authoritative validation across all sources; a legacy→QTI global migration with an API-layer dual-read; ricecooker upload delegating to the AssessmentItem serializer; and a Perseus custom-interaction contract confirmed against the QTI 3.0 specification. Claude mapped the existing publish/validation/ricecooker code, proposed the breakdown, and drafted each issue; the maintainer steered every decision and reviewed throughout.

Watching for resolution on behalf of #6002.

Triage: mostly implementable as-is, with one blocking gap.

Already in place:

Choice/text-entry conversion for single/multiple selection, input, true_false exists in utils/assessment/qti/archive.py's QTIExerciseGenerator.
XSD validation ([QTI] QTI 3.0 schema XML validation utilities #6005) is done and already wired in.

Gap:

Acceptance criteria here require hints to survive losslessly.
Hint→QTI-catalog support doesn't exist in the generator yet.
That work is scoped to [QTI] Carry legacy hints into generated QTI items as dormant catalog content #6011, which is open and unimplemented — building it here would duplicate/conflict with [QTI] Carry legacy hints into generated QTI items as dormant catalog content #6011's PR.

Recommendation:

Land [QTI] Carry legacy hints into generated QTI items as dormant catalog content #6011 first, or fold its scope into this issue explicitly.
Then implement [QTI] Reusable legacy→QTI assessment-item conversion utility #6003 as extraction/consolidation of the existing per-type conversion logic into a standalone reusable utility for the three consumers ([QTI] Serve legacy assessment items as QTI through the API endpoint (dual-read) #6030, [QTI] Accept QTI items through the internal API for ricecooker import #6002, [QTI] Backfill all non-raw AssessmentItems to QTI items #6007).

The bot has been waiting for a response for 2 hour(s). It will resume automatically when someone replies.

Good point, I have removed the hints requirement from this issue, it will be handled entirely in follow up.

@rtibblesbot

Plan: Extract the existing legacy→QTI per-type XML-building logic out of the zip/archive-shaped QTIExerciseGenerator into a standalone, storage/Django-decoupled function that converts a structured legacy assessment item (single/multiple selection, input, true_false) into <qti-assessment-item> XML, so #6030 (API dual-read), #6002 (ricecooker ingest), and #6007 (global backfill) can each call it directly instead of re-implementing conversion.

Build the reusable qti/convert.py conversion module
Refactor archive.py to delegate to qti/convert.py

@rtibblesbot's comments are generated by an LLM, and should be evaluated accordingly

How was this generated?

Implemented code following the pre-approved plan using test-driven development (red-green-refactor)
Ran the project's full test suite and linter before committing
For UI changes: captured live screenshots to verify rendering
For backend changes: verified with example API/CLI output

The bot has been waiting for a response for 2 hour(s). It will resume automatically when someone replies.

Navigation Menu

Repository navigation

[QTI] Reusable legacy→QTI assessment-item conversion utility #6003

Overview

Context

The Change

Acceptance Criteria

Out of scope

AI usage

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

[QTI] Reusable legacy→QTI assessment-item conversion utility #6003

Description

Overview

Context

The Change

Acceptance Criteria

Out of scope

AI usage

Activity

rtibblesbot commented on Jul 3, 2026

rtibblesbot commented on Jul 4, 2026

rtibblesbot commented on Jul 4, 2026

rtibbles commented on Jul 4, 2026

rtibblesbot commented on Jul 4, 2026

rtibblesbot commented on Jul 4, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions