Setting Activity Ids in Tin Can

Sep 04, 2013

Dean Kimball
By Dean Kimball

Hello,

I recently implemented Articulate Storyline, Wordpress, LearnDash, and Grassblade.

The open source adl lrs was not out of beta yet and only available for Ubuntu. Which I am on RHEL. So, I ended up writing my own tincan LRS endpoint. I could not find any other open source LRS systems to implement in a private environment.

I love it all, works great, have about 10,000 active users pounding it daily with well over 100 modules in to different brands.

The one thing I am sticking on now is the auto generated mangled Activity Ids that storyline creates for you. For the most part I can get by using grouping ids  and types = course to get some meaningful reporting for the end users.

But, what I have not seen is a way to set the activity ids in storyline, and from what I have read on here you cannot effectively change the activity ids in the tincan.xml and have the published content pick them up. Haven't tested that myself yet.

So, my question is, is there a way to set these activity ids to something other than mangled descriptors? And if you can't it would sure be a really nice feature of the articulate guys! Hint.. Hint...

Also, props to Pankaj Agrawal who you will see on this forum and his product GrassBlade. Very nice product and great support!

Dean

5 Replies
Ashley Terwilliger-Pollard
over 10 years ago09/05/13 at 8:58 am (UTC)

Hi Dean and welcome to Heroes! 

It certainly looks like you've done your research into this! I don't know of any ways to edit the ids, but possibly someone in the community will be able to assist you here. 

In the meantime, I did want to point you to the page where you can submit feature requests so that you could share your thoughts with our Development team. If you need anything else just let us know! 

Steve Flowers
over 10 years ago09/05/13 at 9:16 am (UTC)

Hey Dean,

Super interested in hearing more about your implementation. The mangled ID's, i believe, are due to Storyline aligning with version .95 of the spec and not 1.0. I'm hoping to see movement in compatibility with 1.0 as I'm seeing folks indicate non-conformance with the release version is causing problems.

Steve

Dean Kimball
over 10 years ago09/05/13 at 4:26 pm (UTC)

Sure, let me know what you would like to hear. We can post here or go offline.

I am sure being just about the only authoring tool supporting xAPI without a lot of other standards compliance endpoints leaves lots of room for interpretation and getting it out the door.

I look forward to the future though, as it is a really great protocol over scorm.

Dean

This discussion is closed. You can start a new discussion or contact Articulate Support.