EdCast supports integrating with content providers, Learning Management Systems or any external system by fetching the metadata from the source system.
After fetching the metadata of the content, the content is replicated in EdCast in the form of a SmartCard. The SmartCard maintains a reference to the actual content in the form of a deep link URL. Once the SmartCard is created in the EdCast system, it can be searched , assigned , added to pathways, journeys, channels - i.e all standard EdCast functionalities which are available for manually created SmartCards are also available for SmartCards created via integrations
Only metadata is shared with EdCast via integration. The content resides in the source system. A link is provided in EdCast to navigate the user to the source system where the content is then consumed.
During this navigation, SSO (via SAML2.0) is supported by EdCast for authentication.
The source system can share the completion records (after the content has been consumed) back with EdCast and the same can be reflected on EdCast
The below approaches can be employed to import the content metadata & completion events with EdCast
The catalog metadata is provided in a CSV format & is manually uploaded to the EdCast system.
The catalog metadata / completions data is provided in a CSV format on a SFTP location & is automatically uploaded to the EdCast system on a schedule.
EdCast LMS APIs can be consumed to push catalog & completions data to Edcast
EdCast also supports importing Completions events via xAPI
EdCast provides standard connectors for importing content metadata & completions
EdCast supports importing User Data from HRMS systems through Integrations
Once the user data has been imported into EdCast, users can be searched , assigned content, added to groups etc - i.e all standard EdCast functionalities which are available for manually created users are also available for users imported via Integrations.
In addition to the basic 5 fields - First Name, Last Name, Email Id , External Id & status ( active / inactive / suspended) , custom fields (upto max 20) , the user's learning goals & the immediate manager can be also be imported.
This flow of user data is one way - i.e. only from source system to EdCast.
The below approaches can be employed to import the user data into EdCast .
The user data is provided in a CSV format & is manually uploaded to the Edcast system.
The user data data is provided in a CSV format on a SFTP location & is automatically uploaded to the Edcast system on a schedule.
Edcast User Management APIs can be consumed to push user data to Edcast
Edcast provides standard connectors for importing user data from
Updated over 1 year ago