Applicable Product:

PeopleFluent Learning
 

Applicable Release:

All Versions

Course administrators can create, update and delete learning modules and sessions by using the import functions in the Manage Center. For example, you can import individual courses on an ad hoc basis, or bulk import multiple courses at once by compressing them into a single ZIP file. With the Course CSV Loader you can also update learning modules whether they were created in the Catalog Editor or from imported course packages.

When you import courses into the LMS you can record and track enrollments, learner progress, assessment scores and other administrative data according to each course’s data model and communications standards.

Courses are usually collected into content aggregation packages. These are ZIP files containing all of the files that make up a course. When you import a course package it is validated according to its data model and communications standard, and then stored on your learning content server.

To facilitate communication between the LMS and other administration and analytics platforms, the LMS supports the following data model and communications standards:

• SCORM
• xAPI (also known as Experience API or Tin Can API)
• CMI5 (only available when importing to Rustici Engine)
• AICC

You will need to know which standard your courses 



If Rustici Engine is enabled for your LMS implementation, you can:

• Import new course content packages (including CMI5-based courses) into Rustici Engine
• Migrate existing courses to use the Rustici Engine launch interface.
• Migrate course revisions to the Rustici Engine for courses originally loaded to the original native LMS SCORM engine.
• Preview courses that have changed their launch interface to Rustici Engine.

For more information about the benefits of using Rustici Engine, and each standard, see the Rustici Software website. For more information about importing content packages and revisions into Rustici Engine, and migrating existing courses to Rustici Engine, see About Rustici Engine.

Content Packages with Non-English File Names

File names that contain non-English letters or digits in a content package must be encoded using the UTF-8 character encoding, otherwise the LMS cannot import them.