Text entry variables and xAPI

Hi ElizabethPat123 this is more of a thought bubble than a solution.

I'm wondering if rather than using a Storyline variable you could use the Slide.Id variable to associate the use note with the relevant slide. Each slide has a unique ID, for example 5rUJg6NfRQQ.

Could use use this with xAPI to Set/Get the comments for each slide?

I like Sam's idea, for your xAPI statement you could either send all the statements at the end, use numbered variables and loop through that would save loads of time rewriting. Or you could use numbered variables in storyline and then set a number variable at timeline start that corresponds to the variable being used and use code to combine the two, so you in effect use the same code on every slide and it pulls the right variable. Both would save time.

We can dynamically gather these variables and values (key | value pair), store variables and their values in a single variable (xapiResponse), and send that information in an xAPI format but only with a consistent naming pattern (e.g., comment_1, comment_2, comment_3, ... comment_n). Then we can use JavaScript to retrieve each variable’s value and build a response that will be sent in the xAPI statement.

Example JavaScript:

var totalVars = 130; // less or more
var responses = [];

for (var i = 1; i <= totalVars; i++) {
    var varName = "comment_" + i;
    var varValue = getVar(varName);

    if (varValue && varValue.trim() !== "") {
        responses.push(varName + ": " + varValue);
    }
}

var jointResponse = responses.join(" | "); 
setVar("xapiResponse", jointResponse);
console.log("xapiResponse set to:", jointResponse);

xAPI statement:

In this example, I used the JavaScript code above along with a single xAPI statement, which is executed on the master slide when it loads. 

However, this approach can be further optimized by modifying the script to only include variable | value pairs relevant to the current slide, rather than sending all comment variables and values at once.

I personally prefer sending the xAPI statement at the end, after all text entry fields have been filled. This ensures that all user inputs are captured, reducing redundant xAPI calls.

Again, this approach is only possible if a structured variable naming convention is planned ahead and followed from the beginning.

I'm liking the idea of one statement at the end because it's too easy to have a typo in 130 different statements.  Thank you for the code. 

Right now I'm using the question name  (e.g., Comment_Mary1, Comment_Mary2, Comment_Mark1) as the comment name.  The questions are named not numbered because we are pulling from a test bank (learner confused if they get questions 37, 45, 63?).

If I rename all the comments 1, 2, 3, and pull them in a list at the end, how will I know which comment refers to what question?