Exporting and Downloading

Overview

When your course is complete, you'll:

1. Export it as a SCORM package
2. Download the ZIP file
3. Upload to your LMS
4. Or publish directly

The exported package works in any SCORM-compatible LMS.

How It Works

Exporting transforms your Course Builder project into a standard SCORM 2004 package. The system compiles all your content, configurations, and assets into a self-contained ZIP file that can be used in any SCORM-compatible learning management system.

The Export Process

When you click Export, the system performs several steps:

1. Content Collection - Gathers all pages, content blocks, images, videos, and other assets
2. Asset Processing - Optimizes images, embeds videos, and prepares media files
3. SCORM Runtime Generation - Creates the SCORM API wrapper and communication layer
4. Manifest Creation - Generates the imsmanifest.xml file with course metadata, structure, and resources
5. Metadata Embedding - Includes project name, description, version, and configuration settings
6. Package Assembly - Compiles everything into a ZIP file following SCORM 2004 specifications
7. Validation - Ensures the package meets SCORM standards
8. Download Ready - Makes the ZIP file available for download

What Gets Included in the Package

The SCORM package contains:

SCORM Package Structure

The exported ZIP file follows SCORM standards:

• imsmanifest.xml - The manifest file that defines course structure, metadata, and resources
• HTML Files - Your course pages as HTML files with embedded content
• Assets Folder - Images, videos, and other media files
• SCORM Runtime - JavaScript files for LMS communication and tracking
• Metadata - Course information embedded in the package

Version Control

Each export creates a version:

• Version Numbering - Each export increments the version number
• Export History - Previous exports are tracked with timestamps
• Project Persistence - The project remains editable after export
• Multiple Exports - You can export the same project multiple times as you make improvements
• Version Metadata - Version information is embedded in the SCORM package

After Export

Once exported:

• Download Available - ZIP file is ready for download
• Project Unchanged - Your project remains in the editor (you can continue editing)
• Upload to LMS - Use the ZIP file to add the course to your LMS
• Immediate Use - The package can be used immediately in any SCORM-compliant LMS
• Tracking Enabled - Full SCORM tracking (progress, scores, completion) is functional

Before Exporting

Pre-Export Checklist

Common Last-Minute Checks

Exporting Your Course

What Happens During Export

1. Collects all your content (pages, blocks, assets)
2. Generates the SCORM runtime files
3. Creates the imsmanifest.xml
4. Packages everything into a ZIP
5. Makes it available for download

Export Duration

SCORM Package Contents

What's in the ZIP

course-package.zip/
├── index.html          # Main course entry point
├── runtime.js          # Course logic and quiz
├── styles.css          # Visual styling
├── imsmanifest.xml     # SCORM manifest
├── assets/             # Shared resources
│   ├── fonts/
│   └── icons/
└── images/             # Your uploaded images
    ├── image1.jpg
    └── image2.png

Key Files

SCORM Compatibility

SCORM Version

Packages are SCORM 2004 compliant:

• Full completion tracking
• Score reporting
• Pass/fail status
• Bookmarking (resume)
• Interaction tracking

LMS Compatibility

Uploading to Your LMS

In TrainMe UK LMS

1. Go to Admin → Course Management
2. Click Add Course
3. In the SCORM File section, upload your ZIP
4. System detects SCORM version
5. Complete remaining course details
6. Save the course

In Other LMS Systems

1. Access LMS admin area
2. Find SCORM upload/import option
3. Upload the ZIP file
4. Configure course settings
5. Make available to learners

Version Management

Export Versioning

Each export increments the version:

• First export: v1
• After changes + export: v2
• And so on...

When to Create New Version

File Management

Naming Conventions

Default naming: {project-name}-v{version}.zip

Example: Fire-Safety-Training-v2.zip

Organising Downloads

SCORM Packages/
├── 2025/
│   ├── Fire-Safety-Training-v1.zip
│   ├── Fire-Safety-Training-v2.zip
│   └── Data-Protection-v1.zip
└── Archive/
    └── Old versions...

Keeping Backups

• Save copies of each version
• Store in cloud backup
• Document what changed per version

After Export

Testing the Package

Before deploying widely:

1. Upload to test environment
2. Launch and complete as learner
3. Verify: Content displays, quiz functions, score recorded, completion tracked

Deployment

1. Make course active/available
2. Assign to appropriate learners
3. Monitor initial completions
4. Address any issues

Best Practices

Export Workflow

1. ✅ Complete all content
2. ✅ Preview and test thoroughly
3. ✅ Fix all issues
4. ✅ Save all changes
5. ✅ Export
6. ✅ Download
7. ✅ Test in LMS
8. ✅ Deploy

Quality Assurance

Troubleshooting