You can host TinQwise learning platform content in an external LMS, allowing content creators to craft unique learning experiences within the TinQwise platform and share these experiences on other platforms using Remote SCORM (or sometimes called proxy SCORM). SCORM provides a standardised way to host your learning content on a external LMS or system.

With this connection, learners can access one specific content part or an entire platform, depending on your set-up.

From learners' perspective:

A user logs into an LMS and selects a resource link to play a course. The course is launched in their own LMS system in an iframe and they land on the Discovery Stream.

Step 1. Before uploading the SCORM file to your external LMS, please contact TinQwise

Step 2. Go to Content > Integrations > Remote SCORM

Step 3. Click on Create Remote SCORM

Step 4. Title: give the connection a name that will be shown as the title in the external LMS.

Step 5. Add to the following groups: Select your target group (see the remarks in the Good to Know section to connect the group to the right content) Save the settings.

This will automatically create the Remote SCORM elements.

Step 6. After Save select Actions V dropdown and select “Download zip”. This ZIP file is your Remote SCORM file. This file is always version SCORM 2004 4th Edition (latest edition).

Step 7. The zipfile can be uploaded in the external LMS to access the content. (which should support the SCORM 2004 edition).

Step 8. Optional: View or change the Remote SCORM details via Actions > Remote SCORM details.

Step 9. Optional: Delete the Remote SCORM at Actions > Remove Remote SCORM. For total removal of a Remote SCORM, you also need to delete the voucher and group automatically attached to this SCORM at the Groups tab and Vouchers tab (look for the same name as the Title given in step 4).

The Remote SCORM zipfile is uploaded in the external LMS as 1 activity or tile you can click on. You can make multiple tiles by creating multiple Remote SCORM packages for different learning content. For example 1 zipfile for each journey will enable you to show the different journeys in different tiles in the external LMS.

User ID, first and lastname are read from the external LMS if they have all these fields available and passed to the learning platform via remote SCORM. You have limited user data, so email addresses, departments or functions are not included.

If a user has access to multiple Remote SCORM zipfiles, they will have a different User ID for each zipfile and thus multiple accounts are created for the same user when opening multiple zipfiles. This limits the overall reporting of one specific user.

There is always a parent group called “Remote SCORM groups” in which all remote SCORM users are automatically placed, with sub groups of each particular Remote SCORM you made. These groups are used for tracking who opened which zipfile and to see progression on the content made within the platform.

Remote SCORM offers limited insights. Completion rates are reported back as 0% with completion status “incomplete” until a user has completed 100% of the content available within the learning platform for the target group.

If the learner reached 100% progress, we will send back the completion status 'completed'. Some LMS-es also require success status to be set in order to complete a SCORM package, in those cases we also send success status “passed” to the LMS.