Summary
KC Library content and the completion data it generates can move to external systems through three portability mechanisms: SCORM, xAPI, and API integrations. This article explains how each mechanism carries content or results between KC Library and an outside platform, and describes how course completion data can be exported in bulk to SuccessFactors.
Introduction
Organizations rarely run KC Library in isolation. Learning often needs to be delivered inside another platform, and completion records frequently need to land in a system of record such as an HR suite. Content portability is the set of standards and integrations that let library content and its results cross that boundary in a predictable, machine-readable form.
The three mechanisms covered here work at different layers. SCORM and xAPI are packaging and tracking standards that travel with a lesson, while an API integration is a data exchange that delivers completion records to a named external system. Understanding which one applies helps you choose the right path for a given destination.
Key Concepts
- SCORM: A packaging and runtime standard for a lesson. A SCORM lesson is played by the LMS and reports status and score back to the host platform so that learner activity is tracked in a standard way.
- xAPI: A statement-based tracking standard. Instead of only reporting completion inside a single course window, xAPI expresses learner activity as structured statements that can be recorded and shared with other systems.
- API integration: A data exchange that moves completion records out of KC Library and into a named external platform on a scheduled or on-demand basis.
- External courses: Course activity that must be reflected in a system outside KC Library. Integrations package that activity so the receiving platform can consume it.
- Bulk export: A one-time or periodic run that gathers completion records for an account over a date range and sends them to the target system, rather than syncing one record at a time.
- SuccessFactors integration: A supported destination for exported course completion data.
Steps to Follow
Choose the right portability mechanism
Decide how the content or data needs to travel before you act. If a lesson must be delivered and tracked inside another LMS, that is a SCORM or xAPI scenario, where the standard travels with the lesson and reports activity back to the host. If completion records need to reach a system of record such as SuccessFactors, that is an API integration.
Gather the export details
For a SuccessFactors export, decide on the scope of the run. You need to know which account's data you want to export, and you can optionally limit the run to a specific date range with a start date and an end date. If you do not set a start date, the export covers from the first day of the previous month; if you do not set an end date, the export runs through the most recent data.
Request the SuccessFactors completion export
The bulk export of course completion data to SuccessFactors is an integration operation run by KnowledgeCity for your account. To arrange it, contact your KnowledgeCity representative or support team and provide the account you want exported and, if needed, the date range to cover. They will run the export that gathers the matching completion records and delivers them to SuccessFactors.
Confirm the data reached the destination
After the run completes, verify that the expected completion records for the chosen account and date range appear in the receiving platform. If records are missing, recheck the account and the date range that were used, since an unset start date defaults to the first day of the previous month.
Conclusion
Content portability gives KC Library several ways to interoperate with external systems: SCORM and xAPI carry a lesson and its tracking into another platform, while API integrations deliver completion records to a named destination such as SuccessFactors. Matching the mechanism to your destination, and supplying the correct account and date range, keeps content and results moving reliably across system boundaries.