Analytics View for Raw Student Input

[andrew-pyle]

Is your feature request related to a problem? Please describe. I would like to have Lumi Analytics to provide analysis options for reviewing student-generated essays. The Lumi Analytics view for the Essay or Questionnaire H5P content types do not allow an instructor to read the long-form content generated by students. The data seems to be present in the .lumi JSON file, however.

Currently, importing the Questionnaire H5P content type to Lumi Analytics results in a "broken student interactions" error.

Describe the solution you'd like Can the Lumi Analytics view show the student essays? Or could the Analytics view provide a downloadable format?

Describe alternatives you've considered I understand that the idea of a "score" is foundational to the Analytics view, so maybe this would be a drastic change. I suppose I could parse the .lumi file directly to obtain the student essay data.

[sr258]

Hi Andrew,

I'm afraid this is currently only possible by digging into the JSON data. I absolutely see the need for more fine-grained reporting, but the Analytics view is not used much and that's why I currently don't put much time into it. It's quite possible that better analytics and reporting will be a side-product of commercial contract work, though, as this is something that is really needed in many learning settings. It's hard to say when this will become reality, though.

[andrew-pyle]

@sr258 Your explanation makes sense. I am considering digging into the JSON for a reporting feature myself. What kind of work, if I did it myself, be beneficial to contribute back? How would something need to be structured to be helpful to the project?

My potential project has its own priorities, but all other things equal, I'd like to contribute to the project directly, rather than creating a standalone JSON processing tool.

[sr258]

@andrew-pyle The best way would be if you continued the work on https://github.com/Lumieducation/Lumi-xAPI This is where we put the xAPI parsing functionality in the past. We wanted to discontinue this extra package and integrate everything into Lumi, as it turns out it didn't make too much sense to put things into too many different NPM packages. In light of recent developments, it might make sense to have the xAPI package after all, as we could put reporting functionality it other products than just Lumi.

It would make most sense to have generic xAPI parsing functionality (identify subcontent results etc.) and display functionality that displays xAPI statements in human-readable form. It would be best for us if these components were created in React, so that we can put them into Lumi without hassle.