Hello everyone,
\n
I don't understand the meaning of the new option released in November 2021: publication for LMS and LRS. The documentation says:
\n
\"Actor is the information used by the LRS to identify each learner—for example, the full name and email address of a learner. You don't need to supply the actor when you publish for xAPI or cmi5—your LMS supplies the actor. However, you must provide the actor when you publish for both LRS and SCORM or AICC LMS or you publish for LRS only.\"
\n
But what is the point then? If my LMS supports xAPI/CMI-5, why would I send data to another LRS?
\n
This option makes sense for those LMS that only support SCORM and cannot provide an actor. Articulate Storyline should receive the actor via SCORM automatically, for example, as it is done here:
\n
var studentID = pipwerks.SCORM.data.get(\"cmi.core.student_id\");
\n
One of the valid Inverse Functional Identifiers in xAPI is an account Object, which has two properties, homePage, and name. The name is the id that we just got through the SCORM API, and the homePage is an IRL that we must specify in the configuration of the course.
\n
As you can see this launch method constructs the user identity in an artificial way: getting part of it from the LMS, and using a pre-configured value to complete it. Obviously, this will only be useful if that way of identifying users is acceptable in your situation.
Hello everyone,
\n
I don't understand the meaning of the new option released in November 2021: publication for LMS and LRS. The documentation says:
\n
\"Actor is the information used by the LRS to identify each learner—for example, the full name and email address of a learner. You don't need to supply the actor when you publish for xAPI or cmi5—your LMS supplies the actor. However, you must provide the actor when you publish for both LRS and SCORM or AICC LMS or you publish for LRS only.\"
\n
But what is the point then? If my LMS supports xAPI/CMI-5, why would I send data to another LRS?
\n
This option makes sense for those LMS that only support SCORM and cannot provide an actor. Articulate Storyline should receive the actor via SCORM automatically, for example, as it is done here:
\n
var studentID = pipwerks.SCORM.data.get(\"cmi.core.student_id\");
\n
One of the valid Inverse Functional Identifiers in xAPI is an account Object, which has two properties, homePage, and name. The name is the id that we just got through the SCORM API, and the homePage is an IRL that we must specify in the configuration of the course.
\n
As you can see this launch method constructs the user identity in an artificial way: getting part of it from the LMS, and using a pre-configured value to complete it. Obviously, this will only be useful if that way of identifying users is acceptable in your situation.
Hi Lauren,
\n
Articulate has been supporting xAPI / CMI-5 for a long time. I don't understand what is the point of the November 2021 update. Prior to this update, Storyline courses were available in the LRS.
\n
As I understand it, the point is to send data to two LRSs at the same time? But what is it for?
\n
I was hoping that two standards could be supported: SCORM and xAPI (the course launched in the old LMS via SCORM and sends data to the LRS), but that doesn't work, since the old LMS cannot provide an actor. It is not possible to modify old LMS or cloud LMS that only support SCORM to provide an actor.
Hi Lauren,
\n
Articulate has been supporting xAPI / CMI-5 for a long time. I don't understand what is the point of the November 2021 update. Prior to this update, Storyline courses were available in the LRS.
\n
As I understand it, the point is to send data to two LRSs at the same time? But what is it for?
\n
I was hoping that two standards could be supported: SCORM and xAPI (the course launched in the old LMS via SCORM and sends data to the LRS), but that doesn't work, since the old LMS cannot provide an actor. It is not possible to modify old LMS or cloud LMS that only support SCORM to provide an actor.
Hello Oleg!
\n
The November 2021 update makes it possible to send data to an LRS, an LMS, or both. Publishing to two LRSs isn't an option.
\n
Does the LMS you're using also include an LRS?
Hi Lauren,
\n
How can I send data to both LMS and LRS, if LMS only supports SCORM and cannot provide an actor?
Hello Oleg!
\n
Which LMS are you using and I can see if your LMS includes an LRS?
