Producing Human Readable Tin Can Activity IDs from my Storyline Package to my LRS

I'm currently using Storyline, and am testing a Tin Can LMS option. I am having difficulty getting the Activity IDs in my LRS to display in a human readable format. Is there anything that I can do within my Storyline package to make sure my Activity IDs display in a human readable format? Is this something that I would have better success with if I upgraded to  Storyline 2?

2 Replies
Ashley Terwilliger

Hi Jennifer, 

Tin Can API lets an activity be defined in a statement or in the tincan.xml file. We've chosen to define all activities in the tincan.xml file to improve LMS reporting. As a result, learners' responses must be cross-referenced with the tincan.xml file to be readable.
To be specific, the tincan.xml file gives the LMS all the metadata about the content (question text, answer choices, etc.), then we send statements to the LMS with unique identifiers that are defined in the tincan.xml file. To generate meaningful descriptors for learners' responses, the LMS needs to cross-reference the unique identifiers with the tincan.xml file.
This architecture is part of the Tin Can API specification defined here.
Here's an excerpt that describes what we're talking about: 
"What TinCan.xml should have is: Any activity details (such as activity descriptions) that should be available to reporting systems, but will not be (or may not be) sent by the activity provider when reporting statements. That is, TinCan.xml may be used to describe activities to the LRS, as an alternative to doing that description at runtime." 
The reason we exclude meaningful descriptors from our statements to the LMS in favor of collecting them in the tincan.xml file is so the LMS will know about all answer choices and not just those the learner selected.
You can find more technical information to help LMS developers implement Tin Can API for Articulate content here.
Hope that helps!