Exports

The QTI packages made from a tenant's content, to download and check.

For authors · Open this screen

An export makes a QTI 3.0.1 content package: a zip that another QTI system, or another AIB tenant, can import. Exports run in the background and are listed here until they expire.

Starting an export

• Export › QTI package on a test, section, item or stimulus page exports it and everything it uses: a test brings its sections, items, stimuli and media.
• Export selected on Resources exports the rows you ticked.
• Whole bank, for site admins and for tenant admins whose tenant has the whole-bank export feature, is on Tenant Admin › Utilities.

The dialog asks how to include metadata:

• Inline: inside the package’s manifest, where most systems look for it.
• As files: as separate metadata files.
• None: no metadata.

Your tenant admin chooses which is offered first.

The list

Each export shows what was exported, its state (queued, building, validating, then ready, refused or failed), when it was started, and its actions:

• Download the package.
• Findings shows what the package validator reported. A package is checked as strictly as the public validator checks.
• Delete removes the package and its findings. You can delete your own; tenant admins can delete any.

Invalid packages

If the validator finds errors, your tenant decides what happens: by default you can still download the package, with the findings to read; a tenant set to refuse keeps only the findings.