Skip to content

scormConverter

Python script that relabels SCORM 2004 3rd Edition packages as 4th Edition

Maintained Last commit Checked · 24 Aug 2026

The facts

Licence
MIT — OSI approved
Pricing
Open source
Deployment
Embedded in your own application
Platforms
Command line

Standards support

Every line says where the claim came from. We do not test conformance ourselves and we issue no badge of our own.

Standards support for scormConverter, with the source of each claim and the date it was last confirmed.
Standard Supported Provenance Checked Note
SCORM 1.2 Not stated
SCORM 20043rd, 4th editions Yes editor-checked · 24 Aug 2026— source, opens in a new tabParseXML.py rewrites the manifest's schemaversion element to "2004 4th Edition" and removes imsss:sequencing and metadata elements from the organization and its items. It does not otherwise transform the package. Read in source, August 2026.
xAPI Not stated
cmi5 Not stated
AICC Not stated
LTI Not stated
Claimed
— the vendor states it. We have not confirmed it.
Checked
— an editor confirmed it on the date shown.
Verified
— an official registry lists it, and we link to the entry.

Editor's notes

This is a hundred-line Python utility across three files, written for one migration and published as-is. The author's organisation was moving from ILIAS to SAP SuccessFactors and found that SCORM 2004 3rd Edition packages which ran happily in the old system were rejected by the new one. Rather than re-author, they wrote a script that unzips each package, rewrites the schemaversion element in imsmanifest.xml to "2004 4th Edition", strips the imsss:sequencing and metadata elements out of the organization and its items, and zips it back up.

Understanding what that is, and is not, matters. It is not a conversion between editions — no data-model migration, no sequencing translation, no validation of the result. It is a workaround for an importer stricter than the specification requires, and dropping the sequencing rules is a silent behavioural change rather than a side effect.

Judged as a product it is unremarkable: three commits, all on one day in October 2024, no stars, no tests, and a README that documents its own dependencies as os, ZIP and ParseXML. Two details should stop you running it unattended: it deletes each source zip after extraction, and it joins paths with hardcoded Windows backslashes.

Judged as what it is — a shared workaround for a common and badly documented import failure — it is worth reading. The forty lines of ParseXML.py will tell you in two minutes whether your rejected package has the same cause, which is more than most vendor support tickets achieve.

Listed on scorm-tools.com

Maintainers and vendors are welcome to show the listing badge in a README or on a product page. It is free, it does not require a claim, and there is nothing to buy.

Get the embed code