MoodleDocs - Wkład użytkownika [pl]

Text editor

2014-03-06T04:21:13Z

Cttxg: /* Screencasts */ Adding MoodleBites YouTube video link

{{Editing text}}
The text editor (sometimes referred to as the 'HTML editor' or even 'TinyMCE') has many icons to assist the user in entering content. Many of these icons and functions should be familiar to anyone who uses a word processor. Some examples of where you will see the text editor include: Editing Section headings, description of an activity, writing an answer to a quiz question or editing the content of many blocks.

'''Note:''' It's possible to disable the TinyMCE editor and only use a plain text editor from ''Administration>Site administration>Plugins>Text editors>Manage editors.''

An individual user can select an editor in their profile from ''Administration>My Profile settings>Edit profile.''

==Collapsing and expanding the editor==
{{New features}}
The TinyMCE editor first appears with just one row of buttons. Clicking the icon top left will expand it to three rows.

{|
|[[File:26tinymce1.png|250px|thumb|Collapsed view]]
|[[File:26tinymce2.png|250px|thumb|Expanded view]]
|}

==Toolbar buttons==
For those who are not familiar with the tool bar, here are the buttons as grouped in their rows. Remember that the site administrator can edit or provide additional buttons.

Row 1
{|
|[[File:26tinymcerow1.png|400px|thumb]]
|}

{| class="nicetable"
|-
|-
| 1:Expand
| 2.Formatting
| 3.Bold
| 4.Italic
|-
| 5.Bulleted list
| 6.Numbered list
| 7.Add link
| 8.Unlink
|-
| 9.Stop auto linking
| 10.Add image
| 11.Add emoticon
| 12.Add media
|-
| 13.Manage embedded files
|
|
|
|}
Row 2

{|
|[[File:26tinymcerow2.png|400px|thumb]]
|}

{| class="nicetable"
|-
|-
| 1:Undo
| 2.Redo
| 3.Underline
| 4.Strikethrough
|-
| 5.Subscript
| 6.Superscript
| 7.Align left
| 8.Align centre
|-
| 9.Align right
| 10.Decrease indent
| 11.Increase indent
| 12.Text colour
|-
| 13.Background colour
| 14.Left to Right
| 15.Right to Left
|
|-

|}
Row 3

{|
|[[File:26tinymcerow3.png|400px|thumb]]
|}

{| class="nicetable"
|-
|-
| 1:Font family
| 2.Font size
| 3.Edit HTML
| 4.Find
|-
| 5.Find/replace
| 6.Insert non-breaking space
| 7.Insert special character
| 8.Insert table
|-
| 9.Clean up messy code
| 10.Remove formatting
| 11.Paste as plain text
| 12.Paste from MS Word

|-
| 13.Toggle full screen
|-

|}

===Colour pickers===
*[[Image:26colourpickers.png]]
There are four levels of selecting a font or background colour,
*A quick pick 5x8 matrix of colours
*"More colours" that links to Picker, Pallet and Named tabs
<gallery>
Image:HTML_editor_color_selector_basic_1.png|A quick pick 5x8 matrix of colors
Image:HTML_editor_color_selector_more_picker_1.png|A rainbow color picker tab
Image:HTML_editor_color_selector_more_pallet_1.png|A Pallet tab with a 18x12 matrix of colors
Image:HTML_editor_color_selector_more_named_1.png|A Named tab with custom pallets
</gallery>

====Insert table====
<gallery widths="300px">
Image:HTMLeditor_Insert_Table_general_1.png|General tab
Image:HTMLeditor_Insert_Table_advanced_1.png|Advanced tab
</gallery>

'''To add borders to a table'''

Cell borders are crucial for helping readers to follow the rows across the screen. If they aren’t showing already you can add them as follows:

#In the Wiki page containing your table, click its Edit tab
#Carefully select all the cells of the table
#Then right click (Macs: Command+click or Ctrl+Click) over any part of your selection to get a context menu; from it select Cell > Table Cell Properties; the cell properties dialog box then loads.
#Click on its Advanced tab, set Border Color to black (for instance), then click Apply, and then click Update.
#Click Save; the Wiki page containing your table will then load displaying its borders.

==Site administration settings==

===Manage editors===

A site administrator can enable / disable text editors in ''Settings > Site administration > Plugins > Text editors > Manage editors''. By default the TinyMCE HTML editor and plain text area are enabled.

===TinyMCE editor settings===

The TinyMCE HTML editor has its own settings page ''Administration>Site administration>Plugins>Text editors>TinyMCE HTML editor>General settings'' with the following options:

====Plugins====
*Buttons for equations, emoticons,images, media, automatic linking, and legacy spell-checking may be enabled, disabled or uninstall here by clicking on their eye.
*Additionally the equation, emoticon and spell check buttons have links to their Settings screens.

[[File:26tinymceplugins.png |thumb|none|upright=2.0|alt="The TinyMCE editor plugins screen" | The TinyMCE editor plugins screen]]

=====Manage embedded files=====
{{New features}}
This plugin allows users to add, delete or override files embedded in the current text area, for example in a label or topic summary. (It complements the [[Embedded files repository]])

{|
|[[File:26embeddedfiles1.png|thumb|The Manage files button]]
|
|[[File:26embeddefiles2.png|thumb|Managing embedded files from within TinyMCE]]
|}

=====Insert equation=====

Accessed from ''Administration>Site administration>Plugins>Text editors>TinyMCE HTML editor>Edit equation'', this allows you to enable or disable the TeX filter in the editor context and thereby display the Dragmath button. If you have a global custom TeX filter, then disable this setting.

=====Insert emoticon=====
Accessed from ''Administration>Site administration>Plugins>Text editors>TinyMCE HTML editor>Insert emoticon'', this allows you to enable or disable the emoticon filter in the editor context and thereby display the emoticon button.

===== Legacy spell checker=====
The legacy spell checker is visible in IE9 and lower only, but not in other browsers. If you want to disable it and and rely on browser spell checker functionality instead, you can do this by disabling the ''legacy spellchecker'' plugin by clicking its eye in ''Administration > Site administration > Plugins > Text editors > TinyMCE HTML editor > General settings''

To spell-check via your browser, type your word (which if incorrectly spelt will have red lines under it) and press right click + CTRL
{|
|[[File:Browserspellcheck.png|thumb|Right-click+CTRL for browser spellcheck]]
|}

'''NOTE:'''
While the default spell engine is Google spell which can be changed in ''Administration>Site administration>Plugins>Text editors>TinyMCE HTML editor'', this is no longer supported by Google and will not work. (Note that it is only visible in IE9 and lower) It is due to be removed. See MDL-38867. In browser spell check is recommended.

If PSpell is selected then aspell 0.50 or later must be installed on your server and the path to aspell set in Administration > Site administration > Server > System Paths.

You can select a different spell engine from ''Administration> Site administration > Plugins > Text editors > TinyMCE HTML editor>Check spelling''

{|
|[[File:Spellengine.png|thumb|Choosing a different spell engine]]
|}
According to: http://php.net/manual/en/book.pspell.php

"As of php 5.3. Pspell is no longer supported/bundled. Instead you can use the enchant which is bundled by default in 5.3."

If PSpell is selected then aspell 0.50 or later must be installed on your server and the path to aspell set in Administration > Site administration > Server > System Paths.

===Customising the editor toolbar===

