<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://docs.moodle.org/310/en/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Anderson.blaine</id>
	<title>MoodleDocs - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://docs.moodle.org/310/en/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Anderson.blaine"/>
	<link rel="alternate" type="text/html" href="https://docs.moodle.org/310/en/Special:Contributions/Anderson.blaine"/>
	<updated>2026-04-13T07:26:39Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.43.5</generator>
	<entry>
		<id>https://docs.moodle.org/310/en/index.php?title=Standard_Moodle_tags&amp;diff=140405</id>
		<title>Standard Moodle tags</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/310/en/index.php?title=Standard_Moodle_tags&amp;diff=140405"/>
		<updated>2021-05-14T18:17:26Z</updated>

		<summary type="html">&lt;p&gt;Anderson.blaine: /* Tags in use */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Tags are useful for connecting different bits of information together.&lt;br /&gt;
&lt;br /&gt;
Obviously it&#039;s important to use the same tags everywhere.&lt;br /&gt;
&lt;br /&gt;
This page describes standard Moodle tags that you should use when describing Moodle events on the internet (Flickr, Twitter, Facebook, del.icio.us etc)&lt;br /&gt;
&lt;br /&gt;
==General Moodle stuff==&lt;br /&gt;
&lt;br /&gt;
For general discussion of Moodle, use the tag &amp;quot;moodle&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
Twitter example:&lt;br /&gt;
 I just installed #moodle on a computer I bought ten years ago!&lt;br /&gt;
&lt;br /&gt;
==Moodle Moots==&lt;br /&gt;
&lt;br /&gt;
For Moodle conferences (Moots) use mootCCYY where:&lt;br /&gt;
* CC is a country ISO code or state abbreviation, and&lt;br /&gt;
* YY is a year.&lt;br /&gt;
&lt;br /&gt;
 mootAU09&lt;br /&gt;
&lt;br /&gt;
Capitalisation doesn&#039;t matter and just helps readability.&lt;br /&gt;
&lt;br /&gt;
The two letter code would usually be a country, but for somewhere like the US where there are different moots they might choose to use &amp;quot;us&amp;quot; or a state like &amp;quot;sf&amp;quot; or &amp;quot;ok&amp;quot;. It really doesn&#039;t matter if two moots both used mootus09 for example, because they would be separated in time.&lt;br /&gt;
&lt;br /&gt;
==Tags in use==&lt;br /&gt;
&lt;br /&gt;
* #mooteu09 MoodleMoot Euskadi&lt;br /&gt;
* #mootNL09 Amsterdam Moodlemoot&lt;br /&gt;
* #mootUS09ok Moodlemoot Oklahoma  (or #mootok09)&lt;br /&gt;
* #mootUS09SF Moodlemoot San Francisco  (or #mootsf09)&lt;br /&gt;
* #mootin09 Goshen Midwest MoodleMoot&lt;br /&gt;
* #mootus09ny MoodleMoot Delhi (or #mootny09) &lt;br /&gt;
* #mootar09 MoodleMoot Argentina&lt;br /&gt;
* #mootat09 MoodleMoot Austria &lt;br /&gt;
* #mootDE09 MoodleMoot Germany 2009&lt;br /&gt;
* #mootco09 MoodleMoot Colombia&lt;br /&gt;
* #mootcl09 MoodleMoot Chile&lt;br /&gt;
* #mootes09 MoodleMoot Spain 2009&lt;br /&gt;
* #moodle #OE09 Moodle at Online Educa 2009 in Berlin (December)&lt;br /&gt;
* #moodledev09 [[Development:Czech Hackfest 2009|Czech Hackfest 2009]]&lt;br /&gt;
* #imoot and #imoot2010 iMoot 2010&lt;br /&gt;
* #mootJP10hk Moodlemoot Japan in Hakodate, February 2010&lt;br /&gt;
* #mootDE10b Moodlemoot Germany 2010 in Berlin March&lt;br /&gt;
* #mootDE10e [http://moodle2010.de/ Moodlemoot Germany 2010 in Essen] 16-17 September 2010&lt;br /&gt;
* #mootNZ10 Moodle Moot New Zealand (Christchurch) April 2010&lt;br /&gt;
* #mootUK10 MoodleMoot UK April 2010&lt;br /&gt;
* #mootsi10 Slovenian MoodleMoot&lt;br /&gt;
* #mootok10 MoodleMoot Oklahoma&lt;br /&gt;
* #mootau10 MoodleMoot AU 2010&lt;br /&gt;
* #mootcz10 [http://www.moodlemoot.cz/ MoodleMoot Czech Republic, Brno] 10-11 June 2010&lt;br /&gt;
* #mootfr10 6th French MoodleMoot&lt;br /&gt;
* #mootIT10 MoodleMoot Italia 2010&lt;br /&gt;
* #mootnl10 MoodleMoot NL 2010&lt;br /&gt;
* #mootPL10 Second Polish MoodleMoot, 4-5 November 2010, Czestochowa, Poland, http://moodlemoot.pl&lt;br /&gt;
* #mootusin10 Goshen, Indiana, USA 26-28 July, 2010&lt;br /&gt;
* #mootustx10 Austin, Texas, USA 2-3 August, 2010&lt;br /&gt;
* #mootfr11 [http://moodlemoot2011.uvt.rnu.tn/ 7th French MoodleMoot], Hammamet, Tunisia, 27-29 June 2011&lt;br /&gt;
* #mootde12 [http://moodlemoot.de/ German Moodlemoot], Münster, Germany, 13-16 March 2012&lt;br /&gt;
* #mootfr12 [http://moodlemoot2012.unimes.fr/ 8th French MoodleMoot], Nîmes, France, 20-22 June 2012&lt;br /&gt;
* #mootde13 [http://moodlemoot.de/ German Moodlemoot], München, Germany, 28 Feb - 1 Mar 2013&lt;br /&gt;
* #mootfr13 [http://moodlemoot2013.univ-bordeaux.fr/ 9th French MoodleMoot], Bordeaux, France, 5-7 June 2013&lt;br /&gt;
* #smootau13 [http://http://school.moodlemoot.com.au/ 2nd Australian Schoolmoot], Sydney, Australia, 2-4 October 2013&lt;br /&gt;
* #mootfr14 [http://moodlemoot2014.univ-paris3.fr 10th French MoodleMoot], Paris, 4-6 June 2014&lt;br /&gt;
* #mootfr15 [https://moodlemoot2015.univ-tours.fr 11th French MoodleMoot], Tours, 10-12 June 2015&lt;br /&gt;
* #mootfr16 [http://2016.moodlemoot.fr 12th French MoodleMoot], Sierre, Switzerland, 6-8 July 2016&lt;br /&gt;
* #mootfr17 [http://2017.moodlemoot.fr 13th French MoodleMoot], Lyon, 28-30 June 2017&lt;br /&gt;
* #mootfr18 [https://2018.moodlemoot.fr 14th French MoodleMoot], Bruxelles, 4-6 July 2018&lt;br /&gt;
* #mootfr19 [https://2019.moodlemoot.fr 15th French MoodleMoot], Rennes, 3-5 July 2019&lt;br /&gt;
* #mootBR19  [https://www.moodlebrasil.org 19th Brazil MoodleMoot], São Paulo, 25-26 April 2019&lt;br /&gt;
* #mootBR19  [https://www.moodlebrasil.org 20th Brazil MoodleMoot], São Luís-MA, 10-11 October 2019&lt;br /&gt;
* #mootBR21  [https://www.moodlebrasil.org 21th Brazil MoodleMoot], Brazil - Online, 27-28 May 2021&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
&lt;br /&gt;
* Lounge discussion [http://moodle.org/mod/forum/discuss.php?d=121619 A standard naming scheme for Moodle hashtags]&lt;/div&gt;</summary>
		<author><name>Anderson.blaine</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/310/en/index.php?title=Standard_Moodle_tags&amp;diff=140404</id>
		<title>Standard Moodle tags</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/310/en/index.php?title=Standard_Moodle_tags&amp;diff=140404"/>
		<updated>2021-05-14T18:16:38Z</updated>

		<summary type="html">&lt;p&gt;Anderson.blaine: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Tags are useful for connecting different bits of information together.&lt;br /&gt;
&lt;br /&gt;
Obviously it&#039;s important to use the same tags everywhere.&lt;br /&gt;
&lt;br /&gt;
This page describes standard Moodle tags that you should use when describing Moodle events on the internet (Flickr, Twitter, Facebook, del.icio.us etc)&lt;br /&gt;
&lt;br /&gt;
==General Moodle stuff==&lt;br /&gt;
&lt;br /&gt;
For general discussion of Moodle, use the tag &amp;quot;moodle&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
Twitter example:&lt;br /&gt;
 I just installed #moodle on a computer I bought ten years ago!&lt;br /&gt;
&lt;br /&gt;
==Moodle Moots==&lt;br /&gt;
&lt;br /&gt;
For Moodle conferences (Moots) use mootCCYY where:&lt;br /&gt;
* CC is a country ISO code or state abbreviation, and&lt;br /&gt;
* YY is a year.&lt;br /&gt;
&lt;br /&gt;
 mootAU09&lt;br /&gt;
&lt;br /&gt;
Capitalisation doesn&#039;t matter and just helps readability.&lt;br /&gt;
&lt;br /&gt;
The two letter code would usually be a country, but for somewhere like the US where there are different moots they might choose to use &amp;quot;us&amp;quot; or a state like &amp;quot;sf&amp;quot; or &amp;quot;ok&amp;quot;. It really doesn&#039;t matter if two moots both used mootus09 for example, because they would be separated in time.&lt;br /&gt;
&lt;br /&gt;
==Tags in use==&lt;br /&gt;
&lt;br /&gt;
* #mooteu09 MoodleMoot Euskadi&lt;br /&gt;
* #mootNL09 Amsterdam Moodlemoot&lt;br /&gt;
* #mootUS09ok Moodlemoot Oklahoma  (or #mootok09)&lt;br /&gt;
* #mootUS09SF Moodlemoot San Francisco  (or #mootsf09)&lt;br /&gt;
* #mootin09 Goshen Midwest MoodleMoot&lt;br /&gt;
* #mootus09ny MoodleMoot Delhi (or #mootny09) &lt;br /&gt;
* #mootar09 MoodleMoot Argentina&lt;br /&gt;
* #mootat09 MoodleMoot Austria &lt;br /&gt;
* #mootDE09 MoodleMoot Germany 2009&lt;br /&gt;
* #mootco09 MoodleMoot Colombia&lt;br /&gt;
* #mootcl09 MoodleMoot Chile&lt;br /&gt;
* #mootes09 MoodleMoot Spain 2009&lt;br /&gt;
* #moodle #OE09 Moodle at Online Educa 2009 in Berlin (December)&lt;br /&gt;
* #moodledev09 [[Development:Czech Hackfest 2009|Czech Hackfest 2009]]&lt;br /&gt;
* #imoot and #imoot2010 iMoot 2010&lt;br /&gt;
* #mootJP10hk Moodlemoot Japan in Hakodate, February 2010&lt;br /&gt;
* #mootDE10b Moodlemoot Germany 2010 in Berlin March&lt;br /&gt;
* #mootDE10e [http://moodle2010.de/ Moodlemoot Germany 2010 in Essen] 16-17 September 2010&lt;br /&gt;
* #mootNZ10 Moodle Moot New Zealand (Christchurch) April 2010&lt;br /&gt;
* #mootUK10 MoodleMoot UK April 2010&lt;br /&gt;
* #mootsi10 Slovenian MoodleMoot&lt;br /&gt;
* #mootok10 MoodleMoot Oklahoma&lt;br /&gt;
* #mootau10 MoodleMoot AU 2010&lt;br /&gt;
* #mootcz10 [http://www.moodlemoot.cz/ MoodleMoot Czech Republic, Brno] 10-11 June 2010&lt;br /&gt;
* #mootfr10 6th French MoodleMoot&lt;br /&gt;
* #mootIT10 MoodleMoot Italia 2010&lt;br /&gt;
* #mootnl10 MoodleMoot NL 2010&lt;br /&gt;
* #mootPL10 Second Polish MoodleMoot, 4-5 November 2010, Czestochowa, Poland, http://moodlemoot.pl&lt;br /&gt;
* #mootusin10 Goshen, Indiana, USA 26-28 July, 2010&lt;br /&gt;
* #mootustx10 Austin, Texas, USA 2-3 August, 2010&lt;br /&gt;
* #mootfr11 [http://moodlemoot2011.uvt.rnu.tn/ 7th French MoodleMoot], Hammamet, Tunisia, 27-29 June 2011&lt;br /&gt;
* #mootde12 [http://moodlemoot.de/ German Moodlemoot], Münster, Germany, 13-16 March 2012&lt;br /&gt;
* #mootfr12 [http://moodlemoot2012.unimes.fr/ 8th French MoodleMoot], Nîmes, France, 20-22 June 2012&lt;br /&gt;
* #mootde13 [http://moodlemoot.de/ German Moodlemoot], München, Germany, 28 Feb - 1 Mar 2013&lt;br /&gt;
* #mootfr13 [http://moodlemoot2013.univ-bordeaux.fr/ 9th French MoodleMoot], Bordeaux, France, 5-7 June 2013&lt;br /&gt;
* #smootau13 [http://http://school.moodlemoot.com.au/ 2nd Australian Schoolmoot], Sydney, Australia, 2-4 October 2013&lt;br /&gt;
* #mootfr14 [http://moodlemoot2014.univ-paris3.fr 10th French MoodleMoot], Paris, 4-6 June 2014&lt;br /&gt;
* #mootfr15 [https://moodlemoot2015.univ-tours.fr 11th French MoodleMoot], Tours, 10-12 June 2015&lt;br /&gt;
* #mootfr16 [http://2016.moodlemoot.fr 12th French MoodleMoot], Sierre, Switzerland, 6-8 July 2016&lt;br /&gt;
* #mootfr17 [http://2017.moodlemoot.fr 13th French MoodleMoot], Lyon, 28-30 June 2017&lt;br /&gt;
* #mootfr18 [https://2018.moodlemoot.fr 14th French MoodleMoot], Bruxelles, 4-6 July 2018&lt;br /&gt;
* #mootfr19 [https://2019.moodlemoot.fr 15th French MoodleMoot], Rennes, 3-5 July 2019&lt;br /&gt;
* #mootBR19  [https://www.moodlebrasil.org 19th Brazil MoodleMoot], São Paulo, 25-26 April 2019&lt;br /&gt;
* #mootBR19  [https://www.moodlebrasil.org 20th Brazil MoodleMoot], São Luís-MA, 10-11 October 2019&lt;br /&gt;
* #mootBR21  [https://www.moodlebrasil.org 21th Brazil MoodleMoot], Brazil - Online, 27-28 May 2020&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
&lt;br /&gt;
* Lounge discussion [http://moodle.org/mod/forum/discuss.php?d=121619 A standard naming scheme for Moodle hashtags]&lt;/div&gt;</summary>
		<author><name>Anderson.blaine</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/310/en/index.php?title=Adding_a_new_course&amp;diff=139621</id>
		<title>Adding a new course</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/310/en/index.php?title=Adding_a_new_course&amp;diff=139621"/>
		<updated>2021-02-08T13:03:03Z</updated>

		<summary type="html">&lt;p&gt;Anderson.blaine: /* Automatically approving course requests */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Courses}}&lt;br /&gt;
