Note: You are currently viewing documentation for Moodle 3.8. Up-to-date documentation for the latest stable version of Moodle may be available here: Managing analytics.

Managing analytics

From MoodleDocs
Revision as of 22:59, 24 June 2019 by Elizabeth Dalton (talk | contribs) (fix navigation, intro)

Once models have been selected, enabled and trained (see Using analytics), they will start to generate predictions.

Predictions and Insights

Models will start generating predictions at different points in time, depending on the site prediction models and the site courses start and end dates.

Each model defines which predictions will generate insights and which predictions will be ignored. For example, the Students at risk of dropping out prediction model does not generate an insight if a student is predicted as "not at risk," since the primary interest is which students are at risk of dropping out of courses, not which students are not at risk.

prediction-model-insights.jpeg

Users can specify how they wish to receive insights notifications, or turn them off, via their User menu > Preferences > Notification preferences.

Actions

Each insight can have one or more actions defined. Actions provide a way to act on the insight as it is read. These actions may include a way to send a message to another user, a link to a report providing information about the sample the prediction has been generated for (e.g. a report for an existing student), or a way to view the details of the model prediction.

Insights and Actions

Insights can also offer two important general actions that are applicable to all insights. First, the user can acknowledge the insight. This removes that particular prediction from the view of the user, e.g. a notification about a particular student at risk is removed from the display.

The second general action is to mark the insight as "Not useful." This also removes the insight associated with this calculation from the display, but the model is adjusted to make this prediction less likely in the future.

Monitoring model quality

Check the log reports regularly to review the accuracy of your models.