MoodleDocs - User contributions [en]

Standards

2020-12-10T07:28:02Z

Sarjona: Added IMS OBv2.0 reference

{{About Moodle}}
Moodle is a global learning management platform that supports open standards, and is interoperable by design to enable integration of external applications and information onto a single Moodle platform.

Our commitment to open standards means institutions and organisations can leverage Moodle to customise and extend features for any teaching and learning requirements, and benefit from increased cost efficiencies, flexibility, easier manageability along with performance and scalability advantages of using Moodle.

Moodle has achieved and is compliant with the following international standards:

{| cellpadding="10px"
| style="width: 170px;" | [[File:moodle-opensource.png|left|160px|middle]]
| ''' 1. An Open Source Initiative'''
Moodle is provided as a free, open source software that can be used, modified and freely distributed under the terms of the [[License|GNU General Public License]]. There are also plenty of documentation, course content and resources available on Moodle.org for anyone to use under the terms of various licenses, including:
*'''''Moodle Documentation''''': All documentation on [[Main_page|docs.moodle.org]] is openly licensed under the terms of the GNU General Public License, and is Copyright © 2005 onwards by the individual authors of each page.
|-
| style="width: 170px;" | [[File:moodle-imslticertified.png|left|160px|middle]]
| '''2. IMS LTI™ Certified'''
Moodle is certified Learning Tool Interoperability (LTI) v2.0 compliant. The LTI™ certification is a global technical standard of integrating learning applications. Users can integrate and present externally hosted applications and content within a single Moodle platform without having to develop and maintain custom integrations. Learn more about [[External_tool|integrating LTI resources onto your Moodle platform]]. In Moodle 3.1 onwards, Moodle can also act as an LTI tool provider with the [[Publish as LTI tool]].
|-
| style="width: 170px;" | [[File:moodle-scormcertified.png|left|160px|middle]]
| '''3. SCORM-ADL compliant'''
Moodle complies with the SCORM 1.2 specification. The SCORM (Sharable Content Object Reference Model) is a set of specifications and standards for web-based e-learning. Users can [[SCORM_module|deliver SCORM content via Moodle]] by uploading any SCORM or AICC package to the Moodle course. There are also community plugins available that provide limited support for the Experience API (Tin Can). A commercial plugin that provides full support for SCORM 2004 and the Experience API is also available in Plugins [https://moodle.org/plugins/view.php?plugin=mod_scormcloud/ here].
|-
| style="width: 170px;" | [[File:moodle-openbadges.png|left|160px|middle]]
| '''4. Open Badges '''
[http://openbadges.org/ Open Badges] project is an online standard to recognise and verify learning using digital badges. Integrated as a core feature in Moodle, any institution, organisation or individual can create and issue [[Badges|badges]] to learners on their Moodle learning platform. Moodle is certified [https://site.imsglobal.org/certifications/moodle/moodle#cert_pane_nid_402893 Open Badges v2.0 compliant as Issuer by IMS].
|-
| style="width: 170px;" | [[File:wcag21AA-logo.png|left|160px|middle]]
| '''5. WCAG 2.1 Level AA'''
Moodle has received [https://www.webkeyit.com/accessibility-services/accessibility-accreditations/moodle/ WCAG 2.1 Level AA accreditation] based on successfully resolving the issues identified in an external audit of key pages which were chosen as representative of its overall functionality and accessibility. Continuing work is being done to further improve the accessibility of other areas in Moodle in order to maintain conformance with the [https://www.w3.org/TR/WCAG21/ WCAG 2.1 Level AA guidelines].
|}

== Moodle and Interoperability ==

In supporting the seamless integration and use of content from different sources and multiple vendors, the Moodle platform is designed to exchange data using open industry standards for Web deployments, and supports:
# '''[[Authentication]]''' using:
#* [[LDAP_authentication|LDAP]], the most widely-used standard protocol for authentication.
#* Direct direct database lookup (e.g. in an external Oracle database), or on the Shibboleth protocol, or alternatively using IMAP, NNTP, CAS or FirstClass.
# '''[[Enrolment]]''' using:
#* LDAP server (e.g. Active Directory)
#* [[IMS_Enterprise|IMS Enterprise standard]] (via a downloadable plugin).
# '''Content''' using the import of Reusable Learning Objects, packaged according to the SCORM/AICC/IMS Content Packaging standards.
#* Moodle 1.9.5 is certified [[SCORM_module|SCORM]] 1.2 compliant.
#* Moodle supports [[IMS Common Cartridge import and export]]
#* The use of XML for content import/export (standard in Moodle). The "web services" method of exchanging data with other systems (e.g. via SOAP or XML-RPC) is not yet standard - but is in active development.
# '''Quiz questions''' via [[Import_questions|import]] and [[Export_questions|export]] using a variety of formats.
# '''[[RSS|RSS newsfeeds]]''', integrated into a Moodle site or course.
#* Forum discussions, glossary entries and database content can be accessed as RSS newsfeeds, and therefore integrated into other RSS-capable websites or systems.

[[fr:Standards]]
[[es:Estándares]]
[[de:Standards]]
[[it:Standard]]

Managing plagiarism prevention

2020-07-16T10:18:13Z

Sarjona: Replace UNPLAG to Unicheck

{{Plagiarism prevention}}
==Enabling plagiarism prevention==

To make use of plagiarism prevention, the feature must be enabled by an administrator by checking the enable plagiarism plugins box in ''Administration > Site administration > [[Advanced features]]''.

[[File:Enableplagiarism.png]]

==Plagiarism prevention plugins==

An administrator then needs to install and configure one or more plagiarism prevention plugins in ''Administration > Site administration > Plugins > Plagiarism prevention > Plagiarism settings''. Possible plugins include:

=== Fully supported plugins ===
These are plugins that support plagiarism detection within the Moodle Assignment, Workshop and Forum activities.
*[[Plagiarism Prevention Compilatio|Compilatio]] - Commercial tool requires paid subscription
*[[Plagiarism Prevention Turnitin|Turnitin]] - Commercial tool requires paid subscription
*[[Plagiarism Prevention URKUND|URKUND]] - Commercial tool requires paid subscription
* [https://moodle.org/plugins/plagiarism_unicheck Unicheck] - Commercial tool requires paid subscription

=== Partially supported plugins ===
These are plugins that currently only support the Moodle Assignment activity.
* [https://moodle.org/plugins/plagiarism_copycheck CopyCheck] - Commercial tool requires paid subscription
* [https://moodle.org/plugins/plagiarism_plagiarisma PLAGIARISMA] - Commercial tool requires paid subscription
* [https://moodle.org/plugins/plagiarism_plagscan PlagScan] - Commercial tool requires paid subscription
* [https://moodle.org/plugins/plagiarism_vericite Vericite] - Commercial tool requires paid subscription

== Other tools for managing plagiarism ==
*[[Acknowledge plagiarism statement access rule]] - A plugin by the Open University lets you require students to agree to a statement about not plagiarising before starting a quiz.
*[https://moodle.org/plugins/view.php?plugin=quizaccess_safeexambrowser Safe Exam Browser quiz access rule] - Provides Safe Exam Browser 2.0 integration for Moodle.
*[[Essay (auto-grade) question type]] - An additional essay question type that can use a glossary of common errors to detect plagiarized phrases.

[[Category:Site administration]]
[[de:Plagiatsuche-Plugins verwalten]]
[[es:Gestionando prevención de plagio]]

Interactive Content - H5P activity

2020-07-16T09:45:47Z

Sarjona: Migration tool reference

{{Infobox plugin
|type = Activity
|entry = https://moodle.org/plugins/mod_hvp
|tracker = https://github.com/h5p/h5p-moodle-plugin/issues
|discussion = https://h5p.org/forum
|maintainer = [[User:Frode Petterson|Frode Petterson]]
|float = right
}}

==Highlights==
* H5P gives you access to lots of different interactive content types (see [[#Activities_available_for_creation_from_inside_the_plugin| 'Activities available for creation from inside the plugin']] below).
* H5P allows you to easily share and reuse content.
** To reuse content, you just download the H5P you would like to edit and make your changes – e.g. translate to a new language or adjust it to a new situation.

==Overview==

===Supercharge your website with H5P===
* H5P makes it easy to create, share and reuse HTML5 content and applications.
* H5P empowers creatives to create rich and interactive web experiences more efficiently - all you need is a web browser and a web site with an H5P plugin.
{{Note|Moodle itself can embedd [[Media embedding|HTML5 media]].}}

===Mobile friendly content===
* Publish once, view and interact on all screens.
* H5P content is responsive and mobile friendly.
* Users experience the same rich, interactive content on computers, smartphones and tablets alike.

===Share rich content===
* H5P enables existing CMSs and LMSs (such as Moodle) to create richer content.
* With H5P, authors may create and edit interactive videos, presentations, games, advertisements and more.
* Content may be imported and exported.
** All that is needed to view or edit H5P content is a web browser.
* Rich content, applications and content components may be shared on H5P.org.

===Free to use===
* H5P is a completely free and open technology, licensed with the [https://en.wikipedia.org/wiki/MIT_License MIT license].
* Demos/downloads, tutorials and documentation is available for users who want to join the community.

==Links to examples and downloads==
* [https://h5p.org/presentation Course Presentation]
* [https://h5p.org/interactive-video Interactive Video]
* [https://h5p.org/memory-game Memory Game]
* Visit the [https://h5p.org/content-types-and-applications H5P content types and applications] page for more examples and downloads (see the download link inside the red rectangle in the following image).
[[File:H5P download an activity.png|600px]]

==Compatible Moodle versions==
Moodle 2.7 to 3.6

==Potential privacy issues==
The plugin is set up to automatically download content types and provide anonymous usage data which can be disabled through settings.

==Installation==
==== Get the plugin ====
* From the [https://moodle.org/plugins/mod_hvp Moodle plugins database]
==== Install the plugin ====
* Visit http://yoursite.com/admin to finish the installation
==== Moodle Mobile App compatibility ====

H5P contents are compatible with the Mobile App provided these 2 parameters have been set in Admin.
# Site administration > Mobile app > Mobile settings > Enable web services for mobile devices (of course!)
# Site administration > Security > HTTP security > Allow frame embedding
''Note 1.-'' The help text in this 2nd parameter displays a wrong piece of information. It reads "''Please, note also that for the mobile app this setting is ignored and frame embedding is always allowed.''" This is not true for H5P, Frame embedding '''must''' be enabled.

''Note 2.-'' If the admin has forgotten to enable this setting, in the Mobile App 2 different messages will be displayed to the end-user, according to their role (or rather their capacities).
* student role: ''This site is not configured properly for displaying mobile H5P content. Please contact a site administrator.''
* admin role: ''Iframe embedding must be enabled in order to display H5P content in the mobile app. You can enable it by checking Allow frame embedding" in Site Administration / Security / Http Security''

====Migrate activities from mod_hvp to mod_h5pactivity====

See [[H5P_activity#Migrating_activities_from_mod_hvp_to_mod_h5pactivity|Migrating activities from mod_hvp to mod_h5pactivity]] to know how to migrate existing activities (available for Moodle 3.9 onwards).

==Usage==
===Display Options===
You can enable/disable:
* Display action bar and frame
* Download button
* Copyright button

=== Uploading or Creating an activity===
[[File:H5P upload an activity.png|400px]]
* If you choose to 'Upload' an activity, you can choose a (.h5p) file or drag and drop one into the designated area.
[[File:H5P upload a previously downloaded h5p activity.png|100px]]

* You can easily create an interactive activity with the built-in editor inside the plugin.

[[File:H5P create an activity.png|400px]]
* If you choose to 'Create' an activity, the Editor drop-down list will let you choose any one of the following:

===Activities available for creation from inside the plugin===

* [https://h5p.org/accordion Accordion] - An accordion content type allowing users to add accessible [https://en.wikipedia.org/wiki/WAI-ARIA WAI - ARIA] enabled accordions. WAI - ARIA is used to increase the accessibility of web pages, in particular, dynamic content and user interface components developed with Ajax, HTML, JavaScript and related technologies.
[[File:H5P example accordion.png|400px]]
{{Note| The images pasted inside the text area will not show up in the final activity, only the text will be shown.}}

* [https://h5p.org/appear.in appear.in] for Chat and Talk - A video conference content type allowing authors to set up conference rooms.
[[File:H5P example appear_in.png|400px]]

* Audio - An easy to use audio player.
[[File:H5P example audio.png|400px]]

* [https://h5p.org/node/6729 Chart] - A chart content type allowing users to create pie charts and bar charts with H5P, to present simple statistical data graphically without creating the artwork manually.
[[File:H5P example chart.png|400px]]

* [https://h5p.org/collage Collage] - A photo collage content type allowing users to set up multiple photos in a custom layout using only a web browser in order to show off their photos in a tasteful way.
[[File:H5P example collage.png|400px]]

* [https://h5p.org/presentation Course presentation] - A presentation content type which allows users to add multiple choice, fill in the blanks, texts and other types of interactions to their presentations using only a web browser in order to make engaging presentations.
[[File:H5P example course presentation.png|400px]]

* [https://h5p.org/dialog-cards Dialog Cards] - A content type allowing authors to create great language learning resources with H5P.
[[File:H5P example dialog cards.png|400px]]

* [https://h5p.org/documentation-tool Documentation Tool] - A content type allowing authors to create guides for structured writing processes with H5P.
[[File:H5P example documentation tool.png|400px]]

* [https://h5p.org/drag-and-drop Drag and Drop] - A drag and drop question type allowing creatives to create many forms of drag and drop using only a web browser in order to make engaging challenges using H5P.
[[File:H5P example drag and drop.png|400px]]

* [https://h5p.org/drag-the-words Drag the Words] - A question type allowing creatives to create text based challenges where users are to drag words into blanks in sentences. Excellent for language training.
[[File:H5P example drag the words.png|400px]]

* [https://h5p.org/fill-in-the-blanks Fill in the Blanks] - A question type allowing creatives to create fill in the blanks, also known as [[Embedded Answers (Cloze) question type|cloze]] tests.
[[File:H5P example fill in the blanks.png|400px]]
{{Note|Moodle has two additional plugins suitable for easily making cloze questions using the Moodle [[Text editor|text editors]]: the [[Cloze editor for TinyMCE]] and the [[Cloze editor for Atto]].}}

* [https://h5p.org/image-hotspot-question Find the Hotspot] - A question type allowing creatives to create an image based test where the learner is to find the correct spot on an image. Use this content type with the H5P plugin to challenge your users.
[[File:H5P example find the hotspot.png|400px]]

* [https://h5p.org/flashcards Flashcards] - A content type allowing creatives to create flashcards. Flashcards are often used in language learning for drilling words and expressions. Flashcards can also be used to present math problems or help learners remember facts such as historical dates, formulas or names.
[[File:H5P example flashcards.png|400px]]

* Greeting Card - To easily create a greeting card.
[[File:H5P example greeting card.png|400px]]

* [https://h5p.org/node/2398 Guess the Answer] - A content type allowing creatives to create challenges where the user is to guess an answer based on a picture.
[[File:H5P example guess the answer.png|400px]]

* [https://h5p.org/iframe-embedder Iframe Embedder] - The Iframe embedder makes it easy to make an H5P of already existing JavaScript applications.
[[File:H5P example iframe embedder.png|400px]]
{{Note|Moodle itself can use [[PhET simulations]]. You can embedd them in a page or inside a question in a quiz.}}

* [https://h5p.org/image-hotspots Image Hotspots] - A content type allowing creatives to add hotspots to images. Hotspots may reveal texts, images and videos when clicked.
[[File:H5P example image hotspots.png|400px]]

* [https://h5p.org/interactive-video Interactive Video] - An interactive video content type allowing users to add multiple choice and fill in the blank questions, pop-up text and other types of interactions to their videos using only a web browser. Make your videos more engaging.
[[File:H5P example interactive video.png|400px]]

[https://h5p.org/sites/default/files/front-page-demo.mp4 Click here to link to an interactive video demo]

* [https://h5p.org/mark-the-words Mark the Words] - A question type allowing creatives to create challenges where the user is to mark specific types of verbs in a text.
[[File:H5P example mark the words.png|400px]]

* [https://h5p.org/memory-game Memory Game] - A memory game content type allowing authors to add their own images (and optional text) to a memory game. To play the game, users search for image pairs, which will display a specified text message once a matching pair has been found.
[[File:H5P memory game 001.png|400px]]

* [https://h5p.org/multichoice Multiple Choice] - A question type allowing creatives to create challenges where the user is to identify one ore more correct choices.
[[File:H5P example multiple choice.png|400px]]

* [https://h5p.org/question-set Question Set] - A content type allowing creatives to create quizzes. Many question types are supported like multiple choice, fill in the blanks, drag the words, mark the words and regular drag and drop.
[[File:H5P example question set..png|400px]]

* [https://h5p.org/single-choice-set Single Choice Set] - A content type allowing creatives to create simple and smoot quizzes consisting of single choice questions.
[[File:H5P example single choice set..png|400px]]

* [https://h5p.org/summary Summary] - A summary builder. This content type allows creatives to create challenges where the user is to choose between statements and build the correct summary.
[[File:H5P example summary..png|400px]]

* [https://h5p.org/timeline Timeline] - A content type allowing creatives to create interactive timelines.
[[File:H5P example timeline..png|400px]]

* [https://h5p.org/twitter-user-feed Twitter User feed] - A Twitter feed.
[[File:H5P example twitter user feed..png|400px]]

== See also==
* [https://h5p.org/ H5P] homepage
* [https://h5p.org/forum forum] for discussing H5P
* [https://github.com/h5p/h5p-moodle-plugin source code] repository
* [https://docs.moodle.org/dev/H5P H5P Moodle Dev documentation]

[[Category:Audio]]
[[Category:Video]]
[[Category:Language teaching]]
[[Category:Mathematics]]

[[es:Actividad Contenido Interactivo - H5P]]
[[fr:H5P]]

H5P activity

2020-07-16T09:36:23Z

Sarjona: Added some clarifications.

{{Activities}}{{New features}}
The H5P activity enables H5P content created in the [[Content bank]] or on h5p.com to be easily added to a course.

==Adding an H5P activity==

# With the editing turned on in a course, click 'Add an activity or resource' and then select H5P.
# Add the title and other information and either:
#*upload a new activity (file extension .h5p) from the file picker or
#* locate and upload an existing .h5p file from the file picker > content bank or
#* click the link "Use the content bank (opens in a new window) to manage your H5P files" and, from the new window, create a new H5P activity, save it, return to the H5P activity settings and upload the file from the content bank.
# Remember that if you add the content as an alias, any content edition will update this instance; but if you add it as a copy changes won't be applied, See [[Working with files]] for more details

==Capabilities==

There are 4 capabilities relating to the H5P activity:

* [[Capabilities/mod/h5pactivity:addinstance|Add a new H5P]] activity to the course
* [[Capabilities/mod/h5pactivity:reviewattempts|Review H5P attempts]]
* [[Capabilities/mod/h5pactivity:submit|Submit H5P attempts]]
* [[Capabilities/mod/h5pactivity:view|View H5P]]

==Migrating activities from mod_hvp to mod_h5pactivity==

The [[Interactive_Content_-_H5P_activity|mod_hvp plugin]] is a third-party plugin created and maintained by Joubel.
Since 3.9, a new H5P activity has been developed and included in Moodle LMS core: mod_h5pactivity

For migrating content from mod_hvp to mod_h5pactivity, a migration tool has been created. It can be downloaded and installed from https://moodle.org/plugins/tool_migratehvp2h5p.
This tool will allow admins to choose the mod_hvp activities to migrate to mod_h5pactivity and what to do with the original activity once migrated (hide it, delete it or leave as it is). When using it, a new mod_h5pactivity will be created and the student results will be copied too.

There are some limitations to consider before using the migration tool to copy activities from mod_hvp to mod_h5pactivity:

# Currently it's still not possible to save the current status with the mod_h5pactivity. The mod_hvp supports it (although it's disabled by default) so, before migrating the activities, consider students might loose these unfinished attempts.
# The new mod_h5pactivity hasn't any global settings to define the default behaviour so general settings defined in mod_hvp, such as the default display options or whether to use or not the hub, are not migrated.
# The new mod_h5pactivity doesn't support (at least for now), H5P styles (hvp_alter_styles): MDL-69087

[[File:migrationtool_hvp2h5p.png|Migration tool]]

==See also==

* [[H5P]] for more information on H5P in Moodle

[[Category: H5P]]

[[es:Actividad H5P]]

H5P activity

2020-07-16T09:33:16Z

Sarjona: What to do with mod_hvp activities when migrating them

{{Activities}}{{New features}}
The H5P activity enables H5P content created in the [[Content bank]] or on h5p.com to be easily added to a course.

==Adding an H5P activity==

# With the editing turned on in a course, click 'Add an activity or resource' and then select H5P.
# Add the title and other information and either:
#*upload a new activity (file extension .h5p) from the file picker or
#* locate and upload an existing .h5p file from the file picker > content bank or
#* click the link "Use the content bank (opens in a new window) to manage your H5P files" and, from the new window, create a new H5P activity, save it, return to the H5P activity settings and upload the file from the content bank.
# Remember that if you add the content as an alias, any content edition will update this instance; but if you add it as a copy changes won't be applied, See [[Working with files]] for more details

==Capabilities==

There are 4 capabilities relating to the H5P activity:

* [[Capabilities/mod/h5pactivity:addinstance|Add a new H5P]] activity to the course
* [[Capabilities/mod/h5pactivity:reviewattempts|Review H5P attempts]]
* [[Capabilities/mod/h5pactivity:submit|Submit H5P attempts]]
* [[Capabilities/mod/h5pactivity:view|View H5P]]

==Migrating activities from mod_hvp to mod_h5pactivity==

The [[Interactive_Content_-_H5P_activity|mod_hvp plugin]] is a third-party plugin created and maintained by Joubel.
Since 3.9, a new H5P activity has been developed and included in Moodle LMS core.

For migrating content from mod_hvp to mod_h5pactivity, a migration tool has been created. It can be downloaded and installed from https://moodle.org/plugins/tool_migratehvp2h5p.
This tool will allow admins to choose the mod_hvp activities to migrate to mod_h5pactivity and what to do with the original activity once migrated (hide it, delete it or leave as it is). When using it, a new mod_h5pactivity will be created and the student results will be copied too.

There are some limitations to consider before using the migration tool to copy activities from mod_hvp to mod_h5pactivity:

# Currently it's still not possible to save the current status with the mod_h5pactivity. The mod_hvp supports it (although it's disabled by default) so, before migrating the activities, consider students might loose these unfinished attempts.
# The new mod_h5pactivity hasn't any global settings to define the default behaviour so general settings defined in mod_hvp, such as the default display options or whether to use or not the hub, are not migrated.
# The new mod_h5pactivity doesn't support (at least for now), H5P styles (hvp_alter_styles): MDL-69087

[[File:migrationtool_hvp2h5p.png|Migration tool]]

==See also==

* [[H5P]] for more information on H5P in Moodle

[[Category: H5P]]

[[es:Actividad H5P]]

H5P activity

2020-07-16T09:31:34Z

Sarjona: Added migration image

{{Activities}}{{New features}}
The H5P activity enables H5P content created in the [[Content bank]] or on h5p.com to be easily added to a course.

==Adding an H5P activity==

# With the editing turned on in a course, click 'Add an activity or resource' and then select H5P.
# Add the title and other information and either:
#*upload a new activity (file extension .h5p) from the file picker or
#* locate and upload an existing .h5p file from the file picker > content bank or
#* click the link "Use the content bank (opens in a new window) to manage your H5P files" and, from the new window, create a new H5P activity, save it, return to the H5P activity settings and upload the file from the content bank.
# Remember that if you add the content as an alias, any content edition will update this instance; but if you add it as a copy changes won't be applied, See [[Working with files]] for more details

==Capabilities==

There are 4 capabilities relating to the H5P activity:

* [[Capabilities/mod/h5pactivity:addinstance|Add a new H5P]] activity to the course
* [[Capabilities/mod/h5pactivity:reviewattempts|Review H5P attempts]]
* [[Capabilities/mod/h5pactivity:submit|Submit H5P attempts]]
* [[Capabilities/mod/h5pactivity:view|View H5P]]

==Migrating activities from mod_hvp to mod_h5pactivity==

The [[Interactive_Content_-_H5P_activity|mod_hvp plugin]] is a third-party plugin created and maintained by Joubel.
Since 3.9, a new H5P activity has been developed and included in Moodle LMS core.

For migrating content from mod_hvp to mod_h5pactivity, a migration tool has been created. It can be downloaded and installed from https://moodle.org/plugins/tool_migratehvp2h5p.
This tool will allow admins to choose the mod_hvp activities to migrate to mod_h5pactivity and what to do with the original activity once migrated. When using it, a new mod_h5pactivity will be created and the student results will be copied too.

There are some limitations to consider before using the migration tool to copy activities from mod_hvp to mod_h5pactivity:

# Currently it's still not possible to save the current status with the mod_h5pactivity. The mod_hvp supports it (although it's disabled by default) so, before migrating the activities, consider students might loose these unfinished attempts.
# The new mod_h5pactivity hasn't any global settings to define the default behaviour so general settings defined in mod_hvp, such as the default display options or whether to use or not the hub, are not migrated.
# The new mod_h5pactivity doesn't support (at least for now), H5P styles (hvp_alter_styles): MDL-69087

[[File:migrationtool_hvp2h5p.png|Migration tool]]

==See also==

* [[H5P]] for more information on H5P in Moodle

[[Category: H5P]]

[[es:Actividad H5P]]

File:migrationtool hvp2h5p.png

2020-07-16T09:29:35Z

Sarjona:

H5P activity

2020-07-16T09:24:16Z

Sarjona: Migration tool

{{Activities}}{{New features}}
The H5P activity enables H5P content created in the [[Content bank]] or on h5p.com to be easily added to a course.

==Adding an H5P activity==

# With the editing turned on in a course, click 'Add an activity or resource' and then select H5P.
# Add the title and other information and either:
#*upload a new activity (file extension .h5p) from the file picker or
#* locate and upload an existing .h5p file from the file picker > content bank or
#* click the link "Use the content bank (opens in a new window) to manage your H5P files" and, from the new window, create a new H5P activity, save it, return to the H5P activity settings and upload the file from the content bank.
# Remember that if you add the content as an alias, any content edition will update this instance; but if you add it as a copy changes won't be applied, See [[Working with files]] for more details

==Capabilities==

There are 4 capabilities relating to the H5P activity:

* [[Capabilities/mod/h5pactivity:addinstance|Add a new H5P]] activity to the course
* [[Capabilities/mod/h5pactivity:reviewattempts|Review H5P attempts]]
* [[Capabilities/mod/h5pactivity:submit|Submit H5P attempts]]
* [[Capabilities/mod/h5pactivity:view|View H5P]]

==Migrating activities from mod_hvp to mod_h5pactivity==

The [[Interactive_Content_-_H5P_activity|mod_hvp plugin]] is a third-party plugin created and maintained by Joubel.
Since 3.9, a new H5P activity has been developed and included in Moodle LMS core.

For migrating content from mod_hvp to mod_h5pactivity, a migration tool has been created. It can be downloaded and installed from https://moodle.org/plugins/tool_migratehvp2h5p.
This tool will allow admins to choose the mod_hvp activities to migrate to mod_h5pactivity and what to do with the original activity once migrated. When using it, a new mod_h5pactivity will be created and the student results will be copied too.

There are some limitations to consider before using the migration tool to copy activities from mod_hvp to mod_h5pactivity:

# Currently it's still not possible to save the current status with the mod_h5pactivity. The mod_hvp supports it (although it's disabled by default) so, before migrating the activities, consider students might loose these unfinished attempts.
# The new mod_h5pactivity hasn't any global settings to define the default behaviour so general settings defined in mod_hvp, such as the default display options or whether to use or not the hub, are not migrated.
# The new mod_h5pactivity doesn't support (at least for now), H5P styles (hvp_alter_styles): MDL-69087

==See also==

* [[H5P]] for more information on H5P in Moodle

[[Category: H5P]]

[[es:Actividad H5P]]

Participants

2019-02-13T07:32:01Z

Sarjona: How to search and use wildcards

{{Course enrolment}}
==About==
The Participants page enables teachers to easily enrol, view, search for, filter, edit and delete course participants.

The Participants page can be accessed from the navigation drawer in the [[Boost theme]] or the Administration block in other themes. It can also be accessed from the More link in the gear menu, by clicking Enrolled users in the Users tab.

{{MediaPlayer | url = https://youtu.be/jj_ynDPpHBk | desc = 3.4 Participants and Enrolments Page}}

==Enrolling users==
Users may be enrolled from the Enrol users button at the top right and bottom right of the screen.

[[File:NewEnrolUsers.png]]

==Filtering and searching for users==
The filter at the top left of the screen allows for filtering by period of activity, enrolment method, group, role and status:

[[File:ParticipantsFilter.png]]

You can also search users by any of the fields defined in the "Show user identity" setting. Some of the searchable fields, like username, first name and last name, use a "like" search, to let find all the users containing the written string. There are two wildcars:
* % The percent sign represents zero, one, or multiple characters
* _ The underscore represents a single character (Note: MS Access uses a question mark '?' instead of the underscore '_').

These wildcards can be escaped, if needed, to search users containing them, using the '\':
* A_B will find all the users starting with an A, followed by any character and then B (i.e. AxB or A2B, but not AxxB).
* A\_B will find users starting exactly with 'A_B'.

It is possible to bulk select, edit and delete users who have self enrolled, in a similar way to users who have been enrolled manually.

==Roles==
*To assign an enrolled user a role, click the pencil icon in the Roles column then select the desired role and click the save icon to confirm the change.
*To remove a role assignment, click the delete icon (a cross) next to the role name.
*Only roles which can be assigned in the course context type are available to select. The course context type may be set by an admin by editing the role via Site administration > Users > Permissions > Define roles.
*Only roles which a user is allowed to assign are available to select.

==Groups==
To add a user to a group (requires at least one group to have been created previously), click the pencil icon in the Groups column, select the group and then click the save icon to confirm the change.

[[File:NewGroupSelect.png]]

==Status==
The status column shows the current status of a user's enrolments, for example Active or Suspended. Where a user has two different enrolment types (eg manual/cohort sync) both are displayed in the status column:

[[File:Statuscolumn.png]]

==City/town or country==

Users' city/town or country may be displayed for users with the capability moodle/site:viewuseridentity (by default manager, teacher and non-editing teacher) by selecting these fields in 'Show user identity' in [[User policies]] in the Site administration.

==Sending a message, adding a note, or editing manual user enrolments==

You can send a message, add a note, or edit or delete selected manual user enrolments via the dropdown menu below the list of course participants.

Note that only users who were previously ''manually'' enrolled can have their enrolment edited or deleted in bulk. The enrolment for users who enrolled using a different enrolment method, such as self enrolment, may be edited or deleted via the edit enrolment link (cog icon) in the status column.

[[File:BulkEditDeleteUsers.png]]

[[es:Participantes]]
[[de:Teilnehmer/innen]]
[[it:Partecipanti]]

Upgrading

2018-12-17T09:41:16Z

Sarjona: Add reference to $CFG->keepmessagingallusersenabled = true;

{{Installing Moodle}}
''This page explains in detail how to upgrade Moodle. For a summary of the process, see [[Upgrade overview]].''

==Check the requirements==

Before upgrading, check that your server meets all requirements for {{Version}} in ''Site administration > Server > [[Environment]]''.

See the [{{Release notes}} release notes] in the dev docs for both [{{Release notes}}#Server_requirements server] and [{{Release notes}}#Client_requirements client] software requirements.

Notes:

* You can only upgrade to Moodle {{Version}} from Moodle 3.1 or later. If upgrading from earlier versions, you must [https://docs.moodle.org/31/en/Upgrading_to_Moodle_3.1 upgrade to 3.1] as a first step.

==Before upgrading==

'''We advise that you test the upgrade first on a COPY of your production site, to make sure it works as you expect.'''

Consider setting the [[Upgrade key|upgrade key]] for your site.

== Backup important data ==

There are three areas that should be backed up before any upgrade:
#Moodle software (For example, everything in server/htdocs/moodle)
#Moodle uploaded files (For example, server/moodledata)
#Moodle database (For example, your Postgres or MySQL database dump)

See [[Site backup]] for more specific information.

== Check for plugin updates ==

If you have [[Automatic updates deployment]] enabled, you will be able to update installed plugins automatically during the upgrade. Just make sure you check for available updates (via the button for it) at the Plugins check screen.

If you are updating plugins manually, it is a good moment now to check in the [http://moodle.org/plugins Moodle Plugins directory] whether there is a {{Version}} version available for any plugins (including themes) that you have previously installed on your site. If so, download the plugin package. In the next step, you will copy it to the appropriate location in your Moodle code (see [[Installing plugins]]).

The upgrade of the plugin will then happen as part of the Moodle upgrade process.

If an out-of-date plugin causes your upgrade to fail, you can usually delete the plugin code rather than uninstalling it from within Moodle so that the data associated with it is not deleted.

==Put your site into maintenance mode==
Before you begin upgrading your site, you should put it into [[Maintenance_mode | maintenance mode]] to stop any non-admin users from logging in. Then you should wait for any currently running cron processes to complete before proceeding.

== Install the new Moodle software ==
You can fetch the current version of the software through

wget http://sourceforge.net/projects/moodle/files/Moodle/stable{{Version2}}/moodle-latest-{{Version2}}.tgz

=== Standard install package ===

# Move your old Moodle software program files to another location. ''Do NOT copy new files over the old files.''
# Unzip or unpack the upgrade file so that all the new Moodle software program files are in the location the old files used to be in on the server. Moodle will adjust SQL and moodledata if it needs to in the upgrade.
# Copy your old [[Configuration file|config.php file]] back to the new Moodle directory.
# As mentioned above, if you had installed any plugins on your site you should add them to the new code tree (Moodle directory structure) now. It is important to check that you get the correct version for your new version of Moodle. Be particularly careful that you do not overwrite any code in the new version of Moodle and that you place the plugin folders in the correct directory (the same directory that they are in in the current installation.)
# Your moodledata folder should be located separately to your Moodle code folder and, as such, should not need anything done to it. Moodle 3.0 will throw a warning if it is located in a web accessible folder and the moodledata should never be located in the Moodle code folder. If you are moving your installation to a new server or new location on your server, then you will need to follow the Migration documents.

====Linux====
mv moodle moodle.backup
tar xvzf moodle-{{Version}}.tgz

Next, copy across your config.php, any custom plugins, and your .htaccess file if you created one ('''check that custom plugins are the correct version for your new Moodle first'''):

cp moodle.backup/config.php moodle
cp -pr moodle.backup/theme/mytheme moodle/theme/mytheme
cp -pr moodle.backup/mod/mymod moodle/mod/mymod

Don't forget to make moodle/config.php (and the rest of the source code) readable by your www server. For maximum security the files should not be writeable by your server. This is especially important on a 'production' server open to the public internet.

chown -R root:root moodle (Linux debian - or even create a user especially for moodle. '''Don't''' use the web server user, e.g. www-data)
chmod -R 755 moodle

If you use cron, take care that cron.php is executeable and uses the correct php command:
chmod 740 admin/cli/cron.php (some configurations need chmod 750 or chmod 755)
copy the first line from cron.php (if it looks like '#!/usr/local/bin/php' or '#!/usr/local/bin/php5.3', no need to copy '<?php')
if necessary. However, for a simple upgrade, there should be no need to change anything with cron.

=== Using Git ===

You can use Git for updating or upgrading your Moodle. See [[Git for Administrators]] for details.

===Command line upgrade===

On Linux servers, Moodle {{Version}} supports running the [[CLI|upgrade from the command line]], rather than through a web browser. This is likely to be more reliable, particularly for large sites.

== Finishing the upgrade ==

The last step is to trigger the upgrade processes within Moodle.

If you put your site into Maintenance mode earlier; take it out now!

To do this just go to ''Administration > Site administration > Notifications''.

Moodle will automatically detect the new version and perform all the SQL database or file system upgrades that are necessary. If there is anything it can't do itself (very rare) then you will see messages telling you what you need to do.

Assuming all goes well (no error messages) then you can start using your new version of Moodle and enjoy the new features!

Note: If you are running multiple servers then you should purge all caches manually (via ''Administration > Site administration > Development > Purge all caches'') after completing the upgrade on all servers.

===Fatal error: Maximum execution time of 30 seconds exceeded...===

If your server uses a main language other than English, you may encounter a 'Fatal error: Maximum execution time of 30 seconds exceeded' when you try to upgrade it. You can increase max_execution_time = 160 on php.ini to allow the scripts enough time to process the language update. Otherwise, you can switch to English as the default language before doing the upgrade and back to your original language after a succcessful upgrade. See the forum discussion at https://moodle.org/mod/forum/discuss.php?d=119598.

==After upgrading==

The config.php file from your installation should work fine but if you take a look at config-dist.php that came with Moodle 3.0 there are more/different options available (e.g. database drivers and settings). It's a good idea to map your old config.php settings to a new one based on the 3.0 config-dist.php.

===Cron===

Cron has received a major update (MDL-25499) and now has support for both scheduled and ad hoc tasks.

The benefits of these changes are:
* The schedule for every task can be configured by the admin
* Tasks can run in parallel
* Cron processes use locking to prevent the same task running at the same time by different processes
* Clusters with multiple identical application nodes are supported, you can run cron on all of them

A result of this is that cron can be run much more often, which means (for example) forum posts can be sent out sooner. To take advantage of the new cron system it is now strongly recommended that administrators increase the frequency that cron is run to at least ''once per minute''.

You also may need to modify any automated scripts you have that are parsing the output from cron. It is no longer possible to simply monitor the output of cron for the string "Cron script completed correctly" (if that is what you were doing). An alternative is to monitor the output for the string "task failed:". If you detect that a task is failing, [[Cron#Debugging_Scheduled_Tasks|here]] are some tips for debugging the failure.

Before the upgrade, there may have been a cron task that was failing, which was preventing the rest of cron from being executed. A failure in any single task will no longer prevent the rest of the Moodle cron tasks from executing, so you may uncover previously masked bugs. It is a good idea to closely monitor the output from cron after the upgrade.

===Assignments===

The old assignment (2.2) module has been removed from core and has been replaced by a stub to support transparently remapping URLs and restoring course backups from the old module to the new one.

If you are still using the old assignment (2.2) module, after upgrading to Moodle 3.0 all assignment (2.2) activities will be hidden. You need to run the [[Assignment upgrade tool]] to un-hide the activities.

If you really, really need to keep using the old assignment (2.2) module, you should update the code to Moodle 3.0, and then replace the "mod/assignment" folder with the one from https://github.com/moodlehq/moodle-mod_assignment/releases before completing the upgrade.

==Possible issues that may affect you in Moodle {{Version}}==

* For sites using a custom theme you will need to add a renderer callback to "standard_after_main_region_html" see [[:dev:Upgrading themes to Moodle 3.6|Upgrading themes to Moodle 3.6]]
* Sites using a custom theme or login form must include a new login token field in the login form. See the dev docs [[:dev:Login token|Login token]] for details.
* To use 'Run now' links in [[Scheduled tasks]], you will need to set 'Path to PHP CLI' (pathtophp) in Site administration / Server / System paths.
* Adding another user as a messaging contact now requires approval from the other user. Any contacts that you have that aren't mutual (ie. both users have added each other as a contact) will be removed from your list of contacts.
* New setting 'Allow site-wide messaging' in Site administration / Advanced features. The setting is disabled by default (for new installs) but enabled for upgraded sites if ''$CFG->keepmessagingallusersenabled = true;'' is defined in config.php.
* The timeline tab in the course overview block is now in a separate block [[Timeline block|Timeline]]. There are also more new Dashboard blocks - [[Recently accessed courses block|Recently accessed courses]], [[Recently accessed items block|Recently accessed items]] and [[Starred courses block|Starred courses]].
*The [[Assignment upgrade tool]], for upgrading old assignments from 2.2 or earlier, has been removed from core.

''Please add more items...''

See also the list of [https://tracker.moodle.org/issues/?jql=project%20%3D%20mdl%20AND%20resolution%20%3D%20fixed%20AND%20fixVersion%20in%20(%223.6%22)%20AND%20labels%20%3D%20upgrade_notes upgrade_notes-labelled issues] and [https://tracker.moodle.org/issues/?jql=project%20%3D%20mdl%20AND%20resolution%20%3D%20fixed%20AND%20fixVersion%20in%20(%223.6%22)%20AND%20labels%20%3D%20ui_change%20 ui_change-labelled issues].

=== Moodle 3.1, 3.2, 3.3, 3.4 and 3.5 improvements ===

Depending on which version you are upgrading from, please see the section 'Possible issues that may affect you' in the documentation

* [https://docs.moodle.org/31/en/Upgrading Upgrading to Moodle 3.1]
* [https://docs.moodle.org/32/en/Upgrading Upgrading to Moodle 3.2]
* [https://docs.moodle.org/33/en/Upgrading Upgrading to Moodle 3.3]
* [https://docs.moodle.org/34/en/Upgrading Upgrading to Moodle 3.4]
* [https://docs.moodle.org/35/en/Upgrading Upgrading to Moodle 3.5]

==See also==

* [[Installation]]
* Using Moodle [http://moodle.org/mod/forum/view.php?id=28 Installation help forum]
* [[dev:Moodle {{Version}} release notes|Moodle {{Version}} release notes]]

[[es:Actualización de moodle]]
[[fr:Mise à jour]]
[[ja:Moodleをアップグレードする]]
[[de:Aktualisierung von Moodle]]

Policies

2018-06-15T09:24:07Z

Sarjona: /* Adding and managing policies */

{{GDPR}}{{New features}}
The Policies plugin provides a new user sign-on process, with ability to define multiple policies (site, privacy, third party), track user consents, and manage updates and versioning of the policies.

The Policies plugin forms part of Moodle’s privacy feature set assisting sites to become GDPR compliant. It is included as standard in Moodle 3.5 onwards and available as a separately [https://moodle.org/plugins/tool_policy downloadable plugin] for Moodle 3.3.6 and 3.4.3.

==Enabling the policies plugin==

To enable the policies plugin

# Go to 'Policy settings' in the Site administration.
# Set the Site policy handler to 'Policies (tool_policy)'.
# Save changes.

Two new pages will then appear in the Site administration - 'Manage policies' and 'User agreements'.

Note that when Policies is set as the site policy handler, the settings 'Site policy' and 'Site policy for guests' are ignored.

==Adding and managing policies==
[[File:policies and agreements.png|thumb|Policies and agreements]]
An admin or any user with the [[Capabilities/tool/policy:managedocs|Manage policies]] capability (by default manager) can access the page 'Manage policies' in the Site administration and:

* Add a new site / privacy / third parties / other policy for all users, authenticated users or guests
* Change the active / inactive status of each policy
* View the number and percentage of users who have agreed to each policy
* Edit a policy and specify whether it is a minor change (not requiring users to reconfirm their consent) or not
* View the current version of each policy and also previous versions
* Change the order in which policies are shown to users

To add a new policy:

# Go to 'Manage policies' in the Site administration.
# Click the button 'New policy'
# Complete the form and save changes.

Note that once created, a policy can be edited, or set to inactive, but if users have agreed to it, it can't be deleted.

The policy type (site / privacy / third parties) is only displayed at the 'Policies' page linked on the footer and the behaviour is the same for all the policy types.

==Giving consent to policies==
[[File:Agreeing to policies.png|thumb|Giving consent to policies]]
All users (with the exception of admins) will be required to give their consent to all policies defined either for “Authenticated users” or for “All users” before proceeding further on the site.

If a new policy is added, all users will be required to give their consent when they next log in. Similarly, if an existing policy is edited and is not marked as a minor change, all users will be required to give their consent when they next log in.

If self-registration is enabled on the site, new users will be required to give their consent to all policies before proceeding to the sign-up form. If digital age of consent verification (a new setting in Moodle 3.4.2 onwards) is enabled in '[[Privacy|Privacy settings]]' in the Site administration, when a new user clicks the 'Create new account' button, they will be prompted to enter their age and country. If the user's age is lower than the age of consent for their country, they will see a message prompting them to ask their parent/guardian to contact the support contact (as specified in 'Support contact' in the Site administration).

==Policies for guests==
[[File:policies modal window.png|thumb|Policies for guests modal window]]
If a user logs in as a [[Guest access|guest]], a modal window will be shown at the bottom of the user's browser window with links to all policies defined either for guests or for all users.

==Minors==
[[File:No permission to agree to policies.png|thumb|Minor prevented from proceeding further on the site]]
Users who are younger than the age of digital consent, called 'minors', may be prevented from giving their consent by prohibiting the capability [[Capabilities/tool/policy:accept|Agree to policies]]. They will then be prevented from proceeding further on the site until someone can give consent on their behalf.

===Sites with minors as the majority of users===

To prohibit users from agreeing to policies because they are a minor:

# Go to 'Define roles' in the Site administration.
# Edit the role of authenticated user and set [[Capabilities/tool/policy:accept|Agree to policies]] to prohibit.
# Save changes.

To enable teachers and other users who are not minors to agree to policies:

# Go to 'Define roles' in the Site administration.
# Click the button 'Add a new role'.
# Give the role a name such as 'Able to give consent', short name and description.
# For context types where this role may be assigned, tick system.
# Enter policy in the filter box, then allow the capability Agree to policies.
# Click the button 'Create this role'.
# Go to 'Assign system roles' in the Site administration.
# Choose the 'Able to give consent' role to assign.
# Select teachers and other users in the Potential users list, and use the left-facing arrow button to add them to the Existing users list.

===Sites with only a few minors===

To prohibit users from agreeing to policies because they are a minor:

# Go to 'Define roles' in the Site administration.
# Click the button 'Add a new role'.
# Give the role a name such as 'Digital minor', short name and description.
# For context types where this role may be assigned, tick system.
# Enter policy in the filter box, then prohibit the capability Agree to policies.
# Click the button 'Create this role'.
# Go to 'Assign system roles' in the Site administration.
# Choose the 'Digital minor' role to assign.
# Select minors in the Potential users list, and use the left-facing arrow button to add them to the Existing users list.

==User agreements==
[[File:user agreements.png|thumb|User agreements filtered to show minors]]
An admin or any user with the [[Capabilities/tool/policy:viewacceptances|View user agreements reports]] capability (by default manager) can access the page 'User agreements' in the Site administration and:

* View user consents
* Filter by policy, permission, status or role
* Give consent on behalf of minors
* Download table data

User agreements for a particular policy may also be viewed via the 'Manage policies' page by clicking the link in the Agreements column.

==Giving consent on behalf of other users==

An admin or any user with the capability [[Capabilities/tool/policy:acceptbehalf|Agree to the policies on someone else's behalf]] can give consent on behalf of minors or when a written consent was obtained offline.

===Giving consent on behalf of multiple users===
[[File:Record of consents.png|thumb|Record of consents with remarks]]
Users with capability [[Capabilities/tool/policy:acceptbehalf|Agree to the policies on someone else's behalf]] in the system context, such as managers, can give consent on behalf of multiple users as follows:

# Go to 'User agreements' in the Site administration.
# If necessary, filter by 'Permission: Can not agree'.
# To give consent for multiple policies, tick the box next to selected users' names then click the consent button.
# To give consent for a single policy, click the red cross next to the user's name.

When giving consent on behalf of other users, there is an opportunity to add some remarks. Clicking on the link in the Overall column gives an overview with details of who gave consent and when, together with any remarks.

===Giving consent on behalf of a child===

A parent or guardian may be allowed to give consent on behalf of their child by giving them the capability [[Capabilities/tool/policy:acceptbehalf|Agree to the policies on someone else's behalf]] in the user context. See the [[Parent role]] for details of how to create the role and assign a parent to a student. The parent or guardian will then be able to give consent as follows:

# Go to the child's profile page.
# Click the link 'Policies and agreements'.
# Click the red cross next to the policy name.

==Capabilities==

* [[Capabilities/tool/policy:accept|Agree to policies]] - allowed for authenticated user role
* [[Capabilities/tool/policy:managedocs|Manage policies]] - allowed for default role of manager only
* [[Capabilities/tool/policy:viewacceptances|View user agreements reports]] - allowed for default role of manager only
* [[Capabilities/tool/policy:acceptbehalf|Agree to policies on someone else's behalf]] - allowed for default role of manager only

[[Category:Privacy]]

[[es:Plugin de políticas]]
[[de:Richtlinien und Einwilligungen]]

Policies

2018-06-15T09:23:28Z

Sarjona: Policy types

{{GDPR}}{{New features}}
The Policies plugin provides a new user sign-on process, with ability to define multiple policies (site, privacy, third party), track user consents, and manage updates and versioning of the policies.

The Policies plugin forms part of Moodle’s privacy feature set assisting sites to become GDPR compliant. It is included as standard in Moodle 3.5 onwards and available as a separately [https://moodle.org/plugins/tool_policy downloadable plugin] for Moodle 3.3.6 and 3.4.3.

==Enabling the policies plugin==

To enable the policies plugin

# Go to 'Policy settings' in the Site administration.
# Set the Site policy handler to 'Policies (tool_policy)'.
# Save changes.

Two new pages will then appear in the Site administration - 'Manage policies' and 'User agreements'.

Note that when Policies is set as the site policy handler, the settings 'Site policy' and 'Site policy for guests' are ignored.

==Adding and managing policies==
[[File:policies and agreements.png|thumb|Policies and agreements]]
An admin or any user with the [[Capabilities/tool/policy:managedocs|Manage policies]] capability (by default manager) can access the page 'Manage policies' in the Site administration and:

* Add a new site / privacy / third parties / other policy for all users, authenticated users or guests
* Change the active / inactive status of each policy
* View the number and percentage of users who have agreed to each policy
* Edit a policy and specify whether it is a minor change (not requiring users to reconfirm their consent) or not
* View the current version of each policy and also previous versions
* Change the order in which policies are shown to users

To add a new policy:

# Go to 'Manage policies' in the Site administration.
# Click the button 'New policy'
# Complete the form and save changes.

Note that once created, a policy can be edited, or set to inactive, but if users have agreed to it, it can't be deleted.
The policy type (site / privacy / third parties) is only displayed at the 'Policies' page linked on the footer and the behaviour is the same for all the policy types.

==Giving consent to policies==
[[File:Agreeing to policies.png|thumb|Giving consent to policies]]
All users (with the exception of admins) will be required to give their consent to all policies defined either for “Authenticated users” or for “All users” before proceeding further on the site.

If a new policy is added, all users will be required to give their consent when they next log in. Similarly, if an existing policy is edited and is not marked as a minor change, all users will be required to give their consent when they next log in.

If self-registration is enabled on the site, new users will be required to give their consent to all policies before proceeding to the sign-up form. If digital age of consent verification (a new setting in Moodle 3.4.2 onwards) is enabled in '[[Privacy|Privacy settings]]' in the Site administration, when a new user clicks the 'Create new account' button, they will be prompted to enter their age and country. If the user's age is lower than the age of consent for their country, they will see a message prompting them to ask their parent/guardian to contact the support contact (as specified in 'Support contact' in the Site administration).

==Policies for guests==
[[File:policies modal window.png|thumb|Policies for guests modal window]]
If a user logs in as a [[Guest access|guest]], a modal window will be shown at the bottom of the user's browser window with links to all policies defined either for guests or for all users.

==Minors==
[[File:No permission to agree to policies.png|thumb|Minor prevented from proceeding further on the site]]
Users who are younger than the age of digital consent, called 'minors', may be prevented from giving their consent by prohibiting the capability [[Capabilities/tool/policy:accept|Agree to policies]]. They will then be prevented from proceeding further on the site until someone can give consent on their behalf.

===Sites with minors as the majority of users===

To prohibit users from agreeing to policies because they are a minor:

# Go to 'Define roles' in the Site administration.
# Edit the role of authenticated user and set [[Capabilities/tool/policy:accept|Agree to policies]] to prohibit.
# Save changes.

To enable teachers and other users who are not minors to agree to policies:

# Go to 'Define roles' in the Site administration.
# Click the button 'Add a new role'.
# Give the role a name such as 'Able to give consent', short name and description.
# For context types where this role may be assigned, tick system.
# Enter policy in the filter box, then allow the capability Agree to policies.
# Click the button 'Create this role'.
# Go to 'Assign system roles' in the Site administration.
# Choose the 'Able to give consent' role to assign.
# Select teachers and other users in the Potential users list, and use the left-facing arrow button to add them to the Existing users list.

===Sites with only a few minors===

To prohibit users from agreeing to policies because they are a minor:

# Go to 'Define roles' in the Site administration.
# Click the button 'Add a new role'.
# Give the role a name such as 'Digital minor', short name and description.
# For context types where this role may be assigned, tick system.
# Enter policy in the filter box, then prohibit the capability Agree to policies.
# Click the button 'Create this role'.
# Go to 'Assign system roles' in the Site administration.
# Choose the 'Digital minor' role to assign.
# Select minors in the Potential users list, and use the left-facing arrow button to add them to the Existing users list.

==User agreements==
[[File:user agreements.png|thumb|User agreements filtered to show minors]]
An admin or any user with the [[Capabilities/tool/policy:viewacceptances|View user agreements reports]] capability (by default manager) can access the page 'User agreements' in the Site administration and:

* View user consents
* Filter by policy, permission, status or role
* Give consent on behalf of minors
* Download table data

User agreements for a particular policy may also be viewed via the 'Manage policies' page by clicking the link in the Agreements column.

==Giving consent on behalf of other users==

An admin or any user with the capability [[Capabilities/tool/policy:acceptbehalf|Agree to the policies on someone else's behalf]] can give consent on behalf of minors or when a written consent was obtained offline.

===Giving consent on behalf of multiple users===
[[File:Record of consents.png|thumb|Record of consents with remarks]]
Users with capability [[Capabilities/tool/policy:acceptbehalf|Agree to the policies on someone else's behalf]] in the system context, such as managers, can give consent on behalf of multiple users as follows:

# Go to 'User agreements' in the Site administration.
# If necessary, filter by 'Permission: Can not agree'.
# To give consent for multiple policies, tick the box next to selected users' names then click the consent button.
# To give consent for a single policy, click the red cross next to the user's name.

When giving consent on behalf of other users, there is an opportunity to add some remarks. Clicking on the link in the Overall column gives an overview with details of who gave consent and when, together with any remarks.

===Giving consent on behalf of a child===

A parent or guardian may be allowed to give consent on behalf of their child by giving them the capability [[Capabilities/tool/policy:acceptbehalf|Agree to the policies on someone else's behalf]] in the user context. See the [[Parent role]] for details of how to create the role and assign a parent to a student. The parent or guardian will then be able to give consent as follows:

# Go to the child's profile page.
# Click the link 'Policies and agreements'.
# Click the red cross next to the policy name.

==Capabilities==

* [[Capabilities/tool/policy:accept|Agree to policies]] - allowed for authenticated user role
* [[Capabilities/tool/policy:managedocs|Manage policies]] - allowed for default role of manager only
* [[Capabilities/tool/policy:viewacceptances|View user agreements reports]] - allowed for default role of manager only
* [[Capabilities/tool/policy:acceptbehalf|Agree to policies on someone else's behalf]] - allowed for default role of manager only

[[Category:Privacy]]

[[es:Plugin de políticas]]
[[de:Richtlinien und Einwilligungen]]

Self enrolment

2018-05-23T07:05:56Z

Sarjona: /* Shared settings for all courses */

{{Enrolment}}

{{Note|If you want your learners to create accounts on your site and have access to your courses, then you first need to enable [[Email-based self registration]] so they can create accounts, and then enable self enrolment within your course(s) so they can enrol. These are two separate steps.}}
Self enrolment is the method whereby users can choose to enrol themselves into a course, either immediately by clicking "\enrol me in this course" or by typing in an enrolment key they have been given. The enrolment plugin needs to be enabled by the site admin in [[Enrolment_plugins|Enrolment plugins]] and has to be enabled within the course. The manual enrolment plugin has to be enabled in the same course as well.

==Enabling self-enrolment in a course==

{{MediaPlayer | url = https://youtu.be/UCVfOIY1m0Y }}

1. In your course, click the Participants link from the navigation drawer (or, for non-Boost themes, click Users in the Course administration block)

2. Click the cogwheel/gear icon and click Enrolment methods(or for non-Boost themes, expand the Users link and click Enrolment methods)

[[File:BoostEnrolmentMethods.png|center]]

3. Open the "eye" icon next to the Self enrolment method:

[[File:OpenSelfEnrolment.png|center]]

===Adding an enrolment key to a course===

If you wish only a certain group of users to self enrol (and not anyone) then you can set an enrolment key which you then tell them to use when they access the self-enrolment screen. See section 1 of [[Enrolment_key|enrolment key]] for how to do this.

===Adding a group enrolment key to a course===

If you wish your users to enrol themselves directly into a group in the course then you can set a group enrolment key which you then tell them to use when they access the self-enrolment screen. See section 2 of [[Enrolment_key|enrolment key]] for how to do this.

The following settings may be changed by clicking the edit (hand/pen) icon to the right of the self-enrolment option in ''Administration > Course administration > Users > Enrolment methods'':

===Setting the enrolment period===

Tick the "enable" box to the right of Enrolment period and then choose your dates.

=== Enrolment duration===

Set the amount of time a user enrolment is valid, starting with the moment the user enrols themselves. If disabled, the enrolment duration will be unlimited.

===Notifying users when their enrolment expires===

It is possible also for students and/or teachers to be notified when enrolments expire by selecting either "Enroller only" or "Enroller and enrolled user" from the dropdown "Notify before enrolment expires" and a time in "Notification threshold".

{|
|[[File:selfenrolmenexpirynotification.png|thumb|Settings for notifiying users before enrolment expires. Click to enlarge.]]
|}

====Editing individual enrolment times====

It is possible to edit the date and hour of an individual's enrolment from ''Administration>Course administration>Users>Enrolled users'' by clicking the edit icon in the enrolment methods column for the user in question. This then brings up a screen where the date and time can be modified.

{|
|[[File:selfenrolment241.png|thumb|Click the edit icon in the enrolment methods column for the user]]
|[[File:selfenrolment242.png|thumb|Modifying the date and time]]
|}

===Unenrolling students who haven't been active on the course===

Choose from the dropdown to the right of "Unenrol inactive after..."

===Deciding the maximum number of users in your course===

Type the maximum number of users you want in your course in "Max enrolled users". When this limit is reached, nobody will be able to self-enrol. If you leave the number at 0 then there will be no maximum number.

===Allowing only cohort members to self-enrol===

If you have cohorts set up, then you can restrict self enrolment to particular cohorts by selecting the name of the cohort from the drop down box, A member of the cohort can self-enrol as normal; whereas a non-member gets a message telling them they are not able to self-enrol.

{|
|[[File:cohortselfenrol.png|thumb|Restricting self enrolment to members of a particular cohort]]
|[[File:noncohortmember.png|thumb|Message seen by a user not in a cohort who is attempting to self-enrol]]
|}

===Sending a welcome message to new users===

If enabled, users receive the following message via email when they self-enrol in a course:

Welcome to {Course name}
If you have not done so already, you should edit your profile page so that we can learn more about you: {link to profile page}

If you want to send a different message, simply type it in the custom welcome message text box.

The following placeholders may be included in the message:

Course name {$a->coursename}
Link to user's profile page {$a->profileurl}
User email {$a->email}
User fullname {$a->fullname}

The welcome message may be sent from the [[Course contacts|course contact]], the [[Keyholder]] or from the default no-reply address. If the course contact is chosen, and there is more than one user with the role, then the welcome message is sent from the course contact with surname that comes first in alphabetical order (MDL-61236).

Note: An admin can customise the message for the whole site by editing the ''welcometocoursetext'' language string. See [[Language customisation]] for further details.

==Admin settings==
The self enrolment plugin may be enabled or disabled throughout the site in ''Administration > Site administration > Plugins > Enrolments > Manage enrol plugins.''

===Shared settings for all courses===
The page ''Administration > Site administration > Plugins > Enrolments > Self enrolment.'' contains options for defaults that admin can set:
* Require an enrolment key - if this box is ticked then all courses with self-enrolment enabled will need to have an enrolment key. The setting won't save until the teacher adds a key - something to be aware of as this can cause confusion:)
* Use password policy - tick this box if you want enrolment keys set by teachers to follow the password policy of the site.
* Show hint - tick this box if you are prepared to allow the first letter of a key to be given as a "hint"
* Enrolment expiry action - specifies what happens when user enrolments reach expiration date. Please note that option "Unenrol user from course" purges grades, group memberships, preferences and other user related data from the courses.
* Hour to send enrolment expiry notifications - specify hour for sending expiration notifications.

===Default enrolment settings in new courses===
These can be set in ''Administration > Site administration > Plugins > Enrolments > Self enrolment'' but teachers in individual courses can alter them to suit their needs:
* Add instance to new courses - if admin selects this, then any new course created will include the self enrolment plugin
* Enable self enrolments- if this is enabled then users by default can self enrol into a course.
* Use group enrolment keys - the setting for group enrolment keys in a course will be set to "yes" by default
* Default role assignment - normally, when users self enrol, they have the student role. If necessary that role can be changed by default here - for example - if your Moodle has a dedicated role you wish to use instead.
* Enrolment duration - this sets the default enrolment length for new courses (but again, may be altered by the course teacher.)
* Notify before enrolment expires - specifies if teacher or optionally students should be notified before the expiration.
* Notification threshold - specify how many days should be users notified before the enrolment expiration.
* Unenrol inactive after- this sets the default time after which a student will be unenrolled if they haven't accessed the courses. (Teachers may change this)
* Max enrolled users - adding a number here will specify the maximum number of users who can self-enrol into new courses. Teachers in the course can change this. If it is left at 0, there will be no maximum.
* Send course welcome message- if this box is checked then newly enrolled users will receive a welcome message by default.

==Self enrolment method options==
One course may contain multiple self enrolment methods. User may be enrolled once in each instance only.

* Custom instance name - specify custom enrolment method name.
* Enable existing enrolments - if disabled all users enrolled via this plugin can not access course.
* Allow new enrolments - disable if you do not want to allow students to self enrol in the future.
* Enrolment key - specify key required for enrolment.
* Use group enrolment keys - optionally use group keys for enrolment too.
* Default assigned role - specify role to be assigned to users during enrolment, this can be changed manually after enrolment.
* Enrolment duration - specify enrolment length, this can be manually after user enrolment.
* Notify before enrolment expires - specifies if teacher or optionally students should be notified before the expiration.
* Notification threshold - specify how many days should be users notified before the enrolment expiration.
* Unenrol inactive after- specify time after which a student will be unenrolled if they haven't accessed the courses.
* Max enrolled users - adding a number here will specify the maximum number of users who can self-enrol into this course.
* Only cohort members - optionally restrict this enrolment method to members of specified cohort.
* Send course welcome message- if this box is checked then newly enrolled users will receive a welcome message by default.
* Custom welcome message - specify custom message if necessary.

==Self enrolment capabilities==

*[[Capabilities/enrol/self:config|Configure self enrol instances]]
*[[Capabilities/enrol/self:manage|Manage enrolled users]]
*[[Capabilities/enrol/self:unenrol|Unenrol users from course]]
*[[Capabilities/enrol/self:unenrolself|Unenrol self from the course]]

[[de:Selbsteinschreibung]]
[[es:Auto inscripción]]

Question sharer

2016-09-13T16:07:41Z

Sarjona:

{{Questions}}

By default, teachers can only share questions with teachers in the same course as themselves and they can only save questions to the course they are currently working in.

This custom role of 'Question sharer' allows them to access and share questions at category or site level. The role must be created by an administrator and then given to selected teachers.

==Creating a new role==
#As an administrator, go to ''Site administration>Users>Permissions>Define roles'' and click the 'Add a new role' button at the bottom of the screen.
#On the next screen, ignore archetypes and presets and click 'Continue'
#Give the role a name and if desired a description and tick the "System" context:

[[File:questionsharer.png|center|thumb|600px]]

4.In the filter, type "question"

5.Set the following capabilities to 'allow':

moodle/question:add

moodle/question:editall

moodle/question:managecategory

moodle/question:moveall

moodle/question:viewall

moodle/question:useall

[[File:questioncaps.png|center]]

6. Click the 'Create this role' button.

==Assigning the role to a teacher==

#As an administrator, go to ''Site administration > Users > Permissions > Assign system roles''.
#You should now see your newly created role here
#Assign the role to the required course teacher(s).(''Note that the users still need to have the teacher role in their courses.)''

Note that you can also assign the role to a user in a course category if you only wish them to share questions in that category. To assign a role to a user within the scope of a particular category only:
# Log in as an administrator.
# From the site's homepage, click on the desired course category.
# From inside the desired course category, click on "Assign roles" in the Administration block.
# Click on the role you wish to assign to the user.
# Select and add the user to the role.

==Sharing questions==

A normal teacher in a course can only see the question category for their own course when they access the question bank. This teacher for example can only see her US Film course questions and can only add her questions to there (or any sub-category she might create):

[[File:regularteacherview.png]]

However, when she has been given the Question sharer role she can then access any questions which have been added at category level ('Miscellaneous') and for the whole site ('System')

[[File:sharerview.png]]

She can also save her questions to there, allowing them to be shared by other teachers with the Question sharer role.

Note that she can also add questions from ''Administration>Front page settings>Question bank.'' (but she has no higher administrative powers.)

===What are these categories?===
*The categories you will see relate to course categories. For example, 'Miscellaneous' is the default category available on a new install of Moodle (which can be renamed)
*So a teacher of French with the Question sharer role might see 'Category - Languages' , assuming her French course resides with the Spanish and German course in a category called 'Languages', for example. If she saves her quiz questions to the 'Languages' category, then her Spanish and German teacher colleagues with the role can also access them from their respective courses.

[[File:questioncategories.png]]

*She can edit the names by clicking on ''Course administration>Question bank>Categories'' and then clicking the edit icon:

{|
|[[File:categorieslink.png|left|Question bank|thumb|300px]]
|[[File:editname.png|eft|Editing the name|thumb|300px]]
|}

===Sharing questions site-wide===
*From a course, go to ''Course administration>Question bank>Categories''
*Click 'Add category' and select System as the parent category.
*Create your category and add questions to it.
*The questions in this category will be available anywhere on the site for teachers with the question sharer role to access.

==Why does this work?==

See: [[Question permissions explained with diagrams]].

==See also==

* [[Question bank]]

[[Category:Roles]]

[[de:Fragen-Sharer-Rolle]]

[[es:Compartidor de preguntas]]

[[fr:Partager la banque de questions]]