In KAF-based integrations, when looking in the KMC category tree, the categories that represent KAF channels in the external system (e.g. Moodle course or SharePoint site) are named using numbered IDs or GUIDs which sometimes may not even make sense to a KMC user, and may complicate the ability to locate the gallery within the KMC.
In KAF-based applications, the integration between the two systems is very loosely coupled and relies mostly on the SSO part that identifies the external user and the context for KAF.
Kaltura uses a context ID from the external system (e.g. Moodle course ID from the Moodle database, SharePoint site GUID) that is both unique and static.
Unique:
So that Kaltura will not come across a case that two different contexts will have the same identifier.
In Kaltura, categories in the same level (i.e. siblings in the tree) cannot have the same name. A unique value is required because the KAF channels are all siblings under the "Channels" category.
Static:
A value that never changes.
Due to the fact the integration is loosely coupled, the KAF-based solutions are not aware of events, for example "course name changed".
For example, If a value that is not static is used (can be changed by the system, or by the user), when the KAF gallery is loaded in the same context after the name was changed, all previously assigned content is lost.
KAF cannot be configured to use other SSO attributes as category names. In all Kaltura's KAF-based applications, this "configuration" is statically set in the code.
