+<p align="center"><b>Capita</b></p>
<p>The student data system produced by Capita has been found to have one slight error in its XML output. If you are using Capita you should activate this option - otherwise leave it un-ticked.</p>
-<h1>Automatic Categorisation</h1>
+<p align="center"><b>Automatic Categorisation</b></p>
<p>If the <org><orgunit> element is present in a course's incoming data, its content will be used to specify a category if the course is to be created from scratch.</p>
-<h1>Automatic creation of new courses</h1>
+<p align="center"><b>Automatic creation of new courses</b></p>
<p>The IMS Enterprise enrolment plugin can create new courses for any it finds in the IMS data but not in Moodle's database, if this setting is activated.</p>
-<h1>Automatic creation of user accounts</h1>
+<p align="center"><b>Automatic creation of user accounts</b></p>
<p>IMS Enterprise enrolment data typically describes a set of users. If this setting is turned on, accounts can be created for any users not found in Moodle's database.</p>
-<h1>Automatic deletion of user accounts</h1>
+<p align="center"><b>Automatic deletion of user accounts</b></p>
<p>IMS Enterprise enrolment data can specify the deletion of user accounts (if the "recstatus" flag is set to 3, which represents deletion of an account), if this setting is turned on.</p>
+<p align="center"><b>Format overview</b></p>
<p>Below is a simple guide to the basic structure of a typical IMS Enterprise
data file. Much more information is available on the <a href="http://www.imsglobal.org/enterprise/">IMS Enterprise official website</a>.</p>
+<p align="center"><b>Photo's</b></p>
<p>When creating a new user account based on the Enterprise data, it's possible that a photo is specified for the user - usually by giving a URL to the image file.</p>
<p>If <photo> data is supplied, then Moodle can attempt to download the image file and turn it into the user-picture displayed within Moodle.</p>
+<p align="center"><b>SourceID as fallback</b></p>
<p>In IMS data, the <strong><sourcedid></strong> field represents the persistent ID code
for a person as used in the source system. The <strong><userid></strong>
field is a separate field which should contain the ID code used by
+<p align="center"><b>Targets</b></p>
<p>An IMS Enterprise data file could be intended for multiple "targets" - different LMSes, or different systems within a school/university. It's possible to specify in the Enterprise file that the data is intended for one or more named target systems, by naming them in <target> tags contained within the <properties> tag.</p>
<p>In many cases you don't need to worry about this. Leave the config setting blank and Moodle will always process the data file, no matter whether a target is specified or not. Otherwise, fill in the exact name that will be output inside the <target> tag.
+<p align="center"><b>Truncate course codes</b></p>
<p>In some situations you may have course codes which you wish to truncate to a specified length before processing. If so, enter the number of characters in this box. Otherwise, leave the box <strong>blank</strong> and no truncation will occur.</p>
\ No newline at end of file
-<h1>Unenrolling students/teachers</h1>
+<p align="center"><b>Unenrolling students/teachers</b></p>
<p>The Enterprise data can add as well as remove course enrolments - for students and for teachers. If this setting is turned on, then Moodle will carry out unenrolments when specified in the data.</p>
projects / moodle.git / commitdiff