Bulk-import training courses

What this achieves

A provider’s whole catalogue can be loaded from one file instead of entered course by course. The import checks the file first and tells you which rows it cannot use, before anything is created.

Required role: Humavera platform staff.

Before you start

Add the providers first. A row naming a provider that does not exist is flagged and skipped, so importing courses before their providers wastes a pass.

Steps

Go to Platform → Training Courses.
Select Download reference to get the reference file.
Prepare your file against it.
Select Bulk import.
Choose the file. The dialog reads it and shows what it found.
Read Total rows, Ready, and Flagged, and work through the flagged rows.
Select the import action to create the rows that are ready.

Reading the preview

Option	Description
Total rows	How many rows the file holds.
Ready	How many will import.
Flagged	How many will not.

Each flagged row is listed with its row number, the field at fault, the value found, and the reason. Rows are flagged where a skill, a sector, or a provider in the file does not match anything on the platform.

Example: a row naming a skill that is not in the shared library is flagged against that field, with the value it could not match. Correcting the spelling in the file is usually all it needs.

Flagged rows are skipped, not guessed at

The import creates the ready rows and leaves the flagged ones alone. It does not invent a provider, add a skill to the library, or approximate a sector to get a row in.

That means a partial import is a normal outcome: fix the flagged rows in your file and upload it again to bring them in. The rows that already imported are unaffected.

Check the reference file each time

Download reference gives you the current shape the import expects, along with the values it will match against. Take it fresh rather than reusing an old copy, so that a file prepared over several days is still checked against what the platform holds today.

What happens next

Imported courses appear in the directory under their providers, with whatever tags the file carried, and every customer workspace can find them. Anything the import could not resolve is either fixed and re-uploaded or added as a single course by hand.