Some authoring tools like Articulate so far don’t send important human-readable details in the statements like Course Name, Question Text, Answer Text, Slide Name, etc.
This renders the reports on LRS unreadable. GrassBlade LRS provides a solution for this issue. Here is what you need to do:
Load from tincan.xml URL
If you have uploaded the tincan.xml file and have the URL. You can load it directly.
In each xAPI pacakge, there is a file present called tincan.xml. When you upload your xAPI (tincan) package from any authoring tool like Storyline or Rise 360. It gets uploaded to your WordPress server. Or wherever you host your package.
Create a tincan.xml URL
- In WordPress Dashboard, Go to the xAPI Content edit page.
- Scroll to the xAPI Content Details section.
- Copy the Content URL
- Replace story.html or lms_index.html or index.html with tincan.xml in the URL.
Content URL: https://example.com/wp-content/uploads/grassblade/123-xapi-package-name/index.html
tincan.xml URL: https://example.com/wp-content/uploads/grassblade/123-xapi-package-name/tincan.xml
If your content is hosted or uploaded somewhere else, please use the same kind of URL that ends with tincan.xml
Go to GrassBlade LRS > Configuration > Translations
Copy the URL tincan.xml file URL and paste it into the input box near the load button.
Click on the “Load” button to load the tincan.xml file(s)
Load from GrassBlade
If you have uploaded your content to WordPress using GrassBlade xAPI Companion, and if the LRS is installed on the same database, you can use this button to import all tincan.xml files at once.
Loading the tincan.xml files here means that the translations will be stored in the database, and the reports will show the human-readable text instead of IDs.
If you’re facing issues while using this feature feel free to contact us.