An administrator can remove or add buttons to the TinyMCE editor toolbar by altering the Editor toolbar box in ''Administration>Site administration>Plugins>Text editors>TinyMCE HTML editor>General settings'' as demonstrated in the screencast [http://youtu.be/vTW1DImro9c Customise the text editor in 2.4]

{|
| [[File:editortoolbar.png|thumb|The Editor toolbar box]]
|[[File:horizontalrule.png|thumb|Example of toolbar with added horizontal rule button]]

|}

====Available fonts list====

In addition to the default fonts, a site administrator can add extra fonts by typing their name and string in the box in ''Administration > Site administration > Plugins > Text editors > TinyMCE HTML editor>General settings'' as demonstrated in the screencast [http://youtu.be/udP7Bnur30Y How to add extra fonts].

{|
|[[File:comicsans.png|thumb|Example of custom font]]
|}

====Custom configuration====

A setting in ''Administration>Site administration>Plugins>Text editors>TinyMCE HTML editor>General settings'' provides a box in which an administrator can apply custom formats. See MDL-37186 for more details with examples, and see also the [http://www.tinymce.com/wiki.php/Configuration:formats TinyMCE configuration page]

{|
|[[File:bottomtoolbar.png|thumb| Example 1:Toolbar at the bottom]]
|[[File:customstyles.png|thumb| Example 2: Custom styles]]
|}

*Example: Moving the toolbar to the bottom:

Add the following:
{"theme_advanced_toolbar_location" : "bottom"}

*Example: Adding your own custom styles.
(This might be useful for example if you want a "house style" for important notes, key points or similar)
In the editor toolbar, enter "styleselect" and then in the custom box add the following code, changing it to suit your purposes:
{"style_formats" : [
{"title" : "Bold text", "inline" : "b"},
{"title" : "Red text", "inline" : "span", "styles" : {"color" : "#ff0000"}},
{"title" : "Red header", "block" : "h1", "styles" : {"color" : "#ff0000"}} ]}

The following will let you use bootstrap CSS classes if you use a bootstrap based theme:

{"style_formats" : [
{"title" : "Well", "block" : "div", "classes" : "well"},
{"title" : "Label", "inline" : "span", "classes" : "label"},
{"title" : "Label - success", "inline" : "span", "classes" : "label label-success"},
{"title" : "Label - warning", "inline" : "span", "classes" : "label label-warning"},
{"title" : "Label - important", "inline" : "span", "classes" : "label label-important"},
{"title" : "Label - info", "inline" : "span", "classes" : "label label-info"},
{"title" : "Label - inverse", "inline" : "span", "classes" : "label label-inverse"},
{"title" : "Button", "inline" : "a", "classes" : "btn btn"},
{"title" : "Button - primary", "inline" : "a", "classes" : "btn btn-primary"},
{"title" : "Button - info", "inline" : "a", "classes" : "btn btn-info"},
{"title" : "Button - success", "inline" : "a", "classes" : "btn btn-success"},
{"title" : "Button - warning", "inline" : "a", "classes" : "btn btn-warning"},
{"title" : "Button - danger", "inline" : "a", "classes" : "btn btn-danger"},
{"title" : "Button - inverse", "inline" : "a", "classes" : "btn btn-inverse"}
]}

*Example: Enabling copy of rich content with styles from MS Word (tm) and paste into TineMCE without removing important styles:

{"paste_retain_style_properties" : "margin, padding, width, height, font-size,
font-weight, font-family, color, text-align, ul, ol, li,
text-decoration, border, background, float, display"}

==See also==

===Screencasts===
[http://www.youtube.com/watch?v=1m2xkm2EyXA&feature=share&list=SPxcO_MFWQBDe8RRnGjoUDqbcm9PSlIoWn&index=4 TinyMCE text editor improvements.]

*[http://youtu.be/bBZQYGcDaMg Moodle 2.0 HTML Editor - Row 1] MoodleBites video on YouTube
*[http://youtu.be/uS_M6-eHsxE Moodle 2.0 HTML Editor - Row 2] MoodleBites video on YouTube
*[http://youtu.be/3rRztnWkhuY Moodle 2.0 HTML Editor - Row 3] MoodleBites video on YouTube

===Other===

* [[Text editor FAQ]]
* [[Embedded files repository]]

[[Category:Site administration]]

[[de:Text-Editor]]
[[es:Editor de texto]]

Developer tools

2014-03-06T04:17:16Z

Cttxg: Adding MoodleBites YouTube video link

{{Managing a Moodle site}}
Developers of Moodle code have some special tools included in the Moodle package to assist them. Most of the tools should ONLY be used on test sites (not production sites). However there are a couple which may be used by a cautious administrator.

===Debugging===

''Administration > Site administration > Development > Debugging''

At certain times a site administrator will need to see more and/or a more complete error message. The default is to show NONE. These messages can also 1) be very confusing to teachers and students when they suddenly appear and 2) can reveal things about your Moodle and web server that should not be common knowledge. Thus use with care and for short periods of time. See [[Debugging]] for details.

===Purge all caches===

''Administration > Site administration > Development > Purge all caches''

Moodle can cache themes, language strings, filters and other bits of information that have been calculated and stored by the web browser. This link forces all user web browsers to refresh their screens of '''any''' information that Moodle has cached. Several modules that use cache have settings which will turn off caching for that module. Eliminating or purging caches slows performance.

==Experimental features==

Moodle includes a few experimental features which a cautious administrator may consider enabling. See [[Experimental settings]] for details.

==See also==
*[http://youtu.be/HlVOcqeUHBs Moodle Administration Development settings] MoodleBites video on YouTube

[[es:Herramientas para desarrolladores]]

Building Database

2014-03-06T03:44:47Z

Cttxg: /* See also */ Adding MoodleBites YouTube video links

{{Database}}
After creating a database, as explained in [[Database activity settings]]...
* Next you define the kind of fields that define the information you wish to collect. For example a database of famous paintings may have a picture field called ''painting'', for uploading an image file showing the painting, and two text fields called ''artist'' and ''title'' for the name of the artist and the painting. Alternatively, you can use a database preset (see below).
* It is then optional to edit the [[Database templates|database templates]] to alter the way in which the database displays entries.

==Database fields==

A '''field''' is a named unit of information. Each entry in a [[Database activity module|database activity module]] can have multiple fields of multiple types e.g. a text field called 'favourite color' which allows you to type in your favourite shade, or a menu called 'state' that lets you choose one from a list of the 50 that make up the United States of America. By combining several fields with appropriate names and types you should be able to capture all the relevant information about the items in your database.

Note that if you later edit the fields in the databases you must use the Reset template button, or manually edit the template, to ensure the new fields are added to the display.

=== Field name and description ===

The name is what is shown when an entry is added. It must be unique and short. The description is for your benefit to help identify that field.

=== Field types ===

The following screenshots show "before" and "afters" of setting up fields. The selection in orange shows the field as it is displayed for the user when they add an entry.

;Checkbox
:This allows you to offer checkboxes for the user to select. Add the options one under the other. The word will appear next to a checkbox when the user clicks to add an entry. They can check more than one box.

[[File:Checkboxfield1.png]]

;Date
:This allows a user to enter a date by picking a day, month and year from a drop down list.

[[File:Datefield1.png]]

;File
:Users can upload a file from their computer. If it is an image file then the picture field may be a better choice.

[[File:Filefield.png]]

;Latitude/longitude
:Users can enter a geographic location using latitude and longitude. For example, [http://moodle.com/hq/ Moodle HQ] is at latitude -31.9545, longitude 115.877. When viewing the record, links are automatically generated linking to geographic data services such as [http://earth.google.com Google Earth], [http://www.openstreetmap.org/ OpenStreetMap], [http://www.geabios.com/ GeaBios],[http://www.mapstars.com/extern/deltaworks-holland Mapstars] and more. (The teacher can choose which of those links appear, if any.)

[[File:Latlongfield.png]]

;Menu
:The text entered in the ''options'' area will be presented as a drop-down list for the user to choose from. Each line become a different option.

[[File:Menufield.png]]

;Menu (Multi-select)
:The text entered in the ''options'' area will be presented as a list for the user to choose from and each line become a different option. By holding down control or shift as they click, users will be able to select multiple options. This is a fairly advanced computer skill so it may be wise to use multiple checkboxes instead.

[[File:Multiselectfield.png]]

;Number
:This allows users to enter any number. For example:
* 42
* -1000
* 0
* 0.123
* 3.0e8
:(For those who care about the technical details, the field stores floating point numbers.)

[[File:Numberfield.png]]

;Picture
:This allows a user to upload and display an image file. "Single view" is when the image is viewed on its own; "list view" is when it is viewed in with other images. Single view can be larger than list view.

[[File:Picturefield.png]]

;Radio buttons
:The user gets radio buttons and can choose only one. They can only submit the entry when they have clicked on one button. (Note:If you only have two options and they are opposites (true/false, yes/no) then you could simply use a single checkbox instead. However checkboxes default to their unchecked status and so people could submit without actively selecting one of the options. This may not always be appropriate.)

[[File:Radiofield.png]]

;Text
:Users can enter text up to 60 characters in length. For longer text, or for text that requires formatting such as headers and bullet points, you can use a text area field.

[[File:Textfield.png]]

;Text area
:This allows users to enter a long piece of text using the text editor.

[[File:Textareafield.png]]

;URL
:The user can add a link to a website here. If you select ''autolink'' then the URL becomes clickable.. If you also enter a ''forced name for the link'' then that text will be used for the hyperlink. For example in a database of authors you may wish people to enter the author's website. If you enter the text 'homepage' as a forced name then clicking on text "homepage" will take you to the entered URL.
You can choose to have the URL open in a new window if so desired.

[[File:Urlfield.png]]

==Presets==

To avoid the necessity of always having to create a new database from scratch, the database activity module has a presets feature. An image gallery preset is currently included in the database module to help get you started. You can create your own presets as well and share them with others.

===Importing a preset===

[[Image:databasepresetsnew.png|thumb|Database presets page]]
To use a preset:

# On the database page, click the Presets tab.
# The usual way to import a preset is clicking the "Choose file" button and browsing to the ZIP file containing the preset (eg. "preset.zip") stored on the server. If there does not yet exist a preset ZIP file on the server, upload it from your local machine. Choose the desired preset file by clicking on its action "Choose". Finally, press the "Import" button.
# Alternatively, you can choose a previously loaded preset.
# After the import, you can start to add or import entries. All the hard work of setting up the fields and templates has been done for you. If you desire, you can still customize the fields and templates.

You will see a "Overwrite current settings" checkbox after the "Import" button has been pressed. If checked, the database activity overwrites some of its current general settings by those stored in the preset:
* the "Introduction" HTML text
* "Required entries"
* "Entries required before viewing"
* "Maximum entries"
* "Comments"
* "Require approval?"
* rssarticles

===Exporting a preset===

If you wish to share your database presets with others, you have two options:

#Export as a ZIP file, which can then be imported to another course or Moodle site.
#Save as a preset, which publishes the database for other teachers on your site to use. It will then appear in the preset list. (You can delete it from the list at any time.)

Note: Only the fields and templates of the database are copied when exporting or saving it as a preset, not the entries.

===Presets for download===

The [http://school.demo.moodle.net/course/view.php?id=127 Activity Examples course] on the School demo site has a number of database activities with presets for download.

==See also==
*[http://youtu.be/sRxDg7tGyjw Moodle 2.0 Database - part 1 ] MoodleBites video on YouTube
*[http://youtu.be/RRHy7vjCc7E Moodle 2.0 Database - part 2] MoodleBites video on YouTube

Using Moodle forum discussions:
*[http://moodle.org/mod/forum/discuss.php?d=84050 Can't get columns to line up in list view] including moodle.org presets for download
*[http://moodle.org/mod/forum/discuss.php?d=87005 New preset, please review, and make suggestions!] including FAQ preset for download
*[http://moodle.org/mod/forum/discuss.php?d=87560 Issue 53: Encyclopedia database preset] including encyclopedia-style preset for download
*[http://moodle.org/mod/forum/discuss.php?d=88727 Issue 51 - Design a Database Preset for Document Sharing] including preset for download
*[http://moodle.org/mod/forum/discuss.php?d=94854#p457252 Looking for some stellar examples of Moodle courses] including book reviews preset for download
*[http://moodle.org/mod/forum/discuss.php?d=89117#p511029 Restricting access to database content by user?] with research diary preset for download

[[de:Datenbank erstellen]]

Database activity settings

2014-03-06T03:44:12Z

Cttxg: /* See also */ Adding MoodleBites YouTube video link

{{Database}}==Adding a database activity==

To add a database activity:
#With the editing turned on,in the section you wish to add your database, click the "Add an activity or resource" link (or, if not present, the "Add an activity" drop down menu )and choose ''Database'' All settings may expanded by clicking the "Expand all" link top right.
# Give your new database a name and a description.
# Select your options (see below).
# Click the "Save and display" button at the bottom of the page.
# Define the [[Database fields|fields]] or use a [[Database presets|preset]].
# Define the [[Database templates|templates]].
# Add one or two same entries then edit the templates as appropriate.

==General==
{|
|[[File:database26general.png|General settings expanded by default]]
|}

===Name===
Choose a helpful name as this will form the link students will click on to access your database.
===Description===
Type the description of the database here. Click the icon on the left to expand the toolbar to three lines.

===Display description on course page===
If this box is ticked, the description will appear on the course page just below the name of the Database.

==Entries==
(These settings are collapsed by default.)
{|
|[[File:databasentries25.png|Entries settings expanded]]
|}

===Approval required?===
If set to "yes", the entry will only be visible once a teacher has checked and approved it.
===Allow comments on entries===
If set to "yes", users will be able to comment on database entries.
===Entries required for completion===
Select here how many entries you wish the student to add before the activity can be considered "complete".
===Entries required for viewing===
Select here how many entries you wish the student to add before they are allowed to see entries by other people. ''Note'': If entries are required before viewing, the database auto-linking filter should be disabled. This is because the database auto-linking filter can't determine whether a user has submitted the required number of entries.
===Maxiumum number of entries===
Select here the maximum number of entries you wish students to make.

==Availability==
(These settings are collapsed by default.)
{|
|[[File:datbaseavailability26.png|Availability settings expanded]]
|}

===Available from/to===
Select here the dates you want the database to be visible to students.

===Read only from/to===
If you wish, select here the dates you want students to be able to see entries in the database but not be able to add their own.
For example you could make a database 'available from' January 1st until March 1st, but 'read only' from January 1st to February 1st. This means students can only view entries for a month before being able to add their own.

The 'available from/to' settings override the 'read only from/to' settings. So if a database has 'read only' from 1st January, and "available from" 1st February, students will '''not''' be able to view its content during January.

==RSS==
(This setting is collapsed by default and only visible if RSS has been enabled on the site and for the database.)

Select the number of entries you wish to appear in the RSS feed here.

==Grade==
(This setting is collapsed by default)
Choose the category in which this database will appear if ratings are enabled.

==Ratings==
(These settings are collapsed by default)

{|
|[[File:databaseratings26.png|Ratings settings expanded]]
|}

===Roles with permissions to rate===
Database entries can be rated using a [[Scales|scale]]. By default, only teachers can rate database entries, though students can be given permission to do so if desired from ''Administration>Database administration''. This is a useful tool for giving students participation grades. Any ratings given are recorded in the [[Gradebook|gradebook]].

==Common module settings==

(These settings are collapsed by default.)

See [[Common module settings]]
==Restrict access/Activity completion==
(These settings are collapsed by default)

These settings are visible if [[Conditional activities]] and [[Activity completion]] have been enabled in the site and the course.

==Site administration settings==

Database activity defaults and additional settings may changed by an administrator in ''Administration > Site administration > Plugins > Activity modules > Database''.

==Database activity capabilities==

*[[Capabilities/mod/data:approve|Approve unapproved entries]]
*[[Capabilities/mod/data:comment|Write comments]]
*[[Capabilities/mod/data:exportallentries|Export all database entries]]
*[[Capabilities/mod/data:exportentry|Export a database entry]]
*[[Capabilities/mod/data:exportownentry|Export own database entry]]
*[[Capabilities/mod/data:managecomments|Manage database activity comments]]
*[[Capabilities/mod/data:manageentries|Manage database activity entries]]
*[[Capabilities/mod/data:managetemplates|Manage templates]]
*[[Capabilities/mod/data:manageuserpresets|Manage all template presets]]
*[[Capabilities/mod/data:rate|Rate entries]]
*[[Capabilities/mod/data:viewallratings|View all raw ratings given by individuals]]
*[[Capabilities/mod/data:viewalluserpresets|View presets from all users]]
*[[Capabilities/mod/data:viewanyrating|View total ratings that anyone received]]
*[[Capabilities/mod/data:viewentry|View entries]]
*[[Capabilities/mod/data:viewrating|View the total rating you received]]
*[[Capabilities/mod/data:writeentry|Write entries]]
*[[Capabilities/mod/data:addinstance|Add a new database activity]]

==See also==
*[http://youtu.be/sRxDg7tGyjw Moodle 2.0 Database - part 1] MoodleBites video on YouTube
*[http://youtu.be/RRHy7vjCc7E Moodle 2.0 Database - part 2] MoodleBites video on YouTube

[[de:Datenbank konfigurieren]]
[[fr:Créer une base de données]]
[[ja:データベースの追加/編集]]
[[es:Configuraciones de actividad BasedeDatos]]

Database activity settings

2014-03-06T03:42:54Z

Cttxg: /* See also */

{{Database}}==Adding a database activity==

To add a database activity:
#With the editing turned on,in the section you wish to add your database, click the "Add an activity or resource" link (or, if not present, the "Add an activity" drop down menu )and choose ''Database'' All settings may expanded by clicking the "Expand all" link top right.
# Give your new database a name and a description.
# Select your options (see below).
# Click the "Save and display" button at the bottom of the page.
# Define the [[Database fields|fields]] or use a [[Database presets|preset]].
# Define the [[Database templates|templates]].
# Add one or two same entries then edit the templates as appropriate.

==General==
{|
|[[File:database26general.png|General settings expanded by default]]
|}

===Name===
Choose a helpful name as this will form the link students will click on to access your database.
===Description===
Type the description of the database here. Click the icon on the left to expand the toolbar to three lines.

===Display description on course page===
If this box is ticked, the description will appear on the course page just below the name of the Database.

==Entries==
(These settings are collapsed by default.)
{|
|[[File:databasentries25.png|Entries settings expanded]]
|}

===Approval required?===
If set to "yes", the entry will only be visible once a teacher has checked and approved it.
===Allow comments on entries===
If set to "yes", users will be able to comment on database entries.
===Entries required for completion===
Select here how many entries you wish the student to add before the activity can be considered "complete".
===Entries required for viewing===
Select here how many entries you wish the student to add before they are allowed to see entries by other people. ''Note'': If entries are required before viewing, the database auto-linking filter should be disabled. This is because the database auto-linking filter can't determine whether a user has submitted the required number of entries.
===Maxiumum number of entries===
Select here the maximum number of entries you wish students to make.

==Availability==
(These settings are collapsed by default.)
{|
|[[File:datbaseavailability26.png|Availability settings expanded]]
|}

===Available from/to===
Select here the dates you want the database to be visible to students.

===Read only from/to===
If you wish, select here the dates you want students to be able to see entries in the database but not be able to add their own.
For example you could make a database 'available from' January 1st until March 1st, but 'read only' from January 1st to February 1st. This means students can only view entries for a month before being able to add their own.

The 'available from/to' settings override the 'read only from/to' settings. So if a database has 'read only' from 1st January, and "available from" 1st February, students will '''not''' be able to view its content during January.

==RSS==
(This setting is collapsed by default and only visible if RSS has been enabled on the site and for the database.)

Select the number of entries you wish to appear in the RSS feed here.

==Grade==
(This setting is collapsed by default)
Choose the category in which this database will appear if ratings are enabled.

==Ratings==
(These settings are collapsed by default)

{|
|[[File:databaseratings26.png|Ratings settings expanded]]
|}

===Roles with permissions to rate===
Database entries can be rated using a [[Scales|scale]]. By default, only teachers can rate database entries, though students can be given permission to do so if desired from ''Administration>Database administration''. This is a useful tool for giving students participation grades. Any ratings given are recorded in the [[Gradebook|gradebook]].

==Common module settings==

(These settings are collapsed by default.)

See [[Common module settings]]
==Restrict access/Activity completion==
(These settings are collapsed by default)

These settings are visible if [[Conditional activities]] and [[Activity completion]] have been enabled in the site and the course.

==Site administration settings==

Database activity defaults and additional settings may changed by an administrator in ''Administration > Site administration > Plugins > Activity modules > Database''.

==Database activity capabilities==

*[[Capabilities/mod/data:approve|Approve unapproved entries]]
*[[Capabilities/mod/data:comment|Write comments]]
*[[Capabilities/mod/data:exportallentries|Export all database entries]]
*[[Capabilities/mod/data:exportentry|Export a database entry]]
*[[Capabilities/mod/data:exportownentry|Export own database entry]]
*[[Capabilities/mod/data:managecomments|Manage database activity comments]]
*[[Capabilities/mod/data:manageentries|Manage database activity entries]]
*[[Capabilities/mod/data:managetemplates|Manage templates]]
*[[Capabilities/mod/data:manageuserpresets|Manage all template presets]]
*[[Capabilities/mod/data:rate|Rate entries]]
*[[Capabilities/mod/data:viewallratings|View all raw ratings given by individuals]]
*[[Capabilities/mod/data:viewalluserpresets|View presets from all users]]
*[[Capabilities/mod/data:viewanyrating|View total ratings that anyone received]]
*[[Capabilities/mod/data:viewentry|View entries]]
*[[Capabilities/mod/data:viewrating|View the total rating you received]]
*[[Capabilities/mod/data:writeentry|Write entries]]
*[[Capabilities/mod/data:addinstance|Add a new database activity]]

==See also==
*[http://youtu.be/sRxDg7tGyjw Moodle 2.0 Database - part 1] MoodleBites video on YouTube

[[de:Datenbank konfigurieren]]
[[fr:Créer une base de données]]
[[ja:データベースの追加/編集]]
[[es:Configuraciones de actividad BasedeDatos]]

Database activity settings

2014-03-06T03:42:06Z

Cttxg: Adding MoodleBites YouTube video link

{{Database}}==Adding a database activity==

To add a database activity:
#With the editing turned on,in the section you wish to add your database, click the "Add an activity or resource" link (or, if not present, the "Add an activity" drop down menu )and choose ''Database'' All settings may expanded by clicking the "Expand all" link top right.
# Give your new database a name and a description.
# Select your options (see below).
# Click the "Save and display" button at the bottom of the page.
# Define the [[Database fields|fields]] or use a [[Database presets|preset]].
# Define the [[Database templates|templates]].
# Add one or two same entries then edit the templates as appropriate.

==General==
{|
|[[File:database26general.png|General settings expanded by default]]
|}

===Name===
Choose a helpful name as this will form the link students will click on to access your database.
===Description===
Type the description of the database here. Click the icon on the left to expand the toolbar to three lines.

===Display description on course page===
If this box is ticked, the description will appear on the course page just below the name of the Database.

==Entries==
(These settings are collapsed by default.)
{|
|[[File:databasentries25.png|Entries settings expanded]]
|}

===Approval required?===
If set to "yes", the entry will only be visible once a teacher has checked and approved it.
===Allow comments on entries===
If set to "yes", users will be able to comment on database entries.
===Entries required for completion===
Select here how many entries you wish the student to add before the activity can be considered "complete".
===Entries required for viewing===
Select here how many entries you wish the student to add before they are allowed to see entries by other people. ''Note'': If entries are required before viewing, the database auto-linking filter should be disabled. This is because the database auto-linking filter can't determine whether a user has submitted the required number of entries.
===Maxiumum number of entries===
Select here the maximum number of entries you wish students to make.

==Availability==
(These settings are collapsed by default.)
{|
|[[File:datbaseavailability26.png|Availability settings expanded]]
|}

===Available from/to===
Select here the dates you want the database to be visible to students.

===Read only from/to===
If you wish, select here the dates you want students to be able to see entries in the database but not be able to add their own.
For example you could make a database 'available from' January 1st until March 1st, but 'read only' from January 1st to February 1st. This means students can only view entries for a month before being able to add their own.

The 'available from/to' settings override the 'read only from/to' settings. So if a database has 'read only' from 1st January, and "available from" 1st February, students will '''not''' be able to view its content during January.

==RSS==
(This setting is collapsed by default and only visible if RSS has been enabled on the site and for the database.)

Select the number of entries you wish to appear in the RSS feed here.

==Grade==
(This setting is collapsed by default)
Choose the category in which this database will appear if ratings are enabled.

==Ratings==
(These settings are collapsed by default)

{|
|[[File:databaseratings26.png|Ratings settings expanded]]
|}

===Roles with permissions to rate===
Database entries can be rated using a [[Scales|scale]]. By default, only teachers can rate database entries, though students can be given permission to do so if desired from ''Administration>Database administration''. This is a useful tool for giving students participation grades. Any ratings given are recorded in the [[Gradebook|gradebook]].

==Common module settings==

(These settings are collapsed by default.)

See [[Common module settings]]
==Restrict access/Activity completion==
(These settings are collapsed by default)

These settings are visible if [[Conditional activities]] and [[Activity completion]] have been enabled in the site and the course.

==Site administration settings==

Database activity defaults and additional settings may changed by an administrator in ''Administration > Site administration > Plugins > Activity modules > Database''.

==Database activity capabilities==

*[[Capabilities/mod/data:approve|Approve unapproved entries]]
*[[Capabilities/mod/data:comment|Write comments]]
*[[Capabilities/mod/data:exportallentries|Export all database entries]]
*[[Capabilities/mod/data:exportentry|Export a database entry]]
*[[Capabilities/mod/data:exportownentry|Export own database entry]]
*[[Capabilities/mod/data:managecomments|Manage database activity comments]]
*[[Capabilities/mod/data:manageentries|Manage database activity entries]]
*[[Capabilities/mod/data:managetemplates|Manage templates]]
*[[Capabilities/mod/data:manageuserpresets|Manage all template presets]]
*[[Capabilities/mod/data:rate|Rate entries]]
*[[Capabilities/mod/data:viewallratings|View all raw ratings given by individuals]]
*[[Capabilities/mod/data:viewalluserpresets|View presets from all users]]
*[[Capabilities/mod/data:viewanyrating|View total ratings that anyone received]]
*[[Capabilities/mod/data:viewentry|View entries]]
*[[Capabilities/mod/data:viewrating|View the total rating you received]]
*[[Capabilities/mod/data:writeentry|Write entries]]
*[[Capabilities/mod/data:addinstance|Add a new database activity]]

==See also==
*[http://youtu.be/sRxDg7tGyjw Creating a Moodle database activity template] MoodleBites video on YouTube

[[de:Datenbank konfigurieren]]
[[fr:Créer une base de données]]
[[ja:データベースの追加/編集]]
[[es:Configuraciones de actividad BasedeDatos]]

Database templates

2014-03-06T03:37:30Z

Cttxg: /* See also */ Adding MoodleBites YouTube video link

{{Database}}
Templates for the [[Database activity module]] allow you to control the visual layout of information when listing, viewing or editing database entries. It is a similar to the technique used to ''mail merge'' letters in word processors such as Open Office Writer or Microsoft Word.

== Tag usage ==

The content of each [[Database fields|field]] you create for your database and some special tags (listed below) can be inserted into the output template by the use of tags.

Fields have the format <code><nowiki>[[fieldname]]</nowiki></code>. All other tags have the format <code>##sometag##</code>.

To use the tags in the box on the left of the page, use the HTML viewer, place your cursor in the text area of your target edit and then click on the tag you want to place. Alternatively, you may simply type the appropriate name within the required symbols like <code>##this##</code> or <code><nowiki>[[this]]</nowiki></code>, respectively.

* <code>##edit##</code> creates a clickable icon link that allows you to edit the current entry (only appears if you have the rights to do this)
* <code>##delete##</code> creates a link that lets you delete the current entry (only appears if you have the rights to do this)
* <code>##approve##</code> create a link that lets you approve the current database entry (only appears if you have the rights to do this)
* <code>##more##</code> creates a link to the single view, which may contain more detailed info
* <code>##moreurl##</code> creates just the URL for the above link, useful for creating your own links. You can click on the link icon and type <code>##moreurl##</code> into URL field or in source view type <pre><a href="##moreurl##">[[fieldname]]</a></pre>
* <code>##comments##</code> creates a link to the view/edit comments page, the link text is the current number of comments (only appears if comments are turned on)
* <code>##user##</code> creates a link to the user page of the user who submitted the entry, link text is their name
* <code>##timeadded##</code>
* <code>##timemodified##</code>

== List template ==

This template allows you to control the fields used and their layout when viewing multiple entries at once (e.g. search results). It is possible that this view may simply provide an overview with more detailed information available by clicking on an entry to access the single view of the entry.

See [http://tracker.moodle.org/secure/attachment/23333/moodle_databse_activity_list_formatting.pdf Designing a list view in Moodle database activity] for instructions on how to create a list template table.

The list template can also be used as a way to [[Database export|export your database]] as a CSV file.

== Single template ==
This is used to display a single entry at a time and so has more space for display and can use, for example, larger versions of images or optionally provide more information than shown in the list view.

[[Image:Databasesingletemplate.png]]

== Advanced search template ==

An advanced search template is for creating the interface form used in the advanced search.

== Add template ==

This template creates the interface form used when adding or editing database entries.

== RSS template ==

Lets you control the content of the [[RSS]] feed for database entries.

== CSS template ==

If any of the [[HTML in Moodle|HTML]] in your other templates requires [[CSS]] to provide visual style you can specify it here.

== Javascript template ==

You can use javascript to manipulate the way elements are displayed in either the List, Single or Add templates. Basically you need to enclose the part you want to manipulate in some named html element. The naming is essential as it allows you to identify the element for manipulation.

Let's say, for example, you have a field in your database that stores a person's name and when you display the names in the List View you want to count the times a name matches some criteria and display the result.

Your database will contain a field which we will call "name". In your List template you will be able to display the contents of that field by using the <nowiki>[[name]]</nowiki> construct at the place where you want that information displayed. For example in the ''Repeated entry'' on the list template you will have

<pre>
<table>
<tr>
<td>Name: [[name]]</td>
</tr>
<table>
</pre>

You now need to modify that entry to ensure that the part you want to manipulate is a named element.

<pre>
<table>
<tr>
<td name="named">Name: [[name]]</td>
</tr>
<table>
</pre>

The footer of your list view can then contain another named element to display the result.

<pre>
<div name="result"></div>
</pre>

Your javascript template can now look as follows

<pre>
var cnt = 0;
var re = /foo|Foo/;

function init(){
var namedElements = document.getElementsByName("named");
for (i=0; i < namedElements.length; i++) {
if(re.test(namedElements[i].innerHTML)) cnt++;
}
var namedResult = document.getElementsByName("result");
namedResult[0].innerHTML = cnt;
}

window.onload = init;
</pre>

This will display a table of names as is usual in the list view. Now at the bottom there will also be the count of the names that matched foo or Foo.

Note that window.onload does not handle any dependencies on [https://docs.moodle.org/dev/Javascript_FAQ#What_JavaScript_library_does_Moodle_use.3F YUI] code, so any YUI modules required by your init() code may not be loaded, and your code will fail.

In this case, instead of onload, use:
<pre>
YUI().use('node', 'other', 'dependencies', function(Y) {

// Your code here.

// This function is a closure so the Y object you define in the function definition is yours and nothing else on the page should be able to break it.

});
</pre>

== Reset templates button ==

When you first create a database the templates will be pre-filled with appropriate HTML. If you later add fields then you can press the ''reset templates'' button and it will add HTML for the new fields in a similar fashion. If you have edited any of the templates in the meantime then your changes will be lost. It is recommended that you finalize the database fields before changing the template code.

==See also==
*[[Database presets]]
*[http://video.google.com/videoplay?docid=7026851446099005477 Video demonstrating tag usage]
*[http://youtu.be/sRxDg7tGyjw Creating a Moodle database activity template ] MoodleBites video on YouTube

Using Moodle forum discussions:
*[http://moodle.org/mod/forum/discuss.php?d=55338 Look of the database module]
*[http://moodle.org/mod/forum/discuss.php?d=74243 How can I list database information horizontally instead of vertically?]
*[http://moodle.org/mod/forum/discuss.php?d=61179 For those who want the display of Moodle Site's Modules and plugins]
*[http://moodle.org/mod/forum/discuss.php?d=84050 Can't get columns to line up in list view]
*[http://moodle.org/mod/forum/discuss.php?d=86927 Time stamp for database entries?]

[[de:Datenbank-Vorlagen]]
[[fr:Modèles]]
[[ru:Шаблоны]]
[[ja:データベーステンプレート]]

User profile fields

2014-03-06T03:21:15Z

Cttxg: /* See also */ Adding MoodleBites YouTube video link

{{Accounts}}
==Overview==

Administrators can create new user profile categories and fields in ''Administration > Site administration > Users > Accounts > User profile fields''.

Profile fields may be a menu of choices, text area, text input or a checkbox and may be required or not.

New profile fields will appear on each user’s profile page unless "Who is this field visible to?" is set to "Not visible" in which case only the administrator can see the field. The fields can also be displayed on the signup page if "Display on signup page?" is set to "Yes" (although note that they will never be displayed if set to "Not visible").

You can set the order in which your custom profile fields appear under the associated profile category using the up/down arrows on the User profiles fields page.

To create a new profile field, select the profile field format you require from the dropdown list.

== Common Settings ==

All new fields must be given a unique Short Name and a Name (this is displayed on the profile page). You may also choose to enter a Description for the field for your own reference.

There are also a number of configuration options common to all custom profile field types:

;Is this field required?
:This option specifies whether this is a mandatory or optional field for user accounts.

;Is this field locked?
:This option determines whether once information is populated in this field, it cannot be edited by the user.

;Should the data be unique?
:If you need the information populated in your field to be unique across the system (such as an ID number) select Yes to this option and the profile page update will perform a validation check on the data entered.

;Display on signup page?
:Depending on the authentication method in use on your Moodle site, you may have some users creating their own accounts. If you would like this custom field to appear on the registration or signup page, select Yes.

;Who is this field visible to?
:Each custom field can be given one of three visibility settings:

:* Visible to everyone
:* Not visible
:* Visible to user

:The Not visible setting would typically be set by an administrator who wants to hold private data on the users. The Visible to user setting would normally be selected for a field that holds sensitive information, while the Visible to everyone setting can be used for any type of information.

== Specific Settings ==

There are also a few field type Specific Settings requiring configuration around default value and size.

'''Important'''

If the site administrator bulk [[Upload users|uploads user data]] via .csv file, it is essential to use the correct convention to represent the new profile field. The convention is ''profile_field_shortname''

Replace 'shortname' with the actual short name used for the new profile field eg. dob. So the field should read something like profile_field_dob.

Also, you will need to visit ''Administration > Site Administration > Users > Accounts > User Profile Fields > Create new Profile Field'' before attempting to upload a file using it. <i>Creating an upload file first with custom profile fields</i> <b>without</b> <i>creating the User Profile Fields first in Site Administration</i> <b>will result in the error <u>profile_field_shortname is not a valid field name.</u></b>

==Examples of use==

*'''House System'''

Many schools have a 'House' system where students and staff are assigned to a given House. For example, a school has eight houses, named after its founders: Adderton, Coolock, Gorry, Loretto, McAuley, Mercedes, Tighe and Whitty. The site administrator can add a user profile field that offers a 'Menu of choices' to the user. A default value can also be selected. If the administrator decides to bulk upload House data for users via a .csv file, it is important to represent the above array of values as 1,2,3,4,5,6,7,8 in the file. That is to state, if a user belongs to Adderton House, the value '1' should be entered for the 'House' user profile field in the given record.

*'''U.S. States'''

This can be used to improve ambiguous postal addresses by including (for example) the State.

*[[Birthday block]] (contributed code)

==See also==
*[http://youtu.be/5x9etteuayc Custom Profile Fields] MoodleBites video on YouTube
*[[:dev:User profile fields]] developer documentation

[[fr:Champs du profil]]
[[de:Profilfelder]]
[[es:Campos del perfil de usuarios]]

Upload users

2014-01-25T03:51:19Z

Cttxg: /* See also */ Adding MoodleBites YouTube video link

{{Accounts}}
An administrator can upload multiple user accounts via text file in ''Administration > Site administration > Users > Accounts > Upload users''.

There are many robust 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.

Rather than uploading the text file, it can simply dragged from the desktop and dropped into the upload area, as demonstrated in the screencast [http://youtu.be/6E-TQXTkZB0 Drag and drop new users into Moodle 2.3] (by Mary Cooch).

''Tip:'' 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.

[[File:uploadusersnew.png|thumb|center|Initial upload users screen]]

==Upload user process==
Here is an outline of the process:

# Create file for uploading
# Go to ''Settings > Site administration > Users > Accounts > Upload users''
# Add file to upload
# Upload users preview - check settings and default user profile settings
# Upload users preview - click "Upload users"
# Upload users results - shows list of users, exceptions made in upload and summary of number of users
# Upload users results - click "Continue"
# Returns to Upload users screen

==Updating users preview==
There are settings for the kind of Upload user function you want to perform on the "Upload users preview" page.
[[File:Upload users preview 2.0.JPG|thumb|center|Upload users preview in Moodle 2.x]]

===Updating existing accounts===

By default Moodle adds new user accounts and skips existing users lines where the <code>username</code> matches an existing account. Set "Upload Type" to '''Add new and update existing users''', and existing user account will be updated.
*Add all, append number to usernames if needed
*Add new and update existing users
*Update existing users only

'''Warning''': errors updating existing accounts can affect your users badly. Be careful when using the options to update.

===Additional Options===

There are also fields settings to force password change, allow renames, allow deletes, prevent email address duplicates, standardise usernames and select for bulk operations(new users. updated users, all users).

*Standardise usernames - This folds username to lowercase and strips out illegal characters. This is roughly equivalent to:

$username = preg_replace('/[^-\.@_a-z0-9]/', '', $username);

===Set default user values===

You may be able to set default user field values, if the fields were not included in the uploaded file on this page.

==Upload user results ==
After accepting the preview settings by clicking on "Upload users", you should see the the Upload users results screen.
[[File:Upload users results 2.0.JPG|thumb|center|The results screen; everything went well!]]
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.

The screen will summarize how many users were uploaded or updated, indicate the number of weak passwords and the number of errors.

==File formats for upload users file==
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.

'':Tip:'' Avoid special characters in field information like quotes or other commas. Test a file with only one record before a large upload. Remember there are other ways to authenticate users on you site or enroll users in a course.

'':Tip:'' You can use a spread sheet program to create the file with the required columns and fields. Then save the file as "CSV (comma delimited)". These files can be opened with simple text editors for verification.

===Valid upload file for testing===
Here is an example of a simple valid upload file:
(Column headers on the first line of the file are only highlighted in bold in this example to distinguish it from the rest of the of the data/user details)

'''username,password,firstname,lastname,email,course1,group1,cohort1'''
jonest,verysecret,Tom,Jones,jonest@someplace.edu,math102,Section 1,year 3
reznort,somesecret,Trent,Reznor,reznort@someplace.edu,math102,Section 3,year 4

===Fields that can be included===
'':Tip:'' 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. http://demo.moodle.net might be a good place to see if your test file works.

*'''Required fields''':
:<p><code>username,firstname,lastname,email</code>
:Validity checks are performed for:
#<code>username</code> can only contain alphabetical '''lowercase''' letters , numbers, hypen '-', underscore '_', period '.', or at-sign '@'
#<code>email</code> is in the form: ''name@example.com'' .</p>

*'''Password field''': "password" field is optional if "Create password if needed" setting is chosen (default).
**If included, values should meet the requirements for the site's [[Site_policies#Password_policy|Password policy]]. To force password change for a particular user, set the password field to <code>changeme</code>.
**If omitted, a password will be generated for each user (during the next Cron job) and welcome e-mails sent out.
**Note: the text for the welcome e-mail is in the language settings. Please refer to this [https://moodle.org/mod/forum/discuss.php?d=210359&parent=917138 forum thread]for details.

*'''Optional fields''': To provide values other than the default include one or more of these
:<p><code>institution,department,city,country,lang,auth,timezone,idnumber,icq,phone1,phone2,address,url,description,mailformat,maildisplay,htmleditor,autosubscribe</code></p>
*'''[[Additional name fields]]'''
*Country- use a country TWO LETTER CODE
*Some fields have a maximum number of characters that are allowed (notably institution should be '''at most 40 characters''' long). See hints below.
*Maildisplay, htmleditor and autosubscribe can be set from an import screen.

*'''Custom profile field names''': (Optional). xxxxx is the real custom user profile field name (i.e. the unique shortname)
:<p><code>profile_field_xxxxx</code></p>
: Create the custom fields BEFORE importing. Use the standard header. The "shortname" for your custom field is xxxxx (NB the shortname must be all lowercase, otherwise won't be recognised). The first record must include "profile_field_xxxxx".

:'''Example''': To create a custom field "genre", you must write a shortname "genre" in the new field, and write "profile_field_genre" in the header of the .csv file.

: For custom profile fields that are a menu, use the corresponding value (new in Moodle 2.3 onwards).

:'''Example''': A custom field 'Department' with one of three values 'HR', 'Marketing' or 'Training'. Just insert one of those three words (e.g. 'Training') as the value for that field.

*'''Special fields''': Used for changing of usernames or deleting of users
:<p><code>oldusername</code>, <code>deleted</code></p>

*'''Enrolment fields''': (Optional):
:<code>course1,type1,role1,group1,enrolperiod1,enrolstatus1/course2,type2,role2,group2,enrolperiod2/enrolstatus2</code> etc.

:*<code>course</code> is the "shortname" of the course, if present the user will be enrolled in those courses.
:* <code>type</code> refers to the role to be used for associated course enrolment. Value 1 is default course role, 2 is legacy Teacher role and 3 is legacy Non-editing Teacher.
:* You can use role field instead to specify roles directly - use either role short name or id (numeric names of roles are not supported).
:* Users may be also assigned to groups in course (group1 in course1, group2 in course2, etc.).
:* A group is identified by name or id (numeric group names are not supported)
:* You can set the enrolment duration, in days, for each course (<code>enrolperiod1</code> for <code>course1</code>, <code>enrolperiod2</code> for <code>course2</code>, etc.).
{{New features}}
:* You can suspend users from courses by using the ''enrolstatus'' field, where 1 against a user means they are suspended (and leaving blank means they are still enrolled.)

*'''Cohort field''': (Optional):
:<code>cohort1</code>

:Internal cohort id numbers or non-numeric Cohort IDs of existing cohorts must be used; names are not allowed.
*'''mnethostid''' (Optional)

Existing [[MNet]]users can be added to courses, groups or cohorts as below:
#enrolling to courses: username+mnethostid+course required
# adding to group: username+mnethostid+course+group required
#adding to cohort: username+mnethostid+cohort required
#suspending/reviving accounts: username+mnethostid+suspended required
All other operations are ignored. You can not add users, delete them or update them (such as change names or email, profile fields, etc.)

Commas within a field must be encoded as &#44 - the script will decode these back to commas.

For Boolean fields, use <code>0</code> for false and <code>1</code> for true.

To prevent users from receiving a large number of emails from courses or forced subscription forums use the '''maildigest'''. The options for this field are 0 = No digest, 1 = Complete digest and 2 = Digest with just subjects.

==Advanced potentials of Upload user==
===Templates===

''Note: This section needs checking and updating if necessary for Moodle 2.0. Please do so and remove this note when finished.''

The default values are processed as templates in which the following codes are allowed:

* %l - will be replaced by the lastname
* %f - will be replaced by the firstname
* %u - will be replaced by the username
* %% - will be replaced by the %

Between the percent sign (%) and any code letter (l, f or u) the following modifiers are allowed:

* (-) minus sign - the information specified by the code letter will be converted to lowercase
* (+) plus sign - the information specified by the code letter will be converted to UPPERCASE
* (~) tilde sign - the information specified by the code letter will be converted to Title Case
* a decimal number - the information specified by the code letter will be truncated to that many characters

For example, if the firstname is John and the lastname is Doe, the following values will be obtained with the specified templates:

* %l%f = DoeJohn
* %l%1f = DoeJ
* %-l%+f = doeJOHN
* %-f_%-l = john_doe
*<nowiki> http://www.example.com/~%u/</nowiki> results in <nowiki>http://www.example.com/~jdoe/</nowiki> (if the username is jdoe or %-1f%-l)

Template processing is done only on default values, and not on the values retrieved from the CSV file.

In order to create correct Moodle usernames, the username is always converted to lowercase. Moreover, if the "Allow extended characters in usernames" 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.

When the "New username duplicate handling" 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.

===Deleting accounts===

If the <code>deleted</code> field is present, users with value 1 for it will be deleted. In this case, all the fields may be omitted, except for <code>username</code>. After uploading the file, be sure to change the "Upload type" to "Update existing users only" and the "Allow deletes" option to "Yes".

:''Tip:'' A similar field is available for <code>suspended</code>. This enables a user account to be temporarily disabled rather than completely removed.

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:

username,firstname,lastname,deleted
jonest,Tom,Jones,0
reznort,,,1

==Encoding file format==
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.

==Hints==

===Spreadsheet===

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.

Excel translates passwords that begin with - (minus) or + (plus) as zero. Even when saving as .csv and saying "Yes" to "Keep this format, and leave out any incompatible features." Check for this before uploading, as a zero halts the upload process.

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.

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 " " and Replace with "". 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.

===Country===
The country should be written as a two letter code, in capitals. For example, use BE for Belgium or NL for the Netherlands. Using "be" or "nl" as a country code will result in a database error.
:''Tip:'' If you are having trouble working out the two-letter code for a country, you can consult the list of [http://www.iso.org/iso/country_names_and_code_elements country names and code elements] available on the ISO Website. A common error is to use UK for United Kingdom; it should be GB.

===Field size limits===
Some fields have maximum character lengths. 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. Common fields to cause problems are "Institution" which is limited to 40 characters, and "City", also limited (20 characters). The error will be "User not added - error".

===All fields listed here===
:All the fields that are valid are listed below, except for any custom fields you may have created.
firstname, lastname, username, email, city, country, lang, timezone, mailformat, maildisplay, maildigest, htmleditor, ajax, autosubscribe ,institution, department, idnumber, skype , msn, aim, yahoo, icq, phone1, phone2, address, url, description, descriptionformat, password, auth, oldusername , deleted, suspended, course1, course2, course3, course4

===Enroll users to Cohorts (system groups)===
You can enroll users to any Cohort (system level group) by using only the "username" and the "Cohort ID".
Here is a sample CSV file:

'''username,cohort1'''
teacher1,system-teachers
teacher2,system-teachers
teacher3,system-teachers

Make sure you set "Upload type" to "Update existing users only" (So you are not asked to add firstname, lastname and email fields too)

== See also ==
* [http://youtu.be/PFGLZnuu_JI Adding users by using a CSV in Moodle] MoodleBites video on YouTube
*[[Flat file]] enrolment
* [[User profile fields]] for details of how to include data about custom user profile fields in the upload users file
* [[Upload courses]] (new in 2.6)

Using Moodle forum discussions:
*[http://moodle.org/mod/forum/discuss.php?d=36851 Can I auto enroll from Excel?]
*[http://moodle.org/mod/forum/discuss.php?d=97903 Uploading users to custom roles]
*[http://moodle.org/mod/forum/discuss.php?d=181259 User upload option: standardise usernames]
*[http://moodle.org/mod/forum/discuss.php?d=144569 Matriculacion con flat file csv] - discussion in Spanish

[[fr:Importer des utilisateurs]]
[[ja:ユーザのアップロード]]
[[de:Nutzerliste hochladen]]
[[es:Subir usuarios]]

Automated course backup

2014-01-25T03:47:14Z

Cttxg: /* See also */ Adding MoodleBites YouTube video link

{{Backup}}
A site administrator can configure a schedule for automated course backups in ''Settings > Site administration > > Courses > Backups > Automated backup setup''.

Automated course backups runs the same functions as individual [[Course backup|course backups]]. It's a good idea to schedule backups for when your server isn't usually busy. Running the backup tool over all the courses can be processor-intensive, so you shouldn't run it when there are a lot of students trying to access the server. You should always alert users with an announcement on the first page that if they log on during the backup hours they may notice a decrease in performance.

In order to make scheduled backups, you have to set up CRON to run periodically. Please refer to the [[Cron|cron instructions]].

==Setting an automated course backup schedule==

To set the backup schedule:
#Go to ''Settings > Site administration > > Courses > Backups > Automated backup setup''.
#Set backup_auto_active to enabled.
#Select the days of the week to run the backup.
#Set the execution time for the backup process. For most servers, early morning will be the best time. Keep in mind the time zone your server is using.
#Set the "Save to..." path. If you can, choose a backup path on another machine or on a different drive than the one Moodle is on. You don’t want to lose your backups at the same time you lose your Moodle site if the drive fails. If you leave the field blank, then backup zip files will be saved in the backup folder of each course files folder. On a Linux server the path might look like: /home/(your user or domain)/public_html/archive/ or if it's below the publicly accessible folders: /home/(your user or domain)/archive/ if the path is not recognized a red X is shown after saving, otherwise a green check.
#Choose whether to skip the backup of hidden courses or courses which have not been modified within a specified number of days, or not modified since the last backup (new settings in Moodle 2.4 onwards).
#Click the "Save changes" button.

Once you've set up your backup schedule, Moodle will automatically create archives of all the courses on the server at the time you specified. Once the backup is complete, Moodle will send you an email describing the status of the backup.

===Use course names for your backups===

By default, the backups will be named according to the course ID, which is not always easily recognisable. Check the box ''Use course name in backup filename'' in ''Settings > Site Administration > Courses > Backups > Automated backup setup'' to have them saved with the course shortname instead.

==Backups report==

A last execution log of scheduled course backups can be found in ''Settings > Site administration > Reports > Backups''. It displays a list of all course backups made, the time taken to create them, their status (see below), and the next scheduled automated backup execution time.

Clicking on a particular course name will cause a detailed execution log to be displayed, including date, hour and minute when each step of the backup was performed.

[[Image:Reports_Site_Backups_1.jpg]]

===Backup status===

*'''OK''' - The course backup was successfully completed.
*'''Skipped''' - The course was skipped (not backed up) because the course was unavailable to students and had not been changed in the last 31 days. This is not an error, but a feature designed to save process time.
*'''Unfinished''' - The backup was not finished. This might have happened because the job to execute backups ran out of time or resources (e.g., the cron running the backups ran out of time before finishing all the courses waiting). The unfinished jobs should be completed when the next scheduled backups are repeated.
*'''Error''' - There were errors in the backup process for the course, so a backup was not completed. For additional details about the error (1) check the backup log for the affected course (i.e., click the course name in the backups log), or (2) back up the course manually with debugging turned on to see what error message is displayed.

==Course versus site backups==

*Automated course backups are more expensive in terms of time and CPU usage. The recovery time to have your site running again is longer.
*Course backups are useful for obtaining "fresh" copies of courses to be re-used or distributed individually, however they should never be used as a primary backup system (unless your hosting doesn't allow the preferred [[Site backup|site backups]]).

==See also==
* [http://youtu.be/rg6rUuBwITo Moodle 2 Administration Courses ] MoodleBites video on YouTube
* MDL-30725 Automated backups with external storage fill trashdir

Using Moodle forum discussions:
*[http://moodle.org/mod/forum/discuss.php?d=167471 Where is the Moodle 2.0 "Course Backup Filearea"?]
*[http://moodle.org/mod/forum/discuss.php?d=191275 the story of the mysteriously filling up hard disk]

[[Category:Report]]
[[Category:Site administration]]

[[eu:Ikastaroen_segurtasun-kopia_automatikoa]]
[[fr:Sauvegarde (administrateur)]]
[[ja:自動コースバックアップ]]
[[de:Automatische Kurssicherung]]
[[es:Respaldo de curso automatizado]]

Dodawanie nowego kursu

2014-01-25T03:35:56Z

Cttxg: /* Screencasts */ Adding MoodleBites YouTube video link

{{Courses}}

By default a regular teacher can'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.

==Adding a course==
To add a course:
*Go to ''Administration>Site Administration>Courses>Manage courses and categories''
{|
|[[File:26addcourse.png|200px|thumb|Link to add a new course]]
|[[File:26addcourse1.png|200px|thumb|Click New course in the category page on the right]]
|}

*Click on the category where you want your course to be. For more information see [[Course categories|Course categories]]
*Click the "New course" link
*Enter the [[Course settings|course settings]], then click the "Save changes" button.
*On the next screen, choose your students/teachers to assign to the course.

==Deleting a course(s)==

A regular teacher can't delete a course. Administrators and managers (i.e. users with a role for which the capability [[Capabilities/moodle/course:delete|moodle/course:delete]] is allowed) can delete courses. A [[Course creator|Course creator]] can delete courses they have created themselves.

To delete a course (as an administrator or manager):
*Go to ''Administration>Site Administration>Courses>Manage courses and categories''
*Click the course's category and click the course in the screen on the right.
*Click the Delete link.

{|
|[[File:26coursedelete.png|200px|thumb|Deleting a course]]
|}

You can delete multiple courses by:
*Creating a new (temporary) category. You can name it "To be deleted".
*Select and '''move''' the "About to be deleted" courses to that category ("To be deleted").
*Delete the category ("To be deleted") and choose "Delete ALL - cannot be undone".

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 <nowiki>http://yourmoodlesite.net/course/view.php?id=N</nowiki> to <nowiki>http://yourmoodlesite.net/course/delete.php?id=N</nowiki> (replacing 'view' with 'delete').

==Course requests==

[[File:Courserequest.png|thumb|Course request screen]]The course request feature can be enabled by an administrator in ''Settings > Site administration > Courses > Course request''.

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]]).

A 'Request a new course' button will then appear on the 'All courses' page. The All courses page can be accessed via a link in the [[Courses block]].

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.

==Bulk course creation==
{{New features}}
For full details on how to bulk create courses and use course templates, see [[Upload courses]].

# Go to ''Administration > Site Administration > Courses > Upload courses''.
# Upload a CSV file either by dragging and dropping or using the button to select from the File picker.
# Select your import options and click Preview. If the settings are acceptable, click Upload.

==Course templates==
It is possible, from ''Administration>Site Administration>Courses>Upload courses'' to specify a course and settings to use as template for future courses:

===Using an existing course as a template===

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.

''Note that only the content of the course will be restored; not its settings. Settings are added separately.''

====Method 1====

*Create your csv file. See [[Upload courses]] for accepted fields.
*From ''Site administration>Administration>Courses>Upload courses'', add your file.
*Preview it and scroll down to 'Course process'. In the box 'Restore from this course after upload', add the shortname of your template course.
*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.
*Upload your csv file.

{|
|[[File:template1.png|thumb|400px|Adding shortname of template course]]
|
|[[File:26defaultcoursevalues.png|thumb|400|Default course values]]
|}

====Method 2====
*All the settings and the chosen template course can be specified in the csv file you create. Use ''templatecourse'' as the field for your chosen template course, and use the course shortname. See [[Upload courses]] for full list of fields you can include.
*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.

<code bash>
shortname,fullname,category,newsitems,theme,lang,format,enrolment_1,enrolment_1_role,role_student,role_teacher,templatecourse
Knit,Knitting,2,0,afterburner,fr,topics,manual,student,NewKnitter,MasterKnitter,OMT
</code>
*Go to Administration>Site administration>Courses>Upload courses and add your csv file.

===Using a backup course as a template===
It is possible during the process of creating courses with a csv file in ''Site administration>Administration>Courses>Upload courses'' to specify and upload a backup file to be used as a template.

*Create your csv file. See [[Upload courses]] for accepted fields.
*From ''Site administration>Administration>Courses>Upload courses'', add your file.
*Preview it and scroll down to 'Course process'. In the box 'Restore from this file after upload', add the backup file you wish to use as the template.
*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' section.
*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.
*Upload your csv file.
{|
|[[File:template2.png|thumb|400px|Uploading a template course]]
|}

==See also==

===Screencasts===
* [http://youtu.be/MzK2jb-9SwE Bulk course creation]
* [http://youtu.be/vOm1NAknuvk Creating a Course and Course Settings] MoodleBites video on YouTube
* [http://youtu.be/rg6rUuBwITo Moodle 2 Administration Courses] MoodleBites video on YouTube

===Forum discussions===
*Using Moodle [http://moodle.org/mod/forum/discuss.php?d=83830 Hide Courses from some users or students] forum discussion

[[de:Kurs anlegen]]
[[es:Añadiendo un nuevo curso]]
[[eu:Ikastaroak_%28Kudeatzaileak%29]]

Course backup

2014-01-25T03:31:13Z

Cttxg: /* See also */ Adding MoodleBites YouTube video link

{{Backup}}
A course can be saved with some or all of its parts by using the course backup. Typically, the site administrator will set a schedule of [[Automated course backup|automated course backups]] for the whole site. A teacher with editing privileges can create a backup or download an existing backup for safe keeping, or for use on another Moodle site.

==Backing up a course==

To backup a course

* Go to ''Administration > Course administration > Backup''
* Initial settings - Select activities, blocks, filters and other items as required then click the Next button. Users with appropriate permissions, such as administrators and managers, can choose whether to [[Backup of user data|include users]], anonymize user information, or include user role assignments, user files, comments, user completion details, course logs and grade history in the backup.
* Schema settings - Select/deselect specific items to include in backup, then click the Next button.

* If desired, select specific types of activity to be backed up by clicking the link 'Show type options' {{New features}}

{|
|[[File:26backuprestore1.png|thumb|Back up screen with option to select all or none]]
|
|[[File:26backuprestore2.png|thumb|Back up screen with option to select activity types]]
|}

* Confirmation and review - Check that everything is as required, using the Previous button if necessary, otherwise click the 'Perform backup' button
* Complete - Click the Continue button

A backup file (with distinctive .mbz extension to avoid confusion with .zip files) is then saved in the course backup area. Backup file names are of the form ''backup-moodle2-course-coursename-date-hour.mbz'', ending in ''-nu.mbz'' when backed up with no users and ''-an.mbz'' with anonymized names.

==Anonymizing user information==

Anonymize user information is a backup feature which "protects user identities" by making each user anonymous. If this box is checked in the backup initial settings, Moodle will substitute aliases for real names, substituting @doesntexist.com email addresses and so forth. For example "Max Manager" might become "anonfirstname4 anonlastname4".

==Backup and restore from 1.9 to 2==

Courses created in 1.9 can be backed up and then restored into a 2.1 Moodle or later but blocks are not currently restored and nor is user data (such as forum posts, grades, submissions etc).

==Backup and restore of assignments from Moodle 2.2 and older==

The assignment activity module was completely rewritten in Moodle 2.3. Thus, assignments from Moodle 2.2 and older (e.g. from Moodle 1.9) need to be upgraded in order to continue being usable. See the section 'Restoring course backups from Moodle 2.2 and older' in [[Assignment upgrade tool]] for details of what to do.

==Tips and tricks==
* Lose content after a restore in Moodle 2.0 ? Do you see topic headings that say "Orphaned activities"? Solution: Go to course settings and increase the number of topic sections and things will return to normal.

==Creative uses==
The backup and restore processes can offer the teacher and administrators many creative solutions.
*Duplicating courses or specific activities in one course to another course (similar to Import)
*Updating a production Moodle site course, with material from a localhost site course
*Transferring a course to a new Moodle site.
*In earlier versions of Moodle, a way of rolling a course forward without past student activity
*Creating a blank activity, save just that activity and then restore it to the course or another course one or more times.

==General backup defaults==

Default settings for course backups can be set by a site administrator in ''Settings > Site administration > Courses > Backups > General backup defaults''.

Selected settings may be locked, so that they cannot be changed when creating a course backup.

By selecting a time in the "Keep logs for.." dropdown, it is possible to specify how long backup logs information is kept before being deleted. As this information may be very large, it is recommended the length of time chosen be quite short.

==Course backup capabilities==

*[[Capabilities/moodle/backup:anonymise|Anonymise user data on backup]]
*[[Capabilities/moodle/backup:backupcourse|Backup courses]]
*[[Capabilities/moodle/backup:backupsection|Backup sections]]
*[[Capabilities/moodle/backup:backuptargethub|Backup for hub]]
*[[Capabilities/moodle/backup:backuptargetimport|Backup for import]]
*[[Capabilities/moodle/backup:configure|Configure backup options]]
*[[Capabilities/moodle/backup:downloadfile|Download files from backup areas]]
*[[Capabilities/moodle/backup:userinfo|Backup user data]]

==See also==
*[[Course restore]]
*[[Backup of user data]]
*[[Activity backup]]
* [http://youtu.be/rg6rUuBwITo Moodle 2 Administration Courses] MoodleBites video on YouTube

[[de:Kurssicherung]]
[[es:Respaldo del curso]]
[[eu:Ikastaroaren_Segurtasun-kopia]]
[[fr:Sauvegarde de cours]]
[[ja:コースバックアップ]]

Course settings

2014-01-25T03:29:31Z

Cttxg: /* See also */

{{Courses}}
A teacher, or other user with the [[Capabilities/moodle/course:update|update course settings capability]], can change course settings in ''Administration > Course administration > Edit settings''.

==General==
{|
|[[File:generalcourse25.png|thumb|General settings,expanded by default]]
|}

===Course full name===

This is the name of the course. It is displayed as a link on course lists on the [[Front page]] and on [[My home]] and in reports. It is also used in the browser title bar when the course is viewed.

The capability [[Capabilities/moodle/course:changefullname|moodle/course:changefullname]] controls whether a user can edit the course full name.

===Short name===

Many institutions have a shorthand way of referring to a course, such as BP102 or COMMS. Even if you do not already have such a name for your course, make one up here. It will be used in several places where the long name is not appropriate, such as the Navigation block.

The capability [[Capabilities/moodle/course:changeshortname|moodle/course:changeshortname]] controls whether a user can edit the short name field.

By default, only course full names are displayed in the list of courses. However an administrator can enable short names to be displayed too if required by ticking the checkbox in ''Administration > Site administration > Appearance > Courses''.

=== Course category===

The site administrator may have created course categories to help teachers and students find their courses easily. Course categories may be reflected in the [[Navigation block]].

The capability [[Capabilities/moodle/course:changecategory|moodle/course:changecategory]] controls whether a user can edit the course category.

===Course start date===

This setting affects the display of logs and the weekly format topic dates.

If you use the "Weekly" course format, the start date will appear in the first section of the course. For example selecting 27 July, will display "27 July - 2 August" in the first section (when default display is selected for that section).

This setting will have an effect on the display of logs. This will be the earliest possible date the log activity will display.

This setting will '''not''' affect courses using the 'social' or 'topics' formats.

:''TIP:'' If your institution runs on a weekly schedule, you may want to consider setting the start date for courses on the first day of the week, like a Monday. Please note that the 'first day of the week' is set by the [https://docs.moodle.org/dev/Translation_langconfig langconfig file] of your [[Language]], and might be different from the default Monday of the English language pack.

:''TIP:'' In general, if your course does not have a real starting date then set the date to yesterday and use the availability setting to reveal the course to students.

:''TIP:'' See self enrolment course settings to prevent students from entering the course before a certain date/time.

===Visible===

Here you can "hide" your course completely. It will not appear on any course listings, except for managers, course creators, teachers and any other users with the [[Capabilities/moodle/course:viewhiddencourses|view hidden courses capability]]. Even if students try to access the course URL directly, they will not be allowed to enter.

The [[Capabilities/moodle/course:visibility|hide/show courses capability]] controls whether a user can hide a course.

Note: In earlier versions of Moodle, this setting was named 'Course availability'.

=== Course ID number===

The ID number is an alphanumeric field. It has several potential uses. Generally, it is not displayed to students. However, it can be used to match this course against an external system's ID, as your course catalogue ID or can be used in the certificate module as a printed field.

The capability [[Capabilities/moodle/course:changeidnumber|moodle/course:changeidnumber]] controls whether a user can edit the ID number.

==Description==
{|
|[[File:descriptioncourse25.png|thumb|Description settings expanded by default]]
|}

===Course summary===

The summary appears on the course listings page. This field is searched when searching for a course and also appears in the Course/Site description block.

The capability [[Capabilities/moodle/course:changesummary|moodle/course:changesummary]] controls whether a user can edit the course summary.

===Course summary files===

An image (and if allowed by the administrator, other file types) may be attached to the course summary. They will be accessible by anyone from outside of the course just like the course name and/or summary. Only users with [[Capabilities/moodle/course:changesummary| moodle/course:changesummary capability]] are able to upload/change course summary files.
''Note that if this is not allowed by the administrator, then no box will appear to upload course summary files''.

By default, only jpg, gif and png file types are allowed as course summary files. An administrator can change the allowed file types in ''Administration > Site administration > Appearance > Courses''.

==Course format==

(These settings are collapsed by default.)
{|
|[[File:coursefomat25.png|thumb|Course format settings expanded]]
|}

===Format===

See [[Course formats]]

===Number of sections===

This setting is only used by the 'weekly' and 'topics' course formats. In the 'weekly' format, it specifies the number of weeks that the course will run for, starting from the course starting date. In the 'topics' format, it specifies the number of topics in the course. Both of these translate to the number of "boxes" down the middle of the course page.

If the number of weeks/topics is changed for an existing course so that the number is less than the number of course sections containing activities (for example the course contains activities in 3 sections and the number or weeks/topics is set to 2) then when editing is turned on section(s) at the bottom of the course page will be shown with the title 'Orphaned activities'.

The number of weeks/topics may be set to 0, so that only the top general section is displayed on the course page and there are no numbered sections.

By default, the maximum number of weeks/topics is 52, but an administrator can set a different maximum number which will apply to all courses on the site (see below).

===Hidden sections===

This option allows you to decide how the hidden sections in your course are displayed to students. By default, a small area is shown (in collapsed form, usually grey) to indicate where the hidden section is, though they still cannot actually see the hidden activities and texts. This is particularly useful in the Weekly format, so that non-class weeks are clear, or if you have quizzes you don't want your students to see.

:''TIP:'' If you choose, these non-available items can be completely hidden, so that students do not even know that sections or an activity in the course are hidden.

===Course layout===

The Course layout setting determines whether the whole course is displayed on one page or split over several pages. The setting currently applies to the topics and weekly core course formats and contributed collapsed topics course format only.

Teachers choose from the dropdown whether they wish to "show all sections on one page" in the familiar scrolling format, or "show one section per page".

If one section per page is selected, the course page is abbreviated to a list of links to individual sections. If an individual section is shown, next and previous sections may be accessed via links above and below the section.

{|
| [[File:one section per page course format.png|thumb|Course page for course using one section per page course layout]]
| [[File:Single_section_page.png|thumb|Individual section of a course using one section per page course layout]]
|}

Visit the School demo site course [http://school.demo.moodle.net/course/view.php?id=96 The Types of Sport] to see the "Show one section per page" course layout in action!

For further details plus screenshots, see blog post [http://www.somerandomthoughts.com/blog/2012/05/08/moodle-2-3-section-per-page/ Moodle 2.3 – Section per page] by Gavin Henrick.

==Appearance==

(These settings are collapsed by default.)

{|
|[[File:appearancecourse252.png|thumb|Appearance settings expanded]]
|}

===Force theme===

If the site administrator has allowed the teacher to set a course [[Themes|theme]], this pull down menu will appear with a list of themes on the site. Teachers can use this to choose a different look for the course from the rest of the Moodle site.

=== Force language===

If you force a language in a course, the interface of Moodle in this course will be in this particular language, even if a student has selected a different preferred language in his/her personal profile.

===News items to show===

How many news items should show the [[Latest news block]]. Set it to 0 and Latest news block will not appear.

The Latest News block relies on the use of the associated News Forum. News posted in other forums do not display in the latest News block

===Show gradebook to students===

Here you can decide whether to allow students to see the link to [[Grades|grades]] in the Administration block. If your course doesn't use graded activities, it makes sense to disable this. If grades are used and this link is disabled, students can still see their grade from the actual activity itself, such as an [[Assignment|assignment]]

===Show activity reports===

Here you can decide whether to show students their [[Activity_report#Individual_Activity_Report|activity reports]]. Doing so places a load on the server however, which is why the setting is disabled by default.

==Files and uploads==

(These settings are collapsed by default.)

===Maximum upload size===

Here you can decide the largest size of file that students can upload to a course. The site administrator can determine [[Site_policies#Maximum_uploaded_file_sizefile |sizes available]] for the teacher to select.

Editing teachers or other users may be allowed to upload files larger than the maximum size by giving them the capability [[Capabilities/moodle/course:ignorefilesizelimits|moodle/course:ignorefilesizelimits]]

==Completion tracking==

(These settings are collapsed by default.)

Completion tracking must be enabled for [[Activity completion]]. [[Course completion]] criteria may also be based upon Activity completion values found in the activity's settings.

==Guest access==

(These settings are collapsed by default.)
{|
|[[File:guestaccess25.png|thumb|Guest access settings expanded]]
|}
Here you can decide whether to allow logged in users to access the course as a guest, and whether or not they need to enter a password. See [[Guest role|Guest role]] for more information.

==Groups==

(These settings are collapsed by default.)
{|
|[[File:coursegroups25.png|thumb|Groups settings expanded]]
|}

===Group mode===

Here you can define the [[Groups|group mode]] at the course level by a pull down menu. "[[Groups#No_groups|No groups]]", "[[Groups#Separate_groups|Separate groups]]" and "[[Groups#Visible_groups|Visible groups]]" are the choices. The selected setting will be the default group mode for all activities defined within that course. The group setting can affect what users see in the [[Participants]] list and who they can interact with in activities.

===Force===

If the group mode is "forced" at a course-level, then this particular group mode will be applied to every activity in that course. This will override any activities that may have a special group setting.

===Default grouping===

If [[Groupings|groupings]] are enabled, a default grouping for course activities and resources may be set.

==Role renaming==

(These settings are collapsed by default.)
{|
|[[File:rolerenaming.png|thumb|Role renaming settings expanded]]
|}
You can rename the [[Roles|roles]] used in your course. For example, you may wish to rename the [[Teacher role]] as "Facilitator", "Tutor" or "Guide". These new role names will appear within the course. For example on the [[Participants|participants]] and the override permissions pages.

Please note that the site administrator or a [[Manager |course manager]] may have changed the names or added new roles. These names will appear and the teacher may rename them.

== Site administration settings==

An administrator can set course default settings in ''Administration > Site administration > Courses > Course default settings''.

The maximum number of weeks/topics may be set for all courses on the site. The default value is 52.

==Preventing teachers from editing course settings==

Any/all of the following fields - course full name, short name, ID number and category, summary - may be locked to prevent teachers from editing them. To do so:

#Access ''Site Administration > Users > Permissions > Define roles''.
#Click the edit icon opposite the teacher role.
#Change any/all of the capabilities [[Capabilities/moodle/course:changefullname|moodle/course:changefullname]], [[Capabilities/moodle/course:changeshortname|moodle/course:changeshortname]], [[Capabilities/moodle/course:changeidnumber|moodle/course:changeidnumber]], [[Capabilities/moodle/course:changecategory|moodle/course:changecategory]], [[Capabilities/moodle/course:changesummary|moodle/course:changesummary]] from allow to not set.
#Click the "Save changes" button at the bottom of the page.

==See also==
* [http://youtu.be/vOm1NAknuvk Creating a Course and Course Settings] MoodleBites video on YouTube
* [http://youtu.be/rg6rUuBwITo Moodle 2 Administration Courses] MoodleBites video on YouTube

[[de:Kurseinstellungen]]
[[es:Configuraciones del curso]]
[[eu:Ikastaroaren_ezarpenak]]
[[fr:Paramètres du cours]]
[[ja:コース設定]]

Course settings

2014-01-25T03:28:52Z

Cttxg: /* See also */ Adding MoodleBites YouTube video link

{{Courses}}
A teacher, or other user with the [[Capabilities/moodle/course:update|update course settings capability]], can change course settings in ''Administration > Course administration > Edit settings''.

==General==
{|
|[[File:generalcourse25.png|thumb|General settings,expanded by default]]
|}

===Course full name===

This is the name of the course. It is displayed as a link on course lists on the [[Front page]] and on [[My home]] and in reports. It is also used in the browser title bar when the course is viewed.

The capability [[Capabilities/moodle/course:changefullname|moodle/course:changefullname]] controls whether a user can edit the course full name.

===Short name===

Many institutions have a shorthand way of referring to a course, such as BP102 or COMMS. Even if you do not already have such a name for your course, make one up here. It will be used in several places where the long name is not appropriate, such as the Navigation block.

The capability [[Capabilities/moodle/course:changeshortname|moodle/course:changeshortname]] controls whether a user can edit the short name field.

By default, only course full names are displayed in the list of courses. However an administrator can enable short names to be displayed too if required by ticking the checkbox in ''Administration > Site administration > Appearance > Courses''.

=== Course category===

The site administrator may have created course categories to help teachers and students find their courses easily. Course categories may be reflected in the [[Navigation block]].

The capability [[Capabilities/moodle/course:changecategory|moodle/course:changecategory]] controls whether a user can edit the course category.

===Course start date===

This setting affects the display of logs and the weekly format topic dates.

If you use the "Weekly" course format, the start date will appear in the first section of the course. For example selecting 27 July, will display "27 July - 2 August" in the first section (when default display is selected for that section).

This setting will have an effect on the display of logs. This will be the earliest possible date the log activity will display.

This setting will '''not''' affect courses using the 'social' or 'topics' formats.

:''TIP:'' If your institution runs on a weekly schedule, you may want to consider setting the start date for courses on the first day of the week, like a Monday. Please note that the 'first day of the week' is set by the [https://docs.moodle.org/dev/Translation_langconfig langconfig file] of your [[Language]], and might be different from the default Monday of the English language pack.

:''TIP:'' In general, if your course does not have a real starting date then set the date to yesterday and use the availability setting to reveal the course to students.

:''TIP:'' See self enrolment course settings to prevent students from entering the course before a certain date/time.

===Visible===

Here you can "hide" your course completely. It will not appear on any course listings, except for managers, course creators, teachers and any other users with the [[Capabilities/moodle/course:viewhiddencourses|view hidden courses capability]]. Even if students try to access the course URL directly, they will not be allowed to enter.

The [[Capabilities/moodle/course:visibility|hide/show courses capability]] controls whether a user can hide a course.

Note: In earlier versions of Moodle, this setting was named 'Course availability'.

=== Course ID number===

The ID number is an alphanumeric field. It has several potential uses. Generally, it is not displayed to students. However, it can be used to match this course against an external system's ID, as your course catalogue ID or can be used in the certificate module as a printed field.

The capability [[Capabilities/moodle/course:changeidnumber|moodle/course:changeidnumber]] controls whether a user can edit the ID number.

==Description==
{|
|[[File:descriptioncourse25.png|thumb|Description settings expanded by default]]
|}

===Course summary===

The summary appears on the course listings page. This field is searched when searching for a course and also appears in the Course/Site description block.

The capability [[Capabilities/moodle/course:changesummary|moodle/course:changesummary]] controls whether a user can edit the course summary.

===Course summary files===

An image (and if allowed by the administrator, other file types) may be attached to the course summary. They will be accessible by anyone from outside of the course just like the course name and/or summary. Only users with [[Capabilities/moodle/course:changesummary| moodle/course:changesummary capability]] are able to upload/change course summary files.
''Note that if this is not allowed by the administrator, then no box will appear to upload course summary files''.

By default, only jpg, gif and png file types are allowed as course summary files. An administrator can change the allowed file types in ''Administration > Site administration > Appearance > Courses''.

==Course format==

(These settings are collapsed by default.)
{|
|[[File:coursefomat25.png|thumb|Course format settings expanded]]
|}

===Format===

See [[Course formats]]

===Number of sections===

This setting is only used by the 'weekly' and 'topics' course formats. In the 'weekly' format, it specifies the number of weeks that the course will run for, starting from the course starting date. In the 'topics' format, it specifies the number of topics in the course. Both of these translate to the number of "boxes" down the middle of the course page.

If the number of weeks/topics is changed for an existing course so that the number is less than the number of course sections containing activities (for example the course contains activities in 3 sections and the number or weeks/topics is set to 2) then when editing is turned on section(s) at the bottom of the course page will be shown with the title 'Orphaned activities'.

The number of weeks/topics may be set to 0, so that only the top general section is displayed on the course page and there are no numbered sections.

By default, the maximum number of weeks/topics is 52, but an administrator can set a different maximum number which will apply to all courses on the site (see below).

===Hidden sections===

This option allows you to decide how the hidden sections in your course are displayed to students. By default, a small area is shown (in collapsed form, usually grey) to indicate where the hidden section is, though they still cannot actually see the hidden activities and texts. This is particularly useful in the Weekly format, so that non-class weeks are clear, or if you have quizzes you don't want your students to see.

:''TIP:'' If you choose, these non-available items can be completely hidden, so that students do not even know that sections or an activity in the course are hidden.

===Course layout===

The Course layout setting determines whether the whole course is displayed on one page or split over several pages. The setting currently applies to the topics and weekly core course formats and contributed collapsed topics course format only.

Teachers choose from the dropdown whether they wish to "show all sections on one page" in the familiar scrolling format, or "show one section per page".

If one section per page is selected, the course page is abbreviated to a list of links to individual sections. If an individual section is shown, next and previous sections may be accessed via links above and below the section.

{|
| [[File:one section per page course format.png|thumb|Course page for course using one section per page course layout]]
| [[File:Single_section_page.png|thumb|Individual section of a course using one section per page course layout]]
|}

Visit the School demo site course [http://school.demo.moodle.net/course/view.php?id=96 The Types of Sport] to see the "Show one section per page" course layout in action!

For further details plus screenshots, see blog post [http://www.somerandomthoughts.com/blog/2012/05/08/moodle-2-3-section-per-page/ Moodle 2.3 – Section per page] by Gavin Henrick.

==Appearance==

(These settings are collapsed by default.)

{|
|[[File:appearancecourse252.png|thumb|Appearance settings expanded]]
|}

===Force theme===

If the site administrator has allowed the teacher to set a course [[Themes|theme]], this pull down menu will appear with a list of themes on the site. Teachers can use this to choose a different look for the course from the rest of the Moodle site.

=== Force language===

If you force a language in a course, the interface of Moodle in this course will be in this particular language, even if a student has selected a different preferred language in his/her personal profile.

===News items to show===

How many news items should show the [[Latest news block]]. Set it to 0 and Latest news block will not appear.

The Latest News block relies on the use of the associated News Forum. News posted in other forums do not display in the latest News block

===Show gradebook to students===

Here you can decide whether to allow students to see the link to [[Grades|grades]] in the Administration block. If your course doesn't use graded activities, it makes sense to disable this. If grades are used and this link is disabled, students can still see their grade from the actual activity itself, such as an [[Assignment|assignment]]

===Show activity reports===

Here you can decide whether to show students their [[Activity_report#Individual_Activity_Report|activity reports]]. Doing so places a load on the server however, which is why the setting is disabled by default.

==Files and uploads==

(These settings are collapsed by default.)

===Maximum upload size===

Here you can decide the largest size of file that students can upload to a course. The site administrator can determine [[Site_policies#Maximum_uploaded_file_sizefile |sizes available]] for the teacher to select.

Editing teachers or other users may be allowed to upload files larger than the maximum size by giving them the capability [[Capabilities/moodle/course:ignorefilesizelimits|moodle/course:ignorefilesizelimits]]

==Completion tracking==

(These settings are collapsed by default.)

Completion tracking must be enabled for [[Activity completion]]. [[Course completion]] criteria may also be based upon Activity completion values found in the activity's settings.

==Guest access==

(These settings are collapsed by default.)
{|
|[[File:guestaccess25.png|thumb|Guest access settings expanded]]
|}
Here you can decide whether to allow logged in users to access the course as a guest, and whether or not they need to enter a password. See [[Guest role|Guest role]] for more information.

==Groups==

(These settings are collapsed by default.)
{|
|[[File:coursegroups25.png|thumb|Groups settings expanded]]
|}

===Group mode===

Here you can define the [[Groups|group mode]] at the course level by a pull down menu. "[[Groups#No_groups|No groups]]", "[[Groups#Separate_groups|Separate groups]]" and "[[Groups#Visible_groups|Visible groups]]" are the choices. The selected setting will be the default group mode for all activities defined within that course. The group setting can affect what users see in the [[Participants]] list and who they can interact with in activities.

===Force===

If the group mode is "forced" at a course-level, then this particular group mode will be applied to every activity in that course. This will override any activities that may have a special group setting.

===Default grouping===

If [[Groupings|groupings]] are enabled, a default grouping for course activities and resources may be set.

==Role renaming==

(These settings are collapsed by default.)
{|
|[[File:rolerenaming.png|thumb|Role renaming settings expanded]]
|}
You can rename the [[Roles|roles]] used in your course. For example, you may wish to rename the [[Teacher role]] as "Facilitator", "Tutor" or "Guide". These new role names will appear within the course. For example on the [[Participants|participants]] and the override permissions pages.

Please note that the site administrator or a [[Manager |course manager]] may have changed the names or added new roles. These names will appear and the teacher may rename them.

== Site administration settings==

An administrator can set course default settings in ''Administration > Site administration > Courses > Course default settings''.

The maximum number of weeks/topics may be set for all courses on the site. The default value is 52.

==Preventing teachers from editing course settings==

Any/all of the following fields - course full name, short name, ID number and category, summary - may be locked to prevent teachers from editing them. To do so:

#Access ''Site Administration > Users > Permissions > Define roles''.
#Click the edit icon opposite the teacher role.
#Change any/all of the capabilities [[Capabilities/moodle/course:changefullname|moodle/course:changefullname]], [[Capabilities/moodle/course:changeshortname|moodle/course:changeshortname]], [[Capabilities/moodle/course:changeidnumber|moodle/course:changeidnumber]], [[Capabilities/moodle/course:changecategory|moodle/course:changecategory]], [[Capabilities/moodle/course:changesummary|moodle/course:changesummary]] from allow to not set.
#Click the "Save changes" button at the bottom of the page.

==See also==
* [http://youtu.be/vOm1NAknuvk Creating a Course and Course Settings] MoodleBites video on YouTube
* [http://youtu.be/rg6rUuBwITo Moodle 2 Administration Courses ] MoodleBites video on YouTube

[[de:Kurseinstellungen]]
[[es:Configuraciones del curso]]
[[eu:Ikastaroaren_ezarpenak]]
[[fr:Paramètres du cours]]
[[ja:コース設定]]

Course settings

2014-01-25T03:12:27Z

Cttxg: /* See also */ Adding MoodleBites YouTube video link

{{Courses}}
A teacher, or other user with the [[Capabilities/moodle/course:update|update course settings capability]], can change course settings in ''Administration > Course administration > Edit settings''.

==General==
{|
|[[File:generalcourse25.png|thumb|General settings,expanded by default]]
|}

===Course full name===

This is the name of the course. It is displayed as a link on course lists on the [[Front page]] and on [[My home]] and in reports. It is also used in the browser title bar when the course is viewed.

The capability [[Capabilities/moodle/course:changefullname|moodle/course:changefullname]] controls whether a user can edit the course full name.

===Short name===

Many institutions have a shorthand way of referring to a course, such as BP102 or COMMS. Even if you do not already have such a name for your course, make one up here. It will be used in several places where the long name is not appropriate, such as the Navigation block.

The capability [[Capabilities/moodle/course:changeshortname|moodle/course:changeshortname]] controls whether a user can edit the short name field.

By default, only course full names are displayed in the list of courses. However an administrator can enable short names to be displayed too if required by ticking the checkbox in ''Administration > Site administration > Appearance > Courses''.

=== Course category===

The site administrator may have created course categories to help teachers and students find their courses easily. Course categories may be reflected in the [[Navigation block]].

The capability [[Capabilities/moodle/course:changecategory|moodle/course:changecategory]] controls whether a user can edit the course category.

===Course start date===

This setting affects the display of logs and the weekly format topic dates.

If you use the "Weekly" course format, the start date will appear in the first section of the course. For example selecting 27 July, will display "27 July - 2 August" in the first section (when default display is selected for that section).

This setting will have an effect on the display of logs. This will be the earliest possible date the log activity will display.

This setting will '''not''' affect courses using the 'social' or 'topics' formats.

:''TIP:'' If your institution runs on a weekly schedule, you may want to consider setting the start date for courses on the first day of the week, like a Monday. Please note that the 'first day of the week' is set by the [https://docs.moodle.org/dev/Translation_langconfig langconfig file] of your [[Language]], and might be different from the default Monday of the English language pack.

:''TIP:'' In general, if your course does not have a real starting date then set the date to yesterday and use the availability setting to reveal the course to students.

:''TIP:'' See self enrolment course settings to prevent students from entering the course before a certain date/time.

===Visible===

Here you can "hide" your course completely. It will not appear on any course listings, except for managers, course creators, teachers and any other users with the [[Capabilities/moodle/course:viewhiddencourses|view hidden courses capability]]. Even if students try to access the course URL directly, they will not be allowed to enter.

The [[Capabilities/moodle/course:visibility|hide/show courses capability]] controls whether a user can hide a course.

Note: In earlier versions of Moodle, this setting was named 'Course availability'.

=== Course ID number===

The ID number is an alphanumeric field. It has several potential uses. Generally, it is not displayed to students. However, it can be used to match this course against an external system's ID, as your course catalogue ID or can be used in the certificate module as a printed field.

The capability [[Capabilities/moodle/course:changeidnumber|moodle/course:changeidnumber]] controls whether a user can edit the ID number.

==Description==
{|
|[[File:descriptioncourse25.png|thumb|Description settings expanded by default]]
|}

===Course summary===

The summary appears on the course listings page. This field is searched when searching for a course and also appears in the Course/Site description block.

The capability [[Capabilities/moodle/course:changesummary|moodle/course:changesummary]] controls whether a user can edit the course summary.

===Course summary files===

An image (and if allowed by the administrator, other file types) may be attached to the course summary. They will be accessible by anyone from outside of the course just like the course name and/or summary. Only users with [[Capabilities/moodle/course:changesummary| moodle/course:changesummary capability]] are able to upload/change course summary files.
''Note that if this is not allowed by the administrator, then no box will appear to upload course summary files''.

By default, only jpg, gif and png file types are allowed as course summary files. An administrator can change the allowed file types in ''Administration > Site administration > Appearance > Courses''.

==Course format==

(These settings are collapsed by default.)
{|
|[[File:coursefomat25.png|thumb|Course format settings expanded]]
|}

===Format===

See [[Course formats]]

===Number of sections===

This setting is only used by the 'weekly' and 'topics' course formats. In the 'weekly' format, it specifies the number of weeks that the course will run for, starting from the course starting date. In the 'topics' format, it specifies the number of topics in the course. Both of these translate to the number of "boxes" down the middle of the course page.

If the number of weeks/topics is changed for an existing course so that the number is less than the number of course sections containing activities (for example the course contains activities in 3 sections and the number or weeks/topics is set to 2) then when editing is turned on section(s) at the bottom of the course page will be shown with the title 'Orphaned activities'.

The number of weeks/topics may be set to 0, so that only the top general section is displayed on the course page and there are no numbered sections.

By default, the maximum number of weeks/topics is 52, but an administrator can set a different maximum number which will apply to all courses on the site (see below).

===Hidden sections===

This option allows you to decide how the hidden sections in your course are displayed to students. By default, a small area is shown (in collapsed form, usually grey) to indicate where the hidden section is, though they still cannot actually see the hidden activities and texts. This is particularly useful in the Weekly format, so that non-class weeks are clear, or if you have quizzes you don't want your students to see.

:''TIP:'' If you choose, these non-available items can be completely hidden, so that students do not even know that sections or an activity in the course are hidden.

===Course layout===

The Course layout setting determines whether the whole course is displayed on one page or split over several pages. The setting currently applies to the topics and weekly core course formats and contributed collapsed topics course format only.

Teachers choose from the dropdown whether they wish to "show all sections on one page" in the familiar scrolling format, or "show one section per page".

If one section per page is selected, the course page is abbreviated to a list of links to individual sections. If an individual section is shown, next and previous sections may be accessed via links above and below the section.

{|
| [[File:one section per page course format.png|thumb|Course page for course using one section per page course layout]]
| [[File:Single_section_page.png|thumb|Individual section of a course using one section per page course layout]]
|}

Visit the School demo site course [http://school.demo.moodle.net/course/view.php?id=96 The Types of Sport] to see the "Show one section per page" course layout in action!

For further details plus screenshots, see blog post [http://www.somerandomthoughts.com/blog/2012/05/08/moodle-2-3-section-per-page/ Moodle 2.3 – Section per page] by Gavin Henrick.

==Appearance==

(These settings are collapsed by default.)

{|
|[[File:appearancecourse252.png|thumb|Appearance settings expanded]]
|}

===Force theme===

If the site administrator has allowed the teacher to set a course [[Themes|theme]], this pull down menu will appear with a list of themes on the site. Teachers can use this to choose a different look for the course from the rest of the Moodle site.

=== Force language===

If you force a language in a course, the interface of Moodle in this course will be in this particular language, even if a student has selected a different preferred language in his/her personal profile.

===News items to show===

How many news items should show the [[Latest news block]]. Set it to 0 and Latest news block will not appear.

The Latest News block relies on the use of the associated News Forum. News posted in other forums do not display in the latest News block

===Show gradebook to students===

Here you can decide whether to allow students to see the link to [[Grades|grades]] in the Administration block. If your course doesn't use graded activities, it makes sense to disable this. If grades are used and this link is disabled, students can still see their grade from the actual activity itself, such as an [[Assignment|assignment]]

===Show activity reports===

Here you can decide whether to show students their [[Activity_report#Individual_Activity_Report|activity reports]]. Doing so places a load on the server however, which is why the setting is disabled by default.

==Files and uploads==

(These settings are collapsed by default.)

===Maximum upload size===

Here you can decide the largest size of file that students can upload to a course. The site administrator can determine [[Site_policies#Maximum_uploaded_file_sizefile |sizes available]] for the teacher to select.

Editing teachers or other users may be allowed to upload files larger than the maximum size by giving them the capability [[Capabilities/moodle/course:ignorefilesizelimits|moodle/course:ignorefilesizelimits]]

==Completion tracking==

(These settings are collapsed by default.)

Completion tracking must be enabled for [[Activity completion]]. [[Course completion]] criteria may also be based upon Activity completion values found in the activity's settings.

==Guest access==

(These settings are collapsed by default.)
{|
|[[File:guestaccess25.png|thumb|Guest access settings expanded]]
|}
Here you can decide whether to allow logged in users to access the course as a guest, and whether or not they need to enter a password. See [[Guest role|Guest role]] for more information.

==Groups==

(These settings are collapsed by default.)
{|
|[[File:coursegroups25.png|thumb|Groups settings expanded]]
|}

===Group mode===

Here you can define the [[Groups|group mode]] at the course level by a pull down menu. "[[Groups#No_groups|No groups]]", "[[Groups#Separate_groups|Separate groups]]" and "[[Groups#Visible_groups|Visible groups]]" are the choices. The selected setting will be the default group mode for all activities defined within that course. The group setting can affect what users see in the [[Participants]] list and who they can interact with in activities.

===Force===

If the group mode is "forced" at a course-level, then this particular group mode will be applied to every activity in that course. This will override any activities that may have a special group setting.

===Default grouping===

If [[Groupings|groupings]] are enabled, a default grouping for course activities and resources may be set.

==Role renaming==

(These settings are collapsed by default.)
{|
|[[File:rolerenaming.png|thumb|Role renaming settings expanded]]
|}
You can rename the [[Roles|roles]] used in your course. For example, you may wish to rename the [[Teacher role]] as "Facilitator", "Tutor" or "Guide". These new role names will appear within the course. For example on the [[Participants|participants]] and the override permissions pages.

Please note that the site administrator or a [[Manager |course manager]] may have changed the names or added new roles. These names will appear and the teacher may rename them.

== Site administration settings==

An administrator can set course default settings in ''Administration > Site administration > Courses > Course default settings''.

The maximum number of weeks/topics may be set for all courses on the site. The default value is 52.

==Preventing teachers from editing course settings==

Any/all of the following fields - course full name, short name, ID number and category, summary - may be locked to prevent teachers from editing them. To do so:

#Access ''Site Administration > Users > Permissions > Define roles''.
#Click the edit icon opposite the teacher role.
#Change any/all of the capabilities [[Capabilities/moodle/course:changefullname|moodle/course:changefullname]], [[Capabilities/moodle/course:changeshortname|moodle/course:changeshortname]], [[Capabilities/moodle/course:changeidnumber|moodle/course:changeidnumber]], [[Capabilities/moodle/course:changecategory|moodle/course:changecategory]], [[Capabilities/moodle/course:changesummary|moodle/course:changesummary]] from allow to not set.
#Click the "Save changes" button at the bottom of the page.

==See also==
* [http://youtu.be/vOm1NAknuvk Creating a Course and Course Settings] MoodleBites video on YouTube

[[de:Kurseinstellungen]]
[[es:Configuraciones del curso]]
[[eu:Ikastaroaren_ezarpenak]]
[[fr:Paramètres du cours]]
[[ja:コース設定]]

Choice settings

2014-01-19T02:15:48Z

Cttxg: Adding MoodleBites YouTube video link

{{Choice}}
==Choice administration settings==
*With the editing turned on, choose from the"Add an activity or resource" link (or, if not present, the "Add an activity" drop down menu) the option ''Choice''. To see all the settings expanded, click "Expand all" top right.

==General==

{|
|[[File:choicegeneral26.png|General settings expanded by default]]
|}

===Choice name===
A short name of the choice (e.g. "Favourite colour"). This will be displayed on the course's homepage.

===Description===

Type the description of the choice activity here. Click the icon on the left to expand the toolbars and drag the bottom right of the text box out to expand it. It should contain the question that you want your students to answer. An example of the choice text could be "What is your favourite colour?" There is also an option to display the choice description on the course page below the link to the activity.

====Display mode for the options====
*Choose "horizontally" if you only have three or four choices maximum; choose "vertically if you have a large number of choices.

==Options==
{|
|[[File:choiceoptions25.png|Options settings expanded by default]]
|}

===Allow choice to be updated===

*If this is set to "Yes", students can change their mind after they have voted. If it's set to "No", students cannot change their choice.
'''
===Limit the number of responses===
*Enabling this option allows you to limit the number of participants who can select each particular choice. When that number has been reached, no one else can select that choice.

'''Warning!!''' If you unintentionally check this box but don't add a number then your students won't be able to select any choices and will get confused :)

===Option===
*Specify here the options that participants have to choose from. They will become radio buttons when the choice is saved.
*You can leave other options blank or click "Add 3 fields to form" to add more options.
*If ''Limits'' is disabled, then any number of participants can select any of the options.

==Availability==
(These settings are collapsed by default)
{|
|[[File:choiceavailability26.png|Availability expanded]]
|}

===Restrict answering===
*If you check this box you can set an "open and close" date for your choice.
*If you leave it, they can respond at any time.

==Results==
(These settings are collapsed by default)
{|
|[[File:choiceresults26.png|450px|Results expanded]]
|}

===Publish results===

*This determines whether (and when) the students will be able to view the results of the choice activity. They may:

**never see the results of the choice
**see the results only after they have given the answer themselves
**see the results only after the closing date of the choice
**always see the results

===Privacy of results===

*If "Publish" was chosen above, then this dropdown in unlocked. You can decide whether to show names of students or merely the number who responded but without names.

===Show column for unanswered===

*If set to "Yes", this will display a column showing how many participants have not answered the choice activity yet. If set to "No", the results will only include the participants who have already voted.

==Common module settings==
These settings are collapsed by default. See [[Common module settings]]for more information.

==Restrict access/Activity completion==
(These settings are collapsed by default)

These settings are visible if [[Conditional activities]] and [[Activity completion]] have been enabled in the site and the course.

==Choice module capabilities==

*[[Capabilities/mod/choice:downloadresponses|Download choice responses]]
*[[Capabilities/mod/choice:deleteresponses|Delete choice responses]]
*[[Capabilities/mod/choice:readresponses|Read choice responses]]
*[[Capabilities/mod/choice:choose|Record a choice]]
*[[Capabilities/mod/choice:addinstance|Add a new choice]]

==See also==
* [http://youtu.be/QMlmZtZGrWM Moodle 2.0 Choice] MoodleBites video on YouTube

[[de:Abstimmung konfigurieren]]
[[fr:Ajouter/modifier un sondage]]

Chat settings

2014-01-19T02:13:08Z

Cttxg: Adding MoodleBites YouTube video link

{{Chat}}

==Adding a Chat to your course==

*With the editing turned on,in the section you wish to add your chat, click the "Add an activity or resource" link (or, if not present, the "Add an activity" drop down menu )and choose ''Chat'' All settings may expanded by clicking the "Expand all" link top right.

===General===
{|
|[[File:chatgeneral26.png|General settings expanded by default]]
|}

===Name of this chat room===
*Whatever you type here will form the link learners click on to enter the chat so it is helpful to give it a name that suggests its purpose - for example "Student council discussion" or "Field trip planning meeting".

===Description===
Type the description of the chat here. Include precise instructions for students regarding the subject of the chat. Click the icon on the left to expand the toolbar, and drag the bottom right of the text box out to expand it.

===Display description on course page===
If this box is ticked, the description will appear on the course page just below the name of the Chat.

==Chat sessions==
(These settings are collapsed by default.)

{|
|[[File:chatsessions25.png|thumb|450px|Chat sessions settings expanded.]]
|}
===Next chat time===

*The day and hour of the next chat session. This will appear in the calendar so students know the schedule but it doesn't stop them accessing the chatroom at any other time.
*If you don't want them in the chatroom at other times, then hide it (with the eye icon) or use [[Conditional activities]] to restrict access.
*If you don't wish to schedule chat times then ignore this and choose from the next settings.

'''Note:'''For courses involving users across different time zones, it is useful to know that the time you set here will be adjusted to match the time zone of the user viewing it.

===Repeat/publish sessions===

*There are four options for scheduling future chat sessions:

# '''Don't publish any chat times'''- there are no set times and students are welcome to chat at any time.
# '''No repeats - publish the specified time only'''- only the Next chat time will be published. This could be used to schedule special events or meetings or simply to help learners identify a common time in which they can expect to find other learners in the chat room.
# '''At the same time every day'''- Daily chats are useful for scheduling daily office hours or work sessions with learners.
# '''At the same time every week'''--This setting will schedule a chat for the same day and time every week, which could be useful for instance for meeting and reviewing key ideas and questions related to the week’s content/assessment.

===Save past chat sessions===

*Choose from the dropdown how many days to save - or save everything by selecting ''Never delete messages''
*If you have any concerns about discussions that might take place in your chat room, you may want to keep transcripts to check the suitablility of what is discussed. If your learners are using the chatroom to collaborate on a group project you won't want to delete the messages until the project is complete.

===Everyone can view past sessions===

*Decide here whether or not allow everyone to view past chat sessions. (Teachers can always view past sessions)

==Common module settings==
(These settings are collapsed by default.)

See [[Common module settings]]
==Restrict access/Activity completion==
(These settings are collapsed by default)

These settings are visible if [[Conditional activities]] and [[Activity completion]] have been enabled in the site and the course.

==Locally assigned roles==

*In ''Administration > Chat administration > Locally assigned roles'' selected users can be given additional roles in the activity, such as the capability to delete chat logs.

*Role permissions for the activity can be changed in ''Administration > Chat administration > Permissions''.

==Site administration settings==

The chat module has additional settings which may be changed by an administrator in ''Administration > Site administration > Plugins > Activity modules > Chat''. They depend on the chat method which has been selected:

[[File:Chatmethod.png]]

===Ajax===
*This is the default method. It works everywhere but if many people are chatting it can put a large load on the server. Its particular settings are:
**'''Refresh user list''' - choose the number of seconds after which the user list is refreshed
**'''Disconnect timeout''' - choose the number of seconds after which we detect a user has disconnected.

===Normal method===
*The particular settings for this method are:
**'''Refresh room''' - choose the number of seconds after which the room is refreshed
**'''Update method''' - choose how to update the chatroom - "Keep alive" or "Stream" strategy. Stream works better but your sever might not support it.

===Chat server daemon===
*A daemon is a program that runs all the time in the background. In this case it's a PHP script, listening to a particular port on your server, accepting and giving out chat information.If you intend to use the chat activity a lot, then you should consider using a chat server daemon to reduce server load.Its particular settings are:
**Server name
**Server IP address
**Server port
**Max users

Then you need to start the chat daemon script from the command line:

cd moodle/mod/chat
php chatd.php --start &

==Chat capabilities==

*[[Capabilities/mod/chat:chat|Access a chat room]]
*[[Capabilities/mod/chat:deletelog|Delete chat logs]]
*[[Capabilities/mod/chat:exportparticipatedsession|Export chat session which you took part in]]
*[[Capabilities/mod/chat:exportsession|Export any chat session]]
*[[Capabilities/mod/chat:readlog|Read chat logs]]
*[[Capabilities/mod/chat:addinstance|Add a new chat]]

==See also==
* [http://youtu.be/TFRCZ21tvNk The Chat actvitiy in Moodle 2.x] MoodleBites video on YouTube

[[de:Chat konfigurieren]]
[[fr:Ajouter/modifier un chat]]

Bloki

2014-01-19T02:03:12Z

Cttxg: /* See also */ Adding MoodleBites YouTube video link

{{Managing a Moodle course}}
Blocks are items which may be added to the left or right or centre column of any page in Moodle. They may also be added to the centre of the My Home (My Moodle) page. You can theme the position of blocks in the centre of pages as well.

Any block can be made 'sticky' so that it appears in all the contexts below, such as throughout a course or a particular activity - see [[Block settings]].

Blocks can be placed on the side of the screen (if your theme supports it) via the [[Dock]] icons ( [[Image:Dock_to_block.png]] and [[Image:Block_to_dock.png]] ). If a responsive theme (such as 'Clean') is used, blocks will be accessible from the bottom of smaller screens, below the main content.

==Standard blocks==

Available blocks include:

[[Image:blocks01.png|thumb|Default block positions for a new course page]]

{|-
|[[Activities block|Activities]]
|-
|[[Admin bookmarks block|Admin bookmarks]]
|-
|[[Administration block|Administration]]
|-
|[[Blog menu block|Blog menu]]
|-
|[[Blog tags block|Blog tags]]
|-
|[[Calendar block|Calendar]]
|-
| [[Comments block|Comments]]
|-
| [[Community finder block|Community finder]]
|-
| [[Course completion status block|Course completion status]]
|-
|[[Course overview block|Course overview]]
|-
| [[Course/site summary block|Course/site summary]]
|-
| [[Courses block|Courses]]
|-
| [[Feedback block|Feedback]]
|-
| [[Flickr block|Flickr]]
|-
|[[HTML block|HTML]]
|-
| [[Latest news block|Latest news]]
|-
|[[Logged in user block|Logged in user]]
|-
|[[Login block|Login]]
|-
|[[Main menu block|Main menu]]
|-
|[[Mentees block]]
|-
|[[Messages block|Messages]]
|-
|[[My latest badges block|My latest badges]]
|-
| [[My private files_block|My private files]]
|-
|[[Navigation block|Navigation]]
|-
|[[Network servers block|Network servers]]
|-
|[[Online users block|Online users]]
|-
|[[People block|People]]
|-
|[[Quiz results block|Quiz results]]
|-
|[[Random glossary entry block|Random glossary entry]]
|-
|[[Recent activity block|Recent activity]]
|-
|[[Recent blog entries block|Recent blog entries]]
|-
|[[Remote RSS feeds block|Remote RSS feeds]]
|-
|[[Search forums block|Search forums]]
|-
|[[Section links block|Section links]]
|-
|[[Self completion block|Self completion]]
|-
|[[Social activities block|Social activities]]
|-
|[[Tags block|Tags]]
|-
|[[Upcoming events block|Upcoming events]]
|-
|[[Youtube block|Youtube]]
|-
|}

There are also many contributed blocks available for download from the [https://moodle.org/plugins/ plugins database].

==See also==
* [http://youtu.be/0Y0hZI09ol0 Adding a Moodle block] MoodleBites video on YouTube
* [http://youtu.be/qabocvXXRhU Moodle 2.0 Blocks - part 1] and [http://youtu.be/EJFp3a4W860 Moodle 2.0 Blocks - part 2] MoodleBites videos on YouTube for an explanation of the standard Moodle blocks in 2.x sites
* [[Managing blocks]] - for administrators
* [[Blocks FAQ]]
* [http://www.youtube.com/watch?v=6aX1XHfBjqg Blocks in Moodle 2.0 video]
* [https://moodle.org/mod/forum/discuss.php?d=227772 Moodle forum discussion about ''which Moodle blocks are the most useful for teaching'']

[[Category:Block]]

[[de:Blöcke]]
[[es:Bloques]]
[[eu:Irakaslearen_blokeak]]
[[fr:Blocs]]
[[ja:ブロック]]

Bloki

2014-01-19T01:54:35Z

Cttxg: /* See also */ Adding MoodleBites YouTube video link

{{Managing a Moodle course}}
Blocks are items which may be added to the left or right or centre column of any page in Moodle. They may also be added to the centre of the My Home (My Moodle) page. You can theme the position of blocks in the centre of pages as well.

Any block can be made 'sticky' so that it appears in all the contexts below, such as throughout a course or a particular activity - see [[Block settings]].

Blocks can be placed on the side of the screen (if your theme supports it) via the [[Dock]] icons ( [[Image:Dock_to_block.png]] and [[Image:Block_to_dock.png]] ). If a responsive theme (such as 'Clean') is used, blocks will be accessible from the bottom of smaller screens, below the main content.

==Standard blocks==

Available blocks include:

[[Image:blocks01.png|thumb|Default block positions for a new course page]]

{|-
|[[Activities block|Activities]]
|-
|[[Admin bookmarks block|Admin bookmarks]]
|-
|[[Administration block|Administration]]
|-
|[[Blog menu block|Blog menu]]
|-
|[[Blog tags block|Blog tags]]
|-
|[[Calendar block|Calendar]]
|-
| [[Comments block|Comments]]
|-
| [[Community finder block|Community finder]]
|-
| [[Course completion status block|Course completion status]]
|-
|[[Course overview block|Course overview]]
|-
| [[Course/site summary block|Course/site summary]]
|-
| [[Courses block|Courses]]
|-
| [[Feedback block|Feedback]]
|-
| [[Flickr block|Flickr]]
|-
|[[HTML block|HTML]]
|-
| [[Latest news block|Latest news]]
|-
|[[Logged in user block|Logged in user]]
|-
|[[Login block|Login]]
|-
|[[Main menu block|Main menu]]
|-
|[[Mentees block]]
|-
|[[Messages block|Messages]]
|-
|[[My latest badges block|My latest badges]]
|-
| [[My private files_block|My private files]]
|-
|[[Navigation block|Navigation]]
|-
|[[Network servers block|Network servers]]
|-
|[[Online users block|Online users]]
|-
|[[People block|People]]
|-
|[[Quiz results block|Quiz results]]
|-
|[[Random glossary entry block|Random glossary entry]]
|-
|[[Recent activity block|Recent activity]]
|-
|[[Recent blog entries block|Recent blog entries]]
|-
|[[Remote RSS feeds block|Remote RSS feeds]]
|-
|[[Search forums block|Search forums]]
|-
|[[Section links block|Section links]]
|-
|[[Self completion block|Self completion]]
|-
|[[Social activities block|Social activities]]
|-
|[[Tags block|Tags]]
|-
|[[Upcoming events block|Upcoming events]]
|-
|[[Youtube block|Youtube]]
|-
|}

There are also many contributed blocks available for download from the [https://moodle.org/plugins/ plugins database].

==See also==
*[http://youtu.be/0Y0hZI09ol0 Adding a Moodle block] MoodleBites video on YouTube
* [[Managing blocks]] - for administrators
* [[Blocks FAQ]]
* [http://www.youtube.com/watch?v=6aX1XHfBjqg Blocks in Moodle 2.0 video]
* [https://moodle.org/mod/forum/discuss.php?d=227772 Moodle forum discussion about ''which Moodle blocks are the most useful for teaching'']

[[Category:Block]]

[[de:Blöcke]]
[[es:Bloques]]
[[eu:Irakaslearen_blokeak]]
[[fr:Blocs]]
[[ja:ブロック]]

Managing blocks

2014-01-19T01:53:28Z

Cttxg: /* See also */ Removing Youtube video to teachers pages

{{Blocks}}
==Manage blocks==

An administrator can manage Moodle's blocks for the site in ''Administration > Site administration > Plugins > Blocks > Manage blocks'', including any contributed blocks that have been added.

===Instances===

The blocks page lists the number of instance for each block. Clicking on a number results in the list of courses containing that block being displayed. See [[Block settings]] for configuration settings that might be of interest to a site administrator or someone with Front Page editing permissions.

===Version===

Listed with each block is its version number — in the format 2012061700. This is helpful to ensure that you have the latest version of each block.

===Hiding a block===

The hide/show column allows selected blocks to be hidden i.e. they do not appear in any course "Add a block" dropdown menu and cannot be used in any course. To hide a block, click the eye icon so that it changes to a closed eye.

To reduce the length of course "Add a block" dropdown menus, you should hide blocks which will not be used, such as mentees (unless you have added a [[Parent role|mentor role]]) and network servers (unless you are using [[MNet|Moodle Networking]]).

===Protecting blocks from deletion===

By clicking the padlock against a block in this column, you are preventing it from being deleted on the site. The [[Administration block]] and [[Navigation block]] are already padlocked, as major difficulties arise if these blocks are deleted. Only unlock them if you are absolutely sure you understand the consequences and have alternative settings and navigation features in place.

===Block deletion===

Blocks can be deleted using the link in the delete column (but see comments about the [[Administration block]] and [[Navigation block]] in the previous section) There is usually no reason for standard blocks to be deleted (they are usually hidden) However, non-standard blocks may need to be deleted before upgrading.

:''Note:'' To delete a block completely, in addition to deleting it on the blocks page, you also need to remove/delete the actual block folder from the ''moodle/blocks'' folder, otherwise Moodle will reinstall it next time you access the site administration.

===Block settings===

Certain blocks have additional settings, which can be accessed via the links in the settings column.

==Block capabilities==

*[[Capabilities/moodle/my:manageblocks|Manage My home page blocks]]
*[[Capabilities/moodle/tag:editblocks|Edit blocks in tags pages]]
*[[Capabilities/moodle/user:manageownblocks|Manage blocks on own public user profile]]
*[[Capabilities/moodle/user:manageblocks|Manage blocks on user profile of other users]]
*[[Capabilities/moodle/block:edit|Edit a block's settings]]
*[[Capabilities/moodle/block:view|View block]]
*[[Capabilities/moodle/site:manageblocks|Manage blocks on a page]]

In addition, every block has an ''addinstance'' capability (e.g. [[Capabilities/block/comments:addinstance|block/comments:addinstance]]) and most blocks also have a ''myaddinstance'' capability (e.g. [[Capabilities/block/comments:myaddinstance|block/comments:myaddinstance]]) for controlling whether a user with a particular role can add the block to a page or to their [[My home]] page respectively.

==Contributed blocks==

In addition to using the blocks included in the standard download, other Moodlers have developed their own blocks which they share with the Moodle community. You can download these contributed blocks from the Moodle.org [http://moodle.org/plugins Moodle Plugins directory]. See [[Installing plugins]] for details of how to install a block.

==See also==
*[[Block layout]]

[[Category:Site administration]]

[[eu:Blokeak_%28Kudeatzailea%29]]
[[ja:ブロック管理 (管理者)]]
[[de:Administration_von_Bl%C3%B6cken]]
[[es:Gestionando bloques]]

Managing blocks

2014-01-19T01:52:25Z

Cttxg: /* See also */ Adding MoodleBites YouTube video link

{{Blocks}}
==Manage blocks==

An administrator can manage Moodle's blocks for the site in ''Administration > Site administration > Plugins > Blocks > Manage blocks'', including any contributed blocks that have been added.

===Instances===

The blocks page lists the number of instance for each block. Clicking on a number results in the list of courses containing that block being displayed. See [[Block settings]] for configuration settings that might be of interest to a site administrator or someone with Front Page editing permissions.

===Version===

Listed with each block is its version number — in the format 2012061700. This is helpful to ensure that you have the latest version of each block.

===Hiding a block===

The hide/show column allows selected blocks to be hidden i.e. they do not appear in any course "Add a block" dropdown menu and cannot be used in any course. To hide a block, click the eye icon so that it changes to a closed eye.

To reduce the length of course "Add a block" dropdown menus, you should hide blocks which will not be used, such as mentees (unless you have added a [[Parent role|mentor role]]) and network servers (unless you are using [[MNet|Moodle Networking]]).

===Protecting blocks from deletion===

By clicking the padlock against a block in this column, you are preventing it from being deleted on the site. The [[Administration block]] and [[Navigation block]] are already padlocked, as major difficulties arise if these blocks are deleted. Only unlock them if you are absolutely sure you understand the consequences and have alternative settings and navigation features in place.

===Block deletion===

Blocks can be deleted using the link in the delete column (but see comments about the [[Administration block]] and [[Navigation block]] in the previous section) There is usually no reason for standard blocks to be deleted (they are usually hidden) However, non-standard blocks may need to be deleted before upgrading.

:''Note:'' To delete a block completely, in addition to deleting it on the blocks page, you also need to remove/delete the actual block folder from the ''moodle/blocks'' folder, otherwise Moodle will reinstall it next time you access the site administration.

===Block settings===

Certain blocks have additional settings, which can be accessed via the links in the settings column.

==Block capabilities==

*[[Capabilities/moodle/my:manageblocks|Manage My home page blocks]]
*[[Capabilities/moodle/tag:editblocks|Edit blocks in tags pages]]
*[[Capabilities/moodle/user:manageownblocks|Manage blocks on own public user profile]]
*[[Capabilities/moodle/user:manageblocks|Manage blocks on user profile of other users]]
*[[Capabilities/moodle/block:edit|Edit a block's settings]]
*[[Capabilities/moodle/block:view|View block]]
*[[Capabilities/moodle/site:manageblocks|Manage blocks on a page]]

In addition, every block has an ''addinstance'' capability (e.g. [[Capabilities/block/comments:addinstance|block/comments:addinstance]]) and most blocks also have a ''myaddinstance'' capability (e.g. [[Capabilities/block/comments:myaddinstance|block/comments:myaddinstance]]) for controlling whether a user with a particular role can add the block to a page or to their [[My home]] page respectively.

==Contributed blocks==

In addition to using the blocks included in the standard download, other Moodlers have developed their own blocks which they share with the Moodle community. You can download these contributed blocks from the Moodle.org [http://moodle.org/plugins Moodle Plugins directory]. See [[Installing plugins]] for details of how to install a block.

==See also==
*[http://youtu.be/0Y0hZI09ol0 Adding a Moodle block] MoodleBites video on YouTube
*[[Block layout]]

[[Category:Site administration]]

[[eu:Blokeak_%28Kudeatzailea%29]]
[[ja:ブロック管理 (管理者)]]
[[de:Administration_von_Bl%C3%B6cken]]
[[es:Gestionando bloques]]

Site appearance

2014-01-19T01:46:24Z

Cttxg: Adding MoodleBites YouTube video link

{{Managing a Moodle site}}

There are many ways to customise the appearance of your Moodle site so that it blends in with, for example, your college site or your company's corporate brand. The links below provide more information on personalising the appearance of Moodle:
*[[Front page]] - how best to display the entry page to your Moodle.
*[[My home]] - a personalised "dashboard" page for each user
*[[User profiles]]
*[[Navigation]] - control how users find their way around Moodle
*[[Course list]] - control who appears in the list of courses
*[[Themes]] - change the "skin" of your Moodle for the whole site or just sections.
*[[Header and footer]] - add information to the top and bottom areas of your Moodle.

==See also==
* [http://youtu.be/05eW0NzDi_c Moodle 2 Appearance Administration settings] MoodleBites video on YouTube
*Change the language or default wording on your site - [[Language|Language]]

[[de:Darstellung]]

Administration block

2014-01-19T01:38:25Z

Cttxg: Adding MoodleBites YouTube video link

{{Blocks}}
The Administration block provides context-sensitive links to settings pages.

What appears in the Administration block depends upon the [[Context]] (Page being shown and user's permissions). For example, a site administrator on the front page will have Front page settings while a teacher in a course will have more options in Course administration than a student.

Here are examples of the Administration block:
<gallery widths="200px" heights="200px" perrow="3">

Image:25frontpageadmin.png|Admin view from Front page (collapsed)
Image:25teacheradmin.png|Teacher view in a course (expanded)
Image:25studentadmin.png|Student view in a course (collapsed)
</gallery>

==Administration block menus==
The main menu items (Front page settings, Course Administration, My profile settings and Site Administration) contain a submenu and can be collapsed or expanded to display the (typical) full menu as shown below:
*[[Front_page_settings_block|Front page settings]]
**Turn edit on/off
**Edit settings
**Users
**Filters
**Backup
**Restore
**Questions
**Files

*[[Managing a Moodle course|Course administration]]
**Turn editing on
**Edit settings
**Users
**Filters
**Reports
**Grades
**Badges (if enabled)
**Backup
**Restore
**Import
**Publish
**Reset
**Question bank

*[[Profile |My profile settings]]
**Edit profile
**Change password
**Roles
**Portfolios (if available at site level)
**Security keys
**Messaging
**Blogs
**Make this my default home page (if set at site level)

*[[Site_administration|Site administration]]
**Notifications
**Registration
**Advanced features
**Users
**Courses
**Grades
**Badges
**Location
**Language
**Plugins
**Security
**Appearance
**Front page
**Server
**Reports
**Development
**Question engine upgrade helper

==See also==
* [http://youtu.be/H3dh-7U4dT8 Moodle 2.0 Administration area] MoodleBites video on YouTube

[[de:Einstellungen-Block]]
[[es:Bloque de administración]]
[[eu:Ezarpenak_blokea]]

Screencasts

2014-01-19T01:30:07Z

Cttxg: /* Where do I find screencasts about Moodle? */ adding the MoodleBites videos link

Screencasts are ways to present instructional material, usually through a series of pictures with an audio track.

==Screencasts in Moodle==
Screencasts use the [[Multimedia plugins|multimedia capabilities]] in Moodle. They can be embedded in most Moodle pages that have the [[HTML editor]]. A screencast might use a [[Flash|flash]] (.swf) file.

== Where do I find screencasts about Moodle? ==
You may find links to screencasts at the bottom of many MoodleDoc pages with external links to [http://www.youtube.com/results?search_type=&search_query=moodle Moodle screencasts on YouTube] or other places, e.g. [http://moodletutorials.org/ Moodle Tutorials].

Favorites include:
* the [http://www.youtube.com/usingmoodle UsingMoodle] channel by Moodlefairy aka [[User:Mary Cooch|Mary Cooch]], and
* the [http://www.youtube.com/HRDNZMoodlePartner MoodleBites videos] uploaded by [http://www.moodlebites.com/ MoodleBites] facilitators HRDNZ, official Moodle Partner

== Tools for creating screencasts ==

* '''CamStudio''' (open source) - http://camstudio.org
* '''Jing''' (free, but not open source) - http://www.jingproject.com
* '''recordMyDesktop''' (open source, for GNU/Linux systems) - http://recordmydesktop.sourceforge.net
* '''Camtasia Studio''' (commercial, 30-day trials and educational-pricing available) - http://www.techsmith.com/camtasia.asp
* '''Screentoaster''' (web-based, free) - http://screentoaster.com/
* '''Wink''' (free, but not open source) - http://www.debugmode.com/wink/

== How do I create a screencast? ==

* For detailed instructions see http://code.google.com/p/google-highly-open-participation-moodle/wiki/CreatingTutorialVideos
* You also find instructions on the web sites of the above mentioned tools.

== See also ==

* [[Flash]]

[[Category:Tutorial]]

Plik:dialogue-conversationsTeacher.png

2013-12-11T01:58:30Z

Cttxg: Cttxg uploaded a new version of "File:dialogue-conversationsTeacher.png"

Plik:dialogue-post.png

2013-12-11T01:54:25Z

Cttxg:

Plik:Editing Dialogue.png

2013-12-11T01:53:50Z

Cttxg:

Plik:dialogue-conversationsTeacher.png

2013-12-11T01:53:20Z

Cttxg:

Dialogue module

2013-12-11T01:52:54Z

Cttxg:

{{Infobox plugin
|type = Activity
|entry = https://moodle.org/plugins/view.php?plugin=mod_dialogue
|tracker = http://tracker.moodle.org/browse/CONTRIB/component/10139
|discussion = https://moodle.org/mod/forum/view.php?id=854
|maintainer = [[User:Troy Williams|Troy Williams]]
|float = right
}}
'''Dialogues''' allow students or teachers to start a private conversation with another user in the same course. They are course activities that can be useful when the teacher wants a place to give private feedback to a student on their online activity. For example, if a student is participating in a language forum and made a grammatical error that the teacher wants to point out without embarrassing the student, a dialogue is the perfect place. A dialogue activity would also be an excellent way for counsellors within an institution to interact with students - all activities are logged and email is not necessarily required.

Dialogue is a contributed activity module originally released for Moodle 1.6.x. and subsequently updated for Moodle 1.8.x to support roles and capabilities then updated to support Moodle 1.9.x, 2.0x and Groupings (groups of groups) and most recently to support Moodle 2.5x and bootstrap based themes.

==Features==
* Teachers can initiate private Dialogues between themselves and individual students
* Teachers can initiate individual Dialogues with all members of a group at one time
* Users can attach documents to their dialogue posts
* Students can view a time-stamped history of interaction between themselves and their teachers / tutors within the context of papers.
* Teachers and Students can view time-stamped histories of the interaction between them. Teachers can additionally view interaction histories with all students within a particular paper.
* Users can receive notification of new Dialogue posts via messaging options

==Settings==
[[Image:Editing_Dialogue.png|thumb|Dialogue Settings]]
* Dialogue Name - appears on the front page in the Moodle course section
* Dialogue Introduction - text that appears above the list of conversations

'''Legacy Settings'''
* Type of dialogue can be set to Teacher-Student, Student-Student, Everyone (these modify the permissions). These were legacy options pre-2.5x

==Creating a Conversations==
Click the 'Create' button to opening a new conversation.
Choose the person you would like to have a conversation with by typing their name in the 'People' text box.
If you would like to open a conversation with All Participants or an entire Group configure this via the Bulk open role section.
When opening via the Bulk Open Role select if future members will also receive a copy of the message (when they enrol after the initial message is created) and the cut off date for future members receiving the message. Note that the message will be created via the next cron job - not instantly.

==Viewing a Conversation==
[[Image:dialogue-conversationsTeacher.png|thumb|Dialogue Conversation List]]
Conversations can be sorted and if a user has the 'viewany' capability they can click the 'Everyone' button to view all conversations within the course.
Click the conversation to open it.

==Replying to a Conversation==
[[Image:dialogue-post.png|thumb|Dialogue Conversation Reply]]
When a conversation is open the Reply text box and attachment option is displayed below the last post.
It is possible to save a draft before sending - drafts are displayed in the Drafts tab in the conversation list.

==Tips and tricks==
*When students initially enrol on a site, it might be a good idea to send them a welcome dialogue to let them know the teacher is there. This way if the student has something to say to the teacher, they will feel more comfortable responding, since the teacher made the first step.
* In team teaching situations ensure the teacher roles have 'viewany' and 'participateany' but be clear to the students that the dialogue conversations are visible to other teachers.

==Roles/Capabilities==
The following capabilities are able to be assigned/set against site wide roles and overridden in your local Dialogue instances:

* mod/dialogue:bulkopenrulecreate - Determines if a role can open a conversation with All participants in a course/group
* mod/dialogue:bulkopenruleeditany - Determines if a role can edit an existing bulk open rule
* mod/dialogue:close - Determines if a role can close a conversation that user belongs to
* mod/dialogue:closeany - Determines if the role can close any conversation (used in conjunction with 'viewany')
* mod/dialogue:open - Determines which roles can open a new conversation
* mod/dialogue:receive - Determines which roles will appear in the list when creating a conversation
* mod/dialogue:reply - The ability to Reply to a conversation you are associated with
* mod/dialogue:replyany - The ability to Reply to any conversation (used in conjunction with 'viewany'
* mod/dialogue:viewany - The ability to View any conversation in a dialogue course module instance via the 'Everyone' button on the conversations page

==Module History==
* 2003/Oct - Ray Kingdon released the original module
* 2004/Jun - Dialogues with groups of students were supported
* 2006/Apr - Howard Miller (aka thepurpleblob) University of Glasgow, contributed fixes to bring Dialogue in line w v1.6
* 2006/Aug - Howard Miller volunteered to maintain the module. At the time he mentioned Messaging was the mechanism MartinD saw as the tool the core project would be supporting for this sort of activity, and that Dialogue was never actually intended to be anything other than an optional module.
* 2007/May - Clinton Graham provided a diff to get Dialogue running with roles in v1.8
* 2007 - Catalyst integrated group support allowing allocation of groups (or groupings) to specific activities.
* 2007/Aug - University of Waikato contract Catalyst to update Dialogue module to support v1.9 and make a number of feature changes
* 2008/Aug - Reinstated dialogue type selector, various bug fixes (Enrique,Clinton,Lorenzo & Dean Stringer)
* 2009/Feb - Improvements to student-to-student mode and all-participants selection for teachers (Dean Stringer)
* 2009/Mar - Reintroduced unread entries tracking, and validation fix on edittime field (Dean Stringer)
* 2009/Aug - Multiple fixes and improvements (Dean Stringer. With lots of contributed code/inspiration here from Enrique Castro)
** fixed bug re lost HTML formatting (see: CONTRIB-1448)
** sorting columns by name, date, post count etc (see: CONTRIB-1449)
** improved group-mode support (see: CONTRIB-1490)
** added participation report support (see: CONTRIB-1454)
** change to view current conversation after update rather than go back to list (see: CONTRIB-1455)
** lots of codeing/style improvments, thanx Petr :) (see: CONTRIB-1216)
* 2011/Oct - Troy Williams updated to support v2.0x
* 2013/Oct - Troy Williams rewrite for version 2.5x

== See also ==
* [http://moodle.org/mod/forum/view.php?id=854 Dialogue module forum] - discuss the module here
* [http://download.moodle.org/download.php/docs/en/using_moodle/ch4_forums.pdf Chapter 4: Using Forums, Chats and Dialogues]
* [https://docs.moodle.org/en/Development:Dialogue_2.0_specification Development:Dialogue 2.0 specification]

[[Category:Contributed code]]

Add-on Review Criteria

2013-05-27T10:07:18Z

Cttxg:

{{Help}}
== Some Criteria to consider when looking at 3rd party Add-ons==
There are many great 3rd party plugins available for Moodle. However, it is important to assess the suitability and reliability of the plugin before adopting it.

This list is not exhaustive as there may be more or less questions depending on the individual installation and organisation.

This list was published originally by Gavin Henrick ([http://www.lts.ie/ Learning Technology Services]), see [http://www.somerandomthoughts.com/blog/2012/05/14/some-criteria-to-review-when-considering-a-plugin/ Some criteria to review when considering a plugin]

== Some initial questions==
*What is the purpose of the plugin?
*Is there nothing in the installation which can deliver this feature already?
*Is this the best solution for this requirement?
*What versions does it work with
*How many times has it been downloaded for your version

== Is it easy to install?==
*Is the source managed on svn/github
*Is it available in the Moodle.org plugins database
*Is the zip available to download into the correct folder name or does it need exploring to change
*Is it just a drop in and use notifications or is it more complex / require patches manual intervention / additional server software requirements (if so is this clearly indicated in the version.php - see [https://docs.moodle.org/dev/version.php Version docs])

== Is the documentation good?==
*Has it got a Moodle Docs page
*Has it got good readme.txt
*Has it got good help files & instructions
*Has it got screenshots

== Is it easy for teacher to use?==
*For the most common use case is it logical in usage?
*Are the instructions for use correct and usable?

== Is it easy for student to use?==
*For the most common use case is it logical in usage?
*Are the instructions for use correct and usable?

== Does it do what it says?==
*Are the instructions for use correct and usable?
*Does it provide the functionality as described in a good sensible way, is it a "full feature" or an interim solution.

== Features==
*Does it have a roadmap of potential improvements /changes?
*Will it work on Mobile theme and on Web?

== Feedback==
*Are there any comments from users on the plugin site?
*Are there any reviews of the module?
*Are there any discussions on it in the forums?

== Author Background (experience/reliability check)==
*Are they active in Moodle community for a good period of time?
*Do they respond well to queries on bugs etc.?
*Do they work for an established Moodle development team (Moodle partner, the OU, or HQ for example)?

== Technical==
*Does it work properly with the different database types?
*Is the mod being updated regularly with new Moodle versions?
*Does the module follow good Moodle coding standards? (Use [https://moodle.org/plugins/view.php?plugin=local_codechecker the Code Checker plugin])
*Does it properly use language files or has it got hardcoded text?
*Does it properly follow accessibility guidelines?
*Does it properly follow css and theming approaches?
*Does it conflict with anything else naming wise?
*Does it depend on another non-standard add-on (if so is this clearly indicated in the version.php - see [https://docs.moodle.org/dev/version.php Version docs])
*Does author regularly bug fix?
*Does it impact performance of Moodle in normal or high traffic usage?
*Does it have any security risks (is the user data protected/sanitised)
*What resources will it require to be used?
*Does backup/restore work?
*Has it got unit tests?

== See Also==
*[http://www.somerandomthoughts.com/blog/2012/05/14/some-criteria-to-review-when-considering-a-plugin/ Some criteria to review when considering a plugin] Gavin Henrick - May 2012
*[http://www.moodleaddons.com/book/ Moodle Addons Book] Gavin Henrick, Michael de Raadt - May 2013

Add-on Review Criteria

2013-05-27T10:02:13Z

Cttxg: adding a few extra bits from an iMoot2013 brainstorm with Lindy Klein

{{Help}}
== Some Criteria to consider when looking at 3rd party Add-ons==
There are many great 3rd party plugins available for Moodle. However, it is important to assess the suitability and reliability of the plugin before adopting it.

This list is not exhaustive as there may be more or less questions depending on the individual installation and organisation.

This list was published originally by Gavin Henrick ([http://www.lts.ie/ Learning Technology Services]), see [http://www.somerandomthoughts.com/blog/2012/05/14/some-criteria-to-review-when-considering-a-plugin/ Some criteria to review when considering a plugin]

== Some initial questions==
*What is the purpose of the plugin?
*Is there nothing in the installation which can deliver this feature already?
*Is this the best solution for this requirement?
*What versions does it work with
*How many times has it been downloaded for your version

== Is it easy to install?==
*Is the source managed on svn/github
*Is it available in the Moodle.org plugins database
*Is the zip available to download into the correct folder name or does it need exploring to change
*Is it just a drop in and use notifications or is it more complex / require patches manual intervention / additional server software requirements

== Is the documentation good?==
*Has it got a Moodle Docs page
*Has it got good readme.txt
*Has it got good help files & instructions
*Has it got screenshots

== Is it easy for teacher to use?==
*For the most common use case is it logical in usage?
*Are the instructions for use correct and usable?

== Is it easy for student to use?==
*For the most common use case is it logical in usage?
*Are the instructions for use correct and usable?

== Does it do what it says?==
*Are the instructions for use correct and usable?
*Does it provide the functionality as described in a good sensible way, is it a "full feature" or an interim solution.

== Features==
*Does it have a roadmap of potential improvements /changes?
*Will it work on Mobile theme and on Web?

== Feedback==
*Are there any comments from users on the plugin site?
*Are there any reviews of the module?
*Are there any discussions on it in the forums?

== Author Background (experience/reliability check)==
*Are they active in Moodle community for a good period of time?
*Do they respond well to queries on bugs etc.?
*Do they work for an established Moodle development team (Moodle partner, the OU, or HQ for example)?

== Technical==
*Does it work properly with the different database types?
*Is the mod being updated regularly with new Moodle versions?
*Does the module follow good Moodle coding standards?
*Does it properly use language files or has it got hardcoded text?
*Does it properly follow accessibility guidelines?
*Does it properly follow css and theming approaches?
*Does it conflict with anything else naming wise?
*Does it depend on another non-standard add-on (if so is this clearly indicated in the readme.txt)
*Does author regularly bug fix?
*Does it impact performance of Moodle in normal or high traffic usage?
*Does it have any security risks (is the user data protected/sanitised)
*What resources will it require to be used?
*Does backup/restore work?
*Has it got unit tests?

== See Also==
*[http://www.somerandomthoughts.com/blog/2012/05/14/some-criteria-to-review-when-considering-a-plugin/ Some criteria to review when considering a plugin] Gavin Henrick - May 2012
*[http://www.moodleaddons.com/book/ Moodle Addons Book] Gavin Henrick, Michael de Raadt - May 2013

error/moodle/missingparam

2013-02-05T03:11:21Z

Cttxg:

A required parameter (id) was missing

This is an error we have seen when a user is timed out.

I am trying to restore courses from version 1.8 to 2.0. Most of the courses have posted fine, but several of them are returning the above message. These are the largest courses with user data. Any solutions out there?

Forum settings

2012-03-21T00:25:52Z

Cttxg: /* Subscription mode */ clarifying subscription mode options as per 2.x

{{Forum}}
[[Image:Adding a forum.png||thumb|Adding a forum, showing General and Grade sections]]To add a forum:
#As an editing teacher for a course, click "Turn Editing On", and go to the topic or week section in which you want to create the forum.
#From the dropdown menu labeled "Add an activity", select "Forum". This will take you to the forum settings page titled "Adding a new forum" page.

In an existing forum, the following settings can be found in ''Settings > Forum administration > Edit settings''.

==Forum administration settings==

===Forum name===

A short name of the forum (e.g. "Favourite colour"), which will be displayed on the course homepage.

===Forum type===

There are five forum types to choose from:

[[File:Forumtypes.png]]

*A single simple discussion - A single topic discussion developed on one page, which is useful for short focused discussions
*Standard forum for general use - An open forum where anyone can start a new topic at any time; this is the best general-purpose forum
*Each person posts one discussion - Each person can post exactly one new discussion topic (everyone can reply to them though); this is useful when you want each student to start a discussion about, say, their reflections on the week's topic, and everyone else responds to these
*Q and A Forum - Instead of initiating discussions participants pose a question in the initial post of a discussion. Students may reply with an answer, but they will not see the replies of other Students to the question in that discussion until they have themselves replied to the same discussion.
*Standard forum displayed in a blog-like format

A [[News forum]] is a special type of forum that is automatically created with a new course.

===Forum introduction===

Place the description of the forum here. It has the standard Moodle [[HTML editor]] toolbar to assist the teacher.

:''TIP:'' It is a good practice to include precise instructions for students regarding the subject of the forum and the rating and grading criteria that might be used in this forum (see below).

===Subscription mode===

When a person is subscribed to a forum it means that they will be sent email copies of every post in that forum. This will over ride some [[Edit profile|student settings in their profile]]. By default, posts are recorded about 30 minutes after the post was first written. Depending upon the email settings of each forum member, they may be sent an email immediately after the 30 minute edit window is closed, or in a batch at a time fixed by the site administrator (see below).

People can usually choose whether or not they want to be subscribed to each forum. However, the teacher can choose to force subscription on a particular forum then all course users will be subscribed automatically, even those that enrol at a later time.

There are 4 subscription mode options:
* Optional subscription - Participants can choose whether to be subscribed
* Forced subscription - Everyone is subscribed and cannot unsubscribe
* Auto subscription - Everyone is subscribed initially but can choose to unsubscribe at any time
* Subscription disabled - Subscriptions are not allowed.

The subscription mode and subscribe or unsubscribe links appear in the Settings menu under Forum administration when viewing the forum. teachers can quickly change the mode via the 'Subscription mode' options and view the current subscribers via the 'Show/edit current subscribers' link.

Tips:
* Forcing everyone to subscribe is especially useful in the [[News forum]] and in forums towards the beginning of the course (before everyone has worked out that they can subscribe to these emails themselves).
* Changing the setting from "Yes, initially" to "No" will not unsubscribe existing users, it will only affect those who enrol in the course in the future. Similarly changing "Yes, initially" will not subscribe existing course users but only those enrolling later.
* There is also a "Subscriptions not allowed" setting which prevents Students from subscribing to a Forum. Teachers may choose to subscribe to a forum if they wish.

===Read tracking for this forum?===

"Read tracking" for a forum allows users to track read and unread messages in the forum.

There are three options for this setting:
* Optional (default) - students can turn tracking on or off for the forum at their discretion
* On - tracking is always on in this forum for all members
** Not quite sure about this statement. This seems to only be true for users who have read tracking enabled in their user settings (Tested in Moodle 2.0.4 and at http://demo.moodle.net/)
* Off - tracking is always off in this forum for all members

===Maximum attachment size===

The maximum file size that may be attached to a forum post will first be determined by the Moodle site settings. The teacher may want a smaller size limit for the forum. Server file capacity, student downloading speeds and discouraging images in a document centered discussion are a few reasons to limit file size.

===Post threshold for blocking===

Students (i.e. users which don't have the 'Exempt from post threshold' permission) can be blocked from posting more than a specified number of posts in a given period.

===Grade===

Forum posts can be rated using a [[Scales|scale]] (pre existing number or word scales). By default, only teachers can rate forum posts, though students can be given permission to do so if desired (see Forum permissions below). This is a useful tool for giving students participation grades. Any ratings given in the forum are recorded in the [[Gradebook|gradebook]].

===Aggregate type===

You can set an aggregate type, in other words, decide how all the ratings given to posts in a forum are combined to form the final grade (for each post and for the whole forum activity). Some scales do not lend themselves to certain types of aggregates. There are five options:

* Average of ratings (default) - This is the mean of all the ratings given to posts in that forum. It is especially useful with peer grading when there are a lot of ratings being made.
* Count of ratings - The counts the number of rated posts which becomes the final grade. This is useful when the number of posts is important. Note that the total can not exceed the maximum grade allowed for the forum. A count may be used if the teacher simply wants to acknowledge that a reply was given in the case students being required to make a certain number of posts in the discussion. Note: Count of ratings does not work for the "Separate or Connected Ways of Knowing" scale or custom scales due to the limitation imposed by the max grade.
* Maximum rating - The highest rating is returned as the final grade. This method is useful for emphasising the best work from participants, allowing them to post one high-quality post as well as a number of more casual responses to others.
* Minimum rating - The smallest rating is returned as the final grade. This method promotes a culture of high quality for all posts.
* Sum of ratings - All the ratings for a particular user are added together. Note that the total is not allowed to exceed the maximum grade for the forum. Note: Sum of ratings does not work for the "Separate or Connected Ways of Knowing" scale or custom scales due to the limitation imposed by the max grade.

===Restrict ratings to posts with dates in this range===
The teacher can allow only posts within a certain date range to be rated. This is useful if the teacher wants to keep students focused on the most recent content and maintain a specific pace within the forum or course.

===RSS feed for this activity===

This turns RSS on or off for this forum. When set to “None,” RSS is disabled. When set to “Discussions,” the RSS feed will send out new discussions to subscribers. When set to “Posts,” the RSS feed will send out any new posts to subscribers.

===Number of RSS recent articles===

This number sets the number of articles that go out via RSS. If this number is set to 5, then the 5 most recent articles will be sent to subscribers. As new posts (or discussions) get added, the oldest post/discussion gets replaced on the RSS feed. If your forum gets a lot of posts every day, you will want to set this number high.

The administrative cron (admin/cron.php) must run after the forum is created and posts or discussions have been made. Otherwise the user will receive an error "Error reading RSS data"

Note: [[RSS feeds]] must be enabled for the site and for forums in order for the RSS settings to appear.

===Common module settings===

====Group mode====

The [[Groups|group]] mode setting has three options:

# No groups
# Separate groups - each group can only see their own group, others are invisible
# Visible groups - each group works in their own group, but can also see other groups

If the group mode is set to separate groups:
[[Image:Forum set to separate groups.png|650px|thumb|Adding a new discussion topic to a forum set to separate groups]]
* Teachers are given the option of adding a new discussion topic for all participants or for a selected group. If a teacher adds a new discussion topic for a selected group, then only group members can reply to it. If a teacher adds a new discussion topic for all participants, then students can't reply to it. (This is to ensure that groups are kept separate.)
* Students can only start discussions for their own group.
* Students can only reply to discussions started by other group members or discussions for their own group started by a teacher.

If the group mode is set to visible groups:

* Teachers are given the option of adding a new discussion topic for all participants or for a selected group. If a teacher adds a new discussion topic for a selected group, then only group members can reply to it.
* Students can only start discussions for their own group.
* Students can only reply to discussions started by other group members or teachers.

Teachers, and other users with the capability [[Capabilities/moodle/site:accessallgroups|moodle/site:accessallgroups]] set to allow, can view and post in all forum discussions, regardless of the group mode setting.

:''Note'': Single simple discussions cannot be set to separate groups (as this feature is not implemented). Instead, a standard forum should be used, with the teacher copying and pasting the same discussion topic for each separate group. If required, a permissions override may be set to prevent students from starting new discussions.

:''Note 2'': There is a further setting in 2.0, enabled at system level admin > development that hides groups-enabled activities from a student if they are not in a group.

====Visible to students====

You can hide the activity from students by selecting "Hide" here. It is useful if you wouldn't like to make the activity available immediately.

====ID number====

Setting an ID number provides a way of identifying the forum for grade calculation purposes. If the activity is not included in any grade calculation then the ID number field can be left blank.

==Locally assigned roles==

In ''Settings > Forum administration > Locally assigned roles'' selected users can be given additional roles in the activity.

===Forum moderator===

A student can be given the rights to moderate a forum by assigning them the role of non-editing teacher in the forum.

# In ''Settings > Forum administration > Locally assigned roles'' click on student
# Select the student from the potential users list on the right, and use the Add button to add them to the existing users list on the left. Multiple users may be selected by holding down the Apple or Ctrl key whilst clicking on the users' names.

See also [[Forum moderator role]].

==Forum permissions==

Role permissions for the activity can be changed in ''Settings > Forum administration > Permissions''.

[[File:Forum permissions.png|Frame|]]

Common permissions changes include:

===Enabling students to rate posts===

Click the Allow icon (+) opposite the capability to rate posts and allow the role of student.

===Archiving a forum===

A forum can be closed / archived so that students may no longer start new discussions, nor add replies, but can still read all the discussions by clicking the Prevent icon (X) for the student role for the capabilities 'Start new discussions' and 'Reply to posts'.

===Guests and posting in a forum===

There are certain things, such as posting in a forum, that guests are never allowed to do, despite the permissions interface suggesting otherwise.

The guest role has some special functionality, for example when a guest user attempts to post in a forum, they obtain the message "Sorry, guests are not allowed to post. Would you like to log in now with a full user account?"

(Note: If guests don't obtain the "Sorry, guests are not allowed to post" message because they have no reply link, then self enrolment needs enabling in ''Settings > Course administration > Users > Enrolment methods''.)

If you wish guests to be able to post in a forum, you can [[Manage roles|create a similar role]], say "visitor" with very few permissions allowed, then create an account and assign it the role of visitor. Guests can then share this visitor account.

''Anything else you'd like to achieve with a forum permissions change? Please add your suggestions to [[Talk:Forum settings]]!''

==User administration settings==

Users can choose whether or not to track unread posts in their profile settings under 'Forum tracking'. The settings are:

* Yes: highlight new posts for me
* No: don't keep track of posts I have seen

If the user chooses 'Yes: highlight new posts for me' and the forum administrator has set the 'Read tracking for this forum?' to On or Optional then the user will have new posts highlighted for them. The posts will be highlighted in the following places:

* My home page
* Main Course page
* Within the forum itself

[[Image:MoodleDocs forum_show_unread_behaviour.png|frame|center|Show unread on forum page]]

==Site administration settings==

The forum module has additional settings which may be changed by an administrator in ''Settings > Site administration > Plugins > Activity modules > Forum'' and, for 'Maximum time to edit posts', in ''Settings > Site administration > Security > Site policies''.

===Long and short posts===

The long and short post setting determine how forum posts on the site front page, social format course pages, and user profiles are displayed. (Note: There is currently an unresolved issue - "Site news - forum length setting has no effect for certain users" - MDL-4781.)

===Enabling timed posts===

Timed forum posts may be enabled i.e. having the option to set a display start and end date for a new discussion. Timed posts can then be created by users with the [[Capabilities/mod/forum:viewhiddentimedposts|capability to view hidden timed posts]] (normally admins and teachers).

===Maximum time to edit posts===

This specifies the amount of time people have to re-edit forum postings, glossary comments etc. Usually 30 minutes is a good value. The setting may be changed by an administrator in ''Settings > Site administration > Security > Site policies''.

===Mark post read after 'X' days===

This setting is forum_oldpostdays and specifies the number of days after which any post is considered to be read. E.g. If this is set to 14 days then any post older than 14 days will be considered read. If you set this to 0 then '''ALL''' posts are instantly considered to be read. If you don't want any posts to be considered read without the user reading them then set a high figure (e.g. 1000)

[[fr:Ajouter/modifier un forum]]
[[ja:フォーラムの追加/編集]]
[[de:Forum anlegen]]

ad-hoc contributed reports

2012-03-08T03:56:58Z

Cttxg: Attempt to categorise reports so it's easier to find them! No changes just headings added :)

==User and Role Report==
===Detailed ACTIONs for each ROLE (TEACHER,NONE-EDITING TEACHER and STUDENT)===
<code sql>
SELECT r.name,l.action, count( l.userid ) as counter
FROM `prefix_log` as l
JOIN `prefix_role_assignments` AS ra on l.userid = ra.userid
JOIN prefix_role AS r ON ra.roleid = r.id
WHERE ra.roleid IN (3,4,5)
GROUP BY roleid,l.action
ORDER BY counter desc
</code>

===LIST of all site USERS by COURSE enrollment (Moodle 1.9.x)===

Reports a site global list of all users enroled in each course
<code sql>
SELECT
user.firstname AS Firstname,
user.lastname AS Lastname,
user.email AS Email,
user.city AS City,
course.fullname AS Course
,(SELECT name FROM prefix_role WHERE id=asg.roleid)
FROM
prefix_user AS user,
prefix_course AS course,
prefix_role_assignments AS asg
INNER JOIN prefix_context AS context ON asg.contextid=context.id
WHERE
context.contextlevel = 50
AND
user.id=asg.userid
AND
context.instanceid=course.id
</code>

===LIST of all site USERS by COURSE enrollment (Moodle 2.x)===

<code sql>
SELECT
user2.firstname AS Firstname,
user2.lastname AS Lastname,
user2.email AS Email,
user2.city AS City,
course.fullname AS Course
,(SELECT shortname FROM prefix_role WHERE id=en.roleid) as Role
,(SELECT name FROM prefix_role WHERE id=en.roleid) as RoleName

FROM prefix_course as course
JOIN prefix_enrol AS en ON en.courseid = course.id
JOIN prefix_user_enrolments AS ue ON ue.enrolid = en.id
JOIN prefix_user AS user2 ON ue.userid = user2.id
</code>

===Permissions Overides on Categories===
(By: [http://moodle.org/mod/forum/discuss.php?d=153059#p712834 Séverin Terrier] )
<code sql>
SELECT rc.id, ct.instanceid, ccat.name, rc.roleid, rc.capability, rc.permission,
DATE_FORMAT( FROM_UNIXTIME( rc.timemodified ) , '%Y-%m-%d' ) AS timemodified, rc.modifierid, ct.instanceid, ct.path, ct.depth
FROM `prefix_role_capabilities` AS rc
INNER JOIN `prefix_context` AS ct ON rc.contextid = ct.id
INNER JOIN `prefix_course_categories` AS ccat ON ccat.id = ct.instanceid
AND `contextlevel` =40
</code>

===Lists "Totally Opened Courses" (visible, opened to guests, with no password)===
(By: [http://moodle.org/mod/forum/discuss.php?d=153059#p712837 Séverin Terrier] )
<code sql>
SELECT id , category , fullname , shortname , enrollable
FROM `prefix_course`
WHERE `guest` =1
AND `password` = ""
AND `visible` =1
</code>

===Lists "loggedin users" from the last 120 days===
<code sql>
SELECT id,username,FROM_UNIXTIME(`lastlogin`) as days
FROM `prefix_user`
WHERE DATEDIFF( NOW(),FROM_UNIXTIME(`lastlogin`) ) < 120
</code>

''and user count for that same population:''
<code sql>
SELECT COUNT(id) as Users FROM `prefix_user`
WHERE DATEDIFF( NOW(),FROM_UNIXTIME(`lastlogin`) ) < 120
</code>

===Students in all courses of some institute===
What is the status (deleted or not) of all Students (roleid = 5) in all courses of some Institute
<code sql>
SELECT c.id, c.fullname, u.firstname, u.lastname, u.deleted
FROM prefix_course AS c
JOIN prefix_context AS ctx ON c.id = ctx.instanceid
JOIN prefix_role_assignments AS ra ON ra.contextid = ctx.id
JOIN prefix_user AS u ON u.id = ra.userid
WHERE ra.roleid =5
AND ctx.instanceid = c.id
AND u.institution = 'please enter school name here'
</code>

===Full User info (for deleted users)===
Including extra custom profile fields (from mdl_user_info_data)
<code sql>
SELECT *
FROM prefix_user as u
JOIN prefix_user_info_data as uid ON uid.userid = u.id
JOIN prefix_user_info_field as uif ON (uid.fieldid = uif.id AND uif.shortname = 'class')
WHERE `deleted` = "1" and `institution`="your school name" and `department` = "your department" and `data` = "class level and number"
</code>

===User's courses===
change "u.id = 2" with a new user id
<code sql>
SELECT u.firstname, u.lastname, c.id, c.fullname
FROM prefix_course AS c
JOIN prefix_context AS ctx ON c.id = ctx.instanceid
JOIN prefix_role_assignments AS ra ON ra.contextid = ctx.id
JOIN prefix_user AS u ON u.id = ra.userid
WHERE u.id = 2
</code>

===Special Roles===
<code sql>
SELECT ra.roleid,r.name
,concat('<a target="_new" href="%%WWWROOT%%/course/user.php?id=1&user=',ra.userid,'">',u.firstname ,' ',u.lastname,'</a>') AS Username
,concat('<a target="_new" href="%%WWWROOT%%/course/view.php?id=',c.id,'">',c.fullname,'</a>') AS Course
FROM prefix_role_assignments AS ra
JOIN prefix_role AS r ON r.id = ra.roleid
JOIN prefix_user AS u ON u.id = ra.userid
JOIN prefix_context AS ctx ON (ctx.id = ra.contextid AND ctx.contextlevel = 50)
JOIN prefix_course AS c ON ctx.instanceid = c.id
WHERE ra.roleid > 6
</code>

===Courses without Teachers===
Actually, shows the number of Teachers in a course.
<code sql>
SELECT concat('<a target="_new" href="%%WWWROOT%%/course/view.php?id=',c.id,'">',c.fullname,'</a>') as Course
,(SELECT Count( ra.userid ) AS Users FROM prefix_role_assignments AS ra
JOIN prefix_context AS ctx ON ra.contextid = ctx.id
WHERE ra.roleid = 3 AND ctx.instanceid = c.id) AS Teachers
FROM prefix_course AS c
ORDER BY Teachers ASC
</code>

==Log Acivity Reports==
===Detailed "VIEW" ACTION for each ROLE (TEACHER,NONE-EDITING TEACHER and STUDENT)===
<code sql>
SELECT l.action, count( l.userid ) as counter , r.name
FROM `prefix_log` as l
JOIN `prefix_role_assignments` AS ra on l.userid = ra.userid
JOIN `prefix_role` AS r ON ra.roleid = r.id
WHERE (ra.roleid IN (3,4,5)) AND (l.action LIKE '%view%' )
GROUP BY roleid,l.action
order by r.name,counter desc
</code>

===Total Activity of Roles:"Teacher" and "None-Editing Teacher" by Dates and by Hours===
The output columns of this report table can be used as base for a Pivot-Table
which will show the amount of '''activity''' per '''hour''' per '''days''' in 3D graph view.

<code sql>
SELECT DATE_FORMAT( FROM_UNIXTIME( l.time ) , '%Y/%m/%d' ) AS grptimed ,
DATE_FORMAT( FROM_UNIXTIME( l.time ) , '%k' ) AS grptimeh , count( l.userid ) AS counter
FROM `prefix_log` AS l
JOIN prefix_user AS u ON u.id = l.userid
JOIN prefix_role_assignments AS ra ON l.userid = ra.userid
JOIN prefix_role AS r ON r.id = ra.roleid
WHERE ra.roleid IN (3,4)
GROUP BY grptimed,grptimeh
ORDER BY grptimed,grptimeh
</code>

===How many LOGINs per user and user's Activity===
+ link username to a user activity graph report
<code sql>
SELECT concat('<a target="_new" href="%%WWWROOT%%/course/user.php?id=1&user=',u.id,'&mode=alllogs">',u.firstname ,' ',u.lastname,'</a>') as Username
,count(*) as logins
,(SELECT count(*) FROM prefix_log WHERE userid = l.userid GROUP BY userid) as Activity
FROM prefix_log as l JOIN prefix_user as u ON l.userid = u.id
WHERE `action` LIKE '%login%' group by userid
ORDER BY Activity DESC
</code>

==Course Reports==
===Most Active courses===
<code sql>
SELECT COUNT(l.id) hits, l.course courseId, c.fullname coursename
FROM prefix_log l INNER JOIN prefix_course c ON l.course = c.id
GROUP BY courseId
ORDER BY hits DESC
</code>

===RESOURCE count for each COURSE===
<code sql>
SELECT COUNT(l.id) count, l.course, c.fullname coursename
FROM prefix_resource l INNER JOIN prefix_course c on l.course = c.id
GROUP BY course
ORDER BY count DESC
</code>

===Courses that are defined as using GROUPs===
<code sql>
SELECT concat('<a target="_new" href="%%WWWROOT%%/group/index.php?id=',c.id,'">',c.fullname,'</a>') AS Course
FROM `prefix_course` AS c
WHERE groupmode > 0
</code>

===List all Courses in and below a certain category===
Use this SQL code to retrieve all courses that exist in or under a set category.

$s should be the id of the category you want to know about...
<code sql>
SELECT prefix_course. * , prefix_course_categories. *
FROM prefix_course, prefix_course_categories
WHERE prefix_course.category = prefix_course_categories.id
AND (
prefix_course_categories.path LIKE '/$s/%'
OR prefix_course_categories.path LIKE '/$s'
)
</code>

===Blog activity per Course (not including VIEW)===
Filter activity logging to some specific Course Categories!
+ link course name to actual course (for quick reference)
(you can change %blog% to %wiki% to filter down all wiki activity or any other module you wish)
<code sql>
SELECT concat('<a target="_new" href="%%WWWROOT%%/course/view.php?id=',cm.course,'">',c.fullname,'</a>') as CourseID
,m.name ,count(cm.id) as counter
,(SELECT Count( ra.userid ) AS Users
FROM prefix_role_assignments AS ra
JOIN prefix_context AS ctx ON ra.contextid = ctx.id
WHERE ra.roleid = 5
AND ctx.instanceid = c.id
) AS Students
, ( SELECT count(id) FROM prefix_log WHERE `module` LIKE '%blog%' AND course = c.id AND action NOT LIKE '%view%' ) as BlogActivity
FROM `prefix_course_modules` as cm JOIN prefix_modules as m ON cm.module=m.id JOIN prefix_course as c ON cm.course = c.id
WHERE m.name LIKE '%blog%' AND c.category IN ( 8,13,15)
GROUP BY cm.course,cm.module order by counter desc
</code>

===All Courses which uploaded a Syllabus file===
+ under specific Category
+ show first Teacher in that course
+ link Course's fullname to actual course
<code sql>
SELECT
concat('<a target="_new" href="%%WWWROOT%%/course/view.php?id=',c.id,'">',c.fullname,'</a>') as Course
,c.shortname,r.name
,(SELECT CONCAT(u.firstname,' ', u.lastname) as Teacher
FROM prefix_role_assignments AS ra
JOIN prefix_context AS ctx ON ra.contextid = ctx.id
JOIN prefix_user as u ON u.id = ra.userid
WHERE ra.roleid = 3 AND ctx.instanceid = c.id LIMIT 1) as Teacher
FROM prefix_resource as r
JOIN prefix_course as c ON r.course = c.id
WHERE ( r.name LIKE '%סילבוס%' OR r.name LIKE '%סילאבוס%' OR r.name LIKE '%syllabus%' OR r.name LIKE '%תכנית הקורס%' )
AND c.category IN (10,18,26,13,28)
</code>

==Grade Reports==
===Site-Wide Grade Report with All Items===
Shows grades for all course items along with course totals for each student.
<code sql>
SELECT u.firstname AS 'First' , u.lastname AS 'Last', u.firstname + ' ' + u.lastname AS 'Display Name',
c.fullname AS 'Course',
cc.name AS 'Category',

CASE
WHEN gi.itemtype = 'course'
THEN c.fullname + ' Course Total'
ELSE gi.itemname
END AS 'Item Name',

ROUND(gg.finalgrade,2) AS Grade,
DATEADD(ss,gi.timemodified,'1970-01-01') AS Time

FROM prefix_course AS c
JOIN prefix_context AS ctx ON c.id = ctx.instanceid
JOIN prefix_role_assignments AS ra ON ra.contextid = ctx.id
JOIN prefix_user AS u ON u.id = ra.userid
JOIN prefix_grade_grades AS gg ON gg.userid = u.id
JOIN prefix_grade_items AS gi ON gi.id = gg.itemid
JOIN prefix_course_categories as cc ON cc.id = c.category

WHERE gi.courseid = c.id
ORDER BY lastname
</code>
For MySQL users, you'll need to use the MySQL DATE_ADD function instead of DATEADD:
<code>
DATE_ADD('1970-01-01', INTERVAL gi.timemodified SECONDS) AS Time
</code>

===Site-Wide Grade Report with Just Course Totals===
A second site-wide grade report for all students that just shows course totals.
<code sql>
SELECT u.firstname AS 'First' , u.lastname AS 'Last', u.firstname + ' ' + u.lastname AS 'Display Name',
cc.name AS 'Category',
CASE
WHEN gi.itemtype = 'course'
THEN c.fullname + ' Course Total'
ELSE gi.itemname
END AS 'Item Name',

ROUND(gg.finalgrade,2) AS Grade,
DATEADD(ss,gi.timemodified,'1970-01-01') AS Time

FROM prefix_course AS c
JOIN prefix_context AS ctx ON c.id = ctx.instanceid
JOIN prefix_role_assignments AS ra ON ra.contextid = ctx.id
JOIN prefix_user AS u ON u.id = ra.userid
JOIN prefix_grade_grades AS gg ON gg.userid = u.id
JOIN prefix_grade_items AS gi ON gi.id = gg.itemid
JOIN prefix_course_categories as cc ON cc.id = c.category

WHERE gi.courseid = c.id AND gi.itemtype = 'course'

ORDER BY lastname
</code>
For MySQL users, you'll need to use the MySQL DATE_ADD function instead of DATEADD:
<code>
DATE_ADD('1970-01-01', INTERVAL gi.timemodified SECONDS) AS Time
</code>

===Learner report by Learner with grades===
Which Learners in which course and what are the grades
<code sql>
SELECT u.firstname AS 'Name' , u.lastname AS 'Surname', c.fullname AS 'Course', cc.name AS 'Category',
CASE WHEN gi.itemtype = 'Course'
THEN c.fullname + ' Course Total'
ELSE gi.itemname
END AS 'Item Name', ROUND(gg.finalgrade,2) AS Score,ROUND(gg.rawgrademax,2) AS Max, ROUND(gg.finalgrade / gg.rawgrademax * 100 ,2) as Percentage,

if (ROUND(gg.finalgrade / gg.rawgrademax * 100 ,2) > 79,'Yes' , 'No') as Pass

FROM prefix_course AS c
JOIN prefix_context AS ctx ON c.id = ctx.instanceid
JOIN prefix_role_assignments AS ra ON ra.contextid = ctx.id
JOIN prefix_user AS u ON u.id = ra.userid
JOIN prefix_grade_grades AS gg ON gg.userid = u.id
JOIN prefix_grade_items AS gi ON gi.id = gg.itemid
JOIN prefix_course_categories AS cc ON cc.id = c.category
WHERE gi.courseid = c.id and gi.itemname != 'Attendance'
ORDER BY `Name` ASC
</code>

==Activity Module Reports==

===Detailed ACTIONs for each MODULE===
<code sql>
SELECT module,action,count(id) as counter
FROM prefix_log
GROUP BY module,action
ORDER BY module,counter desc
</code>

===Most popular ACTIVITY===
<code sql>
SELECT COUNT(l.id) hits, module
FROM prefix_log l
WHERE module != 'login' AND module != 'course' AND module != 'role'
GROUP BY module
ORDER BY hits DESC
</code>

===System wide use of ACTIVITIES and RESOURCES===
<code sql>
SELECT count( cm.id ) AS counter, m.name
FROM `prefix_course_modules` AS cm
JOIN prefix_modules AS m ON cm.module = m.id
GROUP BY cm.module
ORDER BY counter DESC
</code>

===LOG file ACTIONS per MODULE per COURSE (IDs)===
<code sql>
select course,module,action,count(action) as summa from prefix_log
where action <> 'new'
group by course,action,module
order by course,module,action
</code>

===System Wide usage count of various course Activities===
(Tested and works fine in Moodle 2.x)
Like: Forum, Wiki, Blog, Assignment, Database,
#Within specific category
#Teacher name in course

<code sql>
SELECT concat('<a target="_new" href="%%WWWROOT%%/course/view.php?id=',c.id,'">',c.fullname,'</a>') as Course

,(SELECT CONCAT(u.firstname,' ', u.lastname) AS Teacher
FROM prefix_role_assignments AS ra
JOIN prefix_context AS ctx ON ra.contextid = ctx.id
JOIN prefix_user AS u ON u.id = ra.userid
WHERE ra.roleid = 3 AND ctx.instanceid = c.id LIMIT 1) AS Teacher

,(SELECT count( m.name ) AS count FROM prefix_course_modules AS cm
JOIN prefix_modules AS m ON cm.module = m.id
WHERE cm.course = c.id AND m.name LIKE '%wiki%') AS Wikis
,(SELECT count( m.name ) AS count FROM prefix_course_modules AS cm
JOIN prefix_modules AS m ON cm.module = m.id
WHERE cm.course = c.id AND m.name LIKE '%blog%') AS Blogs

,(SELECT count( m.name ) AS count FROM
prefix_course_modules AS cm
JOIN prefix_modules AS m ON cm.module = m.id
WHERE cm.course = c.id AND m.name LIKE '%forum%') AS Forums

,(SELECT count( m.name ) AS count FROM prefix_course_modules AS cm
JOIN prefix_modules AS m ON cm.module = m.id
WHERE cm.course = c.id AND m.name LIKE '%data%') AS Databses

,(SELECT count( m.name ) AS count FROM prefix_course_modules AS cm
JOIN prefix_modules AS m ON cm.module = m.id
WHERE cm.course = c.id AND m.name LIKE '%assignment%') AS Assignments

,(SELECT Count( ra.userid ) AS Users FROM prefix_role_assignments AS ra
JOIN prefix_context AS ctx ON ra.contextid = ctx.id
WHERE ra.roleid = 5 AND ctx.instanceid = c.id) AS Students

FROM prefix_course AS c
WHERE c.category IN ( 18)
ORDER BY Wikis DESC,Blogs DESC, Forums DESC
</code>

===Detailed WIKI activity (per wiki per course)===
Including Number of Students in course (for reference)
<code sql>
SELECT concat('<a target="_new" href="%%WWWROOT%%/course/view.php?id=',cm.course,'">',c.fullname,'</a>') as CourseID
,(SELECT Count( ra.userid ) AS Users
FROM prefix_role_assignments AS ra
JOIN prefix_context AS ctx ON ra.contextid = ctx.id
WHERE ra.roleid = 5 AND ctx.instanceid = c.id ) AS Students
,m.name
, ( SELECT count(id) FROM prefix_log WHERE cmid = cm.id AND action LIKE '%updat%' ) as 'UPDAT E'
, ( SELECT count(id) FROM prefix_log WHERE cmid = cm.id AND action LIKE '%annotate%' ) as ANNOTATE
, ( SELECT count(id) FROM prefix_log WHERE cmid = cm.id AND action LIKE '%comment%' ) as COMMENT
, ( SELECT count(id) FROM prefix_log WHERE cmid = cm.id AND action LIKE '%add%' ) as 'A DD'
, ( SELECT count(id) FROM prefix_log WHERE cmid = cm.id AND action LIKE '%edit%' ) as EDIT
, ( SELECT count(id) FROM prefix_log WHERE cmid = cm.id AND action NOT LIKE '%view%' ) as 'All (NO View)'
FROM `prefix_course_modules` as cm
JOIN prefix_modules as m ON cm.module=m.id
JOIN prefix_course as c ON cm.course = c.id
WHERE m.name LIKE '%wiki%'
GROUP BY cm.course,cm.module
ORDER BY 'All (NO View)' DESC
</code>

===Wiki usage, system wide===
(you can filter the output by selecting some specific course categories : "WHERE c.category IN ( 8,13,15)")

<code sql>
SELECT concat('<a target="_new" href="%%WWWROOT%%/course/view.php?id=',c.id,'">',c.fullname,'</a>') as Course

,(SELECT count( m.name ) AS count FROM prefix_course_modules AS cm
JOIN prefix_modules AS m ON cm.module = m.id
WHERE cm.course = c.id AND m.name LIKE '%wiki%') AS Wikis

,(SELECT count(*) FROM prefix_log as l WHERE l.course = c.id AND l.module LIKE '%wiki%') AS 'WikiActivity<br/>ALL'

,(SELECT count(*) FROM prefix_log as l WHERE l.course = c.id AND l.module LIKE '%wiki%' and l.action LIKE '%add%' ) AS 'WikiActivity<br/>ADD'

,(SELECT count(*) FROM prefix_log as l WHERE l.course = c.id AND l.module LIKE '%wiki%' and l.action LIKE '%edit%' ) AS 'WikiActivity<br/>EDIT'

,(SELECT count(*) FROM prefix_log as l WHERE l.course = c.id AND l.module LIKE '%wiki%' and l.action LIKE '%annotate%' ) AS 'WikiActivity<br/>ANNOTATE'

,(SELECT count(*) FROM prefix_log as l WHERE l.course = c.id AND l.module LIKE '%wiki%' and l.action LIKE '%comments%' ) AS 'WikiActivity<br/>Comments'

,(SELECT Count( ra.userid ) AS Users FROM prefix_role_assignments AS ra
JOIN prefix_context AS ctx ON ra.contextid = ctx.id
WHERE ra.roleid = 5 AND ctx.instanceid = c.id) AS Students

,(SELECT count(*) FROM prefix_ouwiki_pages as ouwp
JOIN prefix_ouwiki as ouw ON ouw.id = ouwp.subwikiid
WHERE ouw.course = c.id GROUP BY ouw.course ) as OUWikiPages

,(SELECT count( DISTINCT nwp.pagename ) FROM prefix_wiki_pages AS nwp
JOIN prefix_wiki AS nw ON nw.id = nwp.dfwiki WHERE nw.course = c.id ) As NWikiPages

FROM prefix_course AS c
WHERE c.category IN ( 8,13,15)
HAVING Wikis > 0
ORDER BY 'WikiActivity<br/>ALL' DESC
</code>

===Aggregated Teacher activity by "WEB2" Modules===
(Tested and works fine in Moodle 2.x)
The NV column shows activity without VIEW log activity
<code sql>
SELECT ra.userid, u.firstname,u.lastname
,(SELECT count(*) FROM prefix_log as l WHERE l.userid = u.id AND l.module LIKE '%wiki%') AS Wiki
,(SELECT count(*) FROM prefix_log as l WHERE l.userid = u.id AND l.module LIKE '%wiki%' AND l.action NOT LIKE '%view%') AS Wiki_NV
,(SELECT count(*) FROM prefix_log as l WHERE l.userid = u.id AND l.module LIKE '%forum%') AS Forum
,(SELECT count(*) FROM prefix_log as l WHERE l.userid = u.id AND l.module LIKE '%forum%' AND l.action NOT LIKE '%view%') AS Forum_NV
,(SELECT count(*) FROM prefix_log as l WHERE l.userid = u.id AND l.module LIKE '%blog%') AS Blog
,(SELECT count(*) FROM prefix_log as l WHERE l.userid = u.id AND l.module LIKE '%blog%' AND l.action NOT LIKE '%view%') AS Blog_NV
,(SELECT count(*) FROM prefix_log as l WHERE l.userid = u.id AND l.module LIKE '%assignment%') AS Assignment
,(SELECT count(*) FROM prefix_log as l WHERE l.userid = u.id AND l.module LIKE '%assignment%' AND l.action NOT LIKE '%view%') AS Assignment_NV
FROM prefix_role_assignments AS ra
JOIN prefix_user AS u ON u.id = ra.userid
WHERE ra.roleid = 3
GROUP BY ra.userid
</code>

===List all the certificates issued, sort by variables in the custom profile fields===
Note: The SQL queries look intimidating at first, but isn't really that difficult to learn. I've seen in the forums that users wanted to do 'site-wide' groups in 1.9x. This is sort of the idea. It pulls all the certificates issued to all users sorted by the custom profile fields, which in my case is the Units or Depts (i.e. my site wide groups). Why certificates? I've explored with both grades and quizzes, the course admins are not really interested in the actual grades but whether the learner received a certificate (i.e. passed the course with x, y, z activities). It also saves me from creating groups and assigning them into the right groups. Even assigning in bulk is not efficient, since I have upward of 25 groups per course and constantly new learners enrolling in courses. The limitation is something to do with the server? as it only pull 5000 rows of data. If anyone figured out how to change this, please let me know. In the meantime, the work around is to pull only a few units/depts at a time to limit the number of rows. This is fine at the moment, since each course admin are only responsible for certain units/depts.

<code sql>
SELECT
DATE_FORMAT( FROM_UNIXTIME(prefix_certificate_issues.timecreated), '%Y/%m/%d' ) AS Date,
prefix_certificate_issues.classname AS Topic,
prefix_certificate.name AS Certificate,
prefix_certificate_issues.studentname as Name,
prefix_user_info_data.data AS Units

FROM
prefix_certificate_issues

INNER JOIN prefix_user_info_data
on prefix_certificate_issues.userid = prefix_user_info_data.userid

INNER JOIN prefix_certificate
on prefix_certificate_issues.certificateid = prefix_certificate.id

WHERE prefix_user_info_data.data='Unit 1'
OR prefix_user_info_data.data='Unit 2'
OR prefix_user_info_data.data='Unit 3'

ORDER BY Units, Name, Topic ASC
</code>

===Counter Blog usage in Courses,system wide===
What teachers in what courses, uses blogs and how many + student count in that course.
<code sql>

SELECT ( @counter := @counter+1) as counter,
concat('<a target="_new" href="%%WWWROOT%%/course/view.php?id=',c.id,'">',c.fullname,'</a>') as Course

,( SELECT DISTINCT CONCAT(u.firstname,' ',u.lastname)
FROM prefix_role_assignments AS ra
JOIN prefix_user AS u ON ra.userid = u.id
JOIN prefix_context AS ctx ON ctx.id = ra.contextid
WHERE ra.roleid = 3 AND ctx.instanceid = c.id AND ctx.contextlevel = 50 LIMIT 1) AS Teacher

,(SELECT count( m.name ) AS count FROM prefix_course_modules AS cm
JOIN prefix_modules AS m ON cm.module = m.id
WHERE cm.course = c.id AND m.name LIKE '%blog%') AS Blogs

,(SELECT Count( ra.userid ) AS Users FROM prefix_role_assignments AS ra
JOIN prefix_context AS ctx ON ra.contextid = ctx.id
WHERE ra.roleid = 5 AND ctx.instanceid = c.id) AS Students

FROM prefix_course AS c, (SELECT @counter := 0) as s_init
WHERE c.category IN ( 8,13,15)
HAVING Blogs > 0
ORDER BY Blogs DESC
</code>

==Assignment Module Reports==
===All Ungraded Assignments===
Returns all the submitted assignments that still need grading
<code sql>
select
u.firstname AS "First",
u.lastname AS "Last",
c.fullname AS "Course",
a.name AS "Assignment"

from prefix_assignment_submissions as asb
join prefix_assignment as a ON a.id = asb.assignment
join prefix_user as u ON u.id = asb.userid
join prefix_course as c ON c.id = a.course
join prefix_course_modules as cm ON c.id = cm.course

where asb.grade < 0 and cm.instance = a.id
and cm.module = 1

order by c.fullname, a.name, u.lastname
</code>

===All Ungraded Assignments w/ Link===
Returns all the submitted assignments that still need grading, along with a link that goes directly to the submission to grade it. The links work if you view the report within Moodle.
<code sql>
select
u.firstname AS "First",
u.lastname AS "Last",
c.fullname AS "Course",
a.name AS "Assignment",

'<a href="http://education.varonis.com/mod/assignment/submissions.php' + char(63) +
+ 'id=' + cast(cm.id as varchar) + '&userid=' + cast(u.id as varchar)
+ '&mode=single&filter=0&offset=2">' + a.name + '</a>'
AS "Assignmentlink"

from prefix_assignment_submissions as asb
join prefix_assignment as a ON a.id = asb.assignment
join prefix_user as u ON u.id = asb.userid
join prefix_course as c ON c.id = a.course
join prefix_course_modules as cm ON c.id = cm.course

where asb.grade < 0 and cm.instance = a.id and cm.module = 1

order by c.fullname, a.name, u.lastname
</code>

===Who is using "Single File Upload" assignment===
<code sql>
SELECT
concat('<a target="_new" href="%%WWWROOT%%/course/view.php?id=',c.id,'">',c.fullname,'</a>') AS Course

,(SELECT CONCAT(u.firstname,' ', u.lastname) AS Teacher
FROM prefix_role_assignments AS ra
JOIN prefix_context AS ctx ON ra.contextid = ctx.id
JOIN prefix_user AS u ON u.id = ra.userid
WHERE ra.roleid = 3 AND ctx.instanceid = c.id LIMIT 1) AS Teacher

,ass.name as "Assignment Name"

FROM
prefix_assignment as ass

JOIN
prefix_course as c ON c.id = ass.course

WHERE `assignmenttype` LIKE 'uploadsingle'
</code>

==Resource Module Reports==
===List "Recently uploaded files"===
see what users are uploading
<code sql>
SELECT FROM_UNIXTIME(time,'%Y %M %D %h:%i:%s') as time ,ip,userid,url,info
FROM `prefix_log`
WHERE `action` LIKE 'upload'
ORDER BY `prefix_log`.`time` DESC
</code>

===List Courses that loaded a specific file: "X"===
Did the Teacher (probably) uploaded course's Syllabus ?
<code sql>
SELECT c.id, c.fullname FROM `prefix_log` as l
JOIN prefix_course as c ON c.id = l.course
WHERE `action` LIKE '%upload%' AND ( info LIKE '%Syllabus%' OR info LIKE '%Sylabus%' ) GROUP BY c.id
</code>

===All resources that link to some specific external website===
+ link to course
+ who's the teacher
+ link to external resource
<code sql>
SELECT
concat('<a target="_new" href="%%WWWROOT%%/course/view.php?id=',c.id,'">',c.fullname,'</a>') AS Course
,c.shortname,r.name
,(SELECT CONCAT(u.firstname,' ', u.lastname) AS Teacher
FROM prefix_role_assignments AS ra
JOIN prefix_context AS ctx ON ra.contextid = ctx.id
JOIN prefix_user AS u ON u.id = ra.userid
WHERE ra.roleid = 3 AND ctx.instanceid = c.id LIMIT 1) AS Teacher
,concat('<a target="_new" href="%%WWWROOT%%/mod/resource/view.php?id=',r.id,'">',r.name,'</a>') AS Resource
FROM prefix_resource AS r
JOIN prefix_course AS c ON r.course = c.id
WHERE r.reference LIKE 'http://info.oranim.ac.il/home%'
</code>

==="Compose Web Page" RESOURCE count===
<code sql>
SELECT course,prefix_course.fullname, COUNT(*) AS Total
FROM `prefix_resource`
JOIN `prefix_course` ON prefix_course.id = prefix_resource.course
WHERE type='html'
GROUP BY course
</code>

===Resource count in courses===
+ (First)Teacher name
+ Where course is inside some specific Categories
<code sql>
SELECT
COUNT(*) AS count
,r.course
,c.shortname shortname
,c.fullname coursename
,( SELECT DISTINCT CONCAT(u.firstname,' ',u.lastname)
FROM prefix_role_assignments AS ra
JOIN prefix_user as u ON ra.userid = u.id
JOIN prefix_context AS ctx ON ctx.id = ra.contextid
WHERE ra.roleid = 3 AND ctx.instanceid = r.course AND ctx.contextlevel = 50 LIMIT 1) AS Teacher
FROM prefix_resource r
JOIN prefix_course c ON r.course = c.id
WHERE c.category IN (10,13,28,18,26)
GROUP BY r.course
ORDER BY COUNT(*) DESC
</code>

==Forum Module Reports==
===FORUM use Count per COURSE -- not including NEWS Forum!===
<code sql>
SELECT prefix_course.fullname, prefix_forum.course, count(*) as total FROM prefix_forum
INNER JOIN prefix_course
ON prefix_course.id = prefix_forum.course
WHERE NOT(prefix_forum.type = 'news')
GROUP BY prefix_forum.course
ORDER BY total desc
</code>

===FORUM use Count per COURSE by type -- not including NEWS Forum!===
<code sql>
SELECT prefix_course.fullname, prefix_forum.course, prefix_forum.type, count(*) as total FROM prefix_forum
INNER JOIN prefix_course
ON prefix_course.id = prefix_forum.course
WHERE NOT(prefix_forum.type = 'news')
GROUP BY prefix_forum.course,prefix_forum.type
ORDER BY total desc
</code>

===Activity In Forums===
Trying to figure out how much real activity we have in Forums by aggregating:
Users in Course, Number of Posts, Number of Discussions, Unique student post, Unique student discussions, Number of Teachers , Number of Students, ratio between unique Student posts and the number of students in the Course...
<code sql>
SELECT c.fullname,f.name,f.type
,(SELECT count(id) FROM prefix_forum_discussions as fd WHERE f.id = fd.forum) as Discussions
,(SELECT count(distinct fd.userid) FROM prefix_forum_discussions as fd WHERE fd.forum = f.id) as UniqueUsersDiscussions
,(SELECT count(fp.id) FROM prefix_forum_discussions fd JOIN prefix_forum_posts as fp ON fd.id = fp.discussion WHERE f.id = fd.forum) as Posts
,(SELECT count(distinct fp.userid) FROM prefix_forum_discussions fd JOIN prefix_forum_posts as fp ON fd.id = fp.discussion WHERE f.id = fd.forum) as UniqueUsersPosts
,(SELECT Count( ra.userid ) AS Students
FROM prefix_role_assignments AS ra
JOIN prefix_context AS ctx ON ra.contextid = ctx.id
WHERE ra.roleid =5
AND ctx.instanceid = c.id
) AS StudentsCount
,(SELECT Count( ra.userid ) AS Teachers
FROM prefix_role_assignments AS ra
JOIN prefix_context AS ctx ON ra.contextid = ctx.id
WHERE ra.roleid =3
AND ctx.instanceid = c.id
) AS 'Teacher<br/>Count'
,(SELECT Count( ra.userid ) AS Users
FROM prefix_role_assignments AS ra
JOIN prefix_context AS ctx ON ra.contextid = ctx.id
WHERE ra.roleid IN (3,5)
AND ctx.instanceid = c.id
) AS UserCount
, (SELECT (UniqueUsersDiscussions / StudentsCount )) as StudentDissUsage
, (SELECT (UniqueUsersPosts /StudentsCount)) as StudentPostUsage
FROM prefix_forum as f
JOIN prefix_course as c ON f.course = c.id
WHERE `type` != 'news'
ORDER BY StudentPostUsage DESC
</code>

===All Forum type:NEWS===
<code sql>
SELECT f.id, f.name
FROM prefix_course_modules AS cm
JOIN prefix_modules AS m ON cm.module = m.id
JOIN prefix_forum AS f ON cm.instance = f.id
WHERE m.name = 'forum'
AND f.type = 'news'
</code>

===All new forum NEWS items (discussions) from all my Courses===
change "userid = 26" and "id = 26" to a new user id
<code sql>
SELECT c.shortname,f.name,fd.name,FROM_UNIXTIME(fd.timemodified ,"%d %M %Y ") as Date
FROM prefix_forum_discussions as fd
JOIN prefix_forum as f ON f.id = fd.forum
JOIN prefix_course as c ON c.id = f.course
JOIN prefix_user_lastaccess as ul ON (c.id = ul.courseid AND ul.userid = 26)
WHERE fd.timemodified > ul.timeaccess
AND fd.forum IN (SELECT f.id
FROM prefix_course_modules AS cm
JOIN prefix_modules AS m ON cm.module = m.id
JOIN prefix_forum AS f ON cm.instance = f.id
WHERE m.name = 'forum'
AND f.type = 'news')
AND c.id IN (SELECT c.id
FROM prefix_course AS c
JOIN prefix_context AS ctx ON c.id = ctx.instanceid
JOIN prefix_role_assignments AS ra ON ra.contextid = ctx.id
JOIN prefix_user AS u ON u.id = ra.userid
WHERE u.id = 26) ORDER BY `fd`.`timemodified` DESC
</code>

===News Forum - Discussions COUNT===
Which is actually... How much instructions students get from their teachers
<code sql>
SELECT c.shortname ,
concat('<a target="_new" href="%%WWWROOT%%/course/view.php?id=',c.id,'">',c.fullname,'</a>') AS Course
,( SELECT DISTINCT CONCAT(u.firstname,' ',u.lastname)
FROM prefix_role_assignments AS ra
JOIN prefix_user AS u ON ra.userid = u.id
JOIN prefix_context AS ctx ON ctx.id = ra.contextid
WHERE ra.roleid = 3 AND ctx.instanceid = c.id AND ctx.contextlevel = 50 LIMIT 1) AS Teacher
,concat('<a target="_new" href="%%WWWROOT%%/mod/forum/view.php?f=',fd.forum,'">',count(fd.id),'</a>') AS DiscussionsSum
FROM prefix_forum_discussions AS fd
INNER JOIN prefix_forum AS f ON f.id = fd.forum
INNER JOIN prefix_course AS c ON c.id = f.course
WHERE f.type = 'news' AND c.category IN (10,13,28,18,26)
GROUP BY fd.forum
ORDER BY count(fd.id) DESC
</code>

==Quiz Module Reports==
===Generate a list of instructors and their email addresses for those courses that has "essay questions" in their quizzes===
<code sql>
SELECT qu.id AS quiz_id, qu.course AS course_id, qu.questions,
co.fullname AS course_fullname, co.shortname AS course_shortname,
qu.name AS quiz_name, FROM_UNIXTIME(qu.timeopen) AS quiz_timeopen, FROM_UNIXTIME(qu.timeclose) AS quiz_timeclose,
u.firstname, u.lastname, u.email,
FROM mdl_quiz qu, mdl_course co, mdl_role re, mdl_context ct, mdl_role_assignments ra, mdl_user u
WHERE FROM_UNIXTIME(timeopen) > '2008-05-14' AND
qu.course = co.id AND
co.id = ct.instanceid AND
ra.roleid = re.id AND
re.name = 'Teacher' AND
ra.contextid = ct.id AND
ra.userid = u.id

SELECT Count('x') As NumOfStudents
FROM mdl_role_assignments a
JOIN mdl_user u ON userid = u.id
WHERE roleid = 5 AND contextid = (SELECT id FROM mdl_context WHERE instanceid = 668 AND contextlevel = 50)
</code>

enrol/manual/edit

2011-11-11T03:48:47Z

Cttxg: adding link to Manual Enrolment page

See [[Manual_enrolment]]

admin/setting/additionalhtml

2011-11-01T00:44:47Z

Cttxg: adding information to auto-linked page

== Additional HTML ==

These settings allow you to specify HTML that you want added to every page without altering the Moodle code files.

You can add HTML will be added within the HEAD tag for the page, immediately after the BODY tag has been opened, or immediately before the body tag is closed.

Doing this allows you add custom headers or footers on every page, or add support for services like Google Analytics very easily and independent of your chosen theme.

== See also ==
[[Site_appearance|Site appearance]] menu on Moodle Docs

[[Category:Site administration]]

Dialogue module

2011-10-31T20:11:11Z

Cttxg: /* Module History */ adding 2011 2.0x support

'''Dialogues''' allow students or teachers to start two-way dialogues with another person. They are course activities that can be useful when the teacher wants a place to give private feedback to a student on their online activity. For example, if a student is participating in a language forum and made a grammatical error that the teacher wants to point out without embarassing the student, a dialogue is the perfect place. A dialogue activity would also be an excellent way for counsellors within an institution to interact with students - all activities are logged and email is not necessarily required.

Dialogue is a contributed activity module originally released for Moodle 1.6.x. and subsequently updated for Moodle 1.8.x to support roles and capabilities and most recently updated to support Moodle 1.9.x, 2.0x and Groupings (groups of groups)

==Features==
* Teachers can initiate private Dialogues between themselves and individual students
* Teachers can initiate individual Dialogues with all members of a group at one time
* Users can attach documents to their dialogue posts
* Students can view a time-stamped history of interaction between themselves and their teachers / tutors within the context of papers.
* Teachers and Students can view time-stamped histories of the interaction between them. Teachers can additionally view interaction histories with all students within a particular paper.
* Users can receive notification of new Dialogue posts via e-mail subscription
* Students can edit Dialogue posts within a specified period of time (30min default).

==Settings==
[[Image:DialogueSettings.gif|thumb|Dialogue Settings]]
* Type of dialogue can be set to Teacher-Student, Student-Student, Anyone-Anyone
* Ability for Students (or any role) to initiate a Dialogue can be managed in the activity role overrides
* Can configure whether a Dialogue activity should allow more than one Dialogue between any two participants
* Can enable/disable email notification
* Can set the number of days after which a closed Dialogue will be removed
* Admin setting at site-level to control display of unread dialog count on course pages

==Roles/Capabilities==
The following capabilities are able to be assigned/set against site wide roles and overridden in your local Dialogue instances:
* mod/dialogue:open
* mod/dialogue:close
* mod/dialogue:manage
* mod/dialogue:viewall - allow users to have read access to dialogues which they are not a participant
* mod/dialogue:participate
* mod/dialogue:participateany - allows users to participate in dialogues that are not initiated with themselves

==Tips and tricks==
*When students initially enroll on a site, it might be a good idea to send them a welcome dialogue to let them know the teacher is there. This way if the student has something to say to the teacher, they will feel more comfortable responding, since the teacher made the first step.

==Module History==
* 2003/Oct - Ray Kingdon released the original module
* 2004/Jun - Dialogues with groups of students were supported
* 2006/Apr - Howard Miller (aka thepurpleblob) University of Glasgow, contributed fixes to bring Dialogue in line w v1.6
* 2006/Aug - Howard Miller volunteered to maintain the module. At the time he mentioned Messaging was the mechanism MartinD saw as the tool the core project would be supporting for this sort of activity, and that Dialogue was never actually intended to be anything other than an optional module.
* 2007/May - Clinton Graham provided a diff to get Dialogue running with roles in v1.8
* 2007 - Catalyst integrated group support allowing allocation of groups (or groupings) to specific activities.
* 2007/Aug - University of Waikato contract Catalyst to update Dialogue module to support v1.9 and make a number of feature changes
* 2008/Aug - Reinstated dialogue type selector, various bug fixes (Enrique,Clinton,Lorenzo & Dean)
* 2009/Feb - Improvements to student-to-student mode and all-participants selection for teachers (Dean)
* 2009/Mar - Reintroduced unread entries tracking, and validation fix on edittime field (Dean)
* 2009/Aug - Multiple fixes and improvements (Dean. With lots of contributed code/inspiration here from Enrique Castro)
** fixed bug re lost HTML formatting (see: CONTRIB-1448)
** sorting columns by name, date, post count etc (see: CONTRIB-1449)
** improved group-mode support (see: CONTRIB-1490)
** added participation report support (see: CONTRIB-1454)
** change to view current conversation after update rather than go back to list (see: CONTRIB-1455)
** lots of codeing/style improvments, thanx Petr :) (see: CONTRIB-1216)
* 2011/Oct - Troy Williams updated to support v2.0x

== Possible Future Developments ==
Following is a list of future developments (in priority order). Please feel free to [http://moodle.org/mod/forum/discuss.php?d=126340 discuss these developments] and vote for these if you feel the priority order is not quite right. We also ask that you add to this list:

CONTRIB-1450 Email Notifications includes:
* Option to send immediately (rather than wait 30 mins)
* Option to include the dialogue message content in the email notification

CONTRIB-1451 Change to entry header to include user's name & increase font
* Instead of "On Friday, 1 June 2009, 05:43 pm you wrote: ", would it be better that the name is displayed instead, if the dialogue was exported and archived and the people who are reading it would not know the "you" is referring to who.

CONTRIB-1452 Close conversations for unenrolled students & display date
* Close Dialogue conversations when students are unenrolled
* Display the date that the individual dialogue was closed. the last entry date is good, but sometimes the close date is not always the last entry date.
* Display the date that the closed dialogue would be removed.

CONTRIB-1453 Provide edit & delete for Manage capability (similar to forums)<br />

'''Other requests with no tracker items created''' - see page Page Comments for more details
* Let the user specified the end date for the closed dialogue to be removed. Which I think it would be more flexible rather than the 7, 30,...,365 days options.
* Export entries (what format - Text, Html, xml??)
* Display the date that the dialogue was added
* Don't display the "You have 30 mins to edit..." after submit, instead the user should be bought to the current dialogue and allowed to edit it even if it has passed 30mins limit.

== See also ==
* [http://moodle.org/mod/forum/view.php?id=854 Dialogue module forum] - discuss the module here
* [http://cvs.moodle.org/contrib/plugins/mod/dialogue/ CVS Repository] - browse and download the code
* [http://moodle.org/mod/data/view.php?d=13&rid=258 Dialogue Module entry at moodle.org]
* [http://download.moodle.org/download.php/docs/en/using_moodle/ch4_forums.pdf Chapter 4: Using Forums, Chats and Dialogues]
* [https://docs.moodle.org/en/Development:Dialogue_2.0_specification Development:Dialogue 2.0 specification]

[[Category:Contributed code]]

Dialogue module

2011-10-31T20:09:13Z

Cttxg: added 2.0x support in introduction

'''Dialogues''' allow students or teachers to start two-way dialogues with another person. They are course activities that can be useful when the teacher wants a place to give private feedback to a student on their online activity. For example, if a student is participating in a language forum and made a grammatical error that the teacher wants to point out without embarassing the student, a dialogue is the perfect place. A dialogue activity would also be an excellent way for counsellors within an institution to interact with students - all activities are logged and email is not necessarily required.

Dialogue is a contributed activity module originally released for Moodle 1.6.x. and subsequently updated for Moodle 1.8.x to support roles and capabilities and most recently updated to support Moodle 1.9.x, 2.0x and Groupings (groups of groups)

==Features==
* Teachers can initiate private Dialogues between themselves and individual students
* Teachers can initiate individual Dialogues with all members of a group at one time
* Users can attach documents to their dialogue posts
* Students can view a time-stamped history of interaction between themselves and their teachers / tutors within the context of papers.
* Teachers and Students can view time-stamped histories of the interaction between them. Teachers can additionally view interaction histories with all students within a particular paper.
* Users can receive notification of new Dialogue posts via e-mail subscription
* Students can edit Dialogue posts within a specified period of time (30min default).

==Settings==
[[Image:DialogueSettings.gif|thumb|Dialogue Settings]]
* Type of dialogue can be set to Teacher-Student, Student-Student, Anyone-Anyone
* Ability for Students (or any role) to initiate a Dialogue can be managed in the activity role overrides
* Can configure whether a Dialogue activity should allow more than one Dialogue between any two participants
* Can enable/disable email notification
* Can set the number of days after which a closed Dialogue will be removed
* Admin setting at site-level to control display of unread dialog count on course pages

==Roles/Capabilities==
The following capabilities are able to be assigned/set against site wide roles and overridden in your local Dialogue instances:
* mod/dialogue:open
* mod/dialogue:close
* mod/dialogue:manage
* mod/dialogue:viewall - allow users to have read access to dialogues which they are not a participant
* mod/dialogue:participate
* mod/dialogue:participateany - allows users to participate in dialogues that are not initiated with themselves

==Tips and tricks==
*When students initially enroll on a site, it might be a good idea to send them a welcome dialogue to let them know the teacher is there. This way if the student has something to say to the teacher, they will feel more comfortable responding, since the teacher made the first step.

==Module History==
* 2003/Oct - Ray Kingdon released the original module
* 2004/Jun - Dialogues with groups of students were supported
* 2006/Apr - Howard Miller (aka thepurpleblob) University of Glasgow, contributed fixes to bring Dialogue in line w v1.6
* 2006/Aug - Howard Miller volunteered to maintain the module. At the time he mentioned Messaging was the mechanism MartinD saw as the tool the core project would be supporting for this sort of activity, and that Dialogue was never actually intended to be anything other than an optional module.
* 2007/May - Clinton Graham provided a diff to get Dialogue running with roles in v1.8
* 2007 - Catalyst integrated group support allowing allocation of groups (or groupings) to specific activities.
* 2007/Aug - University of Waikato contract Catalyst to update Dialogue module to support v1.9 and make a number of feature changes
* 2008/Aug - Reinstated dialogue type selector, various bug fixes (Enrique,Clinton,Lorenzo & Dean)
* 2009/Feb - Improvements to student-to-student mode and all-participants selection for teachers (Dean)
* 2009/Mar - Reintroduced unread entries tracking, and validation fix on edittime field (Dean)
* 2009/Aug - Multiple fixes and improvements (Dean. With lots of contributed code/inspiration here from Enrique Castro)
** fixed bug re lost HTML formatting (see: CONTRIB-1448)
** sorting columns by name, date, post count etc (see: CONTRIB-1449)
** improved group-mode support (see: CONTRIB-1490)
** added participation report support (see: CONTRIB-1454)
** change to view current conversation after update rather than go back to list (see: CONTRIB-1455)
** lots of codeing/style improvments, thanx Petr :) (see: CONTRIB-1216)

== Possible Future Developments ==
Following is a list of future developments (in priority order). Please feel free to [http://moodle.org/mod/forum/discuss.php?d=126340 discuss these developments] and vote for these if you feel the priority order is not quite right. We also ask that you add to this list:

CONTRIB-1450 Email Notifications includes:
* Option to send immediately (rather than wait 30 mins)
* Option to include the dialogue message content in the email notification

CONTRIB-1451 Change to entry header to include user's name & increase font
* Instead of "On Friday, 1 June 2009, 05:43 pm you wrote: ", would it be better that the name is displayed instead, if the dialogue was exported and archived and the people who are reading it would not know the "you" is referring to who.

CONTRIB-1452 Close conversations for unenrolled students & display date
* Close Dialogue conversations when students are unenrolled
* Display the date that the individual dialogue was closed. the last entry date is good, but sometimes the close date is not always the last entry date.
* Display the date that the closed dialogue would be removed.

CONTRIB-1453 Provide edit & delete for Manage capability (similar to forums)<br />

'''Other requests with no tracker items created''' - see page Page Comments for more details
* Let the user specified the end date for the closed dialogue to be removed. Which I think it would be more flexible rather than the 7, 30,...,365 days options.
* Export entries (what format - Text, Html, xml??)
* Display the date that the dialogue was added
* Don't display the "You have 30 mins to edit..." after submit, instead the user should be bought to the current dialogue and allowed to edit it even if it has passed 30mins limit.

== See also ==
* [http://moodle.org/mod/forum/view.php?id=854 Dialogue module forum] - discuss the module here
* [http://cvs.moodle.org/contrib/plugins/mod/dialogue/ CVS Repository] - browse and download the code
* [http://moodle.org/mod/data/view.php?d=13&rid=258 Dialogue Module entry at moodle.org]
* [http://download.moodle.org/download.php/docs/en/using_moodle/ch4_forums.pdf Chapter 4: Using Forums, Chats and Dialogues]
* [https://docs.moodle.org/en/Development:Dialogue_2.0_specification Development:Dialogue 2.0 specification]

[[Category:Contributed code]]

Plik:edit-section-summary.png

2011-09-15T23:59:15Z

Cttxg: Editing a course section summary

Editing a course section summary

Section summary

2011-09-15T23:57:43Z

Cttxg: adding info re default section name and an image

The very top of your course (the General section) and every topic or week contains a summary. This is a default label which allows you to place information about the specific topic or week. It could be an introduction to the unit of study or a short summary of the weekly plan. Activities and resources are listed below this section.

Because the information you add to the summary appears as a label, it should be very short so that the course page doesn't become too long. If you find yourself wanting to say more than a sentence or two then consider adding a resource to this topic instead (for example, the first activity might be a page called About This Topic).

To provide a custom section title in the Navigation menu untick the "Use default section name" and include the title in the 'Section Name' text box. If you leave the default section name the navigation menu will contain 'General' for the general section and either 'Topic 1', 'Topic 2', etc for Topics format or the Week dates for Weekly format.

[[Image:edit-section-summary.png|frame|center|Edit Section Summary]]

[[Category:Course]]

Administration block

2011-09-09T03:58:28Z

Cttxg:

{{Moodle site - basic structure}}

The settings block is new to Moodle 2.0. It can be found on most pages in the left column. It is composed of links to sub menus. When the link is clicked the sub menu expands below it.

Many of the sub menus have the same functions as older versions of Moodle.

What appears in the setting block depends upon the [[Context]] (Page being shown and user's permissions). For example, the site administrator will notice the Front Page settings block has fewer options than the Course settings block and a student will have fewer options in the Course administration than a teacher.

Here are two unexpanded examples of the settings block:
<gallery widths="200px" heights="200px" perrow="2">

Image:Settings block FrontPage collapsed.png|FrontPage settings block
Image:Settings block Course collapsed.png|Course settings block
</gallery>

==Settings block menus==
The main menu items (Front page settings, Course Administration, My profile settings and Site Administration) contain a submenu and can be collapsed or expanded to display the (typical) full menu as shown below:
*[[Front_page_settings_block|Front page settings]]
**Turn edit on/off
**Edit settings
**Users
**Filters
**Backup
**Restore
**Questions
**Files

*[[Course_administration_menu|Course administration]]
**Turn editing on
**Edit settings
**Users
**Filters
**Grades
**Backup
**Restore
**Import
**Publish
**Reset
**Question bank

*[[Profile |My profile settings]]
**Edit profile
**Change password
**Roles
**Portfolios (if available at site level)
**Security keys
**Messaging
**Blogs
**Make this my default home page (if set at site level)

*[[Site_administration|Site administration]]
**Notifications
**Registration
**Advanced features
**Users
**Courses
**Grades
**Location
**Language
**Plugins
**Security
**Appearance
**Front page
**Server
**Reports
**Development
**Question engine upgrade helper

==See also==

[[Category:Block]]

[[eu:Ezarpenak_blokea]]
[[de:Einstellungen (Block)]]

Plik:Settings block Course collapsed.png

2011-09-09T02:22:37Z

Cttxg: uploaded a new version of "File:Settings block Course collapsed.png": Reverted to version as of 02:19, 9 September 2011

Plik:Settings block Course collapsed.png

2011-09-09T02:21:26Z

Cttxg: uploaded a new version of "File:Settings block Course collapsed.png"

Plik:Settings block Course collapsed.png

2011-09-09T02:19:40Z

Cttxg: uploaded a new version of "File:Settings block Course collapsed.png": new version with no Add Resource / Add Activity options

Administration block

2011-09-09T02:11:35Z

Cttxg: replacing edit settings with basic structure

{{Moodle site - basic structure}}

The settings block is new to Moodle 2.0. It can be found on most pages in the left column. It is composed of links to sub menus. When the link is clicked the sub menu expands below it.

Many of the sub menus have the same functions as older versions of Moodle.

What appears in the setting block depends upon the [[Context]] (Page being shown and user's permissions). For example, the site administrator will notice the Front Page settings block has fewer options than the Course settings block and a student will have fewer options in the Course administration than a teacher.

Here are two unexpanded examples of the settings block:
<gallery widths="200px" heights="275px" perrow="2">

Image:Settings block FrontPage collapsed.png|FrontPage settings block
Image:Settings block Course collapsed.png|Course settings block
</gallery>

==Settings block menus==
The main menu items (Front page settings, Course Administration, My profile settings and Site Administration) contain a submenu and can be collapsed or expanded to display the (typical) full menu as shown below:
*[[Front_page_settings_block|Front page settings]]
**Turn edit on/off
**Edit settings
**Users
**Filters
**Backup
**Restore
**Questions
**Files

*[[Course_administration_menu|Course administration]]
**Turn editing on
**Edit settings
**Users
**Filters
**Grades
**Backup
**Restore
**Import
**Publish
**Reset
**Question bank

*[[Profile |My profile settings]]
**Edit profile
**Change password
**Roles
**Portfolios (if available at site level)
**Security keys
**Messaging
**Blogs
**Make this my default home page (if set at site level)

*[[Site_administration|Site administration]]
**Notifications
**Registration
**Advanced features
**Users
**Courses
**Grades
**Location
**Language
**Plugins
**Security
**Appearance
**Front page
**Server
**Reports
**Development
**Question engine upgrade helper

==See also==

[[Category:Block]]

[[eu:Ezarpenak_blokea]]
[[de:Einstellungen (Block)]]

Administration block

2011-09-09T02:11:04Z

Cttxg: Undo revision 89362 by Cttxg (talk)

{{Editing settings}}

The settings block is new to Moodle 2.0. It can be found on most pages in the left column. It is composed of links to sub menus. When the link is clicked the sub menu expands below it.

Many of the sub menus have the same functions as older versions of Moodle.

What appears in the setting block depends upon the [[Context]] (Page being shown and user's permissions). For example, the site administrator will notice the Front Page settings block has fewer options than the Course settings block and a student will have fewer options in the Course administration than a teacher.

Here are two unexpanded examples of the settings block:
<gallery widths="200px" heights="275px" perrow="2">

Image:Settings block FrontPage collapsed.png|FrontPage settings block
Image:Settings block Course collapsed.png|Course settings block
</gallery>

==Settings block menus==
The main menu items (Front page settings, Course Administration, My profile settings and Site Administration) contain a submenu and can be collapsed or expanded to display the (typical) full menu as shown below:
*[[Front_page_settings_block|Front page settings]]
**Turn edit on/off
**Edit settings
**Users
**Filters
**Backup
**Restore
**Questions
**Files

*[[Course_administration_menu|Course administration]]
**Turn editing on
**Edit settings
**Users
**Filters
**Grades
**Backup
**Restore
**Import
**Publish
**Reset
**Question bank

*[[Profile |My profile settings]]
**Edit profile
**Change password
**Roles
**Portfolios (if available at site level)
**Security keys
**Messaging
**Blogs
**Make this my default home page (if set at site level)

*[[Site_administration|Site administration]]
**Notifications
**Registration
**Advanced features
**Users
**Courses
**Grades
**Location
**Language
**Plugins
**Security
**Appearance
**Front page
**Server
**Reports
**Development
**Question engine upgrade helper

==See also==

[[Category:Block]]

[[eu:Ezarpenak_blokea]]
[[de:Einstellungen (Block)]]

Administration block

2011-09-09T02:10:34Z

Cttxg: removing edit settings menu as not applicable here

The settings block is new to Moodle 2.0. It can be found on most pages in the left column. It is composed of links to sub menus. When the link is clicked the sub menu expands below it.

Many of the sub menus have the same functions as older versions of Moodle.

What appears in the setting block depends upon the [[Context]] (Page being shown and user's permissions). For example, the site administrator will notice the Front Page settings block has fewer options than the Course settings block and a student will have fewer options in the Course administration than a teacher.

Here are two unexpanded examples of the settings block:
<gallery widths="200px" heights="275px" perrow="2">

Image:Settings block FrontPage collapsed.png|FrontPage settings block
Image:Settings block Course collapsed.png|Course settings block
</gallery>

==Settings block menus==
The main menu items (Front page settings, Course Administration, My profile settings and Site Administration) contain a submenu and can be collapsed or expanded to display the (typical) full menu as shown below:
*[[Front_page_settings_block|Front page settings]]
**Turn edit on/off
**Edit settings
**Users
**Filters
**Backup
**Restore
**Questions
**Files

*[[Course_administration_menu|Course administration]]
**Turn editing on
**Edit settings
**Users
**Filters
**Grades
**Backup
**Restore
**Import
**Publish
**Reset
**Question bank

*[[Profile |My profile settings]]
**Edit profile
**Change password
**Roles
**Portfolios (if available at site level)
**Security keys
**Messaging
**Blogs
**Make this my default home page (if set at site level)

*[[Site_administration|Site administration]]
**Notifications
**Registration
**Advanced features
**Users
**Courses
**Grades
**Location
**Language
**Plugins
**Security
**Appearance
**Front page
**Server
**Reports
**Development
**Question engine upgrade helper

==See also==

[[Category:Block]]

[[eu:Ezarpenak_blokea]]
[[de:Einstellungen (Block)]]

Front page settings block

2011-09-09T02:09:16Z

Cttxg:

{{Moodle 2.0}}
Moodle 2.0 has placed all the settings in [Settings_block|one block]]. What the user sees depends upon context. The front page menu is generally only available to Administrators.

[[Image:block-settings-frontpage.gif|frame|right|Front page menu]]
'''Front page settings'''
*Turn editing on
*[[Front_Page_settings|Edit settings]]
*Users
**Groups
**[[admin/roles/permissions|Permissions]]
***Assigned roles
***Check permissions
**[[Filters|Filters]]
**[[Course_backup|Backup]]
**[[Course_restore|Restore]]
**[[Question_bank|Questions]]

==See also==
*[[Settings block]]
*[[Course settings block]]
*[[:Category:Front_Page|Front page Category]]

[[eu:Hasiera-orriaren_ezarpenak_blokea]]

Plik:block-settings-frontpage.gif

2011-09-09T02:06:48Z

Cttxg: Front page settings image with submenus expanded

Front page settings image with submenus expanded

Front page settings block

2011-09-09T02:06:26Z

Cttxg: adding front page settings menu image

{{Moodle 2.0}}
Moodle 2.0 has placed all the settings in one block. What the user sees depends upon context. A site administrator on the front page will see something different than on the home page of a course. A teacher will see something different than an administrator or a student.

The site administrator will see 3 categories in the setting block on the front page of the site. A teacher or student will not see as many things. Clicking on any of these expands the menu selection. Here are the areas a submenu links:

[[Image:block-settings-frontpage.gif|frame|right|Front page menu]]
'''Front page settings'''
*Turn editing on
*[[Front_Page_settings|Edit settings]]
*Users
**Groups
**[[admin/roles/permissions|Permissions]]
***Assigned roles
***Check permissions
**[[Filters|Filters]]
**[[Course_backup|Backup]]
**[[Course_restore|Restore]]
**[[Question_bank|Questions]]

==See also==
*[[Settings block]]
*[[Course settings block]]
*[[:Category:Front_Page|Front page Category]]

[[eu:Hasiera-orriaren_ezarpenak_blokea]]