The Experience API (xAPI) allows us to collect data about any type of learning experience or activity, but does that mean we should? Should we generate massive amounts of xAPI data for every possible type of interaction and then expect to make sense of it all later? This approach can be costly in terms of data storage, but also in terms of your time.
As part of the development and introduction of xAPI into a large organisation, it can always be a challenge to provide the benefits. I'd like to share with you how I used xAPI with Articulate Storyline 360, published as SCORM and being delivered via a Learning Management System (LMS). The Learning Record Store (LRS) is Learning Locker.
M. Böhringer, P. Gluchowski, C. Kurze, and C. Schieder. Proceedings of the 31st International Conference on Information Technology Interfaces (ITI), Cavtat/Dubrovnik, Croatia, June 22-25, 2009, page in press. (2009)
B. He, R. Wang, Y. Chen, A. Lelescu, and J. Rhodes. SIGMOD '07: Proceedings of the 2007 ACM SIGMOD international conference on Management of data, page 1041--1052. New York, NY, USA, ACM, (2007)
H. Gupta, V. Harinarayan, A. Rajaraman, and J. Ullman. ICDE '97: Proceedings of the Thirteenth International Conference on Data Engineering, page 208--219. Washington, DC, USA, IEEE Computer Society, (1997)