Edge Import - ILT Sessions Load and Feed

Sessions enable administrators to create any type of scheduled learning event. It is helpful to think of sessions as scheduled instances of instructor-led training courses or individual occurrences of Events. Sessions hold more specific data, including the times, locations, and trainers for a specific course instance.

It is a best practice to load event data prior to loading session data. Session part data should be loaded after loading session data, if necessary.

Starter Guide

Select this link to download the Edge Import - Learning Starter Guide.

Select this link to download the Edge Import Learning Loads Migration Guide.

Unique Identifiers

When loading session data, the unique identifier for sessions can be provided in the following ways:

  • Unique Session ID across all Events - Select this method when you have unique Session IDs available and want to import new sessions or update existing sessions.
  • Unique Session ID within each Event - Select this method when you have a unique combination (Event ID + Session ID) available and want to import new sessions or update existing sessions.
  • Session Locator Number - Select this method when you want to update existing sessions or when your Session ID is not unique in the portal. Session Locator Number cannot be used to create new sessions.

When loading session data, the unique identifier for events can be provided in the following ways:

  • Event ID - Select this option when the existing event in the portal has a unique Event ID.
  • Learning Object ID - Select this option when the existing event in the portal does not have an Event ID and Learning Object ID is the only way to reference the event.

The following examples show how unique session and event IDs can be used:

  • Unique Session ID across all Events - If two events in the system have the same Session ID, then this option would be invalid.
    • Example: If Event A has a Session 1 and Event B has a Session 1, this would be invalid.
    • Example: If Event A has a Session 1 and Event B has a Session 2, this would be valid.
  • Unique Session ID within each Event - The new Session ID will be loaded as a combination of Event ID and Session ID (“EventID:SessionID”).
    • Example: If Event A has a Session 1, and Event B has a Session 1, this will be loaded as Event A:Session 1 and Event B:Session 1.

Session Parts

For new sessions, the following occurs:

  • One session part is created automatically using the session start date and time, session end date and time and time zone provided in the file.
  • The part name can be provided. If a part name is not provided, the default part name is "Historical Data."
  • The frequency (Part Occurrence) is set as Once. Multiple occurrences is not supported.

Session Start and End Date and Time

Session start date and time must be less than or equal to Session end date and time.

If the time value does not contain a value for HH:MM, 00:00 will be used.

One-day sessions must contain the hours and minutes.

Event Default Values

For new sessions, the following fields from the event are used as session default values when the fields are not available or not mapped in your configuration:

  • General Fields:
    • Availability
    • Available Language
    • Min and Max Registration
  • Penalty Fields:
    • Penalty for No Show
    • Penalty Percentage
    • Penalty Amount
    • Penalty Number of Days Prior to Start
  • Refund Fields:
    • Refund Percentage
    • Refund Amount
    • Refund Number of Days Prior to Start

Session Status

Session status cannot be updated using Edge Import.

Depending on the load configuration, past-dated sessions can either be imported as Completed or Approved. A past-dated session is a session with a start date that is earlier than the import date.

  • Completed - Select this option to import past-dated session as Completed for historical record purpose.
  • Approved - Select this option to import past-dated session as Approved for session status to be further managed from portal.

Future-dated sessions are loaded as Approved and will never be completed by Edge Import, irrespective of transcripts loaded for that session. A future-dated session is a session with a start date that is later than the import date.

Learning Object Availability Settings

Availability for this learning object type is set using the Learning Object (LO) Availability Load.

Only the following availability related criteria can be loaded using this data load type:

  • Availability: All Users - When this is set to true, it overrides all other availability settings for the learning object.
  • Register Upon Approval
  • Pre-approved
  • Include Subordinates

Considerations

The following considerations apply to this load type:

  • Events must be loaded prior to loading sessions.
  • Depending on the configuration, the Session ID or the combination of Event ID and Session ID must be unique.
  • After a session is created, sessions can be updated using Edge Import regardless of the session status (i.e., approved, expired, tentative, or completed).
  • Sessions in an Approved status cannot be marked as Completed using Edge Import.
  • Session date and time cannot be updated once the session is created.
  • The data load does not check for conflicts, which means the data load does not check if multiple sessions are being conducted at the same date, time, and location.
  • Providers are also referred to as vendors.
  • When Session Locator Number is selected as the unique identifier for the load, an optional New Session ID field is available. This enables organizations to update the Session ID for sessions. The Session ID value is only updated if a new Session ID value is provided; it cannot be updated with a blank value. The Session ID value does not need to be unique.
  • Administrators can set the provider for a session when creating new sessions if the Enable to select provider when creating sessions. option is selected in ILT Preferences. See ILT Preferences - General.
  • Review the latest template guideline for fields that are not visible in the template but do have default values for new Sessions.