https://docs.moodle.org/30/en/api.php?action=feedcontributions&user=Deraadt&feedformat=atomMoodleDocs - User contributions [en]2024-03-29T12:39:53ZUser contributionsMediaWiki 1.39.6https://docs.moodle.org/30/en/index.php?title=Learning_analytics&diff=122829Learning analytics2016-04-06T07:32:51Z<p>Deraadt: /* Moodle Plugins */</p>
<hr />
<div>Learning Analytics are any piece of information that can help an LMS user improve learning outcomes. Users include students, teachers, administrators and decision-makers.<br />
<br />
== Moodle Plugins ==<br />
<br />
There are a number of reports, blocks and other plugins for Moodle that provide learning analytics.<br />
<br />
{| class="nicetable"<br />
|-<br />
! Plugin <br />
! Plugin type<br />
! Standard / Additional<br />
! Useful for<br />
! Description<br />
! Reported usage*<br />
|-<br />
| [[:en:Logs|Logs]]<br />
| Report<br />
| Standard<br />
| Teachers, Admins, Decision-makers<br />
| Filterable log of events<br />
| style="text-align:center;" | 71.4%<br />
|-<br />
| [[:en:Activity_report|Activity]]<br />
| Report<br />
| Standard<br />
| Teachers<br />
| View count of activities in course<br />
| style="text-align:center;" | 69.1%<br />
|-<br />
| [[:en:Using_Activity_completion|Activity completion]], see also [[:en:Using_Course_completion|Course completion]]<br />
| Report<br />
| Standard<br />
| Teachers<br />
| Completion matrix of students and activities<br />
| style="text-align:center;" | 66.3%<br />
|-<br />
| [[:en:Logs|Live logs]]<br />
| Report<br />
| Standard<br />
| Teachers, Admins<br />
| Automatically refreshing log of events<br />
| style="text-align:center;" | 55.2% <br />
|-<br />
| [[:en:Feedback_activity|Feedback]]<br />
| Activity<br />
| Standard<br />
| Teachers, Researchers<br />
| Configurable survey tool<br />
| style="text-align:center;" | 59.5% <br />
|-<br />
| [[:en:Quiz_statistics_report|(Quiz) Statistics]]<br />
| Report<br />
| Standard<br />
| Teachers<br />
| Student quiz performance report<br />
| style="text-align:center;" | 53.0%<br />
|-<br />
| [[:en:Participation_report|(Course) Participation]]<br />
| Report<br />
| Standard<br />
| Teachers<br />
| Single student's participation in course<br />
| style="text-align:center;" | 49.9%<br />
|-<br />
| [[:en:Survey_module|Survey]]<br />
| Activity<br />
| Standard<br />
| Teachers, Researchers<br />
| Set of standardised educational surveys<br />
| style="text-align:center;" | 45.6%<br />
|-<br />
| [http://moodle.org/plugins/view.php?plugin=mod_questionnaire Questionnaire]<br />
| Activity<br />
| Additional<br />
| Teachers, Researchers<br />
| Configurable survey tool<br />
| style="text-align:center;" | 45.3%<br />
|-<br />
| [[:en:Course_overview_report|Course overview]]<br />
| Report<br />
| Standard<br />
| Admins, Decision-makers<br />
| Comparison of participation across multiple courses<br />
| style="text-align:center;" | 45.0%<br />
|-<br />
| [[:en:Course_completion_status_block|Course completion status]]<br />
| Block<br />
| Standard<br />
| Students<br />
| View of student's own completion of activities<br />
| style="text-align:center;" | 41.4%<br />
|-<br />
| [http://moodle.org/plugins/view.php?plugin=block_progress Progress Bar]<br />
| Block<br />
| Additional<br />
| Students, Teachers<br />
| Time management tool for students with overview for teachers<br />
| style="text-align:center;" | 32.0%<br />
|-<br />
| [[:en:Events_list_report|Events list]]<br />
| Report<br />
| Standard<br />
| Teachers, Admins<br />
| Events that can be monitored/searched in logs<br />
| style="text-align:center;" | 28.6%<br />
|-<br />
| [[:en:Activity_results_block|Activity results block]]<br />
| Block<br />
| Standard<br />
| Students<br />
| Leader-board of results in single activity<br />
| style="text-align:center;" | 26.1%<br />
|-<br />
| [http://moodle.org/plugins/view.php?id=82 Configurable Reports] <br />
([https://docs.moodle.org/29/en/ad-hoc_contributed_reports A list of contributed reports])<br />
| Block ([https://github.com/nadavkav/moodle-report_configurablereports Report] [https://github.com/nadavkav/moodle-filter_crgraph Graphs filter])<br />
| Additional<br />
| Teachers, Admins, Decision-makers<br />
| Report generation and viewing<br />
| style="text-align:center;" | 22.7%<br />
|-<br />
| [[Overview_report|(Gradebook) Overview]]<br />
| Report<br />
| Standard<br />
| Teachers, Students<br />
| View of student grades across activites<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [[Statistics]]<br />
| Report<br />
| Standard<br />
| Admins, Decision-makers<br />
| Daily activity across site<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [[:en:Event_monitoring|Event monitor]]<br />
| Report<br />
| Standard<br />
| Teachers, Admins, Decision-makers<br />
| Proactive, focussed monitor tool<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/view/report_customsql Ad-hoc database queries]<br />
| Report<br />
| Additional<br />
| Teachers, Admins, Decision-makers<br />
| SQL-based report generation and viewing<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/browse.php?list=set&id=20 Engagement Analytics]<br />
| Block, Report, Activity module<br />
| Additional<br />
| Teachers<br />
| Configurable engagement measurement report and block<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/view/block_dedication Course Dedication]<br />
| Block<br />
| Additional<br />
| Students, Teachers<br />
| Estimated time online for students<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/view.php?plugin=block_graph_stats Graph Stats]<br />
| Block<br />
| Additional<br />
| Teachers, Admins<br />
| Daily visits to site or course<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/view/block_gismo GISMO]<br />
| Block<br />
| Additional<br />
| Teachers<br />
| Numerous charts of student activity participation<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/view/block_xp Level Up!]<br />
| Block<br />
| Additional<br />
| Students, Teachers<br />
| Incentive-drive participation meter<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/report_forumgraph Forum Graph]<br />
| Report<br />
| Additional<br />
| Teachers<br />
| Graph of forum interactions<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [https://moodle.org/plugins/block_analytics_graphs Analytics Graphs]<br />
| Block<br />
| Additional<br />
| Teachers<br />
| Visualisation of student participation<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [https://moodle.org/plugins/block_heatmap Heatmap]<br />
| Block<br />
| Additional<br />
| Teachers<br />
| Colour-coded indication of activity views on course page<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [https://moodle.org/plugins/local_analytics Analytics]<br />
| Local<br />
| Additional<br />
| Admins, Decision-makers<br />
| Enriched feed to Google Analytics and Pywick<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [https://moodle.org/plugins/logstore_xapi Logstore xAPI]<br />
| Logstore<br />
| Additional<br />
| Admins, Decision-makers, Researchers<br />
| xAPI event stream output<br />
| style="text-align:center;" | N/A<br />
|}<br />
<br />
<nowiki>*</nowiki> Reported usage is drawn from the [http://research.moodle.net/71/1/Plugins%20Usage%20Survey%202015%20Report.pdf Plugins Usage Survey from 2015].<br />
<br />
== Integrations with Moodle ==<br />
<br />
A number of systems integrate with Moodle to provide learning analytics information externally.<br />
<br />
* [http://damos.world/2013/08/30/the-moodle-activity-viewer-mav-heatmaps-of-student-activity/ Moodle Activity Viewer] (MAV) ([https://github.com/damoclark/mav-enterprise Git]), consider [https://moodle.org/plugins/block_heatmap Heatmap] as an alternative<br />
* [http://www.intelliboard.net/ Intelliboard]<br />
* [http://www.lambdasolutions.net/products/lmsreporting/ Analytika]<br />
* [https://learninglocker.net/ Learning Locker], can be used with [https://moodle.org/plugins/logstore_xapi Logstore xAPI]<br />
* [http://klassdata.com/smartklass-learning-analytics-plugin/learning-analytics-moodle-smartklass/ SmartKlass]<br />
<br />
== Dimensions of Analytics ==<br />
<br />
Learning analytics are a concept that has been emerging under a number of different names through the past decades. Its origins lie in research in data mining and intelligent tutoring systems. LA tools can be categorised in a number of ways. The diagram below describes such tools by how deeply they are integrated with other systems ([http://www.netdimensions.com/downloads-2015/others/lms-evolution-or-extinction.pdf?mkt_tok=3RkMMJWWfF9wsRokuKjMZKXonjHpfsX56OQtW6CwlMI%2F0ER3fOvrPUfGjI4DTsdlI%2BSLDwEYGJlv6SgFS7fAMaFl3bgIWBY%3D source]).<br />
<br />
[[File:Learning-analytics.png]]<br />
<br />
== See also... ==<br />
* [https://moodle.org/mod/forum/view.php?id=8044 Analytics and reporting forum]<br />
* [https://moodle.org/mod/forum/view.php?id=8205 Moodle Research forum]<br />
* [[:dev:Moodle_research|Moodle research page]]<br />
* [[Logging]]<br />
* [[:en:Events_list_report|Events list]]<br />
* [[:dev:Learning_Analytics_Specification|Learning Analytics API specification]]<br />
* [[:dev:Working_Groups#Assessment_Analytics|Assessment Analytics working group details and issues]]<br />
* [[:dev:Event_2|Events specification]]<br />
* [[:dev:Logging_2|Logging specification]]<br />
* [[:dev:reportbuilder/API|Report Builder API specification]]<br />
<br />
[[Category:Report]]<br />
<br />
[[es:Análisis del aprendizaje]]</div>Deraadthttps://docs.moodle.org/30/en/index.php?title=Learning_analytics&diff=122828Learning analytics2016-04-06T07:31:24Z<p>Deraadt: Adding descriptions to plugins</p>
<hr />
<div>Learning Analytics are any piece of information that can help an LMS user improve learning outcomes. Users include students, teachers, administrators and decision-makers.<br />
<br />
== Moodle Plugins ==<br />
<br />
There are a number of reports, blocks and other plugins for Moodle that provide learning analytics.<br />
<br />
{| class="nicetable"<br />
|-<br />
! Plugin <br />
! Plugin type<br />
! Standard / Additional<br />
! Useful for<br />
! Description<br />
! Reported usage*<br />
|-<br />
| [[:en:Logs|Logs]]<br />
| Report<br />
| Standard<br />
| Teachers, Admins, Decision-makers<br />
| Filterable log of events<br />
| style="text-align:center;" | 71.4%<br />
|-<br />
| [[:en:Activity_report|Activity]]<br />
| Report<br />
| Standard<br />
| Teachers<br />
| View count of activities in course<br />
| style="text-align:center;" | 69.1%<br />
|-<br />
| [[:en:Using_Activity_completion|Activity completion]], see also [[:en:Using_Course_completion|Course completion]]<br />
| Report<br />
| Standard<br />
| Teachers<br />
| Completion matrix of students and activities<br />
| style="text-align:center;" | 66.3%<br />
|-<br />
| [[:en:Logs|Live logs]]<br />
| Report<br />
| Standard<br />
| Teachers, Admins<br />
| Automatically refreshing log of events<br />
| style="text-align:center;" | 55.2% <br />
|-<br />
| [[:en:Feedback_activity|Feedback]]<br />
| Activity<br />
| Standard<br />
| Teachers, Researchers<br />
| Configurable survey tool<br />
| style="text-align:center;" | 59.5% <br />
|-<br />
| [[:en:Quiz_statistics_report|(Quiz) Statistics]]<br />
| Report<br />
| Standard<br />
| Teachers<br />
| Student quiz performance report<br />
| style="text-align:center;" | 53.0%<br />
|-<br />
| [[:en:Participation_report|(Course) Participation]]<br />
| Report<br />
| Standard<br />
| Teachers<br />
| Single student's participation in course<br />
| style="text-align:center;" | 49.9%<br />
|-<br />
| [[:en:Survey_module|Survey]]<br />
| Activity<br />
| Standard<br />
| Teachers, Researchers<br />
| Set of standardised educational surveys<br />
| style="text-align:center;" | 45.6%<br />
|-<br />
| [http://moodle.org/plugins/view.php?plugin=mod_questionnaire Questionnaire]<br />
| Activity<br />
| Additional<br />
| Teachers, Researchers<br />
| Configurable survey tool<br />
| style="text-align:center;" | 45.3%<br />
|-<br />
| [[:en:Course_overview_report|Course overview]]<br />
| Report<br />
| Standard<br />
| Admins, Decision-makers<br />
| Comparison of participation across multiple courses<br />
| style="text-align:center;" | 45.0%<br />
|-<br />
| [[:en:Course_completion_status_block|Course completion status]]<br />
| Block<br />
| Standard<br />
| Students<br />
| View of student's own completion of activities<br />
| style="text-align:center;" | 41.4%<br />
|-<br />
| [http://moodle.org/plugins/view.php?plugin=block_progress Progress Bar]<br />
| Block<br />
| Additional<br />
| Students, Teachers<br />
| Time management tool for students with overview for teachers<br />
| style="text-align:center;" | 32.0%<br />
|-<br />
| [[:en:Events_list_report|Events list]]<br />
| Report<br />
| Standard<br />
| Teachers, Admins<br />
| Events that can be monitored/searched in logs<br />
| style="text-align:center;" | 28.6%<br />
|-<br />
| [[:en:Activity_results_block|Activity results block]]<br />
| Block<br />
| Standard<br />
| Students<br />
| Leader-board of results in single activity<br />
| style="text-align:center;" | 26.1%<br />
|-<br />
| [http://moodle.org/plugins/view.php?id=82 Configurable Reports] <br />
([https://docs.moodle.org/29/en/ad-hoc_contributed_reports A list of contributed reports])<br />
| Block ([https://github.com/nadavkav/moodle-report_configurablereports Report] [https://github.com/nadavkav/moodle-filter_crgraph Graphs filter])<br />
| Additional<br />
| Teachers, Admins, Decision-makers<br />
| Report generation and viewing<br />
| style="text-align:center;" | 22.7%<br />
|-<br />
| [[Overview_report|(Gradebook) Overview]]<br />
| Report<br />
| Standard<br />
| Teachers, Students<br />
| View of student grades across activites<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [[Statistics]]<br />
| Report<br />
| Standard<br />
| Admins, Decision-makers<br />
| Daily activity across site<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [[:en:Event_monitoring|Event monitor]]<br />
| Report<br />
| Standard<br />
| Teachers, Admins, Decision-makers<br />
| Proactive, focussed monitor tool<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/view/report_customsql Ad-hoc database queries]<br />
| Report<br />
| Additional<br />
| Teachers, Admins, Decision-makers<br />
| SQL-based report generation and viewing<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/browse.php?list=set&id=20 Engagement Analytics]<br />
| Block, Report, Activity module<br />
| Additional<br />
| Teachers<br />
| Configurable engagement measurement report and block<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/view/block_dedication Course Dedication]<br />
| Block<br />
| Additional<br />
| Students, Teachers<br />
| Estimated time online for students<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/view.php?plugin=block_graph_stats Graph Stats]<br />
| Block<br />
| Additional<br />
| Teachers, Admins<br />
| Daily visits to site or course<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/view/block_gismo GISMO]<br />
| Block<br />
| Additional<br />
| Teachers<br />
| Numerous charts of student activity participation<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/view/block_xp Level Up!]<br />
| Block<br />
| Additional<br />
| Students, Teachers<br />
| Incentive-drive participation meter<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/report_forumgraph Forum Graph]<br />
| Report<br />
| Additional<br />
| Teachers<br />
| Graph of forum interactions<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [https://moodle.org/plugins/block_analytics_graphs Analytics Graphs]<br />
| Block<br />
| Additional<br />
| Teachers<br />
| Visualisation of student participation<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [https://moodle.org/plugins/block_heatmap Heatmap]<br />
| Block<br />
| Additional<br />
| Teachers<br />
| Colour-coded indication of activity views on course page<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [https://moodle.org/plugins/local_analytics|Analytics]<br />
| Local<br />
| Additional<br />
| Admins, Decision-makers<br />
| Enriched feed to Google Analytics and Pywick<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [https://moodle.org/plugins/logstore_xapi Logstore xAPI]<br />
| Logstore<br />
| Additional<br />
| Admins, Decision-makers, Researchers<br />
| xAPI event stream output<br />
| style="text-align:center;" | N/A<br />
|}<br />
<br />
<nowiki>*</nowiki> Reported usage is drawn from the [http://research.moodle.net/71/1/Plugins%20Usage%20Survey%202015%20Report.pdf Plugins Usage Survey from 2015].<br />
<br />
== Integrations with Moodle ==<br />
<br />
A number of systems integrate with Moodle to provide learning analytics information externally.<br />
<br />
* [http://damos.world/2013/08/30/the-moodle-activity-viewer-mav-heatmaps-of-student-activity/ Moodle Activity Viewer] (MAV) ([https://github.com/damoclark/mav-enterprise Git]), consider [https://moodle.org/plugins/block_heatmap Heatmap] as an alternative<br />
* [http://www.intelliboard.net/ Intelliboard]<br />
* [http://www.lambdasolutions.net/products/lmsreporting/ Analytika]<br />
* [https://learninglocker.net/ Learning Locker], can be used with [https://moodle.org/plugins/logstore_xapi Logstore xAPI]<br />
* [http://klassdata.com/smartklass-learning-analytics-plugin/learning-analytics-moodle-smartklass/ SmartKlass]<br />
<br />
== Dimensions of Analytics ==<br />
<br />
Learning analytics are a concept that has been emerging under a number of different names through the past decades. Its origins lie in research in data mining and intelligent tutoring systems. LA tools can be categorised in a number of ways. The diagram below describes such tools by how deeply they are integrated with other systems ([http://www.netdimensions.com/downloads-2015/others/lms-evolution-or-extinction.pdf?mkt_tok=3RkMMJWWfF9wsRokuKjMZKXonjHpfsX56OQtW6CwlMI%2F0ER3fOvrPUfGjI4DTsdlI%2BSLDwEYGJlv6SgFS7fAMaFl3bgIWBY%3D source]).<br />
<br />
[[File:Learning-analytics.png]]<br />
<br />
== See also... ==<br />
* [https://moodle.org/mod/forum/view.php?id=8044 Analytics and reporting forum]<br />
* [https://moodle.org/mod/forum/view.php?id=8205 Moodle Research forum]<br />
* [[:dev:Moodle_research|Moodle research page]]<br />
* [[Logging]]<br />
* [[:en:Events_list_report|Events list]]<br />
* [[:dev:Learning_Analytics_Specification|Learning Analytics API specification]]<br />
* [[:dev:Working_Groups#Assessment_Analytics|Assessment Analytics working group details and issues]]<br />
* [[:dev:Event_2|Events specification]]<br />
* [[:dev:Logging_2|Logging specification]]<br />
* [[:dev:reportbuilder/API|Report Builder API specification]]<br />
<br />
[[Category:Report]]<br />
<br />
[[es:Análisis del aprendizaje]]</div>Deraadthttps://docs.moodle.org/30/en/index.php?title=Learning_analytics&diff=122827Learning analytics2016-04-06T06:43:23Z<p>Deraadt: Adding Events list</p>
<hr />
<div>Learning Analytics are any piece of information that can help an LMS user improve learning outcomes. Users include students, teachers, administrators and decision-makers.<br />
<br />
== Moodle Plugins ==<br />
<br />
There are a number of reports, blocks and other plugins for Moodle that provide learning analytics.<br />
<br />
{| class="nicetable"<br />
|-<br />
! Plugin <br />
! Plugin type<br />
! Standard / Additional<br />
! Useful for<br />
! Reported usage*<br />
|-<br />
| [[:en:Logs|Logs]]<br />
| Report<br />
| Standard<br />
| Teachers, Admins, Decision-makers<br />
| style="text-align:center;" | 71.4%<br />
|-<br />
| [[:en:Activity_report|Activity]]<br />
| Report<br />
| Standard<br />
| Teachers<br />
| style="text-align:center;" | 69.1%<br />
|-<br />
| [[:en:Using_Activity_completion|Activity completion]], see also [[:en:Using_Course_completion|Course completion]]<br />
| Report<br />
| Standard<br />
| Teachers<br />
| style="text-align:center;" | 66.3%<br />
|-<br />
| [[:en:Logs|Live logs]]<br />
| Report<br />
| Standard<br />
| Teachers, Admins<br />
| style="text-align:center;" | 55.2% <br />
|-<br />
| [[:en:Feedback_activity|Feedback]]<br />
| Activity<br />
| Standard<br />
| Teachers, Researchers<br />
| style="text-align:center;" | 59.5% <br />
|-<br />
| [[:en:Quiz_statistics_report|(Quiz) Statistics]]<br />
| Report<br />
| Standard<br />
| Teachers<br />
| style="text-align:center;" | 53.0%<br />
|-<br />
| [[:en:Participation_report|(Course) Participation]]<br />
| Report<br />
| Standard<br />
| Teachers<br />
| style="text-align:center;" | 49.9%<br />
|-<br />
| [[:en:Survey_module|Survey]]<br />
| Activity<br />
| Standard<br />
| Teachers, Researchers<br />
| style="text-align:center;" | 45.6%<br />
|-<br />
| [http://moodle.org/plugins/view.php?plugin=mod_questionnaire Questionnaire]<br />
| Activity<br />
| Additional<br />
| Teachers, Researchers<br />
| style="text-align:center;" | 45.3%<br />
|-<br />
| [[:en:Course_overview_report|Course overview]]<br />
| Report<br />
| Standard<br />
| Admins, Decision-makers<br />
| style="text-align:center;" | 45.0%<br />
|-<br />
| [[:en:Course_completion_status_block|Course completion status]]<br />
| Block<br />
| Standard<br />
| Students<br />
| style="text-align:center;" | 41.4%<br />
|-<br />
| [http://moodle.org/plugins/view.php?plugin=block_progress Progress Bar]<br />
| Block<br />
| Additional<br />
| Students, Teachers<br />
| style="text-align:center;" | 32.0%<br />
|-<br />
| [[:en:Events_list_report|Events list]]<br />
| Report<br />
| Standard<br />
| Teachers, Admins<br />
| style="text-align:center;" | 28.6%<br />
|-<br />
| [[:en:Activity_results_block|Activity results block]]<br />
| Block<br />
| Standard<br />
| Students<br />
| style="text-align:center;" | 26.1%<br />
|-<br />
| [http://moodle.org/plugins/view.php?id=82 Configurable Reports] <br />
([https://docs.moodle.org/29/en/ad-hoc_contributed_reports A list of contributed reports])<br />
| Block ([https://github.com/nadavkav/moodle-report_configurablereports Report] [https://github.com/nadavkav/moodle-filter_crgraph Graphs filter])<br />
| Additional<br />
| Teachers, Admins, Decision-makers<br />
| style="text-align:center;" | 22.7%<br />
|-<br />
| [[Overview_report|(Gradebook) Overview]]<br />
| Report<br />
| Standard<br />
| Teachers, Students<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [[Statistics]]<br />
| Report<br />
| Standard<br />
| Admins, Decision-makers<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/view/report_customsql Ad-hoc database queries]<br />
| Report<br />
| Additional<br />
| Teachers, Admins, Decision-makers<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/browse.php?list=set&id=20 Engagement Analytics]<br />
| Block, Report, Activity module<br />
| Additional<br />
| Teachers<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/view/block_dedication Course Dedication]<br />
| Block<br />
| Additional<br />
| Students, Teachers<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/view.php?plugin=block_graph_stats Graph Stats]<br />
| Block<br />
| Additional<br />
| Teachers, Admins<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/view/block_gismo GISMO]<br />
| Block<br />
| Additional<br />
| Teachers<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/view/block_xp Level Up!]<br />
| Block<br />
| Additional<br />
| Students, Teachers<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/report_forumgraph Forum Graph]<br />
| Report<br />
| Additional<br />
| Teachers<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [https://moodle.org/plugins/block_analytics_graphs Analytics Graphs]<br />
| Block<br />
| Additional<br />
| Teachers<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [https://moodle.org/plugins/block_heatmap Heatmap]<br />
| Block<br />
| Additional<br />
| Teachers<br />
| style="text-align:center;" | N/A<br />
|}<br />
<br />
<nowiki>*</nowiki> Reported usage is drawn from the [http://research.moodle.net/71/1/Plugins%20Usage%20Survey%202015%20Report.pdf Plugins Usage Survey from 2015].<br />
<br />
== Integrations with Moodle ==<br />
<br />
A number of systems integrate with Moodle to provide learning analytics information.<br />
<br />
* [http://damos.world/2013/08/30/the-moodle-activity-viewer-mav-heatmaps-of-student-activity/ Moodle Activity Viewer] (MAV) ([https://github.com/damoclark/mav-enterprise Git])<br />
* [http://www.intelliboard.net/ Intelliboard]<br />
<br />
== Dimensions of Analytics ==<br />
<br />
Learning analytics are a concept that has been emerging under a number of different names through the past decades. Its origins lie in research in data mining and intelligent tutoring systems. LA tools can be categorised in a number of ways. The diagram below describes such tools by how deeply they are integrated with other systems ([http://www.netdimensions.com/downloads-2015/others/lms-evolution-or-extinction.pdf?mkt_tok=3RkMMJWWfF9wsRokuKjMZKXonjHpfsX56OQtW6CwlMI%2F0ER3fOvrPUfGjI4DTsdlI%2BSLDwEYGJlv6SgFS7fAMaFl3bgIWBY%3D source]).<br />
<br />
[[File:Learning-analytics.png]]<br />
<br />
== See also... ==<br />
* [https://moodle.org/mod/forum/view.php?id=8044 Analytics and reporting forum]<br />
* [https://moodle.org/mod/forum/view.php?id=8205 Moodle Research forum]<br />
* [[:dev:Moodle_research|Moodle research page]]<br />
* [[Logging]]<br />
* [[:en:Events_list_report|Events list]]<br />
* [[:dev:Learning_Analytics_Specification|Learning Analytics API specification]]<br />
* [[:dev:Working_Groups#Assessment_Analytics|Assessment Analytics working group details and issues]]<br />
* [[:dev:Event_2|Events specification]]<br />
* [[:dev:Logging_2|Logging specification]]<br />
* [[:dev:reportbuilder/API|Report Builder API specification]]<br />
<br />
[[Category:Report]]<br />
<br />
[[es:Análisis del aprendizaje]]</div>Deraadthttps://docs.moodle.org/30/en/index.php?title=Learning_analytics&diff=122826Learning analytics2016-04-06T06:42:29Z<p>Deraadt: Adding more learning analytics plugins</p>
<hr />
<div>Learning Analytics are any piece of information that can help an LMS user improve learning outcomes. Users include students, teachers, administrators and decision-makers.<br />
<br />
== Moodle Plugins ==<br />
<br />
There are a number of reports, blocks and other plugins for Moodle that provide learning analytics.<br />
<br />
{| class="nicetable"<br />
|-<br />
! Plugin <br />
! Plugin type<br />
! Standard / Additional<br />
! Useful for<br />
! Reported usage*<br />
|-<br />
| [[:en:Logs|Logs]]<br />
| Report<br />
| Standard<br />
| Teachers, Admins, Decision-makers<br />
| style="text-align:center;" | 71.4%<br />
|-<br />
| [[:en:Activity_report|Activity]]<br />
| Report<br />
| Standard<br />
| Teachers<br />
| style="text-align:center;" | 69.1%<br />
|-<br />
| [[:en:Using_Activity_completion|Activity completion]], see also [[:en:Using_Course_completion|Course completion]]<br />
| Report<br />
| Standard<br />
| Teachers<br />
| style="text-align:center;" | 66.3%<br />
|-<br />
| [[:en:Logs|Live logs]]<br />
| Report<br />
| Standard<br />
| Teachers, Admins<br />
| style="text-align:center;" | 55.2% <br />
|-<br />
| [[:en:Feedback_activity|Feedback]]<br />
| Activity<br />
| Standard<br />
| Teachers, Researchers<br />
| style="text-align:center;" | 59.5% <br />
|-<br />
| [[:en:Quiz_statistics_report|(Quiz) Statistics]]<br />
| Report<br />
| Standard<br />
| Teachers<br />
| style="text-align:center;" | 53.0%<br />
|-<br />
| [[:en:Participation_report|(Course) Participation]]<br />
| Report<br />
| Standard<br />
| Teachers<br />
| style="text-align:center;" | 49.9%<br />
|-<br />
| [[:en:Survey_module|Survey]]<br />
| Activity<br />
| Standard<br />
| Teachers, Researchers<br />
| style="text-align:center;" | 45.6%<br />
|-<br />
| [http://moodle.org/plugins/view.php?plugin=mod_questionnaire Questionnaire]<br />
| Activity<br />
| Additional<br />
| Teachers, Researchers<br />
| style="text-align:center;" | 45.3%<br />
|-<br />
| [[:en:Course_overview_report|Course overview]]<br />
| Report<br />
| Standard<br />
| Admins, Decision-makers<br />
| style="text-align:center;" | 45.0%<br />
|-<br />
| [[:en:Course_completion_status_block|Course completion status]]<br />
| Block<br />
| Standard<br />
| Students<br />
| style="text-align:center;" | 41.4%<br />
|-<br />
| [http://moodle.org/plugins/view.php?plugin=block_progress Progress Bar]<br />
| Block<br />
| Additional<br />
| Students, Teachers<br />
| style="text-align:center;" | 32.0%<br />
|-<br />
| [[:en:Events_list_report|Events list]]<br />
| Report<br />
| Standard<br />
| Teachers, Admins<br />
| style="text-align:center;" | 28.6%<br />
|-<br />
| [[:en:Activity_results_block|Activity results block]]<br />
| Block<br />
| Standard<br />
| Students<br />
| style="text-align:center;" | 26.1%<br />
|-<br />
| [http://moodle.org/plugins/view.php?id=82 Configurable Reports] <br />
([https://docs.moodle.org/29/en/ad-hoc_contributed_reports A list of contributed reports])<br />
| Block ([https://github.com/nadavkav/moodle-report_configurablereports Report] [https://github.com/nadavkav/moodle-filter_crgraph Graphs filter])<br />
| Additional<br />
| Teachers, Admins, Decision-makers<br />
| style="text-align:center;" | 22.7%<br />
|-<br />
| [[Overview_report|(Gradebook) Overview]]<br />
| Report<br />
| Standard<br />
| Teachers, Students<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [[Statistics]]<br />
| Report<br />
| Standard<br />
| Admins, Decision-makers<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/view/report_customsql Ad-hoc database queries]<br />
| Report<br />
| Additional<br />
| Teachers, Admins, Decision-makers<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/browse.php?list=set&id=20 Engagement Analytics]<br />
| Block, Report, Activity module<br />
| Additional<br />
| Teachers<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/view/block_dedication Course Dedication]<br />
| Block<br />
| Additional<br />
| Students, Teachers<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/view.php?plugin=block_graph_stats Graph Stats]<br />
| Block<br />
| Additional<br />
| Teachers, Admins<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/view/block_gismo GISMO]<br />
| Block<br />
| Additional<br />
| Teachers<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/view/block_xp Level Up!]<br />
| Block<br />
| Additional<br />
| Students, Teachers<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/report_forumgraph Forum Graph]<br />
| Report<br />
| Additional<br />
| Teachers<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [https://moodle.org/plugins/block_analytics_graphs Analytics Graphs]<br />
| Block<br />
| Additional<br />
| Teachers<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [https://moodle.org/plugins/block_heatmap Heatmap]<br />
| Block<br />
| Additional<br />
| Teachers<br />
| style="text-align:center;" | N/A<br />
|}<br />
<br />
<nowiki>*</nowiki> Reported usage is drawn from the [http://research.moodle.net/71/1/Plugins%20Usage%20Survey%202015%20Report.pdf Plugins Usage Survey from 2015].<br />
<br />
== Integrations with Moodle ==<br />
<br />
A number of systems integrate with Moodle to provide learning analytics information.<br />
<br />
* [http://damos.world/2013/08/30/the-moodle-activity-viewer-mav-heatmaps-of-student-activity/ Moodle Activity Viewer] (MAV) ([https://github.com/damoclark/mav-enterprise Git])<br />
* [http://www.intelliboard.net/ Intelliboard]<br />
<br />
== Dimensions of Analytics ==<br />
<br />
Learning analytics are a concept that has been emerging under a number of different names through the past decades. Its origins lie in research in data mining and intelligent tutoring systems. LA tools can be categorised in a number of ways. The diagram below describes such tools by how deeply they are integrated with other systems ([http://www.netdimensions.com/downloads-2015/others/lms-evolution-or-extinction.pdf?mkt_tok=3RkMMJWWfF9wsRokuKjMZKXonjHpfsX56OQtW6CwlMI%2F0ER3fOvrPUfGjI4DTsdlI%2BSLDwEYGJlv6SgFS7fAMaFl3bgIWBY%3D source]).<br />
<br />
[[File:Learning-analytics.png]]<br />
<br />
== See also... ==<br />
* [https://moodle.org/mod/forum/view.php?id=8044 Analytics and reporting forum]<br />
* [https://moodle.org/mod/forum/view.php?id=8205 Moodle Research forum]<br />
* [[:dev:Moodle_research|Moodle research page]]<br />
* [[Logging]]<br />
* [[:dev:Learning_Analytics_Specification|Learning Analytics API specification]]<br />
* [[:dev:Working_Groups#Assessment_Analytics|Assessment Analytics working group details and issues]]<br />
* [[:dev:Event_2|Events specification]]<br />
* [[:dev:Logging_2|Logging specification]]<br />
* [[:dev:reportbuilder/API|Report Builder API specification]]<br />
<br />
[[Category:Report]]<br />
<br />
[[es:Análisis del aprendizaje]]</div>Deraadthttps://docs.moodle.org/30/en/index.php?title=Heatmap_block&diff=122535Heatmap block2016-03-18T04:50:30Z<p>Deraadt: /* Capabilities (Controlling who sees parts of the block) */</p>
<hr />
<div>{{Infobox plugin<br />
|type = Block<br />
|entry = https://moodle.org/plugins/view.php?plugin=block_heatmap<br />
|tracker = https://tracker.moodle.org/browse/CONTRIB/component/15738<br />
|discussion = https://moodle.org/mod/forum/discuss.php?d=329136<br />
|maintainer = [[User:Michael de Raadt|Michael de Raadt]]<br />
|float = right<br />
}}<br />
[[Blocks|Back to Blocks page]]<br />
<br />
== Features ==<br />
<br />
[[Image:Heatmap_in_course.png|thumb|right|A heatmap applied to a course]]<br />
* The Heatmap block overlays a heatmap onto a course to highlight activities with more or less activity.<br />
* Counts of visits and unique users to each activity is also shown.<br />
* The Heatmap can be toggled off when it is not needed.<br />
<br />
== Installation ==<br />
<br />
The Heatmap block is added like other blocks ([[Installing_contributed_modules_or_plugins|How to install a block]]).<br />
<br />
== Global settings ==<br />
<br />
The Heatmap block has a number of global settings that will be seen on installation and can be accessed later at Site administration > Plugins > Blocks > Heatmap.<br />
[[Image:Heatmap_global_settings.png|thumb|Global settings]]<br />
* ''Cache lifespan''<br>A cache is used to retain results and reduce impact on the log table. The lifespan of the cache can be controlled. A longer-lived cache means the burden of querying the log table is reduced. A shorter-lived cache will show more recent results.<br />
* ''Check for activity''<br>You can limit the timespan that is covered by the log entries queried by the block can be controlled. You can choose to search back to the start of the course (default) or to the beginning of the log. This option can be changed if courses are re-run and teachers want to see beyond the start of the current instance. Searching further back in the log may cause additional load.<br />
* ''What to show on course page''<br>Two things can be added to course pages: a background colour for activities with visits and icons showing the count of visits and count of unique users. You can select to show both (default) or one or the other.<br />
<br />
'''Note: Changes to cache-related settings may not appear immediately in the user interface unless you also purge caches after saving these settings.'''<br />
<br />
== Capabilities (Controlling who sees parts of the block) ==<br />
<br />
The block uses a number of capabilities that are added when the block is installed.<br />
[[Image:Heatmap_capabilities.png|thumb|Capabilities]]<br />
* ''Add a new Heatmap block'' (block/heatmap:addinstance)<br>Controls whether the Heatmap block can be added to a course page. By default, this is allowed for the following archetypal roles.<br />
** Teacher (editingteacher)<br />
** Manager (manager)<br />
** (and Admins)<br />
* ''View the Heatmap'' (block/heatmap:view)<br>Controls who can see the Heatmap block and subsequently the overlay of the heatmap on the course. This is something that will usually be relevant to Teachers, so it is hidden from students.<br />
** Teacher (editingteacher)<br />
** Manager (manager)<br />
** (and Admins)<br />
<br />
== Setting up a Heatmap in a course ==<br />
<br />
Once the Heatmap block is installed, you can use it in a course as follows.<br />
# Turn editing on<br />
# Add the Heatmap block to your page ([[Blocks|How to add a block]])<br />
# Toggle the Heatmap off and on as needed<br />
<br />
== Links ==<br />
<br />
* [http://moodle.org/plugins/view.php?plugin=block_heatmap Entry in Plugins repository]<br />
* [https://tracker.moodle.org/browse/CONTRIB/component/15738 Bug Tracker Page] (Please report bugs here.)<br />
* [https://github.com/deraadt/moodle-block_heatmap Git repository]<br />
<br />
===Videos===<br />
<br />
<mediaplayer>https://www.youtube.com/watch?v=jqZP0T0rR4U</mediaplayer><br />
<br />
[[Category:Contributed code]]<br />
[[Category:Block]]<br />
<br />
[[es:Bloque Heatmap]]</div>Deraadthttps://docs.moodle.org/30/en/index.php?title=File:Heatmap_capabilities.png&diff=122534File:Heatmap capabilities.png2016-03-18T04:45:35Z<p>Deraadt: Deraadt uploaded a new version of File:Heatmap capabilities.png</p>
<hr />
<div></div>Deraadthttps://docs.moodle.org/30/en/index.php?title=Heatmap_block&diff=122533Heatmap block2016-03-18T04:45:00Z<p>Deraadt: Removing capability for the Dashboard as it was removed from the block</p>
<hr />
<div>{{Infobox plugin<br />
|type = Block<br />
|entry = https://moodle.org/plugins/view.php?plugin=block_heatmap<br />
|tracker = https://tracker.moodle.org/browse/CONTRIB/component/15738<br />
|discussion = https://moodle.org/mod/forum/discuss.php?d=329136<br />
|maintainer = [[User:Michael de Raadt|Michael de Raadt]]<br />
|float = right<br />
}}<br />
[[Blocks|Back to Blocks page]]<br />
<br />
== Features ==<br />
<br />
[[Image:Heatmap_in_course.png|thumb|right|A heatmap applied to a course]]<br />
* The Heatmap block overlays a heatmap onto a course to highlight activities with more or less activity.<br />
* Counts of visits and unique users to each activity is also shown.<br />
* The Heatmap can be toggled off when it is not needed.<br />
<br />
== Installation ==<br />
<br />
The Heatmap block is added like other blocks ([[Installing_contributed_modules_or_plugins|How to install a block]]).<br />
<br />
== Global settings ==<br />
<br />
The Heatmap block has a number of global settings that will be seen on installation and can be accessed later at Site administration > Plugins > Blocks > Heatmap.<br />
[[Image:Heatmap_global_settings.png|thumb|Global settings]]<br />
* ''Cache lifespan''<br>A cache is used to retain results and reduce impact on the log table. The lifespan of the cache can be controlled. A longer-lived cache means the burden of querying the log table is reduced. A shorter-lived cache will show more recent results.<br />
* ''Check for activity''<br>You can limit the timespan that is covered by the log entries queried by the block can be controlled. You can choose to search back to the start of the course (default) or to the beginning of the log. This option can be changed if courses are re-run and teachers want to see beyond the start of the current instance. Searching further back in the log may cause additional load.<br />
* ''What to show on course page''<br>Two things can be added to course pages: a background colour for activities with visits and icons showing the count of visits and count of unique users. You can select to show both (default) or one or the other.<br />
<br />
'''Note: Changes to cache-related settings may not appear immediately in the user interface unless you also purge caches after saving these settings.'''<br />
<br />
== Capabilities (Controlling who sees parts of the block) ==<br />
<br />
The block uses a number of capabilities that are added when the block is installed.<br />
[[Image:Heatmap_capabilities.png|thumb|Global settings]]<br />
* ''Add a new Heatmap block'' (block/heatmap:addinstance)<br>Controls whether the Heatmap block can be added to a course page. By default, this is allowed for the following archetypal roles.<br />
** Teacher (editingteacher)<br />
** Manager (manager)<br />
** (and Admins)<br />
* ''View the Heatmap'' (block/heatmap:view)<br>Controls who can see the Heatmap block and subsequently the overlay of the heatmap on the course. This is something that will usually be relevant to Teachers, so it is hidden from students.<br />
** Teacher (editingteacher)<br />
** Manager (manager)<br />
** (and Admins)<br />
<br />
== Setting up a Heatmap in a course ==<br />
<br />
Once the Heatmap block is installed, you can use it in a course as follows.<br />
# Turn editing on<br />
# Add the Heatmap block to your page ([[Blocks|How to add a block]])<br />
# Toggle the Heatmap off and on as needed<br />
<br />
== Links ==<br />
<br />
* [http://moodle.org/plugins/view.php?plugin=block_heatmap Entry in Plugins repository]<br />
* [https://tracker.moodle.org/browse/CONTRIB/component/15738 Bug Tracker Page] (Please report bugs here.)<br />
* [https://github.com/deraadt/moodle-block_heatmap Git repository]<br />
<br />
===Videos===<br />
<br />
<mediaplayer>https://www.youtube.com/watch?v=jqZP0T0rR4U</mediaplayer><br />
<br />
[[Category:Contributed code]]<br />
[[Category:Block]]<br />
<br />
[[es:Bloque Heatmap]]</div>Deraadthttps://docs.moodle.org/30/en/index.php?title=admin/setting/blocksettingheatmap&diff=122406admin/setting/blocksettingheatmap2016-03-08T02:13:15Z<p>Deraadt: Redirected page to Heatmap block#Global settings</p>
<hr />
<div>#REDIRECT [[Heatmap_block#Global_settings]]</div>Deraadthttps://docs.moodle.org/30/en/index.php?title=Heatmap_block&diff=122405Heatmap block2016-03-08T02:12:04Z<p>Deraadt: Created page with "{{Infobox plugin |type = Block |entry = https://moodle.org/plugins/view.php?plugin=block_heatmap |tracker = https://tracker.moodle.org/browse/CONTRIB/component/15738 |discussi..."</p>
<hr />
<div>{{Infobox plugin<br />
|type = Block<br />
|entry = https://moodle.org/plugins/view.php?plugin=block_heatmap<br />
|tracker = https://tracker.moodle.org/browse/CONTRIB/component/15738<br />
|discussion = https://moodle.org/mod/forum/discuss.php?d=329136<br />
|maintainer = [[User:Michael de Raadt|Michael de Raadt]]<br />
|float = right<br />
}}<br />
[[Blocks|Back to Blocks page]]<br />
<br />
== Features ==<br />
<br />
[[Image:Heatmap_in_course.png|thumb|right|A heatmap applied to a course]]<br />
* The Heatmap block overlays a heatmap onto a course to highlight activities with more or less activity.<br />
* Counts of visits and unique users to each activity is also shown.<br />
* The Heatmap can be toggled off when it is not needed.<br />
<br />
== Installation ==<br />
<br />
The Heatmap block is added like other blocks ([[Installing_contributed_modules_or_plugins|How to install a block]]).<br />
<br />
== Global settings ==<br />
<br />
The Heatmap block has a number of global settings that will be seen on installation and can be accessed later at Site administration > Plugins > Blocks > Heatmap.<br />
[[Image:Heatmap_global_settings.png|thumb|Global settings]]<br />
* ''Cache lifespan''<br>A cache is used to retain results and reduce impact on the log table. The lifespan of the cache can be controlled. A longer-lived cache means the burden of querying the log table is reduced. A shorter-lived cache will show more recent results.<br />
* ''Check for activity''<br>You can limit the timespan that is covered by the log entries queried by the block can be controlled. You can choose to search back to the start of the course (default) or to the beginning of the log. This option can be changed if courses are re-run and teachers want to see beyond the start of the current instance. Searching further back in the log may cause additional load.<br />
* ''What to show on course page''<br>Two things can be added to course pages: a background colour for activities with visits and icons showing the count of visits and count of unique users. You can select to show both (default) or one or the other.<br />
<br />
'''Note: Changes to cache-related settings may not appear immediately in the user interface unless you also purge caches after saving these settings.'''<br />
<br />
== Capabilities (Controlling who sees parts of the block) ==<br />
<br />
The block uses a number of capabilities that are added when the block is installed.<br />
[[Image:Heatmap_capabilities.png|thumb|Global settings]]<br />
* ''Add a Heatmap block to the Dashboard'' (block/heatmap:myaddinstance)<br>Leave this off for all users. The block won't work on the Dashboard.<br />
* ''Add a new Heatmap block'' (block/heatmap:addinstance)<br>Controls whether the Heatmap block can be added to a course page. By default, this is allowed for the following archetypal roles.<br />
** Teacher (editingteacher)<br />
** Manager (manager)<br />
** (and Admins)<br />
* ''View the Heatmap'' (block/heatmap:view)<br>Controls who can see the Heatmap block and subsequently the overlay of the heatmap on the course. This is something that will usually be relevant to Teachers, so it is hidden from students.<br />
** Teacher (editingteacher)<br />
** Manager (manager)<br />
** (and Admins)<br />
<br />
== Setting up a Heatmap in a course ==<br />
<br />
Once the Heatmap block is installed, you can use it in a course as follows.<br />
# Turn editing on<br />
# Add the Heatmap block to your page ([[Blocks|How to add a block]])<br />
# Toggle the Heatmap off and on as needed<br />
<br />
== Links ==<br />
<br />
* [http://moodle.org/plugins/view.php?plugin=block_heatmap Entry in Plugins repository]<br />
* [https://tracker.moodle.org/browse/CONTRIB/component/15738 Bug Tracker Page] (Please report bugs here.)<br />
* [https://github.com/deraadt/moodle-block_heatmap Git repository]<br />
<br />
===Videos===<br />
<br />
<mediaplayer>https://www.youtube.com/watch?v=jqZP0T0rR4U</mediaplayer><br />
<br />
[[Category:Contributed code]]<br />
[[Category:Block]]</div>Deraadthttps://docs.moodle.org/30/en/index.php?title=File:Heatmap_capabilities.png&diff=122404File:Heatmap capabilities.png2016-03-08T01:44:41Z<p>Deraadt: </p>
<hr />
<div></div>Deraadthttps://docs.moodle.org/30/en/index.php?title=File:Heatmap_global_settings.png&diff=122403File:Heatmap global settings.png2016-03-08T01:25:45Z<p>Deraadt: </p>
<hr />
<div></div>Deraadthttps://docs.moodle.org/30/en/index.php?title=File:Heatmap_in_course.png&diff=122402File:Heatmap in course.png2016-03-08T01:23:30Z<p>Deraadt: </p>
<hr />
<div></div>Deraadthttps://docs.moodle.org/30/en/index.php?title=Learning_analytics&diff=122354Learning analytics2016-02-26T03:17:34Z<p>Deraadt: Adding Level Up!</p>
<hr />
<div>Learning Analytics are any piece of information that can help an LMS user improve learning outcomes. Users include students, teachers, administrators and decision-makers.<br />
<br />
== Moodle Plugins ==<br />
<br />
There are a number of reports, blocks and other plugins for Moodle that provide learning analytics.<br />
<br />
{| class="nicetable"<br />
|-<br />
! Plugin <br />
! Plugin type<br />
! Standard / Additional<br />
! Useful for<br />
! Reported usage*<br />
|-<br />
| [[:en:Logs|Logs]]<br />
| Report<br />
| Standard<br />
| Teachers, Admins, Decision-makers<br />
| style="text-align:center;" | 71.4%<br />
|-<br />
| [[:en:Activity_report|Activity]]<br />
| Report<br />
| Standard<br />
| Teachers<br />
| style="text-align:center;" | 69.1%<br />
|-<br />
| [[:en:Using_Activity_completion|Activity completion]]<br />
| Report<br />
| Standard<br />
| Teachers<br />
| style="text-align:center;" | 66.3%<br />
|-<br />
| [[:en:Logs|Live logs]]<br />
| Report<br />
| Standard<br />
| Teachers, Admins<br />
| style="text-align:center;" | 55.2% <br />
|-<br />
| [[:en:Feedback_activity|Feedback]]<br />
| Activity<br />
| Standard<br />
| Teachers, Researchers<br />
| style="text-align:center;" | 59.5% <br />
|-<br />
| [[:en:Quiz_statistics_report|(Quiz) Statistics]]<br />
| Report<br />
| Standard<br />
| Teachers<br />
| style="text-align:center;" | 53.0%<br />
|-<br />
| [[:en:Participation_report|(Course) Participation]]<br />
| Report<br />
| Standard<br />
| Teachers<br />
| style="text-align:center;" | 49.9%<br />
|-<br />
| [[:en:Survey_module|Survey]]<br />
| Activity<br />
| Standard<br />
| Teachers, Researchers<br />
| style="text-align:center;" | 45.6%<br />
|-<br />
| [http://moodle.org/plugins/view.php?plugin=mod_questionnaire Questionnaire]<br />
| Activity<br />
| Additional<br />
| Teachers, Researchers<br />
| style="text-align:center;" | 45.3%<br />
|-<br />
| [[:en:Course_overview_report|Course overview]]<br />
| Report<br />
| Standard<br />
| Admins, Decision-makers<br />
| style="text-align:center;" | 45.0%<br />
|-<br />
| [[:en:Course_completion_status_block|Course completion status]]<br />
| Block<br />
| Standard<br />
| Students<br />
| style="text-align:center;" | 41.4%<br />
|-<br />
| [http://moodle.org/plugins/view.php?plugin=block_progress Progress Bar]<br />
| Block<br />
| Additional<br />
| Students, Teachers<br />
| style="text-align:center;" | 32.0%<br />
|-<br />
| [[:en:Events_list_report|Events list]]<br />
| Report<br />
| Standard<br />
| Teachers, Admins<br />
| style="text-align:center;" | 28.6%<br />
|-<br />
| [[:en:Activity_results_block|Activity results block]]<br />
| Block<br />
| Standard<br />
| Students<br />
| style="text-align:center;" | 26.1%<br />
|-<br />
| [http://moodle.org/plugins/view.php?id=82 Configurable Reports] <br />
([https://docs.moodle.org/29/en/ad-hoc_contributed_reports A list of contributed reports])<br />
| Block ([https://github.com/nadavkav/moodle-report_configurablereports Report])<br />
| Additional<br />
| Teachers, Admins, Decision-makers<br />
| style="text-align:center;" | 22.7%<br />
|-<br />
| [[Overview_report|(Gradebook) Overview]]<br />
| Report<br />
| Standard<br />
| Teachers, Students<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/view/report_customsql Ad-hoc database queries]<br />
| Report<br />
| Additional<br />
| Teachers, Admins, Decision-makers<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/browse.php?list=set&id=20 Engagement Analytics]<br />
| Block, Report, Activity module<br />
| Additional<br />
| Teachers<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/view/block_dedication Course Dedication]<br />
| Block<br />
| Additional<br />
| Students, Teachers<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/view.php?plugin=block_graph_stats Graph Stats]<br />
| Block<br />
| Additional<br />
| Teachers, Admins<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/view/block_gismo GISMO]<br />
| Block<br />
| Additional<br />
| Teachers<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/view/block_xp Level Up!]<br />
| Block<br />
| Additional<br />
| Students, Teachers<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/report_forumgraph Forum Graph]<br />
| Report<br />
| Additional<br />
| Teachers<br />
| style="text-align:center;" | N/A<br />
|}<br />
<br />
<nowiki>*</nowiki> Reported usage is drawn from the [http://research.moodle.net/71/1/Plugins%20Usage%20Survey%202015%20Report.pdf Plugins Usage Survey from 2015].<br />
<br />
== Integrations with Moodle ==<br />
<br />
A number of systems integrate with Moodle to provide learning analytics information.<br />
<br />
* [http://damos.world/2013/08/30/the-moodle-activity-viewer-mav-heatmaps-of-student-activity/ Moodle Activity Viewer] (MAV) ([https://github.com/damoclark/mav-enterprise Git])<br />
* [http://www.intelliboard.net/ Intelliboard]<br />
<br />
== Dimensions of Analytics ==<br />
<br />
Learning analytics are a concept that has been emerging under a number of different names through the past decades. Its origins lie in research in data mining and intelligent tutoring systems. LA tools can be categorised in a number of ways. The diagram below describes such tools by how deeply they are integrated with other systems ([http://www.netdimensions.com/downloads-2015/others/lms-evolution-or-extinction.pdf?mkt_tok=3RkMMJWWfF9wsRokuKjMZKXonjHpfsX56OQtW6CwlMI%2F0ER3fOvrPUfGjI4DTsdlI%2BSLDwEYGJlv6SgFS7fAMaFl3bgIWBY%3D source]).<br />
<br />
[[File:Learning-analytics.png]]<br />
<br />
== See also... ==<br />
* [https://moodle.org/mod/forum/view.php?id=8044 Analytics and reporting forum]<br />
* [https://moodle.org/mod/forum/view.php?id=8205 Moodle Research forum]<br />
* [[:dev:Moodle_research|Moodle research page]]<br />
* [[Logging]]<br />
* [[:dev:Learning_Analytics_Specification|Learning Analytics API specification]]<br />
* [[:dev:Working_Groups#Assessment_Analytics|Assessment Analytics working group details and issues]]<br />
* [[:dev:Event_2|Events specification]]<br />
* [[:dev:Logging_2|Logging specification]]<br />
* [[:dev:reportbuilder/API|Report Builder API specification]]<br />
<br />
[[Category:Report]]<br />
<br />
[[es:Análisis del aprendizaje]]</div>Deraadthttps://docs.moodle.org/30/en/index.php?title=Progress_Bar_block&diff=122353Progress Bar block2016-02-25T21:44:00Z<p>Deraadt: Changing repo link to Github</p>
<hr />
<div>{{Infobox plugin<br />
|type = Block, Progress bar <br />
|entry = https://moodle.org/plugins/view.php?plugin=block_progress<br />
|tracker = https://tracker.moodle.org/browse/CONTRIB/component/10489/?selectedTab=com.atlassian.jira.jira-projects-plugin:component-summary-panel<br />
|discussion = https://moodle.org/plugins/view.php?plugin=block_progress<br />
|maintainer = [[User:Michael de Raadt|Michael de Raadt]]<br />
|float = right<br />
}}<br />
[[Blocks|Back to Blocks page]]<br />
<br />
== Features ==<br />
<br />
[[Image:Bar_in_block_-_with_details.png|right|A progress bar for a student]]<br />
* The Progress Bar is a time-management tool for students.<br />
* It visually shows what activities/resources a student is supposed to interact with in a course.<br />
* It is colour coded so students can quickly see what they have and have not completed/viewed.<br />
* The teacher selects which pre-existing activities/resources are to be included in the Progress Bar and when they should be completed/viewed.<br />
* Ordering can be done by times/deadlines or by the ordering of activities in the course.<br />
* There is an overview page allowing teachers to see the progress of all students in a class, which is helpful for finding students at risk.<br />
* Adding the Progress Bar block to the [[Dashboard]] shows users a combined view of their progress on all courses (where the block is set up).<br />
[[Image:Overview_of_students.png|The overview page]]<br />
<br />
== Installation ==<br />
<br />
The Progress Bar block is added like other blocks ([[Installing_contributed_modules_or_plugins|How to install a block]]).<br />
<br />
== Global settings ==<br />
<br />
The Progress Bar block has a number of global settings that will be seen on installation and can be accessed later at Site administration > Plugins > Blocks > Progress Bar.<br />
[[Image:Progress_Bar_Global_settings.png|thumb|Global settings]]<br />
* ''Course name to show on Dashboard''<br>The block can be added to the dashboard and combines visible Progress Bar block content from the courses a user is enrolled in. By default, the course name shown for each relevant course, is the short course name, but some institutions/organisations may not think this is appropriate in relation to their course naming scheme, so a long course name can be selected.<br />
* ''Colours''<br>By default, the colours used in the block are red, blue and green. In certain cultures these colours may not have the same meaning. Also, institutions/organisations may wish to use colours that match their theme.<br />
* ''Show inactive students in Overview''<br>In most cases, inactive students are not wanted in course lists, such as the Overview page associated with the Progress Bar. However, in some cases, such as ongoing courses, inactive students might need to be visible on the Overview page.<br />
<br />
== Capabilities (Controlling who sees parts of the block) ==<br />
<br />
The block uses a number of capabilities that are added when the block is installed.<br />
[[Image:Progress_Bar_Capabilities.png|thumb|Global settings]]<br />
* ''Add a Progress Bar block to My home'' (block/progress:myaddinstance)<br>Controls whether the Progress Bar can be added by a user to the Dashboard (formerly My home) page. By default, this is allowed for all authenticated users.<br />
* ''Add a new Progress Bar block'' (block/progress:addinstance)<br>Controls whether the Progress Bar block can be added to a course page. By default, this is allowed for the following archetypal roles.<br />
** Teacher (editingteacher)<br />
** Manager (manager)<br />
** Course creator (coursecreator)<br />
** (and Admins)<br />
* ''View course overview of Progress bars for all students'' (block/progress:overview)<br>Controls whether the Overview page and the button on the Progress Bar block used to access the Overview page can be viewed by a user. By default, this is allowed for the following archetypal roles.<br />
** Non-editing teacher (teacher)<br />
** Teacher (editingteacher)<br />
** Manager (manager)<br />
** Course creator (coursecreator)<br />
** (and Admins)<br />
* ''Show the bar in the Progress Bar block'' (block/progress:showbar)<br>Controls whether the bar in the Progress Bar block is shown to a user. The reason for not showing this to certain users is that this might not be relevant and possibly annoying. By default, this is shown to the following archetypal roles.<br />
** Non-editing teacher (teacher)<br />
** Teacher (editingteacher)<br />
** Student (student)<br />
** (and Admins)<br />
<br />
== Setting up a Progress Bar in a course ==<br />
<br />
Once the progress bar is installed, you can use it in a course as follows.<br />
# Turn editing on<br />
# Create your activities/resources as normal<br />
# Add the Progress Bar block to your page ([[Blocks|How to add a block]])<br />
# Move your Progress Bar block into a prominent position (click and drag the block title)<br />
# Choose to:<br />
#* Monitor all activities (pre-fills configuration page)<br />
#* Select which activities to monitor (start from scratch)<br />
# Set the activities/resources you want shown in the block to "Yes" and those you don't to "No".<br />
# Set the date and time when the activity/resource is expected to be completed/viewed by (some activities have deadlines set, if so, that deadline can be used or another can be set in the Progress Bar block configuration).<br />
# Save changes.<br />
<br />
Hidden items will not appear in the Progress Bar until they are unhidden. This is useful for a scheduled release of activities.<br />
<br />
== Links ==<br />
<br />
* [http://moodle.org/plugins/view.php?plugin=block_progress Block code in Plugins repository]<br />
* [http://tracker.moodle.org/browse/CONTRIB/component/10489 Bug Tracker Page] (Please report bugs here.)<br />
* [https://github.com/deraadt/moodle-block_progress Git repository]<br />
<br />
==Available translations==<br />
This plugin has been (partly or completely) [https://docs.moodle.org/dev/Translation translated] in [http://lang.moodle.org/ AMOS] to these 24 languages by February 2016:<br />
* Basque (eu) <br />
* Catalan (ca) <br />
* Chinese (Traditional/Big5) (zh_tw)<br />
* Croatian (hr)<br />
* Czech (cs)<br />
* Dansk (da) <br />
* Dutch (nl) <br />
* Finnish (fi)<br />
* French (fr) <br />
* German (de) <br />
* Hebrew (he) <br />
* Japanese (ja) <br />
* Lietuvių (lt)<br />
* Macedonian (mk)<br />
* Mongolian (mn)<br />
* Norwegian (no)<br />
* Polish (pl)<br />
* Portuguese (Brazil) (pt_br)<br />
* Romanian (ro) <br />
* Russian (ru)<br />
* Serbian (Cyrillic) (sr_cr) <br />
* Serbian (Latin) (sr_lt)<br />
* Spanish (International) (es)<br />
* Spanish - Mexico (es_mx)<br />
<br />
The documentation (this page that you are reading now) is available in spanish at [https://docs.moodle.org/all/es/Bloque_de_barra_de_progreso Bloque de barra de progreso].<br />
<br />
== Acknowledgements ==<br />
<br />
* Thanks to:<br />
** Toshimi Hatanaka for contributing a Japanese translation<br />
** Yvonne Schneider and Joachim Vogelgesang for contributing a German translation<br />
** Maria João Spilker for contributing a Portuguese-Brazilian translation<br />
** Pieter Wolters for contributing a Dutch translation<br />
** Fernando Sánchez for contributing a Spanish translation<br />
** Fabien Sartoretti for contributing a French translation<br />
** Adam Levy for contributing queries and strings for Hot Potatoes support<br />
** Petras Virzintas for contributing queries for Turnitin support<br />
** Willian Mano for helping with the modern look CSS<br />
** Matthieu Rolland for contributing queries for the Questionnaire module<br />
** Johan Reinalda for contributing global config changes for block colours<br />
** German Valero for Spanish - Mexico translation of the block and this page.<br />
<br />
===Videos===<br />
<br />
<mediaplayer>http://www.youtube.com/watch?v=06LA5Cv9Fhw</mediaplayer><br />
<br />
<mediaplayer>http://www.youtube.com/watch?v=ekH8IfCyGzM</mediaplayer><br />
<br />
[[Category:Contributed code]]<br />
[[Category:Block]]<br />
<br />
[[es:Bloque de barra de progreso]]</div>Deraadthttps://docs.moodle.org/30/en/index.php?title=Learning_analytics&diff=122337Learning analytics2016-02-24T23:45:16Z<p>Deraadt: Adding Feedback and Questionnaire activities</p>
<hr />
<div>Learning Analytics are any piece of information that can help an LMS user improve learning outcomes. Users include students, teachers, administrators and decision-makers.<br />
<br />
== Moodle Plugins ==<br />
<br />
There are a number of reports, blocks and other plugins for Moodle that provide learning analytics.<br />
<br />
{| class="nicetable"<br />
|-<br />
! Plugin <br />
! Plugin type<br />
! Standard / Additional<br />
! Useful for<br />
! Reported usage*<br />
|-<br />
| [[:en:Logs|Logs]]<br />
| Report<br />
| Standard<br />
| Teachers, Admins, Decision-makers<br />
| style="text-align:center;" | 71.4%<br />
|-<br />
| [[:en:Activity_report|Activity]]<br />
| Report<br />
| Standard<br />
| Teachers<br />
| style="text-align:center;" | 69.1%<br />
|-<br />
| [[:en:Using_Activity_completion|Activity completion]]<br />
| Report<br />
| Standard<br />
| Teachers<br />
| style="text-align:center;" | 66.3%<br />
|-<br />
| [[:en:Logs|Live logs]]<br />
| Report<br />
| Standard<br />
| Teachers, Admins<br />
| style="text-align:center;" | 55.2% <br />
|-<br />
| [[:en:Feedback_activity|Feedback]]<br />
| Activity<br />
| Standard<br />
| Teachers, Researchers<br />
| style="text-align:center;" | 59.5% <br />
|-<br />
| [[:en:Quiz_statistics_report|(Quiz) Statistics]]<br />
| Report<br />
| Standard<br />
| Teachers<br />
| style="text-align:center;" | 53.0%<br />
|-<br />
| [[:en:Participation_report|(Course) Participation]]<br />
| Report<br />
| Standard<br />
| Teachers<br />
| style="text-align:center;" | 49.9%<br />
|-<br />
| [[:en:Survey_module|Survey]]<br />
| Activity<br />
| Standard<br />
| Teachers, Researchers<br />
| style="text-align:center;" | 45.6%<br />
|-<br />
| [http://moodle.org/plugins/view.php?plugin=mod_questionnaire Questionnaire]<br />
| Activity<br />
| Additional<br />
| Teachers, Researchers<br />
| style="text-align:center;" | 45.3%<br />
|-<br />
| [[:en:Course_overview_report|Course overview]]<br />
| Report<br />
| Standard<br />
| Admins, Decision-makers<br />
| style="text-align:center;" | 45.0%<br />
|-<br />
| [[:en:Course_completion_status_block|Course completion status]]<br />
| Block<br />
| Standard<br />
| Students<br />
| style="text-align:center;" | 41.4%<br />
|-<br />
| [http://moodle.org/plugins/view.php?plugin=block_progress Progress Bar]<br />
| Block<br />
| Additional<br />
| Students, Teachers<br />
| style="text-align:center;" | 32.0%<br />
|-<br />
| [[:en:Events_list_report|Events list]]<br />
| Report<br />
| Standard<br />
| Teachers, Admins<br />
| style="text-align:center;" | 28.6%<br />
|-<br />
| [[:en:Activity_results_block|Activity results block]]<br />
| Block<br />
| Standard<br />
| Students<br />
| style="text-align:center;" | 26.1%<br />
|-<br />
| [http://moodle.org/plugins/view.php?id=82 Configurable Reports] <br />
([https://docs.moodle.org/29/en/ad-hoc_contributed_reports A list of contributed reports])<br />
| Block ([https://github.com/nadavkav/moodle-report_configurablereports Report])<br />
| Additional<br />
| Teachers, Admins, Decision-makers<br />
| style="text-align:center;" | 22.7%<br />
|-<br />
| [[Overview_report|(Gradebook) Overview]]<br />
| Report<br />
| Standard<br />
| Teachers, Students<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/view/report_customsql Ad-hoc database queries]<br />
| Report<br />
| Additional<br />
| Teachers, Admins, Decision-makers<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/browse.php?list=set&id=20 Engagement Analytics]<br />
| Block, Report, Activity module<br />
| Additional<br />
| Teachers<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/view/block_dedication Course Dedication]<br />
| Block<br />
| Additional<br />
| Students, Teachers<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/view.php?plugin=block_graph_stats Graph Stats]<br />
| Block<br />
| Additional<br />
| Teachers, Admins<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/view/block_gismo GISMO, a graphical interactive student monitoring]<br />
| Block<br />
| Additional<br />
| Teachers<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/report_forumgraph Forum Graph]<br />
| Report<br />
| Additional<br />
| Teachers<br />
| style="text-align:center;" | N/A<br />
|}<br />
<br />
<nowiki>*</nowiki> Reported usage is drawn from the [http://research.moodle.net/71/1/Plugins%20Usage%20Survey%202015%20Report.pdf Plugins Usage Survey from 2015].<br />
<br />
== Integrations with Moodle ==<br />
<br />
A number of systems integrate with Moodle to provide learning analytics information.<br />
<br />
* [http://damos.world/2013/08/30/the-moodle-activity-viewer-mav-heatmaps-of-student-activity/ Moodle Activity Viewer] (MAV) ([https://github.com/damoclark/mav-enterprise Git])<br />
* [http://www.intelliboard.net/ Intelliboard]<br />
<br />
== Dimensions of Analytics ==<br />
<br />
Learning analytics are a concept that has been emerging under a number of different names through the past decades. Its origins lie in research in data mining and intelligent tutoring systems. LA tools can be categorised in a number of ways. The diagram below describes such tools by how deeply they are integrated with other systems ([http://www.netdimensions.com/downloads-2015/others/lms-evolution-or-extinction.pdf?mkt_tok=3RkMMJWWfF9wsRokuKjMZKXonjHpfsX56OQtW6CwlMI%2F0ER3fOvrPUfGjI4DTsdlI%2BSLDwEYGJlv6SgFS7fAMaFl3bgIWBY%3D source]).<br />
<br />
[[File:Learning-analytics.png]]<br />
<br />
== See also... ==<br />
* [https://moodle.org/mod/forum/view.php?id=8044 Analytics and reporting forum]<br />
* [https://moodle.org/mod/forum/view.php?id=8205 Moodle Research forum]<br />
* [[:dev:Moodle_research|Moodle research page]]<br />
* [[Logging]]<br />
* [[:dev:Learning_Analytics_Specification|Learning Analytics API specification]]<br />
* [[:dev:Working_Groups#Assessment_Analytics|Assessment Analytics working group details and issues]]<br />
* [[:dev:Event_2|Events specification]]<br />
* [[:dev:Logging_2|Logging specification]]<br />
* [[:dev:reportbuilder/API|Report Builder API specification]]<br />
<br />
[[Category:Report]]<br />
<br />
[[es:Análisis del aprendizaje]]</div>Deraadthttps://docs.moodle.org/30/en/index.php?title=Progress_Bar_block&diff=122333Progress Bar block2016-02-24T00:11:10Z<p>Deraadt: Adding global settings and capabilities</p>
<hr />
<div>{{Infobox plugin<br />
|type = Block, Progress bar <br />
|entry = https://moodle.org/plugins/view.php?plugin=block_progress<br />
|tracker = https://tracker.moodle.org/browse/CONTRIB/component/10489/?selectedTab=com.atlassian.jira.jira-projects-plugin:component-summary-panel<br />
|discussion = https://moodle.org/plugins/view.php?plugin=block_progress<br />
|maintainer = [[User:Michael de Raadt|Michael de Raadt]]<br />
|float = right<br />
}}<br />
[[Blocks|Back to Blocks page]]<br />
<br />
== Features ==<br />
<br />
[[Image:Bar_in_block_-_with_details.png|right|A progress bar for a student]]<br />
* The Progress Bar is a time-management tool for students.<br />
* It visually shows what activities/resources a student is supposed to interact with in a course.<br />
* It is colour coded so students can quickly see what they have and have not completed/viewed.<br />
* The teacher selects which pre-existing activities/resources are to be included in the Progress Bar and when they should be completed/viewed.<br />
* Ordering can be done by times/deadlines or by the ordering of activities in the course.<br />
* There is an overview page allowing teachers to see the progress of all students in a class, which is helpful for finding students at risk.<br />
* Adding the Progress Bar block to the [[Dashboard]] shows users a combined view of their progress on all courses (where the block is set up).<br />
[[Image:Overview_of_students.png|The overview page]]<br />
<br />
== Installation ==<br />
<br />
The Progress Bar block is added like other blocks ([[Installing_contributed_modules_or_plugins|How to install a block]]).<br />
<br />
== Global settings ==<br />
<br />
The Progress Bar block has a number of global settings that will be seen on installation and can be accessed later at Site administration > Plugins > Blocks > Progress Bar.<br />
[[Image:Progress_Bar_Global_settings.png|thumb|Global settings]]<br />
* ''Course name to show on Dashboard''<br>The block can be added to the dashboard and combines visible Progress Bar block content from the courses a user is enrolled in. By default, the course name shown for each relevant course, is the short course name, but some institutions/organisations may not think this is appropriate in relation to their course naming scheme, so a long course name can be selected.<br />
* ''Colours''<br>By default, the colours used in the block are red, blue and green. In certain cultures these colours may not have the same meaning. Also, institutions/organisations may wish to use colours that match their theme.<br />
* ''Show inactive students in Overview''<br>In most cases, inactive students are not wanted in course lists, such as the Overview page associated with the Progress Bar. However, in some cases, such as ongoing courses, inactive students might need to be visible on the Overview page.<br />
<br />
== Capabilities (Controlling who sees parts of the block) ==<br />
<br />
The block uses a number of capabilities that are added when the block is installed.<br />
[[Image:Progress_Bar_Capabilities.png|thumb|Global settings]]<br />
* ''Add a Progress Bar block to My home'' (block/progress:myaddinstance)<br>Controls whether the Progress Bar can be added by a user to the Dashboard (formerly My home) page. By default, this is allowed for all authenticated users.<br />
* ''Add a new Progress Bar block'' (block/progress:addinstance)<br>Controls whether the Progress Bar block can be added to a course page. By default, this is allowed for the following archetypal roles.<br />
** Teacher (editingteacher)<br />
** Manager (manager)<br />
** Course creator (coursecreator)<br />
** (and Admins)<br />
* ''View course overview of Progress bars for all students'' (block/progress:overview)<br>Controls whether the Overview page and the button on the Progress Bar block used to access the Overview page can be viewed by a user. By default, this is allowed for the following archetypal roles.<br />
** Non-editing teacher (teacher)<br />
** Teacher (editingteacher)<br />
** Manager (manager)<br />
** Course creator (coursecreator)<br />
** (and Admins)<br />
* ''Show the bar in the Progress Bar block'' (block/progress:showbar)<br>Controls whether the bar in the Progress Bar block is shown to a user. The reason for not showing this to certain users is that this might not be relevant and possibly annoying. By default, this is shown to the following archetypal roles.<br />
** Non-editing teacher (teacher)<br />
** Teacher (editingteacher)<br />
** Student (student)<br />
** (and Admins)<br />
<br />
== Setting up a Progress Bar in a course ==<br />
<br />
Once the progress bar is installed, you can use it in a course as follows.<br />
# Turn editing on<br />
# Create your activities/resources as normal<br />
# Add the Progress Bar block to your page ([[Blocks|How to add a block]])<br />
# Move your Progress Bar block into a prominent position (click and drag the block title)<br />
# Choose to:<br />
#* Monitor all activities (pre-fills configuration page)<br />
#* Select which activities to monitor (start from scratch)<br />
# Set the activities/resources you want shown in the block to "Yes" and those you don't to "No".<br />
# Set the date and time when the activity/resource is expected to be completed/viewed by (some activities have deadlines set, if so, that deadline can be used or another can be set in the Progress Bar block configuration).<br />
# Save changes.<br />
<br />
Hidden items will not appear in the Progress Bar until they are unhidden. This is useful for a scheduled release of activities.<br />
<br />
== Links ==<br />
<br />
* [http://moodle.org/plugins/view.php?plugin=block_progress Block code in Plugins repository]<br />
* [http://tracker.moodle.org/browse/CONTRIB/component/10489 Bug Tracker Page] (Please report bugs here)<br />
* [http://cvs.moodle.org/contrib/plugins/blocks/progress/ CVS Repository]<br />
<br />
==Available translations==<br />
This plugin has been (partly or completely) [https://docs.moodle.org/dev/Translation translated] in [http://lang.moodle.org/ AMOS] to these 14 languages by Sept 2014:<br />
* Basque (eu) <br />
* Chinese (Traditional/Big5) (zh_tw)<br />
* Dutch (nl) <br />
* Finnish (fi)<br />
* French (fr) <br />
* German (de) <br />
* Hebrew (he) <br />
* Japanese (ja) <br />
* Macedonian (mk)<br />
* Norwegian (no)<br />
* Portuguese (Brazil) (pt_br)<br />
* Russian (ru)<br />
* Spanish (International) (es)<br />
* Spanish - Mexico (es_mx)<br />
<br />
The documentation (this page that you are reading now) is available in spanish at [https://docs.moodle.org/all/es/Bloque_de_barra_de_progreso Bloque de barra de progreso].<br />
<br />
== Acknowledgements ==<br />
<br />
* Thanks to:<br />
** Toshimi Hatanaka for contributing a Japanese translation<br />
** Yvonne Schneider and Joachim Vogelgesang for contributing a German translation<br />
** Maria João Spilker for contributing a Portuguese-Brazilian translation<br />
** Pieter Wolters for contributing a Dutch translation<br />
** Fernando Sánchez for contributing a Spanish translation<br />
** Fabien Sartoretti for contributing a French translation<br />
** Adam Levy for contributing queries and strings for Hot Potatoes support<br />
** Petras Virzintas for contributing queries for Turnitin support<br />
** Willian Mano for helping with the modern look CSS<br />
** Matthieu Rolland for contributing queries for the Questionnaire module<br />
** Johan Reinalda for contributing global config changes for block colours<br />
** German Valero for Spanish - Mexico translation of the block and this page.<br />
<br />
===Videos===<br />
<br />
<mediaplayer>http://www.youtube.com/watch?v=06LA5Cv9Fhw</mediaplayer><br />
<br />
<mediaplayer>http://www.youtube.com/watch?v=ekH8IfCyGzM</mediaplayer><br />
<br />
[[Category:Contributed code]]<br />
[[Category:Block]]<br />
<br />
[[es:Bloque de barra de progreso]]</div>Deraadthttps://docs.moodle.org/30/en/index.php?title=Capabilities/block/progress:addinstance&diff=122332Capabilities/block/progress:addinstance2016-02-24T00:07:48Z<p>Deraadt: Created page with "This capability controls whether the Progress Bar block can be added to a course page. By default, this is allowed for the following archetypal roles. * Teacher (editingteac..."</p>
<hr />
<div>This capability controls whether the Progress Bar block can be added to a course page. <br />
<br />
By default, this is allowed for the following archetypal roles.<br />
* Teacher (editingteacher)<br />
* Manager (manager)<br />
* Course creator (coursecreator)<br />
* (and Admins)</div>Deraadthttps://docs.moodle.org/30/en/index.php?title=Capabilities/block/progress:overview&diff=122331Capabilities/block/progress:overview2016-02-24T00:07:45Z<p>Deraadt: Created page with "This capability controls whether the Overview page and the button on the Progress Bar block used to access the Overview page can be viewed by a user. By default, this is allo..."</p>
<hr />
<div>This capability controls whether the Overview page and the button on the Progress Bar block used to access the Overview page can be viewed by a user.<br />
<br />
By default, this is allowed for the following archetypal roles.<br />
* Non-editing teacher (teacher)<br />
* Teacher (editingteacher)<br />
* Manager (manager)<br />
* Course creator (coursecreator)<br />
* (and Admins)</div>Deraadthttps://docs.moodle.org/30/en/index.php?title=Capabilities/block/progress:showbar&diff=122330Capabilities/block/progress:showbar2016-02-24T00:07:42Z<p>Deraadt: Created page with "This capability controls whether the bar in the Progress Bar block is shown to a user. The reason for not showing this to certain users is that this might not be relevant and..."</p>
<hr />
<div>This capability controls whether the bar in the Progress Bar block is shown to a user.<br />
<br />
The reason for not showing this to certain users is that this might not be relevant and possibly annoying.<br />
<br />
By default, this is shown to the following archetypal roles.<br />
* Non-editing teacher (teacher)<br />
* Teacher (editingteacher)<br />
* Student (student)<br />
* (and Admins)</div>Deraadthttps://docs.moodle.org/30/en/index.php?title=Capabilities/block/progress:myaddinstance&diff=122329Capabilities/block/progress:myaddinstance2016-02-24T00:05:38Z<p>Deraadt: Created page with "This capability controls whether the Progress Bar can be added by a user to the Dashboard (formerly My home) page. By default, this is allowed for all authenticated users."</p>
<hr />
<div>This capability controls whether the Progress Bar can be added by a user to the Dashboard (formerly My home) page. By default, this is allowed for all authenticated users.</div>Deraadthttps://docs.moodle.org/30/en/index.php?title=File:Progress_Bar_Capabilities.png&diff=122328File:Progress Bar Capabilities.png2016-02-23T23:53:14Z<p>Deraadt: </p>
<hr />
<div></div>Deraadthttps://docs.moodle.org/30/en/index.php?title=File:Progress_Bar_Global_settings.png&diff=122327File:Progress Bar Global settings.png2016-02-23T23:36:48Z<p>Deraadt: </p>
<hr />
<div></div>Deraadthttps://docs.moodle.org/30/en/index.php?title=Moodle_research&diff=122150Moodle research2016-02-01T04:35:23Z<p>Deraadt: Redirecting to new Moodle research page on Dev docs. Papers listed have been copied to Moodle Research Library</p>
<hr />
<div>#REDIRECT [[:dev:Moodle_research]]</div>Deraadthttps://docs.moodle.org/30/en/index.php?title=Learning_analytics&diff=122149Learning analytics2016-02-01T04:22:46Z<p>Deraadt: Correcting Event 2 link</p>
<hr />
<div>Learning Analytics are any piece of information that can help an LMS user improve learning outcomes. Users include students, teachers, administrators and decision-makers.<br />
<br />
== Moodle Plugins ==<br />
<br />
There are a number of reports, blocks and other plugins for Moodle that provide learning analytics.<br />
<br />
{| class="nicetable"<br />
|-<br />
! Plugin <br />
! Plugin type<br />
! Standard / Additional<br />
! Useful for<br />
! Reported usage*<br />
|-<br />
| [[:en:Logs|Logs]]<br />
| Report<br />
| Standard<br />
| Teachers, Admins, Decision-makers<br />
| style="text-align:center;" | 71.4%<br />
|-<br />
| [[:en:Activity_report|Activity]]<br />
| Report<br />
| Standard<br />
| Teachers<br />
| style="text-align:center;" | 69.1%<br />
|-<br />
| [[:en:Using_Activity_completion|Activity completion]]<br />
| Report<br />
| Standard<br />
| Teachers<br />
| style="text-align:center;" | 66.3%<br />
|-<br />
| [[:en:Logs|Live logs]]<br />
| Report<br />
| Standard<br />
| Teachers, Admins<br />
| style="text-align:center;" | 55.2% <br />
|-<br />
| [[:en:Quiz_statistics_report|(Quiz) Statistics]]<br />
| Report<br />
| Standard<br />
| Teachers<br />
| style="text-align:center;" | 53.0%<br />
|-<br />
| [[:en:Participation_report|(Course) Participation]]<br />
| Report<br />
| Standard<br />
| Teachers<br />
| style="text-align:center;" | 49.9%<br />
|-<br />
| [[:en:Survey_module|Survey]]<br />
| Activity<br />
| Standard<br />
| Teachers<br />
| style="text-align:center;" | 45.6%<br />
|-<br />
| [[:en:Course_overview_report|Course overview]]<br />
| Report<br />
| Standard<br />
| Admins, Decision-makers<br />
| style="text-align:center;" | 45.0%<br />
|-<br />
| [[:en:Course_completion_status_block|Course completion status]]<br />
| Block<br />
| Standard<br />
| Students<br />
| style="text-align:center;" | 41.4%<br />
|-<br />
| [http://moodle.org/plugins/view.php?plugin=block_progress Progress Bar]<br />
| Block<br />
| Additional<br />
| Students, Teachers<br />
| style="text-align:center;" | 32.0%<br />
|-<br />
| [[:en:Events_list_report|Events list]]<br />
| Report<br />
| Standard<br />
| Teachers, Admins<br />
| style="text-align:center;" | 28.6%<br />
|-<br />
| [[:en:Activity_results_block|Activity results block]]<br />
| Block<br />
| Standard<br />
| Students<br />
| style="text-align:center;" | 26.1%<br />
|-<br />
| [http://moodle.org/plugins/view.php?id=82 Configurable Reports] <br />
([https://docs.moodle.org/29/en/ad-hoc_contributed_reports A list of contributed reports])<br />
| Block ([https://github.com/nadavkav/moodle-report_configurablereports Report])<br />
| Additional<br />
| Teachers, Admins, Decision-makers<br />
| style="text-align:center;" | 22.7%<br />
|-<br />
| [[Overview_report|(Gradebook) Overview]]<br />
| Report<br />
| Standard<br />
| Teachers, Students<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/view/report_customsql Ad-hoc database queries]<br />
| Report<br />
| Additional<br />
| Teachers, Admins, Decision-makers<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/browse.php?list=set&id=20 Engagement Analytics]<br />
| Block, Report, Activity module<br />
| Additional<br />
| Teachers<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/view/block_dedication Course Dedication]<br />
| Block<br />
| Additional<br />
| Students, Teachers<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/view.php?plugin=block_graph_stats Graph Stats]<br />
| Block<br />
| Additional<br />
| Teachers, Admins<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/view/block_gismo GISMO, a graphical interactive student monitoring]<br />
| Block<br />
| Additional<br />
| Teachers<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/report_forumgraph Forum Graph]<br />
| Report<br />
| Additional<br />
| Teachers<br />
| style="text-align:center;" | N/A<br />
|}<br />
<br />
<nowiki>*</nowiki> Reported usage is drawn from the [http://research.moodle.net/71/1/Plugins%20Usage%20Survey%202015%20Report.pdf Plugins Usage Survey from 2015].<br />
<br />
== Integrations with Moodle ==<br />
<br />
A number of systems integrate with Moodle to provide learning analytics information.<br />
<br />
* [http://damos.world/2013/08/30/the-moodle-activity-viewer-mav-heatmaps-of-student-activity/ Moodle Activity Viewer] (MAV) ([https://github.com/damoclark/mav-enterprise Git])<br />
* [http://www.intelliboard.net/ Intelliboard]<br />
<br />
== Dimensions of Analytics ==<br />
<br />
Learning analytics are a concept that has been emerging under a number of different names through the past decades. Its origins lie in research in data mining and intelligent tutoring systems. LA tools can be categorised in a number of ways. The diagram below describes such tools by how deeply they are integrated with other systems ([http://www.netdimensions.com/downloads-2015/others/lms-evolution-or-extinction.pdf?mkt_tok=3RkMMJWWfF9wsRokuKjMZKXonjHpfsX56OQtW6CwlMI%2F0ER3fOvrPUfGjI4DTsdlI%2BSLDwEYGJlv6SgFS7fAMaFl3bgIWBY%3D source]).<br />
<br />
[[File:Learning-analytics.png]]<br />
<br />
== See also... ==<br />
* [https://moodle.org/mod/forum/view.php?id=8044 Analytics and reporting forum]<br />
* [https://moodle.org/mod/forum/view.php?id=8205 Moodle Research forum]<br />
* [[:dev:Moodle_research|Moodle research page]]<br />
* [[Logging]]<br />
* [[:dev:Learning_Analytics_Specification|Learning Analytics API specification]]<br />
* [[:dev:Working_Groups#Assessment_Analytics|Assessment Analytics working group details and issues]]<br />
* [[:dev:Event_2|Events specification]]<br />
* [[:dev:Logging_2|Logging specification]]<br />
* [[:dev:reportbuilder/API|Report Builder API specification]]<br />
<br />
[[Category:Report]]<br />
<br />
[[es:Análisis del aprendizaje]]</div>Deraadthttps://docs.moodle.org/30/en/index.php?title=Learning_analytics&diff=122148Learning analytics2016-02-01T04:15:14Z<p>Deraadt: Adding some links</p>
<hr />
<div>Learning Analytics are any piece of information that can help an LMS user improve learning outcomes. Users include students, teachers, administrators and decision-makers.<br />
<br />
== Moodle Plugins ==<br />
<br />
There are a number of reports, blocks and other plugins for Moodle that provide learning analytics.<br />
<br />
{| class="nicetable"<br />
|-<br />
! Plugin <br />
! Plugin type<br />
! Standard / Additional<br />
! Useful for<br />
! Reported usage*<br />
|-<br />
| [[:en:Logs|Logs]]<br />
| Report<br />
| Standard<br />
| Teachers, Admins, Decision-makers<br />
| style="text-align:center;" | 71.4%<br />
|-<br />
| [[:en:Activity_report|Activity]]<br />
| Report<br />
| Standard<br />
| Teachers<br />
| style="text-align:center;" | 69.1%<br />
|-<br />
| [[:en:Using_Activity_completion|Activity completion]]<br />
| Report<br />
| Standard<br />
| Teachers<br />
| style="text-align:center;" | 66.3%<br />
|-<br />
| [[:en:Logs|Live logs]]<br />
| Report<br />
| Standard<br />
| Teachers, Admins<br />
| style="text-align:center;" | 55.2% <br />
|-<br />
| [[:en:Quiz_statistics_report|(Quiz) Statistics]]<br />
| Report<br />
| Standard<br />
| Teachers<br />
| style="text-align:center;" | 53.0%<br />
|-<br />
| [[:en:Participation_report|(Course) Participation]]<br />
| Report<br />
| Standard<br />
| Teachers<br />
| style="text-align:center;" | 49.9%<br />
|-<br />
| [[:en:Survey_module|Survey]]<br />
| Activity<br />
| Standard<br />
| Teachers<br />
| style="text-align:center;" | 45.6%<br />
|-<br />
| [[:en:Course_overview_report|Course overview]]<br />
| Report<br />
| Standard<br />
| Admins, Decision-makers<br />
| style="text-align:center;" | 45.0%<br />
|-<br />
| [[:en:Course_completion_status_block|Course completion status]]<br />
| Block<br />
| Standard<br />
| Students<br />
| style="text-align:center;" | 41.4%<br />
|-<br />
| [http://moodle.org/plugins/view.php?plugin=block_progress Progress Bar]<br />
| Block<br />
| Additional<br />
| Students, Teachers<br />
| style="text-align:center;" | 32.0%<br />
|-<br />
| [[:en:Events_list_report|Events list]]<br />
| Report<br />
| Standard<br />
| Teachers, Admins<br />
| style="text-align:center;" | 28.6%<br />
|-<br />
| [[:en:Activity_results_block|Activity results block]]<br />
| Block<br />
| Standard<br />
| Students<br />
| style="text-align:center;" | 26.1%<br />
|-<br />
| [http://moodle.org/plugins/view.php?id=82 Configurable Reports] <br />
([https://docs.moodle.org/29/en/ad-hoc_contributed_reports A list of contributed reports])<br />
| Block ([https://github.com/nadavkav/moodle-report_configurablereports Report])<br />
| Additional<br />
| Teachers, Admins, Decision-makers<br />
| style="text-align:center;" | 22.7%<br />
|-<br />
| [[Overview_report|(Gradebook) Overview]]<br />
| Report<br />
| Standard<br />
| Teachers, Students<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/view/report_customsql Ad-hoc database queries]<br />
| Report<br />
| Additional<br />
| Teachers, Admins, Decision-makers<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/browse.php?list=set&id=20 Engagement Analytics]<br />
| Block, Report, Activity module<br />
| Additional<br />
| Teachers<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/view/block_dedication Course Dedication]<br />
| Block<br />
| Additional<br />
| Students, Teachers<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/view.php?plugin=block_graph_stats Graph Stats]<br />
| Block<br />
| Additional<br />
| Teachers, Admins<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/view/block_gismo GISMO, a graphical interactive student monitoring]<br />
| Block<br />
| Additional<br />
| Teachers<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/report_forumgraph Forum Graph]<br />
| Report<br />
| Additional<br />
| Teachers<br />
| style="text-align:center;" | N/A<br />
|}<br />
<br />
<nowiki>*</nowiki> Reported usage is drawn from the [http://research.moodle.net/71/1/Plugins%20Usage%20Survey%202015%20Report.pdf Plugins Usage Survey from 2015].<br />
<br />
== Integrations with Moodle ==<br />
<br />
A number of systems integrate with Moodle to provide learning analytics information.<br />
<br />
* [http://damos.world/2013/08/30/the-moodle-activity-viewer-mav-heatmaps-of-student-activity/ Moodle Activity Viewer] (MAV) ([https://github.com/damoclark/mav-enterprise Git])<br />
* [http://www.intelliboard.net/ Intelliboard]<br />
<br />
== Dimensions of Analytics ==<br />
<br />
Learning analytics are a concept that has been emerging under a number of different names through the past decades. Its origins lie in research in data mining and intelligent tutoring systems. LA tools can be categorised in a number of ways. The diagram below describes such tools by how deeply they are integrated with other systems ([http://www.netdimensions.com/downloads-2015/others/lms-evolution-or-extinction.pdf?mkt_tok=3RkMMJWWfF9wsRokuKjMZKXonjHpfsX56OQtW6CwlMI%2F0ER3fOvrPUfGjI4DTsdlI%2BSLDwEYGJlv6SgFS7fAMaFl3bgIWBY%3D source]).<br />
<br />
[[File:Learning-analytics.png]]<br />
<br />
== See also... ==<br />
* [https://moodle.org/mod/forum/view.php?id=8044 Analytics and reporting forum]<br />
* [https://moodle.org/mod/forum/view.php?id=8205 Moodle Research forum]<br />
* [[:dev:Moodle_research|Moodle research page]]<br />
* [[Logging]]<br />
* [[:dev:Learning_Analytics_Specification|Learning Analytics API specification]]<br />
* [[:dev:Working_Groups#Assessment_Analytics|Assessment Analytics working group details and issues]]<br />
* [[:dev:Events_2|Events specification]]<br />
* [[:dev:Logging_2|Logging specification]]<br />
* [[:dev:reportbuilder/API|Report Builder API specification]]<br />
<br />
[[Category:Report]]<br />
<br />
[[es:Análisis del aprendizaje]]</div>Deraadthttps://docs.moodle.org/30/en/index.php?title=Learning_analytics&diff=121970Learning analytics2016-01-13T04:34:20Z<p>Deraadt: Adding link to assessment analytics work</p>
<hr />
<div>Learning Analytics are any piece of information that can help an LMS user improve learning outcomes. Users include students, teachers, administrators and decision-makers.<br />
<br />
== Moodle Plugins ==<br />
<br />
There are a number of reports, blocks and other plugins for Moodle that provide learning analytics.<br />
<br />
{| class="nicetable"<br />
|-<br />
! Plugin <br />
! Plugin type<br />
! Standard / Additional<br />
! Useful for<br />
! Reported usage*<br />
|-<br />
| [[:en:Logs|Logs]]<br />
| Report<br />
| Standard<br />
| Teachers, Admins, Decision-makers<br />
| style="text-align:center;" | 71.4%<br />
|-<br />
| [[:en:Activity_report|Activity]]<br />
| Report<br />
| Standard<br />
| Teachers<br />
| style="text-align:center;" | 69.1%<br />
|-<br />
| [[:en:Using_Activity_completion|Activity completion]]<br />
| Report<br />
| Standard<br />
| Teachers<br />
| style="text-align:center;" | 66.3%<br />
|-<br />
| [[:en:Logs|Live logs]]<br />
| Report<br />
| Standard<br />
| Teachers, Admins<br />
| style="text-align:center;" | 55.2% <br />
|-<br />
| [[:en:Quiz_statistics_report|(Quiz) Statistics]]<br />
| Report<br />
| Standard<br />
| Teachers<br />
| style="text-align:center;" | 53.0%<br />
|-<br />
| [[:en:Participation_report|(Course) Participation]]<br />
| Report<br />
| Standard<br />
| Teachers<br />
| style="text-align:center;" | 49.9%<br />
|-<br />
| [[:en:Survey_module|Survey]]<br />
| Activity<br />
| Standard<br />
| Teachers<br />
| style="text-align:center;" | 45.6%<br />
|-<br />
| [[:en:Course_overview_report|Course overview]]<br />
| Report<br />
| Standard<br />
| Admins, Decision-makers<br />
| style="text-align:center;" | 45.0%<br />
|-<br />
| [[:en:Course_completion_status_block|Course completion status]]<br />
| Block<br />
| Standard<br />
| Students<br />
| style="text-align:center;" | 41.4%<br />
|-<br />
| [http://moodle.org/plugins/view.php?plugin=block_progress Progress Bar]<br />
| Block<br />
| Additional<br />
| Students, Teachers<br />
| style="text-align:center;" | 32.0%<br />
|-<br />
| [[:en:Events_list_report|Events list]]<br />
| Report<br />
| Standard<br />
| Teachers, Admins<br />
| style="text-align:center;" | 28.6%<br />
|-<br />
| [[:en:Activity_results_block|Activity results block]]<br />
| Block<br />
| Standard<br />
| Students<br />
| style="text-align:center;" | 26.1%<br />
|-<br />
| [http://moodle.org/plugins/view.php?id=82 Configurable Reports] <br />
([https://docs.moodle.org/29/en/ad-hoc_contributed_reports A list of contributed reports])<br />
| Block ([https://github.com/nadavkav/moodle-report_configurablereports Report])<br />
| Additional<br />
| Teachers, Admins, Decision-makers<br />
| style="text-align:center;" | 22.7%<br />
|-<br />
| [[Overview_report|(Gradebook) Overview]]<br />
| Report<br />
| Standard<br />
| Teachers, Students<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/view/report_customsql Ad-hoc database queries]<br />
| Report<br />
| Additional<br />
| Teachers, Admins, Decision-makers<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/browse.php?list=set&id=20 Engagement Analytics]<br />
| Block, Report, Activity module<br />
| Additional<br />
| Teachers<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/view/block_dedication Course Dedication]<br />
| Block<br />
| Additional<br />
| Students, Teachers<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/view.php?plugin=block_graph_stats Graph Stats]<br />
| Block<br />
| Additional<br />
| Teachers, Admins<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/view/block_gismo GISMO, a graphical interactive student monitoring]<br />
| Block<br />
| Additional<br />
| Teachers<br />
| style="text-align:center;" | N/A<br />
|}<br />
<br />
<nowiki>*</nowiki> Reported usage is drawn from the [http://research.moodle.net/71/1/Plugins%20Usage%20Survey%202015%20Report.pdf Plugins Usage Survey from 2015].<br />
<br />
== Integrations with Moodle ==<br />
<br />
A number of systems integrate with Moodle to provide learning analytics information.<br />
<br />
* [http://damos.world/2013/08/30/the-moodle-activity-viewer-mav-heatmaps-of-student-activity/ Moodle Activity Viewer] (MAV) ([https://github.com/damoclark/mav-enterprise Git])<br />
* [http://www.intelliboard.net/ Intelliboard]<br />
<br />
== Dimensions of Analytics ==<br />
<br />
Learning analytics are a concept that has been emerging under a number of different names through the past decades. Its origins lie in research in data mining and intelligent tutoring systems. LA tools can be categorised in a number of ways. The diagram below describes such tools by how deeply they are integrated with other systems ([http://www.netdimensions.com/downloads-2015/others/lms-evolution-or-extinction.pdf?mkt_tok=3RkMMJWWfF9wsRokuKjMZKXonjHpfsX56OQtW6CwlMI%2F0ER3fOvrPUfGjI4DTsdlI%2BSLDwEYGJlv6SgFS7fAMaFl3bgIWBY%3D source]).<br />
<br />
[[File:Learning-analytics.png]]<br />
<br />
== See also... ==<br />
* [[Logging]]<br />
* [[:dev:Learning_Analytics_Specification|Learning Analytics API specification]]<br />
* [[:dev:Working_Groups#Assessment_Analytics|Assessment Analytics working group details and issues]]<br />
* [[:dev:Events_2|Events specification]]<br />
* [[:dev:Logging_2|Logging specification]]<br />
* [[:dev:reportbuilder/API|Report Builder API specification]]<br />
<br />
[[Category:Report]]<br />
<br />
[[es:Análisis del aprendizaje]]</div>Deraadthttps://docs.moodle.org/30/en/index.php?title=Learning_analytics&diff=121953Learning analytics2016-01-12T00:02:54Z<p>Deraadt: Adding learning analytics dimensions image</p>
<hr />
<div>Learning Analytics are any piece of information that can help an LMS user improve learning outcomes. Users include students, teachers, administrators and decision-makers.<br />
<br />
== Moodle Plugins ==<br />
<br />
There are a number of reports, blocks and other plugins for Moodle that provide learning analytics.<br />
<br />
{| class="nicetable"<br />
|-<br />
! Plugin <br />
! Plugin type<br />
! Standard / Additional<br />
! Useful for<br />
! Reported usage*<br />
|-<br />
| [[:en:Logs|Logs]]<br />
| Report<br />
| Standard<br />
| Teachers, Admins, Decision-makers<br />
| style="text-align:center;" | 71.4%<br />
|-<br />
| [[:en:Activity_report|Activity]]<br />
| Report<br />
| Standard<br />
| Teachers<br />
| style="text-align:center;" | 69.1%<br />
|-<br />
| [[:en:Using_Activity_completion|Activity completion]]<br />
| Report<br />
| Standard<br />
| Teachers<br />
| style="text-align:center;" | 66.3%<br />
|-<br />
| [[:en:Logs|Live logs]]<br />
| Report<br />
| Standard<br />
| Teachers, Admins<br />
| style="text-align:center;" | 55.2% <br />
|-<br />
| [[:en:Quiz_statistics_report|(Quiz) Statistics]]<br />
| Report<br />
| Standard<br />
| Teachers<br />
| style="text-align:center;" | 53.0%<br />
|-<br />
| [[:en:Participation_report|(Course) Participation]]<br />
| Report<br />
| Standard<br />
| Teachers<br />
| style="text-align:center;" | 49.9%<br />
|-<br />
| [[:en:Survey_module|Survey]]<br />
| Activity<br />
| Standard<br />
| Teachers<br />
| style="text-align:center;" | 45.6%<br />
|-<br />
| [[:en:Course_overview_report|Course overview]]<br />
| Report<br />
| Standard<br />
| Admins, Decision-makers<br />
| style="text-align:center;" | 45.0%<br />
|-<br />
| [[:en:Course_completion_status_block|Course completion status]]<br />
| Block<br />
| Standard<br />
| Students<br />
| style="text-align:center;" | 41.4%<br />
|-<br />
| [http://moodle.org/plugins/view.php?plugin=block_progress Progress Bar]<br />
| Block<br />
| Additional<br />
| Students, Teachers<br />
| style="text-align:center;" | 32.0%<br />
|-<br />
| [[:en:Events_list_report|Events list]]<br />
| Report<br />
| Standard<br />
| Teachers, Admins<br />
| style="text-align:center;" | 28.6%<br />
|-<br />
| [[:en:Activity_results_block|Activity results block]]<br />
| Block<br />
| Standard<br />
| Students<br />
| style="text-align:center;" | 26.1%<br />
|-<br />
| [http://moodle.org/plugins/view.php?id=82 Configurable Reports] <br />
([https://docs.moodle.org/29/en/ad-hoc_contributed_reports A list of contributed reports])<br />
| Block ([https://github.com/nadavkav/moodle-report_configurablereports Report])<br />
| Additional<br />
| Teachers, Admins, Decision-makers<br />
| style="text-align:center;" | 22.7%<br />
|-<br />
| [[Overview_report|(Gradebook) Overview]]<br />
| Report<br />
| Standard<br />
| Teachers, Students<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/view/report_customsql Ad-hoc database queries]<br />
| Report<br />
| Additional<br />
| Teachers, Admins, Decision-makers<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/browse.php?list=set&id=20 Engagement Analytics]<br />
| Block, Report, Activity module<br />
| Additional<br />
| Teachers<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/view/block_dedication Course Dedication]<br />
| Block<br />
| Additional<br />
| Students, Teachers<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/view.php?plugin=block_graph_stats Graph Stats]<br />
| Block<br />
| Additional<br />
| Teachers, Admins<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/view/block_gismo GISMO, a graphical interactive student monitoring]<br />
| Block<br />
| Additional<br />
| Teachers<br />
| style="text-align:center;" | N/A<br />
|}<br />
<br />
<nowiki>*</nowiki> Reported usage is drawn from the [http://research.moodle.net/71/1/Plugins%20Usage%20Survey%202015%20Report.pdf Plugins Usage Survey from 2015].<br />
<br />
== Integrations with Moodle ==<br />
<br />
A number of systems integrate with Moodle to provide learning analytics information.<br />
<br />
* [http://damos.world/2013/08/30/the-moodle-activity-viewer-mav-heatmaps-of-student-activity/ Moodle Activity Viewer] (MAV) ([https://github.com/damoclark/mav-enterprise Git])<br />
* [http://www.intelliboard.net/ Intelliboard]<br />
<br />
== Dimensions of Analytics ==<br />
<br />
Learning analytics are a concept that has been emerging under a number of different names through the past decades. Its origins lie in research in data mining and intelligent tutoring systems. LA tools can be categorised in a number of ways. The diagram below describes such tools by how deeply they are integrated with other systems ([http://www.netdimensions.com/downloads-2015/others/lms-evolution-or-extinction.pdf?mkt_tok=3RkMMJWWfF9wsRokuKjMZKXonjHpfsX56OQtW6CwlMI%2F0ER3fOvrPUfGjI4DTsdlI%2BSLDwEYGJlv6SgFS7fAMaFl3bgIWBY%3D source]).<br />
<br />
[[File:Learning-analytics.png]]<br />
<br />
== See also... ==<br />
* [[Logging]]<br />
* [[:dev:Learning_Analytics_Specification|Learning Analytics API specification]]<br />
* [[:dev:Events_2|Events specification]]<br />
* [[:dev:Logging_2|Logging specification]]<br />
* [[:dev:reportbuilder/API|Report Builder API specification]]<br />
<br />
[[Category:Report]]<br />
<br />
[[es:Análisis del aprendizaje]]</div>Deraadthttps://docs.moodle.org/30/en/index.php?title=File:Learning-analytics.png&diff=121952File:Learning-analytics.png2016-01-11T23:57:39Z<p>Deraadt: </p>
<hr />
<div></div>Deraadthttps://docs.moodle.org/30/en/index.php?title=Learning_analytics&diff=120976Learning analytics2015-11-03T01:24:23Z<p>Deraadt: Adding Git link for MAV</p>
<hr />
<div>Learning Analytics are any piece of information that can help an LMS user improve learning outcomes. Users include students, teachers, administrators and decision-makers.<br />
<br />
== Moodle Plugins ==<br />
<br />
There are a number of reports, blocks and other plugins for Moodle that provide learning analytics.<br />
<br />
{| class="nicetable"<br />
|-<br />
! Plugin <br />
! Plugin type<br />
! Standard / Additional<br />
! Useful for<br />
! Reported usage*<br />
|-<br />
| [[:en:Logs|Logs]]<br />
| Report<br />
| Standard<br />
| Teachers, Admins, Decision-makers<br />
| style="text-align:center;" | 71.4%<br />
|-<br />
| [[:en:Activity_report|Activity]]<br />
| Report<br />
| Standard<br />
| Teachers<br />
| style="text-align:center;" | 69.1%<br />
|-<br />
| [[:en:Using_Activity_completion|Activity completion]]<br />
| Report<br />
| Standard<br />
| Teachers<br />
| style="text-align:center;" | 66.3%<br />
|-<br />
| [[:en:Logs|Live logs]]<br />
| Report<br />
| Standard<br />
| Teachers, Admins<br />
| style="text-align:center;" | 55.2% <br />
|-<br />
| [[:en:Quiz_statistics_report|(Quiz) Statistics]]<br />
| Report<br />
| Standard<br />
| Teachers<br />
| style="text-align:center;" | 53.0%<br />
|-<br />
| [[:en:Participation_report|(Course) Participation]]<br />
| Report<br />
| Standard<br />
| Teachers<br />
| style="text-align:center;" | 49.9%<br />
|-<br />
| [[:en:Survey_module|Survey]]<br />
| Activity<br />
| Standard<br />
| Teachers<br />
| style="text-align:center;" | 45.6%<br />
|-<br />
| [[:en:Course_overview_report|Course overview]]<br />
| Report<br />
| Standard<br />
| Admins, Decision-makers<br />
| style="text-align:center;" | 45.0%<br />
|-<br />
| [[:en:Course_completion_status_block|Course completion status]]<br />
| Block<br />
| Standard<br />
| Students<br />
| style="text-align:center;" | 41.4%<br />
|-<br />
| [http://moodle.org/plugins/view.php?plugin=block_progress Progress Bar]<br />
| Block<br />
| Additional<br />
| Students, Teachers<br />
| style="text-align:center;" | 32.0%<br />
|-<br />
| [[:en:Events_list_report|Events list]]<br />
| Report<br />
| Standard<br />
| Teachers, Admins<br />
| style="text-align:center;" | 28.6%<br />
|-<br />
| [[:en:Activity_results_block|Activity results block]]<br />
| Block<br />
| Standard<br />
| Students<br />
| style="text-align:center;" | 26.1%<br />
|-<br />
| [http://moodle.org/plugins/view.php?id=82 Configurable Reports]<br />
| Block ([https://github.com/nadavkav/moodle-report_configurablereports Report])<br />
| Additional<br />
| Teachers, Admins, Decision-makers<br />
| style="text-align:center;" | 22.7%<br />
|-<br />
| [[Overview_report|(Gradebook) Overview]]<br />
| Report<br />
| Standard<br />
| Teachers, Students<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/view/report_customsql Ad-hoc database queries]<br />
| Report<br />
| Additional<br />
| Teachers, Admins, Decision-makers<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/browse.php?list=set&id=20 Engagement Analytics]<br />
| Block, Report, Activity module<br />
| Additional<br />
| Teachers<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/view/block_dedication Course Dedication]<br />
| Block<br />
| Additional<br />
| Students, Teachers<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/view.php?plugin=block_graph_stats Graph Stats]<br />
| Block<br />
| Additional<br />
| Teachers, Admins<br />
| style="text-align:center;" | N/A<br />
|}<br />
<br />
<nowiki>*</nowiki> Reported usage is drawn from the [http://research.moodle.net/71/1/Plugins%20Usage%20Survey%202015%20Report.pdf Plugins Usage Survey from 2015].<br />
<br />
== Integrations with Moodle ==<br />
<br />
A number of systems integrate with Moodle to provide learning analytics information.<br />
<br />
* [http://damos.world/2013/08/30/the-moodle-activity-viewer-mav-heatmaps-of-student-activity/ Moodle Activity Viewer] (MAV) ([https://github.com/damoclark/mav-enterprise Git])<br />
* [http://www.intelliboard.net/ Intelliboard]<br />
<br />
== See also... ==<br />
* [[Logging]]<br />
* [[:dev:Learning_Analytics_Specification|Learning Analytics API specification]]<br />
* [[:dev:Events_2|Events specification]]<br />
* [[:dev:Logging_2|Logging specification]]<br />
* [[:dev:reportbuilder/API|Report Builder API specification]]<br />
<br />
[[Category:Report]]<br />
<br />
[[es:Análisis del aprendizaje]]</div>Deraadthttps://docs.moodle.org/30/en/index.php?title=Learning_analytics&diff=120911Learning analytics2015-10-30T03:14:57Z<p>Deraadt: Adding external integrations</p>
<hr />
<div>Learning Analytics are any piece of information that can help an LMS user improve learning outcomes. Users include students, teachers, administrators and decision-makers.<br />
<br />
== Moodle Plugins ==<br />
<br />
There are a number of reports, blocks and other plugins for Moodle that provide learning analytics.<br />
<br />
{| class="nicetable"<br />
|-<br />
! Plugin <br />
! Plugin type<br />
! Standard / Additional<br />
! Useful for<br />
! Reported usage*<br />
|-<br />
| [[:en:Logs|Logs]]<br />
| Report<br />
| Standard<br />
| Teachers, Admins, Decision-makers<br />
| style="text-align:center;" | 71.4%<br />
|-<br />
| [[:en:Activity_report|Activity]]<br />
| Report<br />
| Standard<br />
| Teachers<br />
| style="text-align:center;" | 69.1%<br />
|-<br />
| [[:en:Using_Activity_completion|Activity completion]]<br />
| Report<br />
| Standard<br />
| Teachers<br />
| style="text-align:center;" | 66.3%<br />
|-<br />
| [[:en:Logs|Live logs]]<br />
| Report<br />
| Standard<br />
| Teachers, Admins<br />
| style="text-align:center;" | 55.2% <br />
|-<br />
| [[:en:Quiz_statistics_report|(Quiz) Statistics]]<br />
| Report<br />
| Standard<br />
| Teachers<br />
| style="text-align:center;" | 53.0%<br />
|-<br />
| [[:en:Participation_report|(Course) Participation]]<br />
| Report<br />
| Standard<br />
| Teachers<br />
| style="text-align:center;" | 49.9%<br />
|-<br />
| [[:en:Survey_module|Survey]]<br />
| Activity<br />
| Standard<br />
| Teachers<br />
| style="text-align:center;" | 45.6%<br />
|-<br />
| [[:en:Course_overview_report|Course overview]]<br />
| Report<br />
| Standard<br />
| Admins, Decision-makers<br />
| style="text-align:center;" | 45.0%<br />
|-<br />
| [[:en:Course_completion_status_block|Course completion status]]<br />
| Block<br />
| Standard<br />
| Students<br />
| style="text-align:center;" | 41.4%<br />
|-<br />
| [http://moodle.org/plugins/view.php?plugin=block_progress Progress Bar]<br />
| Block<br />
| Additional<br />
| Students, Teachers<br />
| style="text-align:center;" | 32.0%<br />
|-<br />
| [[:en:Events_list_report|Events list]]<br />
| Report<br />
| Standard<br />
| Teachers, Admins<br />
| style="text-align:center;" | 28.6%<br />
|-<br />
| [[:en:Activity_results_block|Activity results block]]<br />
| Block<br />
| Standard<br />
| Students<br />
| style="text-align:center;" | 26.1%<br />
|-<br />
| [http://moodle.org/plugins/view.php?id=82 Configurable Reports]<br />
| Block ([https://github.com/nadavkav/moodle-report_configurablereports Report])<br />
| Additional<br />
| Teachers, Admins, Decision-makers<br />
| style="text-align:center;" | 22.7%<br />
|-<br />
| [[Overview_report|(Gradebook) Overview]]<br />
| Report<br />
| Standard<br />
| Teachers, Students<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/view/report_customsql Ad-hoc database queries]<br />
| Report<br />
| Additional<br />
| Teachers, Admins, Decision-makers<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/browse.php?list=set&id=20 Engagement Analytics]<br />
| Block, Report, Activity module<br />
| Additional<br />
| Teachers<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/view/block_dedication Course Dedication]<br />
| Block<br />
| Additional<br />
| Students, Teachers<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/view.php?plugin=block_graph_stats Graph Stats]<br />
| Block<br />
| Additional<br />
| Teachers, Admins<br />
| style="text-align:center;" | N/A<br />
|}<br />
<br />
<nowiki>*</nowiki> Reported usage is drawn from the [http://research.moodle.net/71/1/Plugins%20Usage%20Survey%202015%20Report.pdf Plugins Usage Survey from 2015].<br />
<br />
== Integrations with Moodle ==<br />
<br />
A number of systems integrate with Moodle to provide learning analytics information.<br />
<br />
* [http://damos.world/2013/08/30/the-moodle-activity-viewer-mav-heatmaps-of-student-activity/ Moodle Activity Viewer] (MAV)<br />
* [http://www.intelliboard.net/ Intelliboard]<br />
<br />
== See also... ==<br />
* [[Logging]]<br />
* [[:dev:Learning_Analytics_Specification|Learning Analytics API specification]]<br />
* [[:dev:Events_2|Events specification]]<br />
* [[:dev:Logging_2|Logging specification]]<br />
* [[:dev:reportbuilder/API|Report Builder API specification]]<br />
<br />
[[Category:Report]]<br />
<br />
[[es:Análisis del aprendizaje]]</div>Deraadthttps://docs.moodle.org/30/en/index.php?title=Statistics&diff=115576Statistics2014-10-28T03:29:11Z<p>Deraadt: Updating instructions for forcing statistics generation in 2.7 onwards.</p>
<hr />
<div>{{Course reports}}<br />
If statistics are enabled for the site, graphs and tables of user activity may be generated.<br />
<br />
[[File:Statistics.png]]<br />
<br />
The statistics graphs and tables show how many '''hits''' there have been on various parts of your site during various time frames. They '''do not''' show how many distinct users there have been. They are processed daily at a time you specify. You must enable statistics before you will see anything.<br />
<br />
==Enabling statistics==<br />
<br />
Statistics must be enabled by a site administrator in ''Administration > Site administration > Advanced features''.<br />
<br />
In Moodle 2.4.2 onwards, once statistics have been enabled, the screen to configure them becomes visible as a link in ''Administration > Site administration > Server > Statistics''. (In older versions the link was always available irrespective of whether statistics was enabled.) <br />
<br />
The Course overview report will also then be accessible from ''Administration> Site administration > Reports''.<br />
<br />
==Site administration settings==<br />
<br />
Various settings for statistics may be set by an administrator in ''Administration > Site administration > Server > Statistics''.<br />
<br />
As stats processing is quite resource intensive, it is recommended that you should set the stats processing to start in the early morning.<br />
<br />
:''TIP:'' Set the stats processing to start an hour before your automated course backups are scheduled to start, then set the maximum runtime to 1 hour. This ensures that stats are not being processed at the same time as course backups are being made.<br />
<br />
==Statistics not working?==<br />
<br />
If statistics isn't working and you have checked all the obvious (such as whether it's enabled), check ''Settings > Site administration > Plugins > Activity modules'' for any old hidden modules in the database which miss the files in the ''moodle/mod'' folder on your server. If you find any, they should be deleted.<br />
<br />
You can also try limiting the length of time logs are kept for to reduce the size of the tables. Go to ''Settings > Site administration > Server > Cleanup'' to set this.<br />
<br />
To run stats manually, go to the database, go to the mdl_config table and set statslastdaily, statslastweekly and statslastmonthly to 0 (leave statslastmonthly alone if you think it might be large logtables causing the problem). Then go to ''Settings > Site administration > Server > Scheduled tasks'' and look for the task "Background processing for statistics"; set this to be a minute or two into the future by adjusting the hour and minute values. If you manually run cron, you should see output there showing that stats are processing, but be patient if it appears to hang - this can take between 5 mins and several hours depending on how big your site is, so just leave it going. Afterwards, you might want to return the Scheduled task's values back to asterisks so that it returns to the defined schedule.<br />
<br />
==Viewing statistics==<br />
<br />
A manager, teacher or non-editing teacher (or any other user with the capability [[Capabilities/report/stats:view|report/stats:view]]) can view statistics for their course in ''Administration > Course administration > Reports > Statistics''. <br />
<br />
An administrator can view statistics for the site in ''Administration > Site administration > Reports > Statistics''. <br />
<br />
[[Category:Site administration]]<br />
<br />
<br />
[[de:Statistiken]]<br />
[[es:Estadísticas]]<br />
[[fr:Statistiques]]</div>Deraadthttps://docs.moodle.org/30/en/index.php?title=Progress_Bar_block&diff=113973Progress Bar block2014-08-04T03:23:02Z<p>Deraadt: Adding My home feature</p>
<hr />
<div>{{Infobox plugin<br />
|type = Block, Progress bar <br />
|entry = https://moodle.org/plugins/view.php?plugin=block_progress<br />
|tracker = https://tracker.moodle.org/browse/CONTRIB/component/10489/?selectedTab=com.atlassian.jira.jira-projects-plugin:component-summary-panel<br />
|discussion = https://moodle.org/plugins/view.php?plugin=block_progress<br />
|maintainer = [[User:Michael de Raadt|Michael de Raadt]]<br />
|float = right<br />
}}<br />
[[Blocks|Back to Blocks page]]<br />
<br />
== Features ==<br />
<br />
[[Image:Bar_in_block_-_with_details.png|right|A progress bar for a student]]<br />
* The Progress Bar is a time-management tool for students.<br />
* It visually shows what activities/resources a student is supposed to interact with in a course.<br />
* It is colour coded so students can quickly see what they have and have not completed/viewed.<br />
* The teacher selects which pre-existing activities/resources are to be included in the Progress Bar and when they should be completed/viewed.<br />
* Ordering can be done by times/deadlines or by the ordering of activities in the course.<br />
[[Image:Overview_of_students.png|thumb|right|The overview page]]<br />
* There is an overview page allowing teachers to see the progress of all students in a class, which is helpful for finding students at risk.<br />
* Adding the Progress Bar block to the My home page shows users a combined view of their progress on all courses (where the block is set up).<br />
<br />
<mediaplayer>http://www.youtube.com/watch?v=06LA5Cv9Fhw</mediaplayer><br />
<br />
== Installation ==<br />
<br />
The Progress Bar block is added like other blocks ([[Installing_contributed_modules_or_plugins|How to install a block]]).<br />
<br />
== Setting up a Progress Bar ==<br />
<br />
Once the progress bar is installed, you can use it in a course as follows.<br />
# Turn editing on<br />
# Create your activities/resources as normal<br />
# Add the Progress Bar block to your page ([[Blocks|How to add a block]])<br />
# Move your Progress Bar block into a prominent position (click and drag the block title)<br />
# Choose to:<br />
#* Monitor all activities (pre-fills configuration page)<br />
#* Select which activities to monitor (start from scratch)<br />
# Set the activities/resources you want shown in the block to "Yes" and those you don't to "No".<br />
# Set the date and time when the activity/resource is expected to be completed/viewed by (some activities have deadlines set, if so, that deadline can be used or another can be set in the Progress Bar block configuration).<br />
# Save changes.<br />
<br />
<mediaplayer>http://www.youtube.com/watch?v=ekH8IfCyGzM</mediaplayer><br />
<br />
Hidden items will not appear in the Progress Bar until they are unhidden. This is useful for a scheduled release of activities.<br />
<br />
== Links ==<br />
<br />
* [http://moodle.org/plugins/view.php?plugin=block_progress Block code in Plugins repository]<br />
* [http://tracker.moodle.org/browse/CONTRIB/component/10489 Bug Tracker Page] (Please report bugs here)<br />
* [http://cvs.moodle.org/contrib/plugins/blocks/progress/ CVS Repository]<br />
<br />
==Available translations==<br />
This plugin has been (partly or completely) [https://docs.moodle.org/dev/Translation translated] in [http://lang.moodle.org/ AMOS] to these 14 languages by Sept 2014:<br />
* Basque (eu) <br />
* Chinese (Traditional/Big5) (zh_tw)<br />
* Dutch (nl) <br />
* Finnish (fi)<br />
* French (fr) <br />
* German (de) <br />
* Hebrew (he) <br />
* Japanese (ja) <br />
* Macedonian (mk)<br />
* Norwegian (no)<br />
* Portuguese (Brazil) (pt_br)<br />
* Russian (ru)<br />
* Spanish (International) (es)<br />
* Spanish - Mexico (es_mx)<br />
<br />
The documentation (this page that you are reading now) is available in spanish at [https://docs.moodle.org/all/es/Bloque_de_barra_de_progreso Bloque de barra de progreso].<br />
<br />
== Acknowledgements ==<br />
<br />
* Thanks to:<br />
** Toshimi Hatanaka for contributing a Japanese translation<br />
** Yvonne Schneider and Joachim Vogelgesang for contributing a German translation<br />
** Maria João Spilker for contributing a Portuguese-Brazilian translation<br />
** Pieter Wolters for contributing a Dutch translation<br />
** Fernando Sánchez for contributing a Spanish translation<br />
** Fabien Sartoretti for contributing a French translation<br />
** Adam Levy for contributing queries and strings for Hot Potatoes support<br />
** Petras Virzintas for contributing queries for Turnitin support<br />
** Willian Mano for helping with the modern look CSS<br />
** Matthieu Rolland for contributing queries for the Questionnaire module<br />
** Johan Reinalda for contributing global config changes for block colours<br />
** German Valero for Spanish - Mexico translation of the block and this page.<br />
<br />
[[Category:Contributed code]]<br />
[[Category:Block]]<br />
<br />
[[es:Bloque de barra de progreso]]</div>Deraadthttps://docs.moodle.org/30/en/index.php?title=Progress_Bar_block&diff=113972Progress Bar block2014-08-04T01:49:54Z<p>Deraadt: Adding German to Acknowledgements.</p>
<hr />
<div>{{Infobox plugin<br />
|type = Block, Progress bar <br />
|entry = https://moodle.org/plugins/view.php?plugin=block_progress<br />
|tracker = https://tracker.moodle.org/browse/CONTRIB/component/10489/?selectedTab=com.atlassian.jira.jira-projects-plugin:component-summary-panel<br />
|discussion = https://moodle.org/plugins/view.php?plugin=block_progress<br />
|maintainer = [[User:Michael de Raadt|Michael de Raadt]]<br />
|float = right<br />
}}<br />
[[Blocks|Back to Blocks page]]<br />
<br />
== Features ==<br />
<br />
[[Image:Bar_in_block_-_with_details.png|right|A progress bar for a student]]<br />
* The Progress Bar is a time-management tool for students.<br />
* It visually shows what activities/resources a student is supposed to interact with in a course.<br />
* It is colour coded so students can quickly see what they have and have not completed/viewed.<br />
* The teacher selects which pre-existing activities/resources are to be included in the Progress Bar and when they should be completed/viewed.<br />
* Ordering can be done by times/deadlines or by the ordering of activities in the course.<br />
[[Image:Overview_of_students.png|thumb|right|The overview page]]<br />
* There is an overview page allowing teachers to see the progress of all students in a class, which is helpful for finding students at risk.<br />
<br />
<mediaplayer>http://www.youtube.com/watch?v=06LA5Cv9Fhw</mediaplayer><br />
<br />
== Installation ==<br />
<br />
The Progress Bar block is added like other blocks ([[Installing_contributed_modules_or_plugins|How to install a block]]).<br />
<br />
== Setting up a Progress Bar ==<br />
<br />
Once the progress bar is installed, you can use it in a course as follows.<br />
# Turn editing on<br />
# Create your activities/resources as normal<br />
# Add the Progress Bar block to your page ([[Blocks|How to add a block]])<br />
# Move your Progress Bar block into a prominent position (click and drag the block title)<br />
# Choose to:<br />
#* Monitor all activities (pre-fills configuration page)<br />
#* Select which activities to monitor (start from scratch)<br />
# Set the activities/resources you want shown in the block to "Yes" and those you don't to "No".<br />
# Set the date and time when the activity/resource is expected to be completed/viewed by (some activities have deadlines set, if so, that deadline can be used or another can be set in the Progress Bar block configuration).<br />
# Save changes.<br />
<br />
<mediaplayer>http://www.youtube.com/watch?v=ekH8IfCyGzM</mediaplayer><br />
<br />
Hidden items will not appear in the Progress Bar until they are unhidden. This is useful for a scheduled release of activities.<br />
<br />
== Links ==<br />
<br />
* [http://moodle.org/plugins/view.php?plugin=block_progress Block code in Plugins repository]<br />
* [http://tracker.moodle.org/browse/CONTRIB/component/10489 Bug Tracker Page] (Please report bugs here)<br />
* [http://cvs.moodle.org/contrib/plugins/blocks/progress/ CVS Repository]<br />
<br />
==Available translations==<br />
This plugin has been (partly or completely) [https://docs.moodle.org/dev/Translation translated] in [http://lang.moodle.org/ AMOS] to these 14 languages by Sept 2014:<br />
* Basque (eu) <br />
* Chinese (Traditional/Big5) (zh_tw)<br />
* Dutch (nl) <br />
* Finnish (fi)<br />
* French (fr) <br />
* German (de) <br />
* Hebrew (he) <br />
* Japanese (ja) <br />
* Macedonian (mk)<br />
* Norwegian (no)<br />
* Portuguese (Brazil) (pt_br)<br />
* Russian (ru)<br />
* Spanish (International) (es)<br />
* Spanish - Mexico (es_mx)<br />
<br />
The documentation (this page that you are reading now) is available in spanish at [https://docs.moodle.org/all/es/Bloque_de_barra_de_progreso Bloque de barra de progreso].<br />
<br />
== Acknowledgements ==<br />
<br />
* Thanks to:<br />
** Toshimi Hatanaka for contributing a Japanese translation<br />
** Yvonne Schneider and Joachim Vogelgesang for contributing a German translation<br />
** Maria João Spilker for contributing a Portuguese-Brazilian translation<br />
** Pieter Wolters for contributing a Dutch translation<br />
** Fernando Sánchez for contributing a Spanish translation<br />
** Fabien Sartoretti for contributing a French translation<br />
** Adam Levy for contributing queries and strings for Hot Potatoes support<br />
** Petras Virzintas for contributing queries for Turnitin support<br />
** Willian Mano for helping with the modern look CSS<br />
** Matthieu Rolland for contributing queries for the Questionnaire module<br />
** Johan Reinalda for contributing global config changes for block colours<br />
** German Valero for Spanish - Mexico translation of the block and this page.<br />
<br />
[[Category:Contributed code]]<br />
[[Category:Block]]<br />
<br />
[[es:Bloque de barra de progreso]]</div>Deraadthttps://docs.moodle.org/30/en/index.php?title=Accessibility&diff=113561Accessibility2014-07-10T04:20:50Z<p>Deraadt: Adding some more info and links</p>
<hr />
<div>{{About Moodle}}<br />
<br />
Moodle's goal is to be fully accessible and usable for all users regardless of ability.<br />
<br />
This page describes the current state of accessibility in Moodle as well as our plans for the future.<br />
<br />
== Established practices ==<br />
<br />
Moodle core developers spend a lot of time making sure new developments are accessible. Part of the process when building new code in Moodle is to follow established best practices and part of the process for accepting new code into core is to test pages carefully and gather feedback from experts.<br />
<br />
== Screen-reader support ==<br />
<br />
From Moodle 2.7 onwards, [[:dev:Moodle_2.7_release_notes#Screen_reader_support|supported screen-reader/browser configurations]] are described in release notes.<br />
<br />
== Conformance to standards ==<br />
<br />
The Moodle platform is a complex system with many parts. Its code is always evolving. Modules can be enabled and disabled. The interface can be heavily customised using themes and thousands of settings. Actual content can be produced by any teacher or any student. As such it is impossible to say with 100% certainty whether Moodle or any site based on Moodle is absolutely accessible or not. Accessibility is not a state, it is a process of continuous improvement in response to our users and the wider technical environment.<br />
<br />
=== [http://www.w3.org/TR/WCAG20 WCAG 2.0] ===<br />
<br />
* When deciding how Moodle should present its content for best Web accessibility, the [http://www.w3.org/TR/WCAG20 WCAG 2.0] guidelines is followed.<br />
* We hope to have document here soon discussing how well Moodle meets WCAG 2.0 requirements.<br />
<br />
=== [http://www.w3.org/TR/ATAG20 ATAG 2.0] ===<br />
<br />
* As Moodle is a place to construct content (as well as consume content), we also refer to the [http://www.w3.org/TR/ATAG20 ATAG 2.0] guidelines.<br />
* In Moodle 2.7 a new editor Atto was added that not only helps to improve how everyone can use the editor itself, but also helps to improve the accessibility of the content produced with it.<br />
<br />
=== [http://www.w3.org/TR/wai-aria ARIA 1.0] ===<br />
<br />
* As many parts of the Moodle user interface are dynamic and interactive, we follow the [http://www.w3.org/TR/wai-aria ARIA] recommendations to inform assistive technologies, such as screen-readers.<br />
<br />
=== Section 508 (US) ===<br />
<br />
* As Moodle is used by US Government agencies, the US Section 508 amendment can be relevant to Moodle.<br />
* Moodlerooms (a Moodle Partner) have a [http://www.moodlerooms.com/accessibility VPAT statement] on their web site.<br />
<br />
== Discussions ==<br />
<br />
One of the main places accessibility work is being carried out right now is on the Moodle Accessibility Collaboration Group mailing list, see http://collaborate.athenpro.org/group/moodle/<br />
<br />
There are also many discussion on issues in the [https://tracker.moodle.org/browse/MDL/component/10083/?selectedTab=com.atlassian.jira.jira-projects-plugin:component-issues-panel Moodle Tracker]<br />
<br />
== Known Bugs and issues ==<br />
<br />
This is [https://tracker.moodle.org/issues/?jql=component%20%3D%20Accessibility%20AND%20project%20%3D%20MDL%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC the main list of accessibility issues], organised by priority. This list is always changing.<br />
<br />
== Areas of ongoing development ==<br />
<br />
* [https://tracker.moodle.org/browse/MDL-39663 Filepicker]<br />
* [https://tracker.moodle.org/browse/MDL-41773 Forum]<br />
<br />
== See also ==<br />
<br />
[[dev:Accessibility|Accessibility for Moodle Developers]]</div>Deraadthttps://docs.moodle.org/30/en/index.php?title=Security_FAQ&diff=113225Security FAQ2014-06-20T06:23:55Z<p>Deraadt: Removing duplicated content and directing to the security procedures page.</p>
<hr />
<div>{{Security}}<br />
==How do I report a security issue?==<br />
<br />
See [[Moodle_security_procedures#How_can_I_report_a_security_issue.3F|How to report a security issue]] in the Moodle security procedures page.<br />
<br />
Previously fixed security issues are listed in the [http://moodle.org/security/ Moodle.org Security news]. If you are unsure whether a problem has been fixed or not, it's best to report it anyway.<br />
<br />
==How can I keep my site secure?==<br />
<br />
It's good practice to always use the latest stable release of the version you are using. It is safe to upgrade to a more recent version on the branch you are using, say from Moodle 2.X.1 to the latest version on the 2.X branch. [[Git for Administrators|Downloading via Git]] makes it very easy way to do this.<br />
<br />
==How do I keep track of recent security issues?==<br />
<br />
* [[Site registration | Register your Moodle site with moodle.org]], making sure to enable the option of being notified about security issues and updates. After your registration is accepted, your email address will be automatically added to our low-volume security alerts mailing list.<br />
<br />
* Eventually, all important security issues are published to the general public via the [http://moodle.org/mod/forum/view.php?f=996 Moodle Security forum]. You can subscribe to the [http://moodle.org/rss/file.php/1/1/forum/996/rss.xml forum RSS feed] to automatically add new issues in your favourite feed reader or portal. You can also follow [http://twitter.com/moodlesecurity moodlesecurity on Twitter].<br />
<br />
==Who is able to view security issues in the Tracker?==<br />
<br />
Depending upon the security level of a Tracker issue, access is restricted to developers, testers or members of the security team.<br />
<br />
==Which versions of Moodle are supported?==<br />
<br />
Currently supported versions are listed on [http://download.moodle.org/ download.moodle.org].<br />
<br />
==My site was hacked. What do I do?==<br />
<br />
See [[Hacked site recovery]].<br />
<br />
==How can I reduce spam in Moodle?==<br />
<br />
See [[Reducing spam in Moodle]].<br />
<br />
==How can I increase privacy in Moodle?==<br />
<br />
See [[Increasing privacy in Moodle]].<br />
<br />
==How do I enable reCAPTCHA?==<br />
<br />
To add spam protection to the [[Email-based self-registration]] new account form with a CAPTCHA element:<br />
<br />
#Obtain a reCAPTCHA key from http://recaptcha.net by [https://admin.recaptcha.net/accounts/signup/?next= signing up for an account] (free) then entering a domain.<br />
#Copy and paste the public and private keys provided into the ''recaptchapublickey'' and ''recaptchaprivatekey'' fields in the manage authentication common settings in ''Administration > Plugins > Authentication > [[Manage authentication]]''.<br />
#Click the "Save changes" button at the bottom of the page.<br />
#Follow the settings link for email-based self-registration in ''Administration > Plugins > Authentication > Manage authentication'' and enable the reCAPTCHA element.<br />
#Click the "Save changes" button at the bottom of the page.<br />
<br />
==How can I run the security overview report?==<br />
<br />
To run the [[Security overview|security overview report]], go to ''Administration > Site administration > Reports > Security overview''.<br />
<br />
==See also==<br />
<br />
* Using Moodle [http://moodle.org/mod/forum/view.php?id=7301 Security and Privacy forum]<br />
<br />
[[Category:FAQ]]</div>Deraadthttps://docs.moodle.org/30/en/index.php?title=Moodle_security_procedures&diff=113224Moodle security procedures2014-06-20T04:05:41Z<p>Deraadt: Adding email for security issues.</p>
<hr />
<div>{{Security}}<br />
<br />
We treat security issues in Moodle software very seriously. Even though we dedicate a lot of time designing our code to avoid such problems, it is inevitable in a project of this size that new vulnerabilities will occasionally be discovered.<br />
<br />
==Disclosure policy==<br />
<br />
We practice ''responsible disclosure'', which means we have a policy of disclosing all security issues that come to our attention, but only after we have solved the issue and given registered Moodle sites time to upgrade or patch their installations.<br />
<br />
We ask that when reporting a security issue, you observe these same guidelines, and beyond communicating with the security team, do not share your knowledge of security issues with the public at large.<br />
<br />
==How can I report a security issue?==<br />
<br />
Please "[http://tracker.moodle.org/secure/CreateIssue.jspa Create a new issue]" in the Moodle Tracker describing the problem (and solution if possible) in detail. Make sure you set the security level accurately to make sure that the security team sees it. Bugs classified as a "Serious security issue" are hidden from everyone apart from the security team and the person who reported the problem. If you are not sure whether an issue is a security issue, you should still create a new issue in the tracker for review, using the security level "Could be a security issue".<br />
<br />
If you are not able to create an issue on the Moodle Tracker, you may send an email to security@moodle.org, however this is less secure than using the Tracker.<br />
<br />
Please do ''not'' post about security issues in the forums on moodle.org or elsewhere. This will cause the issue to be more widely known before a fix can be prepared.<br />
<br />
==How we deal with a reported security issue==<br />
<br />
# The security team reviews the issue and evaluates its potential impact on all supported versions of Moodle.<br />
# The security team works with the issue reporter to resolve the problem, following the [[:dev:Process#Security_issues|Security issue development process]] and keeping details of the problem and its solution hidden until a release is made.<br />
# New versions are created and tested.<br />
# New packages are created and made available on download.moodle.org.<br />
# Advisories are mailed to administrators of registered Moodle sites, giving a period of time when they can upgrade before the issue becomes public.<br />
# A public announcement is made about the security issue in the [http://moodle.org/mod/forum/view.php?id=7128 Moodle security news forum].<br />
<br />
==See also...==<br />
* [[:dev:Process#Security_issues|Security issue development process]]<br />
<br />
[[de:Sicherheitsprozeduren]]</div>Deraadthttps://docs.moodle.org/30/en/index.php?title=Upgrading&diff=112382Upgrading2014-05-07T07:30:09Z<p>Deraadt: Adding a few extra words.</p>
<hr />
<div>{{Installing Moodle}} <br />
''This page explains in detail how to upgrade Moodle. For a summary of the process, see [[Upgrade overview]].''<br />
<br />
==Check the requirements==<br />
<br />
Check that your server meets all requirements for 2.7 in ''Administration > Site administration > Server > [[Environment]]''.<br />
<br />
Note: You can only upgrade to Moodle 2.7 from Moodle 2.2 or later. If upgrading from earlier versions, you must [https://docs.moodle.org/22/en/Upgrading_to_Moodle_2.2 upgrade to 2.2] as a first step.<br />
<br />
==Before upgrading==<br />
<br />
'''We advise that you test the upgrade first on a COPY of your production site, to make sure it works as you expect.'''<br />
<br />
===Themes===<br />
<br />
All standard themes present in Moodle 2.6 (and earlier), except the Clean theme, have been removed from Moodle 2.7 (see MDL-43784). Custom themes and themes from the Plugins Directory are not affected, unless they use one of the removed themes as a parent theme. If a theme that was in use has been removed, the theme will revert to the new default theme called Clean.<br />
<br />
For sites wishing to continue using any of the removed standard themes (or themes relying on a standard theme as a parent theme), other than Clean, we recommend you use the following process.<br />
<br />
# Download the 2.7 version of Moodle, but do not run the upgrade yet.<br />
# Download the 2.7 version of your theme from the [https://moodle.org/plugins/browse.php?list=category&id=3 Themes section of the Moodle plugins directory] (or from the links below) into moodle/theme/.<br />
# Proceed with the upgrade.<br />
<br />
It is possible to copy missing themes into Moodle after the upgrade, but this should happen before users touch the system, otherwise theme-related settings may be lost.<br />
<br />
The affected themes (with download links) are...<br />
<br />
{|-<br />
| Afterburner<br />
| [https://moodle.org/plugins/view.php?plugin=theme_afterburner plugins db]<br />
| [https://github.com/moodlehq/moodle-theme_afterburner github]<br />
|-<br />
| Anomaly<br />
| [https://moodle.org/plugins/view.php?plugin=theme_anomaly plugins db]<br />
| [https://github.com/moodlehq/moodle-theme_anomaly github]<br />
|-<br />
| Arialist<br />
| [https://moodle.org/plugins/view.php?plugin=theme_arialist plugins db]<br />
| [https://github.com/moodlehq/moodle-theme_arialist github]<br />
|-<br />
| Binarius<br />
| [https://moodle.org/plugins/view.php?plugin=theme_binarius plugins db]<br />
| [https://github.com/moodlehq/moodle-theme_binarius github]<br />
|-<br />
| Boxxie<br />
| [https://moodle.org/plugins/view.php?plugin=theme_boxxie plugins db]<br />
| [https://github.com/moodlehq/moodle-theme_boxxie github]<br />
|-<br />
| Brick<br />
| [https://moodle.org/plugins/view.php?plugin=theme_brick plugins db]<br />
| [https://github.com/moodlehq/moodle-theme_brick github]<br />
|-<br />
| Formal White<br />
| [https://moodle.org/plugins/view.php?plugin=theme_formal_white plugins db]<br />
| [https://github.com/andreabix/moodle-theme_formal_white github]<br />
|-<br />
| Form Factor<br />
| [https://moodle.org/plugins/view.php?plugin=theme_formfactor plugins db]<br />
| [https://github.com/moodlehq/moodle-theme_formfactor github]<br />
|-<br />
| Fusion<br />
| [https://moodle.org/plugins/view.php?plugin=theme_fusion plugins db]<br />
| [https://github.com/moodlehq/moodle-theme_fusion github]<br />
|-<br />
| Leatherbound<br />
| [https://moodle.org/plugins/view.php?plugin=theme_leatherbound plugins db]<br />
| [https://github.com/moodlehq/moodle-theme_leatherbound github]<br />
|-<br />
| Magazine<br />
| [https://moodle.org/plugins/view.php?plugin=theme_magazine plugins db]<br />
| [https://github.com/moodlehq/moodle-theme_magazine github]<br />
|-<br />
| Nimble<br />
| [https://moodle.org/plugins/view.php?plugin=theme_nimble plugins db]<br />
| [https://github.com/moodlehq/moodle-theme_nimble github]<br />
|-<br />
| Nonzero<br />
| [https://moodle.org/plugins/view.php?plugin=theme_nonzero plugins db]<br />
| [https://github.com/moodlehq/moodle-theme_nonzero github]<br />
|-<br />
| Overlay<br />
| [https://moodle.org/plugins/view.php?plugin=theme_overlay plugins db]<br />
| [https://github.com/moodlehq/moodle-theme_overlay github]<br />
|-<br />
| Serenity<br />
| [https://moodle.org/plugins/view.php?plugin=theme_serenity plugins db]<br />
| [https://github.com/moodlehq/moodle-theme_serenity github]<br />
|-<br />
| Sky High<br />
| [https://moodle.org/plugins/view.php?plugin=theme_sky_high plugins db]<br />
| [https://github.com/moodlehq/moodle-theme_sky_high github]<br />
|-<br />
| Splash<br />
| [https://moodle.org/plugins/view.php?plugin=theme_splash plugins db]<br />
| [https://github.com/moodlehq/moodle-theme_splash github]<br />
|-<br />
| Standard<br />
| [https://moodle.org/plugins/view.php?plugin=theme_standard plugins db]<br />
| [https://github.com/moodlehq/moodle-theme_standard github]<br />
|-<br />
| Standard old<br />
| [https://moodle.org/plugins/view.php?plugin=theme_standardold plugins db]<br />
| [https://github.com/moodlehq/moodle-theme_standardold github]<br />
|}<br />
<br />
Note: Only installed add-on themes are updated automatically during the upgrade, NOT standard themes. Because standard themes have been removed from Moodle 2.7, they have to be re-added.<br />
<br />
===Questions engine upgrade===<br />
<br />
In Moodle 2.1, there was a major overhaul of the Question engine. As explained in [https://docs.moodle.org/21/en/Upgrading_to_Moodle_2.1#Planning_the_question_engine_upgrade the upgrade documentation for that version], it was possible to delay parts of the database upgrade to be run later. Before you upgrade to Moodle 2.7, this upgrade must be completed.<br />
<br />
This will affect you if...<br />
* your site started off on a version of Moodle 2.0.x and<br />
* when you upgraded to Moodle 2.1 or 2.2, you made use of the complex facility to delay part of the question engine upgrade (as explained in [https://docs.moodle.org/21/en/Upgrading_to_Moodle_2.1#Planning_the_question_engine_upgrade the upgrade documentation for that version]) and<br />
* you still have not completing that upgrade<br />
...then you must complete it before upgrading to Moodle 2.7.<br />
<br />
You can check by looking at the bottom of the [[:en:Environment|Environment]] page in your site, providing you are running a version later than 2.4.9, 2.5.5 or 2.6.2. If you have a problem, it will tell you there. If there is no mention of questions there, you can forget about this.<br />
<br />
This is unlikely to affect most users.<br />
<br />
== Backup important data ==<br />
<br />
There are three areas that should be backed up before any upgrade:<br />
#Moodle software (For example, everything in server/htdocs/moodle)<br />
#Moodle uploaded files (For example, server/moodledata)<br />
#Moodle database (For example, your Postgres or MySQL database dump)<br />
<br />
See [[Site backup]] for more specific information.<br />
<br />
==Put your site into maintenance mode==<br />
Before you begin upgrading your site, you should put it into [[Maintenance_mode | maintenance mode]] to stop any non-admin users from logging in.<br />
<br />
== Check for add-on updates ==<br />
<br />
If you have [[Automatic updates deployment]] enabled, you will be able to update installed add-ons automatically during the upgrade. Just make sure you check for available updates (via the button for it) at the Plugins check screen.<br />
<br />
If you are updating add-ons manually, it is a good moment now to check in the [http://moodle.org/plugins Moodle Plugins directory] whether there is a 2.7 version available for any add-ons (including themes) that you have previously installed on your site. If so, download the add-on package. In the next step, you will copy it to the appropriate location in your Moodle code (see [[Installing add-ons]]).<br />
<br />
The upgrade of the add-on will then happen as part of the Moodle upgrade process.<br />
<br />
If an out-of-date add-on causes your upgrade to fail, you can usually delete the add-on code rather than uninstalling it from within Moodle so that the data associated with it is not deleted.<br />
<br />
== Install the new Moodle software ==<br />
<br />
=== Standard install package ===<br />
<br />
# Move your old Moodle software program files to another location. ''Do NOT copy new files over the old files.''<br />
# Unzip or unpack the upgrade file so that all the new Moodle software program files are in the location the old files used to be in on the server. Moodle will adjust SQL and moodledata if it needs to in the upgrade.<br />
# Copy your old [[Configuration file|config.php file]] back to the new Moodle directory. <br />
# As mentioned above, if you had installed any custom add-ons on your site you should add them to the new code tree now. It is important to check that you get the correct version for your new version of Moodle. Be particularly careful that you do not overwrite any code in the new version of Moodle.<br />
# Dont forget to also copy over your moodledata folder / directory. If you don't you will get a "fatal error $cfg- dataroot is not configured properly".<br />
<br />
====Linux====<br />
mv moodle moodle.backup<br />
tar xvzf moodle-2.7.tgz<br />
<br />
Next, copy across your config.php, any custom plugins, and your .htaccess file if you created one ('''check that custom plugins are the correct version for your new Moodle first'''):<br />
<br />
cp moodle.backup/config.php moodle<br />
cp -pr moodle.backup/theme/mytheme moodle/theme/mytheme<br />
cp -pr moodle.backup/mod/mymod moodle/mod/mymod<br />
<br />
Don't forget to make moodle/config.php (and the rest of the source code) readable by your www server. Ideally the files should not be writeable by your server.<br />
<br />
If you use cron, take care that cron.php is executeable and uses the correct php command: <br />
chmod 740 admin/cli/cron.php (some configurations need chmod 750 or chmod 755)<br />
copy the first line from cron.php (if it looks like '#!/usr/local/bin/php' or '#!/usr/local/bin/php5.3', no need to copy '<?php')<br />
<br />
if necessary.<br />
<br />
=== Using Git ===<br />
<br />
You can use Git for updating or upgrading your Moodle. See [[Git for Administrators]] for details.<br />
<br />
===Command line upgrade===<br />
<br />
On Linux servers, Moodle 2.7 supports running the [[CLI|upgrade from the command line]], rather than through a web browser. This is likely to be more reliable, particularly for large sites.<br />
<br />
== Finishing the upgrade ==<br />
<br />
The last step is to trigger the upgrade processes within Moodle. <br />
<br />
To do this just go to ''Administration > Site administration > Notifications''.<br />
<br />
Moodle will automatically detect the new version and perform all the SQL database or file system upgrades that are necessary. If there is anything it can't do itself (very rare) then you will see messages telling you what you need to do.<br />
<br />
Assuming all goes well (no error messages) then you can start using your new version of Moodle and enjoy the new features!<br />
<br />
Note: If you are running multiple servers then you should purge all caches manually (via ''Administration > Site administration > Development > Purge all caches'') after completing the upgrade on all servers.<br />
<br />
===Fatal error: Maximum execution time of 30 seconds exceeded...===<br />
<br />
If your server uses a main language other than English, you may encounter a 'Fatal error: Maximum execution time of 30 seconds exceeded' when you try to upgrade it. You can increase max_execution_time = 160 on php.ini to allow the scripts enough time to process the language update. Otherwise, you can switch to English as the default language before doing the upgrade and back to your original language after a succcessful upgrade. See the forum discussion at https://moodle.org/mod/forum/discuss.php?d=119598.<br />
<br />
==After upgrading==<br />
<br />
The config.php file from your installation should work fine but if you take a look at config-dist.php that came with Moodle 2.7 there are more/different options available (e.g. database drivers and settings). It's a good idea to map your old config.php settings to a new one based on the 2.7 config-dist.php.<br />
<br />
===Assignments===<br />
<br />
The old assignment (2.2) module has been removed from core and has been replaced by a stub to support transparently remapping URLs and restoring course backups from the old module to the new one. <br />
<br />
If you are still using the old assignment (2.2) module, after upgrading to Moodle 2.7 all assignment (2.2) activities will be hidden. You need to run the [[Assignment upgrade tool]] to un-hide the activities.<br />
<br />
If you really, really need to keep using the old assignment (2.2) module, you should update the code to Moodle 2.7, and then replace the "mod/assignment" folder with the one from https://github.com/moodlehq/moodle-mod_assignment/releases before completing the upgrade.<br />
<br />
==Possible issues that may affect you in Moodle 2.7==<br />
<br />
''Items to be added here...''<br />
<br />
=== Moodle 2.3, 2.4, 2.5 and 2.6 improvements ===<br />
<br />
Depending on which version you are upgrading from, please see the section 'Possible issues that may affect you' in the documentation<br />
<br />
* [https://docs.moodle.org/23/en/Upgrading Upgrading to Moodle 2.3]<br />
* [https://docs.moodle.org/24/en/Upgrading Upgrading to Moodle 2.4]<br />
* [https://docs.moodle.org/25/en/Upgrading Upgrading to Moodle 2.5]<br />
* [https://docs.moodle.org/26/en/Upgrading Upgrading to Moodle 2.6]<br />
<br />
==See also==<br />
<br />
* Using Moodle [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum] <br />
* [[dev:Moodle 2.7 release notes|Moodle 2.7 release notes]]<br />
* [[dev:Upgrade API|Upgrade API]]<br />
<br />
[[es:Actualización de moodle]]<br />
[[fr:Mise à jour]]<br />
[[ja:Moodleをアップグレードする]]<br />
[[de:Aktualisierung von Moodle]]</div>Deraadthttps://docs.moodle.org/30/en/index.php?title=Upgrading&diff=112381Upgrading2014-05-07T07:20:17Z<p>Deraadt: Adding note about the new default.</p>
<hr />
<div>{{Installing Moodle}} <br />
''This page explains in detail how to upgrade Moodle. For a summary of the process, see [[Upgrade overview]].''<br />
<br />
==Check the requirements==<br />
<br />
Check that your server meets all requirements for 2.7 in ''Administration > Site administration > Server > [[Environment]]''.<br />
<br />
Note: You can only upgrade to Moodle 2.7 from Moodle 2.2 or later. If upgrading from earlier versions, you must [https://docs.moodle.org/22/en/Upgrading_to_Moodle_2.2 upgrade to 2.2] as a first step.<br />
<br />
==Before upgrading==<br />
<br />
'''We advise that you test the upgrade first on a COPY of your production site, to make sure it works as you expect.'''<br />
<br />
===Themes===<br />
<br />
All standard themes present in Moodle 2.6 (and earlier), except the Clean theme, have been removed from Moodle 2.7 (see MDL-43784). Custom themes and themes from the Plugins Directory are not affected, unless they use one of the removed themes as a parent theme. If a theme in use has been removed, the theme will revert to the new default theme called Clean.<br />
<br />
For sites wishing to continue using any of the removed standard themes (or themes relying on a standard theme as a parent theme), other than Clean, we recommend you use the following process.<br />
<br />
# Download the 2.7 version of Moodle, but do not run the upgrade yet.<br />
# Download the 2.7 version of your theme from the [https://moodle.org/plugins/browse.php?list=category&id=3 Themes section of the Moodle plugins directory] (or from the links below) into moodle/theme/.<br />
# Proceed with the upgrade.<br />
<br />
It is possible to copy missing themes into Moodle after the upgrade, but this should happen before users touch the system, otherwise theme-related settings may be lost.<br />
<br />
The affected themes (with download links) are...<br />
<br />
{|-<br />
| Afterburner<br />
| [https://moodle.org/plugins/view.php?plugin=theme_afterburner plugins db]<br />
| [https://github.com/moodlehq/moodle-theme_afterburner github]<br />
|-<br />
| Anomaly<br />
| [https://moodle.org/plugins/view.php?plugin=theme_anomaly plugins db]<br />
| [https://github.com/moodlehq/moodle-theme_anomaly github]<br />
|-<br />
| Arialist<br />
| [https://moodle.org/plugins/view.php?plugin=theme_arialist plugins db]<br />
| [https://github.com/moodlehq/moodle-theme_arialist github]<br />
|-<br />
| Binarius<br />
| [https://moodle.org/plugins/view.php?plugin=theme_binarius plugins db]<br />
| [https://github.com/moodlehq/moodle-theme_binarius github]<br />
|-<br />
| Boxxie<br />
| [https://moodle.org/plugins/view.php?plugin=theme_boxxie plugins db]<br />
| [https://github.com/moodlehq/moodle-theme_boxxie github]<br />
|-<br />
| Brick<br />
| [https://moodle.org/plugins/view.php?plugin=theme_brick plugins db]<br />
| [https://github.com/moodlehq/moodle-theme_brick github]<br />
|-<br />
| Formal White<br />
| [https://moodle.org/plugins/view.php?plugin=theme_formal_white plugins db]<br />
| [https://github.com/andreabix/moodle-theme_formal_white github]<br />
|-<br />
| Form Factor<br />
| [https://moodle.org/plugins/view.php?plugin=theme_formfactor plugins db]<br />
| [https://github.com/moodlehq/moodle-theme_formfactor github]<br />
|-<br />
| Fusion<br />
| [https://moodle.org/plugins/view.php?plugin=theme_fusion plugins db]<br />
| [https://github.com/moodlehq/moodle-theme_fusion github]<br />
|-<br />
| Leatherbound<br />
| [https://moodle.org/plugins/view.php?plugin=theme_leatherbound plugins db]<br />
| [https://github.com/moodlehq/moodle-theme_leatherbound github]<br />
|-<br />
| Magazine<br />
| [https://moodle.org/plugins/view.php?plugin=theme_magazine plugins db]<br />
| [https://github.com/moodlehq/moodle-theme_magazine github]<br />
|-<br />
| Nimble<br />
| [https://moodle.org/plugins/view.php?plugin=theme_nimble plugins db]<br />
| [https://github.com/moodlehq/moodle-theme_nimble github]<br />
|-<br />
| Nonzero<br />
| [https://moodle.org/plugins/view.php?plugin=theme_nonzero plugins db]<br />
| [https://github.com/moodlehq/moodle-theme_nonzero github]<br />
|-<br />
| Overlay<br />
| [https://moodle.org/plugins/view.php?plugin=theme_overlay plugins db]<br />
| [https://github.com/moodlehq/moodle-theme_overlay github]<br />
|-<br />
| Serenity<br />
| [https://moodle.org/plugins/view.php?plugin=theme_serenity plugins db]<br />
| [https://github.com/moodlehq/moodle-theme_serenity github]<br />
|-<br />
| Sky High<br />
| [https://moodle.org/plugins/view.php?plugin=theme_sky_high plugins db]<br />
| [https://github.com/moodlehq/moodle-theme_sky_high github]<br />
|-<br />
| Splash<br />
| [https://moodle.org/plugins/view.php?plugin=theme_splash plugins db]<br />
| [https://github.com/moodlehq/moodle-theme_splash github]<br />
|-<br />
| Standard<br />
| [https://moodle.org/plugins/view.php?plugin=theme_standard plugins db]<br />
| [https://github.com/moodlehq/moodle-theme_standard github]<br />
|-<br />
| Standard old<br />
| [https://moodle.org/plugins/view.php?plugin=theme_standardold plugins db]<br />
| [https://github.com/moodlehq/moodle-theme_standardold github]<br />
|}<br />
<br />
Note: Only installed add-on themes are updated automatically during the upgrade, NOT standard themes. Because standard themes have been removed from Moodle 2.7, they have to be re-added.<br />
<br />
===Questions engine upgrade===<br />
<br />
In Moodle 2.1, there was a major overhaul of the Question engine. As explained in [https://docs.moodle.org/21/en/Upgrading_to_Moodle_2.1#Planning_the_question_engine_upgrade the upgrade documentation for that version], it was possible to delay parts of the database upgrade to be run later. Before you upgrade to Moodle 2.7, this upgrade must be completed.<br />
<br />
This will affect you if...<br />
* your site started off on a version of Moodle 2.0.x and<br />
* when you upgraded to Moodle 2.1 or 2.2, you made use of the complex facility to delay part of the question engine upgrade (as explained in [https://docs.moodle.org/21/en/Upgrading_to_Moodle_2.1#Planning_the_question_engine_upgrade the upgrade documentation for that version]) and<br />
* you still have not completing that upgrade<br />
...then you must complete it before upgrading to Moodle 2.7.<br />
<br />
You can check by looking at the bottom of the [[:en:Environment|Environment]] page in your site, providing you are running a version later than 2.4.9, 2.5.5 or 2.6.2. If you have a problem, it will tell you there. If there is no mention of questions there, you can forget about this.<br />
<br />
This is unlikely to affect most users.<br />
<br />
== Backup important data ==<br />
<br />
There are three areas that should be backed up before any upgrade:<br />
#Moodle software (For example, everything in server/htdocs/moodle)<br />
#Moodle uploaded files (For example, server/moodledata)<br />
#Moodle database (For example, your Postgres or MySQL database dump)<br />
<br />
See [[Site backup]] for more specific information.<br />
<br />
==Put your site into maintenance mode==<br />
Before you begin upgrading your site, you should put it into [[Maintenance_mode | maintenance mode]] to stop any non-admin users from logging in.<br />
<br />
== Check for add-on updates ==<br />
<br />
If you have [[Automatic updates deployment]] enabled, you will be able to update installed add-ons automatically during the upgrade. Just make sure you check for available updates (via the button for it) at the Plugins check screen.<br />
<br />
If you are updating add-ons manually, it is a good moment now to check in the [http://moodle.org/plugins Moodle Plugins directory] whether there is a 2.7 version available for any add-ons (including themes) that you have previously installed on your site. If so, download the add-on package. In the next step, you will copy it to the appropriate location in your Moodle code (see [[Installing add-ons]]).<br />
<br />
The upgrade of the add-on will then happen as part of the Moodle upgrade process.<br />
<br />
If an out-of-date add-on causes your upgrade to fail, you can usually delete the add-on code rather than uninstalling it from within Moodle so that the data associated with it is not deleted.<br />
<br />
== Install the new Moodle software ==<br />
<br />
=== Standard install package ===<br />
<br />
# Move your old Moodle software program files to another location. ''Do NOT copy new files over the old files.''<br />
# Unzip or unpack the upgrade file so that all the new Moodle software program files are in the location the old files used to be in on the server. Moodle will adjust SQL and moodledata if it needs to in the upgrade.<br />
# Copy your old [[Configuration file|config.php file]] back to the new Moodle directory. <br />
# As mentioned above, if you had installed any custom add-ons on your site you should add them to the new code tree now. It is important to check that you get the correct version for your new version of Moodle. Be particularly careful that you do not overwrite any code in the new version of Moodle.<br />
# Dont forget to also copy over your moodledata folder / directory. If you don't you will get a "fatal error $cfg- dataroot is not configured properly".<br />
<br />
====Linux====<br />
mv moodle moodle.backup<br />
tar xvzf moodle-2.7.tgz<br />
<br />
Next, copy across your config.php, any custom plugins, and your .htaccess file if you created one ('''check that custom plugins are the correct version for your new Moodle first'''):<br />
<br />
cp moodle.backup/config.php moodle<br />
cp -pr moodle.backup/theme/mytheme moodle/theme/mytheme<br />
cp -pr moodle.backup/mod/mymod moodle/mod/mymod<br />
<br />
Don't forget to make moodle/config.php (and the rest of the source code) readable by your www server. Ideally the files should not be writeable by your server.<br />
<br />
If you use cron, take care that cron.php is executeable and uses the correct php command: <br />
chmod 740 admin/cli/cron.php (some configurations need chmod 750 or chmod 755)<br />
copy the first line from cron.php (if it looks like '#!/usr/local/bin/php' or '#!/usr/local/bin/php5.3', no need to copy '<?php')<br />
<br />
if necessary.<br />
<br />
=== Using Git ===<br />
<br />
You can use Git for updating or upgrading your Moodle. See [[Git for Administrators]] for details.<br />
<br />
===Command line upgrade===<br />
<br />
On Linux servers, Moodle 2.7 supports running the [[CLI|upgrade from the command line]], rather than through a web browser. This is likely to be more reliable, particularly for large sites.<br />
<br />
== Finishing the upgrade ==<br />
<br />
The last step is to trigger the upgrade processes within Moodle. <br />
<br />
To do this just go to ''Administration > Site administration > Notifications''.<br />
<br />
Moodle will automatically detect the new version and perform all the SQL database or file system upgrades that are necessary. If there is anything it can't do itself (very rare) then you will see messages telling you what you need to do.<br />
<br />
Assuming all goes well (no error messages) then you can start using your new version of Moodle and enjoy the new features!<br />
<br />
Note: If you are running multiple servers then you should purge all caches manually (via ''Administration > Site administration > Development > Purge all caches'') after completing the upgrade on all servers.<br />
<br />
===Fatal error: Maximum execution time of 30 seconds exceeded...===<br />
<br />
If your server uses a main language other than English, you may encounter a 'Fatal error: Maximum execution time of 30 seconds exceeded' when you try to upgrade it. You can increase max_execution_time = 160 on php.ini to allow the scripts enough time to process the language update. Otherwise, you can switch to English as the default language before doing the upgrade and back to your original language after a succcessful upgrade. See the forum discussion at https://moodle.org/mod/forum/discuss.php?d=119598.<br />
<br />
==After upgrading==<br />
<br />
The config.php file from your installation should work fine but if you take a look at config-dist.php that came with Moodle 2.7 there are more/different options available (e.g. database drivers and settings). It's a good idea to map your old config.php settings to a new one based on the 2.7 config-dist.php.<br />
<br />
===Assignments===<br />
<br />
The old assignment (2.2) module has been removed from core and has been replaced by a stub to support transparently remapping URLs and restoring course backups from the old module to the new one. <br />
<br />
If you are still using the old assignment (2.2) module, after upgrading to Moodle 2.7 all assignment (2.2) activities will be hidden. You need to run the [[Assignment upgrade tool]] to un-hide the activities.<br />
<br />
If you really, really need to keep using the old assignment (2.2) module, you should update the code to Moodle 2.7, and then replace the "mod/assignment" folder with the one from https://github.com/moodlehq/moodle-mod_assignment/releases before completing the upgrade.<br />
<br />
==Possible issues that may affect you in Moodle 2.7==<br />
<br />
''Items to be added here...''<br />
<br />
=== Moodle 2.3, 2.4, 2.5 and 2.6 improvements ===<br />
<br />
Depending on which version you are upgrading from, please see the section 'Possible issues that may affect you' in the documentation<br />
<br />
* [https://docs.moodle.org/23/en/Upgrading Upgrading to Moodle 2.3]<br />
* [https://docs.moodle.org/24/en/Upgrading Upgrading to Moodle 2.4]<br />
* [https://docs.moodle.org/25/en/Upgrading Upgrading to Moodle 2.5]<br />
* [https://docs.moodle.org/26/en/Upgrading Upgrading to Moodle 2.6]<br />
<br />
==See also==<br />
<br />
* Using Moodle [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum] <br />
* [[dev:Moodle 2.7 release notes|Moodle 2.7 release notes]]<br />
* [[dev:Upgrade API|Upgrade API]]<br />
<br />
[[es:Actualización de moodle]]<br />
[[fr:Mise à jour]]<br />
[[ja:Moodleをアップグレードする]]<br />
[[de:Aktualisierung von Moodle]]</div>Deraadthttps://docs.moodle.org/30/en/index.php?title=Upgrading&diff=112380Upgrading2014-05-07T07:18:38Z<p>Deraadt: Incorporating information removed from the Release notes page</p>
<hr />
<div>{{Installing Moodle}} <br />
''This page explains in detail how to upgrade Moodle. For a summary of the process, see [[Upgrade overview]].''<br />
<br />
==Check the requirements==<br />
<br />
Check that your server meets all requirements for 2.7 in ''Administration > Site administration > Server > [[Environment]]''.<br />
<br />
Note: You can only upgrade to Moodle 2.7 from Moodle 2.2 or later. If upgrading from earlier versions, you must [https://docs.moodle.org/22/en/Upgrading_to_Moodle_2.2 upgrade to 2.2] as a first step.<br />
<br />
==Before upgrading==<br />
<br />
'''We advise that you test the upgrade first on a COPY of your production site, to make sure it works as you expect.'''<br />
<br />
===Themes===<br />
<br />
All standard themes present in Moodle 2.6 (and earlier), except the Clean theme, have been removed from Moodle 2.7 (see MDL-43784). Custom themes and themes from the Plugins Directory are not affected, unless they use one of the removed themes as a parent theme.<br />
<br />
For sites wishing to continue using standard themes (or themes relying on a standard theme as a parent theme), other than Clean, we recommend you use the following process.<br />
<br />
# Download the 2.7 version of Moodle, but do not run the upgrade yet.<br />
# Download the 2.7 version of your theme from the [https://moodle.org/plugins/browse.php?list=category&id=3 Themes section of the Moodle plugins directory] (or from the links below) into moodle/theme/.<br />
# Proceed with the upgrade.<br />
<br />
It is possible to copy missing themes into Moodle after the upgrade, but this should happen before users touch the system, otherwise theme-related settings may be lost.<br />
<br />
The affected themes (with download links) are...<br />
<br />
{|-<br />
| Afterburner<br />
| [https://moodle.org/plugins/view.php?plugin=theme_afterburner plugins db]<br />
| [https://github.com/moodlehq/moodle-theme_afterburner github]<br />
|-<br />
| Anomaly<br />
| [https://moodle.org/plugins/view.php?plugin=theme_anomaly plugins db]<br />
| [https://github.com/moodlehq/moodle-theme_anomaly github]<br />
|-<br />
| Arialist<br />
| [https://moodle.org/plugins/view.php?plugin=theme_arialist plugins db]<br />
| [https://github.com/moodlehq/moodle-theme_arialist github]<br />
|-<br />
| Binarius<br />
| [https://moodle.org/plugins/view.php?plugin=theme_binarius plugins db]<br />
| [https://github.com/moodlehq/moodle-theme_binarius github]<br />
|-<br />
| Boxxie<br />
| [https://moodle.org/plugins/view.php?plugin=theme_boxxie plugins db]<br />
| [https://github.com/moodlehq/moodle-theme_boxxie github]<br />
|-<br />
| Brick<br />
| [https://moodle.org/plugins/view.php?plugin=theme_brick plugins db]<br />
| [https://github.com/moodlehq/moodle-theme_brick github]<br />
|-<br />
| Formal White<br />
| [https://moodle.org/plugins/view.php?plugin=theme_formal_white plugins db]<br />
| [https://github.com/andreabix/moodle-theme_formal_white github]<br />
|-<br />
| Form Factor<br />
| [https://moodle.org/plugins/view.php?plugin=theme_formfactor plugins db]<br />
| [https://github.com/moodlehq/moodle-theme_formfactor github]<br />
|-<br />
| Fusion<br />
| [https://moodle.org/plugins/view.php?plugin=theme_fusion plugins db]<br />
| [https://github.com/moodlehq/moodle-theme_fusion github]<br />
|-<br />
| Leatherbound<br />
| [https://moodle.org/plugins/view.php?plugin=theme_leatherbound plugins db]<br />
| [https://github.com/moodlehq/moodle-theme_leatherbound github]<br />
|-<br />
| Magazine<br />
| [https://moodle.org/plugins/view.php?plugin=theme_magazine plugins db]<br />
| [https://github.com/moodlehq/moodle-theme_magazine github]<br />
|-<br />
| Nimble<br />
| [https://moodle.org/plugins/view.php?plugin=theme_nimble plugins db]<br />
| [https://github.com/moodlehq/moodle-theme_nimble github]<br />
|-<br />
| Nonzero<br />
| [https://moodle.org/plugins/view.php?plugin=theme_nonzero plugins db]<br />
| [https://github.com/moodlehq/moodle-theme_nonzero github]<br />
|-<br />
| Overlay<br />
| [https://moodle.org/plugins/view.php?plugin=theme_overlay plugins db]<br />
| [https://github.com/moodlehq/moodle-theme_overlay github]<br />
|-<br />
| Serenity<br />
| [https://moodle.org/plugins/view.php?plugin=theme_serenity plugins db]<br />
| [https://github.com/moodlehq/moodle-theme_serenity github]<br />
|-<br />
| Sky High<br />
| [https://moodle.org/plugins/view.php?plugin=theme_sky_high plugins db]<br />
| [https://github.com/moodlehq/moodle-theme_sky_high github]<br />
|-<br />
| Splash<br />
| [https://moodle.org/plugins/view.php?plugin=theme_splash plugins db]<br />
| [https://github.com/moodlehq/moodle-theme_splash github]<br />
|-<br />
| Standard<br />
| [https://moodle.org/plugins/view.php?plugin=theme_standard plugins db]<br />
| [https://github.com/moodlehq/moodle-theme_standard github]<br />
|-<br />
| Standard old<br />
| [https://moodle.org/plugins/view.php?plugin=theme_standardold plugins db]<br />
| [https://github.com/moodlehq/moodle-theme_standardold github]<br />
|}<br />
<br />
Note: Only installed add-on themes are updated automatically during the upgrade, NOT standard themes. Because standard themes have been removed from Moodle 2.7, they have to be re-added.<br />
<br />
===Questions engine upgrade===<br />
<br />
In Moodle 2.1, there was a major overhaul of the Question engine. As explained in [https://docs.moodle.org/21/en/Upgrading_to_Moodle_2.1#Planning_the_question_engine_upgrade the upgrade documentation for that version], it was possible to delay parts of the database upgrade to be run later. Before you upgrade to Moodle 2.7, this upgrade must be completed.<br />
<br />
This will affect you if...<br />
* your site started off on a version of Moodle 2.0.x and<br />
* when you upgraded to Moodle 2.1 or 2.2, you made use of the complex facility to delay part of the question engine upgrade (as explained in [https://docs.moodle.org/21/en/Upgrading_to_Moodle_2.1#Planning_the_question_engine_upgrade the upgrade documentation for that version]) and<br />
* you still have not completing that upgrade<br />
...then you must complete it before upgrading to Moodle 2.7.<br />
<br />
You can check by looking at the bottom of the [[:en:Environment|Environment]] page in your site, providing you are running a version later than 2.4.9, 2.5.5 or 2.6.2. If you have a problem, it will tell you there. If there is no mention of questions there, you can forget about this.<br />
<br />
This is unlikely to affect most users.<br />
<br />
== Backup important data ==<br />
<br />
There are three areas that should be backed up before any upgrade:<br />
#Moodle software (For example, everything in server/htdocs/moodle)<br />
#Moodle uploaded files (For example, server/moodledata)<br />
#Moodle database (For example, your Postgres or MySQL database dump)<br />
<br />
See [[Site backup]] for more specific information.<br />
<br />
==Put your site into maintenance mode==<br />
Before you begin upgrading your site, you should put it into [[Maintenance_mode | maintenance mode]] to stop any non-admin users from logging in.<br />
<br />
== Check for add-on updates ==<br />
<br />
If you have [[Automatic updates deployment]] enabled, you will be able to update installed add-ons automatically during the upgrade. Just make sure you check for available updates (via the button for it) at the Plugins check screen.<br />
<br />
If you are updating add-ons manually, it is a good moment now to check in the [http://moodle.org/plugins Moodle Plugins directory] whether there is a 2.7 version available for any add-ons (including themes) that you have previously installed on your site. If so, download the add-on package. In the next step, you will copy it to the appropriate location in your Moodle code (see [[Installing add-ons]]).<br />
<br />
The upgrade of the add-on will then happen as part of the Moodle upgrade process.<br />
<br />
If an out-of-date add-on causes your upgrade to fail, you can usually delete the add-on code rather than uninstalling it from within Moodle so that the data associated with it is not deleted.<br />
<br />
== Install the new Moodle software ==<br />
<br />
=== Standard install package ===<br />
<br />
# Move your old Moodle software program files to another location. ''Do NOT copy new files over the old files.''<br />
# Unzip or unpack the upgrade file so that all the new Moodle software program files are in the location the old files used to be in on the server. Moodle will adjust SQL and moodledata if it needs to in the upgrade.<br />
# Copy your old [[Configuration file|config.php file]] back to the new Moodle directory. <br />
# As mentioned above, if you had installed any custom add-ons on your site you should add them to the new code tree now. It is important to check that you get the correct version for your new version of Moodle. Be particularly careful that you do not overwrite any code in the new version of Moodle.<br />
# Dont forget to also copy over your moodledata folder / directory. If you don't you will get a "fatal error $cfg- dataroot is not configured properly".<br />
<br />
====Linux====<br />
mv moodle moodle.backup<br />
tar xvzf moodle-2.7.tgz<br />
<br />
Next, copy across your config.php, any custom plugins, and your .htaccess file if you created one ('''check that custom plugins are the correct version for your new Moodle first'''):<br />
<br />
cp moodle.backup/config.php moodle<br />
cp -pr moodle.backup/theme/mytheme moodle/theme/mytheme<br />
cp -pr moodle.backup/mod/mymod moodle/mod/mymod<br />
<br />
Don't forget to make moodle/config.php (and the rest of the source code) readable by your www server. Ideally the files should not be writeable by your server.<br />
<br />
If you use cron, take care that cron.php is executeable and uses the correct php command: <br />
chmod 740 admin/cli/cron.php (some configurations need chmod 750 or chmod 755)<br />
copy the first line from cron.php (if it looks like '#!/usr/local/bin/php' or '#!/usr/local/bin/php5.3', no need to copy '<?php')<br />
<br />
if necessary.<br />
<br />
=== Using Git ===<br />
<br />
You can use Git for updating or upgrading your Moodle. See [[Git for Administrators]] for details.<br />
<br />
===Command line upgrade===<br />
<br />
On Linux servers, Moodle 2.7 supports running the [[CLI|upgrade from the command line]], rather than through a web browser. This is likely to be more reliable, particularly for large sites.<br />
<br />
== Finishing the upgrade ==<br />
<br />
The last step is to trigger the upgrade processes within Moodle. <br />
<br />
To do this just go to ''Administration > Site administration > Notifications''.<br />
<br />
Moodle will automatically detect the new version and perform all the SQL database or file system upgrades that are necessary. If there is anything it can't do itself (very rare) then you will see messages telling you what you need to do.<br />
<br />
Assuming all goes well (no error messages) then you can start using your new version of Moodle and enjoy the new features!<br />
<br />
Note: If you are running multiple servers then you should purge all caches manually (via ''Administration > Site administration > Development > Purge all caches'') after completing the upgrade on all servers.<br />
<br />
===Fatal error: Maximum execution time of 30 seconds exceeded...===<br />
<br />
If your server uses a main language other than English, you may encounter a 'Fatal error: Maximum execution time of 30 seconds exceeded' when you try to upgrade it. You can increase max_execution_time = 160 on php.ini to allow the scripts enough time to process the language update. Otherwise, you can switch to English as the default language before doing the upgrade and back to your original language after a succcessful upgrade. See the forum discussion at https://moodle.org/mod/forum/discuss.php?d=119598.<br />
<br />
==After upgrading==<br />
<br />
The config.php file from your installation should work fine but if you take a look at config-dist.php that came with Moodle 2.7 there are more/different options available (e.g. database drivers and settings). It's a good idea to map your old config.php settings to a new one based on the 2.7 config-dist.php.<br />
<br />
===Assignments===<br />
<br />
The old assignment (2.2) module has been removed from core and has been replaced by a stub to support transparently remapping URLs and restoring course backups from the old module to the new one. <br />
<br />
If you are still using the old assignment (2.2) module, after upgrading to Moodle 2.7 all assignment (2.2) activities will be hidden. You need to run the [[Assignment upgrade tool]] to un-hide the activities.<br />
<br />
If you really, really need to keep using the old assignment (2.2) module, you should update the code to Moodle 2.7, and then replace the "mod/assignment" folder with the one from https://github.com/moodlehq/moodle-mod_assignment/releases before completing the upgrade.<br />
<br />
==Possible issues that may affect you in Moodle 2.7==<br />
<br />
''Items to be added here...''<br />
<br />
=== Moodle 2.3, 2.4, 2.5 and 2.6 improvements ===<br />
<br />
Depending on which version you are upgrading from, please see the section 'Possible issues that may affect you' in the documentation<br />
<br />
* [https://docs.moodle.org/23/en/Upgrading Upgrading to Moodle 2.3]<br />
* [https://docs.moodle.org/24/en/Upgrading Upgrading to Moodle 2.4]<br />
* [https://docs.moodle.org/25/en/Upgrading Upgrading to Moodle 2.5]<br />
* [https://docs.moodle.org/26/en/Upgrading Upgrading to Moodle 2.6]<br />
<br />
==See also==<br />
<br />
* Using Moodle [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum] <br />
* [[dev:Moodle 2.7 release notes|Moodle 2.7 release notes]]<br />
* [[dev:Upgrade API|Upgrade API]]<br />
<br />
[[es:Actualización de moodle]]<br />
[[fr:Mise à jour]]<br />
[[ja:Moodleをアップグレードする]]<br />
[[de:Aktualisierung von Moodle]]</div>Deraadthttps://docs.moodle.org/30/en/index.php?title=Upgrading&diff=112379Upgrading2014-05-07T06:50:15Z<p>Deraadt: Incorporating information removed from the Release notes page</p>
<hr />
<div>{{Installing Moodle}} <br />
''This page explains in detail how to upgrade Moodle. For a summary of the process, see [[Upgrade overview]].''<br />
<br />
==Check the requirements==<br />
<br />
Check that your server meets all requirements for 2.7 in ''Administration > Site administration > Server > [[Environment]]''.<br />
<br />
Note: You can only upgrade to Moodle 2.7 from Moodle 2.2 or later. If upgrading from earlier versions, you must [https://docs.moodle.org/22/en/Upgrading_to_Moodle_2.2 upgrade to 2.2] as a first step.<br />
<br />
==Before upgrading==<br />
<br />
'''We advise that you test the upgrade first on a COPY of your production site, to make sure it works as you expect.'''<br />
<br />
===Themes===<br />
<br />
All core themes, except clean, have been removed from Moodle 2.7. Thus sites using any core theme (including sites using a core theme as a parent theme) other than clean must do the following:<br />
<br />
# Download the 2.7 version of your theme as a zip file from the [https://moodle.org/plugins/browse.php?list=category&id=3 Themes section of the Moodle plugins directory].<br />
# Follow the steps above to install the new Moodle software. In step 4, unzip the theme and copy it to moodle/theme/.<br />
# Proceed with the upgrade.<br />
<br />
Note: Only installed add-on themes may be updated automatically during the upgrade, NOT core themes. Because core themes have been removed from Moodle 2.7, they have to be re-added.<br />
<br />
===Questions engine upgrade===<br />
<br />
In Moodle 2.1, there was a major overhaul of the Question engine. As explained in [https://docs.moodle.org/21/en/Upgrading_to_Moodle_2.1#Planning_the_question_engine_upgrade the upgrade documentation for that version], it was possible to delay parts of the database upgrade to be run later. Before you upgrade to Moodle 2.7, this upgrade must be completed.<br />
<br />
This will affect you if...<br />
* your site started off on a version of Moodle 2.0.x and<br />
* when you upgraded to Moodle 2.1 or 2.2, you made use of the complex facility to delay part of the question engine upgrade (as explained in [https://docs.moodle.org/21/en/Upgrading_to_Moodle_2.1#Planning_the_question_engine_upgrade the upgrade documentation for that version]) and<br />
* you still have not completing that upgrade<br />
...then you must complete it before upgrading to Moodle 2.7.<br />
<br />
You can check by looking at the bottom of the [[:en:Environment|Environment]] page in your site, providing you are running a version later than 2.4.9, 2.5.5 or 2.6.2. If you have a problem, it will tell you there. If there is no mention of questions there, you can forget about this.<br />
<br />
This is unlikely to affect most users.<br />
<br />
== Backup important data ==<br />
<br />
There are three areas that should be backed up before any upgrade:<br />
#Moodle software (For example, everything in server/htdocs/moodle)<br />
#Moodle uploaded files (For example, server/moodledata)<br />
#Moodle database (For example, your Postgres or MySQL database dump)<br />
<br />
See [[Site backup]] for more specific information.<br />
<br />
==Put your site into maintenance mode==<br />
Before you begin upgrading your site, you should put it into [[Maintenance_mode | maintenance mode]] to stop any non-admin users from logging in.<br />
<br />
== Check for add-on updates ==<br />
<br />
If you have [[Automatic updates deployment]] enabled, you will be able to update installed add-ons automatically during the upgrade. Just make sure you check for available updates (via the button for it) at the Plugins check screen.<br />
<br />
If you are updating add-ons manually, it is a good moment now to check in the [http://moodle.org/plugins Moodle Plugins directory] whether there is a 2.7 version available for any add-ons (including themes) that you have previously installed on your site. If so, download the add-on package. In the next step, you will copy it to the appropriate location in your Moodle code (see [[Installing add-ons]]).<br />
<br />
The upgrade of the add-on will then happen as part of the Moodle upgrade process.<br />
<br />
If an out-of-date add-on causes your upgrade to fail, you can usually delete the add-on code rather than uninstalling it from within Moodle so that the data associated with it is not deleted.<br />
<br />
== Install the new Moodle software ==<br />
<br />
=== Standard install package ===<br />
<br />
# Move your old Moodle software program files to another location. ''Do NOT copy new files over the old files.''<br />
# Unzip or unpack the upgrade file so that all the new Moodle software program files are in the location the old files used to be in on the server. Moodle will adjust SQL and moodledata if it needs to in the upgrade.<br />
# Copy your old [[Configuration file|config.php file]] back to the new Moodle directory. <br />
# As mentioned above, if you had installed any custom add-ons on your site you should add them to the new code tree now. It is important to check that you get the correct version for your new version of Moodle. Be particularly careful that you do not overwrite any code in the new version of Moodle.<br />
# Dont forget to also copy over your moodledata folder / directory. If you don't you will get a "fatal error $cfg- dataroot is not configured properly".<br />
<br />
====Linux====<br />
mv moodle moodle.backup<br />
tar xvzf moodle-2.7.tgz<br />
<br />
Next, copy across your config.php, any custom plugins, and your .htaccess file if you created one ('''check that custom plugins are the correct version for your new Moodle first'''):<br />
<br />
cp moodle.backup/config.php moodle<br />
cp -pr moodle.backup/theme/mytheme moodle/theme/mytheme<br />
cp -pr moodle.backup/mod/mymod moodle/mod/mymod<br />
<br />
Don't forget to make moodle/config.php (and the rest of the source code) readable by your www server. Ideally the files should not be writeable by your server.<br />
<br />
If you use cron, take care that cron.php is executeable and uses the correct php command: <br />
chmod 740 admin/cli/cron.php (some configurations need chmod 750 or chmod 755)<br />
copy the first line from cron.php (if it looks like '#!/usr/local/bin/php' or '#!/usr/local/bin/php5.3', no need to copy '<?php')<br />
<br />
if necessary.<br />
<br />
=== Using Git ===<br />
<br />
You can use Git for updating or upgrading your Moodle. See [[Git for Administrators]] for details.<br />
<br />
===Command line upgrade===<br />
<br />
On Linux servers, Moodle 2.7 supports running the [[CLI|upgrade from the command line]], rather than through a web browser. This is likely to be more reliable, particularly for large sites.<br />
<br />
== Finishing the upgrade ==<br />
<br />
The last step is to trigger the upgrade processes within Moodle. <br />
<br />
To do this just go to ''Administration > Site administration > Notifications''.<br />
<br />
Moodle will automatically detect the new version and perform all the SQL database or file system upgrades that are necessary. If there is anything it can't do itself (very rare) then you will see messages telling you what you need to do.<br />
<br />
Assuming all goes well (no error messages) then you can start using your new version of Moodle and enjoy the new features!<br />
<br />
Note: If you are running multiple servers then you should purge all caches manually (via ''Administration > Site administration > Development > Purge all caches'') after completing the upgrade on all servers.<br />
<br />
===Fatal error: Maximum execution time of 30 seconds exceeded...===<br />
<br />
If your server uses a main language other than English, you may encounter a 'Fatal error: Maximum execution time of 30 seconds exceeded' when you try to upgrade it. You can increase max_execution_time = 160 on php.ini to allow the scripts enough time to process the language update. Otherwise, you can switch to English as the default language before doing the upgrade and back to your original language after a succcessful upgrade. See the forum discussion at https://moodle.org/mod/forum/discuss.php?d=119598.<br />
<br />
==After upgrading==<br />
<br />
The config.php file from your installation should work fine but if you take a look at config-dist.php that came with Moodle 2.7 there are more/different options available (e.g. database drivers and settings). It's a good idea to map your old config.php settings to a new one based on the 2.7 config-dist.php.<br />
<br />
===Assignments===<br />
<br />
The old assignment (2.2) module has been removed from core and has been replaced by a stub to support transparently remapping URLs and restoring course backups from the old module to the new one. <br />
<br />
If you are still using the old assignment (2.2) module, after upgrading to Moodle 2.7 all assignment (2.2) activities will be hidden. You need to run the [[Assignment upgrade tool]] to un-hide the activities.<br />
<br />
If you really, really need to keep using the old assignment (2.2) module, you should update the code to Moodle 2.7, and then replace the "mod/assignment" folder with the one from https://github.com/moodlehq/moodle-mod_assignment/releases before completing the upgrade.<br />
<br />
==Possible issues that may affect you in Moodle 2.7==<br />
<br />
''Items to be added here...''<br />
<br />
=== Moodle 2.3, 2.4, 2.5 and 2.6 improvements ===<br />
<br />
Depending on which version you are upgrading from, please see the section 'Possible issues that may affect you' in the documentation<br />
<br />
* [https://docs.moodle.org/23/en/Upgrading Upgrading to Moodle 2.3]<br />
* [https://docs.moodle.org/24/en/Upgrading Upgrading to Moodle 2.4]<br />
* [https://docs.moodle.org/25/en/Upgrading Upgrading to Moodle 2.5]<br />
* [https://docs.moodle.org/26/en/Upgrading Upgrading to Moodle 2.6]<br />
<br />
==See also==<br />
<br />
* Using Moodle [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum] <br />
* [[dev:Moodle 2.7 release notes|Moodle 2.7 release notes]]<br />
* [[dev:Upgrade API|Upgrade API]]<br />
<br />
[[es:Actualización de moodle]]<br />
[[fr:Mise à jour]]<br />
[[ja:Moodleをアップグレードする]]<br />
[[de:Aktualisierung von Moodle]]</div>Deraadthttps://docs.moodle.org/30/en/index.php?title=Progress_Bar_block&diff=112375Progress Bar block2014-05-07T05:32:52Z<p>Deraadt: Updating after recent functional changes</p>
<hr />
<div>[[Blocks|Back to Blocks page]]<br />
<br />
== Features ==<br />
<br />
[[Image:Bar_in_block_-_with_details.png|right|A progress bar for a student]]<br />
* The Progress Bar is a time-management tool for students.<br />
* It visually shows what activities/resources a student is supposed to interact with in a course.<br />
* It is colour coded so students can quickly see what they have and have not completed/viewed.<br />
* The teacher selects which pre-existing activities/resources are to be included in the Progress Bar and when they should be completed/viewed.<br />
* Ordering can be done by times/deadlines or by the ordering of activities in the course.<br />
[[Image:Overview_of_students.png|thumb|right|The overview page]]<br />
* There is an overview page allowing teachers to see the progress of all students in a class, which is helpful for finding students at risk.<br />
<br />
<mediaplayer>http://www.youtube.com/watch?v=06LA5Cv9Fhw</mediaplayer><br />
<br />
== Installation ==<br />
<br />
The Progress Bar block is added like other blocks ([[Installing_contributed_modules_or_plugins|How to install a block]]).<br />
<br />
== Setting up a Progress Bar ==<br />
<br />
Once the progress bar is installed, you can use it in a course as follows.<br />
# Turn editing on<br />
# Create your activities/resources as normal<br />
# Add the Progress Bar block to your page ([[Blocks|How to add a block]])<br />
# Move your Progress Bar block into a prominent position (click and drag the block title)<br />
# Choose to:<br />
#* Monitor all activities (pre-fills configuration page)<br />
#* Select which activities to monitor (start from scratch)<br />
# Set the activities/resources you want shown in the block to "Yes" and those you don't to "No".<br />
# Set the date and time when the activity/resource is expected to be completed/viewed by (some activities have deadlines set, if so, that deadline can be used or another can be set in the Progress Bar block configuration).<br />
# Save changes.<br />
<br />
<mediaplayer>http://www.youtube.com/watch?v=ekH8IfCyGzM</mediaplayer><br />
<br />
Hidden items will not appear in the Progress Bar until they are unhidden. This is useful for a scheduled release of activities.<br />
<br />
== Links ==<br />
<br />
* [http://moodle.org/plugins/view.php?plugin=block_progress Block code in Plugins repository]<br />
* [http://tracker.moodle.org/browse/CONTRIB/component/10489 Bug Tracker Page] (Please report bugs here)<br />
* [http://cvs.moodle.org/contrib/plugins/blocks/progress/ CVS Repository]<br />
<br />
== Acknowledgements ==<br />
<br />
* Thanks to:<br />
** Toshimi Hatanaka for contributing a Japanese translation<br />
** Yvonne Schneider and Joachim Vogelgesang for contributing a German translation<br />
** Maria João Spilker for contributing a Portuguese-Brazilian translation<br />
** Pieter Wolters for contributing a Dutch translation<br />
** Fernando Sánchez for contributing a Spanish translation<br />
** Fabien Sartoretti for contributing a French translation<br />
** Adam Levy for contributing queries and strings for Hot Potatoes support<br />
** Petras Virzintas for contributing queries for Turnitin support<br />
** Willian Mano for helping with the modern look CSS<br />
** Matthieu Rolland for contributing queries for the Questionnaire module<br />
** Johan Reinalda for contributing global config changes for block colours<br />
<br />
[[Category:Contributed code]]</div>Deraadthttps://docs.moodle.org/30/en/index.php?title=Progress_Bar_block&diff=111738Progress Bar block2014-04-14T04:54:05Z<p>Deraadt: Adding Johan Reinalda's contribution</p>
<hr />
<div>[[Blocks|Back to Blocks page]]<br />
<br />
== Features ==<br />
<br />
[[Image:Bar_in_block_-_with_details.png|right|A progress bar for a student]]<br />
* The Progress Bar is a time-management tool for students.<br />
* It visually shows what activities/resources a student is supposed to interact with in a course.<br />
* It is colour coded so students can quickly see what they have and have not completed/viewed.<br />
* The teacher selects which pre-existing activities/resources are to be included in the Progress Bar and when they should be completed/viewed.<br />
* Ordering can be done by times/deadlines or by the ordering of activities in the course.<br />
[[Image:Overview_of_students.png|thumb|right|The overview page]]<br />
* There is an overview page allowing teachers to see the progress of all students in a class, which is helpful for finding students at risk.<br />
<br />
<mediaplayer>http://www.youtube.com/watch?v=d43KVlMBmLA </mediaplayer><br />
<br />
== Links ==<br />
<br />
* [http://moodle.org/plugins/view.php?plugin=block_progress Block code in Plugins repository]<br />
* [http://tracker.moodle.org/browse/CONTRIB/component/10489 Bug Tracker Page] (Please report bugs here)<br />
* [http://cvs.moodle.org/contrib/plugins/blocks/progress/ CVS Repository]<br />
<br />
== Installing ==<br />
<br />
The Progress Bar block is added like other blocks ([[Installing_contributed_modules_or_plugins|How to install a block]]).<br />
<br />
Once the progress bar is installed, you can use it in a course as follows.<br />
# Turn editing on<br />
# Create your activities/resources as normal<br />
# Add the Progress Bar block to your page ([[Blocks|How to add a block]])<br />
# Move your Progress Bar block into a prominent position, eg. top-left (click and drag the block title)<br />
# Click the Configuration icon on the block below the title<br />
# Give your Progress Bar block a title (default is "Progress Bar")<br />
# Set the activities/resources you want shown in the block to "Yes"<br />
# Set the date and time when the activity/resource is expected to be completed/viewed by (some activities have deadlines set, if so, that deadline can be used or another can be set in the Progress Bar block configuration)<br />
# Save changes<br />
<br />
Hidden items will not appear in the Progress Bar until they are unhidden. This is useful for a scheduled release of activities.<br />
<br />
== Acknowledgements ==<br />
<br />
* Thanks to:<br />
** Toshimi Hatanaka for contributing a Japanese translation<br />
** Yvonne Schneider and Joachim Vogelgesang for contributing a German translation<br />
** Maria João Spilker for contributing a Portuguese-Brazilian translation<br />
** Pieter Wolters for contributing a Dutch translation<br />
** Fernando Sánchez for contributing a Spanish translation<br />
** Fabien Sartoretti for contributing a French translation<br />
** Adam Levy for contributing queries and strings for Hot Potatoes support<br />
** Petras Virzintas for contributing queries for Turnitin support<br />
** Willian Mano for helping with the modern look CSS<br />
** Matthieu Rolland for contributing queries for the Questionnaire module<br />
** Johan Reinalda for contributing global config changes for block colours<br />
<br />
[[Category:Contributed code]]</div>Deraadthttps://docs.moodle.org/30/en/index.php?title=Assignment_settings&diff=111195Assignment settings2014-03-20T03:35:45Z<p>Deraadt: Undo revision 111194 by Deraadt (talk)</p>
<hr />
<div>{{Assignment}}<br />
<p class="note">'''Note''': This page describes settings for the new Assignment module in Moodle 2.3 onwards. For documentation on Assignments (2.2) settings, see [https://docs.moodle.org/22/en/Assignment_settings Assignment settings] in the 2.2 docs.</p><br />
<br />
==Adding and editing an Assignment activity==<br />
*To add a new Assignment activity to your course, login with the appropriate access rights (e.g.editing teacher, course creator or administrator) and Turn Editing On. Within the required Week or Topic Block click Add and Activity or Resource link. <br />
*In the Add an activity or resource dialogue box that appears, select Assignment and click Add.<br />
*To edit an existing Assignment activity, login to your course with the appropriate access rights (e.g. editing teacher, course creator or administrator) and Turn Editing On. Select the Update icon against the relevant Assignment item.<br />
*Alternatively, after logging into your course simply click on the name of the Assignment activity you wish to edit and then click the Edit Settings link under Assignment administration within the Settings block.<br />
<br />
The following configuration options are available when creating or editing/updating any Assignment activity. Only General,Availability and Submission types are open by default;the others are collapsed. To expand everything, click the "Expand all" link top right. <br />
Click on any screenshot to see it full size.<br />
<br />
<br />
==General ==<br />
The General section allows you to give your assignment a name and description. <br />
{|<br />
|[[File:assignmentgeneral26.png|General settings for an assignment]]<br />
|}<br />
<br />
===Assignment name===<br />
Give your Assignment a name (e.g. “Report on Topic 1 Content”). The title entered here will be the name that learners see in the course content area. Learners will click on this name to view the details of the assignment and, if applicable, submit their work.<br />
<br />
===Description===<br />
Provide instructions for your students here so they are clear what they have to do. <br />
Click the icon on the left to expand the toolbar and drag the bottom right of the text box out to expand it.<br />
<br />
You can also provide information or resources related to the assignment, such as a video clip, an image, or a link to a webpage.<br />
<br />
===Display description on course page===<br />
Enabling this will display the description on the course page just below the link to the assignment activity.<br />
<br />
==Availability==<br />
{|<br />
|[[File:AssignAvailability.png|thumb|450px|Availability settings for an assignment]]<br />
|}<br />
<br />
<br />
===Allow submissions from===<br />
The Allow submissions from setting prevents students from submitting their assignment before the shown date. A teacher can to set a day, month, year and time (24 hour clock) from which learners can begin to submit their assignments. Please note that this setting does not hide the activity from the learners. Instead, the learner will see the activity, be able to view the instructions and use any materials you have included in the description, but the learner will not be able to submit or complete the assignment until the Allow submissions from date.<br />
<br />
This setting is enabled (ticked/checked) by default and is set at the day and time you added the assignment. To disable this, remove the tick/check.<br />
<br />
===Due date===<br />
The Due date setting establishes when the assignment is due. Submissions will still be allowed after this date, but any assignments submitted after this date are marked as late.<br />
<br />
This option allows an teacher to set a day, month, year and time (24 hour clock) before which learners must submit their assignment.<br />
<br />
By default the Due date is Enabled (ticked) and is set at 7 days ahead of the day and time you selected Add Assignment. To disable this feature, simply ensure the Enable checkbox is not marked. For more information on using the Due Date see Assignment FAQ<br />
<br />
Note: Assignments without a Due date will appear on the My home page with “No Due date” displayed.<br />
<br />
===Cut-off date===<br />
<br />
The Cut-off date is the date beyond which students will not be able to send in their assignment as the button for doing so will no longer be displayed. After that date (or time) a teacher may, on request, grant an extension by going to the class assignment grading screen, clicking the "Edit" column and choosing "grant extension" for the relevant student. <br />
<br />
For more details, see this Youtube screencast [http://www.youtube.com/watch?v=UaL0LzZwyYI&feature=share&list=UUCRg_EbhU9tdpLdiGGN1Mgg Assignment Extensions]<br />
<br />
===Always show description===<br />
This setting is used in conjunction with the Allow submissions from setting. If it is set to Yes, the assignment Description will become visible to students at the Allow submissions from date. If it is set to No, the assignment Description will be hidden from students until the Allow submissions from date, only the assignment Name will be displayed as shown in the screenshot below. (Click to see full size.)<br />
{|<br />
|[[File:alwaysshowdescription.png|thumb|450px|Always show description]]<br />
|}<br />
<br />
If Allow submissions from is disabled, then this setting has no meaning: the assignment description will always be visible to students.<br />
<br />
==Submission types==<br />
<br />
{|<br />
|[[File:26submissioncomments.png|thumb|450px|Select the type of submission here]]<br />
|}<br />
Here you can decide how you wish students to submit their work to you. <br />
<br />
''Note that if Submission comments are enabled in ''Administration>Plugins>Activity modules>Assignment>Submission plugins'' then students will be able to add a note to their teacher on submitting work. If Blind marking is enabled, student comments display as from "Participant 01 etc" to avoid revealing identities. These comments will appear in the grading table in the Submission comments column.''<br />
<br />
===Online text===<br />
Learners can type their response directly in Moodle using the text editor.<br />
<br />
===File submissions===<br />
Learners can upload and edit one or more files of any type the teacher can open.<br />
<br />
If the student uploads a pdf file, the teacher can annotate it within the browser, and on saving, the annotated file is made available to the student. See section 5.3.1 Annotating pdfs in [[Using Assignment]]<br />
<br />
Note: This requires Ghostscript to be enabled on the server. This can be checked in ''Administration>Site administration>Plugins>Activity modules>Assignments>Feedback plugins>Annotate pdf''.<br />
<br />
===Maximum number of uploaded files===<br />
Here you can decide the maximum number of files which may be uploaded by each learner. (It might be helpful to display the number in the assignment description.)<br />
<br />
===Maximum submission size===<br />
This setting specifies the maximum size per file of each of the files that the students can upload as part of their submission. This maximum upload size may only be equal to or less than the course limit (which in turn may only be equal to or less than the site limit). The maximum size of each file is displayed to students at the point where they upload files.<br />
<br />
{|<br />
|[[File:submission comments.jpg|thumb|Submission comments]]<br />
|[[File:maximum file size.jpg|thumb|Maximum file size]]<br />
|}<br />
<br />
==Feedback types==<br />
(This setting is collapsed by default)<br />
<br />
{|<br />
|[[File:feedbacktypes.png|Feedback types]]<br />
|}<br />
<br />
===Feedback comments===<br />
Setting this to yes means that markers can leave feedback comments for each submission. It enables the Feedback Comments column in the grading table.(To access the grading table, click on the assignment activity and then ''View/Grade all Submissions'').<br />
Feedback comments are also accessible by clicking on the green tick in the grade column on the grading table.<br />
<br />
{|<br />
|[[File:feedback comments.jpg|thumb|The Feedback comments column]]<br />
|[[FIle:feedback comments 2.jpg|thumb|Type feedback comments into the box]]<br />
|}<br />
<br />
===Offline grading worksheet===<br />
<br />
If set to yes, the teacher will have a link to download the grading list as a spreadsheet. They will then be able to enter grades and feedback comments offline:<br />
<br />
{|<br />
|[[File:emptygradebook.png|thumb|The empty gradebook on Moodle]]<br />
|[[File:downloadgradingworksheet.png|thumb|The dropdown to download the list]]<br />
|[[File:excelgrades.png|thumb|Editing the grades offline]]<br />
|}<br />
<br />
When the teacher has completed their grading offline, they can then upload the spreadsheet, confirm the changes and the grades and comments will be transferred over into Moodle's gradebook:<br />
<br />
{|<br />
|[[File:uploadgradingworksheet.png|thumb|Uploading the grading worksheet]]<br />
|[[File:confirmchanges.png|thumb|Confirming the changes]]<br />
|[[File:fullgradebook.png|thumb|Grades and feedback transferred into Moodle]]<br />
|}<br />
<br />
See also [http://www.somerandomthoughts.com/blog/2012/11/19/offline-grading-worksheet-in-moodle-2-4-assignment/ Offline grading worksheet] blog post by Gavin Henrick.<br />
<br />
===Feedback files===<br />
This allows markers to upload files with feedback when marking. These files may be the marked up student assignments, documents with comments, a completed marking guide, or spoken audio feedback. It enables the Feedback Files column in the grading table. (To access the grading table click on the assignment activity and then ''View/Grade all Submissions'')To upload feedback files, click on the green tick in the grade column on the grading table and then upload either with drag and drop or using the [[File picker]].<br />
<br />
Feedback is displayed to students on the assignment submission page. <br />
<br />
{|<br />
|[[File:feedback files.jpg|thumb|The Feedback files column]]<br />
|[[File:feedback files 2.jpg|thumb|Upload files here]]<br />
|[[File:feedback view for students.jpg|thumb|Student view with comments and file feedback both enabled]]<br />
|}<br />
====Uploading multiple feedback files====<br />
<br />
It is also possible to upload multiple feedback files as a zip, from the dropdown above the grading list:<br />
<br />
#Download the students' assignments using the "Download all submissions" link from the same dropdown menu;<br />
#Extract the folder offline and add your comments to the student's submissions.Keep the names the same.<br />
#Select the students' submissions and zip them into a new folder. Important: Don't just edit them inside their original folder and re-zip this; it will not work. The folder name does not matter as long as the feedback files have the same names as before.<br />
#Upload this newly zipped folder.<br />
#You will be presented with a confirmation screen displaying your feedback files.<br />
<br />
{|<br />
|[[File:mutiplefeedbackzip.png|thumb|Choose from the dropdown menu]]<br />
|[[File:multiplezip1.png|thumb|Confirmation screen displaying the feedback files to be uploaded]]<br />
|[[File:multiplezip2.png|thumb|Screen confirming uploaded feedback]]<br />
|}<br />
<br />
''Note:''If you zip files on a Mac, you may get a folder included in the zip called _MACOSX_ which needs to be removed otherwise moodle will not recognise the changes in the files.<br />
<br />
==Submission settings==<br />
(This setting is collapsed by default)<br />
<br />
{|<br />
|[[File:submissionsettings.png|Submission settings]]<br />
|}<br />
===Require students click submit button===<br />
Students can upload draft versions of the assignment until such time as they are ready to submit.Once they click the submit button they indicate to the teacher that they have finished working on the assignment. In earlier versions of Moodle this was called ''"Send for marking"''.)<br />
<br />
They can then longer edit their submission. If they need to change it, they must ask the teacher who can revert the assignment to draft status.<br />
<br />
To revert to the draft stage, click on the assignment activity and then View/Grade all Submissions. Locate the student and click the action icon in the Edit column. Select Revert the submission to draft.<br />
<br />
If this setting is No, then students do not have to to click a submit button and are able to make changes to uploaded files at any time.<br />
<br />
If this setting is No but the teacher wishes to grade students work, then you can stop students from making further changes by using Prevent submission changes. Prevent submission changes can also be used in cases where students have neglected to click the Submit button and grading has commenced.<br />
To prevent submission changes, click on the assignment activity, then click on the View/Grade all submissions button. On the grading table, locate the student and click the action icon in the Edit column. Select Prevent submission changes.<br />
<br />
To do either of these with a number of students, use the ''With selected'' menu at the bottom of the grading table.<br />
<br />
{|<br />
|[[File:revert to draft.jpg|thumb|Reverting to draft]]<br />
|[[File:prevent submission changes.jpg|thumb|Prevent submission changes]]<br />
|[[File:with selected.jpg|thumb|"With selected"..]]<br />
|}<br />
<br />
To do either of these with a number of students, use the ''With selected'' menu at the bottom of the grading table.<br />
<br />
===Require that students accept the Submission statement===<br />
<br />
An administrator can define a "Submission statement", ie, a statement where students promise the work is their own and which they must agree to before submitting their work. This may be done via ''Settings>Site administration>Plugins>Activity modules>Assignment.''<br />
<br />
If preferred, the available default statement which may be used instead: ''This assignment is my own work, except where I have acknowledged the use of the works of other people'' <br />
<br />
If the administrator has given teachers the option of using a submission statement or not, then it will be available in the assignment settings screen. The section [[#Submission_Statement]] explains how an administrator can set this up.<br />
<br />
For more details, see this blog post [http://ourlearning.co.uk/2012/10/moodle-assignment-all-my-own-work/ "All my own work"]<br />
<br />
When this setting is enabled, students will have to check a button before they can submit their assignment:<br />
<br />
If the administrator has forced the statement throughout the site, a teacher will not have this option in the settings but a student will see the statement when accessing their assignment.<br />
<br />
===Attempts reopened===<br />
<br />
This setting allows the teacher to decide how submissions are reopened. The default is "Never", in that students may only submit once. However, a teacher can set this to "Manually" and reopen it themselves for the student to resubmit, or to "Automatically until pass". The student must then keep trying and resubmitting until they get a pass grade. [[Grade_items#Activity-based_grade_items|Passing grades]] are set in the Gradebook.<br />
<br />
===Maximum attempts===<br />
<br />
If a student is allowed to resubmit, this setting will determine how many times they can resubmit before they are no longer allowed to do so. (For example, if a student has to keep trying until they get a pass grade, the teacher might decide that ten attempts is enough even though they have not yet passed!)<br />
<br />
==Groups submission settings==<br />
(This setting is collapsed by default)<br />
{|<br />
|[[File:groupsubmissionsettings.png|Group submission settings]]<br />
|}<br />
<br />
===Students submit in groups===<br />
<br />
If this box is ticked, then students are able to collaborate on an assignment. This might involve for example, working in the same online text area, or one student uploading an MS Powerpoint which another student downloads, improves and re-uploads to the common assignment area.<br />
<br />
When grading, the teacher may choose to give a common grade and feedback to all students in the group or to give individual grades and feedback to each member.<br />
<br />
If no groups have been made, then Moodle will make a default group of every student in the course.<br />
<br />
For more details see this Youtube video [http://www.youtube.com/watch?v=G16gYZJFCrM&feature=share&list=UUCRg_EbhU9tdpLdiGGN1Mgg Group Assignment 2.4]<br />
<br />
===Require all group members submit===<br />
<br />
This setting will only appear if the teacher has ticked the "Require students click submit button" earlier. The assignment will not be classed as "submitted" until all members of the group have made a contribution. When one student has submitted, the other members of the group will be able to see who still has to submit.<br />
<br />
===Grouping for student groups===<br />
If a particular grouping is selected here, then the gradebook will display any other groups and non-grouped students in the "default group", while naming the group(s) that are in the chosen grouping. If "none" is selected, then the gradebook will display the names of all groups and put any non-grouped students in the "default group". See this [https://moodle.org/mod/forum/discuss.php?d=216399#p942913 forum post on grouping for student groups] for examples of how this might be used.<br />
<br />
==Notifications==<br />
(This setting is collapsed by default)<br />
<br />
{|<br />
|[[File:notifications25.png|Notifications]]<br />
|}<br />
===Notify graders about submissions===<br />
Teachers will receive a message (of a type they choose) whenever a student submits an assignment. Please note if you are using the assignment in Groups Mode (eg Separate or Visible Groups), the teacher will need to be a member of the group in order to receive the submission notification.<br />
===Notify graders about late submission===<br />
Teachers will receive a message (of a type they choose)whenever a student submits a late assignment. Please note if you are using the assignment in Groups Mode (eg Separate or Visible Groups), the teacher will need to be a member of the group in order to receive the submission notification.<br />
<br />
==Grade==<br />
(This setting is collapsed by default)<br />
{|<br />
|[[File:grade25.png|Grade]]<br />
|}<br />
<br />
===Grade===<br />
Specify the maximum grade or [[Scales|Scale]] to be applied to the assignment. If you will not be giving a grade for the assignment, choose No Grade.<br />
<br />
===Grading method===<br />
<br />
There are 3 options:<br />
* Simple direct grading (entering a grade or scale item)<br />
* [[Marking guide]]<br />
* [[Rubric]]<br />
<br />
===Grade Category===<br />
Any custom [[Grade_categories|Grade Categories]] that have been created within your site or course will be listed here and will be available for selection. Select the required Grade Category to add this assignment as a [[Grade_items|Grade item]] within this Category.<br />
<br />
<br />
===Blind marking===<br />
<br />
If this setting is enabled, then a teacher will not see the names of students who have submitted their assignments. Instead, they will see randomly generated Participant numbers. (The student view of the assignment does not change.) This is also the case if student comments have been enabled. Once they have graded the assignment, it is however possible for teachers to see who submitted what by clicking on "Reveal student identities" in the Assignment settings.<br />
<br />
====Returning Marks to Students ====<br />
Because of the nature of blind marking, the students cannot see the final grade until all of the students names have been revealed. This is found in Assignment Settings > Reveal Student Names. However, feedback comments will appear.<br />
<br />
''Note:'' Beacuse of this, the level of anonymity might not suit the privacy requirements of your establishment. See this tracker entry MDL-35390 - "Blind Marking is not so blind"<br />
<br />
For more details on this feature, see this Youtube video [http://youtu.be/Biiw3E13mgM Blind marking in 2.4].<br />
<br />
===Use marking workflow===<br />
{{New features}}<br />
When set to Yes, teachers will be able to specify the stage they are at in their grading of individual assignments (as in the screenshot below)<br />
<br />
{|<br />
|[[File:26markingworkflow.png|thumb|Marking workflow state in the individual grading screen]]<br />
|[[File:26quickgradingworkflow.png|thumb|Dropdown to select marking workflow state when quick grading]]<br />
|}<br />
<br />
One advantage of using marking workflow is that the grades can be hidden from students until they are set to 'Released'. The actual list of steps are:<br />
<br />
* Not marked (the marker has not yet started) <br />
* In marking (the marker has started but not yet finished) <br />
* Marking completed (the marker has finished but might need to go back for checking/corrections) <br />
* In review (the marking is now with the teacher in charge for quality checking) <br />
* Ready for release (the teacher in charge is satisfied with the marking but wait before giving students access to the marking) <br />
* Released (the student can access the grades/feedback)<br />
<br />
====Example use cases====<br />
<br />
One marker, Marker, wants to release all grades at the same time <br />
* Marker enables "Use marking workflow" <br />
* Marker marks each submission and transitions the grading to "Marking completed" as each submission is graded. <br />
* Marker then uses the batch operations to transition all grades to "Released" at the same time. <br />
<br />
Multiple markers, <br />
* Marker enables "Use marking workflow" <br />
* Marker marks each submission and transitions the grading to "Marking completed" as each submission is graded. <br />
* Marker then uses the batch operations to transition all grades to "Released" at the same time.<br />
<br />
===Use marking allocation===<br />
{{New features}}<br />
If marking workflow (see above) is set to Yes, it is possible to enable marking allocation. This means that teachers can be selected to grade or review the submitted work of specific students. Colleagues can monitor progress through the displayed marking workflow states:<br />
<br />
{|<br />
|[[File:26markingworkflowallocatedmarkers.png|thumb|Allocated markers on the grading screen]]<br />
|}<br />
<br />
==Common module settings==<br />
See [[Common module settings]]<br />
<br />
==Restrict access settings==<br />
The [[Restrict_access_settings|Restrict access]] area becomes visible in Moodle activities and resource settings if [[Conditional_activities|Conditional Activities]] have been enabled.<br />
<br />
==Locally assigned roles==<br />
<br />
In ''Settings > Assignment administration > Locally assigned roles'' selected users can be given additional roles in the activity. See the Using Moodle [http://moodle.org/mod/forum/discuss.php?d=98208 Custom role for 'Course Monitor'] forum discussion for an example.<br />
<br />
==Assignment capabilities==<br />
<br />
* [[Capabilities/mod/assign:exportownsubmission|Export own submission]]<br />
* [[Capabilities/mod/assign:grade|Grade assignment]]<br />
* [[Capabilities/mod/assign:submit|Submit assignment]]<br />
* [[Capabilities/mod/assign:view|View assignment]]<br />
<br />
Role permissions for the activity can be changed in ''Settings > Assignment administration > Permissions''.<br />
<br />
==Site administration settings==<br />
<br />
The following configuration options are available for an administrator under ''Administration > Site administration > Plugins > Activity modules > Assignment''.<br />
<br />
<br />
===Assignment settings===<br />
====Feedback plugin====<br />
The comments that are pushed to the gradebook from the assignment are limited to a single text only comment. An Administrator can specify which of the feedback plugins will be push comments to the gradebook. On a standard Moodle install the choices are "Feedback comments" (default) or "Feedback file" but there may be additional options if your Moodle install contains additional feedback plugins.<br />
<br />
====Show recent submissions====<br />
This option allows everyone to see notifications of submissions in [[Recent activity]] reports and the Recent Activity Block, within a course context. Note that the default for this option is No which means students will not be able to see when classmates have submitted or updated any Assignments.<br />
<br />
====Send submission receipt to students====<br />
This switch will enable submission receipts for students. Students will receive a notification every time they successfully submit an assignment.<br />
{|<br />
|[[File:ass_settings.jpg|thumb|350px|Submission receipts settings]]<br />
|}<br />
<br />
====Submission Statement====<br />
<br />
An administrator can enter text in the box here which will appear when students are about to submit their assignment. <br />
<br />
{|<br />
|[[File:newsubmissionstatement.png|thumb|Admin view of Submission statement set up screen - click to enlarge]]<br />
|[[File:submissionstatement.png|thumb|Student view when about to submit - click to enlarge]]<br />
|}<br />
<br />
<br />
If it is left as the default "No", then teachers will have the choice within their own assignments to force this or not.<br />
<br />
====Default assignment settings====<br />
{{New features}}<br />
The administrator can specify here the default assignment settings which may be set as 'Advanced' (ie, they will appear when clicking 'Show more') or 'Locked' (ie the teacher cannot change them.)<br />
{|<br />
|[[File:26assignmentdefaults.png|thumb|Default, Advanced and Locked checkboxes]]<br />
|}<br />
<br />
<br />
The following configuration options are available for an administrator under ''Administration > Site administration > Plugins > Assignment''. <br />
<br />
===Submission plugins===<br />
====Manage assignment submission plugins====<br />
Here you can change the order, check the settings or uninstall a particular submission plugin.<br />
====File submissions====<br />
'''Enabled by default''' If set, this submission method will be enabled by default for all new assignments.<br />
<br />
'''Maximum submission size''' An Administrator can specify the maximum size of any individual file uploaded within the assignment module across all courses on the site. This limit may be equal to or less than course file upload limit.<br />
<br />
====Online text submissions====<br />
'''Enabled by default''' If set, this submission method will be enabled by default for all new assignments.<br />
<br />
====Submission comments====<br />
<br />
'''Enabled by default''' If set, students will be able to send a message to their teacher when submitting their assignment.<br />
<br />
===Feedback plugins===<br />
====Manage assignment feedback plugins====<br />
Here you can change the order, check the settings or uninstall a particular feedback plugin.<br />
====Feedback comments====<br />
'''Enabled by default''' If set, this submission method will be enabled by default for all new assignments.<br />
====Annotate pdf====<br />
<br />
Here you can upload stamps for teachers to use when annotating student pdfs. You can also check the ghostscript path:<br />
{|<br />
|[[File:Selection_116.png|thumb|Ghostscript not installed or incorrectly installed]]<br />
|[[File:Selection_115.png|thumb|Ghostscript correctly installed]]<br />
|}<br />
<br />
If the default stamps are deleted by accident, they can be found in mod/assign/feedback/editpdf/pix and re-uploaded.<br />
<br />
====File feedback====<br />
'''Enabled by default''' If set, this submission method will be enabled by default for all new assignments.<br />
<br />
===Offline grading worksheet===<br />
<br />
'''Enabled by default''' If set, this will be enabled by default for all new assignments<br />
<br />
==See also==<br />
Synergy Learning blog post: [http://www.synergy-learning.com/moodle-2-5-improvements-assignment-resubmissions/ Assignment resubmissions]<br />
[[de:Aufgabe konfigurieren]]<br />
[[fr:Ajouter/modifier un devoir]]<br />
[[ja:課題を追加/編集する]]<br />
[[es:Configuraciones de tarea]]</div>Deraadthttps://docs.moodle.org/30/en/index.php?title=Assignment_settings&diff=111194Assignment settings2014-03-20T03:30:09Z<p>Deraadt: Fixing link with target</p>
<hr />
<div>{{Assignment}}<br />
<p class="note">'''Note''': This page describes settings for the new Assignment module in Moodle 2.3 onwards. For documentation on Assignments (2.2) settings, see [https://docs.moodle.org/22/en/Assignment_settings Assignment settings] in the 2.2 docs.</p><br />
<br />
==Adding and editing an Assignment activity==<br />
*To add a new Assignment activity to your course, login with the appropriate access rights (e.g.editing teacher, course creator or administrator) and Turn Editing On. Within the required Week or Topic Block click Add and Activity or Resource link. <br />
*In the Add an activity or resource dialogue box that appears, select Assignment and click Add.<br />
*To edit an existing Assignment activity, login to your course with the appropriate access rights (e.g. editing teacher, course creator or administrator) and Turn Editing On. Select the Update icon against the relevant Assignment item.<br />
*Alternatively, after logging into your course simply click on the name of the Assignment activity you wish to edit and then click the Edit Settings link under Assignment administration within the Settings block.<br />
<br />
The following configuration options are available when creating or editing/updating any Assignment activity. Only General,Availability and Submission types are open by default;the others are collapsed. To expand everything, click the "Expand all" link top right. <br />
Click on any screenshot to see it full size.<br />
<br />
<br />
==General ==<br />
The General section allows you to give your assignment a name and description. <br />
{|<br />
|[[File:assignmentgeneral26.png|General settings for an assignment]]<br />
|}<br />
<br />
===Assignment name===<br />
Give your Assignment a name (e.g. “Report on Topic 1 Content”). The title entered here will be the name that learners see in the course content area. Learners will click on this name to view the details of the assignment and, if applicable, submit their work.<br />
<br />
===Description===<br />
Provide instructions for your students here so they are clear what they have to do. <br />
Click the icon on the left to expand the toolbar and drag the bottom right of the text box out to expand it.<br />
<br />
You can also provide information or resources related to the assignment, such as a video clip, an image, or a link to a webpage.<br />
<br />
===Display description on course page===<br />
Enabling this will display the description on the course page just below the link to the assignment activity.<br />
<br />
==Availability==<br />
{|<br />
|[[File:AssignAvailability.png|thumb|450px|Availability settings for an assignment]]<br />
|}<br />
<br />
<br />
===Allow submissions from===<br />
The Allow submissions from setting prevents students from submitting their assignment before the shown date. A teacher can to set a day, month, year and time (24 hour clock) from which learners can begin to submit their assignments. Please note that this setting does not hide the activity from the learners. Instead, the learner will see the activity, be able to view the instructions and use any materials you have included in the description, but the learner will not be able to submit or complete the assignment until the Allow submissions from date.<br />
<br />
This setting is enabled (ticked/checked) by default and is set at the day and time you added the assignment. To disable this, remove the tick/check.<br />
<br />
===Due date===<br />
The Due date setting establishes when the assignment is due. Submissions will still be allowed after this date, but any assignments submitted after this date are marked as late.<br />
<br />
This option allows an teacher to set a day, month, year and time (24 hour clock) before which learners must submit their assignment.<br />
<br />
By default the Due date is Enabled (ticked) and is set at 7 days ahead of the day and time you selected Add Assignment. To disable this feature, simply ensure the Enable checkbox is not marked. For more information on using the Due Date see Assignment FAQ<br />
<br />
Note: Assignments without a Due date will appear on the My home page with “No Due date” displayed.<br />
<br />
===Cut-off date===<br />
<br />
The Cut-off date is the date beyond which students will not be able to send in their assignment as the button for doing so will no longer be displayed. After that date (or time) a teacher may, on request, grant an extension by going to the class assignment grading screen, clicking the "Edit" column and choosing "grant extension" for the relevant student. <br />
<br />
For more details, see this Youtube screencast [http://www.youtube.com/watch?v=UaL0LzZwyYI&feature=share&list=UUCRg_EbhU9tdpLdiGGN1Mgg Assignment Extensions]<br />
<br />
===Always show description===<br />
This setting is used in conjunction with the Allow submissions from setting. If it is set to Yes, the assignment Description will become visible to students at the Allow submissions from date. If it is set to No, the assignment Description will be hidden from students until the Allow submissions from date, only the assignment Name will be displayed as shown in the screenshot below. (Click to see full size.)<br />
{|<br />
|[[File:alwaysshowdescription.png|thumb|450px|Always show description]]<br />
|}<br />
<br />
If Allow submissions from is disabled, then this setting has no meaning: the assignment description will always be visible to students.<br />
<br />
==Submission types==<br />
<br />
{|<br />
|[[File:26submissioncomments.png|thumb|450px|Select the type of submission here]]<br />
|}<br />
Here you can decide how you wish students to submit their work to you. <br />
<br />
''Note that if Submission comments are enabled in ''Administration>Plugins>Activity modules>Assignment>Submission plugins'' then students will be able to add a note to their teacher on submitting work. If Blind marking is enabled, student comments display as from "Participant 01 etc" to avoid revealing identities. These comments will appear in the grading table in the Submission comments column.''<br />
<br />
===Online text===<br />
Learners can type their response directly in Moodle using the text editor.<br />
<br />
===File submissions===<br />
Learners can upload and edit one or more files of any type the teacher can open.<br />
<br />
If the student uploads a pdf file, the teacher can annotate it within the browser, and on saving, the annotated file is made available to the student. See section 5.3.1 Annotating pdfs in [[Using Assignment]]<br />
<br />
Note: This requires Ghostscript to be enabled on the server. This can be checked in ''Administration>Site administration>Plugins>Activity modules>Assignments>Feedback plugins>Annotate pdf''.<br />
<br />
===Maximum number of uploaded files===<br />
Here you can decide the maximum number of files which may be uploaded by each learner. (It might be helpful to display the number in the assignment description.)<br />
<br />
===Maximum submission size===<br />
This setting specifies the maximum size per file of each of the files that the students can upload as part of their submission. This maximum upload size may only be equal to or less than the course limit (which in turn may only be equal to or less than the site limit). The maximum size of each file is displayed to students at the point where they upload files.<br />
<br />
{|<br />
|[[File:submission comments.jpg|thumb|Submission comments]]<br />
|[[File:maximum file size.jpg|thumb|Maximum file size]]<br />
|}<br />
<br />
==Feedback types==<br />
(This setting is collapsed by default)<br />
<br />
{|<br />
|[[File:feedbacktypes.png|Feedback types]]<br />
|}<br />
<br />
===Feedback comments===<br />
Setting this to yes means that markers can leave feedback comments for each submission. It enables the Feedback Comments column in the grading table.(To access the grading table, click on the assignment activity and then ''View/Grade all Submissions'').<br />
Feedback comments are also accessible by clicking on the green tick in the grade column on the grading table.<br />
<br />
{|<br />
|[[File:feedback comments.jpg|thumb|The Feedback comments column]]<br />
|[[FIle:feedback comments 2.jpg|thumb|Type feedback comments into the box]]<br />
|}<br />
<br />
===Offline grading worksheet===<br />
<br />
If set to yes, the teacher will have a link to download the grading list as a spreadsheet. They will then be able to enter grades and feedback comments offline:<br />
<br />
{|<br />
|[[File:emptygradebook.png|thumb|The empty gradebook on Moodle]]<br />
|[[File:downloadgradingworksheet.png|thumb|The dropdown to download the list]]<br />
|[[File:excelgrades.png|thumb|Editing the grades offline]]<br />
|}<br />
<br />
When the teacher has completed their grading offline, they can then upload the spreadsheet, confirm the changes and the grades and comments will be transferred over into Moodle's gradebook:<br />
<br />
{|<br />
|[[File:uploadgradingworksheet.png|thumb|Uploading the grading worksheet]]<br />
|[[File:confirmchanges.png|thumb|Confirming the changes]]<br />
|[[File:fullgradebook.png|thumb|Grades and feedback transferred into Moodle]]<br />
|}<br />
<br />
See also [http://www.somerandomthoughts.com/blog/2012/11/19/offline-grading-worksheet-in-moodle-2-4-assignment/ Offline grading worksheet] blog post by Gavin Henrick.<br />
<br />
===Feedback files===<br />
This allows markers to upload files with feedback when marking. These files may be the marked up student assignments, documents with comments, a completed marking guide, or spoken audio feedback. It enables the Feedback Files column in the grading table. (To access the grading table click on the assignment activity and then ''View/Grade all Submissions'')To upload feedback files, click on the green tick in the grade column on the grading table and then upload either with drag and drop or using the [[File picker]].<br />
<br />
Feedback is displayed to students on the assignment submission page. <br />
<br />
{|<br />
|[[File:feedback files.jpg|thumb|The Feedback files column]]<br />
|[[File:feedback files 2.jpg|thumb|Upload files here]]<br />
|[[File:feedback view for students.jpg|thumb|Student view with comments and file feedback both enabled]]<br />
|}<br />
====Uploading multiple feedback files====<br />
<br />
It is also possible to upload multiple feedback files as a zip, from the dropdown above the grading list:<br />
<br />
#Download the students' assignments using the "Download all submissions" link from the same dropdown menu;<br />
#Extract the folder offline and add your comments to the student's submissions.Keep the names the same.<br />
#Select the students' submissions and zip them into a new folder. Important: Don't just edit them inside their original folder and re-zip this; it will not work. The folder name does not matter as long as the feedback files have the same names as before.<br />
#Upload this newly zipped folder.<br />
#You will be presented with a confirmation screen displaying your feedback files.<br />
<br />
{|<br />
|[[File:mutiplefeedbackzip.png|thumb|Choose from the dropdown menu]]<br />
|[[File:multiplezip1.png|thumb|Confirmation screen displaying the feedback files to be uploaded]]<br />
|[[File:multiplezip2.png|thumb|Screen confirming uploaded feedback]]<br />
|}<br />
<br />
''Note:''If you zip files on a Mac, you may get a folder included in the zip called _MACOSX_ which needs to be removed otherwise moodle will not recognise the changes in the files.<br />
<br />
==Submission settings==<br />
(This setting is collapsed by default)<br />
<br />
{|<br />
|[[File:submissionsettings.png|Submission settings]]<br />
|}<br />
===Require students click submit button===<br />
Students can upload draft versions of the assignment until such time as they are ready to submit.Once they click the submit button they indicate to the teacher that they have finished working on the assignment. In earlier versions of Moodle this was called ''"Send for marking"''.)<br />
<br />
They can then longer edit their submission. If they need to change it, they must ask the teacher who can revert the assignment to draft status.<br />
<br />
To revert to the draft stage, click on the assignment activity and then View/Grade all Submissions. Locate the student and click the action icon in the Edit column. Select Revert the submission to draft.<br />
<br />
If this setting is No, then students do not have to to click a submit button and are able to make changes to uploaded files at any time.<br />
<br />
If this setting is No but the teacher wishes to grade students work, then you can stop students from making further changes by using Prevent submission changes. Prevent submission changes can also be used in cases where students have neglected to click the Submit button and grading has commenced.<br />
To prevent submission changes, click on the assignment activity, then click on the View/Grade all submissions button. On the grading table, locate the student and click the action icon in the Edit column. Select Prevent submission changes.<br />
<br />
To do either of these with a number of students, use the ''With selected'' menu at the bottom of the grading table.<br />
<br />
{|<br />
|[[File:revert to draft.jpg|thumb|Reverting to draft]]<br />
|[[File:prevent submission changes.jpg|thumb|Prevent submission changes]]<br />
|[[File:with selected.jpg|thumb|"With selected"..]]<br />
|}<br />
<br />
To do either of these with a number of students, use the ''With selected'' menu at the bottom of the grading table.<br />
<br />
===Require that students accept the Submission statement===<br />
<br />
An administrator can define a "Submission statement", ie, a statement where students promise the work is their own and which they must agree to before submitting their work. This may be done via ''Settings>Site administration>Plugins>Activity modules>Assignment.''<br />
<br />
If preferred, the available default statement which may be used instead: ''This assignment is my own work, except where I have acknowledged the use of the works of other people'' <br />
<br />
If the administrator has given teachers the option of using a submission statement or not, then it will be available in the assignment settings screen. The section [[#Submission_Statement]] explains how an administrator can set this up.<br />
<br />
For more details, see this blog post [http://ourlearning.co.uk/2012/10/moodle-assignment-all-my-own-work/ "All my own work"]<br />
<br />
When this setting is enabled, students will have to check a button before they can submit their assignment:<br />
<br />
If the administrator has forced the statement throughout the site, a teacher will not have this option in the settings but a student will see the statement when accessing their assignment.<br />
<br />
===Attempts reopened===<br />
<br />
This setting allows the teacher to decide how submissions are reopened. The default is "Never", in that students may only submit once. However, a teacher can set this to "Manually" and reopen it themselves for the student to resubmit, or to "Automatically until pass". The student must then keep trying and resubmitting until they get a pass grade. [[:en:Grade_items#Activity-based_grade_items|Passing grades]] are set in the Gradebook.<br />
<br />
===Maximum attempts===<br />
<br />
If a student is allowed to resubmit, this setting will determine how many times they can resubmit before they are no longer allowed to do so. (For example, if a student has to keep trying until they get a pass grade, the teacher might decide that ten attempts is enough even though they have not yet passed!)<br />
<br />
==Groups submission settings==<br />
(This setting is collapsed by default)<br />
{|<br />
|[[File:groupsubmissionsettings.png|Group submission settings]]<br />
|}<br />
<br />
===Students submit in groups===<br />
<br />
If this box is ticked, then students are able to collaborate on an assignment. This might involve for example, working in the same online text area, or one student uploading an MS Powerpoint which another student downloads, improves and re-uploads to the common assignment area.<br />
<br />
When grading, the teacher may choose to give a common grade and feedback to all students in the group or to give individual grades and feedback to each member.<br />
<br />
If no groups have been made, then Moodle will make a default group of every student in the course.<br />
<br />
For more details see this Youtube video [http://www.youtube.com/watch?v=G16gYZJFCrM&feature=share&list=UUCRg_EbhU9tdpLdiGGN1Mgg Group Assignment 2.4]<br />
<br />
===Require all group members submit===<br />
<br />
This setting will only appear if the teacher has ticked the "Require students click submit button" earlier. The assignment will not be classed as "submitted" until all members of the group have made a contribution. When one student has submitted, the other members of the group will be able to see who still has to submit.<br />
<br />
===Grouping for student groups===<br />
If a particular grouping is selected here, then the gradebook will display any other groups and non-grouped students in the "default group", while naming the group(s) that are in the chosen grouping. If "none" is selected, then the gradebook will display the names of all groups and put any non-grouped students in the "default group". See this [https://moodle.org/mod/forum/discuss.php?d=216399#p942913 forum post on grouping for student groups] for examples of how this might be used.<br />
<br />
==Notifications==<br />
(This setting is collapsed by default)<br />
<br />
{|<br />
|[[File:notifications25.png|Notifications]]<br />
|}<br />
===Notify graders about submissions===<br />
Teachers will receive a message (of a type they choose) whenever a student submits an assignment. Please note if you are using the assignment in Groups Mode (eg Separate or Visible Groups), the teacher will need to be a member of the group in order to receive the submission notification.<br />
===Notify graders about late submission===<br />
Teachers will receive a message (of a type they choose)whenever a student submits a late assignment. Please note if you are using the assignment in Groups Mode (eg Separate or Visible Groups), the teacher will need to be a member of the group in order to receive the submission notification.<br />
<br />
==Grade==<br />
(This setting is collapsed by default)<br />
{|<br />
|[[File:grade25.png|Grade]]<br />
|}<br />
<br />
===Grade===<br />
Specify the maximum grade or [[Scales|Scale]] to be applied to the assignment. If you will not be giving a grade for the assignment, choose No Grade.<br />
<br />
===Grading method===<br />
<br />
There are 3 options:<br />
* Simple direct grading (entering a grade or scale item)<br />
* [[Marking guide]]<br />
* [[Rubric]]<br />
<br />
===Grade Category===<br />
Any custom [[Grade_categories|Grade Categories]] that have been created within your site or course will be listed here and will be available for selection. Select the required Grade Category to add this assignment as a [[Grade_items|Grade item]] within this Category.<br />
<br />
<br />
===Blind marking===<br />
<br />
If this setting is enabled, then a teacher will not see the names of students who have submitted their assignments. Instead, they will see randomly generated Participant numbers. (The student view of the assignment does not change.) This is also the case if student comments have been enabled. Once they have graded the assignment, it is however possible for teachers to see who submitted what by clicking on "Reveal student identities" in the Assignment settings.<br />
<br />
====Returning Marks to Students ====<br />
Because of the nature of blind marking, the students cannot see the final grade until all of the students names have been revealed. This is found in Assignment Settings > Reveal Student Names. However, feedback comments will appear.<br />
<br />
''Note:'' Beacuse of this, the level of anonymity might not suit the privacy requirements of your establishment. See this tracker entry MDL-35390 - "Blind Marking is not so blind"<br />
<br />
For more details on this feature, see this Youtube video [http://youtu.be/Biiw3E13mgM Blind marking in 2.4].<br />
<br />
===Use marking workflow===<br />
{{New features}}<br />
When set to Yes, teachers will be able to specify the stage they are at in their grading of individual assignments (as in the screenshot below)<br />
<br />
{|<br />
|[[File:26markingworkflow.png|thumb|Marking workflow state in the individual grading screen]]<br />
|[[File:26quickgradingworkflow.png|thumb|Dropdown to select marking workflow state when quick grading]]<br />
|}<br />
<br />
One advantage of using marking workflow is that the grades can be hidden from students until they are set to 'Released'. The actual list of steps are:<br />
<br />
* Not marked (the marker has not yet started) <br />
* In marking (the marker has started but not yet finished) <br />
* Marking completed (the marker has finished but might need to go back for checking/corrections) <br />
* In review (the marking is now with the teacher in charge for quality checking) <br />
* Ready for release (the teacher in charge is satisfied with the marking but wait before giving students access to the marking) <br />
* Released (the student can access the grades/feedback)<br />
<br />
====Example use cases====<br />
<br />
One marker, Marker, wants to release all grades at the same time <br />
* Marker enables "Use marking workflow" <br />
* Marker marks each submission and transitions the grading to "Marking completed" as each submission is graded. <br />
* Marker then uses the batch operations to transition all grades to "Released" at the same time. <br />
<br />
Multiple markers, <br />
* Marker enables "Use marking workflow" <br />
* Marker marks each submission and transitions the grading to "Marking completed" as each submission is graded. <br />
* Marker then uses the batch operations to transition all grades to "Released" at the same time.<br />
<br />
===Use marking allocation===<br />
{{New features}}<br />
If marking workflow (see above) is set to Yes, it is possible to enable marking allocation. This means that teachers can be selected to grade or review the submitted work of specific students. Colleagues can monitor progress through the displayed marking workflow states:<br />
<br />
{|<br />
|[[File:26markingworkflowallocatedmarkers.png|thumb|Allocated markers on the grading screen]]<br />
|}<br />
<br />
==Common module settings==<br />
See [[Common module settings]]<br />
<br />
==Restrict access settings==<br />
The [[Restrict_access_settings|Restrict access]] area becomes visible in Moodle activities and resource settings if [[Conditional_activities|Conditional Activities]] have been enabled.<br />
<br />
==Locally assigned roles==<br />
<br />
In ''Settings > Assignment administration > Locally assigned roles'' selected users can be given additional roles in the activity. See the Using Moodle [http://moodle.org/mod/forum/discuss.php?d=98208 Custom role for 'Course Monitor'] forum discussion for an example.<br />
<br />
==Assignment capabilities==<br />
<br />
* [[Capabilities/mod/assign:exportownsubmission|Export own submission]]<br />
* [[Capabilities/mod/assign:grade|Grade assignment]]<br />
* [[Capabilities/mod/assign:submit|Submit assignment]]<br />
* [[Capabilities/mod/assign:view|View assignment]]<br />
<br />
Role permissions for the activity can be changed in ''Settings > Assignment administration > Permissions''.<br />
<br />
==Site administration settings==<br />
<br />
The following configuration options are available for an administrator under ''Administration > Site administration > Plugins > Activity modules > Assignment''.<br />
<br />
<br />
===Assignment settings===<br />
====Feedback plugin====<br />
The comments that are pushed to the gradebook from the assignment are limited to a single text only comment. An Administrator can specify which of the feedback plugins will be push comments to the gradebook. On a standard Moodle install the choices are "Feedback comments" (default) or "Feedback file" but there may be additional options if your Moodle install contains additional feedback plugins.<br />
<br />
====Show recent submissions====<br />
This option allows everyone to see notifications of submissions in [[Recent activity]] reports and the Recent Activity Block, within a course context. Note that the default for this option is No which means students will not be able to see when classmates have submitted or updated any Assignments.<br />
<br />
====Send submission receipt to students====<br />
This switch will enable submission receipts for students. Students will receive a notification every time they successfully submit an assignment.<br />
{|<br />
|[[File:ass_settings.jpg|thumb|350px|Submission receipts settings]]<br />
|}<br />
<br />
====Submission Statement====<br />
<br />
An administrator can enter text in the box here which will appear when students are about to submit their assignment. <br />
<br />
{|<br />
|[[File:newsubmissionstatement.png|thumb|Admin view of Submission statement set up screen - click to enlarge]]<br />
|[[File:submissionstatement.png|thumb|Student view when about to submit - click to enlarge]]<br />
|}<br />
<br />
<br />
If it is left as the default "No", then teachers will have the choice within their own assignments to force this or not.<br />
<br />
====Default assignment settings====<br />
{{New features}}<br />
The administrator can specify here the default assignment settings which may be set as 'Advanced' (ie, they will appear when clicking 'Show more') or 'Locked' (ie the teacher cannot change them.)<br />
{|<br />
|[[File:26assignmentdefaults.png|thumb|Default, Advanced and Locked checkboxes]]<br />
|}<br />
<br />
<br />
The following configuration options are available for an administrator under ''Administration > Site administration > Plugins > Assignment''. <br />
<br />
===Submission plugins===<br />
====Manage assignment submission plugins====<br />
Here you can change the order, check the settings or uninstall a particular submission plugin.<br />
====File submissions====<br />
'''Enabled by default''' If set, this submission method will be enabled by default for all new assignments.<br />
<br />
'''Maximum submission size''' An Administrator can specify the maximum size of any individual file uploaded within the assignment module across all courses on the site. This limit may be equal to or less than course file upload limit.<br />
<br />
====Online text submissions====<br />
'''Enabled by default''' If set, this submission method will be enabled by default for all new assignments.<br />
<br />
====Submission comments====<br />
<br />
'''Enabled by default''' If set, students will be able to send a message to their teacher when submitting their assignment.<br />
<br />
===Feedback plugins===<br />
====Manage assignment feedback plugins====<br />
Here you can change the order, check the settings or uninstall a particular feedback plugin.<br />
====Feedback comments====<br />
'''Enabled by default''' If set, this submission method will be enabled by default for all new assignments.<br />
====Annotate pdf====<br />
<br />
Here you can upload stamps for teachers to use when annotating student pdfs. You can also check the ghostscript path:<br />
{|<br />
|[[File:Selection_116.png|thumb|Ghostscript not installed or incorrectly installed]]<br />
|[[File:Selection_115.png|thumb|Ghostscript correctly installed]]<br />
|}<br />
<br />
If the default stamps are deleted by accident, they can be found in mod/assign/feedback/editpdf/pix and re-uploaded.<br />
<br />
====File feedback====<br />
'''Enabled by default''' If set, this submission method will be enabled by default for all new assignments.<br />
<br />
===Offline grading worksheet===<br />
<br />
'''Enabled by default''' If set, this will be enabled by default for all new assignments<br />
<br />
==See also==<br />
Synergy Learning blog post: [http://www.synergy-learning.com/moodle-2-5-improvements-assignment-resubmissions/ Assignment resubmissions]<br />
[[de:Aufgabe konfigurieren]]<br />
[[fr:Ajouter/modifier un devoir]]<br />
[[ja:課題を追加/編集する]]<br />
[[es:Configuraciones de tarea]]</div>Deraadthttps://docs.moodle.org/30/en/index.php?title=Moodle_security_procedures&diff=110344Moodle security procedures2014-02-26T08:20:10Z<p>Deraadt: Adding link to security development process</p>
<hr />
<div>{{Security}}<br />
<br />
We treat security issues in Moodle software very seriously. Even though we dedicate a lot of time designing our code to avoid such problems, it is inevitable in a project of this size that new vulnerabilities will occasionally be discovered.<br />
<br />
==Disclosure policy==<br />
<br />
We practice ''responsible disclosure'', which means we have a policy of disclosing all security issues that come to our attention, but only after we have solved the issue and given registered Moodle sites time to upgrade or patch their installations.<br />
<br />
We ask that when reporting a security issue, you observe these same guidelines, and beyond communicating with the security team, do not share your knowledge of security issues with the public at large.<br />
<br />
==How can I report a security issue?==<br />
<br />
Please "[http://tracker.moodle.org/secure/CreateIssue.jspa Create a new issue]" in the Moodle tracker describing the problem (and solution if possible) in detail. Make sure you set the security level accurately to make sure that the security team sees it. Bugs classified as a "Serious security issue" are hidden from everyone apart from the security team and the person who reported the problem.<br />
<br />
If you are not sure whether an issue is a security issue, you should still create a new issue in the tracker for review, using the security level "Could be a security issue".<br />
<br />
Please do ''not'' post about security issues in the forums on moodle.org or elsewhere. This will cause the issue to be more widely known before a fix can be prepared.<br />
<br />
==How we deal with a reported security issue==<br />
<br />
# The security team reviews the issue and evaluates its potential impact on all supported versions of Moodle.<br />
# The security team works with the issue reporter to resolve the problem, keeping details of the problem and its solution hidden until a release is made.<br />
# New versions are created and tested.<br />
# New packages are created and made available on download.moodle.org.<br />
# Advisories are mailed to administrators of registered Moodle sites, giving a period of time when they can upgrade before the issue becomes public.<br />
# A public announcement is made about the security issue in the [http://moodle.org/mod/forum/view.php?id=7128 Moodle security news forum].<br />
<br />
==See also...==<br />
* [[:dev:Process#Security_issues|Security issue development process]]<br />
<br />
[[de:Sicherheitsprozeduren]]</div>Deraadthttps://docs.moodle.org/30/en/index.php?title=Assignment_settings&diff=109980Assignment settings2014-02-17T01:14:58Z<p>Deraadt: Adding link to passing grades settings</p>
<hr />
<div>{{Assignment}}<br />
<p class="note">'''Note''': This page describes settings for the new Assignment module in Moodle 2.3 onwards. For documentation on Assignments (2.2) settings, see [https://docs.moodle.org/22/en/Assignment_settings Assignment settings] in the 2.2 docs.</p><br />
<br />
==Adding and editing an Assignment activity==<br />
*To add a new Assignment activity to your course, login with the appropriate access rights (e.g.editing teacher, course creator or administrator) and Turn Editing On. Within the required Week or Topic Block click Add and Activity or Resource link. <br />
*In the Add an activity or resource dialogue box that appears, select Assignment and click Add.<br />
*To edit an existing Assignment activity, login to your course with the appropriate access rights (e.g. editing teacher, course creator or administrator) and Turn Editing On. Select the Update icon against the relevant Assignment item.<br />
*Alternatively, after logging into your course simply click on the name of the Assignment activity you wish to edit and then click the Edit Settings link under Assignment administration within the Settings block.<br />
<br />
The following configuration options are available when creating or editing/updating any Assignment activity. Only General,Availability and Submission types are open by default;the others are collapsed. To expand everything, click the "Expand all" link top right. <br />
Click on any screenshot to see it full size.<br />
<br />
<br />
==General ==<br />
The General section allows you to give your assignment a name and description. <br />
{|<br />
|[[File:assignmentgeneral26.png|General settings for an assignment]]<br />
|}<br />
<br />
===Assignment name===<br />
Give your Assignment a name (e.g. “Report on Topic 1 Content”). The title entered here will be the name that learners see in the course content area. Learners will click on this name to view the details of the assignment and, if applicable, submit their work.<br />
<br />
===Description===<br />
Provide instructions for your students here so they are clear what they have to do. <br />
Click the icon on the left to expand the toolbar and drag the bottom right of the text box out to expand it.<br />
<br />
You can also provide information or resources related to the assignment, such as a video clip, an image, or a link to a webpage.<br />
<br />
===Display description on course page===<br />
Enabling this will display the description on the course page just below the link to the assignment activity.<br />
<br />
==Availability==<br />
{|<br />
|[[File:AssignAvailability.png|thumb|450px|Availability settings for an assignment]]<br />
|}<br />
<br />
<br />
===Allow submissions from===<br />
The Allow submissions from setting prevents students from submitting their assignment before the shown date. A teacher can to set a day, month, year and time (24 hour clock) from which learners can begin to submit their assignments. Please note that this setting does not hide the activity from the learners. Instead, the learner will see the activity, be able to view the instructions and use any materials you have included in the description, but the learner will not be able to submit or complete the assignment until the Allow submissions from date.<br />
<br />
This setting is enabled (ticked/checked) by default and is set at the day and time you added the assignment. To disable this, remove the tick/check.<br />
<br />
===Due date===<br />
The Due date setting establishes when the assignment is due. Submissions will still be allowed after this date, but any assignments submitted after this date are marked as late.<br />
<br />
This option allows an teacher to set a day, month, year and time (24 hour clock) before which learners must submit their assignment.<br />
<br />
By default the Due date is Enabled (ticked) and is set at 7 days ahead of the day and time you selected Add Assignment. To disable this feature, simply ensure the Enable checkbox is not marked. For more information on using the Due Date see Assignment FAQ<br />
<br />
Note: Assignments without a Due date will appear on the My home page with “No Due date” displayed.<br />
<br />
===Cut-off date===<br />
<br />
The Cut-off date is the date beyond which students will not be able to send in their assignment as the button for doing so will no longer be displayed. After that date (or time) a teacher may, on request, grant an extension by going to the class assignment grading screen, clicking the "Edit" column and choosing "grant extension" for the relevant student. <br />
<br />
For more details, see this Youtube screencast [http://www.youtube.com/watch?v=UaL0LzZwyYI&feature=share&list=UUCRg_EbhU9tdpLdiGGN1Mgg Assignment Extensions]<br />
<br />
===Always show description===<br />
This setting is used in conjunction with the Allow submissions from setting. If it is set to Yes, the assignment Description will become visible to students at the Allow submissions from date. If it is set to No, the assignment Description will be hidden from students until the Allow submissions from date, only the assignment Name will be displayed as shown in the screenshot below. (Click to see full size.)<br />
{|<br />
|[[File:alwaysshowdescription.png|thumb|450px|Always show description]]<br />
|}<br />
<br />
If Allow submissions from is disabled, then this setting has no meaning: the assignment description will always be visible to students.<br />
<br />
==Submission types==<br />
<br />
{|<br />
|[[File:26submissioncomments.png|thumb|450px|Select the type of submission here]]<br />
|}<br />
Here you can decide how you wish students to submit their work to you. <br />
<br />
''Note that if Submission comments are enabled in ''Administration>Plugins>Activity modules>Assignment>Submission plugins'' then students will be able to add a note to their teacher on submitting work. If Blind marking is enabled, student comments display as from "Participant 01 etc" to avoid revealing identities. These comments will appear in the grading table in the Submission comments column.''<br />
<br />
===Online text===<br />
Learners can type their response directly in Moodle using the text editor.<br />
<br />
===File submissions===<br />
Learners can upload and edit one or more files of any type the teacher can open.<br />
<br />
If the student uploads a pdf file, the teacher can annotate it within the browser, and on saving, the annotated file is made available to the student. See section 5.3.1 Annotating pdfs in [[Using Assignment]]<br />
<br />
Note: This requires Ghostscript to be enabled on the server. This can be checked in ''Administration>Site administration>Plugins>Activity modules>Assignments>Feedback plugins>Annotate pdf''.<br />
<br />
===Maximum number of uploaded files===<br />
Here you can decide the maximum number of files which may be uploaded by each learner. (It might be helpful to display the number in the assignment description.)<br />
<br />
===Maximum submission size===<br />
This setting specifies the maximum size per file of each of the files that the students can upload as part of their submission. This maximum upload size may only be equal to or less than the course limit (which in turn may only be equal to or less than the site limit). The maximum size of each file is displayed to students at the point where they upload files.<br />
<br />
{|<br />
|[[File:submission comments.jpg|thumb|Submission comments]]<br />
|[[File:maximum file size.jpg|thumb|Maximum file size]]<br />
|}<br />
<br />
==Feedback types==<br />
(This setting is collapsed by default)<br />
<br />
{|<br />
|[[File:feedbacktypes.png|Feedback types]]<br />
|}<br />
<br />
===Feedback comments===<br />
Setting this to yes means that markers can leave feedback comments for each submission. It enables the Feedback Comments column in the grading table.(To access the grading table, click on the assignment activity and then ''View/Grade all Submissions'').<br />
Feedback comments are also accessible by clicking on the green tick in the grade column on the grading table.<br />
<br />
{|<br />
|[[File:feedback comments.jpg|thumb|The Feedback comments column]]<br />
|[[FIle:feedback comments 2.jpg|thumb|Type feedback comments into the box]]<br />
|}<br />
<br />
===Offline grading worksheet===<br />
<br />
If set to yes, the teacher will have a link to download the grading list as a spreadsheet. They will then be able to enter grades and feedback comments offline:<br />
<br />
{|<br />
|[[File:emptygradebook.png|thumb|The empty gradebook on Moodle]]<br />
|[[File:downloadgradingworksheet.png|thumb|The dropdown to download the list]]<br />
|[[File:excelgrades.png|thumb|Editing the grades offline]]<br />
|}<br />
<br />
When the teacher has completed their grading offline, they can then upload the spreadsheet, confirm the changes and the grades and comments will be transferred over into Moodle's gradebook:<br />
<br />
{|<br />
|[[File:uploadgradingworksheet.png|thumb|Uploading the grading worksheet]]<br />
|[[File:confirmchanges.png|thumb|Confirming the changes]]<br />
|[[File:fullgradebook.png|thumb|Grades and feedback transferred into Moodle]]<br />
|}<br />
<br />
See also [http://www.somerandomthoughts.com/blog/2012/11/19/offline-grading-worksheet-in-moodle-2-4-assignment/ Offline grading worksheet] blog post by Gavin Henrick.<br />
<br />
===Feedback files===<br />
This allows markers to upload files with feedback when marking. These files may be the marked up student assignments, documents with comments, a completed marking guide, or spoken audio feedback. It enables the Feedback Files column in the grading table. (To access the grading table click on the assignment activity and then ''View/Grade all Submissions'')To upload feedback files, click on the green tick in the grade column on the grading table and then upload either with drag and drop or using the [[File picker]].<br />
<br />
Feedback is displayed to students on the assignment submission page. <br />
<br />
{|<br />
|[[File:feedback files.jpg|thumb|The Feedback files column]]<br />
|[[File:feedback files 2.jpg|thumb|Upload files here]]<br />
|[[File:feedback view for students.jpg|thumb|Student view with comments and file feedback both enabled]]<br />
|}<br />
====Uploading multiple feedback files====<br />
<br />
It is also possible to upload multiple feedback files as a zip, from the dropdown above the grading list:<br />
<br />
#Download the students' assignments using the "Download all submissions" link from the same dropdown menu;<br />
#Extract the folder offline and add your comments to the student's submissions.Keep the names the same.<br />
#Select the students' submissions and zip them into a new folder. Important: Don't just edit them inside their original folder and re-zip this; it will not work. The folder name does not matter as long as the feedback files have the same names as before.<br />
#Upload this newly zipped folder.<br />
#You will be presented with a confirmation screen displaying your feedback files.<br />
<br />
{|<br />
|[[File:mutiplefeedbackzip.png|thumb|Choose from the dropdown menu]]<br />
|[[File:multiplezip1.png|thumb|Confirmation screen displaying the feedback files to be uploaded]]<br />
|[[File:multiplezip2.png|thumb|Screen confirming uploaded feedback]]<br />
|}<br />
<br />
''Note:''If you zip files on a Mac, you may get a folder included in the zip called _MACOSX_ which needs to be removed otherwise moodle will not recognise the changes in the files.<br />
<br />
==Submission settings==<br />
(This setting is collapsed by default)<br />
<br />
{|<br />
|[[File:submissionsettings.png|Submission settings]]<br />
|}<br />
===Require students click submit button===<br />
Students can upload draft versions of the assignment until such time as they are ready to submit.Once they click the submit button they indicate to the teacher that they have finished working on the assignment. In earlier versions of Moodle this was called ''"Send for marking"''.)<br />
<br />
They can then longer edit their submission. If they need to change it, they must ask the teacher who can revert the assignment to draft status.<br />
<br />
To revert to the draft stage, click on the assignment activity and then View/Grade all Submissions. Locate the student and click the action icon in the Edit column. Select Revert the submission to draft.<br />
<br />
If this setting is No, then students do not have to to click a submit button and are able to make changes to uploaded files at any time.<br />
<br />
If this setting is No but the teacher wishes to grade students work, then you can stop students from making further changes by using Prevent submission changes. Prevent submission changes can also be used in cases where students have neglected to click the Submit button and grading has commenced.<br />
To prevent submission changes, click on the assignment activity, then click on the View/Grade all submissions button. On the grading table, locate the student and click the action icon in the Edit column. Select Prevent submission changes.<br />
<br />
To do either of these with a number of students, use the ''With selected'' menu at the bottom of the grading table.<br />
<br />
{|<br />
|[[File:revert to draft.jpg|thumb|Reverting to draft]]<br />
|[[File:prevent submission changes.jpg|thumb|Prevent submission changes]]<br />
|[[File:with selected.jpg|thumb|"With selected"..]]<br />
|}<br />
<br />
To do either of these with a number of students, use the ''With selected'' menu at the bottom of the grading table.<br />
<br />
===Require that students accept the Submission statement===<br />
<br />
An administrator can define a "Submission statement", ie, a statement where students promise the work is their own and which they must agree to before submitting their work. This may be done via ''Settings>Site administration>Plugins>Activity modules>Assignment.''<br />
<br />
If preferred, the available default statement which may be used instead: ''This assignment is my own work, except where I have acknowledged the use of the works of other people'' <br />
<br />
If the administrator has given teachers the option of using a submission statement or not, then it will be available in the assignment settings screen. The section [[#Submission_Statement]] explains how an administrator can set this up.<br />
<br />
For more details, see this blog post [http://ourlearning.co.uk/2012/10/moodle-assignment-all-my-own-work/ "All my own work"]<br />
<br />
When this setting is enabled, students will have to check a button before they can submit their assignment:<br />
<br />
If the administrator has forced the statement throughout the site, a teacher will not have this option in the settings but a student will see the statement when accessing their assignment.<br />
<br />
===Attempts reopened===<br />
<br />
This setting allows the teacher to decide how submissions are reopened. The default is "Never", in that students may only submit once. However, a teacher can set this to "Manually" and reopen it themselves for the student to resubmit, or to "Automatically until pass". The student must then keep trying and resubmitting until they get a pass grade. [[Grade_items#Activity-based_grade_items|Passing grades]] are set in the Gradebook.<br />
<br />
===Maximum attempts===<br />
<br />
If a student is allowed to resubmit, this setting will determine how many times they can resubmit before they are no longer allowed to do so. (For example, if a student has to keep trying until they get a pass grade, the teacher might decide that ten attempts is enough even though they have not yet passed!)<br />
<br />
==Groups submission settings==<br />
(This setting is collapsed by default)<br />
{|<br />
|[[File:groupsubmissionsettings.png|Group submission settings]]<br />
|}<br />
<br />
===Students submit in groups===<br />
<br />
If this box is ticked, then students are able to collaborate on an assignment. This might involve for example, working in the same online text area, or one student uploading an MS Powerpoint which another student downloads, improves and re-uploads to the common assignment area.<br />
<br />
When grading, the teacher may choose to give a common grade and feedback to all students in the group or to give individual grades and feedback to each member.<br />
<br />
If no groups have been made, then Moodle will make a default group of every student in the course.<br />
<br />
For more details see this Youtube video [http://www.youtube.com/watch?v=G16gYZJFCrM&feature=share&list=UUCRg_EbhU9tdpLdiGGN1Mgg Group Assignment 2.4]<br />
<br />
===Require all group members submit===<br />
<br />
This setting will only appear if the teacher has ticked the "Require students click submit button" earlier. The assignment will not be classed as "submitted" until all members of the group have made a contribution. When one student has submitted, the other members of the group will be able to see who still has to submit.<br />
<br />
===Grouping for student groups===<br />
If a particular grouping is selected here, then the gradebook will display any other groups and non-grouped students in the "default group", while naming the group(s) that are in the chosen grouping. If "none" is selected, then the gradebook will display the names of all groups and put any non-grouped students in the "default group". See this [https://moodle.org/mod/forum/discuss.php?d=216399#p942913 forum post on grouping for student groups] for examples of how this might be used.<br />
<br />
==Notifications==<br />
(This setting is collapsed by default)<br />
<br />
{|<br />
|[[File:notifications25.png|Notifications]]<br />
|}<br />
===Notify graders about submissions===<br />
Teachers will receive a message (of a type they choose) whenever a student submits an assignment. Please note if you are using the assignment in Groups Mode (eg Separate or Visible Groups), the teacher will need to be a member of the group in order to receive the submission notification.<br />
===Notify graders about late submission===<br />
Teachers will receive a message (of a type they choose)whenever a student submits a late assignment. Please note if you are using the assignment in Groups Mode (eg Separate or Visible Groups), the teacher will need to be a member of the group in order to receive the submission notification.<br />
<br />
==Grade==<br />
(This setting is collapsed by default)<br />
{|<br />
|[[File:grade25.png|Grade]]<br />
|}<br />
<br />
===Grade===<br />
Specify the maximum grade or [[Scales|Scale]] to be applied to the assignment. If you will not be giving a grade for the assignment, choose No Grade.<br />
<br />
===Grading method===<br />
<br />
There are 3 options:<br />
* Simple direct grading (entering a grade or scale item)<br />
* [[Marking guide]]<br />
* [[Rubric]]<br />
<br />
===Grade Category===<br />
Any custom [[Grade_categories|Grade Categories]] that have been created within your site or course will be listed here and will be available for selection. Select the required Grade Category to add this assignment as a [[Grade_items|Grade item]] within this Category.<br />
<br />
<br />
===Blind marking===<br />
<br />
If this setting is enabled, then a teacher will not see the names of students who have submitted their assignments. Instead, they will see randomly generated Participant numbers. (The student view of the assignment does not change.) This is also the case if student comments have been enabled. Once they have graded the assignment, it is however possible for teachers to see who submitted what by clicking on "Reveal student identities" in the Assignment settings.<br />
<br />
====Returning Marks to Students ====<br />
Because of the nature of blind marking, the students cannot see the final grade until all of the students names have been revealed. This is found in Assignment Settings > Reveal Student Names. However, feedback comments will appear.<br />
<br />
''Note:'' Beacuse of this, the level of anonymity might not suit the privacy requirements of your establishment. See this tracker entry MDL-35390 - "Blind Marking is not so blind"<br />
<br />
For more details on this feature, see this Youtube video [http://youtu.be/Biiw3E13mgM Blind marking in 2.4].<br />
<br />
===Use marking workflow===<br />
{{New features}}<br />
When set to Yes, teachers will be able to specify the stage they are at in their grading of individual assignments (as in the screenshot below)<br />
<br />
{|<br />
|[[File:26markingworkflow.png|thumb|Marking workflow state in the individual grading screen]]<br />
|[[File:26quickgradingworkflow.png|thumb|Dropdown to select marking workflow state when quick grading]]<br />
|}<br />
<br />
One advantage of using marking workflow is that the grades can be hidden from students until they are set to 'Released'. The actual list of steps are:<br />
<br />
* Not marked (the marker has not yet started) <br />
* In marking (the marker has started but not yet finished) <br />
* Marking completed (the marker has finished but might need to go back for checking/corrections) <br />
* In review (the marking is now with the teacher in charge for quality checking) <br />
* Ready for release (the teacher in charge is satisfied with the marking but wait before giving students access to the marking) <br />
* Released (the student can access the grades/feedback)<br />
<br />
====Example use cases====<br />
<br />
One marker, Marker, wants to release all grades at the same time <br />
* Marker enables "Use marking workflow" <br />
* Marker marks each submission and transitions the grading to "Marking completed" as each submission is graded. <br />
* Marker then uses the batch operations to transition all grades to "Released" at the same time. <br />
<br />
Multiple markers, <br />
* Marker enables "Use marking workflow" <br />
* Marker marks each submission and transitions the grading to "Marking completed" as each submission is graded. <br />
* Marker then uses the batch operations to transition all grades to "Released" at the same time.<br />
<br />
===Use marking allocation===<br />
{{New features}}<br />
If marking workflow (see above) is set to Yes, it is possible to enable marking allocation. This means that teachers can be selected to grade or review the submitted work of specific students. Colleagues can monitor progress through the displayed marking workflow states:<br />
<br />
{|<br />
|[[File:26markingworkflowallocatedmarkers.png|thumb|Allocated markers on the grading screen]]<br />
|}<br />
<br />
==Common module settings==<br />
See [[Common module settings]]<br />
<br />
==Restrict access settings==<br />
The [[Restrict_access_settings|Restrict access]] area becomes visible in Moodle activities and resource settings if [[Conditional_activities|Conditional Activities]] have been enabled.<br />
<br />
==Locally assigned roles==<br />
<br />
In ''Settings > Assignment administration > Locally assigned roles'' selected users can be given additional roles in the activity. See the Using Moodle [http://moodle.org/mod/forum/discuss.php?d=98208 Custom role for 'Course Monitor'] forum discussion for an example.<br />
<br />
==Assignment capabilities==<br />
<br />
* [[Capabilities/mod/assign:exportownsubmission|Export own submission]]<br />
* [[Capabilities/mod/assign:grade|Grade assignment]]<br />
* [[Capabilities/mod/assign:submit|Submit assignment]]<br />
* [[Capabilities/mod/assign:view|View assignment]]<br />
<br />
Role permissions for the activity can be changed in ''Settings > Assignment administration > Permissions''.<br />
<br />
==Site administration settings==<br />
<br />
The following configuration options are available for an administrator under ''Administration > Site administration > Plugins > Activity modules > Assignment''.<br />
<br />
<br />
===Assignment settings===<br />
====Feedback plugin====<br />
The comments that are pushed to the gradebook from the assignment are limited to a single text only comment. An Administrator can specify which of the feedback plugins will be push comments to the gradebook. On a standard Moodle install the choices are "Feedback comments" (default) or "Feedback file" but there may be additional options if your Moodle install contains additional feedback plugins.<br />
<br />
====Show recent submissions====<br />
This option allows everyone to see notifications of submissions in [[Recent activity]] reports and the Recent Activity Block, within a course context. Note that the default for this option is No which means students will not be able to see when classmates have submitted or updated any Assignments.<br />
<br />
====Send submission receipt to students====<br />
This switch will enable submission receipts for students. Students will receive a notification every time they successfully submit an assignment.<br />
{|<br />
|[[File:ass_settings.jpg|thumb|350px|Submission receipts settings]]<br />
|}<br />
<br />
====Submission Statement====<br />
<br />
An administrator can enter text in the box here which will appear when students are about to submit their assignment. <br />
<br />
{|<br />
|[[File:newsubmissionstatement.png|thumb|Admin view of Submission statement set up screen - click to enlarge]]<br />
|[[File:submissionstatement.png|thumb|Student view when about to submit - click to enlarge]]<br />
|}<br />
<br />
<br />
If it is left as the default "No", then teachers will have the choice within their own assignments to force this or not.<br />
<br />
====Default assignment settings====<br />
{{New features}}<br />
The administrator can specify here the default assignment settings which may be set as 'Advanced' (ie, they will appear when clicking 'Show more') or 'Locked' (ie the teacher cannot change them.)<br />
{|<br />
|[[File:26assignmentdefaults.png|thumb|Default, Advanced and Locked checkboxes]]<br />
|}<br />
<br />
<br />
The following configuration options are available for an administrator under ''Administration > Site administration > Plugins > Assignment''. <br />
<br />
===Submission plugins===<br />
====Manage assignment submission plugins====<br />
Here you can change the order, check the settings or uninstall a particular submission plugin.<br />
====File submissions====<br />
'''Enabled by default''' If set, this submission method will be enabled by default for all new assignments.<br />
<br />
'''Maximum submission size''' An Administrator can specify the maximum size of any individual file uploaded within the assignment module across all courses on the site. This limit may be equal to or less than course file upload limit.<br />
<br />
====Online text submissions====<br />
'''Enabled by default''' If set, this submission method will be enabled by default for all new assignments.<br />
<br />
====Submission comments====<br />
<br />
'''Enabled by default''' If set, students will be able to send a message to their teacher when submitting their assignment.<br />
<br />
===Feedback plugins===<br />
====Manage assignment feedback plugins====<br />
Here you can change the order, check the settings or uninstall a particular feedback plugin.<br />
====Feedback comments====<br />
'''Enabled by default''' If set, this submission method will be enabled by default for all new assignments.<br />
====Annotate pdf====<br />
<br />
Here you can upload stamps for teachers to use when annotating student pdfs. You can also check the ghostscript path:<br />
{|<br />
|[[File:Selection_116.png|thumb|Ghostscript not installed or incorrectly installed]]<br />
|[[File:Selection_115.png|thumb|Ghostscript correctly installed]]<br />
|}<br />
<br />
If the default stamps are deleted by accident, they can be found in mod/assign/feedback/editpdf/pix and re-uploaded.<br />
<br />
====File feedback====<br />
'''Enabled by default''' If set, this submission method will be enabled by default for all new assignments.<br />
<br />
===Offline grading worksheet===<br />
<br />
'''Enabled by default''' If set, this will be enabled by default for all new assignments<br />
<br />
==See also==<br />
Synergy Learning blog post: [http://www.synergy-learning.com/moodle-2-5-improvements-assignment-resubmissions/ Assignment resubmissions]<br />
[[de:Aufgabe konfigurieren]]<br />
[[fr:Ajouter/modifier un devoir]]<br />
[[ja:課題を追加/編集する]]<br />
[[es:Configuraciones de tarea]]</div>Deraadthttps://docs.moodle.org/30/en/index.php?title=OPcache&diff=107917OPcache2013-11-21T07:34:00Z<p>Deraadt: Adding details for IIS</p>
<hr />
<div>{{Environment}}<br />
{{New features}}<br />
The standard OPcache extension is strongly recommended; since Moodle 2.6, it is the only solution officially supported by PHP developers. The benefits are increased performance and significantly lower memory usage.<br />
<br />
==Installation==<br />
<br />
The OPcache extension is distributed as part of PHP 5.5.0 and later. It is available also for older stable PHP releases from PECL under the original name ZendOPcache.<br />
<br />
==Configuration==<br />
<br />
PHP.ini settings:<br />
<br />
<code ini><br />
[opcache]<br />
opcache.enable = 1<br />
opcache.memory_consumption = 128<br />
opcache.max_accelerated_files = 4000<br />
opcache.revalidate_freq = 60<br />
<br />
; Required for Moodle<br />
opcache.use_cwd = 1<br />
opcache.validate_timestamps = 1<br />
opcache.save_comments = 1<br />
opcache.enable_file_override = 0<br />
<br />
; If something does not work in Moodle<br />
;opcache.revalidate_path = 1 ; May fix problems with include paths<br />
<br />
; Experimental for Moodle 2.6 and later<br />
;opcache.fast_shutdown = 1<br />
;opcache.enable_cli = 1 ; Speeds up CLI cron<br />
;opcache.load_comments = 0 ; May lower memory use, might not be compatible with add-ons and other apps.<br />
</code><br />
<br />
When using IIS you will need PHP 5.5 and you will need to add the extension for opcache under the ''ExtensionList'' section of the php.ini file.<br />
<br />
<code ini><br />
[ExtensionList]<br />
...<br />
zend_extension=php_opcache.dll<br />
</code><br />
<br />
==See also==<br />
* [http://pecl.php.net/package/ZendOpcache PECL ZendOPcache]<br />
<br />
[[Category:Environment]]<br />
[[Category:Installation]]<br />
[[Category:Performance]]<br />
<br />
[[es:OPcache]]</div>Deraadthttps://docs.moodle.org/30/en/index.php?title=Progress_Bar_block&diff=106592Progress Bar block2013-09-12T08:19:57Z<p>Deraadt: Adding new acknowledgements</p>
<hr />
<div>[[Blocks|Back to Blocks page]]<br />
<br />
== Features ==<br />
<br />
[[Image:Bar_in_block_-_with_details.png|right|A progress bar for a student]]<br />
* The Progress Bar is a time-management tool for students.<br />
* It visually shows what activities/resources a student is supposed to interact with in a course.<br />
* It is colour coded so students can quickly see what they have and have not completed/viewed.<br />
* The teacher selects which pre-existing activities/resources are to be included in the Progress Bar and when they should be completed/viewed.<br />
* Ordering can be done by times/deadlines or by the ordering of activities in the course.<br />
[[Image:Overview_of_students.png|thumb|right|The overview page]]<br />
* There is an overview page allowing teachers to see the progress of all students in a class, which is helpful for finding students at risk.<br />
<br />
<mediaplayer>http://www.youtube.com/watch?v=d43KVlMBmLA </mediaplayer><br />
<br />
== Links ==<br />
<br />
* [http://moodle.org/plugins/view.php?plugin=block_progress Block code in Plugins repository]<br />
* [http://tracker.moodle.org/browse/CONTRIB/component/10489 Bug Tracker Page] (Please report bugs here)<br />
* [http://cvs.moodle.org/contrib/plugins/blocks/progress/ CVS Repository]<br />
<br />
== Installing ==<br />
<br />
The Progress Bar block is added like other blocks ([[Installing_contributed_modules_or_plugins|How to install a block]]).<br />
<br />
Once the progress bar is installed, you can use it in a course as follows.<br />
# Turn editing on<br />
# Create your activities/resources as normal<br />
# Add the Progress Bar block to your page ([[Blocks|How to add a block]])<br />
# Move your Progress Bar block into a prominent position, eg. top-left (click and drag the block title)<br />
# Click the Configuration icon on the block below the title<br />
# Give your Progress Bar block a title (default is "Progress Bar")<br />
# Set the activities/resources you want shown in the block to "Yes"<br />
# Set the date and time when the activity/resource is expected to be completed/viewed by (some activities have deadlines set, if so, that deadline can be used or another can be set in the Progress Bar block configuration)<br />
# Save changes<br />
<br />
Hidden items will not appear in the Progress Bar until they are unhidden. This is useful for a scheduled release of activities.<br />
<br />
== Acknowledgements ==<br />
<br />
* Thanks to:<br />
** Toshimi Hatanaka for contributing a Japanese translation<br />
** Yvonne Schneider and Joachim Vogelgesang for contributing a German translation<br />
** Maria João Spilker for contributing a Portuguese-Brazilian translation<br />
** Pieter Wolters for contributing a Dutch translation<br />
** Fernando Sánchez for contributing a Spanish translation<br />
** Fabien Sartoretti for contributing a French translation<br />
** Adam Levy for contributing queries and strings for Hot Potatoes support<br />
** Petras Virzintas for contributing queries for Turnitin support<br />
** Willian Mano for helping with the modern look CSS<br />
** Matthieu Rolland for contributing queries for the Questionnaire module<br />
<br />
[[Category:Contributed code]]</div>Deraadthttps://docs.moodle.org/30/en/index.php?title=Progress_Bar_block&diff=106591Progress Bar block2013-09-12T08:18:28Z<p>Deraadt: Updating screenshots</p>
<hr />
<div>[[Blocks|Back to Blocks page]]<br />
<br />
== Features ==<br />
<br />
[[Image:Bar_in_block_-_with_details.png|right|A progress bar for a student]]<br />
* The Progress Bar is a time-management tool for students.<br />
* It visually shows what activities/resources a student is supposed to interact with in a course.<br />
* It is colour coded so students can quickly see what they have and have not completed/viewed.<br />
* The teacher selects which pre-existing activities/resources are to be included in the Progress Bar and when they should be completed/viewed.<br />
* Ordering can be done by times/deadlines or by the ordering of activities in the course.<br />
[[Image:Overview_of_students.png|thumb|right|The overview page]]<br />
* There is an overview page allowing teachers to see the progress of all students in a class, which is helpful for finding students at risk.<br />
<br />
<mediaplayer>http://www.youtube.com/watch?v=d43KVlMBmLA </mediaplayer><br />
<br />
== Links ==<br />
<br />
* [http://moodle.org/plugins/view.php?plugin=block_progress Block code in Plugins repository]<br />
* [http://tracker.moodle.org/browse/CONTRIB/component/10489 Bug Tracker Page] (Please report bugs here)<br />
* [http://cvs.moodle.org/contrib/plugins/blocks/progress/ CVS Repository]<br />
<br />
== Installing ==<br />
<br />
The Progress Bar block is added like other blocks ([[Installing_contributed_modules_or_plugins|How to install a block]]).<br />
<br />
Once the progress bar is installed, you can use it in a course as follows.<br />
# Turn editing on<br />
# Create your activities/resources as normal<br />
# Add the Progress Bar block to your page ([[Blocks|How to add a block]])<br />
# Move your Progress Bar block into a prominent position, eg. top-left (click and drag the block title)<br />
# Click the Configuration icon on the block below the title<br />
# Give your Progress Bar block a title (default is "Progress Bar")<br />
# Set the activities/resources you want shown in the block to "Yes"<br />
# Set the date and time when the activity/resource is expected to be completed/viewed by (some activities have deadlines set, if so, that deadline can be used or another can be set in the Progress Bar block configuration)<br />
# Save changes<br />
<br />
Hidden items will not appear in the Progress Bar until they are unhidden. This is useful for a scheduled release of activities.<br />
<br />
== Acknowledgements ==<br />
<br />
* Thanks to:<br />
** Toshimi Hatanaka for contributing a Japanese translation<br />
** Yvonne Schneider and Joachim Vogelgesang for contributing a German translation<br />
** Maria João Spilker for contributing a Portuguese-Brazilian translation<br />
** Pieter Wolters for contributing a Dutch translation<br />
** Fernando Sánchez for contributing a Spanish translation<br />
** Fabien Sartoretti for contributing a French translation<br />
** Adam Levy for contributing queries and strings for Hot Potatoes support<br />
** Petras Virzintas for contributing queries for Turnitin support<br />
<br />
[[Category:Contributed code]]</div>Deraadthttps://docs.moodle.org/30/en/index.php?title=File:Overview_of_students.png&diff=106590File:Overview of students.png2013-09-12T08:17:24Z<p>Deraadt: </p>
<hr />
<div></div>Deraadt