International Council for Certified Online Training Professionals: Get certified!

« Adobe Captivate: Object Level Audio Management | Main | TechSmith Camtasia: Exporting Frames »

September 21, 2016


Feed You can follow this conversation by subscribing to the comment feed for this post.

Jessie Chuang

Nice writing!
Letting every learning designer set vocab. as they choose isn't necessarily a good thing, maybe 2 learning designers in a company aren't using the same vocab. for a specific event, not to say all designers in the industry. Also they aren't dataviz designers, so only the most primitive chart with vocab. counts are available for them. Better way could be to import vocab. set according to recipes pre-designed. On the other hand, authoring tool might not handle the "context" data, they must allow designers to set context information such as parent, category etc.
We approach this by designing vocab, recipes, dataviz at the same time, so the dataviz isn't only verb counts or time spent, it has built-in structure mapped with activity structure. And then wrappers are provided for programmers, they don't need to understand xAPI recipes, just fill in blanks with needed data properties. (wrappers: https://wiki.visualcatch.org/en/viscawrapper.html)

The comments to this entry are closed.