Catalogue modules

Intro

Catalogue modules can be used for two disntinct purposes: 1. As a collection of catalogues that are released to organisations 2. As a collection of courses for the purposes of Engauge programmes

Flowcode Catalogue Modules

Flowcode catalogue modules are a collection of catalogues. These collections are delivered to app users via the Strategy management area of the app. These catalogue modules are both seeded in the app, as well as created dynamically by the app administrators.

Engauge Catalogue Modules

Engauge catalogue modules are a collection of courses. These collections are delivered to app users via the Engauge area of the app. These catalogue modules are created dynamically by the app administrators.

Default catalogue modules

Default catalogue modules are added and managed in the CatalogueModules.php enum file. All default catalogue modules are of the flowcode type. If a new default catalogue module is added, it needs to be added to this enum file.

Seeding catalogue modules

Every time the app is deployed, the ProductionSeeder.php seeder will update the default modules making sure they are kept up to date.

Custom catalogue modules

Custom catalogue modules can be created in the app management admin area. If a type of flowcode is chosen, then any catalogues can be linked to the catalogue module. If a type of engauge is chosen, then any courses can be linked to the catalogue module.

Catalogue module organisation catalogues

Any organisation catalogues that have been added in an organisation, with the linked catalogue, will be available in the catalogue module.