Edge Import - Learning Load Enhancements (Training Loads)
With this enhancement, training loads are updated with new fields and functions.
Material Load
Previously, administrators could create and update materials in bulk with all portal-supported file types except for .ppsx. With this enhancement, the Material load now supports the .ppsx file type when creating or updating materials.
ILT Events Load
Previously, administrators could use this load to translate event-related standard and custom fields except Event ID. With this enhancement, the ILT Events load now supports the import of translations for the Event ID field. To use this field, the load configuration should be a Translation load type with Learning Object as the unique identifier.
ILT Session Load
Previously, administrators could use this load to translate session-related standard and custom fields except Session ID. With this enhancement, the ILT Session load now supports the import of translations for the Session ID field. To use this field, the load configuration should be a Translation load type with Locator Number as the unique identifier.
Previously, when the unique identifier is set to "Unique Session ID across all Events," the Event ID was always required. However, it should only be required when creating new sessions. With this enhancement, when the unique identifier is set to "Unique Session ID across all Events," the Event ID is only required when creating new sessions. In the template guide, the description for Event ID is updated to reflect this behavior. An error is displayed if the Event ID is not provided for a new session when Session ID is unique across all events.
Curriculum Load
Previously, administrators needed to complete two loads to fully create curricula, the Curriculum load to create the curriculum and the Curriculum Structure load to add child learning objects. With this enhancement, the Curriculum load is enhanced with Child LO ID and Section Name fields. This ensures at least one child learning object is added to the new curriculum structure. These fields are only required when creating new curricula. These fields are not applied when updating curricula, as administrators should use the Curriculum Structure load to update the curriculum structure.
LO Equivalency Load
Previously, administrators could use this load type to apply equivalencies to future transcript transactions, but equivalencies could not be applied retroactively. With this enhancement, an Apply Retroactively field is now available, and this field is optional. This enables administrators to apply equivalencies retroactively in bulk.
LO Availability Load
For LO Availability loads, the existing Availability Type field is repurposed and renamed to Availability Criteria. Existing saved configurations cannot be used. Administrators must create new configurations and delete existing configurations.
Previously, administrators could manage LO availability in bulk, but they could not set the training as Required, Suggested, or Featured. With this enhancement, a new Availability Type field is added. This field is optional, and it can be used to set the training as Required, Suggested, or Featured. When the Availability Criteria is removed via the data load, the respective Availability Type is also removed.
Previously, the LO Availability load could only be used for manual, one-time loads. With this enhancement, automated scheduled feeds and Bulk API are now supported for this load type. Access to this functionality is controlled by new permissions. Also, Bulk API must be activated.
Online Content (OLCO) Metadata Load
Previously, the Online Content (OLCO) Metadata load could only be used for manual, one-time loads. With this enhancement, automated scheduled feeds are now supported for this load type. Access to this functionality is controlled by a new permission.
Online Content (OLCO) Transcript Load
Previously, the Online Content (OLCO) Transcript load could only be used for manual, one-time loads. With this enhancement, automated scheduled feeds are now supported for this load type. Access to this functionality is controlled by a new permission.
Thumbnail Images
Previously, administrators could not add thumbnail images to training in bulk. With this enhancement, a Thumbnail field is now available, and this field is optional. This allows administrators to apply thumbnail images to training in bulk. If no value is provided for this field, the Default Training Image Preferences are applied. The thumbnail image file must be placed in the Cornerstone FTP location in the following folder: LMS/[TRAINING LOAD TYPE]/Thumbnail. This FTP folder structure should be created it if does not already exist.
This applies to the following load types:
To remove a thumbnail image that is already set for a training item, load the training with a blank value for the Thumbnail field and set the configuration to Apply Default Value for blank values. Following the load, the default thumbnail image will be applied based on Default Training Image Preferences.
Starter Guide
Select this link to download the Edge Import - Learning Starter Guide.
Implementation
This functionality is automatically enabled for all organizations using Edge Import. The template guide in Edge Import will be updated to reflect these enhancements.
Permissions
The following new permission applies to this functionality:
PERMISSION NAME | PERMISSION DESCRIPTION | CATEGORY |
Access Bulk API - LMS - LO Availability | Grants access to the LO Availability load in the Bulk API. This permission cannot be constrained. This is an administrator permission. | Edge Import |
Access LMS - LO Availability Feed | Grants access to the LO (Learning Object) Availability data feed via Edge Import. This permission cannot be constrained. This is an administrator permission. | Edge Import |
Access LMS - OLCO Metadata Feed | Grants access to the Online Content Metadata data feed via Edge Import. This permission cannot be constrained. This is an administrator permission. | Edge Import |
Security Roles
Upon release, the new
, , , and permissions are automatically granted to the default System Administrator role. Administrators must grant these permissions to other roles, if necessary.