==Adding a course==&lt;br /&gt;
&lt;br /&gt;
By default a regular teacher can&#039;t add a new course. To add a new course to Moodle, you need to have either [[Administrator|Administrator]], [[Course creator|Course Creator]] or [[Manager|Manager]] rights.To add a course:&lt;br /&gt;
*From the Site administration link, click Courses&amp;gt;Manage courses and categories&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
[[File:26addcourse1.png|400px|thumb|center|Click New course in the category page on the right]]&lt;br /&gt;
&lt;br /&gt;
*Click on the category where you want your course to be. For more information see [[Course categories|Course categories]]&lt;br /&gt;
*Click the &amp;quot;New course&amp;quot; link&lt;br /&gt;
*Enter the [[Course settings|course settings]], and then choose either to &amp;quot;Save and return&amp;quot; to go back to your course, or &amp;quot;Save and display&amp;quot; to go to the next screen.&lt;br /&gt;
&lt;br /&gt;
[[File:newcoursesavereturn.png]]&lt;br /&gt;
&lt;br /&gt;
*On the next screen,if you have chosen &amp;quot;Save and display&amp;quot;, choose your students/teachers to assign to the course.&lt;br /&gt;
&lt;br /&gt;
==Deleting a course==&lt;br /&gt;
&lt;br /&gt;
Teachers cannot delete courses. Managers (i.e. users with a role for which the capability [[Capabilities/moodle/course:delete|moodle/course:delete]] is allowed) can delete courses and [[Course creator|course creators]] can delete courses they have created themselves, but only within 24 hours of creating the course. This is so that courses created by mistake may be deleted without needing to ask an administrator.&lt;br /&gt;
&lt;br /&gt;
Administrators can always delete courses.&lt;br /&gt;
&lt;br /&gt;
To delete a course (as an admin or manager):&lt;br /&gt;
# From the Site administration link, click  Courses &amp;gt; Manage courses and categories&lt;br /&gt;
# Click the course&#039;s category and click the course in the screen on the right.&lt;br /&gt;
# Click the Delete link.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|[[File:26coursedelete.png|200px|thumb|center|Deleting a course]]&lt;br /&gt;
|}&lt;br /&gt;
You can delete multiple courses by: &lt;br /&gt;
*Creating a new (temporary) category. You can name it &amp;quot;To be deleted&amp;quot;.&lt;br /&gt;
*Select and &#039;&#039;&#039;move&#039;&#039;&#039; the &amp;quot;About to be deleted&amp;quot; courses to that category (&amp;quot;To be deleted&amp;quot;).&lt;br /&gt;
*Delete the category (&amp;quot;To be deleted&amp;quot;) and choose &amp;quot;Delete ALL - cannot be undone&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
There is no user interface for course creators to delete courses they have created; however they can do so by editing the URL of the course from &amp;lt;nowiki&amp;gt;http://yourmoodlesite.net/course/view.php?id=N&amp;lt;/nowiki&amp;gt; to &amp;lt;nowiki&amp;gt;http://yourmoodlesite.net/course/delete.php?id=N&amp;lt;/nowiki&amp;gt; (replacing &#039;view&#039; with &#039;delete&#039;).&lt;br /&gt;
&lt;br /&gt;
==Sorting courses==&lt;br /&gt;
Courses may be sorted by an admin or manager from &#039;&#039;Administration&amp;gt;Site administration&amp;gt;Courses&amp;gt;Manage courses and categories.&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Courses may be sorted by ascending/descending and by time created.&lt;br /&gt;
[[File:coursesort.png|thumb|200px|center|Sorting courses]]&lt;br /&gt;
&lt;br /&gt;
==Course requests==&lt;br /&gt;
&lt;br /&gt;
The course request feature can be enabled by an administrator in &#039;&#039;Administration &amp;gt; Site administration &amp;gt; Courses &amp;gt; Course request&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
An admin can set the default category for course requests, whether users can select a category when requesting a course, and who can receive notification of course requests (from a list of users with the capability [[Capabilities/moodle/site:approvecourse|moodle/site:approvecourse]]).&lt;br /&gt;
&lt;br /&gt;
A  &#039;Request a new course&#039; button will then appear on the &#039;All courses&#039; page. The All courses page can be accessed via a link in the [[Courses block]]. Alternatively, you can create a link (in an HTML block or page resource etc) to the request a new course page &amp;lt;nowiki&amp;gt;https://yourmoodlesite.org/course/request.php&amp;lt;/nowiki&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
If course requests are enabled, by default all authenticated users can make course requests. See [[Course requester role]] for details of how to restrict users who can make course requests.&lt;br /&gt;
===Automatically approving course requests===&lt;br /&gt;
A plugin [https://moodle.org/plugins/tool_courseautoapprove Course auto-approve] allows for courses to be automatically approve, as in the [https://learn.moodle.org Learn Moodle Basics MOOC]&lt;br /&gt;
&lt;br /&gt;
==Bulk course creation==&lt;br /&gt;
&lt;br /&gt;
For full details on how to bulk create courses and use course templates, see [[Upload courses]].&lt;br /&gt;
&lt;br /&gt;
# Go to &#039;&#039;Administration &amp;gt; Site Administration &amp;gt; Courses &amp;gt; Upload courses&#039;&#039;.&lt;br /&gt;
# Upload a CSV file either by dragging and dropping or using the button to select from the File picker.&lt;br /&gt;
# Select your import options and click Preview. If the settings are acceptable, click Upload.&lt;br /&gt;
&lt;br /&gt;
==Course templates==&lt;br /&gt;
&lt;br /&gt;
It is possible, from &#039;&#039;Administration&amp;gt;Site Administration&amp;gt;Courses&amp;gt;Upload courses&#039;&#039; to specify a course and settings to use as  template for future courses.&lt;br /&gt;
&lt;br /&gt;
Default blocks for new courses can also be configured in config.php.&lt;br /&gt;
&lt;br /&gt;
===Using an existing course as a template===&lt;br /&gt;
&lt;br /&gt;
First, create or locate on your Moodle the course you wish to use as a template and make a note of its shortname. A template course might for example have common headings or section summaries or policy agreements used throughout the site for consistency.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Note that only the content of the course will be restored; not its settings. Settings are added separately.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
====Method 1====&lt;br /&gt;
&lt;br /&gt;
*Create your csv file. See [[Upload courses]] for accepted fields.&lt;br /&gt;
*From the Site administration link, click Courses&amp;gt;Upload courses and add your file.&lt;br /&gt;
*Preview it and scroll down to &#039;Course process&#039;. In the box &#039;Restore from this course after upload&#039;, add the shortname of your template course.&lt;br /&gt;
*If you are creating several courses using the same template and you wish them all to have the same settings, you can specify these in the Default course values.&lt;br /&gt;
*Upload your csv file.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|[[File:template1.png|thumb|400px|Adding shortname of template course]]&lt;br /&gt;
|&lt;br /&gt;
|[[File:26defaultcoursevalues.png|thumb|400|Default course values]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
====Method 2====&lt;br /&gt;
&lt;br /&gt;
*All the settings and the chosen template course can be specified in the csv file you create. Use &#039;&#039;templatecourse&#039;&#039; as the field for your chosen template course, and use the course shortname. See [[Upload courses]] for full list of fields you can include.&lt;br /&gt;
*Here is an example of a csv file for restoring a course to be used as a template. It specifies for example the theme, language, enrolment method and alternative names for student and teacher.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code bash&amp;gt;&lt;br /&gt;
shortname,fullname,category,newsitems,theme,lang,format,enrolment_1,enrolment_1_role,role_student,role_teacher,templatecourse&lt;br /&gt;
Knit,Knitting,2,0,afterburner,fr,topics,manual,student,NewKnitter,MasterKnitter,OMT&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
*Go to Administration&amp;gt;Site administration&amp;gt;Courses&amp;gt;Upload courses and add your csv file.&lt;br /&gt;
&lt;br /&gt;
===Using a backup course as a template===&lt;br /&gt;
&lt;br /&gt;
It is possible during the process of creating courses with a csv file in &#039;&#039;Site administration&amp;gt;Administration&amp;gt;Courses&amp;gt;Upload courses&#039;&#039; to specify and upload a backup file to be used as a template.&lt;br /&gt;
&lt;br /&gt;
*Create your csv file. See [[Upload courses]] for accepted fields.&lt;br /&gt;
*From &#039;&#039;Site administration&amp;gt;Administration&amp;gt;Courses&amp;gt;Upload courses&#039;&#039;, add your file.&lt;br /&gt;
*Preview it and scroll down to &#039;Course process&#039;. In the box &#039;Restore from this file after upload&#039;, add the backup file you wish to use as the template.&lt;br /&gt;
*If you are creating several courses using the same template and you wish them all to have the same settings, you can specify these in the &#039;Default course values&#039; section.&lt;br /&gt;
*Alternatively, you can specify the course settings (such as format, enrolment methods, language) in the csv file. This method is useful if you wish different courses using the same template to have different settings.&lt;br /&gt;
*Upload your csv file.&lt;br /&gt;
{|&lt;br /&gt;
|[[File:template2.png|thumb|400px|Uploading a template course]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Using the course templates plugin===&lt;br /&gt;
With emeneo&#039;s course templates plugin you can very easily create template based courses. More information and the plugin package you can find here: [https://moodle.org/plugins/local_course_templates https://moodle.org/plugins/local_course_templates]&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
&lt;br /&gt;
===Screencasts===&lt;br /&gt;
* [http://youtu.be/MzK2jb-9SwE Bulk course creation]&lt;br /&gt;
&lt;br /&gt;
===Forum discussions===&lt;br /&gt;
*Using Moodle [http://moodle.org/mod/forum/discuss.php?d=83830 Hide Courses from some users or students] forum discussion&lt;br /&gt;
&lt;br /&gt;
[[de:Kurs anlegen]]&lt;br /&gt;
[[es:Añadiendo un nuevo curso]]&lt;br /&gt;
[[eu:Ikastaroak_%28Kudeatzaileak%29]]&lt;br /&gt;
[[fr:Ajouter_un_cours]]&lt;br /&gt;
[[ja:新しいコースを追加する]]&lt;/div&gt;</summary>
		<author><name>Anderson.blaine</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/310/en/index.php?title=MySQL_full_unicode_support&amp;diff=136689</id>
		<title>MySQL full unicode support</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/310/en/index.php?title=MySQL_full_unicode_support&amp;diff=136689"/>
		<updated>2020-03-02T23:44:26Z</updated>

		<summary type="html">&lt;p&gt;Anderson.blaine: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Environment}}&lt;br /&gt;
==UTF-8==&lt;br /&gt;
&lt;br /&gt;
UTF-8 is a character encoding that most websites use. It encodes each of the 1,112,064 valid code points. To store all of this information, four bytes is required. The most popular values are in the three byte region. MySQL by default only uses a three byte encoding and so values in the four byte range (eg. Asian characters and Emojis) can not be stored. Any attempt to enter a text that contains four byte characters will result in a Moodle database error.&lt;br /&gt;
&lt;br /&gt;
MySQL does provide full four byte UTF-8 support, but it requires certain database settings to be configured. From version 3.3 on Moodle uses full UTF-8 for both MySQL and MariaDB by default. Existing databases will still run with partial support, but it is recommended to move over to full support.&lt;br /&gt;
&lt;br /&gt;
Moodle comes with a Command Line Interface (CLI) script for converting to full UTF-8 for MySQL (and MariaDB). Before Moodle versions 3.1.5 and 3.2.2 this conversion tool would only change the Collation to some variant of &#039;utf8_bin&#039;. &#039;utf8_unicode_ci&#039; was the recommended Collation. We now recommend using &#039;utf8mb4_unicode_ci&#039; which supports four byte characters (utf8_unicode_ci only supports three).&lt;br /&gt;
&lt;br /&gt;
This script will attempt to change the database Collation, Character set, default table settings and column definitions.&lt;br /&gt;
&lt;br /&gt;
To summarise:&lt;br /&gt;
&lt;br /&gt;
* Fresh installs of Moodle 3.1.5 and 3.2.2 onwards will use utf8mb4 by default, if the database server is configured appropriately (see below).&lt;br /&gt;
* Sites upgrading to Moodle 3.1.5 or 3.2.2 can use the script to update to utf8mb4. In Moodle 3.3, 3.4 and 3.5 a warning will show that the database isn&#039;t using full UTF-8 support and suggest moving to &#039;utf8mb4_unicode_ci&#039;, but you may choose to keep using &#039;utf8_*&#039;.&lt;br /&gt;
&lt;br /&gt;
===File format===&lt;br /&gt;
&lt;br /&gt;
To allow for large indexes on columns that are a varchar, a combination of settings needs to be set. The file format for the system needs to be using &amp;quot;Barracuda&amp;quot;. This allows for the row format to be set to &amp;quot;Compressed&amp;quot; or &amp;quot;Dynamic&amp;quot;. To enable this setting see the upgrade steps listed below. Moodle will not install if you have large format enabled without the Barracuda file format.&lt;br /&gt;
&lt;br /&gt;
===File per table===&lt;br /&gt;
&lt;br /&gt;
To enable this setting see the upgrade steps listed below.&lt;br /&gt;
&lt;br /&gt;
===Large prefix===&lt;br /&gt;
&lt;br /&gt;
This in conjunction with the row format being either &amp;quot;Compressed&amp;quot; or &amp;quot;Dynamic&amp;quot; allows for large varchar indexes above 191 characters.&lt;br /&gt;
To enable this setting see the upgrade steps listed below.&lt;br /&gt;
&lt;br /&gt;
==Steps to upgrade==&lt;br /&gt;
&lt;br /&gt;
Most important: Please backup your database before making any changes or running the CLI script.&lt;br /&gt;
&lt;br /&gt;
* Change configuration settings for MySQL (exactly the same for MariaDB). This step is optional. You can run the script and it will try and make these changes itself. If errors occur then try manually changing these settings as listed below.&lt;br /&gt;
** On Linux based systems you will want to alter my.cnf. This may be located in &#039;/etc/mysql/&#039;.&lt;br /&gt;
** Make the following alterations to my.cnf:&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
[client]&lt;br /&gt;
default-character-set = utf8mb4&lt;br /&gt;
&lt;br /&gt;
[mysqld]&lt;br /&gt;
innodb_file_format = Barracuda&lt;br /&gt;
innodb_file_per_table = 1&lt;br /&gt;
innodb_large_prefix&lt;br /&gt;
&lt;br /&gt;
character-set-server = utf8mb4&lt;br /&gt;
collation-server = utf8mb4_unicode_ci&lt;br /&gt;
skip-character-set-client-handshake&lt;br /&gt;
&lt;br /&gt;
[mysql]&lt;br /&gt;
default-character-set = utf8mb4&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
* Restart your MySQL server.&lt;br /&gt;
* Run the CLI script to convert to the new Character set and Collation (requires Moodle 3.1.5, 3.2.2 or newer): &lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
$ php admin/cli/mysql_collation.php --collation=utf8mb4_unicode_ci&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
* Make sure to repair and optimize all databases and tables.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
mysqlcheck -u root -p --auto-repair --optimize --all-databases&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
NOTE: On very large sites this may take a long time to run. You should probably establish how long on a test install before taking your live site offline. In some cases you might consider dumping and re-importing your data.&lt;br /&gt;
&lt;br /&gt;
* Adjust the $CFG-&amp;gt;dboptions Array in your &#039;&#039;&#039;config.php&#039;&#039;&#039; to make sure that Moodle uses the right Collation when connecting to the MySQL Server: &lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
$CFG-&amp;gt;dboptions = array(&lt;br /&gt;
  &amp;amp;hellip;&lt;br /&gt;
  &#039;dbcollation&#039; =&amp;gt; &#039;utf8mb4_unicode_ci&#039;,&lt;br /&gt;
  &amp;amp;hellip;&lt;br /&gt;
);&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you only have access to the database command line (or something like phpmyadmin) you can try the following sql commands:&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
SET GLOBAL innodb_file_format = barracuda&lt;br /&gt;
&lt;br /&gt;
SET GLOBAL innodb_file_per_table = 1&lt;br /&gt;
&lt;br /&gt;
SET GLOBAL innodb_large_prefix = &#039;on&#039;&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Try adding some Emojis (e.g. 😂💩) to your Moodle site to verify that the upgrade was successful.&lt;br /&gt;
&lt;br /&gt;
[[Category:Environment|UTF-8]]&lt;br /&gt;
[[Category:UTF-8]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[es:MySQL soporte unicode completo]]&lt;br /&gt;
[[fr:Support unicode complet pour MySQL]]&lt;br /&gt;
[[de:MySQL Unicode Unterstützung]]&lt;/div&gt;</summary>
		<author><name>Anderson.blaine</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/310/en/index.php?title=Upload_users&amp;diff=136639</id>
		<title>Upload users</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/310/en/index.php?title=Upload_users&amp;diff=136639"/>
		<updated>2020-02-12T00:45:12Z</updated>

		<summary type="html">&lt;p&gt;Anderson.blaine: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Accounts}}&lt;br /&gt;
==Uploading users via text file==&lt;br /&gt;
&lt;br /&gt;
There are many options for uploading information (fields associated with a user) with this method: from enrolling users in multiple courses with course specific [[Roles|roles]] to updating user information in the [[User profile]] to deleting users from the site.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Tip:&#039;&#039; It is usually not necessary to upload users in bulk with Upload users. To keep maintenance work down you should first explore forms of authentication that do not require manual maintenance, such as [[External database authentication|connecting to existing external databases]] or letting the users create their own accounts ([[Self enrolment]]). See [[Authentication]] for more information.&lt;br /&gt;
&lt;br /&gt;
{{MediaPlayer | url = https://youtu.be/_kNMOr7Tdw0 | desc = How to bulk upload users and add to courses}}&lt;br /&gt;
&lt;br /&gt;
==File formats for upload users file==&lt;br /&gt;
The upload users file has fields separated by a comma (or other delimiter) ONLY - no space.   The first line contains the valid field names.  The rest of the lines (records) contain information about each user.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Tip:&#039;&#039; Avoid special characters in field information like quotes or other commas. Test a file with only one record before a large upload.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Tip:&#039;&#039; You can use a spread sheet program to create the file with the required columns and fields. Then save the file as &amp;quot;CSV (comma delimited)&amp;quot;. These files can be opened with simple text editors (eg, [https://notepad-plus-plus.org/ Notepad++]) for verification. &lt;br /&gt;
&lt;br /&gt;
===Valid upload file for testing===&lt;br /&gt;
&lt;br /&gt;
{{New features}}&lt;br /&gt;
*From Site administration / Users / Upload users, an example text (.csv) file is available. It includes can be downloaded and adapted to your needs. &lt;br /&gt;
&lt;br /&gt;
username,firstname,lastname,email&lt;br /&gt;
&lt;br /&gt;
student1,Student,One,s1@example.com&lt;br /&gt;
&lt;br /&gt;
student2,Student,Two,s2@example.com&lt;br /&gt;
&lt;br /&gt;
student3,Student,Three,s3@example.com&lt;br /&gt;
&lt;br /&gt;
*Additional fields can be added as below. The course and cohort must already have been manually created.&lt;br /&gt;
&lt;br /&gt;
username,firstname,lastname,email,course1,group1,cohort1&lt;br /&gt;
&lt;br /&gt;
student1,Student,One,s1@example.com,math102,groupA,cohortZ&lt;br /&gt;
&lt;br /&gt;
student2,Student,Two,s2@example.com,math102,groupB,cohort Y&lt;br /&gt;
&lt;br /&gt;
student3,Student,Three,s3@example.com,math102,groupA,cohortZ&lt;br /&gt;
&lt;br /&gt;
== User Fields that can be included==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Tip:&#039;&#039; We strongly recommend that you test a file that contains fields you proposed to use with one user before attempting a file upload for the first time. &lt;br /&gt;
&lt;br /&gt;
===Required fields=== &lt;br /&gt;
&lt;br /&gt;
These are the required user identification fields:&lt;br /&gt;
&amp;lt;code&amp;gt;username,firstname,lastname,email&amp;lt;/code&amp;gt;&lt;br /&gt;
Validity checks are performed for:&lt;br /&gt;
* &#039;&#039;&#039;username&#039;&#039;&#039; can only contain alphabetical &#039;&#039;&#039;lowercase&#039;&#039;&#039; letters , numbers, hypen &#039;-&#039;, underscore &#039;_&#039;, period &#039;.&#039;, or at-sign &#039;@&#039; &lt;br /&gt;
* &#039;&#039;&#039;email&#039;&#039;&#039; is in the form: &#039;&#039;name@example.com&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
===Passwords===&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;password&amp;quot; field is optional if the &#039;New user password&#039; setting on the upload screen is set to &amp;quot;Create password if needed and send via email&amp;quot;  but is required if the setting to &amp;quot;Field required in file&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
If included, values should meet the requirements for the site&#039;s [[Site_policies#Password_policy|Password policy]]. &lt;br /&gt;
&lt;br /&gt;
To force password change for a particular user, set the password field to &#039;&#039;&#039;changeme&#039;&#039;&#039;. If omitted, a password will be generated for each user (during the next Cron job) and welcome e-mails sent out. The text for the welcome e-mail is in the language settings in &#039;&#039;Site administration &amp;gt; Language &amp;gt; Language customisation&#039;&#039;  with a String identifier of &#039;newusernewpasswordtext&#039;.&lt;br /&gt;
&lt;br /&gt;
===Optional user fields===&lt;br /&gt;
&lt;br /&gt;
Note: Commas within  a field must be encoded as &amp;amp;#44 - the script will decode these back to commas.&lt;br /&gt;
Tip: For Boolean fields with only two values, use &#039;&#039;&#039;0&#039;&#039;&#039; for false and &#039;&#039;&#039;1&#039;&#039;&#039;for true. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
To provide values other than the default you can include one or more of these optional user fields:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;institution,department,city,country,lang,auth,timezone,idnumber,icq,phone1,phone2,address,url,description,mailformat,maildisplay,maildigest,htmleditor,autosubscribe,interests,theme&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Most of the these are user profile fields or user preference fields that belong to the user profile and are the filled in the user or at manual creation. Some however require specific formats:&lt;br /&gt;
&lt;br /&gt;
See [[Additional name fields]] for more details. Key things to note are:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;country&#039;&#039;&#039; - use the country TWO LETTER CODE, in upper case, eg AU,ES,GB,US. These are all UPPER CASE. Using &amp;quot;au&amp;quot; or &amp;quot;es&amp;quot; or &amp;quot;USA&amp;quot; as a country code will result in a database error. If you are having trouble working out the two-letter code for a country, you can consult the list of [https://www.iso.org/obp/ui/#search country names and code elements] available on the ISO Website. A common error is to use UK for United Kingdom; it should be GB.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;lang&#039;&#039;&#039; - use the two letter (or extended four lettter) code as defined in the Moodle language packs, e.g. en, es, en_us, de, in &#039;&#039;Site administration &amp;gt; Language &amp;gt; Language packs&#039;&#039;. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;auth&#039;&#039;&#039; - The auth field must be used if the site uses an alternative authentication method, such as LDAP, as otherwise the authentication method will default to manual and users using a different auth method won&#039;t be able to log in. &lt;br /&gt;
Use the shortname codes defined in Plugins &amp;gt; Authentication for the various types, e.g. manual, nlogin, ldap, cas, mnet, db, none. If you do not include an auth column, then newly created users will be created with the manual account type.&lt;br /&gt;
&lt;br /&gt;
You can set &amp;quot;auth&amp;quot; to &amp;quot;nologin&amp;quot; in your csv file which will mean that then created users cannot login.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;timezone&#039;&#039;&#039; - Should be in the format as found in the Location settings in terms of Zone/Region, eg. Australia/Sydney, Asia/Kathmandu, Europe/Madrid, etc. The entry is case sensitive so Europe/London will work but europe/london will not.&lt;br /&gt;
&lt;br /&gt;
NOTE: Needed: settings for &#039;&#039;&#039;mailformat&#039;&#039;&#039;,&#039;&#039;&#039;maildisplay&#039;&#039;&#039;,&#039;&#039;&#039;htmleditor&#039;&#039;&#039;,&#039;&#039;&#039;autosubscribe&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;maildigest&#039;&#039;&#039; To prevent users from receiving a large number of emails from courses or forced subscription forums use the &#039;&#039;&#039;maildigest&#039;&#039;&#039;.  The options for this field are 0 = No digest, 1 = Complete digest and 2 = Digest with just subjects.&lt;br /&gt;
&#039;&#039;maildisplay&#039;&#039;&#039; allows you to set the email display option for a user. The options for this field are &amp;quot;0&amp;quot; = Hide my email address from non-privileged users, &amp;quot;1&amp;quot; = Allow everyone to see my email address and &amp;quot;2&amp;quot; = Allow only other course members to see my email address.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;theme&#039;&#039;&#039; User themes may be added by using &#039;classic&#039;, &#039;boost&#039; or the name of any other installed theme. The value should be the short name of the theme, e.g &#039;boost&#039; not &#039;Boost&#039;, &#039;fordson&#039; not &#039;Fordson&#039;.&lt;br /&gt;
&lt;br /&gt;
===Custom profile field names===&lt;br /&gt;
&lt;br /&gt;
These are optional and depend on whether you have created any custom profile fields in your site. The name of the header in file is of the form &#039;profile_field_xxxxx&#039; where xxxx is the unique shortname of custom user profile field name as you created it. &lt;br /&gt;
&lt;br /&gt;
The field name should match the case of the profile field shortname. So, for instance if the shortname of your custom profile field is all upper case, for example, &#039;&#039;DOB&#039;&#039;, then use a header of &#039;&#039;profile_field_DOB&#039;&#039; to match the case, not &#039;&#039;profile_field_dob&#039;&#039;, which will produce a &amp;quot;is not a valid field name&amp;quot; error. Likewise, a mixed case shortname such as &#039;&#039;Dob&#039;&#039; should have a header of &#039;&#039;profile_field_Dob&#039;&#039;. (The exception to this is if the shortname is all lower case, then any case will work in the field header, which is a historical quirk: but best practice is to match the case and you will avoid errors.)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;profile_field_xxxxx&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Example&#039;&#039;&#039;: To create a custom field &amp;quot;genre&amp;quot;, you must write a shortname &amp;quot;genre&amp;quot; in the new field, and write &amp;quot;profile_field_genre&amp;quot; in the header of the .csv file.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For custom profile fields that are dates, use the ISO standard format YYYY-MM-DD, eg. 2014-06-19 which will then be properly localized in the interfaced. For example, a field called dohire for date of hire, the fields could be:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
username,firstname,lastname,email,profile_field_dohire&lt;br /&gt;
blumbergh,Bill,Lumbergh,blumbergh@example.com,1990-02-19&lt;br /&gt;
pgibbons,Peter,BGibbons,pgibbons@example.com,1996-06-05&lt;br /&gt;
tsmykowski,Tom,Smykowski,tsmykowski@example.com,1970-01-01 &lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For custom profile fields that are a menu, use the corresponding value in the menu list from field as you defined it. For example: a custom field &#039;corporatedivision&#039; with one of three values &#039;Management&#039;, &#039;Development&#039; or &#039;Training&#039;. Just insert one of those three words (e.g. &#039;Training&#039;) as the value for that field. Eg.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
username,firstname,lastname,email,profile_field_corporatedivision&lt;br /&gt;
blumbergh,Bill,Lumbergh,blumbergh@example.com,Management&lt;br /&gt;
pgibbons,Peter,BGibbons,pgibbons@example.com,Development&lt;br /&gt;
tsmykowski,Tom,Smykowski,tsmykowski@example.com,Training &lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Special user change fields===&lt;br /&gt;
&lt;br /&gt;
Three special fields are used for managing user accounts, &#039;&#039;&#039;oldusername&#039;&#039;&#039;, &#039;&#039;&#039;deleted&#039;&#039;&#039; and &#039;&#039;&#039;suspended&#039;&#039;&#039;.  [[#Allow_renames|See below for details]].&lt;br /&gt;
&lt;br /&gt;
===Enrolment fields===&lt;br /&gt;
&lt;br /&gt;
You may optionally enrol users in already existing courses using manual enrolment. Only manual enrolment is done this way; if the manual enrolment method is disabled in a course, then no enrol is done.&lt;br /&gt;
&lt;br /&gt;
You use fields in the upload file of this type:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;course1,type1,role1,group1,enrolperiod1,enrolstatus1,course2,type2,role2,group2,enrolperiod2,enrolstatus2&amp;lt;/pre&amp;gt; etc.&lt;br /&gt;
&lt;br /&gt;
Header fields &#039;&#039;&#039;must&#039;&#039;&#039; have a numeric suffix such that type1,role1,group1,enrolperiod1 and enrolstatus1 all apply to course1 for course&#039;&#039;&#039;1&#039;&#039;&#039; to course&#039;&#039;&#039;n&#039;&#039;&#039;. Even if you are just doing one course enrolment, you must still use the number 1 on the heading name, i.e. course1,role1, etc. Do not use the bare headings without numbers, e.g. course,role, etc as those will generate an error.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;course#&#039;&#039;&#039; is the shortname of the course, if present the user will be enrolled in that course. Do not use the fullname of the course or it will generate an error. This field is the ONLY required field for a succesful enrolment. All the others are optional. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;type#&#039;&#039;&#039; sets the role to be used for the enrolment. A value of 1 is default course role,  2 is legacy Teacher role and 3 is legacy Non-editing Teacher.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;role#&#039;&#039;&#039; may be used to specify roles directly, using either role short name or the role id (numeric names of roles are not supported). Usually you will use the role name that is the shortname of the role as defined in Users &amp;gt;  Permissions &amp;gt; Define roles, eg. student, editingteacher. If the role column is left out, the users will be enroled in the course with the default role, which is normally student.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;group#&#039;&#039;&#039; may be used to assign users to groups in course, using name or id (numeric group names are not supported). NOTE: if the group does not already exist, it will be created.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;enrolperiod#&#039;&#039;&#039; may be used to set the enrolment duration, in days, for each course. If not explicitly set here, all the users will get the duration as set in the Manual enrolment method of the course (which defaults to 0 meaning unlimited.)&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;enrolstatus#&#039;&#039;&#039; is optional as by default all newly enrolled users are set to active. If used a value of 1, it will suspend users in the course and if a user is previously set as inactive / suspended then a value of 0 will unsuspend them and make them active again.&lt;br /&gt;
&lt;br /&gt;
=== Cohort membership assignment===&lt;br /&gt;
&lt;br /&gt;
You can assign users to any already existing Cohort by using only the &amp;quot;username&amp;quot; and the &amp;quot;Cohort ID&amp;quot; with just two fields in the file. Note that this is an exception to the usual case where the firstname, lastname and email address of the user are required.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;cohort#&#039;&#039;&#039; is the form to use and like enrolment in courses, you have to add a number to each header, so cohort1,cohort2, etc.&lt;br /&gt;
&lt;br /&gt;
Internal cohort id numbers or non-numeric Cohort IDs of existing cohorts must be used; do not use the full name are not allowed. (Note that cohort id is what is usually known elsewhere as the &amp;quot;shortname&amp;quot;.)&lt;br /&gt;
&lt;br /&gt;
Here is a sample CSV file:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
username,cohort1,cohort2&lt;br /&gt;
student1,nursing,2016class&lt;br /&gt;
student2,nursing,2014class&lt;br /&gt;
student3,nursing,2014class&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== MNet ===&lt;br /&gt;
&lt;br /&gt;
Existing [[MNet]]users can be added to courses, groups or cohorts as below by using the field header &#039;&#039;&#039;mnethostid&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
#enrolling to courses: username+mnethostid+course required&lt;br /&gt;
#adding to group: username+mnethostid+course+group required&lt;br /&gt;
#adding to cohort: username+mnethostid+cohort required&lt;br /&gt;
#suspending/reviving accounts: username+mnethostid+suspended required&lt;br /&gt;
&lt;br /&gt;
All other operations are ignored. You can not add users, delete them or update them (such as change names or email, profile fields, etc.)&lt;br /&gt;
&lt;br /&gt;
=== Set system roles ===&lt;br /&gt;
Users may also be assigned to already defined system roles, using the shortname of the system role as defined in &#039;&#039;Site administration &amp;gt; Users &amp;gt; Permissions &amp;gt; Define roles&#039;&#039; for roles with a system context defined.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;sysrole1,sysrole2,sysrole3&amp;lt;/code&amp;gt; etc&lt;br /&gt;
&lt;br /&gt;
Users may be uploaded to a system role (usually Manager or Course creator)  by entering the shortname of that role. Other roles can only be uploaded if they have already been assigned in the &#039;system&#039; context. See [[Creating custom roles]]. Multiple roles can be assigned using sysrole2, sysrole3, etc. fields. Note that the number suffix in no way relates to the number suffixes on the enrolment fields. The numbers must go up in sequence starting at 1.&lt;br /&gt;
&lt;br /&gt;
Unassigning system roles&lt;br /&gt;
Users can also be removed from a given system role by entering the shortname of that role prefixed with a minus symbol: &#039;-&#039;. If the user is currently assigned to that role, they are removed from it. If the user is not currently assigned to that system role, the field value is ignored. However, the field value must refer to a system role that does exist on the system, otherwise an error will occur.&lt;br /&gt;
[[File:GlobalRoles1.png|thumb|500px|center|Example of a file for uploading users with global/system roles]]&lt;br /&gt;
&lt;br /&gt;
==Upload user process==&lt;br /&gt;
&lt;br /&gt;
# Create file for uploading&lt;br /&gt;
# Go to &#039;&#039;Site administration &amp;gt; Users &amp;gt; Accounts &amp;gt; Upload users&#039;&#039;&lt;br /&gt;
# Add file to upload&lt;br /&gt;
# Upload users preview - check settings and default user profile settings&lt;br /&gt;
# Upload users preview - click &amp;quot;Upload users&amp;quot;&lt;br /&gt;
# Upload users results - shows list of users, exceptions made in upload and summary of number of users&lt;br /&gt;
# Upload users results - click &amp;quot;Continue&amp;quot;&lt;br /&gt;
# Returns to Upload users screen&lt;br /&gt;
&lt;br /&gt;
==Updating users preview==&lt;br /&gt;
There are various settings to better control the desired upload behaviour. These settings are found on the &amp;quot;Upload users preview&amp;quot; page.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Warning&#039;&#039;&#039;: errors updating existing accounts can affect your users badly. &#039;&#039;&#039;&#039;&#039;Be careful&#039;&#039;&#039;&#039;&#039; when using the options to update.&lt;br /&gt;
&lt;br /&gt;
====Upload type====&lt;br /&gt;
The Upload type specifies how to handle existing accounts.&lt;br /&gt;
&lt;br /&gt;
;Add new only, skip existing users : is the default Moodle upload type. It creates a new user account for each new record in the uploaded file. If an existing username is found in the uploaded file matches an existing username, that record is &#039;&#039;&#039;skipped&#039;&#039;&#039;. By skipping the existing user account, the data in the existing record is not touched (in contrast to the &amp;quot;Add new and update existing users&amp;quot; option) and a second new user account is &#039;&#039;&#039;not&#039;&#039;&#039; created (in contrast to the &amp;quot;Add all, append number to usernames if needed&amp;quot; option). &lt;br /&gt;
&lt;br /&gt;
;Add all, append number to usernames if needed : creates a new user account for each record in the uploaded file. If an existing user account is found, a new account will be created with a number appended to the username. For example, if a user account for username &#039;jsmith&#039; already exists and a new record in the uploaded file contains a record forusername &#039;jsmith&#039; an additional user account is created with a 1 &#039;&#039;&#039;appended&#039;&#039;&#039; to the username to produce user &#039;jsmith1&#039;. &lt;br /&gt;
&lt;br /&gt;
;Add  new and update existing users : creates a new user account for each new user in the upload file. If an existing user account with the same username is found, the account information is &#039;&#039;&#039;updated&#039;&#039;&#039; by the data in the uploaded file. &lt;br /&gt;
&lt;br /&gt;
;Update existing users only : ignores any new users found in the upload file and updates the user account if a matching username record is found in the uploaded file.&lt;br /&gt;
&lt;br /&gt;
====New user password====&lt;br /&gt;
When creating a new user account Moodle can create a new password (if one is not provided) or require a password in the uploaded file.&lt;br /&gt;
&lt;br /&gt;
;Create password if needed and send via email: creates a random default password for each new user account if one is not provided in the uploaded file, and emails the user their user information and new password.&lt;br /&gt;
&lt;br /&gt;
;Field required in file : requires that a password be provided in the uploaded file in order. If a password is not provided, an error is generated and the user account is not created. No notification of this user information or password is sent to the user.&lt;br /&gt;
&lt;br /&gt;
====Existing user details====&lt;br /&gt;
The Existing user details options are only available when the Upload type allows existing user accounts to be updated. It specifies how Moodle should process user detail information for existing users.&lt;br /&gt;
&lt;br /&gt;
;No changes : ignores user detail data in the uploaded and leaves the existing user account data unchanged.&lt;br /&gt;
;Override with file : overwrites data in the existing user account with the data provided in the uploaded file.&lt;br /&gt;
;Override with file and defaults : overwrites data in the existing user account with data provided in the uploaded file and fills in the default values for existing user details when no data is provided in the uploaded file.&lt;br /&gt;
;Fill in missing from file and defaults : adds data in the existing user account with data provided in the uploaded file if the field is empty (does not already contain data) and fills in the default values for existing user details when no data is provided in the uploaded file.&lt;br /&gt;
&lt;br /&gt;
====Existing user password====&lt;br /&gt;
The Existing user password option appears when you you have set the &amp;quot;Existing user details&amp;quot; setting to &amp;quot;Overwrite with file&amp;quot;. It specifies how to handle password data for existing user accounts, to change them or leave them as it. This is a bit of insurance to make sure that you really want to mass change user passwords.&lt;br /&gt;
&lt;br /&gt;
;No changes : ignores password field in the uploaded user file and leaves the existing user account password untouched&lt;br /&gt;
;Update : overwrites the existing user account password with the password provided in the uploaded file&lt;br /&gt;
&lt;br /&gt;
====Force password change====&lt;br /&gt;
The Force password change option specifies when to tag a user account so that the next login attempt will require the user to change the user&#039;s password.&lt;br /&gt;
&lt;br /&gt;
;Users having a weak password : If the user account has a weak password as defined by the site&#039;s [[Password_policy#Password_policy|Password policy]] then the user will be forced to change the password during the next login attempt. This option is not shown if there the site does not have a [[Password_policy#Password_policy|Password policy]]. &lt;br /&gt;
;None : None of the users in the uploaded file will be forced to change the password during the user&#039;s next login attempt.&lt;br /&gt;
;All : All of the users in the uploaded file will be forced to change the password during the user&#039;s next login attempt.&lt;br /&gt;
&lt;br /&gt;
====Allow renames====&lt;br /&gt;
If the uploaded file contains the special &#039;&#039;&#039;oldusername&#039;&#039;&#039; field, it is possible to rename a user from the &#039;&#039;&#039;oldusername&#039;&#039;&#039; to a new &#039;&#039;&#039;username&#039;&#039;&#039;. The default setting is to &#039;&#039;&#039;not&#039;&#039;&#039; allow renames. Keep in mind that renaming a user will require the user to use the new username when logging in.&lt;br /&gt;
;No : ignores the &#039;&#039;&#039;oldusername&#039;&#039;&#039; field and leaves the existing user account&#039;s username field unchanged.&lt;br /&gt;
;Yes : allows the existing user account&#039;s username to be changed by the data provided in the uploaded file&#039;s username field. The &#039;&#039;&#039;oldusername&#039;&#039;&#039; will be searched for and then updated with the data provided in the username column.&lt;br /&gt;
&lt;br /&gt;
====Allow deletes====&lt;br /&gt;
If the uploaded file contains the &#039;&#039;&#039;deleted&#039;&#039;&#039; special field, it is possible to use the upload file to delete existing user accounts. The default setting is to &#039;&#039;&#039;not&#039;&#039;&#039; allow deletes. Keep in mind that deleting a user account will prevent that user from logging in. As a protection, site administrator user accounts cannot be deleted with this method. &lt;br /&gt;
;No : ignores the &#039;&#039;&#039;deleted&#039;&#039;&#039; special field in the uploaded file and leaves the existing user account unchanged&lt;br /&gt;
;Yes : allows the existing user account to be deleted when the value of the of the &#039;&#039;&#039;deleted&#039;&#039;&#039; field is 1. &lt;br /&gt;
&lt;br /&gt;
====Allow suspending and activating of accounts====&lt;br /&gt;
If the uploaded file contains the &#039;&#039;&#039;suspended&#039;&#039;&#039; special field, it is possible to use the upload file to either suspend or make active (unsuspend) existing user accounts. The default setting is to allow suspending/activating of existing user accounts. Keep in mind that suspending an existing user account will prevent that user from logging in. &lt;br /&gt;
;Yes : allows the existing user account to be suspended when the value of the of the &#039;&#039;&#039;suspended&#039;&#039;&#039; field is 1. &lt;br /&gt;
;No : ignores the &#039;&#039;&#039;suspended&#039;&#039;&#039; special field in the uploaded file and leaves the existing user account status unchanged.&lt;br /&gt;
&lt;br /&gt;
====Prevent email address duplicates====&lt;br /&gt;
It is possible, but &#039;&#039;&#039;not&#039;&#039;&#039; recommended to upload users with duplicate email addresses. By default, uploading users with duplicate email addresses is prevented. To allow duplicate email addresses, go to Site administration ► Plugins ► Authentication ► Manage authentication. You can tick &amp;quot;Allow accounts with same email&amp;quot;. Then on the upload users screen you will be allowed to change the &amp;quot;Prevent email address duplicates&amp;quot; setting. &lt;br /&gt;
&lt;br /&gt;
However, doing this is not recommended for file uploads. Test thoroughly any user uploads before implementing.&lt;br /&gt;
&lt;br /&gt;
For more info, see the [[Managing_authentication#Allow_accounts_with_same_email|Managing authentication]] docs page&lt;br /&gt;
;Yes : prevents user accounts from being created from the uploaded if an existing user account already has the same email address as found in the uploaded file&#039;s  &#039;&#039;&#039;email&#039;&#039;&#039; column.&lt;br /&gt;
;No : allows user accounts to be created if an existing user account already has the same email address found in the uploaded file&#039;s  &#039;&#039;&#039;email&#039;&#039;&#039; column.&lt;br /&gt;
&lt;br /&gt;
====Standardise usernames====&lt;br /&gt;
Standardise usernames is used by default to convert the username to all lower case and to strip out illegal characters. It is possible to not standardise the usernames; however, doing so is &#039;&#039;&#039;not&#039;&#039;&#039; recommended.&lt;br /&gt;
;Yes : standardises usernames found in the uploaded file before updating existing or creating new user accounts so that the username contains only lowercase letters and numbers.&lt;br /&gt;
;No : skips standardising usernames found in the uploaded file so that the newly created or updated usernames will be exactly as they are in the uploaded file (&#039;&#039;&#039;not recommended&#039;&#039;&#039;).&lt;br /&gt;
&lt;br /&gt;
For those seeking a more technical explanation, the process for standardising the usernames consists of ensuring the characters are all UTF-8 (fix_utf8) encoded, converting the username to lower case, and then stripping out non-letters/non-number characters (unless &#039;&#039;Site administration &amp;gt; Security &amp;gt; Site policies &amp;gt; Allow extended characters in usernames&#039;&#039; is set on) with something similar to: &lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;$username = preg_replace(&#039;/[^-\.@_a-z0-9]/&#039;, &#039;&#039;, $username);&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====Select for bulk user actions====&lt;br /&gt;
After the uploaded file has finished being processed (all new accounts have been created and existing accounts updated as specified by the previous settings), there is an option to select some of those user accounts to perform additional [[admin/user/user_bulk|bulk user actions]] such as &lt;br /&gt;
*Confirm user accounts created through Email-based self-registration which are not yet confirmed by the user&lt;br /&gt;
*Send a message (requires Messaging to be enabled)&lt;br /&gt;
*Delete user accounts&lt;br /&gt;
*Display a list of users on a page&lt;br /&gt;
*Download user data in text, ODS or Excel file format&lt;br /&gt;
*Force users to change their passwords&lt;br /&gt;
*Add users to a cohort&lt;br /&gt;
&lt;br /&gt;
By default, no users are selected for [[admin/user/user_bulk|bulk user actions]].&lt;br /&gt;
&lt;br /&gt;
;No : No users are selected for [[admin/user/user_bulk|bulk user actions]]&lt;br /&gt;
;New users : Only newly created users are selected for [[admin/user/user_bulk|bulk user actions]]&lt;br /&gt;
;Updated users : Only updated user accounts are selected for [[admin/user/user_bulk|bulk user actions]]&lt;br /&gt;
;All users : All users found (existing updated users and newly created user accounts) in the uploaded file are selected for [[admin/user/user_bulk|bulk user actions]]&lt;br /&gt;
&lt;br /&gt;
===Default values===&lt;br /&gt;
&lt;br /&gt;
You can provide default user values for some fields not included in the uploaded file. Some fields include:&lt;br /&gt;
&lt;br /&gt;
*Email display&lt;br /&gt;
*Forum auto-subscribe&lt;br /&gt;
*City/town&lt;br /&gt;
*ID number&lt;br /&gt;
*Institution&lt;br /&gt;
*Department&lt;br /&gt;
&lt;br /&gt;
By clicking the &#039;&#039;&#039;Show more....&#039;&#039;&#039; link, other default user profile fields will show up. You can set 17 different fields here, including the Authentication method, Country. Language, Timezone, as well as most other standard User profile fields.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Other fields&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
If you have created any custom profile fields for your users, they will show up here.&lt;br /&gt;
&lt;br /&gt;
==Upload user results ==&lt;br /&gt;
After accepting the preview settings by clicking on &amp;quot;Upload users&amp;quot;, you should see the the Upload users results screen.&lt;br /&gt;
[[File:Upload users results 2.0.JPG|thumb|center|The results screen; everything went well!]]&lt;br /&gt;
This screen will show you any exceptions or changes that were made to each user in the upload process.   For example if you were updating user information, the updated information will be shown. Or if a user was not added that record will be highlighted.&lt;br /&gt;
&lt;br /&gt;
The screen will summarize how many users were uploaded or updated, indicate the number of weak passwords and the number of errors.&lt;br /&gt;
&lt;br /&gt;
==Advanced potentials of Upload user==&lt;br /&gt;
===Templates===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Note: This section needs checking and updating if necessary for Moodle 2.0. Please do so and remove this note when finished.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The default values are processed as templates in which the following codes are allowed:&lt;br /&gt;
&lt;br /&gt;
* %l - will be replaced by the lastname&lt;br /&gt;
* %f - will be replaced by the firstname&lt;br /&gt;
* %u - will be replaced by the username&lt;br /&gt;
* %% - will be replaced by the %&lt;br /&gt;
&lt;br /&gt;
Between the percent sign (%) and any code letter (l, f or u) the following modifiers are allowed:&lt;br /&gt;
&lt;br /&gt;
* (-) minus sign - the information specified by the code letter will be converted to lowercase&lt;br /&gt;
* (+) plus sign - the information specified by the code letter will be converted to UPPERCASE&lt;br /&gt;
* (~) tilde sign - the information specified by the code letter will be converted to Title Case&lt;br /&gt;
* a decimal number - the information specified by the code letter will be truncated to that many characters&lt;br /&gt;
&lt;br /&gt;
For example, if the firstname is John and the lastname is Doe, the following values will be obtained with the specified templates:&lt;br /&gt;
&lt;br /&gt;
* %l%f = DoeJohn&lt;br /&gt;
* %l%1f = DoeJ&lt;br /&gt;
* %-l%+f = doeJOHN&lt;br /&gt;
* %-f_%-l = john_doe&lt;br /&gt;
*&amp;lt;nowiki&amp;gt; http://www.example.com/~%u/&amp;lt;/nowiki&amp;gt; results in  &amp;lt;nowiki&amp;gt;http://www.example.com/~jdoe/&amp;lt;/nowiki&amp;gt; (if the username is jdoe or %-1f%-l)&lt;br /&gt;
&lt;br /&gt;
Template processing is done only on default values, and not on the values retrieved from the CSV file.&lt;br /&gt;
&lt;br /&gt;
In order to create correct Moodle usernames, the username is always converted to lowercase. Moreover, if the &amp;quot;Allow extended characters in usernames&amp;quot; option in the Site policies page is off, characters different to letters, digits, dash (-) and dot (.) are removed. For example if the firstname is John Jr. and the lastname is Doe, the username %-f_%-l will produce john jr._doe when Allow extended characters in usernames is on, and johnjr.doe when off.&lt;br /&gt;
&lt;br /&gt;
When the &amp;quot;New username duplicate handling&amp;quot; setting is set to Append counter, an auto-increment counter will be append to duplicate usernames produced by the template. For example, if the CSV file contains the users named John Doe, Jane Doe and Jenny Doe without explicit usernames, the default username is %-1f%-l and New username duplicate handling is set to Append counter, then the usernames produced will be jdoe, jdoe2 and jdoe3.&lt;br /&gt;
&lt;br /&gt;
===Deleting accounts===&lt;br /&gt;
&lt;br /&gt;
If the &#039;&#039;&#039;deleted&#039;&#039;&#039; field is present, users with value 1 for it will be deleted. In this case, all the fields may be omitted, except for &#039;&#039;&#039;username&#039;&#039;&#039;. After uploading the file, be sure to change the &amp;quot;Upload type&amp;quot; to &amp;quot;Update existing users only&amp;quot; and the &amp;quot;Allow deletes&amp;quot; option to &amp;quot;Yes&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Tip:&#039;&#039;  A similar field is available for &#039;&#039;&#039;suspended&#039;&#039;&#039;. This enables a user account to be temporarily disabled rather than completely removed.&lt;br /&gt;
&lt;br /&gt;
Deleting and uploading accounts could be done with a single CSV file. For example, the following file will add the user Tom Jones and delete the user reznort:&lt;br /&gt;
&lt;br /&gt;
 username,firstname,lastname,deleted&lt;br /&gt;
 jonest,Tom,Jones,0&lt;br /&gt;
 reznort,,,1&lt;br /&gt;
&lt;br /&gt;
==Encoding file format==&lt;br /&gt;
On the initial Upload user screen, you may select the file encoding format from a pull down list.  These include UTF-8 (the default), ASCII,  ISO-8859-1 to ISO-8859-11 or any one of over 36 formats.&lt;br /&gt;
&lt;br /&gt;
==Hints==&lt;br /&gt;
&lt;br /&gt;
===Spreadsheet===&lt;br /&gt;
&lt;br /&gt;
If you use a spreadsheet program such as Excel to create your .csv file, check the resulting output in a text editor before you upload it.  It is possible to get trailing commas on each line from an empty field if you have added and deleted columns of information prior to saving the final file. Also check the character encoding. A csv file is a simple text file (ASCII or Unicode) that can be used to upload user accounts.&lt;br /&gt;
&lt;br /&gt;
Excel translates passwords that begin with - (minus) or + (plus) as zero. Even when saving as .csv and saying &amp;quot;Yes&amp;quot; to &amp;quot;Keep this format, and leave out any incompatible features.&amp;quot; Check for this before uploading, as a zero halts the upload process.&lt;br /&gt;
&lt;br /&gt;
If you use a formula in Excel to create fields (for example, the concatenate function to create a user name), then remember to copy the cells with the formula and use special paste with values checked to make them into an acceptable data for a csv file.&lt;br /&gt;
&lt;br /&gt;
The upload will also fail if you have trailing spaces at the end of your data fields. Often, this can not be removed with a simple Find &amp;quot; &amp;quot; and Replace with &amp;quot;&amp;quot;. If information has been copied from web sources than it is possible to include non-breaking spaces which will prevent your upload from being completed correctly. To find these invisible spaces, use the Find and Replace function in Excel. In the find field, hold alt and type 0160. Leave the replace field blank. &lt;br /&gt;
&lt;br /&gt;
===Field size limits===&lt;br /&gt;
Some fields have maximum character lengths, as defined in the database fields.  Typically the file will import to the preview list screen but not finish the process. Turn on debug to see the fields that are too long. The error will be &amp;quot;User not added - error&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
The sizes of some common fields, in number of characters, are currently (3.2):&lt;br /&gt;
&lt;br /&gt;
*username - 100 	 &lt;br /&gt;
*password - 255 	 &lt;br /&gt;
*idnumber - 255 	 &lt;br /&gt;
*firstname - 100 	 &lt;br /&gt;
*lastname - 100 	 &lt;br /&gt;
*lastnamephonetic - 255 	 &lt;br /&gt;
*firstnamephonetic - 255 	 &lt;br /&gt;
*middlename - 255 	 &lt;br /&gt;
*alternatename - 255 &lt;br /&gt;
*institution -  255 	 &lt;br /&gt;
*department - 255 	 &lt;br /&gt;
*address - 255 	 &lt;br /&gt;
*city - 120 	 &lt;br /&gt;
*icq -15 	 &lt;br /&gt;
*skype - 50 	 &lt;br /&gt;
*yahoo - 50 	 &lt;br /&gt;
*aim - 50&lt;br /&gt;
*msn - 50 	 &lt;br /&gt;
*phone1 - 20 	 &lt;br /&gt;
*phone2  - 20&lt;br /&gt;
&lt;br /&gt;
===All user fields listed here===&lt;br /&gt;
:All the user fields that are valid in an upload file are listed below, except for any custom fields you may have created (for which see below.)&lt;br /&gt;
 &lt;br /&gt;
&amp;lt;pre&amp;gt;firstname,lastname,username,email,password,auth,idnumber,institution,department,city,country,timezone,lang,mailformat,maildisplay,maildigest,htmleditor,autosubscribe,skype,msn,aim,yahoo,icq,phone1,phone2,address,url,description,descriptionformat,interests,oldusername,deleted,suspended,alternatename,lastnamephonetic,firstnamephonetic,middlename&amp;lt;/pre&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The enrolments into courses information are &amp;lt;pre&amp;gt;course1,type1,role1,group1,enrolperiod1,enrolstatus1&amp;lt;/pre&amp;gt; &lt;br /&gt;
where each enrolment is grouped by number.&lt;br /&gt;
&lt;br /&gt;
===Capabilities===&lt;br /&gt;
&lt;br /&gt;
You may wish to create a limited role to allow some users access to this function. Create a role at the system/site level with the following capabilities allowed:&lt;br /&gt;
* moodle/site:uploadusers&lt;br /&gt;
* moodle/role:assign&lt;br /&gt;
&lt;br /&gt;
And &lt;br /&gt;
* In &#039;Allow role assignments&#039; tab of this new role, permit it to assign the required roles that it may be uploading, especially Student, but also Teacher, Non-editing Teacher, and any other custom roles you may have created, which will be used in the uploads to assign users to.&lt;br /&gt;
&lt;br /&gt;
In particular, don&#039;t forget the moodle/role:assign capability (even if these users have it in the courses they will be enrolling users in - it won&#039;t work).&lt;br /&gt;
&lt;br /&gt;
== See also ==&lt;br /&gt;
* [[Flat file]] enrolment&lt;br /&gt;
* [[User profile fields]] for details of how to include data about custom user profile fields in the upload users file&lt;br /&gt;
* [[Upload courses]]&lt;br /&gt;
&lt;br /&gt;
Forum discussions:&lt;br /&gt;
*[http://moodle.org/mod/forum/discuss.php?d=97903 Uploading users to custom roles]&lt;br /&gt;
*[http://moodle.org/mod/forum/discuss.php?d=144569 Matriculacion con flat file csv] - discussion in Spanish&lt;br /&gt;
&lt;br /&gt;
[[fr:Importer des utilisateurs]]&lt;br /&gt;
[[ja:ユーザのアップロード]]&lt;br /&gt;
[[de:Nutzerliste hochladen]]&lt;br /&gt;
[[es:Subir usuarios]]&lt;/div&gt;</summary>
		<author><name>Anderson.blaine</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/310/en/index.php?title=Standard_Moodle_tags&amp;diff=136633</id>
		<title>Standard Moodle tags</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/310/en/index.php?title=Standard_Moodle_tags&amp;diff=136633"/>
		<updated>2020-02-07T19:48:59Z</updated>

		<summary type="html">&lt;p&gt;Anderson.blaine: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Tags are useful for connecting different bits of information together.&lt;br /&gt;
&lt;br /&gt;
Obviously it&#039;s important to use the same tags everywhere.&lt;br /&gt;
&lt;br /&gt;
This page describes standard Moodle tags that you should use when describing Moodle events on the internet (Flickr, Twitter, Facebook, del.icio.us etc)&lt;br /&gt;
&lt;br /&gt;
==General Moodle stuff==&lt;br /&gt;
&lt;br /&gt;
For general discussion of Moodle, use the tag &amp;quot;moodle&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
Twitter example:&lt;br /&gt;
 I just installed #moodle on a computer I bought ten years ago!&lt;br /&gt;
&lt;br /&gt;
==Moodle Moots==&lt;br /&gt;
&lt;br /&gt;
For Moodle conferences (Moots) use mootCCYY where:&lt;br /&gt;
* CC is a country ISO code or state abbreviation, and&lt;br /&gt;
* YY is a year.&lt;br /&gt;
&lt;br /&gt;
 mootAU09&lt;br /&gt;
&lt;br /&gt;
Capitalisation doesn&#039;t matter and just helps readability.&lt;br /&gt;
&lt;br /&gt;
The two letter code would usually be a country, but for somewhere like the US where there are different moots they might choose to use &amp;quot;us&amp;quot; or a state like &amp;quot;sf&amp;quot; or &amp;quot;ok&amp;quot;. It really doesn&#039;t matter if two moots both used mootus09 for example, because they would be separated in time.&lt;br /&gt;
&lt;br /&gt;
==Tags in use==&lt;br /&gt;
&lt;br /&gt;
* #mooteu09 MoodleMoot Euskadi&lt;br /&gt;
* #mootNL09 Amsterdam Moodlemoot&lt;br /&gt;
* #mootUS09ok Moodlemoot Oklahoma  (or #mootok09)&lt;br /&gt;
* #mootUS09SF Moodlemoot San Francisco  (or #mootsf09)&lt;br /&gt;
* #mootin09 Goshen Midwest MoodleMoot&lt;br /&gt;
* #mootus09ny MoodleMoot Delhi (or #mootny09) &lt;br /&gt;
* #mootar09 MoodleMoot Argentina&lt;br /&gt;
* #mootat09 MoodleMoot Austria &lt;br /&gt;
* #mootDE09 MoodleMoot Germany 2009&lt;br /&gt;
* #mootco09 MoodleMoot Colombia&lt;br /&gt;
* #mootcl09 MoodleMoot Chile&lt;br /&gt;
* #mootes09 MoodleMoot Spain 2009&lt;br /&gt;
* #moodle #OE09 Moodle at Online Educa 2009 in Berlin (December)&lt;br /&gt;
* #moodledev09 [[Development:Czech Hackfest 2009|Czech Hackfest 2009]]&lt;br /&gt;
* #imoot and #imoot2010 iMoot 2010&lt;br /&gt;
* #mootJP10hk Moodlemoot Japan in Hakodate, February 2010&lt;br /&gt;
* #mootDE10b Moodlemoot Germany 2010 in Berlin March&lt;br /&gt;
* #mootDE10e [http://moodle2010.de/ Moodlemoot Germany 2010 in Essen] 16-17 September 2010&lt;br /&gt;
* #mootNZ10 Moodle Moot New Zealand (Christchurch) April 2010&lt;br /&gt;
* #mootUK10 MoodleMoot UK April 2010&lt;br /&gt;
* #mootsi10 Slovenian MoodleMoot&lt;br /&gt;
* #mootok10 MoodleMoot Oklahoma&lt;br /&gt;
* #mootau10 MoodleMoot AU 2010&lt;br /&gt;
* #mootcz10 [http://www.moodlemoot.cz/ MoodleMoot Czech Republic, Brno] 10-11 June 2010&lt;br /&gt;
* #mootfr10 6th French MoodleMoot&lt;br /&gt;
* #mootIT10 MoodleMoot Italia 2010&lt;br /&gt;
* #mootnl10 MoodleMoot NL 2010&lt;br /&gt;
* #mootPL10 Second Polish MoodleMoot, 4-5 November 2010, Czestochowa, Poland, http://moodlemoot.pl&lt;br /&gt;
* #mootusin10 Goshen, Indiana, USA 26-28 July, 2010&lt;br /&gt;
* #mootustx10 Austin, Texas, USA 2-3 August, 2010&lt;br /&gt;
* #mootfr11 [http://moodlemoot2011.uvt.rnu.tn/ 7th French MoodleMoot], Hammamet, Tunisia, 27-29 June 2011&lt;br /&gt;
* #mootde12 [http://moodlemoot.de/ German Moodlemoot], Münster, Germany, 13-16 March 2012&lt;br /&gt;
* #mootfr12 [http://moodlemoot2012.unimes.fr/ 8th French MoodleMoot], Nîmes, France, 20-22 June 2012&lt;br /&gt;
* #mootde13 [http://moodlemoot.de/ German Moodlemoot], München, Germany, 28 Feb - 1 Mar 2013&lt;br /&gt;
* #mootfr13 [http://moodlemoot2013.univ-bordeaux.fr/ 9th French MoodleMoot], Bordeaux, France, 5-7 June 2013&lt;br /&gt;
* #smootau13 [http://http://school.moodlemoot.com.au/ 2nd Australian Schoolmoot], Sydney, Australia, 2-4 October 2013&lt;br /&gt;
* #mootfr14 [http://moodlemoot2014.univ-paris3.fr 10th French MoodleMoot], Paris, 4-6 June 2014&lt;br /&gt;
* #mootfr15 [https://moodlemoot2015.univ-tours.fr 11th French MoodleMoot], Tours, 10-12 June 2015&lt;br /&gt;
* #mootfr16 [http://2016.moodlemoot.fr 12th French MoodleMoot], Sierre, Switzerland, 6-8 July 2016&lt;br /&gt;
* #mootfr17 [http://2017.moodlemoot.fr 13th French MoodleMoot], Lyon, 28-30 June 2017&lt;br /&gt;
* #mootfr18 [https://2018.moodlemoot.fr 14th French MoodleMoot], Bruxelles, 4-6 July 2018&lt;br /&gt;
* #mootfr19 [https://2019.moodlemoot.fr 15th French MoodleMoot], Rennes, 3-5 July 2019&lt;br /&gt;
* #mootBR19  [https://www.moodlebrasil.org 19th Brazil MoodleMoot], São Paulo, 25-26 April 2019&lt;br /&gt;
* #mootBR19  [https://www.moodlebrasil.org 20th Brazil MoodleMoot], São Luís-MA, 10-11 October 2019&lt;br /&gt;
* #mootBR20  [https://www.moodlebrasil.org 21th Brazil MoodleMoot], São Paulo-SP, 23-24 April 2020&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
&lt;br /&gt;
* Lounge discussion [http://moodle.org/mod/forum/discuss.php?d=121619 A standard naming scheme for Moodle hashtags]&lt;/div&gt;</summary>
		<author><name>Anderson.blaine</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/310/en/index.php?title=Standard_Moodle_tags&amp;diff=136632</id>
		<title>Standard Moodle tags</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/310/en/index.php?title=Standard_Moodle_tags&amp;diff=136632"/>
		<updated>2020-02-07T19:47:25Z</updated>

		<summary type="html">&lt;p&gt;Anderson.blaine: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Tags are useful for connecting different bits of information together.&lt;br /&gt;
&lt;br /&gt;
Obviously it&#039;s important to use the same tags everywhere.&lt;br /&gt;
&lt;br /&gt;
This page describes standard Moodle tags that you should use when describing Moodle events on the internet (Flickr, Twitter, Facebook, del.icio.us etc)&lt;br /&gt;
&lt;br /&gt;
==General Moodle stuff==&lt;br /&gt;
&lt;br /&gt;
For general discussion of Moodle, use the tag &amp;quot;moodle&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
Twitter example:&lt;br /&gt;
 I just installed #moodle on a computer I bought ten years ago!&lt;br /&gt;
&lt;br /&gt;
==Moodle Moots==&lt;br /&gt;
&lt;br /&gt;
For Moodle conferences (Moots) use mootCCYY where:&lt;br /&gt;
* CC is a country ISO code or state abbreviation, and&lt;br /&gt;
* YY is a year.&lt;br /&gt;
&lt;br /&gt;
 mootAU09&lt;br /&gt;
&lt;br /&gt;
Capitalisation doesn&#039;t matter and just helps readability.&lt;br /&gt;
&lt;br /&gt;
The two letter code would usually be a country, but for somewhere like the US where there are different moots they might choose to use &amp;quot;us&amp;quot; or a state like &amp;quot;sf&amp;quot; or &amp;quot;ok&amp;quot;. It really doesn&#039;t matter if two moots both used mootus09 for example, because they would be separated in time.&lt;br /&gt;
&lt;br /&gt;
==Tags in use==&lt;br /&gt;
&lt;br /&gt;
* #mooteu09 MoodleMoot Euskadi&lt;br /&gt;
* #mootNL09 Amsterdam Moodlemoot&lt;br /&gt;
* #mootUS09ok Moodlemoot Oklahoma  (or #mootok09)&lt;br /&gt;
* #mootUS09SF Moodlemoot San Francisco  (or #mootsf09)&lt;br /&gt;
* #mootin09 Goshen Midwest MoodleMoot&lt;br /&gt;
* #mootus09ny MoodleMoot Delhi (or #mootny09) &lt;br /&gt;
* #mootar09 MoodleMoot Argentina&lt;br /&gt;
* #mootat09 MoodleMoot Austria &lt;br /&gt;
* #mootDE09 MoodleMoot Germany 2009&lt;br /&gt;
* #mootco09 MoodleMoot Colombia&lt;br /&gt;
* #mootcl09 MoodleMoot Chile&lt;br /&gt;
* #mootes09 MoodleMoot Spain 2009&lt;br /&gt;
* #moodle #OE09 Moodle at Online Educa 2009 in Berlin (December)&lt;br /&gt;
* #moodledev09 [[Development:Czech Hackfest 2009|Czech Hackfest 2009]]&lt;br /&gt;
* #imoot and #imoot2010 iMoot 2010&lt;br /&gt;
* #mootJP10hk Moodlemoot Japan in Hakodate, February 2010&lt;br /&gt;
* #mootDE10b Moodlemoot Germany 2010 in Berlin March&lt;br /&gt;
* #mootDE10e [http://moodle2010.de/ Moodlemoot Germany 2010 in Essen] 16-17 September 2010&lt;br /&gt;
* #mootNZ10 Moodle Moot New Zealand (Christchurch) April 2010&lt;br /&gt;
* #mootUK10 MoodleMoot UK April 2010&lt;br /&gt;
* #mootsi10 Slovenian MoodleMoot&lt;br /&gt;
* #mootok10 MoodleMoot Oklahoma&lt;br /&gt;
* #mootau10 MoodleMoot AU 2010&lt;br /&gt;
* #mootcz10 [http://www.moodlemoot.cz/ MoodleMoot Czech Republic, Brno] 10-11 June 2010&lt;br /&gt;
* #mootfr10 6th French MoodleMoot&lt;br /&gt;
* #mootIT10 MoodleMoot Italia 2010&lt;br /&gt;
* #mootnl10 MoodleMoot NL 2010&lt;br /&gt;
* #mootPL10 Second Polish MoodleMoot, 4-5 November 2010, Czestochowa, Poland, http://moodlemoot.pl&lt;br /&gt;
* #mootusin10 Goshen, Indiana, USA 26-28 July, 2010&lt;br /&gt;
* #mootustx10 Austin, Texas, USA 2-3 August, 2010&lt;br /&gt;
* #mootfr11 [http://moodlemoot2011.uvt.rnu.tn/ 7th French MoodleMoot], Hammamet, Tunisia, 27-29 June 2011&lt;br /&gt;
* #mootde12 [http://moodlemoot.de/ German Moodlemoot], Münster, Germany, 13-16 March 2012&lt;br /&gt;
* #mootfr12 [http://moodlemoot2012.unimes.fr/ 8th French MoodleMoot], Nîmes, France, 20-22 June 2012&lt;br /&gt;
* #mootde13 [http://moodlemoot.de/ German Moodlemoot], München, Germany, 28 Feb - 1 Mar 2013&lt;br /&gt;
* #mootfr13 [http://moodlemoot2013.univ-bordeaux.fr/ 9th French MoodleMoot], Bordeaux, France, 5-7 June 2013&lt;br /&gt;
* #smootau13 [http://http://school.moodlemoot.com.au/ 2nd Australian Schoolmoot], Sydney, Australia, 2-4 October 2013&lt;br /&gt;
* #mootfr14 [http://moodlemoot2014.univ-paris3.fr 10th French MoodleMoot], Paris, 4-6 June 2014&lt;br /&gt;
* #mootfr15 [https://moodlemoot2015.univ-tours.fr 11th French MoodleMoot], Tours, 10-12 June 2015&lt;br /&gt;
* #mootfr16 [http://2016.moodlemoot.fr 12th French MoodleMoot], Sierre, Switzerland, 6-8 July 2016&lt;br /&gt;
* #mootfr17 [http://2017.moodlemoot.fr 13th French MoodleMoot], Lyon, 28-30 June 2017&lt;br /&gt;
* #mootfr18 [https://2018.moodlemoot.fr 14th French MoodleMoot], Bruxelles, 4-6 July 2018&lt;br /&gt;
* #mootfr19 [https://2019.moodlemoot.fr 15th French MoodleMoot], Rennes, 3-5 July 2019&lt;br /&gt;
* #mootBR19  [https://www.moodlebrasil.org 19th Brazil MoodleMoot], São Paulo, 25-26 April 2019&lt;br /&gt;
* #mootBR19  [https://www.moodlebrasil.org 20th Brazil MoodleMoot], São Luís-MA, 10-11 October 2019&lt;br /&gt;
* #mootBR20  [https://www.moodlebrasil.org 20th Brazil MoodleMoot], São Paulo-SP, 23-24 April 2020&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
&lt;br /&gt;
* Lounge discussion [http://moodle.org/mod/forum/discuss.php?d=121619 A standard naming scheme for Moodle hashtags]&lt;/div&gt;</summary>
		<author><name>Anderson.blaine</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/310/en/index.php?title=New_for_mobile&amp;diff=136092</id>
		<title>New for mobile</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/310/en/index.php?title=New_for_mobile&amp;diff=136092"/>
		<updated>2019-11-27T00:09:59Z</updated>

		<summary type="html">&lt;p&gt;Anderson.blaine: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Mobile}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The Moodle app for 3.8 will be released a short time after Moodle 3.8 and will include:&lt;br /&gt;
* View H5P content even when offline&lt;br /&gt;
* MathJax support&lt;br /&gt;
* Comments&lt;br /&gt;
* Forum: Update/delete posts&lt;br /&gt;
* Calendar: events now can be filtered by type&lt;br /&gt;
* Search participants&lt;br /&gt;
* Offline working alert&lt;br /&gt;
* Minimum version required&lt;br /&gt;
* Dark mode&lt;br /&gt;
&lt;br /&gt;
[[File:MoodleAppDocs.png|center|600px|thumbnail]]&lt;br /&gt;
The new Dark mode in the Moodle app 3.8&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== See also ==&lt;br /&gt;
&lt;br /&gt;
* [[:dev:Moodle_Mobile_release_notes|Moodle Mobile release notes]] in the dev docs&lt;br /&gt;
  &lt;br /&gt;
[[Category:New features]]&lt;br /&gt;
&lt;br /&gt;
[[es:Nuevo para mobile]]&lt;br /&gt;
[[de:Moodle App - Neuigkeiten]]&lt;br /&gt;
[[fr:Fonctionnalités additionnelles de l&#039;app Moodle]]&lt;br /&gt;
[[pt-br:Novo para dispositivos móveis]]&lt;/div&gt;</summary>
		<author><name>Anderson.blaine</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/310/en/index.php?title=New_for_teachers&amp;diff=136091</id>
		<title>New for teachers</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/310/en/index.php?title=New_for_teachers&amp;diff=136091"/>
		<updated>2019-11-26T16:43:45Z</updated>

		<summary type="html">&lt;p&gt;Anderson.blaine: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{About Moodle}}	&lt;br /&gt;
If you&#039;re a teacher in Moodle, then this page will tell you about the major changes affecting you in Moodle 3.8&lt;br /&gt;
&lt;br /&gt;
__NOTOC__&lt;br /&gt;
  &amp;lt;div class=&amp;quot;row-fluid&amp;quot;&amp;gt;			&lt;br /&gt;
    &amp;lt;ul class=&amp;quot;thumbnails&amp;quot;&amp;gt;			&lt;br /&gt;
      &amp;lt;li class=&amp;quot;span6&amp;quot;&amp;gt;			&lt;br /&gt;
        &amp;lt;div class=&amp;quot;thumbnail&amp;quot;&amp;gt;			&lt;br /&gt;
[[File:DocsForumGrading1.png|600px]]			&lt;br /&gt;
          &amp;lt;div class=&amp;quot;caption&amp;quot;&amp;gt;			&lt;br /&gt;
            &amp;lt;h4&amp;gt;Forum grading &amp;lt;/h4&amp;gt;			&lt;br /&gt;
            &amp;lt;p&amp;gt;Asses forum discussions with Whole forum grading, using direct or advanced grading&amp;lt;/p&amp;gt;&lt;br /&gt;
          &amp;lt;/div&amp;gt; 			&lt;br /&gt;
        &amp;lt;/div&amp;gt;			&lt;br /&gt;
      &amp;lt;/li&amp;gt;			&lt;br /&gt;
      &amp;lt;li class=&amp;quot;span6&amp;quot;&amp;gt;			&lt;br /&gt;
        &amp;lt;div class=&amp;quot;thumbnail&amp;quot;&amp;gt;			&lt;br /&gt;
[[File:ForumSummaryReport.png|600px]]			&lt;br /&gt;
          &amp;lt;div class=&amp;quot;caption&amp;quot;&amp;gt;			&lt;br /&gt;
            &amp;lt;h4&amp;gt;Forum export and summary report&amp;lt;/h4&amp;gt;			&lt;br /&gt;
            &amp;lt;p&amp;gt;Export forum discussions and view a detailed summary report of student activity&amp;lt;/p&amp;gt;&lt;br /&gt;
          &amp;lt;/div&amp;gt;			&lt;br /&gt;
        &amp;lt;/div&amp;gt;			&lt;br /&gt;
      &amp;lt;/li&amp;gt;			&lt;br /&gt;
    &amp;lt;/ul&amp;gt;			&lt;br /&gt;
  &amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;row-fluid&amp;quot;&amp;gt;			&lt;br /&gt;
    &amp;lt;ul class=&amp;quot;thumbnails&amp;quot;&amp;gt;			&lt;br /&gt;
      &amp;lt;li class=&amp;quot;span6&amp;quot;&amp;gt;			&lt;br /&gt;
        &amp;lt;div class=&amp;quot;thumbnail&amp;quot;&amp;gt;			&lt;br /&gt;
[[File:H5PAttoButtonEn.png|600px]]			&lt;br /&gt;
          &amp;lt;div class=&amp;quot;caption&amp;quot;&amp;gt;			&lt;br /&gt;
            &amp;lt;h4&amp;gt;Embed H5P content&amp;lt;/h4&amp;gt;			&lt;br /&gt;
            &amp;lt;p&amp;gt;Link to or upload existing H5P interactive content&amp;lt;/p&amp;gt;			&lt;br /&gt;
          &amp;lt;/div&amp;gt; 			&lt;br /&gt;
        &amp;lt;/div&amp;gt;			&lt;br /&gt;
      &amp;lt;/li&amp;gt;			&lt;br /&gt;
      &amp;lt;li class=&amp;quot;span6&amp;quot;&amp;gt;			&lt;br /&gt;
        &amp;lt;div class=&amp;quot;thumbnail&amp;quot;&amp;gt;			&lt;br /&gt;
[[File:InsightsBulkActions.png|600px]]			&lt;br /&gt;
          &amp;lt;div class=&amp;quot;caption&amp;quot;&amp;gt;			&lt;br /&gt;
            &amp;lt;h4&amp;gt;Analytics bulk actions&amp;lt;/h4&amp;gt;			&lt;br /&gt;
            &amp;lt;p&amp;gt;Bulk select and send messages to students from the Insights report&amp;lt;/p&amp;gt;			&lt;br /&gt;
          &amp;lt;/div&amp;gt;			&lt;br /&gt;
        &amp;lt;/div&amp;gt;			&lt;br /&gt;
      &amp;lt;/li&amp;gt;			&lt;br /&gt;
    &amp;lt;/ul&amp;gt;			&lt;br /&gt;
  &amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;row-fluid&amp;quot;&amp;gt;			&lt;br /&gt;
    &amp;lt;ul class=&amp;quot;thumbnails&amp;quot;&amp;gt;			&lt;br /&gt;
      &amp;lt;li class=&amp;quot;span6&amp;quot;&amp;gt;			&lt;br /&gt;
        &amp;lt;div class=&amp;quot;thumbnail&amp;quot;&amp;gt;			&lt;br /&gt;
[[File:QbankIDTags.png|600px]]			&lt;br /&gt;
          &amp;lt;div class=&amp;quot;caption&amp;quot;&amp;gt;			&lt;br /&gt;
            &amp;lt;h4&amp;gt;Question bank&amp;lt;/h4&amp;gt;			&lt;br /&gt;
            &amp;lt;p&amp;gt;View question ID numbers and tags and benefit from a new Edit menu &amp;lt;/p&amp;gt;			&lt;br /&gt;
          &amp;lt;/div&amp;gt; 			&lt;br /&gt;
        &amp;lt;/div&amp;gt;			&lt;br /&gt;
      &amp;lt;/li&amp;gt;			&lt;br /&gt;
      &amp;lt;li class=&amp;quot;span6&amp;quot;&amp;gt;			&lt;br /&gt;
        &amp;lt;div class=&amp;quot;thumbnail&amp;quot;&amp;gt;			&lt;br /&gt;
[[File:GroupBadges.png|600px]]			&lt;br /&gt;
          &amp;lt;div class=&amp;quot;caption&amp;quot;&amp;gt;			&lt;br /&gt;
            &amp;lt;h4&amp;gt;Badges and groups&amp;lt;/h4&amp;gt;			&lt;br /&gt;
            &amp;lt;p&amp;gt;Filter  by group when manually awarding badges&amp;lt;/p&amp;gt;			&lt;br /&gt;
          &amp;lt;/div&amp;gt;			&lt;br /&gt;
        &amp;lt;/div&amp;gt;			&lt;br /&gt;
      &amp;lt;/li&amp;gt;			&lt;br /&gt;
    &amp;lt;/ul&amp;gt;			&lt;br /&gt;
  &amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:New features]]&lt;br /&gt;
&lt;br /&gt;
[[es:Nuevo para profesores]]&lt;br /&gt;
[[de:Neu für Trainer/innen]]&lt;br /&gt;
[[pt-br:Novo para professores]]&lt;/div&gt;</summary>
		<author><name>Anderson.blaine</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/310/en/index.php?title=New_for_administrators&amp;diff=135963</id>
		<title>New for administrators</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/310/en/index.php?title=New_for_administrators&amp;diff=135963"/>
		<updated>2019-11-19T01:16:20Z</updated>

		<summary type="html">&lt;p&gt;Anderson.blaine: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{About Moodle}}	&lt;br /&gt;
If you&#039;re a Moodle admin, this page will tell you about the major changes affecting you in Moodle 3.8.  If you&#039;d like to see full details of the release with technical information, here are the [[:dev:Moodle 3.8 release notes|Moodle 3.8 release notes]].	&lt;br /&gt;
&lt;br /&gt;
__NOTOC__&lt;br /&gt;
 			&lt;br /&gt;
    &amp;lt;div class=&amp;quot;row-fluid&amp;quot;&amp;gt;			&lt;br /&gt;
    &amp;lt;ul class=&amp;quot;thumbnails&amp;quot;&amp;gt;			&lt;br /&gt;
      &amp;lt;li class=&amp;quot;span6&amp;quot;&amp;gt;			&lt;br /&gt;
        &amp;lt;div class=&amp;quot;thumbnail&amp;quot;&amp;gt;			&lt;br /&gt;
[[File:38 newmodels.png|600px]]			&lt;br /&gt;
          &amp;lt;div class=&amp;quot;caption&amp;quot;&amp;gt;			&lt;br /&gt;
            &amp;lt;h4&amp;gt;Analytics insights&amp;lt;/h4&amp;gt;			&lt;br /&gt;
            &amp;lt;p&amp;gt;Make use of two new models [[Analytics|Learning Analytics]] relating to course access and specify courses or categories for models.&amp;lt;/p&amp;gt;			&lt;br /&gt;
          &amp;lt;/div&amp;gt; 			&lt;br /&gt;
        &amp;lt;/div&amp;gt;			&lt;br /&gt;
      &amp;lt;/li&amp;gt;			&lt;br /&gt;
      &amp;lt;li class=&amp;quot;span6&amp;quot;&amp;gt;			&lt;br /&gt;
        &amp;lt;div class=&amp;quot;thumbnail&amp;quot;&amp;gt;			&lt;br /&gt;
[[File:DocsInsightReport.png|600px]]			&lt;br /&gt;
          &amp;lt;div class=&amp;quot;caption&amp;quot;&amp;gt;			&lt;br /&gt;
            &amp;lt;h4&amp;gt;Analytics Insights report&amp;lt;/h4&amp;gt;			&lt;br /&gt;
            &amp;lt;p&amp;gt; View a graphical [[Analytics|Learning Analytics]] improvements a graphical Insights report.&amp;lt;/p&amp;gt;			&lt;br /&gt;
     &amp;lt;/div&amp;gt;			&lt;br /&gt;
        &amp;lt;/div&amp;gt;			&lt;br /&gt;
      &amp;lt;/li&amp;gt;			&lt;br /&gt;
    &amp;lt;/ul&amp;gt;			&lt;br /&gt;
  &amp;lt;/div&amp;gt;			&lt;br /&gt;
&amp;lt;div class=&amp;quot;row-fluid&amp;quot;&amp;gt;			&lt;br /&gt;
    &amp;lt;ul class=&amp;quot;thumbnails&amp;quot;&amp;gt;			&lt;br /&gt;
      &amp;lt;li class=&amp;quot;span6&amp;quot;&amp;gt;			&lt;br /&gt;
        &amp;lt;div class=&amp;quot;thumbnail&amp;quot;&amp;gt;			&lt;br /&gt;
[[File:H5Pfilter.png|600px]]			&lt;br /&gt;
          &amp;lt;div class=&amp;quot;caption&amp;quot;&amp;gt;			&lt;br /&gt;
            &amp;lt;h4&amp;gt;H5P management&amp;lt;/h4&amp;gt;			&lt;br /&gt;
            &amp;lt;p&amp;gt;Monitor and configure H5P content with a new [[Display H5P filter]] and Manage H5P content page.&amp;lt;/p&amp;gt;			&lt;br /&gt;
          &amp;lt;/div&amp;gt; 			&lt;br /&gt;
        &amp;lt;/div&amp;gt;			&lt;br /&gt;
      &amp;lt;/li&amp;gt;			&lt;br /&gt;
      &amp;lt;li class=&amp;quot;span6&amp;quot;&amp;gt;			&lt;br /&gt;
        &amp;lt;div class=&amp;quot;thumbnail&amp;quot;&amp;gt;			&lt;br /&gt;
[[File:AttoEmojiPickerStudent.png|600px]]			&lt;br /&gt;
          &amp;lt;div class=&amp;quot;caption&amp;quot;&amp;gt;			&lt;br /&gt;
            &amp;lt;h4&amp;gt; Emoji settings&amp;lt;/h4&amp;gt;			&lt;br /&gt;
            &amp;lt;p&amp;gt;Add an emoji button to the [[Atto editor]] or disable emojis from [[Advanced features]] if unsupported.&amp;lt;/p&amp;gt;			&lt;br /&gt;
          &amp;lt;/div&amp;gt;		&lt;br /&gt;
		&amp;lt;/div&amp;gt;			&lt;br /&gt;
&amp;lt;/li&amp;gt;			&lt;br /&gt;
    &amp;lt;/ul&amp;gt;			&lt;br /&gt;
  &amp;lt;/div&amp;gt;			&lt;br /&gt;
&lt;br /&gt;
		&amp;lt;div class=&amp;quot;row-fluid&amp;quot;&amp;gt;			&lt;br /&gt;
    &amp;lt;ul class=&amp;quot;thumbnails&amp;quot;&amp;gt;			&lt;br /&gt;
      &amp;lt;li class=&amp;quot;span6&amp;quot;&amp;gt;			&lt;br /&gt;
        &amp;lt;div class=&amp;quot;thumbnail&amp;quot;&amp;gt;			&lt;br /&gt;
[[File:User Management.png|600px]]			&lt;br /&gt;
          &amp;lt;div class=&amp;quot;caption&amp;quot;&amp;gt;			&lt;br /&gt;
            &amp;lt;h4&amp;gt;User management&amp;lt;/h4&amp;gt;			&lt;br /&gt;
            &amp;lt;p&amp;gt;Configure the default user filter from a new admin page.&amp;lt;/p&amp;gt;			&lt;br /&gt;
          &amp;lt;/div&amp;gt; 			&lt;br /&gt;
        &amp;lt;/div&amp;gt;			&lt;br /&gt;
      &amp;lt;/li&amp;gt;			&lt;br /&gt;
      &amp;lt;li class=&amp;quot;span6&amp;quot;&amp;gt;			&lt;br /&gt;
        &amp;lt;div class=&amp;quot;thumbnail&amp;quot;&amp;gt;			&lt;br /&gt;
[[File:38 examplecsv.png|600px]]			&lt;br /&gt;
          &amp;lt;div class=&amp;quot;caption&amp;quot;&amp;gt;			&lt;br /&gt;
            &amp;lt;h4&amp;gt;Upload users improvements&amp;lt;/h4&amp;gt;			&lt;br /&gt;
            &amp;lt;p&amp;gt;View an example csv file and specify the enrol start date.&amp;lt;/p&amp;gt;			&lt;br /&gt;
          &amp;lt;/div&amp;gt;		&lt;br /&gt;
		&amp;lt;/div&amp;gt;	&lt;br /&gt;
&amp;lt;/li&amp;gt;&lt;br /&gt;
		&lt;br /&gt;
		&amp;lt;div class=&amp;quot;row-fluid&amp;quot;&amp;gt;			&lt;br /&gt;
    &amp;lt;ul class=&amp;quot;thumbnails&amp;quot;&amp;gt;			&lt;br /&gt;
      &amp;lt;li class=&amp;quot;span6&amp;quot;&amp;gt;			&lt;br /&gt;
        &amp;lt;div class=&amp;quot;thumbnail&amp;quot;&amp;gt;			&lt;br /&gt;
[[File:CourseBackupAdmin.png|600px]]			&lt;br /&gt;
          &amp;lt;div class=&amp;quot;caption&amp;quot;&amp;gt;			&lt;br /&gt;
            &amp;lt;h4&amp;gt;Course backup&amp;lt;/h4&amp;gt;			&lt;br /&gt;
            &amp;lt;p&amp;gt;Choose to exclude course files from backup and benefit from a more logical automated backup ordering process. See [[Course backup]].&amp;lt;/p&amp;gt;			&lt;br /&gt;
          &amp;lt;/div&amp;gt; 			&lt;br /&gt;
        &amp;lt;/div&amp;gt;			&lt;br /&gt;
      &amp;lt;/li&amp;gt;			&lt;br /&gt;
      &amp;lt;li class=&amp;quot;span6&amp;quot;&amp;gt;			&lt;br /&gt;
        &amp;lt;div class=&amp;quot;thumbnail&amp;quot;&amp;gt;			&lt;br /&gt;
[[File:CourseOverviewSettings.png|600px]]			&lt;br /&gt;
          &amp;lt;div class=&amp;quot;caption&amp;quot;&amp;gt;			&lt;br /&gt;
            &amp;lt;h4&amp;gt;Course overview&amp;lt;/h4&amp;gt;			&lt;br /&gt;
            &amp;lt;p&amp;gt;Configure [[Course overview]] layouts and filters and specify default course card colours.&amp;lt;/p&amp;gt;			&lt;br /&gt;
          &amp;lt;/div&amp;gt;		&lt;br /&gt;
				&lt;br /&gt;
					&lt;br /&gt;
		&amp;lt;/div&amp;gt;			&lt;br /&gt;
&amp;lt;/li&amp;gt;			&lt;br /&gt;
    &amp;lt;/ul&amp;gt;			&lt;br /&gt;
  &amp;lt;/div&amp;gt;			&lt;br /&gt;
  &lt;br /&gt;
		&amp;lt;div class=&amp;quot;row-fluid&amp;quot;&amp;gt;			&lt;br /&gt;
    &amp;lt;ul class=&amp;quot;thumbnails&amp;quot;&amp;gt;			&lt;br /&gt;
      &amp;lt;li class=&amp;quot;span6&amp;quot;&amp;gt;			&lt;br /&gt;
        &amp;lt;div class=&amp;quot;thumbnail&amp;quot;&amp;gt;			&lt;br /&gt;
[[File:DuplicateUserTours.png|600px]]			&lt;br /&gt;
          &amp;lt;div class=&amp;quot;caption&amp;quot;&amp;gt;			&lt;br /&gt;
            &amp;lt;h4&amp;gt;Duplicate user tours&amp;lt;/h4&amp;gt;			&lt;br /&gt;
            &amp;lt;p&amp;gt;Easily copy and adapt user tours with a new &#039;duplicate&#039; button.&amp;lt;/p&amp;gt;			&lt;br /&gt;
          &amp;lt;/div&amp;gt; 			&lt;br /&gt;
        &amp;lt;/div&amp;gt;			&lt;br /&gt;
      &amp;lt;/li&amp;gt;			&lt;br /&gt;
      &amp;lt;li class=&amp;quot;span6&amp;quot;&amp;gt;			&lt;br /&gt;
        &amp;lt;div class=&amp;quot;thumbnail&amp;quot;&amp;gt;			&lt;br /&gt;
[[File:ExperimentalSettings.png|600px]]			&lt;br /&gt;
          &amp;lt;div class=&amp;quot;caption&amp;quot;&amp;gt;			&lt;br /&gt;
            &amp;lt;h4&amp;gt;Experimental relative dates&amp;lt;/h4&amp;gt;			&lt;br /&gt;
            &amp;lt;p&amp;gt;Enable and test a new Relative dates feature from [[Experimental settings]].&amp;lt;/p&amp;gt;			&lt;br /&gt;
          &amp;lt;/div&amp;gt;		&lt;br /&gt;
		&amp;lt;/div&amp;gt;			&lt;br /&gt;
&amp;lt;/li&amp;gt;			&lt;br /&gt;
    &amp;lt;/ul&amp;gt;			&lt;br /&gt;
  &amp;lt;/div&amp;gt;				&lt;br /&gt;
[[Category:New features]]&lt;br /&gt;
&lt;br /&gt;
[[es:Nuevo para administradores]]&lt;br /&gt;
[[de:Neu für Administrator/innen]]&lt;br /&gt;
[[pt-br:Novo para administradores]]&lt;/div&gt;</summary>
		<author><name>Anderson.blaine</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/310/en/index.php?title=New_for_students&amp;diff=135961</id>
		<title>New for students</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/310/en/index.php?title=New_for_students&amp;diff=135961"/>
		<updated>2019-11-19T00:19:11Z</updated>

		<summary type="html">&lt;p&gt;Anderson.blaine: Lets use full stop (.) Or is end of the line for the full stop? Anyway, let&amp;#039;s standardize on documentation and field texts in Moodle.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{About Moodle}}	&lt;br /&gt;
If you are a student on Moodle, here&#039;s a quick overview of the changes you can expect to see when your Moodle site is using Moodle 3.8:&lt;br /&gt;
__NOTOC__&lt;br /&gt;
&amp;lt;div class=&amp;quot;contentblock&amp;quot;&amp;gt;			&lt;br /&gt;
  &amp;lt;div class=&amp;quot;row-fluid&amp;quot;&amp;gt;			&lt;br /&gt;
    &amp;lt;ul class=&amp;quot;thumbnails&amp;quot;&amp;gt;			&lt;br /&gt;
      &amp;lt;li class=&amp;quot;span6&amp;quot;&amp;gt;			&lt;br /&gt;
        &amp;lt;div class=&amp;quot;thumbnail&amp;quot;&amp;gt;			&lt;br /&gt;
[[File:H5PStudentView.png|600px]]			&lt;br /&gt;
          &amp;lt;div class=&amp;quot;caption&amp;quot;&amp;gt;			&lt;br /&gt;
            &amp;lt;h4&amp;gt;H5P interactive content&amp;lt;/h4&amp;gt;			&lt;br /&gt;
            &amp;lt;p&amp;gt;Engage with interactive content in Pages, Labels, Books and more. See [[H5P]].&amp;lt;/p&amp;gt;		&lt;br /&gt;
          &amp;lt;/div&amp;gt;			&lt;br /&gt;
        &amp;lt;/div&amp;gt;			&lt;br /&gt;
      &amp;lt;/li&amp;gt;			&lt;br /&gt;
      &amp;lt;li class=&amp;quot;span6&amp;quot;&amp;gt;			&lt;br /&gt;
        &amp;lt;div class=&amp;quot;thumbnail&amp;quot;&amp;gt;			&lt;br /&gt;
[[File:StudentForumGrading.png|600px]]			&lt;br /&gt;
          &amp;lt;div class=&amp;quot;caption&amp;quot;&amp;gt;			&lt;br /&gt;
            &amp;lt;h4&amp;gt;Forum grading&amp;lt;/h4&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;Submit forum posts for assessment and view your grades.&amp;lt;/p&amp;gt;			&lt;br /&gt;
          &amp;lt;/div&amp;gt; 			&lt;br /&gt;
        &amp;lt;/div&amp;gt;			&lt;br /&gt;
      &amp;lt;/li&amp;gt;			&lt;br /&gt;
    &amp;lt;/ul&amp;gt;			&lt;br /&gt;
  &amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;contentblock&amp;quot;&amp;gt;			&lt;br /&gt;
  &amp;lt;div class=&amp;quot;row-fluid&amp;quot;&amp;gt;			&lt;br /&gt;
    &amp;lt;ul class=&amp;quot;thumbnails&amp;quot;&amp;gt;			&lt;br /&gt;
      &amp;lt;li class=&amp;quot;span6&amp;quot;&amp;gt;			&lt;br /&gt;
        &amp;lt;div class=&amp;quot;thumbnail&amp;quot;&amp;gt;			&lt;br /&gt;
[[File:courseCustomFieldFilter.png|600px]]			&lt;br /&gt;
          &amp;lt;div class=&amp;quot;caption&amp;quot;&amp;gt;			&lt;br /&gt;
            &amp;lt;h4&amp;gt;Course overview&amp;lt;/h4&amp;gt;			&lt;br /&gt;
            &amp;lt;p&amp;gt;Filter by custom course fields in the [[Course overview]].&amp;lt;/p&amp;gt;		&lt;br /&gt;
          &amp;lt;/div&amp;gt;			&lt;br /&gt;
        &amp;lt;/div&amp;gt;			&lt;br /&gt;
      &amp;lt;/li&amp;gt;			&lt;br /&gt;
      &amp;lt;li class=&amp;quot;span6&amp;quot;&amp;gt;			&lt;br /&gt;
        &amp;lt;div class=&amp;quot;thumbnail&amp;quot;&amp;gt;			&lt;br /&gt;
[[File:DocsForumExperimentalNestedView.png|600px]]			&lt;br /&gt;
          &amp;lt;div class=&amp;quot;caption&amp;quot;&amp;gt;			&lt;br /&gt;
            &amp;lt;h4&amp;gt;New forum view&amp;lt;/h4&amp;gt;			&lt;br /&gt;
            &amp;lt;p&amp;gt;Select and test a new experimental nested discussion view from the forum preferences page.&amp;lt;/p&amp;gt;			&lt;br /&gt;
        			&lt;br /&gt;
          &amp;lt;/div&amp;gt; 			&lt;br /&gt;
        &amp;lt;/div&amp;gt;			&lt;br /&gt;
      &amp;lt;/li&amp;gt;			&lt;br /&gt;
    &amp;lt;/ul&amp;gt;			&lt;br /&gt;
  &amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;contentblock&amp;quot;&amp;gt;			&lt;br /&gt;
  &amp;lt;div class=&amp;quot;row-fluid&amp;quot;&amp;gt;			&lt;br /&gt;
    &amp;lt;ul class=&amp;quot;thumbnails&amp;quot;&amp;gt;			&lt;br /&gt;
      &amp;lt;li class=&amp;quot;span6&amp;quot;&amp;gt;			&lt;br /&gt;
        &amp;lt;div class=&amp;quot;thumbnail&amp;quot;&amp;gt;			&lt;br /&gt;
[[File:CalendarFilter.png|600px]]			&lt;br /&gt;
          &amp;lt;div class=&amp;quot;caption&amp;quot;&amp;gt;			&lt;br /&gt;
            &amp;lt;h4&amp;gt;Calendar filters&amp;lt;/h4&amp;gt;			&lt;br /&gt;
            &amp;lt;p&amp;gt;Filter your calendar by month, day or upcoming event.&amp;lt;/p&amp;gt;		&lt;br /&gt;
          &amp;lt;/div&amp;gt;			&lt;br /&gt;
        &amp;lt;/div&amp;gt;			&lt;br /&gt;
      &amp;lt;/li&amp;gt;			&lt;br /&gt;
      &amp;lt;li class=&amp;quot;span6&amp;quot;&amp;gt;			&lt;br /&gt;
        &amp;lt;div class=&amp;quot;thumbnail&amp;quot;&amp;gt;			&lt;br /&gt;
[[File:MessagingEmoji.png|600px]]			&lt;br /&gt;
          &amp;lt;div class=&amp;quot;caption&amp;quot;&amp;gt;			&lt;br /&gt;
            &amp;lt;h4&amp;gt;Emojis 😍&amp;lt;/h4&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;Add emojis  into [[Messages]] or from a button in the [[Atto editor]].&amp;lt;/p&amp;gt;			&lt;br /&gt;
          &amp;lt;/div&amp;gt; 			&lt;br /&gt;
        &amp;lt;/div&amp;gt;			&lt;br /&gt;
      &amp;lt;/li&amp;gt;			&lt;br /&gt;
    &amp;lt;/ul&amp;gt;			&lt;br /&gt;
  &amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;contentblock&amp;quot;&amp;gt;			&lt;br /&gt;
  &amp;lt;div class=&amp;quot;row-fluid&amp;quot;&amp;gt;			&lt;br /&gt;
    &amp;lt;ul class=&amp;quot;thumbnails&amp;quot;&amp;gt;			&lt;br /&gt;
      &amp;lt;li class=&amp;quot;span6&amp;quot;&amp;gt;			&lt;br /&gt;
        &amp;lt;div class=&amp;quot;thumbnail&amp;quot;&amp;gt;			&lt;br /&gt;
[[File:StudentNotificationsDocs.png|600px]]			&lt;br /&gt;
          &amp;lt;div class=&amp;quot;caption&amp;quot;&amp;gt;			&lt;br /&gt;
            &amp;lt;h4&amp;gt;Clearer reminders&amp;lt;/h4&amp;gt;			&lt;br /&gt;
            &amp;lt;p&amp;gt;Receive and rate reminders about your activities.&amp;lt;/p&amp;gt;		&lt;br /&gt;
          &amp;lt;/div&amp;gt;			&lt;br /&gt;
        &amp;lt;/div&amp;gt;			&lt;br /&gt;
      &amp;lt;/li&amp;gt;			&lt;br /&gt;
      &amp;lt;li class=&amp;quot;span6&amp;quot;&amp;gt;			&lt;br /&gt;
        &amp;lt;div class=&amp;quot;thumbnail&amp;quot;&amp;gt;			&lt;br /&gt;
[[File:Timeout.png|600px]]			&lt;br /&gt;
          &amp;lt;div class=&amp;quot;caption&amp;quot;&amp;gt;			&lt;br /&gt;
            &amp;lt;h4&amp;gt;Session timeout&amp;lt;/h4&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;Stay on target with a Session timeout alert.&amp;lt;/p&amp;gt;			&lt;br /&gt;
          &amp;lt;/div&amp;gt; 			&lt;br /&gt;
        &amp;lt;/div&amp;gt;			&lt;br /&gt;
      &amp;lt;/li&amp;gt;			&lt;br /&gt;
    &amp;lt;/ul&amp;gt;			&lt;br /&gt;
  &amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:New features]]&lt;br /&gt;
&lt;br /&gt;
[[es:Nuevo para estudiantes]]&lt;br /&gt;
[[de:Neu für Teilnehmer/innen]]&lt;br /&gt;
[[pt-br:Novo para estudantes]]&lt;/div&gt;</summary>
		<author><name>Anderson.blaine</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/310/en/index.php?title=Standard_Moodle_tags&amp;diff=135513</id>
		<title>Standard Moodle tags</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/310/en/index.php?title=Standard_Moodle_tags&amp;diff=135513"/>
		<updated>2019-09-20T17:27:46Z</updated>

		<summary type="html">&lt;p&gt;Anderson.blaine: /* Tags in use */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Tags are useful for connecting different bits of information together.&lt;br /&gt;
&lt;br /&gt;
Obviously it&#039;s important to use the same tags everywhere.&lt;br /&gt;
&lt;br /&gt;
This page describes standard Moodle tags that you should use when describing Moodle events on the internet (Flickr, Twitter, Facebook, del.icio.us etc)&lt;br /&gt;
&lt;br /&gt;
==General Moodle stuff==&lt;br /&gt;
&lt;br /&gt;
For general discussion of Moodle, use the tag &amp;quot;moodle&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
Twitter example:&lt;br /&gt;
 I just installed #moodle on a computer I bought ten years ago!&lt;br /&gt;
&lt;br /&gt;
==Moodle Moots==&lt;br /&gt;
&lt;br /&gt;
For Moodle conferences (Moots) use mootCCYY where:&lt;br /&gt;
* CC is a country ISO code or state abbreviation, and&lt;br /&gt;
* YY is a year.&lt;br /&gt;
&lt;br /&gt;
 mootAU09&lt;br /&gt;
&lt;br /&gt;
Capitalisation doesn&#039;t matter and just helps readability.&lt;br /&gt;
&lt;br /&gt;
The two letter code would usually be a country, but for somewhere like the US where there are different moots they might choose to use &amp;quot;us&amp;quot; or a state like &amp;quot;sf&amp;quot; or &amp;quot;ok&amp;quot;. It really doesn&#039;t matter if two moots both used mootus09 for example, because they would be separated in time.&lt;br /&gt;
&lt;br /&gt;
==Tags in use==&lt;br /&gt;
&lt;br /&gt;
* #mooteu09 MoodleMoot Euskadi&lt;br /&gt;
* #mootNL09 Amsterdam Moodlemoot&lt;br /&gt;
* #mootUS09ok Moodlemoot Oklahoma  (or #mootok09)&lt;br /&gt;
* #mootUS09SF Moodlemoot San Francisco  (or #mootsf09)&lt;br /&gt;
* #mootin09 Goshen Midwest MoodleMoot&lt;br /&gt;
* #mootus09ny MoodleMoot Delhi (or #mootny09) &lt;br /&gt;
* #mootar09 MoodleMoot Argentina&lt;br /&gt;
* #mootat09 MoodleMoot Austria &lt;br /&gt;
* #mootDE09 MoodleMoot Germany 2009&lt;br /&gt;
* #mootco09 MoodleMoot Colombia&lt;br /&gt;
* #mootcl09 MoodleMoot Chile&lt;br /&gt;
* #mootes09 MoodleMoot Spain 2009&lt;br /&gt;
* #moodle #OE09 Moodle at Online Educa 2009 in Berlin (December)&lt;br /&gt;
* #moodledev09 [[Development:Czech Hackfest 2009|Czech Hackfest 2009]]&lt;br /&gt;
* #imoot and #imoot2010 iMoot 2010&lt;br /&gt;
* #mootJP10hk Moodlemoot Japan in Hakodate, February 2010&lt;br /&gt;
* #mootDE10b Moodlemoot Germany 2010 in Berlin March&lt;br /&gt;
* #mootDE10e [http://moodle2010.de/ Moodlemoot Germany 2010 in Essen] 16-17 September 2010&lt;br /&gt;
* #mootNZ10 Moodle Moot New Zealand (Christchurch) April 2010&lt;br /&gt;
* #mootUK10 MoodleMoot UK April 2010&lt;br /&gt;
* #mootsi10 Slovenian MoodleMoot&lt;br /&gt;
* #mootok10 MoodleMoot Oklahoma&lt;br /&gt;
* #mootau10 MoodleMoot AU 2010&lt;br /&gt;
* #mootcz10 [http://www.moodlemoot.cz/ MoodleMoot Czech Republic, Brno] 10-11 June 2010&lt;br /&gt;
* #mootfr10 6th French MoodleMoot&lt;br /&gt;
* #mootIT10 MoodleMoot Italia 2010&lt;br /&gt;
* #mootnl10 MoodleMoot NL 2010&lt;br /&gt;
* #mootPL10 Second Polish MoodleMoot, 4-5 November 2010, Czestochowa, Poland, http://moodlemoot.pl&lt;br /&gt;
* #mootusin10 Goshen, Indiana, USA 26-28 July, 2010&lt;br /&gt;
* #mootustx10 Austin, Texas, USA 2-3 August, 2010&lt;br /&gt;
* #mootfr11 [http://moodlemoot2011.uvt.rnu.tn/ 7th French MoodleMoot], Hammamet, Tunisia, 27-29 June 2011&lt;br /&gt;
* #mootde12 [http://moodlemoot.de/ German Moodlemoot], Münster, Germany, 13-16 March 2012&lt;br /&gt;
* #mootfr12 [http://moodlemoot2012.unimes.fr/ 8th French MoodleMoot], Nîmes, France, 20-22 June 2012&lt;br /&gt;
* #mootde13 [http://moodlemoot.de/ German Moodlemoot], München, Germany, 28 Feb - 1 Mar 2013&lt;br /&gt;
* #mootfr13 [http://moodlemoot2013.univ-bordeaux.fr/ 9th French MoodleMoot], Bordeaux, France, 5-7 June 2013&lt;br /&gt;
* #smootau13 [http://http://school.moodlemoot.com.au/ 2nd Australian Schoolmoot], Sydney, Australia, 2-4 October 2013&lt;br /&gt;
* #mootfr14 [http://moodlemoot2014.univ-paris3.fr 10th French MoodleMoot], Paris, 4-6 June 2014&lt;br /&gt;
* #mootfr15 [https://moodlemoot2015.univ-tours.fr 11th French MoodleMoot], Tours, 10-12 June 2015&lt;br /&gt;
* #mootfr16 [http://2016.moodlemoot.fr 12th French MoodleMoot], Sierre, Switzerland, 6-8 July 2016&lt;br /&gt;
* #mootfr17 [http://2017.moodlemoot.fr 13th French MoodleMoot], Lyon, 28-30 June 2017&lt;br /&gt;
* #mootfr18 [https://2018.moodlemoot.fr 14th French MoodleMoot], Bruxelles, 4-6 July 2018&lt;br /&gt;
* #mootfr19 [https://2019.moodlemoot.fr 15th French MoodleMoot], Rennes, 3-5 July 2019&lt;br /&gt;
* #mootBR19  [https://www.moodlebrasil.org 19th Brazil MoodleMoot], São Paulo, 25-26 April 2019&lt;br /&gt;
* #mootBR20  [https://www.moodlebrasil.org 20th Brazil MoodleMoot], São Luís-MA, 10-11 October 2019&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
&lt;br /&gt;
* Lounge discussion [http://moodle.org/mod/forum/discuss.php?d=121619 A standard naming scheme for Moodle hashtags]&lt;/div&gt;</summary>
		<author><name>Anderson.blaine</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/310/en/index.php?title=Standard_Moodle_tags&amp;diff=132954</id>
		<title>Standard Moodle tags</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/310/en/index.php?title=Standard_Moodle_tags&amp;diff=132954"/>
		<updated>2019-01-11T16:04:01Z</updated>

		<summary type="html">&lt;p&gt;Anderson.blaine: /* Tags in use */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Tags are useful for connecting different bits of information together.&lt;br /&gt;
&lt;br /&gt;
Obviously it&#039;s important to use the same tags everywhere.&lt;br /&gt;
&lt;br /&gt;
This page describes standard Moodle tags that you should use when describing Moodle events on the internet (Flickr, Twitter, Facebook, del.icio.us etc)&lt;br /&gt;
&lt;br /&gt;
==General Moodle stuff==&lt;br /&gt;
&lt;br /&gt;
For general discussion of Moodle, use the tag &amp;quot;moodle&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
Twitter example:&lt;br /&gt;
 I just installed #moodle on a computer I bought ten years ago!&lt;br /&gt;
&lt;br /&gt;
==Moodle Moots==&lt;br /&gt;
&lt;br /&gt;
For Moodle conferences (Moots) use mootCCYY where:&lt;br /&gt;
* CC is a country ISO code or state abbreviation, and&lt;br /&gt;
* YY is a year.&lt;br /&gt;
&lt;br /&gt;
 mootAU09&lt;br /&gt;
&lt;br /&gt;
Capitalisation doesn&#039;t matter and just helps readability.&lt;br /&gt;
&lt;br /&gt;
The two letter code would usually be a country, but for somewhere like the US where there are different moots they might choose to use &amp;quot;us&amp;quot; or a state like &amp;quot;sf&amp;quot; or &amp;quot;ok&amp;quot;. It really doesn&#039;t matter if two moots both used mootus09 for example, because they would be separated in time.&lt;br /&gt;
&lt;br /&gt;
==Tags in use==&lt;br /&gt;
&lt;br /&gt;
* #mooteu09 MoodleMoot Euskadi&lt;br /&gt;
* #mootNL09 Amsterdam Moodlemoot&lt;br /&gt;
* #mootUS09ok Moodlemoot Oklahoma  (or #mootok09)&lt;br /&gt;
* #mootUS09SF Moodlemoot San Francisco  (or #mootsf09)&lt;br /&gt;
* #mootin09 Goshen Midwest MoodleMoot&lt;br /&gt;
* #mootus09ny MoodleMoot Delhi (or #mootny09) &lt;br /&gt;
* #mootar09 MoodleMoot Argentina&lt;br /&gt;
* #mootat09 MoodleMoot Austria &lt;br /&gt;
* #mootDE09 MoodleMoot Germany 2009&lt;br /&gt;
* #mootco09 MoodleMoot Colombia&lt;br /&gt;
* #mootcl09 MoodleMoot Chile&lt;br /&gt;
* #mootes09 MoodleMoot Spain 2009&lt;br /&gt;
* #moodle #OE09 Moodle at Online Educa 2009 in Berlin (December)&lt;br /&gt;
* #moodledev09 [[Development:Czech Hackfest 2009|Czech Hackfest 2009]]&lt;br /&gt;
* #imoot and #imoot2010 iMoot 2010&lt;br /&gt;
* #mootJP10hk Moodlemoot Japan in Hakodate, February 2010&lt;br /&gt;
* #mootDE10b Moodlemoot Germany 2010 in Berlin March&lt;br /&gt;
* #mootDE10e [http://moodle2010.de/ Moodlemoot Germany 2010 in Essen] 16-17 September 2010&lt;br /&gt;
* #mootNZ10 Moodle Moot New Zealand (Christchurch) April 2010&lt;br /&gt;
* #mootUK10 MoodleMoot UK April 2010&lt;br /&gt;
* #mootsi10 Slovenian MoodleMoot&lt;br /&gt;
* #mootok10 MoodleMoot Oklahoma&lt;br /&gt;
* #mootau10 MoodleMoot AU 2010&lt;br /&gt;
* #mootcz10 [http://www.moodlemoot.cz/ MoodleMoot Czech Republic, Brno] 10-11 June 2010&lt;br /&gt;
* #mootfr10 6th French MoodleMoot&lt;br /&gt;
* #mootIT10 MoodleMoot Italia 2010&lt;br /&gt;
* #mootnl10 MoodleMoot NL 2010&lt;br /&gt;
* #mootPL10 Second Polish MoodleMoot, 4-5 November 2010, Czestochowa, Poland, http://moodlemoot.pl&lt;br /&gt;
* #mootusin10 Goshen, Indiana, USA 26-28 July, 2010&lt;br /&gt;
* #mootustx10 Austin, Texas, USA 2-3 August, 2010&lt;br /&gt;
* #mootfr11 [http://moodlemoot2011.uvt.rnu.tn/ 7th French MoodleMoot], Hammamet, Tunisia, 27-29 June 2011&lt;br /&gt;
* #mootde12 [http://moodlemoot.de/ German Moodlemoot], Münster, Germany, 13-16 March 2012&lt;br /&gt;
* #mootfr12 [http://moodlemoot2012.unimes.fr/ 8th French MoodleMoot], Nîmes, France, 20-22 June 2012&lt;br /&gt;
* #mootde13 [http://moodlemoot.de/ German Moodlemoot], München, Germany, 28 Feb - 1 Mar 2013&lt;br /&gt;
* #mootfr13 [http://moodlemoot2013.univ-bordeaux.fr/ 9th French MoodleMoot], Bordeaux, France, 5-7 June 2013&lt;br /&gt;
* #smootau13 [http://http://school.moodlemoot.com.au/ 2nd Australian Schoolmoot], Sydney, Australia, 2-4 October 2013&lt;br /&gt;
* #mootfr14 [http://moodlemoot2014.univ-paris3.fr 10th French MoodleMoot], Paris, 4-6 June 2014&lt;br /&gt;
* #mootfr15 [https://moodlemoot2015.univ-tours.fr 11th French MoodleMoot], Tours, 10-12 June 2015&lt;br /&gt;
* #mootfr16 [http://2016.moodlemoot.fr 12th French MoodleMoot], Sierre, Switzerland, 6-8 July 2016&lt;br /&gt;
* #mootfr17 [http://2017.moodlemoot.fr 13th French MoodleMoot], Lyon, 28-30 June 2017&lt;br /&gt;
* #mootfr18 [https://2018.moodlemoot.fr 14th French MoodleMoot], Bruxelles, 4-6 July 2018&lt;br /&gt;
* #mootBR19  [https://www.moodlebrasil.org 19th Brazil MoodleMoot], São Paulo, 25-26 April 2019&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
&lt;br /&gt;
* Lounge discussion [http://moodle.org/mod/forum/discuss.php?d=121619 A standard naming scheme for Moodle hashtags]&lt;/div&gt;</summary>
		<author><name>Anderson.blaine</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/310/en/index.php?title=Standard_Moodle_tags&amp;diff=132953</id>
		<title>Standard Moodle tags</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/310/en/index.php?title=Standard_Moodle_tags&amp;diff=132953"/>
		<updated>2019-01-11T16:03:30Z</updated>

		<summary type="html">&lt;p&gt;Anderson.blaine: /* Tags in use */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Tags are useful for connecting different bits of information together.&lt;br /&gt;
&lt;br /&gt;
Obviously it&#039;s important to use the same tags everywhere.&lt;br /&gt;
&lt;br /&gt;
This page describes standard Moodle tags that you should use when describing Moodle events on the internet (Flickr, Twitter, Facebook, del.icio.us etc)&lt;br /&gt;
&lt;br /&gt;
==General Moodle stuff==&lt;br /&gt;
&lt;br /&gt;
For general discussion of Moodle, use the tag &amp;quot;moodle&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
Twitter example:&lt;br /&gt;
 I just installed #moodle on a computer I bought ten years ago!&lt;br /&gt;
&lt;br /&gt;
==Moodle Moots==&lt;br /&gt;
&lt;br /&gt;
For Moodle conferences (Moots) use mootCCYY where:&lt;br /&gt;
* CC is a country ISO code or state abbreviation, and&lt;br /&gt;
* YY is a year.&lt;br /&gt;
&lt;br /&gt;
 mootAU09&lt;br /&gt;
&lt;br /&gt;
Capitalisation doesn&#039;t matter and just helps readability.&lt;br /&gt;
&lt;br /&gt;
The two letter code would usually be a country, but for somewhere like the US where there are different moots they might choose to use &amp;quot;us&amp;quot; or a state like &amp;quot;sf&amp;quot; or &amp;quot;ok&amp;quot;. It really doesn&#039;t matter if two moots both used mootus09 for example, because they would be separated in time.&lt;br /&gt;
&lt;br /&gt;
==Tags in use==&lt;br /&gt;
&lt;br /&gt;
* #mooteu09 MoodleMoot Euskadi&lt;br /&gt;
* #mootNL09 Amsterdam Moodlemoot&lt;br /&gt;
* #mootUS09ok Moodlemoot Oklahoma  (or #mootok09)&lt;br /&gt;
* #mootUS09SF Moodlemoot San Francisco  (or #mootsf09)&lt;br /&gt;
* #mootin09 Goshen Midwest MoodleMoot&lt;br /&gt;
* #mootus09ny MoodleMoot Delhi (or #mootny09) &lt;br /&gt;
* #mootar09 MoodleMoot Argentina&lt;br /&gt;
* #mootat09 MoodleMoot Austria &lt;br /&gt;
* #mootDE09 MoodleMoot Germany 2009&lt;br /&gt;
* #mootco09 MoodleMoot Colombia&lt;br /&gt;
* #mootcl09 MoodleMoot Chile&lt;br /&gt;
* #mootes09 MoodleMoot Spain 2009&lt;br /&gt;
* #moodle #OE09 Moodle at Online Educa 2009 in Berlin (December)&lt;br /&gt;
* #moodledev09 [[Development:Czech Hackfest 2009|Czech Hackfest 2009]]&lt;br /&gt;
* #imoot and #imoot2010 iMoot 2010&lt;br /&gt;
* #mootJP10hk Moodlemoot Japan in Hakodate, February 2010&lt;br /&gt;
* #mootDE10b Moodlemoot Germany 2010 in Berlin March&lt;br /&gt;
* #mootDE10e [http://moodle2010.de/ Moodlemoot Germany 2010 in Essen] 16-17 September 2010&lt;br /&gt;
* #mootNZ10 Moodle Moot New Zealand (Christchurch) April 2010&lt;br /&gt;
* #mootUK10 MoodleMoot UK April 2010&lt;br /&gt;
* #mootsi10 Slovenian MoodleMoot&lt;br /&gt;
* #mootok10 MoodleMoot Oklahoma&lt;br /&gt;
* #mootau10 MoodleMoot AU 2010&lt;br /&gt;
* #mootcz10 [http://www.moodlemoot.cz/ MoodleMoot Czech Republic, Brno] 10-11 June 2010&lt;br /&gt;
* #mootfr10 6th French MoodleMoot&lt;br /&gt;
* #mootIT10 MoodleMoot Italia 2010&lt;br /&gt;
* #mootnl10 MoodleMoot NL 2010&lt;br /&gt;
* #mootPL10 Second Polish MoodleMoot, 4-5 November 2010, Czestochowa, Poland, http://moodlemoot.pl&lt;br /&gt;
* #mootusin10 Goshen, Indiana, USA 26-28 July, 2010&lt;br /&gt;
* #mootustx10 Austin, Texas, USA 2-3 August, 2010&lt;br /&gt;
* #mootfr11 [http://moodlemoot2011.uvt.rnu.tn/ 7th French MoodleMoot], Hammamet, Tunisia, 27-29 June 2011&lt;br /&gt;
* #mootde12 [http://moodlemoot.de/ German Moodlemoot], Münster, Germany, 13-16 March 2012&lt;br /&gt;
* #mootfr12 [http://moodlemoot2012.unimes.fr/ 8th French MoodleMoot], Nîmes, France, 20-22 June 2012&lt;br /&gt;
* #mootde13 [http://moodlemoot.de/ German Moodlemoot], München, Germany, 28 Feb - 1 Mar 2013&lt;br /&gt;
* #mootfr13 [http://moodlemoot2013.univ-bordeaux.fr/ 9th French MoodleMoot], Bordeaux, France, 5-7 June 2013&lt;br /&gt;
* #smootau13 [http://http://school.moodlemoot.com.au/ 2nd Australian Schoolmoot], Sydney, Australia, 2-4 October 2013&lt;br /&gt;
* #mootfr14 [http://moodlemoot2014.univ-paris3.fr 10th French MoodleMoot], Paris, 4-6 June 2014&lt;br /&gt;
* #mootfr15 [https://moodlemoot2015.univ-tours.fr 11th French MoodleMoot], Tours, 10-12 June 2015&lt;br /&gt;
* #mootfr16 [http://2016.moodlemoot.fr 12th French MoodleMoot], Sierre, Switzerland, 6-8 July 2016&lt;br /&gt;
* #mootfr17 [http://2017.moodlemoot.fr 13th French MoodleMoot], Lyon, 28-30 June 2017&lt;br /&gt;
* #mootfr18 [https://2018.moodlemoot.fr 14th French MoodleMoot], Bruxelles, 4-6 July 2018&lt;br /&gt;
* #mootBR  [https://www.moodlebrasil.org 19th Brazil MoodleMoot], São Paulo, 25-26 April 2019&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
&lt;br /&gt;
* Lounge discussion [http://moodle.org/mod/forum/discuss.php?d=121619 A standard naming scheme for Moodle hashtags]&lt;/div&gt;</summary>
		<author><name>Anderson.blaine</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/310/en/index.php?title=Upgrading&amp;diff=132922</id>
		<title>Upgrading</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/310/en/index.php?title=Upgrading&amp;diff=132922"/>
		<updated>2019-01-04T14:16:19Z</updated>

		<summary type="html">&lt;p&gt;Anderson.blaine: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Installing Moodle}}	&lt;br /&gt;
&#039;&#039;This page explains in detail how to upgrade Moodle. For a summary of the process, see [[Upgrade overview]].&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
==Check the requirements==&lt;br /&gt;
&lt;br /&gt;
Before upgrading, check that your server meets all requirements for {{Version}} in &#039;&#039;Site administration &amp;gt; Server &amp;gt; [[Environment]]&#039;&#039;. &lt;br /&gt;
&lt;br /&gt;
See the [{{Release notes}} release notes] in the dev docs for both [{{Release notes}}#Server_requirements server] and [{{Release notes}}#Client_requirements client] software requirements.&lt;br /&gt;
&lt;br /&gt;
Notes:&lt;br /&gt;
&lt;br /&gt;
* You can only upgrade to Moodle {{Version}} from Moodle 3.1 or later. If upgrading from earlier versions, you must [https://docs.moodle.org/31/en/Upgrading_to_Moodle_3.1 upgrade to 3.1] as a first step.&lt;br /&gt;
&lt;br /&gt;
==Before upgrading==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;We advise that you test the upgrade first on a COPY of your production site, to make sure it works as you expect.&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Consider setting the [[Upgrade key|upgrade key]] for your site.&lt;br /&gt;
&lt;br /&gt;
== Backup important data ==&lt;br /&gt;
&lt;br /&gt;
There are three areas that should be backed up before any upgrade:&lt;br /&gt;
#Moodle software (For example, everything in server/htdocs/moodle)&lt;br /&gt;
#Moodle uploaded files (For example, server/moodledata)&lt;br /&gt;
#Moodle database (For example, your Postgres or MySQL database dump)&lt;br /&gt;
&lt;br /&gt;
See [[Site backup]] for more specific information.&lt;br /&gt;
&lt;br /&gt;
== Check for plugin updates ==&lt;br /&gt;
&lt;br /&gt;
If you have [[Automatic updates deployment]] enabled, you will be able to update installed plugins automatically during the upgrade. Just make sure you check for available updates (via the button for it) at the Plugins check screen.&lt;br /&gt;
&lt;br /&gt;
If you are updating plugins manually, it is a good moment now to check in the [http://moodle.org/plugins Moodle Plugins directory] whether there is a {{Version}} version available for any plugins (including themes) that you have previously installed on your site. If so, download the plugin package. In the next step, you will copy it to the appropriate location in your Moodle code (see [[Installing plugins]]).&lt;br /&gt;
&lt;br /&gt;
The upgrade of the plugin will then happen as part of the Moodle upgrade process.&lt;br /&gt;
&lt;br /&gt;
If an out-of-date plugin causes your upgrade to fail, you can usually delete the plugin code rather than uninstalling it from within Moodle so that the data associated with it is not deleted.&lt;br /&gt;
&lt;br /&gt;
==Put your site into maintenance mode==&lt;br /&gt;
Before you begin upgrading your site, you should put it into [[Maintenance_mode | maintenance mode]] to stop any non-admin users from logging in. Then you should wait for any currently running cron processes to complete before proceeding.&lt;br /&gt;
&lt;br /&gt;
== Install the new Moodle software ==&lt;br /&gt;
You can fetch the current version of the software through &lt;br /&gt;
&lt;br /&gt;
wget http://sourceforge.net/projects/moodle/files/Moodle/stable{{Version2}}/moodle-latest-{{Version2}}.tgz&lt;br /&gt;
&lt;br /&gt;
=== Standard install package ===&lt;br /&gt;
&lt;br /&gt;
# Move your old Moodle software program files to another location. &#039;&#039;Do NOT copy new files over the old files.&#039;&#039;&lt;br /&gt;
# 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.&lt;br /&gt;
# Copy your old [[Configuration file|config.php file]] back to the new Moodle directory. &lt;br /&gt;
# As mentioned above, if you had installed any plugins on your site you should add them to the new code tree (Moodle directory structure) 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 and that you place the plugin folders in the correct directory (the same directory that they are in in the current installation.)&lt;br /&gt;
# Your moodledata folder should be located separately to your Moodle code folder and, as such, should not need anything done to it.  Moodle 3.0 will throw a warning if it is located in a web accessible folder and the moodledata should never be located in the Moodle code folder.  If you are moving your installation to a new server or new location on your server, then you will need to follow the [[Migration]] documents.&lt;br /&gt;
&lt;br /&gt;
====Linux====&lt;br /&gt;
 mv moodle moodle.backup&lt;br /&gt;
 tar xvzf moodle-latest-{{Version}}.tgz&lt;br /&gt;
&lt;br /&gt;
Next, copy across your config.php, any custom plugins, and your .htaccess file if you created one (&#039;&#039;&#039;check that custom plugins are the correct version for your new Moodle first&#039;&#039;&#039;):&lt;br /&gt;
&lt;br /&gt;
 cp moodle.backup/config.php moodle&lt;br /&gt;
 cp -pr moodle.backup/theme/mytheme moodle/theme/mytheme&lt;br /&gt;
 cp -pr moodle.backup/mod/mymod moodle/mod/mymod&lt;br /&gt;
&lt;br /&gt;
Don&#039;t forget to make moodle/config.php (and the rest of the source code) readable by your www server. For maximum security the files should not be writeable by your server. This is especially important on a &#039;production&#039; server open to the public internet. &lt;br /&gt;
&lt;br /&gt;
 chown -R root:root moodle (Linux debian - or even create a user especially for moodle. &#039;&#039;&#039;Don&#039;t&#039;&#039;&#039; use the web server user, e.g. www-data)&lt;br /&gt;
 chmod -R 755 moodle&lt;br /&gt;
&lt;br /&gt;
If you use cron, take care that cron.php is executeable and uses the correct php command: &lt;br /&gt;
 chmod 740 admin/cli/cron.php (some configurations need chmod 750 or chmod 755)&lt;br /&gt;
 copy the first line from cron.php (if it looks like &#039;#!/usr/local/bin/php&#039; or &#039;#!/usr/local/bin/php5.3&#039;, no need to copy &#039;&amp;lt;?php&#039;) &lt;br /&gt;
if necessary.  However, for a simple upgrade, there should be no need to change anything with cron.&lt;br /&gt;
&lt;br /&gt;
=== Using Git ===&lt;br /&gt;
&lt;br /&gt;
You can use Git for updating or upgrading your Moodle. See [[Git for Administrators]] for details.&lt;br /&gt;
&lt;br /&gt;
===Command line upgrade===&lt;br /&gt;
&lt;br /&gt;
On Linux servers, Moodle {{Version}} 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.&lt;br /&gt;
&lt;br /&gt;
== Finishing the upgrade ==&lt;br /&gt;
&lt;br /&gt;
The last step is to trigger the upgrade processes within Moodle. &lt;br /&gt;
&lt;br /&gt;
If you put your site into Maintenance mode earlier; take it out now!&lt;br /&gt;
&lt;br /&gt;
To do this just go to &#039;&#039;Administration &amp;gt; Site administration &amp;gt; Notifications&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
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&#039;t do itself (very rare) then you will see messages telling you what you need to do.&lt;br /&gt;
&lt;br /&gt;
Assuming all goes well (no error messages) then you can start using your new version of Moodle and enjoy the new features!&lt;br /&gt;
&lt;br /&gt;
Note: If you are running multiple servers then you should purge all caches manually (via &#039;&#039;Administration &amp;gt; Site administration &amp;gt; Development &amp;gt; Purge all caches&#039;&#039;) after completing the upgrade on all servers.&lt;br /&gt;
&lt;br /&gt;
===Fatal error: Maximum execution time of 30 seconds exceeded...===&lt;br /&gt;
&lt;br /&gt;
If your server uses a main language other than English, you may encounter a &#039;Fatal error: Maximum execution time of 30 seconds exceeded&#039; 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.&lt;br /&gt;
&lt;br /&gt;
==After upgrading==&lt;br /&gt;
&lt;br /&gt;
The config.php file from your installation should work fine but if you take a look at config-dist.php that came with Moodle 3.0 there are more/different options available (e.g. database drivers and settings). It&#039;s a good idea to map your old config.php settings to a new one based on the 3.0 config-dist.php.&lt;br /&gt;
&lt;br /&gt;
===Cron===&lt;br /&gt;
&lt;br /&gt;
Cron has received a major update (MDL-25499) and now has support for both scheduled and ad hoc tasks.&lt;br /&gt;
&lt;br /&gt;
The benefits of these changes are:&lt;br /&gt;
* The schedule for every task can be configured by the admin&lt;br /&gt;
* Tasks can run in parallel&lt;br /&gt;
* Cron processes use locking to prevent the same task running at the same time by different processes&lt;br /&gt;
* Clusters with multiple identical application nodes are supported, you can run cron on all of them&lt;br /&gt;
&lt;br /&gt;
A result of this is that cron can be run much more often, which means (for example) forum posts can be sent out sooner.  To take advantage of the new cron system it is now strongly recommended that administrators increase the frequency that cron is run to at least &#039;&#039;once per minute&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
You also may need to modify any automated scripts you have that are parsing the output from cron. It is no longer possible to simply monitor the output of cron for the string &amp;quot;Cron script completed correctly&amp;quot; (if that is what you were doing). An alternative is to monitor the output for the string &amp;quot;task failed:&amp;quot;. If you detect that a task is failing, [[Cron#Debugging_Scheduled_Tasks|here]] are some tips for debugging the failure. &lt;br /&gt;
&lt;br /&gt;
Before the upgrade, there may have been a cron task that was failing, which was preventing the rest of cron from being executed. A failure in any single task will no longer prevent the rest of the Moodle cron tasks from executing, so you may uncover previously masked bugs. It is a good idea to closely monitor the output from cron after the upgrade.&lt;br /&gt;
&lt;br /&gt;
===Assignments===&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
If you are still using the old assignment (2.2) module, after upgrading to Moodle 3.0 all assignment (2.2) activities will be hidden. You need to run the [[Assignment upgrade tool]] to un-hide the activities.&lt;br /&gt;
&lt;br /&gt;
If you really, really need to keep using the old assignment (2.2) module, you should update the code to Moodle 3.0, and then replace the &amp;quot;mod/assignment&amp;quot; folder with the one from https://github.com/moodlehq/moodle-mod_assignment/releases before completing the upgrade.&lt;br /&gt;
&lt;br /&gt;
==Possible issues that may affect you in Moodle {{Version}}==&lt;br /&gt;
&lt;br /&gt;
===Messaging===&lt;br /&gt;
&lt;br /&gt;
* New setting &#039;Allow site-wide messaging&#039; in Site administration / Advanced features. The setting is disabled by default (for new installs) but enabled for upgraded sites if &#039;&#039;$CFG-&amp;gt;keepmessagingallusersenabled = true;&#039;&#039; is defined in config.php.&lt;br /&gt;
* Adding another user as a messaging contact now requires approval from the other user. Any contacts that you have that aren&#039;t mutual (ie. both users have added each other as a contact) will be removed from your list of contacts.&lt;br /&gt;
&lt;br /&gt;
===Custom theme changes===&lt;br /&gt;
&lt;br /&gt;
* For sites using a custom theme you will need to add a renderer callback to &amp;quot;standard_after_main_region_html&amp;quot; see [[:dev:Upgrading themes to Moodle 3.6|Upgrading themes to Moodle 3.6]].&lt;br /&gt;
* Sites using a custom theme or login form must include a new login token field in the login form. See the dev docs [[:dev:Login token|Login token]] for details.&lt;br /&gt;
&lt;br /&gt;
===Other===&lt;br /&gt;
&lt;br /&gt;
* To use &#039;Run now&#039; links in [[Scheduled tasks]], you will need to set &#039;Path to PHP CLI&#039; (pathtophp) in Site administration / Server / System paths.&lt;br /&gt;
* The timeline tab in the course overview block is now in a separate block [[Timeline block|Timeline]]. There are also more new Dashboard blocks - [[Recently accessed courses block|Recently accessed courses]], [[Recently accessed items block|Recently accessed items]] and [[Starred courses block|Starred courses]].&lt;br /&gt;
* Two new [[User tours]] covering the new Dashboard blocks and the new messaging interface are enabled by default.&lt;br /&gt;
*The [[Assignment upgrade tool]], for upgrading old assignments from 2.2 or earlier, has been removed from core. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
See also the list of [https://tracker.moodle.org/issues/?jql=project%20%3D%20mdl%20AND%20resolution%20%3D%20fixed%20AND%20fixVersion%20in%20(%223.6%22)%20AND%20labels%20%3D%20upgrade_notes upgrade_notes-labelled issues] and [https://tracker.moodle.org/issues/?jql=project%20%3D%20mdl%20AND%20resolution%20%3D%20fixed%20AND%20fixVersion%20in%20(%223.6%22)%20AND%20labels%20%3D%20ui_change%20 ui_change-labelled issues]. &lt;br /&gt;
&lt;br /&gt;
=== Moodle 3.1, 3.2, 3.3, 3.4 and 3.5 improvements ===&lt;br /&gt;
&lt;br /&gt;
Depending on which version you are upgrading from, please see the section &#039;Possible issues that may affect you&#039; in the documentation&lt;br /&gt;
&lt;br /&gt;
* [https://docs.moodle.org/31/en/Upgrading Upgrading to Moodle 3.1]&lt;br /&gt;
* [https://docs.moodle.org/32/en/Upgrading Upgrading to Moodle 3.2]&lt;br /&gt;
* [https://docs.moodle.org/33/en/Upgrading Upgrading to Moodle 3.3]&lt;br /&gt;
* [https://docs.moodle.org/34/en/Upgrading Upgrading to Moodle 3.4]&lt;br /&gt;
* [https://docs.moodle.org/35/en/Upgrading Upgrading to Moodle 3.5]&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
&lt;br /&gt;
* [[Installation]]&lt;br /&gt;
* Using Moodle [http://moodle.org/mod/forum/view.php?id=28 Installation help forum] &lt;br /&gt;
* [[dev:Moodle {{Version}} release notes|Moodle {{Version}} release notes]]&lt;br /&gt;
&lt;br /&gt;
[[es:Actualización de moodle]]&lt;br /&gt;
[[fr:Mise à jour]]&lt;br /&gt;
[[ja:Moodleをアップグレードする]]&lt;br /&gt;
[[de:Aktualisierung von Moodle]]&lt;/div&gt;</summary>
		<author><name>Anderson.blaine</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/310/en/index.php?title=Tracking_progress&amp;diff=129663</id>
		<title>Tracking progress</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/310/en/index.php?title=Tracking_progress&amp;diff=129663"/>
		<updated>2017-12-12T18:33:36Z</updated>

		<summary type="html">&lt;p&gt;Anderson.blaine: /* Course reports */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Managing a Moodle course}}&lt;br /&gt;
&lt;br /&gt;
There are several ways to track student progress in Moodle.  This page outlines what is available to teachers in a course.&lt;br /&gt;
==Grades==&lt;br /&gt;
Every course has its own [[Gradebook]] which is accessible from &#039;&#039;Course administration &amp;gt; Grades.&#039;&#039; Some activities such as [[Assignment]] and [[Quiz]] send grades back to this gradebook. It is also possible for teachers to enter grades directly into the gradebook. &lt;br /&gt;
[[File:gradebook3.jpg||thumb|frame|[https://www.youtube.com/watch?v=hg7Z6m26jWM&amp;amp;index=32&amp;amp;list=PLxcO_MFWQBDcNFmNYLiffyM58VtpM-vgiGradebook screencast]]]&lt;br /&gt;
&lt;br /&gt;
==Competencies==&lt;br /&gt;
&lt;br /&gt;
[[Competencies]] describe the level of understanding or proficiency of a learner in certain subject-related skills. Competency-based education (CBE), also known as Competency-based learning or Skills-based learning, refers to systems of assessment and grading where students demonstrate these competencies.&lt;br /&gt;
&lt;br /&gt;
==Activity completion==&lt;br /&gt;
If [[Activity completion]] is  enabled by the administrator and in the course settings, teachers can indicate for each course item how they wish it to be registered as complete. A tick/checkmark will then appear against the activity. Students may either mark it complete manually or the item will automatically be registered as complete once a student has met the specified criteria. These may be viewing a resource, submitting an assignment, posting in a forum or other conditions. The teacher can see an overview of who has completed what in the activity completion report in &#039;&#039;Course administration &amp;gt; Reports &amp;gt; Activity completion.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|[[File:studentviewactivitycompletion.png|300px|thumb|Student view]]&lt;br /&gt;
|[[File:activitycompletionreport.png|thumb|300px|Teacher view]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Course completion==&lt;br /&gt;
As an extension of activity completion, enabling [[Course completion]] allows for a course to be officially marked as finished, either manually or automatically according to speficied criteria. If the [[Course completion status block]] is added, students can see their progress during the course. Teachers can view the overall progress of students towards course completion from &#039;&#039;Course administration&amp;gt;Reports&amp;gt;Course completion.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|[[File:studentviewcoursecompletionreport.png|thumb|300px|Student view]]&lt;br /&gt;
|[[File:coursecompletionreport.png|thumb|300px|Teacher view]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Badges==&lt;br /&gt;
[[Badges]] can be awarded either manually or using [[Activity completion|activity completion]] settings in a course and are a popular way to motivate students. Students may be awarded badges at different stages of the course for different levels of progress.&lt;br /&gt;
&lt;br /&gt;
==Course reports==&lt;br /&gt;
A number of [[Course reports]] are available to the teacher in their course to help them track the progress of their students. In addition to the activity and course completion reports mentioned above (which are only available if these settings are enabled) there are also [[Activity report|activity reports]], [[Participation report|participation reports]] and general course [[Logs|logs]].&lt;br /&gt;
&lt;br /&gt;
==Analytics==&lt;br /&gt;
&lt;br /&gt;
The [[Analytics]] feature, in Moodle 3.4 onwards, provides detailed descriptive and prescriptive reports to support learners at risk.&lt;br /&gt;
&lt;br /&gt;
[[de:Lernfortschritt]]&lt;br /&gt;
[[es:Monitoreo del progreso]]&lt;br /&gt;
[[fr:Suivi du progrès]]&lt;/div&gt;</summary>
		<author><name>Anderson.blaine</name></author>
	</entry>
</feed>