Project

General

Profile

Feature #6419

Tin Can / Experience API integration

Added by Yannick Warnier almost 6 years ago. Updated almost 6 years ago.

Status:
New
Priority:
Low
Assignee:
-
Category:
Learning paths / Lecciones
Target version:
Start date:
14/07/2013
Due date:
% Done:

0%

Estimated time:
Complexity:
Difficult
SCRUM pts - complexity:
20

Description

References:

The xAPI defines a Learning Record Store (LRS), which works kind of like the skills acquisition: they could be stored in skill_rel_user in chamilo 1.10, with a different kind of skill_id, or the skill_id could be used but the skill table would just store a reference to the xAPI resource...
OR it could be used as a lower-level item like an lp_item_view (with a status). It's between lp_item, lp_item_view and skill, skill_rel_user, really.

Apparently (to be confirmed), to be a LRS, Chamilo should have ways to store statements as defined in https://github.com/adlnet/xAPI-Spec/blob/master/xAPI.md#41-statement-properties (a combination of statement properties), which are like sentences in English (I did this = actor verb object ...).

  • A Statement MUST use each property no more than one time.
  • A Statement MUST use “actor”, “verb”, and “object”.
  • A Statement MAY use its properties in any order.

Apparently, the messaging is done through JSON, so an example of the simplest possible Statement using all properties that MUST or SHOULD be used would look like this:

{
    "id": "12345678-1234-5678-1234-567812345678",
    "actor":{
        "mbox":"mailto:xapi@adlnet.gov" 
    },
    "verb":{
        "id":"http://adlnet.gov/expapi/verbs/created",
        "display":{
            "en-US":"created" 
        }
    },
    "object":{
        "id":"http://example.adlnet.gov/xapi/example/activity" 
    }
}

The specifications also define that what answers the recording calls (i.e. the LRS) must implement specifications like adding an HTTP X-... header and check the version of the xAPI in the incoming calls, etc. See https://github.com/adlnet/xAPI-Spec/blob/master/xAPI.md#62-api-versioning

History

#1

Updated by Yannick Warnier almost 6 years ago

  • Description updated (diff)
#2

Updated by Yannick Warnier almost 6 years ago

Reading a lot more about this, it appears like it really shouldn't be integrated to the learning path, as it covers a wider area.
I would say we develop new tracking tables for this.

Also, there's some use for the conversation in Moodle's forum about this integration: https://tracker.moodle.org/browse/MDL-35433 as they initially thought about integrating it into LP as well, then decided to back off and make something separate which connects to their SCORM module (which seems logical indeed).

The closest item we have in Chamilo at the moment is actually the horizontal timeline in the personal tracking page. I think making it vertical would increase visibility (we could show several items at once).

Also, see the video here: https://www.youtube.com/watch?v=M6ATndrNlI8, it's interesting to get a real technical overview.

Also available in: Atom PDF