Moodle AnalyST
Maintained by
Technische Universität Darmstadt, Steffen Pegenau
Support tool for medium and large sites, that provides you with
- a better search function for courses and users
- a fast overview about a course with participants and their roles, activities, enrolment methods
- a fast overview about a user with their courses and roles
Comments
Comments are no longer open for new posts. Existing comments remain available to read.
this question was already posted on Steffen's Github as an Issue: https://github.com/eLearning-TUDarmstadt/moodle-report_moodleanalyst/issues/78
Sadly, Steffen has left us in March.
We are currently developing a spiritual successor for the moodle analyst here at the TU Darmstadt which is called the Supporter and is referenced in aforementioned Issue. I have created an Issue on the github repo for the Supporter which you can see here:
https://github.com/eLearning-TUDarmstadt/moodle-tool_supporter/issues/35
The Supporter is still under developement and there is not a stable version yet. When it is, we will post it here in the moodle repo.
I have to mention that the supporter is currently not a priority in our team and your wish is an enhanced feature which will only be tackled once the rest is done and final.
Best Regards,
Benedikt Schneider
Is there a file i can update to include extra fields?
Thanks
Hi Steffen. Good to hear from you again. It's been a while since I saw this plugin last time and I see some good progress here. Same as last time, I understand your plugin uses a lot of techniques not common in Moodle development world. I like it as kind of experiment that shows alternative ways to contribute to Moodle. But it also makes it harder to review and judge all impacts of these techniques.
One particular thing I spotted is that it seems you only require your report's capability
report/moodleanalyst:viewto use the plugin. But it seems to me that you display details about users and courses that go beyond the scope of thecoursereport/log:viewthat you clone permissions from (by the way, your db/access.php definesclonepermissionsfromtwice by mistake and is confusing to read. I believe your report should be available to site admins only and all the REST calls should simply fail for all non-admins.For now, I am going to publish the plugin in the "incubating" state to give you a chance to gather feedback from wider community.
http://integration.moodle.org/job/Precheck%20remote%20branch/24295/artifact/work/smurf.html
Hi Steffen. Thanks for sharing this plugin with the community. The plugin definitely aims to become a useful admin tool (btw, as such, you may consider to refactor it into a plugin of type
toolrather thanreport). However, it can't be approved in this Plugins directory yet.There were some issues spotted while reviewing the code, and I reported them into your tracker. The licensing issue is a real approval blocker for now and should be sorted out. The problems with
$CFG->wwwrootbeing ignored are serious, too.Also note, I had multiple issues while trying to use all the features of the plugin, and even spotted some TODOs in the UI (e.g. in the
html/newusers.tpl.html). Some features did not simply work or did not show anything to me.I am sure this will be a useful and popular tool for many admins. But it would be good to promote it via our community channels first (e.g. on a moodle.org forum, twitter etc) and get some feedback from wider range of users to catch the most obvious bugs, prior to submitting it here.
For now, I am going to mark this as needing more work.
http://integration.moodle.org/job/Precheck%20remote%20branch/12655/artifact/work/smurf.html