Forum Discussion
LRS xAPI Data POST
- 2 months ago
Thank you JoseTansengco ! We were able to figure out the issue. Articulate isn't using a POST here, it's using a PUT. This wasn't added to the allowable OPTIONS, once we change that it works as expected.
JoseTansengcoTwo question for you. For Rise, it doesn't look like we can put the LRS connection details in the Rise presentation at Export time. How would we add the LRS connection details to the Rise presentation when exporting it in xAPI?
The details that come back in Storyline lack the Canvas course id or other details that will help us make use of the data in the database. Do you know if we can adjust the items that come back in the Storyline and Rise LRS items?
Hi ryanHepler!
Happy to jump in here!
Allow me to address each of your questions individually:
- That behavior is expected, as currently there isn't a way to add xAPI statements in Rise 360. However, we are tracking a feature request to extend xAPI reporting options when publishing from Rise. I'll include your voice in the request!
- To access reporting data from a Storyline course within Canvas LMS, the author must first publish the Storyline course to the recommended SCORM standard, and ensure the 'Course Identifier' field (Canvas course ID) is accurately populated in the publishing settings. This will allow the LMS to track learner progress and display relevant data within the reporting interface.
Also, do you mind clarifying what you meant by 'Storyline lacks the Canvas course ID'? Is the expectation to have the published course pick up the LMS-created ID for the course? If so, that is not possible as that type of communication/data is local to the 3rd party LMS being used, and not part of the Storyline specifications. However, if I misunderstood, please let me know!
Looking forward to hearing from you!