Completion tracking of single module in LMS

Hi Lon!

I would like some clarity on why you would rather track the viewed pages of one .story file over four separate .story files. By splitting them into four separate files you have more control over which viewed pages to track.

Would you feel comfortable with sharing your .story file or possibly a screenshot of your publishing settings (LMS > Tracking) to help us troubleshoot this?

Thanks for reaching out!

Hi John,

Thanks for your reply. I will try to clarify. I prefer to develop a whole course in one .story file to assure consistency in all the settings and share resources. It seems overall more efficient. But we are publishing to Moodle, and the client wants all quizzes and tracking done in the Moodle. And they want each module quiz to only be available after the learner has gone through the module. So, each module is published as a .story file and set up on the Moodle. 

See attachments... when I go to publish for LMS, I have chosen to publish just Module 1 slides. So, since I am publishing just Module 1, it seems logical to me that the tracking options would default to just tracking completion of the slides in that module. But instead, we see that the learner must view 57 slides (or 41 if we just count those in the menu...of the full course) which is all of the slides in the full course. There is no option to choose to track only the slides in Module 1. And of course, if I publish just one module like this, completion will never be achieved because most of the 57 slides it is looking for completion on, are not in the published output. 

This sentence is key: "By splitting them into four separate files you have more control over which viewed pages to track." Yes, currently because of this limitation in tracking settings in the publication process, the ONLY way to have the ability to control which viewed pages are tracked (when publishing a subset of slides in the course) is to split up the files. This is an unnecessary step otherwise. I now have to create these separate .story files just to publish, then delete them, since I want to manage the course as a whole in one .story file. 

Does that make sense? Do you see why I'd want to track the viewed pages of one module, when publishing only that module? 

Thanks,

Lon 

Hello Lon, 

Thanks for the detailed explanation of your requirement. Unfortunately, the tracking option 'When the learner has viewed X number of slides' only applies to the entire project. Having the ability to track slide progress per scene sounds like a greater feature to have, and I’ll be happy to pass your thoughts on to our product team, but you can also feel free to detail them more through a feature request! 

One alternative method to tracking completion that you can consider is to track using triggers instead of the number of slides viewed. By having a 'Complete Course' trigger at the end of each of your modules, you can set your course up so that each scene will have the capability to send a completion status to your LMS. Here's a helpful article for your reference:

• Storyline 360: How to Use a Trigger to Send a Completion Status to Your LMS

Let me know if this works for you!

Hello Joe,

Thanks for this suggestion for another work-around to this problem. I am not seeing a simple trigger for having viewed a set of slides (as is the option when choosing tracking method for publishing to an LMS. Would I have to set a trigger for every slide in a module, and keep track of those with a variable? 

If that is what is required, I think splitting up the file before publishing is probably a simpler work-around. 

To me it seems intuitive that if you are publishing one module, you would want to set the tracking to account for just that module. So, in that sense this seems like a bug, or perhaps an incompletely implemented feature. 

I will try to submit a feature request.

Thanks for the help.

Lon 

Hi Joe and Lon, I just wanted to chime in. I found myself in the exact same situation as Lon. I inherited someone else's project and he set it up the same way. One big file that is published as separate modules in the LMS. Frankly, this is the way I would prefer to do it. Like Lon said, there are way more efficiencies when it is one big file. I agree with Lon. It seems more like a defect to offer the ability to publish a scene, but then not give the ability to track by scene. In the meantime, I'll have to split up the file too. Lon did you put in a request? I'll upvote it.

perhaps you could use the storyline feature "Exclude Slides" from tracking

https://community.articulate.com/discussions/articulate-storyline/tracking-options-i-have-an-optional-help-button-on-my-current-project-not-all-learners-will-need-help-how-do-i-set-the-tracking-up-for-it#reply-848694

mark only slides of scene 1 -> publish scene 1

mark only slides of scene 2 -> publish scene 2

...