Import
Bring in QTI, IMSCC, Moodle XML, GIFT, and Aiken content with original source preserved.
RFPs ask for more than an editor. They ask for item types, item bank search, metadata, standards alignment, approvals, revisions, QTI fidelity, accessibility fields, and reportable item history.
The packet should include an item-type matrix with examples, QTI export notes, accessibility fields, and any current limitations. That is the artifact evaluators expect when an RFP asks about authoring coverage.
| Item family | Coverage | Status |
|---|---|---|
| Selected response | Single choice, multiple choice, multi-select, true/false | In build for launch |
| Text entry | Short answer, numeric entry, constructed response metadata | In build for launch |
| Matching and ordering | Associations, ordering, categorization, sequence evidence | In build for launch |
| Media-rich prompts | Images, audio, video, captions, transcripts, alt text, long descriptions | In build for launch |
| Rubric-scored work | Rubric metadata, scoring status, reviewer workflow, export notes | Planned |
| QTI package fidelity | Source package, preserved XML, conversion warnings, export validation | Ready |
Bring in QTI, IMSCC, Moodle XML, GIFT, and Aiken content with original source preserved.
Map content into the QFlowLearn item model without hiding warnings or unsupported transformations.
Approve fidelity, metadata, accommodations, standard alignment, and scoring before release.
Build assessment forms from reusable items and publish immutable versions for delivery.
The authoring packet should include item type coverage, metadata fields, revision history, standards alignment, source preservation, and clean QTI export samples.