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 Leslie,
\n
sorry for the bad english.
\n
What I'm trying to say is: in old or cloud-based LMSs that only support SCORM, there is no way to provide an actor. Therefore, the new publishing options added in the November 2021 update don't make any sense. We cannot change the LMS configuration for us or our clients.
\n
It makes sense if Articulate Storyline will automatically get an actor from SCORM, without involving IT staff. I gave in the post an example of the implementation of the approach in the courses Adapt Learning.
\n
Here's a similar question from another user: https://community.articulate.com/discussions/articulate-storyline/how-do-i-create-an-actor-query-string-when-using-xapi-statemnt-trigger-but-publishing-for-scorm
Hi Leslie,
\n
sorry for the bad english.
\n
What I'm trying to say is: in old or cloud-based LMSs that only support SCORM, there is no way to provide an actor. Therefore, the new publishing options added in the November 2021 update don't make any sense. We cannot change the LMS configuration for us or our clients.
\n
It makes sense if Articulate Storyline will automatically get an actor from SCORM, without involving IT staff. I gave in the post an example of the implementation of the approach in the courses Adapt Learning.
\n
Here's a similar question from another user: https://community.articulate.com/discussions/articulate-storyline/how-do-i-create-an-actor-query-string-when-using-xapi-statemnt-trigger-but-publishing-for-scorm
Hi Oleg,
\n
Check out our documentation here.
\n
If you'd like to send to an LMS and an LRS, make sure both are selected.
\n
In addition, since you're using SCORM, be sure to provide an Actor during your LRS configuration:
\n
Your LRS admin or IT staff will use scripts to supply the LRS details, including the actor, endpoint, and credentials.
Hi Oleg,
\n
Check out our documentation here.
\n
If you'd like to send to an LMS and an LRS, make sure both are selected.
\n
In addition, since you're using SCORM, be sure to provide an Actor during your LRS configuration:
\n
Your LRS admin or IT staff will use scripts to supply the LRS details, including the actor, endpoint, and credentials.
