Swik 1958 student performance prediction prototype

[dpaun]

This is a prototype for the student performance prediction module. The functionality can be checked on the user settings page.
Related: deliverable D3.1 SlideWiki learning analytics

[kprist]

Having merged #1034, and with https://github.com/slidewiki/analytics-service running on experimental, I was able to use the new "Analytics" menu under user settings page, and get an analysis result:

I'm not sure it's clear to users what this does, so please @dpaun could you clarify ? It seems you might need some more features merged ? Current flow is, I add a prediction job, select a deck, and get a number. For this deck, I've completed the exam mode. For some other deck I get this:

As @dpaun explained, for decks that we have no completed exams (for the current user?), the analytics-service uses some sample data, but I'm not sure how those relate to the selected deck.

This branch appears to also add an entry in the user menu, "Analytics", for which I did some minor tweaks. I've fixed some issues with the beta label in the UI, and with the "New prediction job" button to be more consistent. This feature is quite disconnected from the rest of the platform UI, so I don't expect any issues with breaking things elsewhere.

@abijames you can check the UI for this, but I guess @dpaun should help with a listing for the UIs to check, and the flows related, not sure if I got them all.

Finally, in order to get this to production, the analytics service needs to be deployed, i.e. @bwulff has to merge slidewiki/slidewiki-deployment#19 and deploy on testing.

[abijames]

I have tried to run the branch locally but I can't see this feature. As it is marked beta I am less concerned about the UI for now as we can make small changes after the release.

[abijames]

Please do not merge into end-October release. It has been agreed this needs further work so will be a late addition / experimental feature, particularly as we need data in the system to get it to work effectively.

[dpaun]

@kprist , @kadevgraaf , @abijames ,
Since the reviewers might read about this functionality in the deliverable D3.1 and not be able to find it on the platform, I was wondering should we merge this soon (to experimental only, of course)?
As Kostis said earlier, this feature is quite disconnected from the rest of the platform UI, so we don't expect any issues with breaking things elsewhere.

[abijames]

@kprist , @kadevgraaf , @abijames , @dpaun
I have one branch I would like to merge and possibly get on to the live version. I hope to look at that tomorrow. Then i would be fine with experimental features going live.

[kprist]

@bwulff what is the current process for last minute deployments to production versus in experimental? there are some additional stuff I too would like to have on experimental but not on production. I was hoping I could make them on testing but that's out of the picture.

Could you create a release branch r.12.x or something for the production release and merge / tag stuff there as we did previously? I don't see such release branches lately so I assume you tag on master ?