thoughtasylumTOOLBOX Preview Guides Use offline Automate Feedback

Tools › E-learning

SCORM Manifest Editor

Open a SCORM package (or a bare imsmanifest.xml) and fix its manifest in a form: the titles, the order of the items, each resource's launch file and file list, the mastery score and the identifier. The edited package is checked before you save a new ZIP.

About this tool What it's for, how to use it and an example

What it's for

Open a SCORM package, the ZIP you upload to a learning management system (LMS), and fix its manifest (imsmanifest.xml) in a form instead of in a text editor. You can change the manifest identifier, the course and organisation titles, the items in the course and their order, the file each resource launches and the files it lists, and, in SCORM 1.2, each item’s mastery score. SCORM 1.2 and SCORM 2004 are both supported.

For example, when an LMS rejects a package because the manifest lists a file that isn’t in the ZIP, or a course needs renaming and reordering without rebuilding it in the authoring tool, make the change here and save a new ZIP.

How to use it

Choose a package ZIP, or a bare imsmanifest.xml, or drop it on the page. Nothing is uploaded: it’s read in your browser. Then:

  • Titles, items and resources. Edit the fields. Move up and Move down reorder an item among the items at its own level; Add after adds an item next to it, and Remove removes it with any items inside it. Each resource has its launch file (href) and its list of files, one per line.
  • Files (ZIP only). It lists how many files in the ZIP no resource lists, and how many file entries the manifest lists that the ZIP lacks. Add missing files adds the unlisted ones to the resource you choose; Remove missing drops the entries the ZIP doesn’t have. A launch file that’s missing isn’t removed: it’s reported in the checks.
  • Checks on the edited package. After every change the edited manifest is checked in the same way as in the Package Inspector, so you see the errors and warnings before saving.
  • Save a new ZIP writes the package with the edited manifest, with -edited added to its name. The original isn’t touched. Save manifest only downloads just imsmanifest.xml.

Only what you change is rewritten. The rest of the manifest, including namespaces, comments, layout and SCORM 2004 sequencing rules, is kept exactly as it was.

Example

Save this as imsmanifest.xml:

<?xml version="1.0" encoding="UTF-8"?>
<manifest identifier="fire-safety" version="1.0"
  xmlns="http://www.imsproject.org/xsd/imscp_rootv1p1p2"
  xmlns:adlcp="http://www.adlnet.org/xsd/adlcp_rootv1p2">
  <metadata>
    <schema>ADL SCORM</schema>
    <schemaversion>1.2</schemaversion>
  </metadata>
  <organizations default="org1">
    <organization identifier="org1">
      <title>Fire Safety</title>
      <item identifier="item1" identifierref="res1">
        <title>Fire Safety Basics</title>
      </item>
    </organization>
  </organizations>
  <resources>
    <resource identifier="res1" type="webcontent" adlcp:scormtype="sco" href="index.html">
      <file href="index.html"/>
      <file href="missing.js"/>
    </resource>
  </resources>
</manifest>

Put any index.html and extra.js files beside it, select the three files (not a folder holding them), zip them, and choose the ZIP. The message line reads “No changes yet. Package checks on the edited package: 1 error, 1 note.” The error is “The listed file missing.js isn’t in the ZIP.” and the note is that extra.js isn’t listed. Press Add missing files, then Remove missing: the checks now say “no problems found”. Saving a new ZIP gives <name>-edited.zip with extra.js listed and missing.js gone.

Good to know

It edits the structure and file lists only: it doesn’t edit sequencing rules (SCORM 2004 imsss elements), which are kept as they are. Test the edited package in the Package Player and in your LMS before relying on it. The checks are the Package Inspector’s, not a validation against the SCORM XML schemas. Only the default organisation is edited, and an item can’t be moved into another item. Manifests in an encoding other than UTF-8 can’t be opened. A bare imsmanifest.xml can’t be checked against files. AICC and cmi5 packages aren’t supported: the Package Inspector checks them.

Built with The third-party code and data this tool uses, and their licences

This tool uses no third-party code or data of its own: its code was written for this site.

Every page also uses Montserrat (SIL Open Font License 1.1).
Everything the site uses is on Credits and licences.

Private: this tool runs in your browser. Nothing you type, paste or choose leaves this page.

Saved you a few minutes? Say thanks with a coffee.

Something wrong with this tool, or missing from it? Report a bug or suggest a feature.

↑ ↓ move↵ openesc close