The ability for SCORM dispatch packages to be distributed to external users (e.g. clients). The Absorb LMS hosted content/SCORM package is distributed to a client where they can upload and access the content on their own respective LMS, however the SCORM file and user completion data remains within Absorb LMS. Very similar to SCORM Cloud Dispatch.
This has become an increasingly requested feature for us where our third party content partners wish to offer their courses on our Absorb LMS but require to manage version control from their own LMS.
We would also like this feature. We currently sell scorm packages to external clients that they host on their LMS. A scorm dispatch method would give us greater security and visibility. We ask external clients to sign a non disclosure agreement, but once we send the scorm package to them, we are trusting them not to distribute or resell it without our permission, but there is currently no way to prevent that from happening. Even though they would break the law if they redistributed the scorm package after signing the agreement, there is no current way of stopping this from happening and we can only attempt to deal with the issue in retrospect, and potentially only be protected by the laws of the country that we distribute from - eg may be no option of enforcement of law for overseas clients. A scorm dispatch wrapper would provide that missing level of security. In addition, a scorm dispatch wrapper would give us visibility of all the external LMS participants that are accessing the scorm package, whereas currently we are relying on the external client to renew their subscriptions based on the number of participants that they tell us they will enrol - we currently can't see how many participants they actually enrol. Like scorm cloud, Moodle has a similar scorm dispatch feature. Perhaps you could look at that plugin to see how it works - as it is open source. Absorb would benefit from this feature by gaining revenue for all the duplicate accounts that would be created and then charged to their customers - ie all the accounts that are using these dispatched scorm packages on external LMSs would also get created in Absorb LMS for reporting purposes - and then charged to their customers - perhaps it could be a lower cost for these accounts since they would only be used for reporting and not actually logging in to the Absorb LMS. Absorb will potentially lose this revenue without providing this feature, eg if Absorb customers decide to use scorm cloud dispatch - Rustici will get paid for those external LMS accounts instead of Absorb.
This option would be very attractive to many of our clients who can't change systems/LMSs but who wish to use our e-learning content in a seamless way (i.e. avoiding the need to login to a different system or use access key etc.) It would allow us to manage our content (users/licences) and control version updates etc. from our own Absorb LMS) and allow us to cell to wider audiences. Thanks