Details
-
Improvement
-
Status: Closed
-
Critical
-
Resolution: Fixed
-
3.4.1, 3.7
-
MOODLE_34_STABLE, MOODLE_37_STABLE
-
MOODLE_37_STABLE
-
MDL-61667-master-modelsinstall -
Description
Hey David,
we just tried your Analytics API in a spontaneous DevCamp on the MoodleMootDE 2018 and completed a first small prototype for a new built-in model. First, thanks for your amazing work there.
In the progress of the DevCamp, I stumbled over the way, plugins need to install built-in models within a plugin. As also done within your moodle-tool_testanalytics, you need to specify the installation as documented at MoodleDocs within db/install.php. However, this is not the way other APIs define built-in stuff. Examples that came to my mind are the tasks API, where you specify an array within db/tasks.php or the services API with db/services.php, respectively.
I would suggest adding an additional db file such as db/models.php or db/analytics.php for an easy definition of built-in models. The core analytics plugin would have to parse this file and would care about the installation, update and removal of built-in models.
I have not fought about concrete implementation details yet and first wanted to hear, what you think about this idea.
Cheers,
Tobias
Attachments
Issue Links
- blocks
-
MDL-64777 Allow default models to be restored
-
- Closed
-
-
MDL-64783 Create a new model for upcoming activities due
-
- Closed
-
- has been marked as being related by
-
MDL-65186 Final deprecation of \core_analytics\manager::add_builtin_models()
-
- Closed
-
- will be (partly) resolved by
-
MDL-61806 Implement UI for creating and editing learning analytics models based on reports
-
- Closed
-