MoodleDocs - User contributions [en]

Language packs

2016-10-20T20:52:15Z

Benteo: /* Language pack installation and uninstallation */ H3 header added to make it easier to find the link to the download page in the article

{{Language}}
==Language pack installation and uninstallation==

Over 100 language packs are available for an administrator to install on your Moodle site via ''Administration > Site administration > Language > Language packs''. Simply select the languages you require from the list of available language packs and click on the "Install selected language pack" button.

Multiple language packs may be selected for install by holding down the Apple or Ctrl key whilst clicking on the language packs.

Installing many (20+) language packs has [https://moodle.org/mod/forum/discuss.php?d=241098 almost 0 impact] on Moodle performance.

Multiple language packs may be uninstalled, once selected, by clicking the 'Uninstall selected language packs" button.

===Language packs and manual download===

Language packs are a work-in-progress, since new language strings are added for new features in each new version of Moodle. Lang packs can be manually downloaded from [https://download.moodle.org/langpack/3.1/ Language packs for Moodle 3.1]. The page also lists the percentage of language strings translated in each language pack.

==Parent language packs and child language packs==

Certain language packs (a child language pack) contain only the modified language strings from their parent language, rather than a complete set. Thus, it is necessary to install the parent language pack too. These language packs are:
* ca_valencià (which requires ca)
* de_du, de_kids and de_comm (which require de)
* en_us, en_ar, en_kids (which require the default en)
* es_ve (which requires es)
* fil (which requires fi)
* fr_ca (which requires fr)
* he_kids (which requires he)
* ja_kids (which requires ja)
* lt_uni (which requires lt)
* no_gr (which requires no)
* sv_fi (which requires sv)
* wo (which requires fr)

{{Note| If your site uses a child language pack (see the list above), if you use the [[Multi-language content filter]], you need to be very careful about how to use if (as reported in MDL-55197). See [[Multi-language content filter]] for more details and examples.}}

==Manual language pack installation==

In general, the easiest way to install additional language packs is from within Moodle. However, it is also possible to install a language pack manually by downloading the zip file from [https://download.moodle.org/langpack/3.1/ Language packs for Moodle 3.1] and unzipping it to a directory called ''lang'' in your ''moodledata'' directory.

==Language pack updates==

* Language packs can be updated via ''Administration > Site administration > Language > Language packs''.
* You can see which language packs have updates because they are listed in both 'Installed language packs' and 'Available language packs'.
* To update all installed language packs (except English and any local language packs) click the 'Update all installed language packs' button.
* For sites with a large number of language packs installed, to update just a few installed language packs at a time, select the languages from the 'Available language packs' list and click the 'Install selected language pack(s)' button.
* The English language pack is updated automatically each time the site is upgraded.
* As most language packs are a work in progress, it is a good idea to update them regularly.

All installed language packs are updated as a [[Scheduled tasks|scheduled task]]. By default the task is run daily.

==Inside a language pack==

A standard Moodle comes with an English language pack only. It is installed in ''moodledata/lang/en.''

The English language terms (or 'strings') for the main (core) Moodle features such as administration, roles etc, are stored in ''lang/en.'' Language files relating to modules, blocks and other plugins are stored with the files of that particular plugin. So if you wanted to see the language strings for the badges block for example, you would look in ''blocks/badges/lang/en''. If you wanted to see the language files for the workshop module, you would look in'' mod/workshop/lang/en''.

If you install another language pack, you will then get a folder such as ''lang/fr'' which would have French translations of Moodle terms. Unlike with English, other language packs such as ''lang/fr'' will contain all translations along with the main core terms so you would find see for example the badges strings in ''lang/fr/block_badges.php'' and the workshop strings in ''lang/fr/workshop.php''.

These files (which all end in .php) contain short phrases, often called "strings". Strings may contain a placeholder (between the curly brackets below). This placeholder is replaced with the chosen words from the language pack when the string is displayed. The term between the square brackets is called the 'string identifier' or the 'string name'. Examples:

$string['addnewcourse'] = 'Add a new course';
$string['hidesection'] = 'Hide section {$a}';

If a string hasn't been translated, then Moodle will use the parent language or the original English version. Thus, you might see a Moodle site where some terms have been translated into a language but others still display in English.

==Can I personalize language strings per theme?==
Not directly, but you can use new local (child) language packs to achieve different courses behaviours/looks
===Changing the look of a course===
You can have a course with a different theme 'and' a different child language pack. You will then have personalized language strings in the only course that uses that particular theme.
===Changing the behaviour of a course===
* If you do not want a student to see any reference to grades when he/she finishes a lesson, by editing the correct text string, it is possible to replace "Your score is 9 (out of 10)" with "Be sure to get your certificate". Or change "Congratulations - end of lesson reached" to "We hoped this lesson helped you". See [[Lesson_FAQ#Can_I_change_the_End_of_Lesson_page_display|how to change the end of lesson page display]].
* You can have several different courses, each using a different (child) language pack and each one showing personalized language strings.
* See [https://moodle.org/mod/forum/discuss.php?d=220671 this forum post] for detailed instructions on how to create your new child languages.

==Can I install one particular language pack and supplement the missing translations using a second (related) language pack?==
* Short answer: No :(
* But you can use the [[Language customization]] tool. If you do make your own translations, please consider [https://docs.moodle.org/dev/Contributing_a_translation contribuiting your translated strings] to the language pack maintainers, so that your language pack can grow.
* See the Spanish language Moodle Documentation page at [https://docs.moodle.org/all/es/Personalizaci%C3%B3n_del_idioma_(transplantar_archivos) https://docs.moodle.org/all/es/Personalización del idioma (transplantar archivos)] about grafting files from one language into another.

==Can I make a language pack for kids?==
* Yes.
* The current existing language packs for kids are:
** de_kids (which require de)
** en_kids (which require the default en)
** he_kids (which requires he)
** ja_kids (which requires ja)

* If you want to make a language pack for kids in a language different from the ones listed above, use the following method:

** Install the (en_kids) English for kids language pack in your local Moodle server
** You will have to edit 10 files (which are stored in the moodledata/lang/en_kids folder).
** You can use [https://notepad-plus-plus.org/ Notepad++] or any other text editor, but avoid using MS Word or MS Notepad.
* Start with langconfig.php and choose your main language as the parentlanguage
* When you have finished translating all the strings, you can go to AMOS and request a new language pack to the person administering all Moodle language packs.
* Upload into AMOS the 10 files in your moodledata/lang/en_kids folder
* Remember to keep updating and expanding your new language pack

==Why do some languages have several different language packs available?==
See [https://docs.moodle.org/dev/Translation_FAQ#Moodle_languages_with_several_available_language_packs the developer's documentation] about this.

==Why has my language pack suddenly forgotten some translations?==
See the following image showing (Insignias) a properly translated Spanish language string (green rectangle) and an unstranslated English language string (red rectangle) for 'Badges' plus a mixture of translated and untranslated strings with a language pack that should have 100% of the core strings translated.

[[File:Language packs mixed-up llanguages shown.png|200px]]

If you try to update your language packs you will get a message indicating 'Update of 'xxxx_old' language pack skipped.

[[File:Something_old language pack can not be updated.png|300px]]

Read the following section for the cause and the fix.

==Why do I have a language pack named xx_old' that I never installed?==
Sometimes you may find (see image below) that your server has, in addition to your usual language packs (eg, en, es_mx), an odd-named language pack with an _old name ending (eg, es_mx_old), that -obviously- can not be updated.
* This came from an incomplete automated language pack update.
* There may also be a language pack that has mixed languages, like 'English (es_mx)', that obviously can not be.

[[File:Odd-named installed language pack.png|400px]]

* You must uninstall all strange-looking language packs and re-install your usual language packs.

[[File:Language packs uninstall all mixed-up languages.png|400px]]

==See also==

* List of [http://en.wikipedia.org/wiki/List_of_ISO_639-1_codes language codes] on Wikipedia
* [[:dev:Translation]] and help us to translate Moodle to more languages
* [http://youtu.be/0v72GKn2Wuk Moodle 2 Language Administration settings] MoodleBites video on YouTube

[[eu:Hizkuntza-paketeak]]
[[es:Paquetes de idioma]]
[[fr:Paquetages de langue]]
[[ja:言語インポートユーティリティ]]
[[de:Sprachpakete]]

Moodle migration

2016-08-06T12:31:14Z

Benteo: /* Backup the Moodle database on the old sever */ mysqldump command edited. It returned "mysqldump: unknown option '--'" when using --password

{{Installing Moodle}}
There may be times when you need to move your Moodle site from one server to another. For example, moving a Moodle site from shared hosting service's server to a dedicated server.

==Recommended method==

This involves moving a whole site from one server to another. If you are changing the domain/IP address to the new server you need to do these steps:

===Turn on maintenance mode===

Place your current Moodle site into [[Maintenance mode]] Site Administration>Server>Maintenance Mode to prevent any further additions to the Moodle database. Don't let administrators login during the migration as they are not affected by the maintenance mode setting.

===Backup the Moodle database on the old sever===

The right way to back up your database depends on which database system you are using. The instructions below are one way to back up a MySQL database. Another option would be to use a tool like phpMyAdmin to manually make a backup. The documentation for your database will give more options. There are many ways to do such backups. Here is an outline of a little script you can run from command line on Unix to backup the database:

<pre>
cd /my/backup/directory
mv moodle-database.sql.gz moodle-database-old.sql.gz
mysqldump -h example.com -u myusername -p'mypassword' -C -Q -e --create-options mydatabasename > moodle-database.sql
</pre>
If you only write "-p" without your password, you will be prompted for it.

=== Restore the database backup to the new server ===

Copy the database back up files to the new server and restore into the new database server.

Once you have created the new database on the new server:

<pre>mysql -p new_database < moodle-database.sql</pre>

For other databases, follow their instructions for restoring a backup.

===Copy moodledata from the old server to the new server===

Copy the contents of your data directory (check for the value in <code>$CFG->dataroot</code>) to the new server. This can be a lot of data, so consider using a good data copying tool like rsync. If using an FTP client, the transfer of the <code>filedir</code> folder must be in '''BINARY''' mode or the files will get corrupted in the process.

Check the file permissions of the copied files. The web server needs read and write access.

===Copy the Moodle code from the old server to the new server===

You will need to copy the Moodle code itself to the new server (this is the Moodle folder found in your webroot folder e.g. /var/www or public_html).

Check the file permissions of the copied files. The web server needs read access.

===Update config.php with the URL of the new server===

If the migration will move Moodle to a new URL, then update $CFG->wwwroot in config.php to point to the new location.

Also check the other properties there. Is the path $CFG->moodledata still correct? Do the database connection settings need to be changed?

===Test the copied site===

You should now be able to log into the new site as admin, and verify that most things are working.

===Update links containing wwwroot in the databse===

The one thing we have not fixed is any internal links stored in the database. To fix these use the [[Search and replace tool]] buy going to {wwwroot}/admin/tool/replace/index.php.

Enter the url for your old server (<nowiki>http://oldserver.com/</nowiki>) and new server (<nowiki>http://newserver.com/</nowiki>) and it will fix any links stored in the database.

===Take the site out of maintenance mode===

Test the migration some more, then when you are satisfied, remember to take the site out of maintenance mode.

==Quick and hacky method==

If you have shell access on both servers, here is a quick command-line based method.

*Set up a new empty database on the '''new''' server.
*Place your existing Moodle site into maintenance mode.
*Login to shell on the '''old''' existing server.
*Use rsync to copy '''moodledata''' and '''public_html''' or '''moodle''' folders (or whatever directory your Moodle install is in) to the new server - execute (replacing caps with your details; SOURCE = the directory you want to copy) for each directory:
::<code>rsync -av -e ssh SOURCE/ USERNAME@NEW_SERVER.COM:/PATH/TO/DESTINATION/</code>
*Dump existing database and move and import into database on new server by executing:
::<code>mysqldump --allow-keywords --opt -uMySQL_USERNAME -pPASSWORD DATABASE | ssh USER@DOMAIN "mysql -uMySQL_USERNAME -pPASSWORD DATABASE"</code>
*Replace any links in the database that contin the full site URL:
::<code>#sed -e 's/oldserver.com/newserver.com/g' oldmysqldump.sql > newmysqldump.sql</code>
*On the '''new server''', update '''config.php''' with relevant details where applicable (e.g. database name and user details, the wwwroot and the dataroot).
*Check ownership and permissions are correct on both moodle code and moodledata directories.
*Make sure everything is working.

Takes about 15 minutes for a small site. However, transferring several Gigabytes of data for a larger site can take hours depending on your network connection and hard drive read/write speed.

When you are happy all has gone well, set up redirects/make DNS changes if required, take new site out of maintenance mode and "switch off" old site.

*If you are switching the ip address from the old server to the new one, you will need to turn off the old server before firing up the new one to avoid ip addressing conflicts and confusion!

==Other considerations==

===Upgrade Moodle at the same time?===

While doing the work of migrating Moodle, you might want to [[Upgrading | upgrade Moodle]] to the latest version at the same time. On the other hand, if you do that, and something breaks, you won't be sure which change caused the problem, so the more cautious approach is to change one thing at a time, and test in between to verify that all is well.

===DNS & masquerading changes===

You may have had to change the DNS entries for the new Moodle site. If you have done so, it will take some time for the changes to replicate, so be patient. If your server is located behind a firewall, you may also have to change your firewall rules to allow access to the new server. See the [[Masquerading | masquerading docs]].

===Internal and external access===

If you have a set up where your Moodle site can be accessed via a network and via the internet, ensure you check that the new site can be accessed internally and externally.

===ReCAPTURE===
If you migrate to a new domain and have setup [[Email-based_self-registration]], you need to create new API-Keys at google. You will find the explanation and links to google in [[Email-based_self-registration]].

==See also==

* [[Site backup]]
* [[Site restore]]
* [[Backup and restore FAQ]]

Using Moodle forum discussions:
* [http://moodle.org/mod/forum/discuss.php?d=62959 Changing Moodle URL]
* [http://moodle.org/mod/forum/discuss.php?d=57477 Changing site address]
* [http://moodle.org/mod/forum/discuss.php?d=76704 Upgrading whilst migrating]
* [http://moodle.org/mod/forum/discuss.php?d=65450 Internal and external access]
* [http://moodle.org/mod/forum/discuss.php?d=111807 Migrated Moodle to New Server But Can't Login]
* [http://moodle.org/mod/forum/discuss.php?d=228436 Replace script returns "Service Unavailable"]
* [http://moodle.org/mod/forum/discuss.php?d=85812 migrating Moodle's data directory on a Windows system]

[[es:Migración de Moodle]]
[[fr:Migration de Moodle]]
[[ja:Moodle移行]]
[[de:Moodle-Migration]]

Glossary settings

2014-03-07T10:28:11Z

Benteo: /* Display format */ More thoroughly explanation of the 'Continuous without author' setting

{{Glossary}}
==Adding a glossary==
To add a glossary:
#With the editing turned on, in the section you wish to add your glossary, click the "Add an activity or resource" link (or, if not present, the "Add an activity" drop down menu ) and choose ''Glossary.'' All settings may expanded by clicking the "Expand all" link top right.

==General==

{|
|[[File:glossarydescription.png|thumb|477px|General settings expanded by default]]
|}
===Name===
Give your new glossary a descriptive name.
===Description===
Describe the purpose of the glossary and provide instructions or background information, links etc. Click the icon top left to expand the toolbars, 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 glossary.
===Is this glossary global?===

Administrators can make a global glossary, with entries linking throughout the whole Moodle site. Any course may contain a global glossary, though the best practice is to place a global glossary on the site front page.

===Glossary type===

Here you can decide whether the glossary will be main or secondary. The glossary system allows you to export entries from any secondary glossary to the main one of the course. In order to do this, you should specify which glossary is the main one. You can only have one main glossary per course.

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

===Approved by default===
If set to "yes" then new entries appear automatically. If not, then the teacher must approve each one first.
===Always allow editing===
If set to "yes", students can edit their entries at any time. If not, then they can only edit for a certain period (defined in [[Site Policies]])
===Duplicate entries allowed===
This allows the entry of more than one definition for a given word.
===Allow comments on entries===
Students and teachers can leave comments on glossary definitions. The comments are available through a link at the bottom of the definition.

===Automatically link glossary entries===
If the [[Glossary auto-linking filter]] is enabled by an administrator (see [[Filters]] for further details), then turning this on allows individual entries in this glossary to be automatically linked whenever the concept words and phrases appear throughout the rest of the same course. This includes forum postings, internal resources, week summaries and so on.
{|
|[[Image:Glossaryautolink.png|thumb|400px|An auto-linked word in a forum]]
|}

Note: Enabling linking for the glossary does not automatically turn on linking for each entry - linking needs to be set for each entry individually. If you do not want particular text to be linked (in a forum posting, say) then you should add <nolink> and </nolink> tags around the text. Note that category names are also linked.

==Appearance==
(These settings are collapsed by default)
{|
|[[File:glosssaryappearance.png|thumb|430px|Appearance settings expanded]]
|}

===Display format===

That specifies the way that each entry will be shown within the glossary. The default formats are:

* Simple, dictionary style - This looks like a conventional dictionary with separate entries. No authors are displayed and attachments are shown as links.
* Continuous without author - Like the simple style. Shows the entries one after other without any kind of separation but the editing icons, but only if your theme supports it, you usually have to modify the theme if you want an alternative appearance to the simple setting.
* Full with author - A forum-like display format showing author's data. Attachments are shown as links.
* Full without author - A forum-like display format that does not show author's data. Attachments are shown as links.
* Encyclopedia - Like 'Full with author' but attached images are shown inline.
* Entry list - This lists the concepts as links.
* FAQ - Useful for displaying lists of frequently asked questions. It automatically appends the words QUESTION and ANSWER in the concept and definition respectively.

See [[Glossary FAQ]] for more information on the code for the different display formats.

===Approval display format===
It is possible to set an alternative display format for when entries are approved that can differ from the display format on the course page. This could be useful for instance if a tutor wants to see who made a particular glossary entry before approving it but doesn't want the students' name to be displayed for others on the course page.
===Entries shown per page===
Decid here how many entries to show per page.
===Show alphabet links===
If set to "yes", users can browse the glossary by letters of the alphabet.
===Show 'ALL' link===
If set to "yes", users can browse all the entries at once
===Show 'Special' link===
If set to "yes", users can can browse the glossary by special characters, such as @ and #.
===Allow print view===
This provides a printer-friendly version link for students. (Teachers are always provided with a printer-friendly version link.)

==RSS==
(These settings are collapsed by default and only visible if RSS has been enabled on the site and for the glossary.)
{|
|[[File:glossaryrss.png|thumb|450px|RSS settings expanded]]
|}

===RSS feed for this activity===

This turns RSS on or off. When set to “None,” the RSS feed is disabled. When set to “Concepts with authors,” the RSS feed will send out the glossary entries with the name of the author. When set to “Concepts without authors,” the RSS feed sends out glossary entries without the name of the author.

===Number of RSS recent articles===

This number sets the number of entries 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 entries get added, the oldest entry gets replaced on the RSS feed. If your glossary gets a lot of posts every day, you will want to set this number high.

When RSS is enabled for your glossary, an orange RSS button appears on the main page (in the upper right-hand side). When a user clicks on the RSS button, they see the [[XML]] code displayed, needed by the news-reader. Once a user has the RSS news-feed link, adding it to a reader is simple and will then display Glossary aggregated information, along with other information they subscribe to.

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

==Ratings==
(This setting is collapsed by default)

{|
|[[File:glossaryratings.png|thumb|466px|Ratings settings expanded]]
|}

===Roles with permissions to rate===
Glossary entries can be rated using a [[Scales|scale]]. By default, only teachers can rate glossary entries, though students can be given permission to do so if desired from ''Administration>Glossary 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)

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

==Adding a new glossary entry==
See [[Using Glossary]]

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

==Site administration settings==

The glossary module has additional settings which may be changed by an administrator in ''Settings > Site administration > Plugins > Activity modules > Glossary''.

=== Glossary level default settings ===

* glossary_entbypage - Number of Glossary entries shown per page. Default is set to 10.
* glossary_dupentries - Whether or not the Glossary will allow duplicate entries. Default is set to "No".
* glossary_allowcomments - Whether or not the Glossary will accept user comments on its entries. Default is set to "No".
* glossary_linkbydefault - Whether or not a glossary should be automatically linked. Default is set to "Yes".
* glossary_defaultapproval - Whether or not the Glossary will define the approval status of an entry posted by a student. Default is set to "Yes".
* glossary_enablerssfeeds - Enabling of RSS feeds for all glossaries. Default is set to "No". Note: feeds will still need to be turned on manually in the settings for each glossary.

=== Entry level default settings===

* glossary_linkentries - Whether or not glossary entries should be automatically linked. Default is set to "No".
* glossary_casesensitive - Whether or not an entry is case sensitive when linked. Default is set to "No".
* glossary_fullmatch - Whether or not an entry should match the case in the target text by default when linked. Default is set to "No".

=== Display Formats Setup ===

To hide or show any of these entries, simply click on the "eye" icon next to the entry. Clicking on the "writing hand" icon will take you to the settings page for that entry.

[[Category:Site administration]]

[[de:Glossar konfigurieren]]
[[ja:用語集エントリを追加/編集する]]
[[es:Configuraciones del glosario]]

Glossary settings

2013-05-10T12:54:11Z

Benteo: /* Display format */

{{Glossary}}
==Adding a glossary==
To add a glossary:
#With the editing turned on,in the section you wish to add your glossary, click the "Add an activity or resource" link (or, if not present, the "Add an activity" drop down menu )and choose ''Glossary.'' All settings may expanded by clicking the "Expand all" link top right.
==General==

{|
|[[File:glossarygeneral25.png|thumb|General settings expanded by default]]
|}
===Name===
Give your new glossary a descriptive name.
===Description===
Describe the purpose of the glossary and provide instructions or background information, links etc. Click "Show editing tools" to display the rich text editor, 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 glossary.
===Is this glossary global?===

Administrators can make a global glossary, with entries linking throughout the whole Moodle site. Any course may contain a global glossary, though the best practice is to place a global glossary on the site front page.

===Glossary type===

Here you can decide whether the glossary will be main or secondary. The glossary system allows you to export entries from any secondary glossary to the main one of the course. In order to do this, you should specify which glossary is the main one. You can only have one main glossary per course.

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

===Approved by default===
If set to "yes" then new entries appear automatically. If not, then the teacher must approve each one first.
===Always allow editing===
If set to "yes", students can edit their entries at any time. If not, then they can only edit for a certain period (defined in [[Site Policies]])
===Duplicate entries allowed===
This allows the entry of more than one definition for a given word.
===Allow comments on entries===
Students and teachers can leave comments on glossary definitions. The comments are available through a link at the bottom of the definition.

===Automatically link glossary entries===
If the [[Glossary auto-linking filter]] is enabled by an administrator (see [[Filters]] for further details), then turning this on allows individual entries in this glossary to be automatically linked whenever the concept words and phrases appear throughout the rest of the same course. This includes forum postings, internal resources, week summaries and so on.
{|
|[[Image:Glossaryautolink.png|thumb|An auto-linked word in a forum]]
|}

Note: Enabling linking for the glossary does not automatically turn on linking for each entry - linking needs to be set for each entry individually. If you do not want particular text to be linked (in a forum posting, say) then you should add <nolink> and </nolink> tags around the text. Note that category names are also linked.

==Appearance==
(These settings are collapsed by default)
{|
|[[File:glossaryappearance25.png|thumb|Appearance settings expanded]]
|}

===Display format===

That specifies the way that each entry will be shown within the glossary. The default formats are:

* Simple, dictionary style - This looks like a conventional dictionary with separate entries. No authors are displayed and attachments are shown as links.
* Continuous without author - Like the simple style. Shows the entries one after other without any kind of separation but the editing icons if your theme supports it.
* Full with author - A forum-like display format showing author's data. Attachments are shown as links.
* Full without author - A forum-like display format that does not show author's data. Attachments are shown as links.
* Encyclopedia - Like 'Full with author' but attached images are shown inline.
* Entry list - This lists the concepts as links.
* FAQ - Useful for displaying lists of frequently asked questions. It automatically appends the words QUESTION and ANSWER in the concept and definition respectively.

See [[Glossary FAQ]] for more information on the code for the different display formats.

===Approval display format===
It is possible to set an alternative display format for when entries are approved that can differ from the display format on the course page. This could be useful for instance if a tutor wants to see who made a particular glossary entry before approving it but doesn't want the students' name to be displayed for others on the course page.
===Entries shown per page===
Decid here how many entries to show per page.
===Show alphabet links===
If set to "yes", users can browse the glossary by letters of the alphabet.
===Show 'ALL' link===
If set to "yes", users can browse all the entries at once
===Show 'Special' link===
If set to "yes", users can can browse the glossary by special characters, such as @ and #.
===Allow print view===
This provides a printer-friendly version link for students. (Teachers are always provided with a printer-friendly version link.)

==RSS==
(These settings are collapsed by default and only visible if RSS has been enabled on the site and for the glossary.)
{|
|[[File:glossaryrss25.png|thumb|RSS settings expanded]]
|}

===RSS feed for this activity===

This turns RSS on or off. When set to “None,” the RSS feed is disabled. When set to “Concepts with authors,” the RSS feed will send out the glossary entries with the name of the author. When set to “Concepts without authors,” the RSS feed sends out glossary entries without the name of the author.

===Number of RSS recent articles===

This number sets the number of entries 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 entries get added, the oldest entry gets replaced on the RSS feed. If your glossary gets a lot of posts every day, you will want to set this number high.

When RSS is enabled for your glossary, an orange RSS button appears on the main page (in the upper right-hand side). When a user clicks on the RSS button, they see the [[XML]] code displayed, needed by the news-reader. Once a user has the RSS news-feed link, adding it to a reader is simple and will then display Glossary aggregated information, along with other information they subscribe to.

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

==Ratings==
(This setting is collapsed by default)

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

===Roles with permissions to rate===
Glossary entries can be rated using a [[Scales|scale]]. By default, only teachers can rate glossary entries, though students can be given permission to do so if desired from ''Administration>Glossary 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)

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

==Adding a new glossary entry==
See [[Using Glossary]]

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

==Site administration settings==

The glossary module has additional settings which may be changed by an administrator in ''Settings > Site administration > Plugins > Activity modules > Glossary''.

=== Glossary level default settings ===

* glossary_entbypage - Number of Glossary entries shown per page. Default is set to 10.
* glossary_dupentries - Whether or not the Glossary will allow duplicate entries. Default is set to "No".
* glossary_allowcomments - Whether or not the Glossary will accept user comments on its entries. Default is set to "No".
* glossary_linkbydefault - Whether or not a glossary should be automatically linked. Default is set to "Yes".
* glossary_defaultapproval - Whether or not the Glossary will define the approval status of an entry posted by a student. Default is set to "Yes".
* glossary_enablerssfeeds - Enabling of RSS feeds for all glossaries. Default is set to "No". Note: feeds will still need to be turned on manually in the settings for each glossary.

=== Entry level default settings===

* glossary_linkentries - Whether or not glossary entries should be automatically linked. Default is set to "No".
* glossary_casesensitive - Whether or not an entry is case sensitive when linked. Default is set to "No".
* glossary_fullmatch - Whether or not an entry should match the case in the target text by default when linked. Default is set to "No".

=== Display Formats Setup ===

To hide or show any of these entries, simply click on the "eye" icon next to the entry. Clicking on the "writing hand" icon will take you to the settings page for that entry.

[[Category:Site administration]]

[[de:Glossar konfigurieren]]
[[ja:用語集エントリを追加/編集する]]

AMOS

2011-12-15T12:44:40Z

Benteo: /* Using the stage */ deleted (at xx:45)

'''AMOS stands for Automated Manipulation Of Strings. AMOS is a central repository of Moodle strings and their history. It tracks the addition of English strings into Moodle code, gathers translations, handles common translation tasks and generates language packages to be deployed on Moodle servers.'''

The name was chosen in honour of [http://en.wikipedia.org/wiki/John_Amos_Comenius John Amos Comenius], the author of ''Janua linguarum reserata'' (Gate to Languages Unlocked). Sorry Tori ;-)

AMOS is installed at http://lang.moodle.org. If you want to use it, please create an account there. Language pack [[Translation_credits|maintainers]] should then send an email to [mailto:translation@moodle.org translation@moodle.org] (Koen) to get write access for their language.

AMOS provides support for community contributions into the translation. If you want to participate, just create an account at http://lang.moodle.org. There is no need to contact us in this case but you should definitely contact the language maintainer and coordinate your work.

== Basic concepts ==

[[image:amos-screenshot-navigation.png|100px|thumb|right|AMOS tools in the navigation block]]
AMOS consists of several tools available via the main navigation block - Translator, Stage, Stashes, Contributions and Log.

* User - AMOS is used by languages pack maintainers and by the community members who want to contribute
* Translator - is a tool that allows you to filter strings you want to work on and translate them
* Stage - is a temporary working area that holds the strings you have translated during the current session. Maintainers can permanently commit the stage into the strings repository. Contributors can submit the stage for maintainers.
* Stashes - are snapshots of the stage. Imagine them as ordinary files at your computer where you can save your work. You can submit your stash to the language pack maintainers.
* Contributions - is a database tracking all submitted contributions and their current status. Records in this database are like issues in Moodle tracker with the translated strings attached.
* Repository - a database of all Moodle strings and their history running at lang.moodle.org server
* Log - displays the log of all modifications of Moodle strings.

== Translation workflow ==

The following data flow diagram illustrates how AMOS tools are used during the translation process.

[[image:amos-workflow.png]]

The key AMOS component is the staging area or shortly the stage. It holds translated strings temporarily during your current login session. If you log out, the stage is cleared (though there is a backup - see below). There are several ways how translations can be staged, that is how translated strings can be put into the stage:

* by using AMOS translator
* by importing strings from an uploaded file
* by applying a previously created stash
* by applying a submitted contribution

Language pack maintainers have write access into the AMOS strings repository. Therefore they can commit their stage permanently. Once the stage is committed, staged strings are stored in the AMOS repository. Every hour at xx:45, AMOS generates ZIP packages from the most recent snapshot of the repository. These ZIP packages are published at http://download.moodle.org/langpack/2.0/ for download. Moodle sites can install and update language packages automatically from the ''Site administration > Language > Language packs'' page.

Community members do not have write access into the repository so they can't commit their stage. Instead, they can submit it to the maintainers. By submitting a stage, a new contribution record is created and language pack maintainers are notified by automatic email message. Maintainers can review the submitted contribution and, if they accept it, commit it on behalf of the contributor.

The stage can be also saved so you can interrupt your work and continue next time you come back to the site. The stage is saved into so called stashing area. Stashing area consists of stashes. A new stash is nothing but a snapshot copy of your current stage. AMOS automatically keeps one stash for you as a backup copy of your most recent stage. A stash can be submitted to the maintainers, too.

== AMOS tools ==

=== Using the translator tool ===

[[image:amos-screenshot-translator.png|300px|thumb|right|AMOS Translator tool]]
The translator tool page has two main parts. At the top, there is a filter form (1). You use that filter to get the strings you want to translate. When the filter settings are saved (2), a table with the filtered strings is displayed below.

Every row in the table represents a single string. The table has four columns. The first column (3) describes the version (or branch) where the string is used, its identifier and its component. You can see a text like

2.0 [completiondate,coursereport_completion]

That reads: this string is used in Moodle 2.0, its identifier is 'completiondate' and it belongs to 'courserepor_completion' component.

The second column (4) contains the English original of the string. Below the text, you can see Google icon. Click that icon to get automatic translation of the string into the language being translated. The next column contains a code of the language that this string is being translated to (for example "cs" for Czech).

Finally the last column contains the translation itself. If it is empty, the string is not translated yet, otherwise it displays the current translation. '''Click in the cell to turn it into the input editor.''' Insert the translation and click outside the cell to stage the translation. Note there is no submit button, the text is sent to the stage automatically in the background. You can see that the colour of the cell turned blue. Blue colour signalizes that the translation is currently staged.

You have many options of how to use the strings filter. You can work on a single component or all missing strings at once. You can search for strings containing a given text (either in English or the translated string) etc. You can check for strings in older versions, too but those strings are read-only. They get automatically pulled into AMOS from the CVS repository of 1.x translations.

The 'permalink' below the filter's submit button can be used to keep the current filter settings. For example, you can bookmark a setting use regularly or you can copy the link URL and send it to somebody so they can set their filter just by visiting that URL.

When you finish translating, do not forget to visit the stage page. You probably want either commit it (if you are a lang pack maintainer) or submit it to maintainers so they can review your work and include it into the language pack.

=== Using the stage ===

[[image:amos-screenshot-stage-contrib.png|300px|thumb|right|Strings staged by a contributor]]
The translated strings are put into a temporary area called ''stage'' immediately after the cursor leaves the editor field. The stage holds your work before it is either committed into the repository (if you are language pack maintainer) or submitted to the maintainers for inclusion or stashed.

The stage is cleared when you logout. You have to explicitly commit or stash the stage so it is saved permanently. If you forget to do it, or there is a problem with the connectivity, your browser crashes or whatever, you can find your most recent snapshot of the stage in autosave stash.

If you are language pack maintainer, you can commit the stage into the repository so your work is registered and the translated strings become part of the official language package. Language packages in ZIP format are generated every third hour and are published at http://download.moodle.org/langpack/2.2/ - look at the bottom of the page to see the last update. At the same time, they become available for Moodle sites for automatic update.

The stage can also be used to import strings from files and to merge or compare versions of language packs.

=== Importing a file ===

[[image:amos-screenshot-stage-empty.png|300px|thumb|right|Empty stage allows you to import strings from a file]]
Strings can be translated offline and uploaded back to AMOS using the stage page. The only supported format at the moment is common PHP format used by Moodle where strings are defined in associative array called $string. For obvious security reasons, AMOS can not actually execute PHP files uploaded by users. Instead, it parses the uploaded file in a similar way as PHP parser, looking for patterns that are considered as valid string definition. That means that not every valid PHP code is valid string definition. AMOS parser requires following conditions are met:

* the filename is valid component name used by Moodle, for example moodle.php, enrol_manual.php or workshop.php
* the file is valid PHP code without syntax errors - that means is passes the PHP lint check
* strings are defined as elements of global array $string
* strings are single quoted constants

Example of a valid file to import into AMOS (filename countries.php, Czech translation)

<?php

$string['AE'] = 'Spojené Arabské emiráty';
$string['AF'] = 'Afghánistán';
$string['CH'] = 'Švýcarsko';
$string['HU'] = 'Maďarsko';

?>

During the import, strings found in the file are added into your stage as if they were translated via web. You can commit them into repository if you have such privilege.

=== Using stashes ===

At any moment, you can save a snapshot of the current stage. We call such snapshot a ''stash''. Stashed strings are kept forever until you drop them manually (please do not abuse this and keep your stashes reasonable big). To manage your stash, click on Stashes in the right menu of AMOS. You just see a list of the stashes. There are "peekaboo" buttons that appear when you mouse hoover over the stashes. The stash can be ''applied'' so that the stashed strings are copied back to the stage. What the ''pop'' does is apply and drop (delete) the stash. ''drop'' is like delete. ''submit to maintainer'' opens a form for doing just that.

There is one special stash record for every user called autosave stash. This stash keeps the most recent state of the stage. You may find it useful if you loose the current stage for any reason - your browser crashes, your internet connectivity dies or you accidentally unstage all strings. If that happens, just apply the autosave stash to get your work back. The autosave stash is updated every time you stage a string. So if your stage is empty and your autosave stash is full of strings and you go into the translator first without applying the stash, the autosave will be replaced with the new translated string. We recommend to experiment a bit with this feature first.

=== Using the log tool ===

The Log page allows even anonymous users to search in the history of commits tracked by AMOS. At the top of the page there is a filter that allows you to look for a particular information or report. It is important to realize how the filter actually works. Searching and filtering happens in two steps (this was necessary for performance reasons):

* Firstly, commit records are searched based on the criteria specified in the Commit filter form. If there are more commits found matching the filter settings, only 100 most recent commits are processed.
* Then, within the commits found, either all string modification records are returned, or you can filter these records, too. Settings in String filter form section are used in that case.

By default, the filter looks for all commits since the last time you logged in and than displays only strings at the currently translated branch modified by those commits.

===Language packs and Moodle versions===

When a new Moodle version is released, it will become the default version on your Amos - Translator page (see tick boxes at the top).

The suggested work flow is to continue your translation work for the new Moodle version and merge your work in the older versions.
You can do that using the Amos - Stage page: Set the source version to the version you were working in and set the target version to the version you want the strings to be copied to.

== Contributing to a language pack ==

AMOS allows community members to help with the translation of Moodle strings. AMOS Contributions page tracks all submitted translations and their current status. Before you start working on a translation, please communicate with the language pack maintainer (to be found on https://docs.moodle.org/en/Translation_credits).

=== Steps for the contributor ===

[[image:amos-screenshot-contribution-new.png|300px|thumb|right|Submitting a contribution form]]
# Contact the language pack maintainer about your intention to contribute to the language pack
# Use AMOS translator interface to translate missing strings or amend the current translation
# Go to the Stage page
# Click 'Submit to maintainers' button
# At 'Submitting a contribution' page, please provide a message for maintainers describing your work and why you would like to see your contribution included. You can cancel the submission at this moment yet. If you are sure, click 'Submit to maintainers'.
# Your stage will submitted into the contributions database. If there were more languages affected by your contribution, the stage will be divided into separate contribution records, one per each language. The language pack maintainers will be notified by email about your new contribution.
# Language pack maintainers will be able to apply your work into their stage, review it and eventually commit. You will receive automatically generated email when the status of contribution changes (typically when a maintainer starts a review of your work and then when they accept or reject it).
# Use contribution record comments for further communication with the maintainer about the submitted translation.

=== Steps for the maintainer, making own contributions===

# Use AMOS translator interface to translate missing strings or amend the current translation
# Go to the Stage page
# Make a meaningfull comment about your work in the 'Commit message' form
# Click on 'Commit'

=== Steps for the maintainer, approving users contributions===

[[image:amos-screenshot-contribution-details.png|300px|thumb|right|Contribution details page]]
# When a user submits new contribution, you will receive automatically generated email from AMOS
# Go to the Contributions page to see a list of all new incoming contributions. Click the link in the table to open the contribution details page
# Press 'Start review' button. That will assign the contribution to yourself, change the status from 'New' to 'In review', send automatically generated email to the contributor and will copy the submitted strings into your stage. You should check that your stage is empty before you apply the submitted strings, unless you want to merge several contributions into one commit.
# Review the submitted strings, eventually edit them. Commit the stage. It is nice to mention the contributor's name in the commit message and attribute the original authorship to them.
# Go back to the contribution record and change the status to Accepted or Rejected. Automatically generated email will be sent to the contributor whenever you change the status.
# Use contribution record comments for further communication with the contributor about the submitted translation.
# Accepted and Rejected contributions are not shown at the contributions page unless you press 'Show resolved contributions' button.

== See also ==

* [[Translation]] for more information about the process of Moodle 2.x translation
* [[Development:Languages/AMOS]] for the AMOS internals documentation

[[Category:Language]]

[[fr:AMOS]]

AMOS

2011-12-15T12:38:52Z

Benteo: /* AMOS tools */ Changed lang. pack update time & link to doc. v. 2.2

'''AMOS stands for Automated Manipulation Of Strings. AMOS is a central repository of Moodle strings and their history. It tracks the addition of English strings into Moodle code, gathers translations, handles common translation tasks and generates language packages to be deployed on Moodle servers.'''

The name was chosen in honour of [http://en.wikipedia.org/wiki/John_Amos_Comenius John Amos Comenius], the author of ''Janua linguarum reserata'' (Gate to Languages Unlocked). Sorry Tori ;-)

AMOS is installed at http://lang.moodle.org. If you want to use it, please create an account there. Language pack [[Translation_credits|maintainers]] should then send an email to [mailto:translation@moodle.org translation@moodle.org] (Koen) to get write access for their language.

AMOS provides support for community contributions into the translation. If you want to participate, just create an account at http://lang.moodle.org. There is no need to contact us in this case but you should definitely contact the language maintainer and coordinate your work.

== Basic concepts ==

[[image:amos-screenshot-navigation.png|100px|thumb|right|AMOS tools in the navigation block]]
AMOS consists of several tools available via the main navigation block - Translator, Stage, Stashes, Contributions and Log.

* User - AMOS is used by languages pack maintainers and by the community members who want to contribute
* Translator - is a tool that allows you to filter strings you want to work on and translate them
* Stage - is a temporary working area that holds the strings you have translated during the current session. Maintainers can permanently commit the stage into the strings repository. Contributors can submit the stage for maintainers.
* Stashes - are snapshots of the stage. Imagine them as ordinary files at your computer where you can save your work. You can submit your stash to the language pack maintainers.
* Contributions - is a database tracking all submitted contributions and their current status. Records in this database are like issues in Moodle tracker with the translated strings attached.
* Repository - a database of all Moodle strings and their history running at lang.moodle.org server
* Log - displays the log of all modifications of Moodle strings.

== Translation workflow ==

The following data flow diagram illustrates how AMOS tools are used during the translation process.

[[image:amos-workflow.png]]

The key AMOS component is the staging area or shortly the stage. It holds translated strings temporarily during your current login session. If you log out, the stage is cleared (though there is a backup - see below). There are several ways how translations can be staged, that is how translated strings can be put into the stage:

* by using AMOS translator
* by importing strings from an uploaded file
* by applying a previously created stash
* by applying a submitted contribution

Language pack maintainers have write access into the AMOS strings repository. Therefore they can commit their stage permanently. Once the stage is committed, staged strings are stored in the AMOS repository. Every hour at xx:45, AMOS generates ZIP packages from the most recent snapshot of the repository. These ZIP packages are published at http://download.moodle.org/langpack/2.0/ for download. Moodle sites can install and update language packages automatically from the ''Site administration > Language > Language packs'' page.

Community members do not have write access into the repository so they can't commit their stage. Instead, they can submit it to the maintainers. By submitting a stage, a new contribution record is created and language pack maintainers are notified by automatic email message. Maintainers can review the submitted contribution and, if they accept it, commit it on behalf of the contributor.

The stage can be also saved so you can interrupt your work and continue next time you come back to the site. The stage is saved into so called stashing area. Stashing area consists of stashes. A new stash is nothing but a snapshot copy of your current stage. AMOS automatically keeps one stash for you as a backup copy of your most recent stage. A stash can be submitted to the maintainers, too.

== AMOS tools ==

=== Using the translator tool ===

[[image:amos-screenshot-translator.png|300px|thumb|right|AMOS Translator tool]]
The translator tool page has two main parts. At the top, there is a filter form (1). You use that filter to get the strings you want to translate. When the filter settings are saved (2), a table with the filtered strings is displayed below.

Every row in the table represents a single string. The table has four columns. The first column (3) describes the version (or branch) where the string is used, its identifier and its component. You can see a text like

2.0 [completiondate,coursereport_completion]

That reads: this string is used in Moodle 2.0, its identifier is 'completiondate' and it belongs to 'courserepor_completion' component.

The second column (4) contains the English original of the string. Below the text, you can see Google icon. Click that icon to get automatic translation of the string into the language being translated. The next column contains a code of the language that this string is being translated to (for example "cs" for Czech).

Finally the last column contains the translation itself. If it is empty, the string is not translated yet, otherwise it displays the current translation. '''Click in the cell to turn it into the input editor.''' Insert the translation and click outside the cell to stage the translation. Note there is no submit button, the text is sent to the stage automatically in the background. You can see that the colour of the cell turned blue. Blue colour signalizes that the translation is currently staged.

You have many options of how to use the strings filter. You can work on a single component or all missing strings at once. You can search for strings containing a given text (either in English or the translated string) etc. You can check for strings in older versions, too but those strings are read-only. They get automatically pulled into AMOS from the CVS repository of 1.x translations.

The 'permalink' below the filter's submit button can be used to keep the current filter settings. For example, you can bookmark a setting use regularly or you can copy the link URL and send it to somebody so they can set their filter just by visiting that URL.

When you finish translating, do not forget to visit the stage page. You probably want either commit it (if you are a lang pack maintainer) or submit it to maintainers so they can review your work and include it into the language pack.

=== Using the stage ===

[[image:amos-screenshot-stage-contrib.png|300px|thumb|right|Strings staged by a contributor]]
The translated strings are put into a temporary area called ''stage'' immediately after the cursor leaves the editor field. The stage holds your work before it is either committed into the repository (if you are language pack maintainer) or submitted to the maintainers for inclusion or stashed.

The stage is cleared when you logout. You have to explicitly commit or stash the stage so it is saved permanently. If you forget to do it, or there is a problem with the connectivity, your browser crashes or whatever, you can find your most recent snapshot of the stage in autosave stash.

If you are language pack maintainer, you can commit the stage into the repository so your work is registered and the translated strings become part of the official language package. Language packages in ZIP format are generated every third hour (at xx:45) and are published at http://download.moodle.org/langpack/2.2/ - look at the bottom of the page to see the last update. At the same time, they become available for Moodle sites for automatic update.

The stage can also be used to import strings from files and to merge or compare versions of language packs.

=== Importing a file ===

[[image:amos-screenshot-stage-empty.png|300px|thumb|right|Empty stage allows you to import strings from a file]]
Strings can be translated offline and uploaded back to AMOS using the stage page. The only supported format at the moment is common PHP format used by Moodle where strings are defined in associative array called $string. For obvious security reasons, AMOS can not actually execute PHP files uploaded by users. Instead, it parses the uploaded file in a similar way as PHP parser, looking for patterns that are considered as valid string definition. That means that not every valid PHP code is valid string definition. AMOS parser requires following conditions are met:

* the filename is valid component name used by Moodle, for example moodle.php, enrol_manual.php or workshop.php
* the file is valid PHP code without syntax errors - that means is passes the PHP lint check
* strings are defined as elements of global array $string
* strings are single quoted constants

Example of a valid file to import into AMOS (filename countries.php, Czech translation)

<?php

$string['AE'] = 'Spojené Arabské emiráty';
$string['AF'] = 'Afghánistán';
$string['CH'] = 'Švýcarsko';
$string['HU'] = 'Maďarsko';

?>

During the import, strings found in the file are added into your stage as if they were translated via web. You can commit them into repository if you have such privilege.

=== Using stashes ===

At any moment, you can save a snapshot of the current stage. We call such snapshot a ''stash''. Stashed strings are kept forever until you drop them manually (please do not abuse this and keep your stashes reasonable big). To manage your stash, click on Stashes in the right menu of AMOS. You just see a list of the stashes. There are "peekaboo" buttons that appear when you mouse hoover over the stashes. The stash can be ''applied'' so that the stashed strings are copied back to the stage. What the ''pop'' does is apply and drop (delete) the stash. ''drop'' is like delete. ''submit to maintainer'' opens a form for doing just that.

There is one special stash record for every user called autosave stash. This stash keeps the most recent state of the stage. You may find it useful if you loose the current stage for any reason - your browser crashes, your internet connectivity dies or you accidentally unstage all strings. If that happens, just apply the autosave stash to get your work back. The autosave stash is updated every time you stage a string. So if your stage is empty and your autosave stash is full of strings and you go into the translator first without applying the stash, the autosave will be replaced with the new translated string. We recommend to experiment a bit with this feature first.

=== Using the log tool ===

The Log page allows even anonymous users to search in the history of commits tracked by AMOS. At the top of the page there is a filter that allows you to look for a particular information or report. It is important to realize how the filter actually works. Searching and filtering happens in two steps (this was necessary for performance reasons):

* Firstly, commit records are searched based on the criteria specified in the Commit filter form. If there are more commits found matching the filter settings, only 100 most recent commits are processed.
* Then, within the commits found, either all string modification records are returned, or you can filter these records, too. Settings in String filter form section are used in that case.

By default, the filter looks for all commits since the last time you logged in and than displays only strings at the currently translated branch modified by those commits.

===Language packs and Moodle versions===

When a new Moodle version is released, it will become the default version on your Amos - Translator page (see tick boxes at the top).

The suggested work flow is to continue your translation work for the new Moodle version and merge your work in the older versions.
You can do that using the Amos - Stage page: Set the source version to the version you were working in and set the target version to the version you want the strings to be copied to.

== Contributing to a language pack ==

AMOS allows community members to help with the translation of Moodle strings. AMOS Contributions page tracks all submitted translations and their current status. Before you start working on a translation, please communicate with the language pack maintainer (to be found on https://docs.moodle.org/en/Translation_credits).

=== Steps for the contributor ===

[[image:amos-screenshot-contribution-new.png|300px|thumb|right|Submitting a contribution form]]
# Contact the language pack maintainer about your intention to contribute to the language pack
# Use AMOS translator interface to translate missing strings or amend the current translation
# Go to the Stage page
# Click 'Submit to maintainers' button
# At 'Submitting a contribution' page, please provide a message for maintainers describing your work and why you would like to see your contribution included. You can cancel the submission at this moment yet. If you are sure, click 'Submit to maintainers'.
# Your stage will submitted into the contributions database. If there were more languages affected by your contribution, the stage will be divided into separate contribution records, one per each language. The language pack maintainers will be notified by email about your new contribution.
# Language pack maintainers will be able to apply your work into their stage, review it and eventually commit. You will receive automatically generated email when the status of contribution changes (typically when a maintainer starts a review of your work and then when they accept or reject it).
# Use contribution record comments for further communication with the maintainer about the submitted translation.

=== Steps for the maintainer, making own contributions===

# Use AMOS translator interface to translate missing strings or amend the current translation
# Go to the Stage page
# Make a meaningfull comment about your work in the 'Commit message' form
# Click on 'Commit'

=== Steps for the maintainer, approving users contributions===

[[image:amos-screenshot-contribution-details.png|300px|thumb|right|Contribution details page]]
# When a user submits new contribution, you will receive automatically generated email from AMOS
# Go to the Contributions page to see a list of all new incoming contributions. Click the link in the table to open the contribution details page
# Press 'Start review' button. That will assign the contribution to yourself, change the status from 'New' to 'In review', send automatically generated email to the contributor and will copy the submitted strings into your stage. You should check that your stage is empty before you apply the submitted strings, unless you want to merge several contributions into one commit.
# Review the submitted strings, eventually edit them. Commit the stage. It is nice to mention the contributor's name in the commit message and attribute the original authorship to them.
# Go back to the contribution record and change the status to Accepted or Rejected. Automatically generated email will be sent to the contributor whenever you change the status.
# Use contribution record comments for further communication with the contributor about the submitted translation.
# Accepted and Rejected contributions are not shown at the contributions page unless you press 'Show resolved contributions' button.

== See also ==

* [[Translation]] for more information about the process of Moodle 2.x translation
* [[Development:Languages/AMOS]] for the AMOS internals documentation

[[Category:Language]]

[[fr:AMOS]]

Theme settings

2011-11-28T13:29:01Z

Benteo: /* Allow theme changes in the URL */ ? added > ?theme={themename}

{{Themes}}
== Theme settings ==
An administrator can change theme settings in ''Settings > Site administration > Appearance > Themes > Theme settings''.

[[File:Themesettings.png]]

===Theme list===
This lists the themes available for course and user themes. Leave this blank to allow any valid theme to be used. If you want to shorten the theme menu, you may specify a comma-separated list of names, though don't use spaces (e.g. standard,orangewhite).

You can preview the available themes in ''Settings > Site Administration > Appearance > Themes > Themes selector.''

===Theme designer mode===
Turn this on if you are designing and testing themes as it will stop the themes being cached and enable you to see theme changes quickly. (You can also do this with the Clear theme cache button on the theme selector page.)

===Allow user themes===
If the option ''allowuserthemes'' is enabled, each user may select their preferred theme on the edit profile page. All Moodle pages will be displayed in the user's theme, apart from courses where a course theme has been set.

===Allow course themes===
If you enable this, then teachers will be able to set their own course themes. Course themes override all other theme choices (site, user, or session themes).

*If the option ''allowcoursethemes'' is enabled, each editing teacher may select their course theme via the Force theme option on the [[course/edit|Course settings]] page. The course will always be displayed in the theme specified in the course setting, with user and the site themes being overwritten.

===Allow category themes===
When enabled, themes can be set at the category level. This will affect all child categories and courses unless they have specifically set their own theme. WARNING: Enabling category themes may affect performance.

===Allow theme changes in the URL===
*If this is checked then the theme may be changed by adding the ?theme={themename} to the URL in the browser.

===Allow users to hide blocks===
Allows users to display and hide blocks

===Allow blocks to use the docks===
*If the theme allows it, then checking this will allow the user to move blocks to the side dock.

===Custom menu items===
The custommenuitems setting allows you to create a drop down menu that can be displayed by themes that support it. Currently all themes that are provided with Moodle 2.0 support this custom menu.

You are able to create the custom menu by entering custom menu items one per line into the setting. Each item is preceded by a number of hyphens (-), the number of hyphens determines the depth of the item. So items that are '''NOT''' preceded by a hyphen appear on the top level of the menu (always visible), items with a single hyphen appear on a drop down menu below the previous top level item, and items with two hyphens appear on a drop down menu below the previous first level item and so on.

The content of each item is constructed of up to three bits, each separated by a '''|''' (Shift + \) character. The bits are '''label''' | '''url''' | '''tooltip'''.
; label : This is the text that will be shown within the menu item. You must specify a label for every item on the menu.
; url : This is the URL that the user will be taken to it they click the menu item. This is optional, if not provided then the item will not link anywhere.
; tooltip : If you provide a URL you can also choose to provide a tooltip for the link that is created with the URL. This is optional and if not set the label is used as the tooltip for the menu item.

The following is an example of how you would create a custom menu:

<pre>
Moodle community|http://moodle.org
-Moodle free support|http://moodle.org/support
-Moodle development|http://moodle.org/development
--Moodle Tracker|http://tracker.moodle.org
--Moodle Docs|https://docs.moodle.org
-Moodle News|http://moodle.org/news
Moodle company
-Moodle commercial hosting|http://moodle.com/hosting
-Moodle commercial support|http://moodle.com/support
</pre>

Note: The custom menu does not escape characters within the label, if you want to use a special HTML character such as an ampersand you must escape it yourself within the label. e.g. use & instead of &.

For more information on this setting please see the ''Using Moodle'' forum discussion [http://moodle.org/mod/forum/discuss.php?d=149803 Moodle 2.0: Custom menu in core]

==== Multilanguage support ====

You can add a language code (or a comma separated list of codes) as the 4th item of the line. The line will be then printed if and only if the user has currently selected the listed language. For example:

<pre><nowiki>
English only|http://moodle.com|English only item|en
German only|http://moodle.de|Deutsch|de,de_du,de_kids
</nowiki></pre>

===Enable device detection===
Will detect mobile and tablets that identify themselves via the web browser at the time of login to Moodle. These work with the theme selector. When the theme selector has identified a default, mobile and tablet themes, this feature will use that theme.

===Device detection regular expressions===
This will allow you to customize the theme selector options. For example, you can add a custom theme for IE6 and another for Windows CE by entering the identifying expressions the browser sends and the "Return value" you want to display as the theme selectors "Device type".

==Special themes==

=== Session themes ===
Moodle offers an additional way to set a theme - the '''session theme'''. This is set with the URL and lasts until you log out. When you next login, the site/course/user themes are active again. This option is great for theme testing and works perfectly when you want to enable different themes for different situations.

For example you can offer a special link for PDA users and integrate the session theme ''orangewhitepda'' in that link. Nobody needs to change any settings, you just click on that link. The session theme is called by the URL parameter <code>&theme=orangewhitepda</code>. The whole URL without the session theme could look like <code><nowiki>http://mymoodlesite.org/course/view.php?id=18</nowiki></code> and with the parameter for the PDA theme like <code><nowiki>"http://mymoodlesite.org/course/view.php?id=18&theme=orangewhitepda"</nowiki></code>.

In a standard Moodle installation, session themes are not active. To activate them the administrator must add the parameter <code>$CFG->allowthemechangeonurl = true;</code> to the Moodle ''config.php'' file in the Moodle base directory.

=== Page theme ===
A page theme is for special page-only themes set by code.

== Theme hierarchy ==
Here is the usual order that themes are considered by the Moodle interface.

{| style="border:1px dashed #ddd"
|- style="vertical-align:top;text-align:left"
!Theme type
! style="background:#eee"|Overwrites
!Display
! style="background:#eee"|Setting type
|- style="vertical-align:top"
|Site
|style="background:#eee"| -
|all pages*
|style="background:#eee"|saved in theme profile
|- style="vertical-align:top"
|User
|style="background:#eee"|Site theme
|all pages*
|style="background:#eee"|saved in user profile
|- style="vertical-align:top"
|Course
|style="background:#eee"|Site, user and session themes
|one course
|style="background:#eee"|saved in course profile
|- style="vertical-align:top"
|Session
|style="background:#eee"|Site and user themes
|all pages*
|style="background:#eee"|temporary until logout
|}
(* except courses with the course theme set)

=== Change default hierarchy===
The priority of themes can be set via the /moodle/config.php file. The order defines which theme wins when there are several set at different levels. You can set a variable called $CFG->themeorder (see config-dist.php for more details). By default it is set to:

<code><nowiki>$CFG->themeorder = array('page', 'course', 'category', 'session', 'user', 'site');</nowiki></code>

==Particular theme settings==

Logo, tagline, link colour, column width, custom CSS and other settings for a particular theme may be set by an administrator in ''Settings > Site administration > Appearance > Themes > Theme name''.

==See also==

*[http://www.youtube.com/watch?v=mCVsJ3Wsoj8 Video demonstrating how to set a category theme in Moodle 1.9]

[[es:Configuración de temas]]
[[fr:Configuration des thèmes]]
[[ja:テーマ設定]]
[[de:Design-Einstellungen]]

Create group

2009-12-02T12:12:15Z

Benteo: /* See also */ ... and changed it to groupings :-)

[[Image:Create group.png|thumb|Creating a group in Moodle 1.9]]
To create a new group:

#Click the "Create group" button at the bottom of the groups page.
#Set the options for the group (see below).
#Click the "Save changes" button.

==Group name==
This is the name of the group displayed in various places throughout the course.

==Group description==
Write a brief description of the group and its purpose. The description is displayed above the list of group members on the participants page.

==Enrolment key==
Enrolment keys allow users to enrol themselves on a course. You can set an [[enrolment key]] in the [[Course settings|course settings]]. If you set a group enrolment key too, then anyone who enrols on the course using that key will also automatically be made a member of the group.

Note: You need to set an enrolment key in your course settings, as well as setting a group enrolment key, otherwise students will not be prompted to enter a key when they attempt to enrol. Students only need to enter the group enrolment key and do
not need to know the course settings enrolment key.

:''TIP:'' Make sure that the first letter for each group enrolment key is the same as the course settings enrolment key. If a student makes a mistake typing in the enrolment key, they are provided with the first letter of the course settings enrolment key as a hint. (''The 're-enter' text that contains the hint can also be edited using the admin's language editing settings to whatever you wish. Keeping the hint is not necessary.'')

==Hide picture==
Hiding the picture for the group prevents the group picture from being displayed in various activities throughout your course.

==New picture==
You can upload a profile picture for the group or replace an old picture with a new one. Pictures are displayed on the participants page and also on other activities like forums posts (unless you don't want that - see above setting).

==See also==
*[[Groups]]
*[[Assign users to group]]
*[http://www.youtube.com/watch?v=Y1apj-OPuVA Video: Group Enrolment Key]
*[[Groupings]]

[[Category:Groups]]
[[Category:Enrolment]]

[[fr:Créer un groupe]]
[[pl:Tworzenie grupy]]
[[ja:グループを作成する]]
[[de:Gruppen verwalten]]

Create group

2009-12-02T12:10:34Z

Benteo: Added 'Create grouping' to 'See also'

[[Image:Create group.png|thumb|Creating a group in Moodle 1.9]]
To create a new group:

#Click the "Create group" button at the bottom of the groups page.
#Set the options for the group (see below).
#Click the "Save changes" button.

==Group name==
This is the name of the group displayed in various places throughout the course.

==Group description==
Write a brief description of the group and its purpose. The description is displayed above the list of group members on the participants page.

==Enrolment key==
Enrolment keys allow users to enrol themselves on a course. You can set an [[enrolment key]] in the [[Course settings|course settings]]. If you set a group enrolment key too, then anyone who enrols on the course using that key will also automatically be made a member of the group.

Note: You need to set an enrolment key in your course settings, as well as setting a group enrolment key, otherwise students will not be prompted to enter a key when they attempt to enrol. Students only need to enter the group enrolment key and do
not need to know the course settings enrolment key.

:''TIP:'' Make sure that the first letter for each group enrolment key is the same as the course settings enrolment key. If a student makes a mistake typing in the enrolment key, they are provided with the first letter of the course settings enrolment key as a hint. (''The 're-enter' text that contains the hint can also be edited using the admin's language editing settings to whatever you wish. Keeping the hint is not necessary.'')

==Hide picture==
Hiding the picture for the group prevents the group picture from being displayed in various activities throughout your course.

==New picture==
You can upload a profile picture for the group or replace an old picture with a new one. Pictures are displayed on the participants page and also on other activities like forums posts (unless you don't want that - see above setting).

==See also==
*[[Groups]]
*[[Assign users to group]]
*[http://www.youtube.com/watch?v=Y1apj-OPuVA Video: Group Enrolment Key]
*[[Create grouping]]

[[Category:Groups]]
[[Category:Enrolment]]

[[fr:Créer un groupe]]
[[pl:Tworzenie grupy]]
[[ja:グループを作成する]]
[[de:Gruppen verwalten]]

Assignment submissions

2008-04-24T12:58:25Z

Benteo: Final grade column added

{{Assignments}}
To view the submitted assignment, the teacher should click on the assignment activity they wish to review. Then click on "View 'x' submitted assignments" link in the upper right corner.

==Overview of submissions page ==
The submissions page contains a table with headings:

# '''First name and Surname''' (along with the photograph)
# '''Grade''' (for the submitted assignment)
# '''Comment''' (the feedback information you have written in the feedback field while grading the assignment)
# '''Last modified (Student)''' (the date of the last modification of the assignment by the student)
# '''Last modified (Teacher)''' (the date of the last modification of the assignment by the teacher)
# '''Status''' (with which you can move to the page where you grade the submitted assignment or, in case it's been graded, update the grade and/or the comment)
# '''Final grade'''

Above the table there is an alphabetical index, which helps you narrow down the number of students shown on one page only to those whose surname (or name) starts with the same letter. That is particularly helpful in case of a large number of course participants.

The list of submissions may be sorted by clicking on a particular heading. Clicking twice on the same heading sorts the list in the opposite order. If the table is too large then columns may be collapsed by clicking on the Hide icon next to a particular column heading.

By default, 10 submissions are shown per page, though this may be changed at the bottom of the page.

==Grade submission==
===Basic grading assignments===
To grade or mark a submission, click on the Grade link opposite a particular student's name. A new window will open containing a feedback area.

Once you've reviewed the student's assignment, pick the grade for the assignment from the dropdown list. (You set the scale when you created the assignment.) Below the grade scale, you can type comments regarding their work. When you're done, click "Save changes" or "Save and show next".

===Quick grading assignments===
You may prefer to use "quick grading" by checking the box at the bottom of the submissions page. This enables you to quickly grade multiple assignments all on one page, rather than one by one in a new window. Simply add the grades and comments then when you're done, click "Save all my feedback" at the bottom of the page.

==Tutorial on feedback and grading==

#Click directly on the assignment whose submissions you wish to mark.
#Click on View submitted assignments (top right)
#Before going any further, I would like to draw your attention to some settings on this page. Scroll to the bottom and you will see: Submissions per page and Allow quick grading
##I find it useful to set the submissions per page quite large so as not to have to keep opening new pages to see more students.
##Normally you have to click on Grade on the right to open a new page where you can view the submission and enter marks and type some feedback text. If you Allow quick grading you can do this on the same line as the submission is listed.
##Save preferences if you change either of these. For the rest of this, I will assume that you have enabled Allow quick grading.
#On the line across for each person, if they have submited, you will see a link to a file. If you click on the file it will either open in a new browser window (if your browser is capable of viewing the document), or it will ask you if you wish to save to disc or open using the appropriate application program.
#Once you have viewed their submission, you can then indicate a mark from the drop down list, and/or enter your comments in the box.
#You can do this for many students, however the marks are not stored until you select Save all my feedback either at the top or the bottom of the list of student. It is advisable not to leave too long a time before doing this. After you do this, all students who you left feedback for are sent an email to let them know that there is feedback available for them.
#You might not that if you have a long list of students you can sort in many ways, firstname, lastname etc by clicking on the blue link at the top of each column. A useful way is to sort by "Last modified Student" (get the arrow pointing upwards - ie. latest first) which will show the most recently submitted. If you allow more than one submission it is also useful to compare "Last modified student" date with "Last modified Lecturer" date as you can spot who has resubmitted since you last commented.

[[Category:Assignment]]

==See also==
*Using Moodle [http://moodle.org/mod/forum/discuss.php?d=83537 Deleting Submitted Assignments] forum discussion
*Using Moodle [http://moodle.org/mod/forum/discuss.php?d=86224 Indication of submitted work...] forum discussion

[[cs:Odevzdané úkoly]]

Sandbox

2008-04-24T12:45:07Z

Benteo:

==Welcome to the Sandbox page==
Try editing this page. Some people try out things here before placing them on other pages. From time to time this page is erased. --[[User:charles haywood]]| 4:08 PM 3/19/2008(CST)

show a preview of How '''''this'''''will appear on screen?

Here ''is my edit'' - '''change fonts'''[[Image:Example.jpg]]--[[User:Charles Haywood|Charles Haywood]]4:40 PM 3/19/2008(CST)
----

And I added to it.

Hi this is Charles and how can I adding to this page. Does this system actually offer something useful for online course delivery that is free content management user logon and website delivery systems?

Can this site use the new url tool?

Where do I add pages? A good question...

xxx
jkkl

Sandbox

2008-04-24T12:44:50Z

Benteo:

Sandbox

2008-04-24T12:43:58Z

Benteo: x added

Adding/editing a glossary

2007-05-14T10:17:18Z

Benteo: /* Display format */ Edit format table

{{Glossaries}}

==Name/Description==

Here you should describe the purpose of the glossary, provide instructions or background information, links etc.

==Entries shown per page==

This defines the number of entries shown per page. The glossary can be configured to restrict the number of entries shown per page. If you have a large number of automatically-linked entries you should set this number lower to prevent long loading times.

==Glossary type==

Here you can decide whether the glossary will be main or secondary. The glossary system allows you to export entries from any secondary glossary to the main one of the course. In order to do this, you should specify which glossary is the main one. You can only have one main glossary per course and only teachers are allowed to update it.

In addition, a glossary may be specified as "Global" (by administrators only in versions prior to 1.7). A Global glossary is different to a normal Main or Secondary glossary in that the entries create automatic links throughout the whole site (and not just in the same course the glossary belongs to or an associated metacourse).

==Students can add entries==

This lets you specify whether a student can or cannot add, edit or delete his/her own entries. Entries exported to a main glossary can be updated or deleted by teachers only, so this setting only applies to secondary glossaries. (Note: A teacher can edit or delete any entry at any time.)

Note: From Moodle 1.7 onwards, this setting has been replaced with a role override and preventing the capability [[Capabilities/mod/glossary:write|mod/glossary:write]].

==Duplicated entries allowed==

Turning that on allows multiple entries to use the same concept name.

==Allow comments on entries==

That allows students to add comments to glossary entries. You can choose whether this feature is enabled or disabled. Teachers always can add comments to glossary entries.

==Allow print view==

That allows students to use the print view of the glossary. You can choose whether this feature is enabled or disabled. Teachers always can use the print view.

==Automatically link glossary entries==

If site-wide glossary autolinking is enabled by an administrator (see [[Filters (administrator)]] for further details), then turning this on allows individual entries in this glossary to be automatically linked whenever the concept words and phrases appear throughout the rest of the same course. This includes forum postings, internal resources, week summaries and so on. Note that enabling linking for the glossary does not automatically turn on linking for each entry - linking needs to be set for each entry individually. If you do not want particular text to be linked (in a forum posting, say) then you should add <nolink> and </nolink> tags around the text. Note that category names are also linked.

==Approved by default==

That allows the teacher to define what happens to new entries added by students. They can be automatically made available to everyone, otherwise the teacher will have to approve each one.

==Display format==

That specifies the way that each entry will be shown within the glossary.

The default formats are:

* Simple Dictionary

That looks like a conventional dictionary with separate entries. No authors are displayed and attachments are shown as links.

* Continuous

That shows the entries one after other without any kind of separation but the editing icons.

* Full with Author

A forum-like display format showing author's data. Attachments are shown as links.

* Full without Author

A forum-like display format that does not show author's data. Attachments are shown as links.

* Encyclopedia

Like 'Full with Author' but attached images are shown inline.

* FAQ

Useful for displaying lists of Frequently Asked Questions. It automatically appends the words QUESTION and ANSWER in the concept and definition respectively.

<table style="text-align: center;" border="1" cellpadding="2" cellspacing="0">
<tr>
<th style="text-align: left; width: 15em;">Format</th>
<th style="width: 4em;">Entry</th>
<th style="width: 4em;">Author</th>
<th style="width: 4em;">Date</th>

<th style="width: 4em;">Definition</th>
<th style="width: 4em;">Images</th>
<th style="width: 4em;">Attachments</th>
</tr>
<tr>
<td style="text-align: left;">Entry list</td>
<td>x</td>

<td>- </td>
<td>-</td>
<td>x*</td>
<td>x*</td>
<td>link*</td>
</tr>

<tr>
<td style="text-align: left;">Simple Dictionary</td>
<td>x</td>
<td>-</td>
<td>-</td>
<td>x</td>

<td>x</td>
<td>link</td>
</tr>
<tr>
<td style="text-align: left;">Continuous</td>
<td>x</td>
<td>-</td>

<td>-</td>
<td>x</td>
<td>x</td>
<td>link</td>
</tr>
<tr>
<td style="text-align: left;">FAQ</td>

<td>x</td>
<td>-</td>
<td>x</td>
<td>x</td>
<td>x</td>
<td>link</td>

</tr>
<tr>
<td style="text-align: left;">Full without Author</td>
<td>x</td>
<td>-</td>
<td>x</td>
<td>x</td>

<td>x</td>
<td>link</td>
</tr>
<tr>
<td style="text-align: left;">Full with Author</td>
<td>x</td>
<td>x</td>

<td>x</td>
<td>x</td>
<td>x</td>
<td>link</td>
</tr>
<tr>
<td style="text-align: left;">Encyclopedia</td>

<td>x</td>
<td>x</td>
<td>x</td>
<td>x</td>
<td>x</td>
<td>x**</td>

</tr>
</table>
* Will be shown in a pop-up window.
* * Attached images are shown inline.

===Browsing options in Alphabet Display===

You can customize the way a user can browse a glossary. Browsing and searching are always available, but you can define three more options:
# SHOW SPECIAL Enable or disable browsing by special characters like @, #, etc.
# SHOW ALPHABET Enable or disable browsing by alphabetic letters.
# SHOW ALL Enable or disable browsing of all entries at once.

==Allow entries to be rated==

As in forums, you can allow entries to be rated. Here you will have to consider enabling two options:

===Use ratings===

If you decide to rate posts on the forum, you will have to define settings of the three following aspects:

* Users

If you want everybody to rate posts, choose 'Everyone can rate posts'. Otherwise, pick 'Only teachers can rate posts'.

* View

If you want to keep the grades known only to the individual students graded, you should choose the option 'Students can only see their own ratings'. If there is no such a need, opt for 'Students can see everyone's ratings'.

* Grade

There are several grading scales you can choose from. You can give a number of points to each post (from 1 to 100) or you can opt for two other scales: '''Scale: satisfactory''' (Outstanding, Satisfactory and Not satisfactory) or '''Separate and Connected ways of knowing''' (Mostly Connected Knowing, Separate and Connected, Mostly Separate Knowing). More information about the latter one are to be found [[Separate and Connected ways of knowing|here]].

===Restrict ratings to posts with dates in this range===

If you enable the '''Use ratings''' option, you will also face the necessity of choosing whether or not enable another option restricting ratings to posts in terms of time.

==Visible to students==

You can also decide on whether or not the glossary will be seen by the students. You can hide the activity from students by selecting 'Hide'. It is useful if you don't want to make the activity available immediately.

[[Category:Teacher]]
[[Category:Glossary]]

[[fr:Ajouter/Éditer un glossaire]]

Adding/editing a glossary

2007-05-14T10:12:41Z

Benteo: /* Display format */

{{Glossaries}}

==Name/Description==

Here you should describe the purpose of the glossary, provide instructions or background information, links etc.

==Entries shown per page==

This defines the number of entries shown per page. The glossary can be configured to restrict the number of entries shown per page. If you have a large number of automatically-linked entries you should set this number lower to prevent long loading times.

==Glossary type==

Here you can decide whether the glossary will be main or secondary. The glossary system allows you to export entries from any secondary glossary to the main one of the course. In order to do this, you should specify which glossary is the main one. You can only have one main glossary per course and only teachers are allowed to update it.

In addition, a glossary may be specified as "Global" (by administrators only in versions prior to 1.7). A Global glossary is different to a normal Main or Secondary glossary in that the entries create automatic links throughout the whole site (and not just in the same course the glossary belongs to or an associated metacourse).

==Students can add entries==

This lets you specify whether a student can or cannot add, edit or delete his/her own entries. Entries exported to a main glossary can be updated or deleted by teachers only, so this setting only applies to secondary glossaries. (Note: A teacher can edit or delete any entry at any time.)

Note: From Moodle 1.7 onwards, this setting has been replaced with a role override and preventing the capability [[Capabilities/mod/glossary:write|mod/glossary:write]].

==Duplicated entries allowed==

Turning that on allows multiple entries to use the same concept name.

==Allow comments on entries==

That allows students to add comments to glossary entries. You can choose whether this feature is enabled or disabled. Teachers always can add comments to glossary entries.

==Allow print view==

That allows students to use the print view of the glossary. You can choose whether this feature is enabled or disabled. Teachers always can use the print view.

==Automatically link glossary entries==

If site-wide glossary autolinking is enabled by an administrator (see [[Filters (administrator)]] for further details), then turning this on allows individual entries in this glossary to be automatically linked whenever the concept words and phrases appear throughout the rest of the same course. This includes forum postings, internal resources, week summaries and so on. Note that enabling linking for the glossary does not automatically turn on linking for each entry - linking needs to be set for each entry individually. If you do not want particular text to be linked (in a forum posting, say) then you should add <nolink> and </nolink> tags around the text. Note that category names are also linked.

==Approved by default==

That allows the teacher to define what happens to new entries added by students. They can be automatically made available to everyone, otherwise the teacher will have to approve each one.

==Display format==

That specifies the way that each entry will be shown within the glossary.

The default formats are:

* Simple Dictionary

That looks like a conventional dictionary with separate entries. No authors are displayed and attachments are shown as links.

* Continuous

That shows the entries one after other without any kind of separation but the editing icons.

* Full with Author

A forum-like display format showing author's data. Attachments are shown as links.

* Full without Author

A forum-like display format that does not show author's data. Attachments are shown as links.

* Encyclopedia

Like 'Full with Author' but attached images are shown inline.

* FAQ

Useful for displaying lists of Frequently Asked Questions. It automatically appends the words QUESTION and ANSWER in the concept and definition respectively.

<table style="text-align: center;" border="1" cellpadding="2" cellspacing="0">
<tr>
<th style="text-align: left; width: 15em;">Format</th>
<th style="width: 4em;">Entry</th>
<th style="width: 4em;">Author</th>
<th style="width: 4em;">Date</th>

<th style="width: 4em;">Definition</th>
<th style="width: 4em;">Grafics</th>
<th style="width: 4em;">Attachments</th>
</tr>
<tr>
<td style="text-align: left;">Entry list</td>
<td>x</td>

<td>- </td>
<td>-</td>
<td>x*</td>
<td>x*</td>
<td>link*</td>
</tr>

<tr>
<td style="text-align: left;">Simple Dictionary</td>
<td>x</td>
<td>-</td>
<td>-</td>
<td>x</td>

<td>x</td>
<td>link</td>
</tr>
<tr>
<td style="text-align: left;">Continuous</td>
<td>x</td>
<td>-</td>

<td>-</td>
<td>x</td>
<td>x</td>
<td>link</td>
</tr>
<tr>
<td style="text-align: left;">FAQ</td>

<td>x</td>
<td>-</td>
<td>x</td>
<td>x</td>
<td>x</td>
<td>link</td>

</tr>
<tr>
<td style="text-align: left;">Full without Author</td>
<td>x</td>
<td>-</td>
<td>x</td>
<td>x</td>

<td>x</td>
<td>link</td>
</tr>
<tr>
<td style="text-align: left;">Full with Author</td>
<td>x</td>
<td>x</td>

<td>x</td>
<td>x</td>
<td>x</td>
<td>link</td>
</tr>
<tr>
<td style="text-align: left;">Encyclopedia</td>

<td>x</td>
<td>x</td>
<td>x</td>
<td>x</td>
<td>x</td>
<td>x**</td>

</tr>
</table>
* Will be shown in a pop-up window.
* * Attachments are shown inline.

===Browsing options in Alphabet Display===

You can customize the way a user can browse a glossary. Browsing and searching are always available, but you can define three more options:
# SHOW SPECIAL Enable or disable browsing by special characters like @, #, etc.
# SHOW ALPHABET Enable or disable browsing by alphabetic letters.
# SHOW ALL Enable or disable browsing of all entries at once.

==Allow entries to be rated==

As in forums, you can allow entries to be rated. Here you will have to consider enabling two options:

===Use ratings===

If you decide to rate posts on the forum, you will have to define settings of the three following aspects:

* Users

If you want everybody to rate posts, choose 'Everyone can rate posts'. Otherwise, pick 'Only teachers can rate posts'.

* View

If you want to keep the grades known only to the individual students graded, you should choose the option 'Students can only see their own ratings'. If there is no such a need, opt for 'Students can see everyone's ratings'.

* Grade

There are several grading scales you can choose from. You can give a number of points to each post (from 1 to 100) or you can opt for two other scales: '''Scale: satisfactory''' (Outstanding, Satisfactory and Not satisfactory) or '''Separate and Connected ways of knowing''' (Mostly Connected Knowing, Separate and Connected, Mostly Separate Knowing). More information about the latter one are to be found [[Separate and Connected ways of knowing|here]].

===Restrict ratings to posts with dates in this range===

If you enable the '''Use ratings''' option, you will also face the necessity of choosing whether or not enable another option restricting ratings to posts in terms of time.

==Visible to students==

You can also decide on whether or not the glossary will be seen by the students. You can hide the activity from students by selecting 'Hide'. It is useful if you don't want to make the activity available immediately.

[[Category:Teacher]]
[[Category:Glossary]]

[[fr:Ajouter/Éditer un glossaire]]

Sandbox

2007-05-14T09:51:48Z

Benteo: /* bbbbbb */

abcdef deneme 1 2

Very nice :-) 
Moodle is Great! 

'''== אחת שתיים שלו ארבע
==== Headline text ==== Headline text =='''Bold text''''''

====bbbbbb====
[[Table]]

==Aesthetic buggery to follow!==
<hr size=5>
<hr size=10>
<hr size=20>
... well, that's too bad: <tt> I was expecting to be able to make larger headers! [pout!]</tt>

:Interesting. Don't know much about HTML but
#remember this is a Mediawiki.
#When I want to try something off the beaten track in MoodleDocs, I [http://meta.wikimedia.org/wiki/Help:Editing#Templates start here with a search on editing tips].
#Since I am a clutz, I created a web page using a word processor. Then opened my browser and revealed the page code. Then placed it below. So you can make larger headers several ways. chris collman
::see examples below

==This is 26.opt test==

Notice it still is a header just not the default font

===This is a 3rd level - a little smaller===

====This is a 3rd level header - Probably no difference====

== Headline text ==

Martha is a radical

=Is a 1st level header - the larger header topic=

just to see what would happen

=This is a 400.opt font test

Hmm...

[[fr:Bac à sable]]

Just testing it out!

Seems OK!

Sandbox

2007-05-14T09:49:51Z

Benteo: /* bbbbbb */

abcdef deneme 1 2

Very nice :-) 
Moodle is Great! 

'''== אחת שתיים שלו ארבע
==== Headline text ==== Headline text =='''Bold text''''''

====bbbbbb====
Table

==Aesthetic buggery to follow!==
<hr size=5>
<hr size=10>
<hr size=20>
... well, that's too bad: <tt> I was expecting to be able to make larger headers! [pout!]</tt>

:Interesting. Don't know much about HTML but
#remember this is a Mediawiki.
#When I want to try something off the beaten track in MoodleDocs, I [http://meta.wikimedia.org/wiki/Help:Editing#Templates start here with a search on editing tips].
#Since I am a clutz, I created a web page using a word processor. Then opened my browser and revealed the page code. Then placed it below. So you can make larger headers several ways. chris collman
::see examples below

==This is 26.opt test==

Notice it still is a header just not the default font

===This is a 3rd level - a little smaller===

====This is a 3rd level header - Probably no difference====

== Headline text ==

Martha is a radical

=Is a 1st level header - the larger header topic=

just to see what would happen

=This is a 400.opt font test

Hmm...

[[fr:Bac à sable]]

Just testing it out!

Seems OK!

Using Moodle book

2007-04-03T12:29:50Z

Benteo: Added page numbers

[[Image:UsingMoodleBook.jpg|right]]
[http://moodle.org/user/view.php?id=9318&course=5 Jason Cole] has kindly allowed us to freely use excerpts from his book '''Using Moodle''' in this documentation wiki. If you do use it on a page then please add the <code><nowiki>[[Template:excerpted from Jason Cole]]</nowiki></code> at the bottom of the page.

For more information about the book see its [http://www.oreilly.com/catalog/moodle/index.html publisher's web page] or [http://www.amazon.com/gp/product/0596008635/ entry on amazon.com].

==Contents==
*[http://download.moodle.org/docs/using_moodle/table_of_contents.pdf Table of Contents] (8 pages)
*[http://download.moodle.org/docs/using_moodle/preface.pdf Preface] (4 pages)
*[http://download.moodle.org/docs/using_moodle/ch1_introduction.pdf Chapter 1 Introduction] p. 1 (6 pages)
*[http://download.moodle.org/docs/using_moodle/ch2_basics.pdf Chapter 2 Moodle Basics] p. 7 (26 pages)
*[http://download.moodle.org/docs/using_moodle/ch3_content.pdf Chapter 3 Creating and Managing Content] p. 33 (18 pages)
*[http://download.moodle.org/docs/using_moodle/ch4_forums.pdf Chapter 4 Using Forums, Chats and Dialogues] p. 51 (20 pages)
*[http://download.moodle.org/docs/using_moodle/ch5_quizzes.pdf Chapter 5 Quizzes] p. 24 (71 pages)
*[http://download.moodle.org/docs/using_moodle/ch6_workshops.pdf Chapter 6 Workshops] p. 95 (20 pages)
*[http://download.moodle.org/docs/using_moodle/ch7_assignments.pdf Chapter 7 Assignments and Exercises] p. 115 (12 pages)
*[http://download.moodle.org/docs/using_moodle/ch8_journals.pdf Chapter 8 Journals] p. 127 (10 pages)
*[http://download.moodle.org/docs/using_moodle/ch9_glossaries.pdf Chapter 9 Glossaries] p. 137 (12 pages)
*[http://download.moodle.org/docs/using_moodle/ch10_lessons.pdf Chapter 10 Lessons] p. 149 (12 pages)
*[http://download.moodle.org/docs/using_moodle/ch11_wikis.pdf Chapter 11 Wikis] p. 161 (12 pages)
*[http://download.moodle.org/docs/using_moodle/ch12_grades.pdf Chapter 12 Grades and Scales] p. 171 (6 pages)
*[http://download.moodle.org/docs/using_moodle/ch13_managing_classes.pdf Chapter 13 Managing Your Class] p. 177 (10 pages)
*[http://download.moodle.org/docs/using_moodle/ch14_surveys.pdf Chapter 14 Surveys and Choice] p. 187 (6 pages)
*[http://download.moodle.org/docs/using_moodle/ch15_class_design.pdf Chapter 15 Putting It All Together (Class Design)] p. 193 (8 pages)
*[http://download.moodle.org/docs/using_moodle/ch16_server_admin.pdf Chapter 16 Server Administration] p. 201 (6 pages)
*[http://download.moodle.org/docs/using_moodle/index.pdf Index] p. 217 (4 pages)

[[Category:Teacher]]
[[Category:Administrator]]
[[Category:Books]]

You Might Be a Moodler

2006-09-04T07:39:30Z

Benteo:

In the spirit of Jeff Foxworthy's ''You Might be a Redneck'' - http://www.jefffoxworthy.com/comedy/jod/index.shtml

*If you have ever turned on a football game and and the orange uniforms of one team caused you to leap up from the sofa and check out moodle.org, you might be a Moodler.

*If you type "moodle.org" in your browser when you intend to type "google.com."

*If you can spell '''Dougiamas''' without having to look it up.

*If you check the Moodle forums at 8:30 on a Saturday night.

*If you find yourself heading to the bugtracker when the dishwasher is broken.

*If you start seeing double square brackets around words you don't know the translation of.

*If your neighbours wonder why you named your cats Helen and Howard.

*Your spouse wants you to take up golf again because she hates being a 'moodle widow' more.

*You describe the color of something as "Moodle" orange.

*If you find yourself logging in to moodle.org during your summer holiday in Italy instead of enjoying the beautiful view or going to the beach. (Hi from Italy, Sigi)

*If you come all the way from Germany to the US during your summer holiday and in addition to visiting lots of places you must absolutely go to a small town in South Carolina to find out about the latest Moodle tricks

*You try to figure out how to grade e-mails from your friends without a drop down box