Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ADL_LRS .9 #261

Closed
lexwraith opened this issue Jan 13, 2014 · 9 comments
Closed

ADL_LRS .9 #261

lexwraith opened this issue Jan 13, 2014 · 9 comments

Comments

@lexwraith
Copy link

I think it's not supported anymore, but I've downloaded and set up the version .9 to be compatible with Articulate Storyline.

During the "test_lrs" phase of the setup, I am denied access to:

tincanapi.com/wp-content/assets/tincan.xsd

Yet, I can go to that site via web browser and get the required XML. Any ideas how I can get this to work on the fab test_lrs?

@ljwolford
Copy link
Contributor

Make sure the LRS has been started (python manage.py runserver is the command if you're not running it on supervisor). We would really encourage you to use the 1.0 branch (if possible) since the .90 and ,95 tags probably have some glaring issues with them and aren't supported by us anymore.

@lexwraith
Copy link
Author

Unfortunately, that's not an option - I need an LRS that's compatible with Articulate Storyline until they update to Tin Can 1.0. What kind of glaring issues? I might have to fork and build off of it (haha, that's going to hurt, isn't it?).

@ljwolford
Copy link
Contributor

Yeah I'm not sure what kind of bugs you'll run into, but while we were developing there was no community traction yet to test it out and no time to go back and fix bugs that were caught on newer iterations. If you do come across any issues then yes you'll have to fork and fix it haha.

@garemoko
Copy link

You might be better off seeing if you can fix the storyline packages. That has the advantage of future proofing both your LRS and data. 

Sent from Samsung Mobile

-------- Original message --------
From: Michael notifications@github.com
Date: 13/01/2014 16:20 (GMT+00:00)
To: adlnet/ADL_LRS ADL_LRS@noreply.github.com
Subject: Re: [ADL_LRS] ADL_LRS .9 (#261)

Unfortunately, that's not an option - I need an LRS that's compatible with Articulate Storyline until they update to Tin Can 1.0. What kind of glaring issues? I might have to fork and build off of it (haha, that's going to hurt, isn't it?).


Reply to this email directly or view it on GitHub.

@lexwraith
Copy link
Author

How could we fix the storyline packages? Any reading material recommended? I don't see huge differences between .9 and 1.0, but can't pin out the technical differences I would need to change to make it forward compatible.

@ljwolford
Copy link
Contributor

For the technical differences to make it compatible, here's a section in the xapi spec that describes the statement transformation needed: https://github.com/adlnet/xAPI-Spec/blob/master/xAPI.md#AppendixD

I hope this helps you out a bit!

@lexwraith
Copy link
Author

It does. Thanks a lot gents!

@garemoko
Copy link

If you are able to convert the packages, I'd be very interested to hear the process :-) 

Sent from Samsung Mobile

-------- Original message --------
From: Michael notifications@github.com
Date: 13/01/2014 20:29 (GMT+00:00)
To: adlnet/ADL_LRS ADL_LRS@noreply.github.com
Cc: Andrew Downes mrdownes@hotmail.com
Subject: Re: [ADL_LRS] ADL_LRS .9 (#261)

It does. Thanks a lot gents!


Reply to this email directly or view it on GitHub.

@fugu13
Copy link

fugu13 commented Jan 13, 2014

We don't do that form of conversion (we update statements to include activity names and such), but if you run a storyline package through our converter you can see how to hook into the xAPI sending mechanism for flash and html5 output: http://converter.saltbox.com/ We're working on hooking into the xAPI sending mechanism for iPad, too, but don't have that yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants