I have been tasked with exploring the implementation of an LRS system. I have noticed that Storyline automatically sends statements when a user enters and leaves a slide.
Is there anyway to stop this from happening?
Many Cloud based LRS services have a statement limit of some kind, and having two statements per slide really eats into that limit and is kind of redundant if you are planning to record other interactions anyway.
xAPI is designed to provide much finer insights to learner's activities so more numerous outbound statements is expected. Frankly I'm surprised you're seeing two; xAPI can track click/tap activities in fine detail, etc beyond the back/next
If the LRS you are evaluating limits statement capture, I'd strongly suggest looking elsewhere as the commercial grade LRS systems I've leveraged for client projects easily handle thousands of statements without blinking an eye
It sounds like you were looking for more control over the Storyline activity statements that get sent to an LRS. Glad to see that Brian has been helping you out!
Currently, there isn't an option within Storyline to restrict what is sent. However, I did find a related discussion where some users shared a workaround that uses Javascript.
My issue is that it is sending two statements automatically, and they are not purposefully built statements (ones we really want or need recorded). A greater level of control is needed.
My research has shown that most LRS have some upper limit on statements per day on top of a total storage limit. And they offer tiered packages to expand. An on-premise solution is probably not as limited, but is not an option in an early exploratory phase. I'd be open to hearing your recommendations on particular vendors.
I think we are dealing with different volumes. My unit runs 50+ courses (most with 6+ modules, around 60 slides each), with 10-50 learners. So two statements might not be much, but it adds up quick. If added to every course and module, we could possibly hit more than a million total for a semester. On average, I'd say there are three statements we'd want to pull per slide, but if two are added automatically its close to doubling the amount of statements and the cost associated. I am calculating on a single course at first and would easily be more than 10,000 statements.
It is disappointing that there has been no resolution after 8 years. Is there any point in me resubmitting a feature request? Articulate is clearly interested in expanding there xAPI support based on updates made in the last couple of years, this seems like a pretty minor correction in the grander scheme of what's been released.
We already have an open feature request for the ability to disable the default xAPI statements, so I went ahead and added this community post to the report. We'll be sure to leave a message here when we have any new updates to share! For your reference, here's a quick look at how we manage feature requests.
6 Replies
xAPI is designed to provide much finer insights to learner's activities so more numerous outbound statements is expected. Frankly I'm surprised you're seeing two; xAPI can track click/tap activities in fine detail, etc beyond the back/next
If the LRS you are evaluating limits statement capture, I'd strongly suggest looking elsewhere as the commercial grade LRS systems I've leveraged for client projects easily handle thousands of statements without blinking an eye
Hi Reginald!
It sounds like you were looking for more control over the Storyline activity statements that get sent to an LRS. Glad to see that Brian has been helping you out!
Currently, there isn't an option within Storyline to restrict what is sent. However, I did find a related discussion where some users shared a workaround that uses Javascript.
Hope this helps!
Hi Brian,
I am familiar with what can be recorded.
My issue is that it is sending two statements automatically, and they are not purposefully built statements (ones we really want or need recorded). A greater level of control is needed.
My research has shown that most LRS have some upper limit on statements per day on top of a total storage limit. And they offer tiered packages to expand. An on-premise solution is probably not as limited, but is not an option in an early exploratory phase. I'd be open to hearing your recommendations on particular vendors.
I think we are dealing with different volumes. My unit runs 50+ courses (most with 6+ modules, around 60 slides each), with 10-50 learners. So two statements might not be much, but it adds up quick. If added to every course and module, we could possibly hit more than a million total for a semester. On average, I'd say there are three statements we'd want to pull per slide, but if two are added automatically its close to doubling the amount of statements and the cost associated. I am calculating on a single course at first and would easily be more than 10,000 statements.
Thanks Steven,
It is disappointing that there has been no resolution after 8 years. Is there any point in me resubmitting a feature request? Articulate is clearly interested in expanding there xAPI support based on updates made in the last couple of years, this seems like a pretty minor correction in the grander scheme of what's been released.
Hi Reginald,
We already have an open feature request for the ability to disable the default xAPI statements, so I went ahead and added this community post to the report. We'll be sure to leave a message here when we have any new updates to share! For your reference, here's a quick look at how we manage feature requests.
Thank you Jose.