Verification of how Tin Can API integrates

Hi All!

I'm doing a Storyline product evaluation for my company and whereas our 3rd-party LMS doesn't have Tin Can API features built-in, can I verify the following regarding Storyline courses themselves actually reporting a course's activity to an external LRS:

Can you please verify the following:

  1. Where the Url to a course launch-page is http://MyLMSServer.com/pathtomycoursefolder/Story_html5.html, and,
  2. The Url to my LRS reporting service is http://MyLRSServer.com/ReportingEndpoint/

then for the Storyline's embedded JavaScript to automatically report the course result using Tin Can API to my LRS, all I have to do is launch the course using the following link (which is not url-escaped here for for readability but would normally be url-escaped):

http://MyLMSServer.com/pathtomycoursefolder/Story_html5.html

?endpoint=http://MyLRSServer.com/ReportingEndpoint/

&auth=OjFjMGY4NTYxNzUwOGI4YWY0NjFkNzU5MWUxMzE1ZGQ1

&actor={"name": ["First Last"], "mbox": ["mailto:firstlast@mycompany.com"]}

&activity_id=61XkSYC1ht2_course_id

&registration=760e3480-ba55-4991-94b0-01820dbd23a2

 

Although this is more or less a cut-and-paste from Articulate's own link (http://www.articulate.com/tincanapi/) I just want to verify that if I initiate a course using a link like that, that the Storyline course will automatically pass results via PUT to http://MyLRSServer.com/ReportingEndpoint/

 

Additionally, could you please identify what the registration component of the querystring is.

 

i.e is it generated:

  1. by Storyline
  2. as our own separately created registration number and hence is merely included in the PUT request but has no dependency on Storyline itself
  3. Other

That is, what is the difference between activity_id and registration.

Thanks very much!

Kind regards,

Anthony

Be the first to reply