QTI Package Maker

Converts question banks into portable LMS packages and standalone teaching formats, so instructors can move assessments between Blackboard, Canvas, and Moodle without rebuilding questions or losing embedded images.

Write the bank once. Deliver it wherever students need it. One source can become an LMS import, a readable review copy, a printable exam source, or a self-grading web quiz.

Blackboard image imports are backed by real Learn and Ultra sandbox probes. Canvas package structure and image references pass automated checks, but live Canvas image rendering remains unverified because the public Free for Teacher sandbox was discontinued. See docs/ENGINES.md for the complete compatibility matrix and exact limitations.

The first image shows the ready-to-answer state; the second shows the same item after a correct response. The same question bank that produces an LMS package can also produce this portable quiz: no server, account, or external image folder required.

• Move questions among Blackboard, Canvas, Moodle, and LibreTexts ADAPT workflows.
• Preserve embedded PNG, JPEG, and GIF figures in packaged LMS exports.
• Cover seven assessment types, from multiple choice to matching and ordered lists.
• Review content as readable text before importing it into a course.
• Publish a self-contained HTML practice quiz with instant grading.
• Use the command line for conversions or the Python API for generated question banks.

Requires Python 3.10 or newer; tested with Python 3.12.

python3 -m pip install qti-package-maker
printf 'MC\tWhat color is a clear sky?\tblue\tcorrect\tgreen\tincorrect\n' > bbq-demo-questions.txt
bbq_converter.py -i bbq-demo-questions.txt -1 -r -s

This converts one Blackboard question-upload row into three useful artifacts:

• qti12-demo.zip: a Canvas QTI 1.2 import package.
• human-demo.html: a readable review copy.
• selftest-demo.html: a self-contained, self-grading quiz.

Input rows are tab-delimited, and input filenames follow bbq-<name>-questions.txt. The complete installation paths, including virtual environments and PyPI, are in docs/INSTALL.md.

Select one or more outputs in the same conversion:

bbq_converter.py -i bbq-demo-questions.txt \
	-f canvas_qti_v1_2 -f blackboard_qti_v2_1 -f html_selftest

Use -a to select every CLI output or bbq_converter.py -h to see the available shortcuts. Some specialized engines are API-only; docs/USAGE.md covers the full CLI and Python API, while docs/FORMATS.md defines inputs and outputs.

Build a mixed question bank directly when the source is generated rather than stored in a text file:

from qti_package_maker import package_interface

bank = package_interface.QTIPackageInterface("bio101", allow_mixed=True)
bank.add_item("MC", ("What color is a clear sky?", ["blue", "green"], "blue"))
bank.add_item("MA", ("Which are primes?", ["2", "3", "4"], ["2", "3"]))
bank.save_package("canvas_qti_v1_2", "bio101.zip")

The result is a Canvas-ready QTI ZIP built through the same engine used by the command-line workflow.

Start here:

• docs/INSTALL.md: Setup, dependencies, and installation choices.
• docs/USAGE.md: CLI commands, Python API, images, and worked examples.
• docs/ENGINES.md: Complete engine, question-type, and media compatibility tables.
• docs/TROUBLESHOOTING.md: Symptoms, error messages, and fixes.

Go deeper:

• docs/FORMATS.md: Supported input and output formats.
• docs/QUESTION_TYPES.md: Fields for all seven assessment types.
• docs/CODE_ARCHITECTURE.md: Reader, item-bank, and writer data flow.
• docs/FILE_STRUCTURE.md: Repository layout and generated artifacts.

The project is beta software. Runtime modules require Python 3.10 or newer, while the development and test environment targets Python 3.12. Blackboard Learn and Ultra image paths have live-import evidence; Canvas image packaging follows the QTI structure and passes local integrity tests, but still needs verification in an institutional Canvas sandbox.

Code is licensed under the GNU Lesser General Public License v3. See LICENSE.LGPL_v3.

Created by Neil Voss. Follow the work on Bluesky, YouTube, or GitHub.

Support continued development through Patreon, PayPal, Bitcoin, or Dash.