One of my objectives for Learning Solutions was to make more sense of how xAPI (fondly known as Tin Can) might work in my Learning Ecosystem.
Thus far – much of the implementation of xAPI has been around “SCORM replacement.”
Makes sense – a step in the process of technology adoption is to make the technology do something familiar. Unfortunately, most technology adoption stops there.
It is promising that ADL (Advanced Distributed Learning – the SCORM folks) and AICC (Aviation Industry Computer-Based-Training Committee) are working together to align the two main APIs used in our industry.
In an ideal world, there would be one standard that does everything we need it to do.
If I really start hallucinating – I’d love to see one standard across all applications and industries (you know – like the “universal” phone chargers we now have the luxury of using).
Ease of integration of data sources?
That could be very powerful – especially once we figure out what the heck we are looking for in the data.
I am still attracted to the simplicity of the data stream in the xAPI spec.
subject / verb / direct object.
I will admit I am still not entirely certain what it all means.
While daydreaming in Texas – I wondered….
What if I could have my content providers just dump an xAPI-wrapped tutorial anywhere in our network?
The Learning Record Store (or whatever data collection mechanism we use) can see whether the item is xAPI, pull the information, then collect it with the other stuff such as web analytics etc.
Maybe a tack-on to Google Analytics for our pages?
Just something where the end-user doesn’t have to report into the system themselves if they are accessing information housed in our corporate environment.
Maybe a wrapper-identifier – like we now have with a lot of web pages that can tell whether a user is accessing their site via desktop, tablet or mobile and adapts the site to fit?
Then I might be able to see what information folks are accessing, scores (if applicable), if there are any trends (particular departments? job types?), whether there are any changes in our business analytics as a result of this information, whether accessing the information is causing a jump in help desk calls….
One, cohesive, easy to parse package.
Yeah – that would be really cool.
There are learning record stores and snippets of code available.
Implementation, however, is not super-friendly…. yet.
I’m still trying to figure out where a learning record store (LRS) would fit in my little learning ecosystem.
Current thinking is that an LRS would be a layer between the learning content objects.
- The information from all of the defined learning objects goes to the LRS.
- Standard L&D reporting (access, completion, scores etc) get accessed through the LRS.
- LRS information gets dumped into our Business Intelligence systems.
- Reports on business impact of training and support that requires information from multiple enterprise systems get pulled from the business reporting tools.
Of course, this idea could get blown out of the water.
I’d rather have it blown up now while it is still a daydream.