Collection SCORM export

Exporting a whole collection as one SCORM package, with each course in it packaged as its own SCO.

Can I export a whole collection as a SCORM package?

Yes. You can export a collection as a single SCORM package instead of exporting each course in it separately. Every course in the collection is packaged as its own SCO (Shareable Content Object), so your LMS tracks completion and scores for each course individually rather than treating the whole collection as one item.

Before the export runs, Coassemble shows you a size estimate, so you know how large the package will be before you start.

Why does one SCO per course matter?

A SCO is the unit your LMS tracks, so packaging each course as its own SCO means:

• Per-course completion. Your LMS records which courses in the programme a learner has finished, rather than only whether they opened the collection.
• Per-course scores. A quiz result belongs to the course it sits in, so a learner's scores stay separated by course.
• Per-course reporting. Reports, rules and certificates in your LMS that key off SCO completion work at course level.

Exporting each course on its own and uploading them one at a time gives your LMS the same per-course tracking, but it leaves you managing several packages and re-uploading each of them when something changes. A collection export gives you that granularity in a single upload.

Which SCORM option do I need?

Coassemble handles SCORM in four distinct ways:

• Collection SCORM export. Take a whole collection out of Coassemble as one package, with one SCO per course. Use it when a multi-course programme has to run in your LMS and you want each course tracked separately.
• Course SCORM export. Take a single course out of Coassemble as a package. Use it when one course has to run in your LMS.
• SCORM hosting. Upload a package authored somewhere else and run it inside Coassemble exactly as it was built, with attempt-level reporting. Use it when the original interaction design has to survive intact.
• SCORM conversion. Upload a package authored somewhere else and turn it into an editable Coassemble course. Use it when you want to keep working on the content in Coassemble.

Frequently asked questions

Do I still need to export each course separately?

No. The collection export includes every course in the collection, each as its own SCO.

Why does the export show a size estimate first?

So you can check the package against your LMS's upload limit before you start, rather than finding out after the export has run.