Catalog, native courses and SCORM packages
Create a course, add a native course file or upload a SCORM package into a draft version, publish it with a sign-off, and why a published version never changes.
The catalog holds every course and its versions. A course has a title, an audience and a summary. A version holds the duration, pass mark, validity and legal baseline, and one or more modules. A module is a native course, which plays in EU Training and is marked by EU Training, or a SCORM package.
A version is a draft until it’s published. A draft can be edited and its modules added or removed. A published version is frozen: it can be assigned, and it never changes again. A retired version can no longer be assigned; assignments, records and certificates keep pointing at it.
Read the catalog
Section titled “Read the catalog”Catalog shows a card per course with its thumbnail, audience, summary, number of versions, the published version, and the status of the newest one. Open a course for its versions, and a version for its settings and modules.
Give a course a thumbnail
Section titled “Give a course a thumbnail”On the course’s page, select Thumbnail and upload a PNG, JPEG or WebP image of up to 1 MB. Use 16:10, 960 by 600 pixels or larger, with the subject in the middle: cards crop it to a square or a strip. The image shows wherever the course appears, for every client. Uploading again replaces it, and Remove thumbnail goes back to the drawn artwork.
SVG is not accepted, because an SVG file can carry script. The seven Aigentcy courses ship with their thumbnails next to their packages.
Create a course and a draft version
Section titled “Create a course and a draft version”- Open Catalog and select New course. Enter the Title, and an Audience and Summary if they help. The slug is made from the title and never changes.
- On the course’s page, select New draft version.
| Field | What to enter |
|---|---|
| Version label | Such as 2027.1. Unique within the course |
| Duration in minutes | The expected time |
| Pass mark % | 0 to 100. 0 means completing it is enough |
| Valid for months | Empty when the certificate does not expire |
| Legal baseline | The date of the law the content follows, as YYYY-MM-DD |
The version’s page opens. Edit draft changes these until it’s published.
Add a native course
Section titled “Add a native course”Aigentcy’s own courses are built as a course file, <slug>.course.json, next to their SCORM package in courseware/dist/. Added to a version, the course plays in EU Training’s own player, and EU Training marks its knowledge check: the answers stay on the server, so a learner can’t read them from the page or report a pass the course didn’t give.
- On a draft version’s page, drop the
.course.jsonfile in Native course, or choose it. - Select Add native course.
EU Training checks the format, every lesson and block, and every question and its answer before it saves anything. A file that fails is turned away with the reason and adds nothing. One that passes becomes a module named after the course, shown as Native with the first characters of its SHA-256. Publishing freezes it with that hash, and the player refuses content that no longer matches it.
A course file can hold questions of four kinds (pick one, select all that apply, true or false, and a short case), a policy the learner accepts before the check, and an optional feedback questionnaire after it. Aigentcy’s annual update carries one of each.
The version’s pass mark is the one that counts, whatever the file says. Each attempt draws the number of questions the file names from its bank: 15 of 22 for most of Aigentcy’s courses, 15 of 25 for the annual update.
Upload a SCORM package
Section titled “Upload a SCORM package”- On a draft version’s page, drop the
.zipin SCORM package, or choose it. - Select Upload.
The page sends the file in parts and shows its progress, then checks the package and unpacks it. When it’s done, the package is a module of the version, named after the manifest’s title. Upload more packages for more modules.
A package is turned away, with the reason, when:
- it isn’t a zip, or has no
imsmanifest.xmlat the top, - the manifest doesn’t say SCORM 1.2 or 2004, has more than one SCO, or launches a file that isn’t in the package,
- it’s larger than 200 MB, holds more than 5,000 files, or unpacks to more than 1 GB,
- a file would land outside the package, is a link, is encrypted, or unpacks to more than the zip says.
Nothing of a refused package is kept. Recently turned away lists the last few with their reason.
If you close the page while a package is unpacking, it waits on the version’s page with Continue and Discard.
The packages built from this repo’s courseware are in courseware/dist/ after npm run courseware:build. The course catalog lists them.
Publish
Section titled “Publish”Under Publish, enter who Signed off by: the content owner who approved the version. Their name and the date go on the version. Publishing needs at least one module and no upload in progress.
Retire on a published version stops new assignments.
Changes ship as a new version
Section titled “Changes ship as a new version”A published version is the curriculum its records certify, so the app and the database both refuse to change it or its modules. A content change is a new draft version with the new package, published and assigned. People who passed the old version keep that record, and the new version gets its own.
How a package is kept apart
Section titled “How a package is kept apart”A SCORM package is code from a vendor, so it never runs as part of the app. It plays in a sandboxed frame on its own origin, it can’t read the session cookie or the app’s pages, and it can only reach the app through a bridge tied to one learner’s attempt at one module. Security and data covers it in full.