<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://docs.moodle.org/403/en/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Ppollet</id>
	<title>MoodleDocs - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://docs.moodle.org/403/en/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Ppollet"/>
	<link rel="alternate" type="text/html" href="https://docs.moodle.org/403/en/Special:Contributions/Ppollet"/>
	<updated>2026-05-15T00:47:26Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.43.5</generator>
	<entry>
		<id>https://docs.moodle.org/403/en/index.php?title=Web_services&amp;diff=78357</id>
		<title>Web services</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/403/en/index.php?title=Web_services&amp;diff=78357"/>
		<updated>2010-11-27T10:06:34Z</updated>

		<summary type="html">&lt;p&gt;Ppollet: /* Others implementations */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Moodle_2.0}}&lt;br /&gt;
Web services enable other systems to login to Moodle and perform operations. &lt;br /&gt;
&lt;br /&gt;
==Enabling web services==&lt;br /&gt;
&lt;br /&gt;
To use web services, the feature must be enabled on the site by checking the enablewebservices box in &#039;&#039;Site Administration &amp;gt; [[Advanced features]]&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
For security reasons, web services should only be enabled if you intend to make use of it.&lt;br /&gt;
&lt;br /&gt;
== User Manual ==&lt;br /&gt;
[[How to get a security key]]&lt;br /&gt;
&lt;br /&gt;
== Administrator ==&lt;br /&gt;
* [[How to enable web services for ordinary users]]&lt;br /&gt;
* [[How to enable web services for an external system]]&lt;br /&gt;
&lt;br /&gt;
== Development ==&lt;br /&gt;
* [[Development:Web services]]&lt;br /&gt;
* [[Development:External services security]]&lt;br /&gt;
* [[Development:External services description]]&lt;br /&gt;
* [[Development:Creating a web service and a web service function]]&lt;br /&gt;
* [[Development:Creating a web service client]]&lt;br /&gt;
&lt;br /&gt;
== Others implementations ==&lt;br /&gt;
* [[Web Services:OK Tech Web Services]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Web Services]]&lt;br /&gt;
&lt;br /&gt;
[[eu:Web-zerbitzuak]]&lt;/div&gt;</summary>
		<author><name>Ppollet</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/403/en/index.php?title=Web_services&amp;diff=78356</id>
		<title>Web services</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/403/en/index.php?title=Web_services&amp;diff=78356"/>
		<updated>2010-11-27T10:05:27Z</updated>

		<summary type="html">&lt;p&gt;Ppollet: /* Others implementations */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Moodle_2.0}}&lt;br /&gt;
Web services enable other systems to login to Moodle and perform operations. &lt;br /&gt;
&lt;br /&gt;
==Enabling web services==&lt;br /&gt;
&lt;br /&gt;
To use web services, the feature must be enabled on the site by checking the enablewebservices box in &#039;&#039;Site Administration &amp;gt; [[Advanced features]]&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
For security reasons, web services should only be enabled if you intend to make use of it.&lt;br /&gt;
&lt;br /&gt;
== User Manual ==&lt;br /&gt;
[[How to get a security key]]&lt;br /&gt;
&lt;br /&gt;
== Administrator ==&lt;br /&gt;
* [[How to enable web services for ordinary users]]&lt;br /&gt;
* [[How to enable web services for an external system]]&lt;br /&gt;
&lt;br /&gt;
== Development ==&lt;br /&gt;
* [[Development:Web services]]&lt;br /&gt;
* [[Development:External services security]]&lt;br /&gt;
* [[Development:External services description]]&lt;br /&gt;
* [[Development:Creating a web service and a web service function]]&lt;br /&gt;
* [[Development:Creating a web service client]]&lt;br /&gt;
&lt;br /&gt;
== Others implementations ==&lt;br /&gt;
* [[OK Tech Web Services]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Web Services]]&lt;br /&gt;
&lt;br /&gt;
[[eu:Web-zerbitzuak]]&lt;/div&gt;</summary>
		<author><name>Ppollet</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/403/en/index.php?title=Web_services&amp;diff=78355</id>
		<title>Web services</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/403/en/index.php?title=Web_services&amp;diff=78355"/>
		<updated>2010-11-27T10:04:45Z</updated>

		<summary type="html">&lt;p&gt;Ppollet: /* Development */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Moodle_2.0}}&lt;br /&gt;
Web services enable other systems to login to Moodle and perform operations. &lt;br /&gt;
&lt;br /&gt;
==Enabling web services==&lt;br /&gt;
&lt;br /&gt;
To use web services, the feature must be enabled on the site by checking the enablewebservices box in &#039;&#039;Site Administration &amp;gt; [[Advanced features]]&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
For security reasons, web services should only be enabled if you intend to make use of it.&lt;br /&gt;
&lt;br /&gt;
== User Manual ==&lt;br /&gt;
[[How to get a security key]]&lt;br /&gt;
&lt;br /&gt;
== Administrator ==&lt;br /&gt;
* [[How to enable web services for ordinary users]]&lt;br /&gt;
* [[How to enable web services for an external system]]&lt;br /&gt;
&lt;br /&gt;
== Development ==&lt;br /&gt;
* [[Development:Web services]]&lt;br /&gt;
* [[Development:External services security]]&lt;br /&gt;
* [[Development:External services description]]&lt;br /&gt;
* [[Development:Creating a web service and a web service function]]&lt;br /&gt;
* [[Development:Creating a web service client]]&lt;br /&gt;
&lt;br /&gt;
== Others implementations ==&lt;br /&gt;
* [[OK Tech Web Service]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Web Services]]&lt;br /&gt;
&lt;br /&gt;
[[eu:Web-zerbitzuak]]&lt;/div&gt;</summary>
		<author><name>Ppollet</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/403/en/index.php?title=Development:Web_services&amp;diff=30798</id>
		<title>Development:Web services</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/403/en/index.php?title=Development:Web_services&amp;diff=30798"/>
		<updated>2007-12-30T14:37:46Z</updated>

		<summary type="html">&lt;p&gt;Ppollet: /* get course */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page is to decide on a STANDARD list of CORE web service functions that we should support in Moodle (by XMLRPC, REST and SOAP with the option to plug in AMFPHP for Flash/Flex interfaces) as an API for those writing code to work against Moodle.&lt;br /&gt;
&lt;br /&gt;
Please add new functions if there&#039;s functionality you want that isn&#039;t covered (we can refactor/whittle at the end).&lt;br /&gt;
&lt;br /&gt;
==add user==&lt;br /&gt;
I think we should require all data needed for a successful &amp;quot;first login&amp;quot; to Moodle without popping him out the profile page to fill in all missing required data. This may require extra inputs such as city, description ... (unsure of the full list depending of Moodle version ?).&lt;br /&gt;
Also password should be &amp;quot;required&amp;quot; if authentication method is &amp;quot;internal&amp;quot; . &lt;br /&gt;
&lt;br /&gt;
INPUT:&lt;br /&gt;
    firstname&lt;br /&gt;
    lastname&lt;br /&gt;
    email &lt;br /&gt;
    idnumber&lt;br /&gt;
    login &lt;br /&gt;
    authentication method (optional , default= manual ?)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Adds a new user to the user database &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    id or false&lt;br /&gt;
&lt;br /&gt;
==delete user==&lt;br /&gt;
INPUT:&lt;br /&gt;
    idnumber  or &lt;br /&gt;
    email or &lt;br /&gt;
    id or&lt;br /&gt;
    login&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    User is marked as deleted&lt;br /&gt;
    All it&#039;s role assignments are destroyed &lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true/false&lt;br /&gt;
&lt;br /&gt;
==get user==&lt;br /&gt;
INPUT:&lt;br /&gt;
    idnumber  or &lt;br /&gt;
    email or &lt;br /&gt;
    id or&lt;br /&gt;
    login&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    user record with optional fields set (Moodle 1.8 and later) and maybe some fields filtered out (password, &lt;br /&gt;
    email if user said not to disclose it ...) depending of the identity of the &amp;quot;caller&amp;quot; (admin or the user himself) &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    false  or user record&lt;br /&gt;
&lt;br /&gt;
==add course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    name&lt;br /&gt;
    shortname&lt;br /&gt;
    format (default topics)&lt;br /&gt;
    idnumber &lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Adds a new course to the course table&lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    id or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==delete course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    name OR&lt;br /&gt;
    shortname  OR&lt;br /&gt;
    idnumber OR&lt;br /&gt;
    id&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Deletes a course from the course table&lt;br /&gt;
    What about associated ressources, roles ... &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==get course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    id or  idnumber or shortname&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
     fetch course record with some fields filtered out depending of the &amp;quot;caller&amp;quot; identity (admin, teacher, student ...)&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    false  or course record&lt;br /&gt;
&lt;br /&gt;
==enrol student to course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    course unique Id (Moodle&#039;s ID or idnumber or shortname)&lt;br /&gt;
    student unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Assign student role to course &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==unenrol student from course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    course unique Id (Moodle&#039;s ID or idnumber or shortname)&lt;br /&gt;
    student unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    remove student role from course &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==assign role to course==&lt;br /&gt;
INPUT:&lt;br /&gt;
   course unique Id (Moodle&#039;s ID or idnumber or shortname)&lt;br /&gt;
   user unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
   role id (teacher, non editing teacher, student (?) ...)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   assign given user a &amp;quot;standard&amp;quot; role to given course   &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==remove role from course==&lt;br /&gt;
INPUT:&lt;br /&gt;
   course unique Id (Moodle&#039;s ID or idnumber or shortname)&lt;br /&gt;
   user unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
   role id (teacher, non editing teacher, student (?) ...)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   remove given user&#039;s &amp;quot;standard&amp;quot; role from given course   &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==get my courses==&lt;br /&gt;
&lt;br /&gt;
INPUT:&lt;br /&gt;
   user unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   return a &amp;quot;list&amp;quot; of course&#039;s id in which given user move given user has some role assigned     &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    &amp;quot;array&amp;quot; of (course id, course shortname, course fullname, role id, role name, course url)&lt;br /&gt;
    or false in case of error (bad user id)&lt;br /&gt;
&lt;br /&gt;
==get last changes in my courses==&lt;br /&gt;
&lt;br /&gt;
INPUT:&lt;br /&gt;
   user unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
   course unique Id (Moodle&#039;s ID ,idnumber or shortname) - optional (default = all my courses)&lt;br /&gt;
   timestamp - optional (default = time of last connexion in every course)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   return a &amp;quot;list&amp;quot; of changes (resource added/modified, new activities, etc.) for courses in which given user has some role assigned - since timestamp or last connexion in given course &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    &amp;quot;array&amp;quot; of (course id, course shortname, course fullname, role id, role name, url of the resource/activity, time of change)&lt;br /&gt;
    or false in case of error (bad user/course id)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==get grades==&lt;br /&gt;
&lt;br /&gt;
INPUT:&lt;br /&gt;
   user unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
   course unique Id (Moodle&#039;s ID ,idnumber or shortname) - optional (default = all my courses)&lt;br /&gt;
   &lt;br /&gt;
OPERATION:&lt;br /&gt;
   return a &amp;quot;list&amp;quot; of grades and statistics for the given student in the given course&lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    &amp;quot;array&amp;quot; of grades records (name,maxgrade,grade,percent,weight,weighted,sortOrder) &lt;br /&gt;
    and &amp;quot;array&amp;quot; of stats (gradeItems,allgrades, points,totalpoints, percent, weight, weighted;)  &lt;br /&gt;
    or false in case of error (bad user/course id or user not in course)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==get groups==&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   return a &amp;quot;list&amp;quot; of group records in a given course (or site ?) &lt;br /&gt;
&lt;br /&gt;
==get group members==&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   return a &amp;quot;list&amp;quot; of ids  for members of a group (within a course or global) &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==enrol to group==&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   add a new member to a group&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==unenrol from group==&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   remove membership from a group&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==get events ==&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   return a &amp;quot;list&amp;quot; of event&#039;s identifiers suitable from the &amp;quot;get event&amp;quot; operation&lt;br /&gt;
&lt;br /&gt;
==get event==&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   return in an &amp;quot;exportable&amp;quot; format (iCal, vCal ...)an event recorded in Moodle database (site, course, private ...)&lt;br /&gt;
&lt;br /&gt;
==set event==&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   add/modify an event in Moodle database (site, course, private ...)&lt;/div&gt;</summary>
		<author><name>Ppollet</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/403/en/index.php?title=Development:Web_services&amp;diff=30797</id>
		<title>Development:Web services</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/403/en/index.php?title=Development:Web_services&amp;diff=30797"/>
		<updated>2007-12-30T14:37:22Z</updated>

		<summary type="html">&lt;p&gt;Ppollet: /* get user */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page is to decide on a STANDARD list of CORE web service functions that we should support in Moodle (by XMLRPC, REST and SOAP with the option to plug in AMFPHP for Flash/Flex interfaces) as an API for those writing code to work against Moodle.&lt;br /&gt;
&lt;br /&gt;
Please add new functions if there&#039;s functionality you want that isn&#039;t covered (we can refactor/whittle at the end).&lt;br /&gt;
&lt;br /&gt;
==add user==&lt;br /&gt;
I think we should require all data needed for a successful &amp;quot;first login&amp;quot; to Moodle without popping him out the profile page to fill in all missing required data. This may require extra inputs such as city, description ... (unsure of the full list depending of Moodle version ?).&lt;br /&gt;
Also password should be &amp;quot;required&amp;quot; if authentication method is &amp;quot;internal&amp;quot; . &lt;br /&gt;
&lt;br /&gt;
INPUT:&lt;br /&gt;
    firstname&lt;br /&gt;
    lastname&lt;br /&gt;
    email &lt;br /&gt;
    idnumber&lt;br /&gt;
    login &lt;br /&gt;
    authentication method (optional , default= manual ?)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Adds a new user to the user database &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    id or false&lt;br /&gt;
&lt;br /&gt;
==delete user==&lt;br /&gt;
INPUT:&lt;br /&gt;
    idnumber  or &lt;br /&gt;
    email or &lt;br /&gt;
    id or&lt;br /&gt;
    login&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    User is marked as deleted&lt;br /&gt;
    All it&#039;s role assignments are destroyed &lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true/false&lt;br /&gt;
&lt;br /&gt;
==get user==&lt;br /&gt;
INPUT:&lt;br /&gt;
    idnumber  or &lt;br /&gt;
    email or &lt;br /&gt;
    id or&lt;br /&gt;
    login&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    user record with optional fields set (Moodle 1.8 and later) and maybe some fields filtered out (password, &lt;br /&gt;
    email if user said not to disclose it ...) depending of the identity of the &amp;quot;caller&amp;quot; (admin or the user himself) &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    false  or user record&lt;br /&gt;
&lt;br /&gt;
==add course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    name&lt;br /&gt;
    shortname&lt;br /&gt;
    format (default topics)&lt;br /&gt;
    idnumber &lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Adds a new course to the course table&lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    id or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==delete course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    name OR&lt;br /&gt;
    shortname  OR&lt;br /&gt;
    idnumber OR&lt;br /&gt;
    id&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Deletes a course from the course table&lt;br /&gt;
    What about associated ressources, roles ... &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==get course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    idor  idnumber or shortname&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
     fetch course record with some fields filtered out depending of the &amp;quot;caller&amp;quot; identity (admin, teacher, student ...)&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    false  or course record &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==enrol student to course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    course unique Id (Moodle&#039;s ID or idnumber or shortname)&lt;br /&gt;
    student unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Assign student role to course &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==unenrol student from course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    course unique Id (Moodle&#039;s ID or idnumber or shortname)&lt;br /&gt;
    student unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    remove student role from course &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==assign role to course==&lt;br /&gt;
INPUT:&lt;br /&gt;
   course unique Id (Moodle&#039;s ID or idnumber or shortname)&lt;br /&gt;
   user unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
   role id (teacher, non editing teacher, student (?) ...)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   assign given user a &amp;quot;standard&amp;quot; role to given course   &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==remove role from course==&lt;br /&gt;
INPUT:&lt;br /&gt;
   course unique Id (Moodle&#039;s ID or idnumber or shortname)&lt;br /&gt;
   user unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
   role id (teacher, non editing teacher, student (?) ...)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   remove given user&#039;s &amp;quot;standard&amp;quot; role from given course   &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==get my courses==&lt;br /&gt;
&lt;br /&gt;
INPUT:&lt;br /&gt;
   user unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   return a &amp;quot;list&amp;quot; of course&#039;s id in which given user move given user has some role assigned     &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    &amp;quot;array&amp;quot; of (course id, course shortname, course fullname, role id, role name, course url)&lt;br /&gt;
    or false in case of error (bad user id)&lt;br /&gt;
&lt;br /&gt;
==get last changes in my courses==&lt;br /&gt;
&lt;br /&gt;
INPUT:&lt;br /&gt;
   user unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
   course unique Id (Moodle&#039;s ID ,idnumber or shortname) - optional (default = all my courses)&lt;br /&gt;
   timestamp - optional (default = time of last connexion in every course)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   return a &amp;quot;list&amp;quot; of changes (resource added/modified, new activities, etc.) for courses in which given user has some role assigned - since timestamp or last connexion in given course &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    &amp;quot;array&amp;quot; of (course id, course shortname, course fullname, role id, role name, url of the resource/activity, time of change)&lt;br /&gt;
    or false in case of error (bad user/course id)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==get grades==&lt;br /&gt;
&lt;br /&gt;
INPUT:&lt;br /&gt;
   user unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
   course unique Id (Moodle&#039;s ID ,idnumber or shortname) - optional (default = all my courses)&lt;br /&gt;
   &lt;br /&gt;
OPERATION:&lt;br /&gt;
   return a &amp;quot;list&amp;quot; of grades and statistics for the given student in the given course&lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    &amp;quot;array&amp;quot; of grades records (name,maxgrade,grade,percent,weight,weighted,sortOrder) &lt;br /&gt;
    and &amp;quot;array&amp;quot; of stats (gradeItems,allgrades, points,totalpoints, percent, weight, weighted;)  &lt;br /&gt;
    or false in case of error (bad user/course id or user not in course)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==get groups==&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   return a &amp;quot;list&amp;quot; of group records in a given course (or site ?) &lt;br /&gt;
&lt;br /&gt;
==get group members==&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   return a &amp;quot;list&amp;quot; of ids  for members of a group (within a course or global) &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==enrol to group==&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   add a new member to a group&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==unenrol from group==&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   remove membership from a group&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==get events ==&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   return a &amp;quot;list&amp;quot; of event&#039;s identifiers suitable from the &amp;quot;get event&amp;quot; operation&lt;br /&gt;
&lt;br /&gt;
==get event==&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   return in an &amp;quot;exportable&amp;quot; format (iCal, vCal ...)an event recorded in Moodle database (site, course, private ...)&lt;br /&gt;
&lt;br /&gt;
==set event==&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   add/modify an event in Moodle database (site, course, private ...)&lt;/div&gt;</summary>
		<author><name>Ppollet</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/403/en/index.php?title=Development:Web_services&amp;diff=30793</id>
		<title>Development:Web services</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/403/en/index.php?title=Development:Web_services&amp;diff=30793"/>
		<updated>2007-12-30T10:36:01Z</updated>

		<summary type="html">&lt;p&gt;Ppollet: /* get user */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page is to decide on a STANDARD list of CORE web service functions that we should support in Moodle (by XMLRPC, REST and SOAP with the option to plug in AMFPHP for Flash/Flex interfaces) as an API for those writing code to work against Moodle.&lt;br /&gt;
&lt;br /&gt;
Please add new functions if there&#039;s functionality you want that isn&#039;t covered (we can refactor/whittle at the end).&lt;br /&gt;
&lt;br /&gt;
==add user==&lt;br /&gt;
I think we should require all data needed for a successful &amp;quot;first login&amp;quot; to Moodle without popping him out the profile page to fill in all missing required data. This may require extra inputs such as city, description ... (unsure of the full list depending of Moodle version ?).&lt;br /&gt;
Also password should be &amp;quot;required&amp;quot; if authentication method is &amp;quot;internal&amp;quot; . &lt;br /&gt;
&lt;br /&gt;
INPUT:&lt;br /&gt;
    firstname&lt;br /&gt;
    lastname&lt;br /&gt;
    email &lt;br /&gt;
    idnumber&lt;br /&gt;
    login &lt;br /&gt;
    authentication method (optional , default= manual ?)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Adds a new user to the user database &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    id or false&lt;br /&gt;
&lt;br /&gt;
==delete user==&lt;br /&gt;
INPUT:&lt;br /&gt;
    idnumber  or &lt;br /&gt;
    email or &lt;br /&gt;
    id or&lt;br /&gt;
    login&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    User is marked as deleted&lt;br /&gt;
    All it&#039;s role assignments are destroyed &lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true/false&lt;br /&gt;
&lt;br /&gt;
==get user==&lt;br /&gt;
INPUT:&lt;br /&gt;
    idnumber  or &lt;br /&gt;
    email or &lt;br /&gt;
    id or&lt;br /&gt;
    login&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    user record with optional fields set (Moodle 1.8 and later) and maybe some fields filtered out (password, &lt;br /&gt;
    email if user said not to discolose it ...) depending of the identity of the &amp;quot;caller&amp;quot; (admin or the user himself) &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    false  or user record&lt;br /&gt;
&lt;br /&gt;
==add course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    name&lt;br /&gt;
    shortname&lt;br /&gt;
    format (default topics)&lt;br /&gt;
    idnumber &lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Adds a new course to the course table&lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    id or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==delete course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    name OR&lt;br /&gt;
    shortname  OR&lt;br /&gt;
    idnumber OR&lt;br /&gt;
    id&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Deletes a course from the course table&lt;br /&gt;
    What about associated ressources, roles ... &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==get course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    idor  idnumber or shortname&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
     fetch course record with some fields filtered out depending of the &amp;quot;caller&amp;quot; identity (admin, teacher, student ...)&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    false  or course record &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==enrol student to course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    course unique Id (Moodle&#039;s ID or idnumber or shortname)&lt;br /&gt;
    student unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Assign student role to course &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==unenrol student from course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    course unique Id (Moodle&#039;s ID or idnumber or shortname)&lt;br /&gt;
    student unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    remove student role from course &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==assign role to course==&lt;br /&gt;
INPUT:&lt;br /&gt;
   course unique Id (Moodle&#039;s ID or idnumber or shortname)&lt;br /&gt;
   user unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
   role id (teacher, non editing teacher, student (?) ...)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   assign given user a &amp;quot;standard&amp;quot; role to given course   &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==remove role from course==&lt;br /&gt;
INPUT:&lt;br /&gt;
   course unique Id (Moodle&#039;s ID or idnumber or shortname)&lt;br /&gt;
   user unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
   role id (teacher, non editing teacher, student (?) ...)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   remove given user&#039;s &amp;quot;standard&amp;quot; role from given course   &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==get my courses==&lt;br /&gt;
&lt;br /&gt;
INPUT:&lt;br /&gt;
   user unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   return a &amp;quot;list&amp;quot; of course&#039;s id in which given user move given user has some role assigned     &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    &amp;quot;array&amp;quot; of (course id, course shortname, course fullname, role id, role name, course url)&lt;br /&gt;
    or false in case of error (bad user id)&lt;br /&gt;
&lt;br /&gt;
==get last changes in my courses==&lt;br /&gt;
&lt;br /&gt;
INPUT:&lt;br /&gt;
   user unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
   course unique Id (Moodle&#039;s ID ,idnumber or shortname) - optional (default = all my courses)&lt;br /&gt;
   timestamp - optional (default = time of last connexion in every course)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   return a &amp;quot;list&amp;quot; of changes (resource added/modified, new activities, etc.) for courses in which given user has some role assigned - since timestamp or last connexion in given course &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    &amp;quot;array&amp;quot; of (course id, course shortname, course fullname, role id, role name, url of the resource/activity, time of change)&lt;br /&gt;
    or false in case of error (bad user/course id)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==get grades==&lt;br /&gt;
&lt;br /&gt;
INPUT:&lt;br /&gt;
   user unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
   course unique Id (Moodle&#039;s ID ,idnumber or shortname) - optional (default = all my courses)&lt;br /&gt;
   &lt;br /&gt;
OPERATION:&lt;br /&gt;
   return a &amp;quot;list&amp;quot; of grades and statistics for the given student in the given course&lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    &amp;quot;array&amp;quot; of grades records (name,maxgrade,grade,percent,weight,weighted,sortOrder) &lt;br /&gt;
    and &amp;quot;array&amp;quot; of stats (gradeItems,allgrades, points,totalpoints, percent, weight, weighted;)  &lt;br /&gt;
    or false in case of error (bad user/course id or user not in course)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==get groups==&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   return a &amp;quot;list&amp;quot; of group records in a given course (or site ?) &lt;br /&gt;
&lt;br /&gt;
==get group members==&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   return a &amp;quot;list&amp;quot; of ids  for members of a group (within a course or global) &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==enrol to group==&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   add a new member to a group&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==unenrol from group==&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   remove membership from a group&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==get events ==&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   return a &amp;quot;list&amp;quot; of event&#039;s identifiers suitable from the &amp;quot;get event&amp;quot; operation&lt;br /&gt;
&lt;br /&gt;
==get event==&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   return in an &amp;quot;exportable&amp;quot; format (iCal, vCal ...)an event recorded in Moodle database (site, course, private ...)&lt;br /&gt;
&lt;br /&gt;
==set event==&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   add/modify an event in Moodle database (site, course, private ...)&lt;/div&gt;</summary>
		<author><name>Ppollet</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/403/en/index.php?title=Development:Web_services&amp;diff=30792</id>
		<title>Development:Web services</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/403/en/index.php?title=Development:Web_services&amp;diff=30792"/>
		<updated>2007-12-30T10:35:18Z</updated>

		<summary type="html">&lt;p&gt;Ppollet: /* get user */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page is to decide on a STANDARD list of CORE web service functions that we should support in Moodle (by XMLRPC, REST and SOAP with the option to plug in AMFPHP for Flash/Flex interfaces) as an API for those writing code to work against Moodle.&lt;br /&gt;
&lt;br /&gt;
Please add new functions if there&#039;s functionality you want that isn&#039;t covered (we can refactor/whittle at the end).&lt;br /&gt;
&lt;br /&gt;
==add user==&lt;br /&gt;
I think we should require all data needed for a successful &amp;quot;first login&amp;quot; to Moodle without popping him out the profile page to fill in all missing required data. This may require extra inputs such as city, description ... (unsure of the full list depending of Moodle version ?).&lt;br /&gt;
Also password should be &amp;quot;required&amp;quot; if authentication method is &amp;quot;internal&amp;quot; . &lt;br /&gt;
&lt;br /&gt;
INPUT:&lt;br /&gt;
    firstname&lt;br /&gt;
    lastname&lt;br /&gt;
    email &lt;br /&gt;
    idnumber&lt;br /&gt;
    login &lt;br /&gt;
    authentication method (optional , default= manual ?)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Adds a new user to the user database &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    id or false&lt;br /&gt;
&lt;br /&gt;
==delete user==&lt;br /&gt;
INPUT:&lt;br /&gt;
    idnumber  or &lt;br /&gt;
    email or &lt;br /&gt;
    id or&lt;br /&gt;
    login&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    User is marked as deleted&lt;br /&gt;
    All it&#039;s role assignments are destroyed &lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true/false&lt;br /&gt;
&lt;br /&gt;
==get user==&lt;br /&gt;
INPUT:&lt;br /&gt;
    idnumber  or &lt;br /&gt;
    email or &lt;br /&gt;
    id or&lt;br /&gt;
    login&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   user record with optional fields set (Moodle 1.8 and later) and maybe some fields filtered out (password, &lt;br /&gt;
email if user said not to discolose it ...) depending of the identity of the &amp;quot;caller&amp;quot; (admin or the user himself) &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    false  or user record&lt;br /&gt;
&lt;br /&gt;
==add course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    name&lt;br /&gt;
    shortname&lt;br /&gt;
    format (default topics)&lt;br /&gt;
    idnumber &lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Adds a new course to the course table&lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    id or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==delete course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    name OR&lt;br /&gt;
    shortname  OR&lt;br /&gt;
    idnumber OR&lt;br /&gt;
    id&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Deletes a course from the course table&lt;br /&gt;
    What about associated ressources, roles ... &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==get course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    idor  idnumber or shortname&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
     fetch course record with some fields filtered out depending of the &amp;quot;caller&amp;quot; identity (admin, teacher, student ...)&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    false  or course record &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==enrol student to course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    course unique Id (Moodle&#039;s ID or idnumber or shortname)&lt;br /&gt;
    student unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Assign student role to course &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==unenrol student from course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    course unique Id (Moodle&#039;s ID or idnumber or shortname)&lt;br /&gt;
    student unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    remove student role from course &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==assign role to course==&lt;br /&gt;
INPUT:&lt;br /&gt;
   course unique Id (Moodle&#039;s ID or idnumber or shortname)&lt;br /&gt;
   user unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
   role id (teacher, non editing teacher, student (?) ...)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   assign given user a &amp;quot;standard&amp;quot; role to given course   &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==remove role from course==&lt;br /&gt;
INPUT:&lt;br /&gt;
   course unique Id (Moodle&#039;s ID or idnumber or shortname)&lt;br /&gt;
   user unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
   role id (teacher, non editing teacher, student (?) ...)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   remove given user&#039;s &amp;quot;standard&amp;quot; role from given course   &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==get my courses==&lt;br /&gt;
&lt;br /&gt;
INPUT:&lt;br /&gt;
   user unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   return a &amp;quot;list&amp;quot; of course&#039;s id in which given user move given user has some role assigned     &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    &amp;quot;array&amp;quot; of (course id, course shortname, course fullname, role id, role name, course url)&lt;br /&gt;
    or false in case of error (bad user id)&lt;br /&gt;
&lt;br /&gt;
==get last changes in my courses==&lt;br /&gt;
&lt;br /&gt;
INPUT:&lt;br /&gt;
   user unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
   course unique Id (Moodle&#039;s ID ,idnumber or shortname) - optional (default = all my courses)&lt;br /&gt;
   timestamp - optional (default = time of last connexion in every course)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   return a &amp;quot;list&amp;quot; of changes (resource added/modified, new activities, etc.) for courses in which given user has some role assigned - since timestamp or last connexion in given course &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    &amp;quot;array&amp;quot; of (course id, course shortname, course fullname, role id, role name, url of the resource/activity, time of change)&lt;br /&gt;
    or false in case of error (bad user/course id)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==get grades==&lt;br /&gt;
&lt;br /&gt;
INPUT:&lt;br /&gt;
   user unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
   course unique Id (Moodle&#039;s ID ,idnumber or shortname) - optional (default = all my courses)&lt;br /&gt;
   &lt;br /&gt;
OPERATION:&lt;br /&gt;
   return a &amp;quot;list&amp;quot; of grades and statistics for the given student in the given course&lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    &amp;quot;array&amp;quot; of grades records (name,maxgrade,grade,percent,weight,weighted,sortOrder) &lt;br /&gt;
    and &amp;quot;array&amp;quot; of stats (gradeItems,allgrades, points,totalpoints, percent, weight, weighted;)  &lt;br /&gt;
    or false in case of error (bad user/course id or user not in course)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==get groups==&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   return a &amp;quot;list&amp;quot; of group records in a given course (or site ?) &lt;br /&gt;
&lt;br /&gt;
==get group members==&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   return a &amp;quot;list&amp;quot; of ids  for members of a group (within a course or global) &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==enrol to group==&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   add a new member to a group&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==unenrol from group==&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   remove membership from a group&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==get events ==&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   return a &amp;quot;list&amp;quot; of event&#039;s identifiers suitable from the &amp;quot;get event&amp;quot; operation&lt;br /&gt;
&lt;br /&gt;
==get event==&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   return in an &amp;quot;exportable&amp;quot; format (iCal, vCal ...)an event recorded in Moodle database (site, course, private ...)&lt;br /&gt;
&lt;br /&gt;
==set event==&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   add/modify an event in Moodle database (site, course, private ...)&lt;/div&gt;</summary>
		<author><name>Ppollet</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/403/en/index.php?title=Development:Web_services&amp;diff=30791</id>
		<title>Development:Web services</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/403/en/index.php?title=Development:Web_services&amp;diff=30791"/>
		<updated>2007-12-30T10:34:51Z</updated>

		<summary type="html">&lt;p&gt;Ppollet: /* get user */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page is to decide on a STANDARD list of CORE web service functions that we should support in Moodle (by XMLRPC, REST and SOAP with the option to plug in AMFPHP for Flash/Flex interfaces) as an API for those writing code to work against Moodle.&lt;br /&gt;
&lt;br /&gt;
Please add new functions if there&#039;s functionality you want that isn&#039;t covered (we can refactor/whittle at the end).&lt;br /&gt;
&lt;br /&gt;
==add user==&lt;br /&gt;
I think we should require all data needed for a successful &amp;quot;first login&amp;quot; to Moodle without popping him out the profile page to fill in all missing required data. This may require extra inputs such as city, description ... (unsure of the full list depending of Moodle version ?).&lt;br /&gt;
Also password should be &amp;quot;required&amp;quot; if authentication method is &amp;quot;internal&amp;quot; . &lt;br /&gt;
&lt;br /&gt;
INPUT:&lt;br /&gt;
    firstname&lt;br /&gt;
    lastname&lt;br /&gt;
    email &lt;br /&gt;
    idnumber&lt;br /&gt;
    login &lt;br /&gt;
    authentication method (optional , default= manual ?)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Adds a new user to the user database &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    id or false&lt;br /&gt;
&lt;br /&gt;
==delete user==&lt;br /&gt;
INPUT:&lt;br /&gt;
    idnumber  or &lt;br /&gt;
    email or &lt;br /&gt;
    id or&lt;br /&gt;
    login&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    User is marked as deleted&lt;br /&gt;
    All it&#039;s role assignments are destroyed &lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true/false&lt;br /&gt;
&lt;br /&gt;
==get user==&lt;br /&gt;
INPUT:&lt;br /&gt;
    idnumber  or &lt;br /&gt;
    email or &lt;br /&gt;
    id or&lt;br /&gt;
    login&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   user record with optional fields set (Moodle 1.8 and later) and maybe some fields filtered out &lt;br /&gt;
(password, email if user said not to discolose it ...) depending of the identity of the &amp;quot;caller&amp;quot; &lt;br /&gt;
(admin or the user himself) &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    false  or user record&lt;br /&gt;
&lt;br /&gt;
==add course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    name&lt;br /&gt;
    shortname&lt;br /&gt;
    format (default topics)&lt;br /&gt;
    idnumber &lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Adds a new course to the course table&lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    id or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==delete course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    name OR&lt;br /&gt;
    shortname  OR&lt;br /&gt;
    idnumber OR&lt;br /&gt;
    id&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Deletes a course from the course table&lt;br /&gt;
    What about associated ressources, roles ... &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==get course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    idor  idnumber or shortname&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
     fetch course record with some fields filtered out depending of the &amp;quot;caller&amp;quot; identity (admin, teacher, student ...)&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    false  or course record &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==enrol student to course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    course unique Id (Moodle&#039;s ID or idnumber or shortname)&lt;br /&gt;
    student unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Assign student role to course &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==unenrol student from course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    course unique Id (Moodle&#039;s ID or idnumber or shortname)&lt;br /&gt;
    student unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    remove student role from course &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==assign role to course==&lt;br /&gt;
INPUT:&lt;br /&gt;
   course unique Id (Moodle&#039;s ID or idnumber or shortname)&lt;br /&gt;
   user unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
   role id (teacher, non editing teacher, student (?) ...)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   assign given user a &amp;quot;standard&amp;quot; role to given course   &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==remove role from course==&lt;br /&gt;
INPUT:&lt;br /&gt;
   course unique Id (Moodle&#039;s ID or idnumber or shortname)&lt;br /&gt;
   user unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
   role id (teacher, non editing teacher, student (?) ...)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   remove given user&#039;s &amp;quot;standard&amp;quot; role from given course   &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==get my courses==&lt;br /&gt;
&lt;br /&gt;
INPUT:&lt;br /&gt;
   user unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   return a &amp;quot;list&amp;quot; of course&#039;s id in which given user move given user has some role assigned     &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    &amp;quot;array&amp;quot; of (course id, course shortname, course fullname, role id, role name, course url)&lt;br /&gt;
    or false in case of error (bad user id)&lt;br /&gt;
&lt;br /&gt;
==get last changes in my courses==&lt;br /&gt;
&lt;br /&gt;
INPUT:&lt;br /&gt;
   user unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
   course unique Id (Moodle&#039;s ID ,idnumber or shortname) - optional (default = all my courses)&lt;br /&gt;
   timestamp - optional (default = time of last connexion in every course)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   return a &amp;quot;list&amp;quot; of changes (resource added/modified, new activities, etc.) for courses in which given user has some role assigned - since timestamp or last connexion in given course &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    &amp;quot;array&amp;quot; of (course id, course shortname, course fullname, role id, role name, url of the resource/activity, time of change)&lt;br /&gt;
    or false in case of error (bad user/course id)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==get grades==&lt;br /&gt;
&lt;br /&gt;
INPUT:&lt;br /&gt;
   user unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
   course unique Id (Moodle&#039;s ID ,idnumber or shortname) - optional (default = all my courses)&lt;br /&gt;
   &lt;br /&gt;
OPERATION:&lt;br /&gt;
   return a &amp;quot;list&amp;quot; of grades and statistics for the given student in the given course&lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    &amp;quot;array&amp;quot; of grades records (name,maxgrade,grade,percent,weight,weighted,sortOrder) &lt;br /&gt;
    and &amp;quot;array&amp;quot; of stats (gradeItems,allgrades, points,totalpoints, percent, weight, weighted;)  &lt;br /&gt;
    or false in case of error (bad user/course id or user not in course)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==get groups==&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   return a &amp;quot;list&amp;quot; of group records in a given course (or site ?) &lt;br /&gt;
&lt;br /&gt;
==get group members==&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   return a &amp;quot;list&amp;quot; of ids  for members of a group (within a course or global) &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==enrol to group==&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   add a new member to a group&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==unenrol from group==&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   remove membership from a group&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==get events ==&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   return a &amp;quot;list&amp;quot; of event&#039;s identifiers suitable from the &amp;quot;get event&amp;quot; operation&lt;br /&gt;
&lt;br /&gt;
==get event==&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   return in an &amp;quot;exportable&amp;quot; format (iCal, vCal ...)an event recorded in Moodle database (site, course, private ...)&lt;br /&gt;
&lt;br /&gt;
==set event==&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   add/modify an event in Moodle database (site, course, private ...)&lt;/div&gt;</summary>
		<author><name>Ppollet</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/403/en/index.php?title=Development:Web_services&amp;diff=30790</id>
		<title>Development:Web services</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/403/en/index.php?title=Development:Web_services&amp;diff=30790"/>
		<updated>2007-12-30T10:34:01Z</updated>

		<summary type="html">&lt;p&gt;Ppollet: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page is to decide on a STANDARD list of CORE web service functions that we should support in Moodle (by XMLRPC, REST and SOAP with the option to plug in AMFPHP for Flash/Flex interfaces) as an API for those writing code to work against Moodle.&lt;br /&gt;
&lt;br /&gt;
Please add new functions if there&#039;s functionality you want that isn&#039;t covered (we can refactor/whittle at the end).&lt;br /&gt;
&lt;br /&gt;
==add user==&lt;br /&gt;
I think we should require all data needed for a successful &amp;quot;first login&amp;quot; to Moodle without popping him out the profile page to fill in all missing required data. This may require extra inputs such as city, description ... (unsure of the full list depending of Moodle version ?).&lt;br /&gt;
Also password should be &amp;quot;required&amp;quot; if authentication method is &amp;quot;internal&amp;quot; . &lt;br /&gt;
&lt;br /&gt;
INPUT:&lt;br /&gt;
    firstname&lt;br /&gt;
    lastname&lt;br /&gt;
    email &lt;br /&gt;
    idnumber&lt;br /&gt;
    login &lt;br /&gt;
    authentication method (optional , default= manual ?)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Adds a new user to the user database &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    id or false&lt;br /&gt;
&lt;br /&gt;
==delete user==&lt;br /&gt;
INPUT:&lt;br /&gt;
    idnumber  or &lt;br /&gt;
    email or &lt;br /&gt;
    id or&lt;br /&gt;
    login&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    User is marked as deleted&lt;br /&gt;
    All it&#039;s role assignments are destroyed &lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true/false&lt;br /&gt;
&lt;br /&gt;
==get user==&lt;br /&gt;
INPUT:&lt;br /&gt;
    idnumber  or &lt;br /&gt;
    email or &lt;br /&gt;
    id or&lt;br /&gt;
    login&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   user record with optional fields set (Moodle 1.8 and later) and maybe some fields filtered out (password, email if user said not to discolose it ...) depending of the identity of the &amp;quot;caller&amp;quot; (admin or the user himself) &lt;br /&gt;
OUTPUT:&lt;br /&gt;
    false  or user record &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==add course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    name&lt;br /&gt;
    shortname&lt;br /&gt;
    format (default topics)&lt;br /&gt;
    idnumber &lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Adds a new course to the course table&lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    id or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==delete course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    name OR&lt;br /&gt;
    shortname  OR&lt;br /&gt;
    idnumber OR&lt;br /&gt;
    id&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Deletes a course from the course table&lt;br /&gt;
    What about associated ressources, roles ... &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==get course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    idor  idnumber or shortname&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
     fetch course record with some fields filtered out depending of the &amp;quot;caller&amp;quot; identity (admin, teacher, student ...)&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    false  or course record &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==enrol student to course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    course unique Id (Moodle&#039;s ID or idnumber or shortname)&lt;br /&gt;
    student unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Assign student role to course &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==unenrol student from course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    course unique Id (Moodle&#039;s ID or idnumber or shortname)&lt;br /&gt;
    student unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    remove student role from course &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==assign role to course==&lt;br /&gt;
INPUT:&lt;br /&gt;
   course unique Id (Moodle&#039;s ID or idnumber or shortname)&lt;br /&gt;
   user unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
   role id (teacher, non editing teacher, student (?) ...)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   assign given user a &amp;quot;standard&amp;quot; role to given course   &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==remove role from course==&lt;br /&gt;
INPUT:&lt;br /&gt;
   course unique Id (Moodle&#039;s ID or idnumber or shortname)&lt;br /&gt;
   user unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
   role id (teacher, non editing teacher, student (?) ...)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   remove given user&#039;s &amp;quot;standard&amp;quot; role from given course   &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==get my courses==&lt;br /&gt;
&lt;br /&gt;
INPUT:&lt;br /&gt;
   user unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   return a &amp;quot;list&amp;quot; of course&#039;s id in which given user move given user has some role assigned     &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    &amp;quot;array&amp;quot; of (course id, course shortname, course fullname, role id, role name, course url)&lt;br /&gt;
    or false in case of error (bad user id)&lt;br /&gt;
&lt;br /&gt;
==get last changes in my courses==&lt;br /&gt;
&lt;br /&gt;
INPUT:&lt;br /&gt;
   user unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
   course unique Id (Moodle&#039;s ID ,idnumber or shortname) - optional (default = all my courses)&lt;br /&gt;
   timestamp - optional (default = time of last connexion in every course)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   return a &amp;quot;list&amp;quot; of changes (resource added/modified, new activities, etc.) for courses in which given user has some role assigned - since timestamp or last connexion in given course &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    &amp;quot;array&amp;quot; of (course id, course shortname, course fullname, role id, role name, url of the resource/activity, time of change)&lt;br /&gt;
    or false in case of error (bad user/course id)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==get grades==&lt;br /&gt;
&lt;br /&gt;
INPUT:&lt;br /&gt;
   user unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
   course unique Id (Moodle&#039;s ID ,idnumber or shortname) - optional (default = all my courses)&lt;br /&gt;
   &lt;br /&gt;
OPERATION:&lt;br /&gt;
   return a &amp;quot;list&amp;quot; of grades and statistics for the given student in the given course&lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    &amp;quot;array&amp;quot; of grades records (name,maxgrade,grade,percent,weight,weighted,sortOrder) &lt;br /&gt;
    and &amp;quot;array&amp;quot; of stats (gradeItems,allgrades, points,totalpoints, percent, weight, weighted;)  &lt;br /&gt;
    or false in case of error (bad user/course id or user not in course)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==get groups==&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   return a &amp;quot;list&amp;quot; of group records in a given course (or site ?) &lt;br /&gt;
&lt;br /&gt;
==get group members==&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   return a &amp;quot;list&amp;quot; of ids  for members of a group (within a course or global) &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==enrol to group==&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   add a new member to a group&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==unenrol from group==&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   remove membership from a group&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==get events ==&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   return a &amp;quot;list&amp;quot; of event&#039;s identifiers suitable from the &amp;quot;get event&amp;quot; operation&lt;br /&gt;
&lt;br /&gt;
==get event==&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   return in an &amp;quot;exportable&amp;quot; format (iCal, vCal ...)an event recorded in Moodle database (site, course, private ...)&lt;br /&gt;
&lt;br /&gt;
==set event==&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   add/modify an event in Moodle database (site, course, private ...)&lt;/div&gt;</summary>
		<author><name>Ppollet</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/403/en/index.php?title=Development_talk:Web_services&amp;diff=30789</id>
		<title>Development talk:Web services</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/403/en/index.php?title=Development_talk:Web_services&amp;diff=30789"/>
		<updated>2007-12-30T10:27:38Z</updated>

		<summary type="html">&lt;p&gt;Ppollet: /* the problem of ID of entity to fetch: */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==general remarks about OUTPUT of operations:==&lt;br /&gt;
Is true of false informative enough ?&lt;br /&gt;
Should the API have some sort of &amp;quot;last_error&amp;quot; function giving back more details such as &amp;quot;non existing course, non existing user, duplicate entry ...)&lt;br /&gt;
Shall we consider that affecting a role that already exist or removing role that do not exist as an error (output=false) or not (output=true)&lt;br /&gt;
:yep, agree, I&#039;d result always one well defined $result object, with his status, error code and error msg (and perhaps, the whole original WS request encapsulated for easier debugging).&lt;br /&gt;
:[[User:Eloy Lafuente (stronk7)|Eloy Lafuente (stronk7)]] 19:55, 21 December 2007 (CST)&lt;br /&gt;
I agree but throught the WS we need to be  be carefull with the feedback we give to errors, due to security issues. --[[User:Ludo (Marc Alier)|Ludo (Marc Alier)]] 14:14, 22 December 2007 (CST)&lt;br /&gt;
&lt;br /&gt;
==some WS to be able to... build courses ?==&lt;br /&gt;
Perhpas it would be a great idea to start thinking about some WS functionalities like this:&lt;br /&gt;
&lt;br /&gt;
* add_course, delete_course, reset_course&lt;br /&gt;
* add_section, delete_section, show_section, hide_section&lt;br /&gt;
* add_activity, delete_activity, show_activity, hide_activity&lt;br /&gt;
&lt;br /&gt;
Apart from the WS utility itself: automated creation of courses... it would help (or force, as we prefer), to better encapsulate course/section/modules internals, 100% isolating the creation and configuration from the frontend (forms, WS...). It implies some decisions, like upwards compatibility of old modules (although I think it can be maintained)... and so on, you know.&lt;br /&gt;
&lt;br /&gt;
Just one idea to analyse. But with benefits in the end, IMO.&lt;br /&gt;
[[User:Eloy Lafuente (stronk7)|Eloy Lafuente (stronk7)]] 20:02, 21 December 2007 (CST)&lt;br /&gt;
&lt;br /&gt;
I do agree with this ; this would also allow creation of specific courses, customized for some users, depending of their &amp;quot;performances&amp;quot; in external evaluations methods ; when the ePortfolio API will be finalized in Moodle core&#039;s, accessing the portfolio of any user would be  needed.&lt;br /&gt;
[[User:Patrick Pollet|Patrick Pollet]] 04:21, 30 December 2007 (CST)&lt;br /&gt;
&lt;br /&gt;
==the problem of ID of entity to fetch:==&lt;br /&gt;
In the list of API calls defined in this page, Moodle entity to process (user,course,grade,event ...) is identified by an ID, that is implicitly the Moodle&#039;s internal id field used in the database. This raises a problem since it is very likely that in the &amp;quot;external SIS&amp;quot; talking to Moodle across the Web Service, the entity will be identified by another attribute such as an idNumber (user,course), a short name (course) or even an username (login of user). &lt;br /&gt;
&lt;br /&gt;
So either we must provide :&lt;br /&gt;
&lt;br /&gt;
* extra API calls to convert external identifiers to Moodle&#039;s internal id, such as user_id_from_idnumber, user_id_from_username, course_id_from_shortname ..., at the cost of extra calls   before the real one ; three calls would be needed to enrol student &amp;quot;CS2121212&amp;quot;, to course &amp;quot;JAVA_101&amp;quot;. &lt;br /&gt;
&lt;br /&gt;
* extra API functions such as delete_user_byusername, get_course_by_idnumber , enrol_student_byidnumber_tocourse_byshortname ....&lt;br /&gt;
&lt;br /&gt;
* or add parameters to the current API calls specifiying what identifier we are using  such as delete_user(id,idField) with idField being a string that could be &amp;quot;id&amp;quot;,&amp;quot;idnumber&amp;quot;,&amp;quot;username&amp;quot;,&amp;quot;email&amp;quot; ... or enrol_student(sid,&amp;quot;idnumber&amp;quot;,cid,&amp;quot;shortname&amp;quot;) . This is the approach in the current SOAP implementation (with some calls of the previous type (get_user_byusername()...)   &lt;br /&gt;
&lt;br /&gt;
[[User:Patrick Pollet|Patrick Pollet]] 04:21, 30 December 2007 (CST)&lt;/div&gt;</summary>
		<author><name>Ppollet</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/403/en/index.php?title=Development_talk:Web_services&amp;diff=30788</id>
		<title>Development talk:Web services</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/403/en/index.php?title=Development_talk:Web_services&amp;diff=30788"/>
		<updated>2007-12-30T10:25:52Z</updated>

		<summary type="html">&lt;p&gt;Ppollet: /* the problem of ID of entity to fetch: */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==general remarks about OUTPUT of operations:==&lt;br /&gt;
Is true of false informative enough ?&lt;br /&gt;
Should the API have some sort of &amp;quot;last_error&amp;quot; function giving back more details such as &amp;quot;non existing course, non existing user, duplicate entry ...)&lt;br /&gt;
Shall we consider that affecting a role that already exist or removing role that do not exist as an error (output=false) or not (output=true)&lt;br /&gt;
:yep, agree, I&#039;d result always one well defined $result object, with his status, error code and error msg (and perhaps, the whole original WS request encapsulated for easier debugging).&lt;br /&gt;
:[[User:Eloy Lafuente (stronk7)|Eloy Lafuente (stronk7)]] 19:55, 21 December 2007 (CST)&lt;br /&gt;
I agree but throught the WS we need to be  be carefull with the feedback we give to errors, due to security issues. --[[User:Ludo (Marc Alier)|Ludo (Marc Alier)]] 14:14, 22 December 2007 (CST)&lt;br /&gt;
&lt;br /&gt;
==some WS to be able to... build courses ?==&lt;br /&gt;
Perhpas it would be a great idea to start thinking about some WS functionalities like this:&lt;br /&gt;
&lt;br /&gt;
* add_course, delete_course, reset_course&lt;br /&gt;
* add_section, delete_section, show_section, hide_section&lt;br /&gt;
* add_activity, delete_activity, show_activity, hide_activity&lt;br /&gt;
&lt;br /&gt;
Apart from the WS utility itself: automated creation of courses... it would help (or force, as we prefer), to better encapsulate course/section/modules internals, 100% isolating the creation and configuration from the frontend (forms, WS...). It implies some decisions, like upwards compatibility of old modules (although I think it can be maintained)... and so on, you know.&lt;br /&gt;
&lt;br /&gt;
Just one idea to analyse. But with benefits in the end, IMO.&lt;br /&gt;
[[User:Eloy Lafuente (stronk7)|Eloy Lafuente (stronk7)]] 20:02, 21 December 2007 (CST)&lt;br /&gt;
&lt;br /&gt;
I do agree with this ; this would also allow creation of specific courses, customized for some users, depending of their &amp;quot;performances&amp;quot; in external evaluations methods ; when the ePortfolio API will be finalized in Moodle core&#039;s, accessing the portfolio of any user would be  needed.&lt;br /&gt;
[[User:Patrick Pollet|Patrick Pollet]] 04:21, 30 December 2007 (CST)&lt;br /&gt;
&lt;br /&gt;
==the problem of ID of entity to fetch:==&lt;br /&gt;
In the list of API calls defined in this page, Moodle entity to process (user,course,grade,event ...) is identified by an ID, that is implicitly the Moodle&#039;s internal id field used in the database. This raises a problem since it is very likely that in the &amp;quot;external SIS&amp;quot; talking to Moodle across the Web Service, the entity will be identified by another attribute such as an idNumber (user,course), a short name (course) or even an username (login of user). &lt;br /&gt;
&lt;br /&gt;
So either we must provide :&lt;br /&gt;
&lt;br /&gt;
* extra API calls to convert external identifiers to Moodle&#039;s internal id, such as user_id_from_idnumber, user_id_from_username, course_id_from_shortname ..., at the cost of extra calls   before the real one&lt;br /&gt;
&lt;br /&gt;
* extra API functions such as delete_user_byusername, get_course_by_idnumber , enrol_student_byidnumber_tocourse_byshortname ....&lt;br /&gt;
&lt;br /&gt;
* or add parameters to the current API calls specifiying what identifier we are using  such as delete_user(id,idField) with idField being a string that could be &amp;quot;id&amp;quot;,&amp;quot;idnumber&amp;quot;,&amp;quot;username&amp;quot;,&amp;quot;email&amp;quot; ... or enrol_student(sid,&amp;quot;idnumber&amp;quot;,cid,&amp;quot;shortname&amp;quot;) . This is the approach in the current SOAP implementation (with some calls of the previous type (get_user_byusername()...)   &lt;br /&gt;
&lt;br /&gt;
[[User:Patrick Pollet|Patrick Pollet]] 04:21, 30 December 2007 (CST)&lt;/div&gt;</summary>
		<author><name>Ppollet</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/403/en/index.php?title=Development_talk:Web_services&amp;diff=30787</id>
		<title>Development talk:Web services</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/403/en/index.php?title=Development_talk:Web_services&amp;diff=30787"/>
		<updated>2007-12-30T10:21:50Z</updated>

		<summary type="html">&lt;p&gt;Ppollet: /* the problem of ID of entity to fetch: */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==general remarks about OUTPUT of operations:==&lt;br /&gt;
Is true of false informative enough ?&lt;br /&gt;
Should the API have some sort of &amp;quot;last_error&amp;quot; function giving back more details such as &amp;quot;non existing course, non existing user, duplicate entry ...)&lt;br /&gt;
Shall we consider that affecting a role that already exist or removing role that do not exist as an error (output=false) or not (output=true)&lt;br /&gt;
:yep, agree, I&#039;d result always one well defined $result object, with his status, error code and error msg (and perhaps, the whole original WS request encapsulated for easier debugging).&lt;br /&gt;
:[[User:Eloy Lafuente (stronk7)|Eloy Lafuente (stronk7)]] 19:55, 21 December 2007 (CST)&lt;br /&gt;
I agree but throught the WS we need to be  be carefull with the feedback we give to errors, due to security issues. --[[User:Ludo (Marc Alier)|Ludo (Marc Alier)]] 14:14, 22 December 2007 (CST)&lt;br /&gt;
&lt;br /&gt;
==some WS to be able to... build courses ?==&lt;br /&gt;
Perhpas it would be a great idea to start thinking about some WS functionalities like this:&lt;br /&gt;
&lt;br /&gt;
* add_course, delete_course, reset_course&lt;br /&gt;
* add_section, delete_section, show_section, hide_section&lt;br /&gt;
* add_activity, delete_activity, show_activity, hide_activity&lt;br /&gt;
&lt;br /&gt;
Apart from the WS utility itself: automated creation of courses... it would help (or force, as we prefer), to better encapsulate course/section/modules internals, 100% isolating the creation and configuration from the frontend (forms, WS...). It implies some decisions, like upwards compatibility of old modules (although I think it can be maintained)... and so on, you know.&lt;br /&gt;
&lt;br /&gt;
Just one idea to analyse. But with benefits in the end, IMO.&lt;br /&gt;
[[User:Eloy Lafuente (stronk7)|Eloy Lafuente (stronk7)]] 20:02, 21 December 2007 (CST)&lt;br /&gt;
&lt;br /&gt;
I do agree with this ; this would also allow creation of specific courses, customized for some users, depending of their &amp;quot;performances&amp;quot; in external evaluations methods ; when the ePortfolio API will be finalized in Moodle core&#039;s, accessing the portfolio of any user would be  needed.&lt;br /&gt;
[[User:Patrick Pollet|Patrick Pollet]] 04:21, 30 December 2007 (CST)&lt;br /&gt;
&lt;br /&gt;
==the problem of ID of entity to fetch:==&lt;br /&gt;
In the list of API calls defined in this page, Moodle entity to process (user,course,grade,event ...) is identified by an ID, that is implicitly the Moodle&#039;s internal id field used in the database. This raises a problem since it is very likely that in the &amp;quot;external SIS&amp;quot; talking to Moodle across the Web Service, the entity will be identified by another attribute such as an idNumber (user,course), a short name (course) or even an username (login of user). &lt;br /&gt;
&lt;br /&gt;
So either we must provide :&lt;br /&gt;
&lt;br /&gt;
* extra API calls to convert external identifiers to Moodle&#039;s internal id, such as user_id_from_idnumber, user_id_from_username, course_id_from_shortname ..., at the cost of extra calls   before the really one&lt;br /&gt;
&lt;br /&gt;
* extra API functions such as get_user_byusername, get_course_by_idnumber ...&lt;br /&gt;
&lt;br /&gt;
* or add parameters to the current API calls specifiying what identifier we are using  such as delete_user(id,idField) with idField being a string that could be &amp;quot;id&amp;quot;,&amp;quot;idnumber&amp;quot;,&amp;quot;username&amp;quot;,&amp;quot;email&amp;quot; ..&lt;br /&gt;
&lt;br /&gt;
[[User:Patrick Pollet|Patrick Pollet]] 04:21, 30 December 2007 (CST)&lt;/div&gt;</summary>
		<author><name>Ppollet</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/403/en/index.php?title=Development_talk:Web_services&amp;diff=30786</id>
		<title>Development talk:Web services</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/403/en/index.php?title=Development_talk:Web_services&amp;diff=30786"/>
		<updated>2007-12-30T10:21:25Z</updated>

		<summary type="html">&lt;p&gt;Ppollet: /* some WS to be able to... build courses ? */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==general remarks about OUTPUT of operations:==&lt;br /&gt;
Is true of false informative enough ?&lt;br /&gt;
Should the API have some sort of &amp;quot;last_error&amp;quot; function giving back more details such as &amp;quot;non existing course, non existing user, duplicate entry ...)&lt;br /&gt;
Shall we consider that affecting a role that already exist or removing role that do not exist as an error (output=false) or not (output=true)&lt;br /&gt;
:yep, agree, I&#039;d result always one well defined $result object, with his status, error code and error msg (and perhaps, the whole original WS request encapsulated for easier debugging).&lt;br /&gt;
:[[User:Eloy Lafuente (stronk7)|Eloy Lafuente (stronk7)]] 19:55, 21 December 2007 (CST)&lt;br /&gt;
I agree but throught the WS we need to be  be carefull with the feedback we give to errors, due to security issues. --[[User:Ludo (Marc Alier)|Ludo (Marc Alier)]] 14:14, 22 December 2007 (CST)&lt;br /&gt;
&lt;br /&gt;
==some WS to be able to... build courses ?==&lt;br /&gt;
Perhpas it would be a great idea to start thinking about some WS functionalities like this:&lt;br /&gt;
&lt;br /&gt;
* add_course, delete_course, reset_course&lt;br /&gt;
* add_section, delete_section, show_section, hide_section&lt;br /&gt;
* add_activity, delete_activity, show_activity, hide_activity&lt;br /&gt;
&lt;br /&gt;
Apart from the WS utility itself: automated creation of courses... it would help (or force, as we prefer), to better encapsulate course/section/modules internals, 100% isolating the creation and configuration from the frontend (forms, WS...). It implies some decisions, like upwards compatibility of old modules (although I think it can be maintained)... and so on, you know.&lt;br /&gt;
&lt;br /&gt;
Just one idea to analyse. But with benefits in the end, IMO.&lt;br /&gt;
[[User:Eloy Lafuente (stronk7)|Eloy Lafuente (stronk7)]] 20:02, 21 December 2007 (CST)&lt;br /&gt;
&lt;br /&gt;
I do agree with this ; this would also allow creation of specific courses, customized for some users, depending of their &amp;quot;performances&amp;quot; in external evaluations methods ; when the ePortfolio API will be finalized in Moodle core&#039;s, accessing the portfolio of any user would be  needed.&lt;br /&gt;
[[User:Patrick Pollet|Patrick Pollet]] 04:21, 30 December 2007 (CST)&lt;br /&gt;
&lt;br /&gt;
==the problem of ID of entity to fetch:==&lt;br /&gt;
In the list of API calls defined in this page, Moodle entity to process (user,course,grade,event ...) is identified by an ID, that is implicitly the Moodle&#039;s internal id field used in the database. This raises a problem since it is very likely that in the &amp;quot;external SIS&amp;quot; talking to Moodle across the Web Service, the entity will be identified by another attribute such as an idNumber (user,course), a short name (course) or even an username (login of user). &lt;br /&gt;
&lt;br /&gt;
So either we must provide :&lt;br /&gt;
&lt;br /&gt;
* extra API calls to convert external identifiers to Moodle&#039;s internal id, such as user_id_from_idnumber, user_id_from_username, course_id_from_shortname ..., at the cost of extra calls   before the really one&lt;br /&gt;
&lt;br /&gt;
* extra API functions such as get_user_byusername, get_course_by_idnumber ...&lt;br /&gt;
&lt;br /&gt;
* or add parameters to the current API calls specifiying what identifier we are using  such as delete_user(id,idField) with idField being a string that could be &amp;quot;id&amp;quot;,&amp;quot;idnumber&amp;quot;,&amp;quot;username&amp;quot;,&amp;quot;email&amp;quot; ..&lt;/div&gt;</summary>
		<author><name>Ppollet</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/403/en/index.php?title=Development_talk:Web_services&amp;diff=30785</id>
		<title>Development talk:Web services</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/403/en/index.php?title=Development_talk:Web_services&amp;diff=30785"/>
		<updated>2007-12-30T10:17:52Z</updated>

		<summary type="html">&lt;p&gt;Ppollet: question of identifier for Moodle&amp;#039;s entity&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==general remarks about OUTPUT of operations:==&lt;br /&gt;
Is true of false informative enough ?&lt;br /&gt;
Should the API have some sort of &amp;quot;last_error&amp;quot; function giving back more details such as &amp;quot;non existing course, non existing user, duplicate entry ...)&lt;br /&gt;
Shall we consider that affecting a role that already exist or removing role that do not exist as an error (output=false) or not (output=true)&lt;br /&gt;
:yep, agree, I&#039;d result always one well defined $result object, with his status, error code and error msg (and perhaps, the whole original WS request encapsulated for easier debugging).&lt;br /&gt;
:[[User:Eloy Lafuente (stronk7)|Eloy Lafuente (stronk7)]] 19:55, 21 December 2007 (CST)&lt;br /&gt;
I agree but throught the WS we need to be  be carefull with the feedback we give to errors, due to security issues. --[[User:Ludo (Marc Alier)|Ludo (Marc Alier)]] 14:14, 22 December 2007 (CST)&lt;br /&gt;
&lt;br /&gt;
==some WS to be able to... build courses ?==&lt;br /&gt;
Perhpas it would be a great idea to start thinking about some WS functionalities like this:&lt;br /&gt;
&lt;br /&gt;
* add_course, delete_course, reset_course&lt;br /&gt;
* add_section, delete_section, show_section, hide_section&lt;br /&gt;
* add_activity, delete_activity, show_activity, hide_activity&lt;br /&gt;
&lt;br /&gt;
Apart from the WS utility itself: automated creation of courses... it would help (or force, as we prefer), to better encapsulate course/section/modules internals, 100% isolating the creation and configuration from the frontend (forms, WS...). It implies some decisions, like upwards compatibility of old modules (although I think it can be maintained)... and so on, you know.&lt;br /&gt;
&lt;br /&gt;
Just one idea to analyse. But with benefits in the end, IMO.&lt;br /&gt;
[[User:Eloy Lafuente (stronk7)|Eloy Lafuente (stronk7)]] 20:02, 21 December 2007 (CST)&lt;br /&gt;
&lt;br /&gt;
I do agree with this ; this would also allow creation of specific courses, customized for some users, depending of their &amp;quot;performances&amp;quot; in external evaluations methods ; when the ePortfolio API will be finalized in Moodle core&#039;s, accessing the portfolio of any user would be  needed.&lt;br /&gt;
&lt;br /&gt;
==the problem of ID of entity to fetch:==&lt;br /&gt;
In the list of API calls defined in this page, Moodle entity to process (user,course,grade,event ...) is identified by an ID, that is implicitly the Moodle&#039;s internal id field used in the database. This raises a problem since it is very likely that in the &amp;quot;external SIS&amp;quot; talking to Moodle across the Web Service, the entity will be identified by another attribute such as an idNumber (user,course), a short name (course) or even an username (login of user). &lt;br /&gt;
&lt;br /&gt;
So either we must provide :&lt;br /&gt;
&lt;br /&gt;
* extra API calls to convert external identifiers to Moodle&#039;s internal id, such as user_id_from_idnumber, user_id_from_username, course_id_from_shortname ..., at the cost of extra calls   before the really one&lt;br /&gt;
&lt;br /&gt;
* extra API functions such as get_user_byusername, get_course_by_idnumber ...&lt;br /&gt;
&lt;br /&gt;
* or add parameters to the current API calls specifiying what identifier we are using  such as delete_user(id,idField) with idField being a string that could be &amp;quot;id&amp;quot;,&amp;quot;idnumber&amp;quot;,&amp;quot;username&amp;quot;,&amp;quot;email&amp;quot; ..&lt;/div&gt;</summary>
		<author><name>Ppollet</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/403/en/index.php?title=Development:Web_services&amp;diff=30569</id>
		<title>Development:Web services</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/403/en/index.php?title=Development:Web_services&amp;diff=30569"/>
		<updated>2007-12-21T12:17:57Z</updated>

		<summary type="html">&lt;p&gt;Ppollet: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page is to decide on a STANDARD list of CORE web service functions that we should support in Moodle (by XMLRPC, REST and SOAP) as an API for those writing code to work against Moodle.&lt;br /&gt;
&lt;br /&gt;
Please add new functions if there&#039;s functionality you want that isn&#039;t covered (we can refactor/whittle at the end).&lt;br /&gt;
&lt;br /&gt;
==add user==&lt;br /&gt;
I think we should require all data needed for a successful &amp;quot;first login&amp;quot; to Moodle without popping him out the profile page to fill in all missing required data. This may require extra inputs such as city, description ... (unsure of the full list depending of Moodle version ?).&lt;br /&gt;
Also password should be &amp;quot;required&amp;quot; if authentication method is &amp;quot;internal&amp;quot; . &lt;br /&gt;
&lt;br /&gt;
INPUT:&lt;br /&gt;
    firstname&lt;br /&gt;
    lastname&lt;br /&gt;
    email &lt;br /&gt;
    idnumber&lt;br /&gt;
    login &lt;br /&gt;
    authentication method (optional , default= manual ?)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Adds a new user to the user database &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    id or false&lt;br /&gt;
&lt;br /&gt;
==delete user==&lt;br /&gt;
INPUT:&lt;br /&gt;
    idnumber  or &lt;br /&gt;
    email or &lt;br /&gt;
    id or&lt;br /&gt;
    login&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    User is marked as deleted&lt;br /&gt;
    All it&#039;s role assignments are destroyed &lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true/false&lt;br /&gt;
&lt;br /&gt;
==add course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    name&lt;br /&gt;
    shortname&lt;br /&gt;
    format (default topics)&lt;br /&gt;
    idnumber &lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Adds a new course to the course table&lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    id or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==delete course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    name OR&lt;br /&gt;
    shortname  OR&lt;br /&gt;
    idnumber OR&lt;br /&gt;
    id&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Deletes a course from the course table&lt;br /&gt;
    What about associated ressources, roles ... &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
==enrol student to course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    course unique Id (Moodle&#039;s ID or idnumber or shortname)&lt;br /&gt;
    student unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Assign student role to course &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==unenrol student from course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    course unique Id (Moodle&#039;s ID or idnumber or shortname)&lt;br /&gt;
    student unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    remove student role from course &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==assign role to course==&lt;br /&gt;
INPUT:&lt;br /&gt;
   course unique Id (Moodle&#039;s ID or idnumber or shortname)&lt;br /&gt;
   user unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
   role id (teacher, non editing teacher, student (?) ...)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   assign given user a &amp;quot;standard&amp;quot; role to given course   &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==remove role from course==&lt;br /&gt;
INPUT:&lt;br /&gt;
   course unique Id (Moodle&#039;s ID or idnumber or shortname)&lt;br /&gt;
   user unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
   role id (teacher, non editing teacher, student (?) ...)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   remove given user&#039;s &amp;quot;standard&amp;quot; role from given course   &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==get my courses==&lt;br /&gt;
&lt;br /&gt;
INPUT:&lt;br /&gt;
   user unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   return a &amp;quot;list&amp;quot; of course&#039;s id in which given user move given user has some role assigned     &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    &amp;quot;array&amp;quot; of (course id, course shortname, course fullname, role id, role name, course url)&lt;br /&gt;
    or false in case of error (bad user id)&lt;br /&gt;
&lt;br /&gt;
==get last changes in my courses==&lt;br /&gt;
&lt;br /&gt;
INPUT:&lt;br /&gt;
   user unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
   course unique Id (Moodle&#039;s ID ,idnumber or shortname) - optional (default = all my courses)&lt;br /&gt;
   timestamp - optional (default = time of last connexion in every course)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   return a &amp;quot;list&amp;quot; of changes (resource added/modified, new activities, etc.) for courses in which given user has some role assigned - since timestamp or last connexion in given course &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    &amp;quot;array&amp;quot; of (course id, course shortname, course fullname, role id, role name, url of the resource/activity, time of change)&lt;br /&gt;
    or false in case of error (bad user/course id)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==get grades==&lt;br /&gt;
&lt;br /&gt;
INPUT:&lt;br /&gt;
   user unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
   course unique Id (Moodle&#039;s ID ,idnumber or shortname) - optional (default = all my courses)&lt;br /&gt;
   &lt;br /&gt;
OPERATION:&lt;br /&gt;
   return a &amp;quot;list&amp;quot; of grades and statistics for the given student in the given course&lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    &amp;quot;array&amp;quot; of grades records (name,maxgrade,grade,percent,weight,weighted,sortOrder) &lt;br /&gt;
    and &amp;quot;array&amp;quot; of stats (gradeItems,allgrades, points,totalpoints, percent, weight, weighted;)  &lt;br /&gt;
    or false in case of error (bad user/course id or user not in course)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==get groups==&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   return a &amp;quot;list&amp;quot; of group records in a given course (or site ?) &lt;br /&gt;
&lt;br /&gt;
==get group members==&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   return a &amp;quot;list&amp;quot; of ids  for members of a group (within a course or global) &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==enrol to group==&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   add a new member to a group&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==unenrol from group==&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   remove membership from a group&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==get events ==&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   return a &amp;quot;list&amp;quot; of event&#039;s identifiers suitable from the &amp;quot;get event&amp;quot; operation&lt;br /&gt;
&lt;br /&gt;
==get event==&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   return in an &amp;quot;exportable&amp;quot; format (iCal, vCal ...)an event recorded in Moodle database (site, course, private ...)&lt;br /&gt;
&lt;br /&gt;
==set event==&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   add/modify an event in Moodle database (site, course, private ...)&lt;/div&gt;</summary>
		<author><name>Ppollet</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/403/en/index.php?title=Development:Web_services&amp;diff=30568</id>
		<title>Development:Web services</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/403/en/index.php?title=Development:Web_services&amp;diff=30568"/>
		<updated>2007-12-21T12:16:30Z</updated>

		<summary type="html">&lt;p&gt;Ppollet: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page is to decide on a STANDARD list of CORE web service functions that we should support in Moodle (by XMLRPC, REST and SOAP) as an API for those writing code to work against Moodle.&lt;br /&gt;
&lt;br /&gt;
Please add new functions if there&#039;s functionality you want that isn&#039;t covered (we can refactor/whittle at the end).&lt;br /&gt;
&lt;br /&gt;
==add user==&lt;br /&gt;
I think we should require all data needed for a successful &amp;quot;first login&amp;quot; to Moodle without popping him out the profile page to fill in all missing required data. This may require extra inputs such as city, description ... (unsure of the full list depending of Moodle version ?).&lt;br /&gt;
Also password should be &amp;quot;required&amp;quot; if authentication method is &amp;quot;internal&amp;quot; . &lt;br /&gt;
&lt;br /&gt;
INPUT:&lt;br /&gt;
    firstname&lt;br /&gt;
    lastname&lt;br /&gt;
    email &lt;br /&gt;
    idnumber&lt;br /&gt;
    login &lt;br /&gt;
    authentication method (optional , default= manual ?)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Adds a new user to the user database &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    id or false&lt;br /&gt;
&lt;br /&gt;
==delete user==&lt;br /&gt;
INPUT:&lt;br /&gt;
    idnumber  or &lt;br /&gt;
    email or &lt;br /&gt;
    id or&lt;br /&gt;
    login&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    User is marked as deleted&lt;br /&gt;
    All it&#039;s role assignments are destroyed &lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true/false&lt;br /&gt;
&lt;br /&gt;
==add course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    name&lt;br /&gt;
    shortname&lt;br /&gt;
    format (default topics)&lt;br /&gt;
    idnumber &lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Adds a new course to the course table&lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    id or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==delete course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    name OR&lt;br /&gt;
    shortname  OR&lt;br /&gt;
    idnumber OR&lt;br /&gt;
    id&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Deletes a course from the course table&lt;br /&gt;
    What about associated ressources, roles ... &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
==enrol student to course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    course unique Id (Moodle&#039;s ID or idnumber or shortname)&lt;br /&gt;
    student unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Assign student role to course &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==unenrol student from course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    course unique Id (Moodle&#039;s ID or idnumber or shortname)&lt;br /&gt;
    student unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    remove student role from course &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==assign role to course==&lt;br /&gt;
INPUT:&lt;br /&gt;
   course unique Id (Moodle&#039;s ID or idnumber or shortname)&lt;br /&gt;
   user unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
   role id (teacher, non editing teacher, student (?) ...)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   assign given user a &amp;quot;standard&amp;quot; role to given course   &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==remove role from course==&lt;br /&gt;
INPUT:&lt;br /&gt;
   course unique Id (Moodle&#039;s ID or idnumber or shortname)&lt;br /&gt;
   user unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
   role id (teacher, non editing teacher, student (?) ...)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   remove given user&#039;s &amp;quot;standard&amp;quot; role from given course   &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==get my courses==&lt;br /&gt;
&lt;br /&gt;
INPUT:&lt;br /&gt;
   user unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   return a &amp;quot;list&amp;quot; of course&#039;s id in which given user move given user has some role assigned     &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    &amp;quot;array&amp;quot; of (course id, course shortname, course fullname, role id, role name, course url)&lt;br /&gt;
    or false in case of error (bad user id)&lt;br /&gt;
&lt;br /&gt;
==get last changes in my courses==&lt;br /&gt;
&lt;br /&gt;
INPUT:&lt;br /&gt;
   user unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
   course unique Id (Moodle&#039;s ID ,idnumber or shortname) - optional (default = all my courses)&lt;br /&gt;
   timestamp - optional (default = time of last connexion in every course)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   return a &amp;quot;list&amp;quot; of changes (resource added/modified, new activities, etc.) for courses in which given user has some role assigned - since timestamp or last connexion in given course &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    &amp;quot;array&amp;quot; of (course id, course shortname, course fullname, role id, role name, url of the resource/activity, time of change)&lt;br /&gt;
    or false in case of error (bad user/course id)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==get grades==&lt;br /&gt;
&lt;br /&gt;
INPUT:&lt;br /&gt;
   user unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
   course unique Id (Moodle&#039;s ID ,idnumber or shortname) - optional (default = all my courses)&lt;br /&gt;
   &lt;br /&gt;
OPERATION:&lt;br /&gt;
   return a &amp;quot;list&amp;quot; of grades and statistics for the given student in the given course&lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    &amp;quot;array&amp;quot; of grades records (name,maxgrade,grade,percent,weight,weighted,sortOrder) &lt;br /&gt;
    and &amp;quot;array&amp;quot; of stats (gradeItems,allgrades, points,totalpoints, percent, weight, weighted;)  &lt;br /&gt;
or false in case of error (bad user/course id or user not in course)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==get groups==&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   return a &amp;quot;list&amp;quot; of group records in a given course (or site ?) &lt;br /&gt;
&lt;br /&gt;
==get group members==&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   return a &amp;quot;list&amp;quot; of ids  for members of a group (within a course or global) &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==enrol to group==&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   add a new member to a group&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==unenrol from group==&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   remove membership from a group&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==get events ==&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   return a &amp;quot;list&amp;quot; of event&#039;s identifiers suitable from the &amp;quot;get event&amp;quot; operation&lt;br /&gt;
&lt;br /&gt;
==get event==&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   return in an &amp;quot;exportable&amp;quot; format (iCal, vCal ...)an event recorded in Moodle database (site, course, private ...)&lt;br /&gt;
&lt;br /&gt;
==set event==&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   add/modify an event in Moodle database (site, course, private ...)&lt;/div&gt;</summary>
		<author><name>Ppollet</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/403/en/index.php?title=Development:Web_services&amp;diff=30567</id>
		<title>Development:Web services</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/403/en/index.php?title=Development:Web_services&amp;diff=30567"/>
		<updated>2007-12-21T12:08:08Z</updated>

		<summary type="html">&lt;p&gt;Ppollet: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page is to decide on a STANDARD list of CORE web service functions that we should support in Moodle (by XMLRPC, REST and SOAP) as an API for those writing code to work against Moodle.&lt;br /&gt;
&lt;br /&gt;
Please add new functions if there&#039;s functionality you want that isn&#039;t covered (we can refactor/whittle at the end).&lt;br /&gt;
&lt;br /&gt;
==add user==&lt;br /&gt;
I think we should require all data needed for a successful &amp;quot;first login&amp;quot; to Moodle without popping him out the profile page to fill in all missing required data. This may require extra inputs such as city, description ... (unsure of the full list depending of Moodle version ?).&lt;br /&gt;
Also password should be &amp;quot;required&amp;quot; if authentication method is &amp;quot;internal&amp;quot; . &lt;br /&gt;
&lt;br /&gt;
INPUT:&lt;br /&gt;
    firstname&lt;br /&gt;
    lastname&lt;br /&gt;
    email &lt;br /&gt;
    idnumber&lt;br /&gt;
    login &lt;br /&gt;
    authentication method (optional , default= manual ?)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Adds a new user to the user database &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    id or false&lt;br /&gt;
&lt;br /&gt;
==delete user==&lt;br /&gt;
INPUT:&lt;br /&gt;
    idnumber  or &lt;br /&gt;
    email or &lt;br /&gt;
    id or&lt;br /&gt;
    login&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    User is marked as deleted&lt;br /&gt;
    All it&#039;s role assignments are destroyed &lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true/false&lt;br /&gt;
&lt;br /&gt;
==add course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    name&lt;br /&gt;
    shortname&lt;br /&gt;
    format (default topics)&lt;br /&gt;
    idnumber &lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Adds a new course to the course table&lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    id or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==delete course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    name OR&lt;br /&gt;
    shortname  OR&lt;br /&gt;
    idnumber OR&lt;br /&gt;
    id&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Deletes a course from the course table&lt;br /&gt;
    What about associated ressources, roles ... &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
==enrol student to course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    course unique Id (Moodle&#039;s ID or idnumber or shortname)&lt;br /&gt;
    student unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Assign student role to course &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==unenrol student from course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    course unique Id (Moodle&#039;s ID or idnumber or shortname)&lt;br /&gt;
    student unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    remove student role from course &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==assign role to course==&lt;br /&gt;
INPUT:&lt;br /&gt;
   course unique Id (Moodle&#039;s ID or idnumber or shortname)&lt;br /&gt;
   user unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
   role id (teacher, non editing teacher, student (?) ...)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   assign given user a &amp;quot;standard&amp;quot; role to given course   &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==remove role from course==&lt;br /&gt;
INPUT:&lt;br /&gt;
   course unique Id (Moodle&#039;s ID or idnumber or shortname)&lt;br /&gt;
   user unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
   role id (teacher, non editing teacher, student (?) ...)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   remove given user&#039;s &amp;quot;standard&amp;quot; role from given course   &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==get my courses==&lt;br /&gt;
&lt;br /&gt;
INPUT:&lt;br /&gt;
   user unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   return a &amp;quot;list&amp;quot; of course&#039;s id in which given user move given user has some role assigned     &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    &amp;quot;array&amp;quot; of (course id, course shortname, course fullname, role id, role name, course url)&lt;br /&gt;
    or false in case of error (bad user id)&lt;br /&gt;
&lt;br /&gt;
==get last changes in my courses==&lt;br /&gt;
&lt;br /&gt;
INPUT:&lt;br /&gt;
   user unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
   course unique Id (Moodle&#039;s ID ,idnumber or shortname) - optional (default = all my courses)&lt;br /&gt;
   timestamp - optional (default = time of last connexion in every course)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   return a &amp;quot;list&amp;quot; of changes (resource added/modified, new activities, etc.) for courses in which given user has some role assigned - since timestamp or last connexion in given course &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    &amp;quot;array&amp;quot; of (course id, course shortname, course fullname, role id, role name, url of the resource/activity, time of change)&lt;br /&gt;
    or false in case of error (bad user/course id)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==get grades==&lt;br /&gt;
&lt;br /&gt;
INPUT:&lt;br /&gt;
   user unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
   course unique Id (Moodle&#039;s ID ,idnumber or shortname) - optional (default = all my courses)&lt;br /&gt;
   &lt;br /&gt;
OPERATION:&lt;br /&gt;
   return a &amp;quot;list&amp;quot; of grades and statistics for the given student in the given course&lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    &amp;quot;array&amp;quot; of grades records (name,maxgrade,grade,percent,weight,weighted,sortOrder) &lt;br /&gt;
    and &amp;quot;array&amp;quot; of stats (gradeItems,allgrades, points,totalpoints, percent, weight, weighted;)  &lt;br /&gt;
or false in case of error (bad user/course id or user not in course)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==get groups==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==get group members==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==enrol to group==&lt;br /&gt;
&lt;br /&gt;
==unenrol from group==&lt;/div&gt;</summary>
		<author><name>Ppollet</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/403/en/index.php?title=Development:Web_services&amp;diff=30566</id>
		<title>Development:Web services</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/403/en/index.php?title=Development:Web_services&amp;diff=30566"/>
		<updated>2007-12-21T12:05:24Z</updated>

		<summary type="html">&lt;p&gt;Ppollet: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page is to decide on a STANDARD list of CORE web service functions that we should support in Moodle (by XMLRPC, REST and SOAP) as an API for those writing code to work against Moodle.&lt;br /&gt;
&lt;br /&gt;
Please add new functions if there&#039;s functionality you want that isn&#039;t covered (we can refactor/whittle at the end).&lt;br /&gt;
&lt;br /&gt;
==add user==&lt;br /&gt;
I think we should require all data needed for a successful &amp;quot;first login&amp;quot; to Moodle without popping him out the profile page to fill in all missing required data. This may require extra inputs such as city, description ... (unsure of the full list depending of Moodle version ?).&lt;br /&gt;
Also password should be &amp;quot;required&amp;quot; if authentication method is &amp;quot;internal&amp;quot; . &lt;br /&gt;
&lt;br /&gt;
INPUT:&lt;br /&gt;
    firstname&lt;br /&gt;
    lastname&lt;br /&gt;
    email &lt;br /&gt;
    idnumber&lt;br /&gt;
    login &lt;br /&gt;
    authentication method (optional , default= manual ?)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Adds a new user to the user database &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    id or false&lt;br /&gt;
&lt;br /&gt;
==delete user==&lt;br /&gt;
INPUT:&lt;br /&gt;
    idnumber  or &lt;br /&gt;
    email or &lt;br /&gt;
    id or&lt;br /&gt;
    login&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    User is marked as deleted&lt;br /&gt;
    All it&#039;s role assignments are destroyed &lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true/false&lt;br /&gt;
&lt;br /&gt;
==add course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    name&lt;br /&gt;
    shortname&lt;br /&gt;
    format (default topics)&lt;br /&gt;
    idnumber &lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Adds a new course to the course table&lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    id or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==delete course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    name OR&lt;br /&gt;
    shortname  OR&lt;br /&gt;
    idnumber OR&lt;br /&gt;
    id&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Deletes a course from the course table&lt;br /&gt;
    What about associated ressources, roles ... &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
==enrol student to course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    course unique Id (Moodle&#039;s ID or idnumber or shortname)&lt;br /&gt;
    student unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Assign student role to course &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==unenrol student from course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    course unique Id (Moodle&#039;s ID or idnumber or shortname)&lt;br /&gt;
    student unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    remove student role from course &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==assign role to course==&lt;br /&gt;
INPUT:&lt;br /&gt;
   course unique Id (Moodle&#039;s ID or idnumber or shortname)&lt;br /&gt;
   user unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
   role id (teacher, non editing teacher, student (?) ...)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   assign given user a &amp;quot;standard&amp;quot; role to given course   &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==remove role from course==&lt;br /&gt;
INPUT:&lt;br /&gt;
   course unique Id (Moodle&#039;s ID or idnumber or shortname)&lt;br /&gt;
   user unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
   role id (teacher, non editing teacher, student (?) ...)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   remove given user&#039;s &amp;quot;standard&amp;quot; role from given course   &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==get my courses==&lt;br /&gt;
&lt;br /&gt;
INPUT:&lt;br /&gt;
   user unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   return a &amp;quot;list&amp;quot; of course&#039;s id in which given user move given user has some role assigned     &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    &amp;quot;array&amp;quot; of (course id, course shortname, course fullname, role id, role name, course url)&lt;br /&gt;
    or false in case of error (bad user id)&lt;br /&gt;
&lt;br /&gt;
==get last changes in my courses==&lt;br /&gt;
&lt;br /&gt;
INPUT:&lt;br /&gt;
   user unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
   course unique Id (Moodle&#039;s ID ,idnumber or shortname) - optional (default = all my courses)&lt;br /&gt;
   timestamp - optional (default = time of last connexion in every course)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   return a &amp;quot;list&amp;quot; of changes (resource added/modified, new activities, etc.) for courses in which given user has some role assigned - since timestamp or last connexion in given course &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    &amp;quot;array&amp;quot; of (course id, course shortname, course fullname, role id, role name, url of the resource/activity, time of change)&lt;br /&gt;
    or false in case of error (bad user/course id)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==get grades==&lt;br /&gt;
&lt;br /&gt;
INPUT:&lt;br /&gt;
   user unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
   course unique Id (Moodle&#039;s ID ,idnumber or shortname) - optional (default = all my courses)&lt;br /&gt;
   &lt;br /&gt;
OPERATION:&lt;br /&gt;
   return a &amp;quot;list&amp;quot; of grades and statistics for the given student in the given course&lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    &amp;quot;array&amp;quot; of grades records (name,maxgrade,grade,percent,weight,weighted,sortOrder) &lt;br /&gt;
    and &amp;quot;array&amp;quot; of stats (gradeItems,allgrades, points,totalpoints, percent, weight, weighted;)  &lt;br /&gt;
or false in case of error (bad user/course id or user not in course)&lt;/div&gt;</summary>
		<author><name>Ppollet</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/403/en/index.php?title=Development:Web_services&amp;diff=28665</id>
		<title>Development:Web services</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/403/en/index.php?title=Development:Web_services&amp;diff=28665"/>
		<updated>2007-11-13T12:16:43Z</updated>

		<summary type="html">&lt;p&gt;Ppollet: /* delete course */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page is to decide on a STANDARD list of CORE web service functions that we should support in Moodle (by XMLRPC, REST and SOAP) as an API for those writing code to work against Moodle.&lt;br /&gt;
&lt;br /&gt;
Please add new functions if there&#039;s functionality you want that isn&#039;t covered (we can refactor/whittle at the end).&lt;br /&gt;
&lt;br /&gt;
==add user==&lt;br /&gt;
I think we should require all data needed for a successful &amp;quot;first login&amp;quot; to Moodle without popping him out the profile page to fill in all missing required data. This may require extra inputs such as city, description ... (unsure of the full list depending of Moodle version ?).&lt;br /&gt;
Also password should be &amp;quot;required&amp;quot; if authentication method is &amp;quot;internal&amp;quot; . &lt;br /&gt;
&lt;br /&gt;
INPUT:&lt;br /&gt;
    firstname&lt;br /&gt;
    lastname&lt;br /&gt;
    email &lt;br /&gt;
    idnumber&lt;br /&gt;
    login &lt;br /&gt;
    authentication method (optional , default= manual ?)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Adds a new user to the user database &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    id or false&lt;br /&gt;
&lt;br /&gt;
==delete user==&lt;br /&gt;
INPUT:&lt;br /&gt;
    idnumber  or &lt;br /&gt;
    email or &lt;br /&gt;
    id or&lt;br /&gt;
    login&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    User is marked as deleted&lt;br /&gt;
    All it&#039;s role assignments are destroyed &lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true/false&lt;br /&gt;
&lt;br /&gt;
==add course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    name&lt;br /&gt;
    shortname&lt;br /&gt;
    format (default topics)&lt;br /&gt;
    idnumber &lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Adds a new course to the course table&lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    id or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==delete course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    name OR&lt;br /&gt;
    shortname  OR&lt;br /&gt;
    idnumber OR&lt;br /&gt;
    id&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Deletes a course from the course table&lt;br /&gt;
    What about associated ressources, roles ... &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
==enrol student to course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    course unique Id (Moodle&#039;s ID or idnumber or shortname)&lt;br /&gt;
    student unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Assign student role to course &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==unenrol student from course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    course unique Id (Moodle&#039;s ID or idnumber or shortname)&lt;br /&gt;
    student unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    remove student role from course &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==assign role to course==&lt;br /&gt;
INPUT:&lt;br /&gt;
   course unique Id (Moodle&#039;s ID or idnumber or shortname)&lt;br /&gt;
   user unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
   role id (teacher, non editing teacher, student (?) ...)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   assign given user a &amp;quot;standard&amp;quot; role to given course   &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==remove role from course==&lt;br /&gt;
INPUT:&lt;br /&gt;
   course unique Id (Moodle&#039;s ID or idnumber or shortname)&lt;br /&gt;
   user unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
   role id (teacher, non editing teacher, student (?) ...)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   remove given user&#039;s &amp;quot;standard&amp;quot; role from given course   &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==get my courses==&lt;br /&gt;
&lt;br /&gt;
INPUT:&lt;br /&gt;
   user unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   return a &amp;quot;list&amp;quot; of course&#039;s id in which given user move given user has some role assigned     &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    &amp;quot;array&amp;quot; of (course id, role id)&lt;br /&gt;
    or false in case of error (bad user id)&lt;/div&gt;</summary>
		<author><name>Ppollet</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/403/en/index.php?title=Development:Web_services&amp;diff=28663</id>
		<title>Development:Web services</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/403/en/index.php?title=Development:Web_services&amp;diff=28663"/>
		<updated>2007-11-13T12:13:54Z</updated>

		<summary type="html">&lt;p&gt;Ppollet: /* get my courses */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page is to decide on a STANDARD list of CORE web service functions that we should support in Moodle (by XMLRPC, REST and SOAP) as an API for those writing code to work against Moodle.&lt;br /&gt;
&lt;br /&gt;
Please add new functions if there&#039;s functionality you want that isn&#039;t covered (we can refactor/whittle at the end).&lt;br /&gt;
&lt;br /&gt;
==add user==&lt;br /&gt;
I think we should require all data needed for a successful &amp;quot;first login&amp;quot; to Moodle without popping him out the profile page to fill in all missing required data. This may require extra inputs such as city, description ... (unsure of the full list depending of Moodle version ?).&lt;br /&gt;
Also password should be &amp;quot;required&amp;quot; if authentication method is &amp;quot;internal&amp;quot; . &lt;br /&gt;
&lt;br /&gt;
INPUT:&lt;br /&gt;
    firstname&lt;br /&gt;
    lastname&lt;br /&gt;
    email &lt;br /&gt;
    idnumber&lt;br /&gt;
    login &lt;br /&gt;
    authentication method (optional , default= manual ?)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Adds a new user to the user database &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    id or false&lt;br /&gt;
&lt;br /&gt;
==delete user==&lt;br /&gt;
INPUT:&lt;br /&gt;
    idnumber  or &lt;br /&gt;
    email or &lt;br /&gt;
    id or&lt;br /&gt;
    login&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    User is marked as deleted&lt;br /&gt;
    All it&#039;s role assignments are destroyed &lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true/false&lt;br /&gt;
&lt;br /&gt;
==add course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    name&lt;br /&gt;
    shortname&lt;br /&gt;
    format (default topics)&lt;br /&gt;
    idnumber &lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Adds a new course to the course table&lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    id or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==delete course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    name OR&lt;br /&gt;
    shortname  OR&lt;br /&gt;
    idnumber OR&lt;br /&gt;
    id&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Deletes a course from the course table&lt;br /&gt;
    &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==enrol student to course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    course unique Id (Moodle&#039;s ID or idnumber or shortname)&lt;br /&gt;
    student unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Assign student role to course &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==unenrol student from course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    course unique Id (Moodle&#039;s ID or idnumber or shortname)&lt;br /&gt;
    student unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    remove student role from course &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==assign role to course==&lt;br /&gt;
INPUT:&lt;br /&gt;
   course unique Id (Moodle&#039;s ID or idnumber or shortname)&lt;br /&gt;
   user unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
   role id (teacher, non editing teacher, student (?) ...)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   assign given user a &amp;quot;standard&amp;quot; role to given course   &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==remove role from course==&lt;br /&gt;
INPUT:&lt;br /&gt;
   course unique Id (Moodle&#039;s ID or idnumber or shortname)&lt;br /&gt;
   user unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
   role id (teacher, non editing teacher, student (?) ...)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   remove given user&#039;s &amp;quot;standard&amp;quot; role from given course   &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==get my courses==&lt;br /&gt;
&lt;br /&gt;
INPUT:&lt;br /&gt;
   user unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   return a &amp;quot;list&amp;quot; of course&#039;s id in which given user move given user has some role assigned     &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    &amp;quot;array&amp;quot; of (course id, role id)&lt;br /&gt;
    or false in case of error (bad user id)&lt;/div&gt;</summary>
		<author><name>Ppollet</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/403/en/index.php?title=Development:Web_services&amp;diff=28658</id>
		<title>Development:Web services</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/403/en/index.php?title=Development:Web_services&amp;diff=28658"/>
		<updated>2007-11-13T10:35:42Z</updated>

		<summary type="html">&lt;p&gt;Ppollet: /* remove role from course */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page is to decide on a STANDARD list of CORE web service functions that we should support in Moodle (by XMLRPC, REST and SOAP) as an API for those writing code to work against Moodle.&lt;br /&gt;
&lt;br /&gt;
Please add new functions if there&#039;s functionality you want that isn&#039;t covered (we can refactor/whittle at the end).&lt;br /&gt;
&lt;br /&gt;
==add user==&lt;br /&gt;
I think we should require all data needed for a successful &amp;quot;first login&amp;quot; to Moodle without popping him out the profile page to fill in all missing required data. This may require extra inputs such as city, description ... (unsure of the full list depending of Moodle version ?).&lt;br /&gt;
Also password should be &amp;quot;required&amp;quot; if authentication method is &amp;quot;internal&amp;quot; . &lt;br /&gt;
&lt;br /&gt;
INPUT:&lt;br /&gt;
    firstname&lt;br /&gt;
    lastname&lt;br /&gt;
    email &lt;br /&gt;
    idnumber&lt;br /&gt;
    login &lt;br /&gt;
    authentication method (optional , default= manual ?)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Adds a new user to the user database &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    id or false&lt;br /&gt;
&lt;br /&gt;
==delete user==&lt;br /&gt;
INPUT:&lt;br /&gt;
    idnumber  or &lt;br /&gt;
    email or &lt;br /&gt;
    id or&lt;br /&gt;
    login&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    User is marked as deleted&lt;br /&gt;
    All it&#039;s role assignments are destroyed &lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true/false&lt;br /&gt;
&lt;br /&gt;
==add course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    name&lt;br /&gt;
    shortname&lt;br /&gt;
    format (default topics)&lt;br /&gt;
    idnumber &lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Adds a new course to the course table&lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    id or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==delete course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    name OR&lt;br /&gt;
    shortname  OR&lt;br /&gt;
    idnumber OR&lt;br /&gt;
    id&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Deletes a course from the course table&lt;br /&gt;
    &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==enrol student to course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    course unique Id (Moodle&#039;s ID or idnumber or shortname)&lt;br /&gt;
    student unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Assign student role to course &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==unenrol student from course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    course unique Id (Moodle&#039;s ID or idnumber or shortname)&lt;br /&gt;
    student unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    remove student role from course &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==assign role to course==&lt;br /&gt;
INPUT:&lt;br /&gt;
   course unique Id (Moodle&#039;s ID or idnumber or shortname)&lt;br /&gt;
   user unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
   role id (teacher, non editing teacher, student (?) ...)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   assign given user a &amp;quot;standard&amp;quot; role to given course   &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==remove role from course==&lt;br /&gt;
INPUT:&lt;br /&gt;
   course unique Id (Moodle&#039;s ID or idnumber or shortname)&lt;br /&gt;
   user unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
   role id (teacher, non editing teacher, student (?) ...)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   remove given user&#039;s &amp;quot;standard&amp;quot; role from given course   &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==get my courses==&lt;br /&gt;
&lt;br /&gt;
INPUT:&lt;br /&gt;
   user unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   return a &amp;quot;list&amp;quot; of course&#039;s id in which given user move given user has some role assigned     &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    &amp;quot;array&amp;quot; of (course id, role id)&lt;/div&gt;</summary>
		<author><name>Ppollet</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/403/en/index.php?title=Development:Web_services&amp;diff=28656</id>
		<title>Development:Web services</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/403/en/index.php?title=Development:Web_services&amp;diff=28656"/>
		<updated>2007-11-13T10:31:49Z</updated>

		<summary type="html">&lt;p&gt;Ppollet: /* assign role to course */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page is to decide on a STANDARD list of CORE web service functions that we should support in Moodle (by XMLRPC, REST and SOAP) as an API for those writing code to work against Moodle.&lt;br /&gt;
&lt;br /&gt;
Please add new functions if there&#039;s functionality you want that isn&#039;t covered (we can refactor/whittle at the end).&lt;br /&gt;
&lt;br /&gt;
==add user==&lt;br /&gt;
I think we should require all data needed for a successful &amp;quot;first login&amp;quot; to Moodle without popping him out the profile page to fill in all missing required data. This may require extra inputs such as city, description ... (unsure of the full list depending of Moodle version ?).&lt;br /&gt;
Also password should be &amp;quot;required&amp;quot; if authentication method is &amp;quot;internal&amp;quot; . &lt;br /&gt;
&lt;br /&gt;
INPUT:&lt;br /&gt;
    firstname&lt;br /&gt;
    lastname&lt;br /&gt;
    email &lt;br /&gt;
    idnumber&lt;br /&gt;
    login &lt;br /&gt;
    authentication method (optional , default= manual ?)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Adds a new user to the user database &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    id or false&lt;br /&gt;
&lt;br /&gt;
==delete user==&lt;br /&gt;
INPUT:&lt;br /&gt;
    idnumber  or &lt;br /&gt;
    email or &lt;br /&gt;
    id or&lt;br /&gt;
    login&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    User is marked as deleted&lt;br /&gt;
    All it&#039;s role assignments are destroyed &lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true/false&lt;br /&gt;
&lt;br /&gt;
==add course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    name&lt;br /&gt;
    shortname&lt;br /&gt;
    format (default topics)&lt;br /&gt;
    idnumber &lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Adds a new course to the course table&lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    id or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==delete course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    name OR&lt;br /&gt;
    shortname  OR&lt;br /&gt;
    idnumber OR&lt;br /&gt;
    id&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Deletes a course from the course table&lt;br /&gt;
    &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==enrol student to course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    course unique Id (Moodle&#039;s ID or idnumber or shortname)&lt;br /&gt;
    student unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Assign student role to course &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==unenrol student from course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    course unique Id (Moodle&#039;s ID or idnumber or shortname)&lt;br /&gt;
    student unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    remove student role from course &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==assign role to course==&lt;br /&gt;
INPUT:&lt;br /&gt;
   course unique Id (Moodle&#039;s ID or idnumber or shortname)&lt;br /&gt;
   user unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
   role id (teacher, non editing teacher, student (?) ...)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   assign given user a &amp;quot;standard&amp;quot; role to given course   &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==remove role from course==&lt;br /&gt;
INPUT:&lt;br /&gt;
   course unique Id (Moodle&#039;s ID or idnumber or shortname)&lt;br /&gt;
   user unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
   role id (teacher, non editing teacher, student (?) ...)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   remove given user&#039;s &amp;quot;standard&amp;quot; role from given course   &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;/div&gt;</summary>
		<author><name>Ppollet</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/403/en/index.php?title=Development:Web_services&amp;diff=28655</id>
		<title>Development:Web services</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/403/en/index.php?title=Development:Web_services&amp;diff=28655"/>
		<updated>2007-11-13T10:30:52Z</updated>

		<summary type="html">&lt;p&gt;Ppollet: /* unenrol student from course */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page is to decide on a STANDARD list of CORE web service functions that we should support in Moodle (by XMLRPC, REST and SOAP) as an API for those writing code to work against Moodle.&lt;br /&gt;
&lt;br /&gt;
Please add new functions if there&#039;s functionality you want that isn&#039;t covered (we can refactor/whittle at the end).&lt;br /&gt;
&lt;br /&gt;
==add user==&lt;br /&gt;
I think we should require all data needed for a successful &amp;quot;first login&amp;quot; to Moodle without popping him out the profile page to fill in all missing required data. This may require extra inputs such as city, description ... (unsure of the full list depending of Moodle version ?).&lt;br /&gt;
Also password should be &amp;quot;required&amp;quot; if authentication method is &amp;quot;internal&amp;quot; . &lt;br /&gt;
&lt;br /&gt;
INPUT:&lt;br /&gt;
    firstname&lt;br /&gt;
    lastname&lt;br /&gt;
    email &lt;br /&gt;
    idnumber&lt;br /&gt;
    login &lt;br /&gt;
    authentication method (optional , default= manual ?)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Adds a new user to the user database &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    id or false&lt;br /&gt;
&lt;br /&gt;
==delete user==&lt;br /&gt;
INPUT:&lt;br /&gt;
    idnumber  or &lt;br /&gt;
    email or &lt;br /&gt;
    id or&lt;br /&gt;
    login&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    User is marked as deleted&lt;br /&gt;
    All it&#039;s role assignments are destroyed &lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true/false&lt;br /&gt;
&lt;br /&gt;
==add course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    name&lt;br /&gt;
    shortname&lt;br /&gt;
    format (default topics)&lt;br /&gt;
    idnumber &lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Adds a new course to the course table&lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    id or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==delete course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    name OR&lt;br /&gt;
    shortname  OR&lt;br /&gt;
    idnumber OR&lt;br /&gt;
    id&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Deletes a course from the course table&lt;br /&gt;
    &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==enrol student to course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    course unique Id (Moodle&#039;s ID or idnumber or shortname)&lt;br /&gt;
    student unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Assign student role to course &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==unenrol student from course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    course unique Id (Moodle&#039;s ID or idnumber or shortname)&lt;br /&gt;
    student unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    remove student role from course &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==assign role to course==&lt;br /&gt;
INPUT:&lt;br /&gt;
   course unique Id (Moodle&#039;s ID or idnumber or shortname)&lt;br /&gt;
   user unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
   role id (teacher, non editing teacher, student (?) ...)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   assign given user a &amp;quot;standard&amp;quot; role to given course   &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;/div&gt;</summary>
		<author><name>Ppollet</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/403/en/index.php?title=Development_talk:Web_services&amp;diff=28654</id>
		<title>Development talk:Web services</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/403/en/index.php?title=Development_talk:Web_services&amp;diff=28654"/>
		<updated>2007-11-13T10:30:23Z</updated>

		<summary type="html">&lt;p&gt;Ppollet: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==general remarks about OUTPUT of operations:==&lt;br /&gt;
Is true of false informative enough ?&lt;br /&gt;
Should the API have some sort of &amp;quot;last_error&amp;quot; function giving back more details such as &amp;quot;non existing course, non existing user, duplicate entry ...)&lt;br /&gt;
Shall we consider that affecting a role that already exist or removing role that do not exist as an error (output=false) or not (output=true)&lt;/div&gt;</summary>
		<author><name>Ppollet</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/403/en/index.php?title=Development_talk:Web_services&amp;diff=28653</id>
		<title>Development talk:Web services</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/403/en/index.php?title=Development_talk:Web_services&amp;diff=28653"/>
		<updated>2007-11-13T10:29:33Z</updated>

		<summary type="html">&lt;p&gt;Ppollet: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==general remarks about OUTPUT of operations:==&lt;br /&gt;
Is true of false informative enough ?&lt;br /&gt;
Should the API have some sort of &amp;quot;last_error&amp;quot; fonction iving back more details such as &amp;quot;no existing course, non existing user, duplicate entry ...)&lt;br /&gt;
Shall we consider that affecting a role that already exist or emovinga role that do not exist as an error (output=fale) or not (output=true)&lt;/div&gt;</summary>
		<author><name>Ppollet</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/403/en/index.php?title=Development_talk:Web_services&amp;diff=28652</id>
		<title>Development talk:Web services</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/403/en/index.php?title=Development_talk:Web_services&amp;diff=28652"/>
		<updated>2007-11-13T10:28:55Z</updated>

		<summary type="html">&lt;p&gt;Ppollet: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==general remarks about OUTPUT of operations:==&lt;br /&gt;
  Is true of false informative enough ?&lt;br /&gt;
  Should the API have some sort of &amp;quot;last_error&amp;quot; fonction iving back more details such as &amp;quot;no existing course, non existing user, duplicate entry ...)&lt;br /&gt;
  Shall we consider that affecting a role that already exist or emovinga role that do not exist as an error (output=fale) or not (output=true)&lt;/div&gt;</summary>
		<author><name>Ppollet</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/403/en/index.php?title=Development_talk:Web_services&amp;diff=28651</id>
		<title>Development talk:Web services</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/403/en/index.php?title=Development_talk:Web_services&amp;diff=28651"/>
		<updated>2007-11-13T10:28:22Z</updated>

		<summary type="html">&lt;p&gt;Ppollet: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;===general remarks about OUTPUT of operations:&lt;br /&gt;
  Is true of false informative enough ?&lt;br /&gt;
  Should the API have some sort of &amp;quot;last_error&amp;quot; fonction iving back more details such as &amp;quot;no existing course, non existing user, duplicate entry ...)&lt;br /&gt;
  Shall we consider that affecting a role that already exist or emovinga role that do not exist as an error (output=fale) or not (output=true)&lt;/div&gt;</summary>
		<author><name>Ppollet</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/403/en/index.php?title=Development:Web_services&amp;diff=28650</id>
		<title>Development:Web services</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/403/en/index.php?title=Development:Web_services&amp;diff=28650"/>
		<updated>2007-11-13T10:24:34Z</updated>

		<summary type="html">&lt;p&gt;Ppollet: /* unenrol student from course */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page is to decide on a STANDARD list of CORE web service functions that we should support in Moodle (by XMLRPC, REST and SOAP) as an API for those writing code to work against Moodle.&lt;br /&gt;
&lt;br /&gt;
Please add new functions if there&#039;s functionality you want that isn&#039;t covered (we can refactor/whittle at the end).&lt;br /&gt;
&lt;br /&gt;
==add user==&lt;br /&gt;
I think we should require all data needed for a successful &amp;quot;first login&amp;quot; to Moodle without popping him out the profile page to fill in all missing required data. This may require extra inputs such as city, description ... (unsure of the full list depending of Moodle version ?).&lt;br /&gt;
Also password should be &amp;quot;required&amp;quot; if authentication method is &amp;quot;internal&amp;quot; . &lt;br /&gt;
&lt;br /&gt;
INPUT:&lt;br /&gt;
    firstname&lt;br /&gt;
    lastname&lt;br /&gt;
    email &lt;br /&gt;
    idnumber&lt;br /&gt;
    login &lt;br /&gt;
    authentication method (optional , default= manual ?)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Adds a new user to the user database &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    id or false&lt;br /&gt;
&lt;br /&gt;
==delete user==&lt;br /&gt;
INPUT:&lt;br /&gt;
    idnumber  or &lt;br /&gt;
    email or &lt;br /&gt;
    id or&lt;br /&gt;
    login&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    User is marked as deleted&lt;br /&gt;
    All it&#039;s role assignments are destroyed &lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true/false&lt;br /&gt;
&lt;br /&gt;
==add course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    name&lt;br /&gt;
    shortname&lt;br /&gt;
    format (default topics)&lt;br /&gt;
    idnumber &lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Adds a new course to the course table&lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    id or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==delete course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    name OR&lt;br /&gt;
    shortname  OR&lt;br /&gt;
    idnumber OR&lt;br /&gt;
    id&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Deletes a course from the course table&lt;br /&gt;
    &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==enrol student to course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    course unique Id (Moodle&#039;s ID or idnumber or shortname)&lt;br /&gt;
    student unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Assign student role to course &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==unenrol student from course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    course unique Id (Moodle&#039;s ID or idnumber or shortname)&lt;br /&gt;
    student unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    remove student role from course &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==assign role to course&lt;br /&gt;
INPUT:&lt;br /&gt;
   course unique Id (Moodle&#039;s ID or idnumber or shortname)&lt;br /&gt;
   user unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
   role id (teacher, non editing teacher, student (?) ...)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
   assign given user a &amp;quot;standard&amp;quot; role to given course   &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;/div&gt;</summary>
		<author><name>Ppollet</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/403/en/index.php?title=Development:Web_services&amp;diff=28649</id>
		<title>Development:Web services</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/403/en/index.php?title=Development:Web_services&amp;diff=28649"/>
		<updated>2007-11-13T10:17:54Z</updated>

		<summary type="html">&lt;p&gt;Ppollet: /* delete course */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page is to decide on a STANDARD list of CORE web service functions that we should support in Moodle (by XMLRPC, REST and SOAP) as an API for those writing code to work against Moodle.&lt;br /&gt;
&lt;br /&gt;
Please add new functions if there&#039;s functionality you want that isn&#039;t covered (we can refactor/whittle at the end).&lt;br /&gt;
&lt;br /&gt;
==add user==&lt;br /&gt;
I think we should require all data needed for a successful &amp;quot;first login&amp;quot; to Moodle without popping him out the profile page to fill in all missing required data. This may require extra inputs such as city, description ... (unsure of the full list depending of Moodle version ?).&lt;br /&gt;
Also password should be &amp;quot;required&amp;quot; if authentication method is &amp;quot;internal&amp;quot; . &lt;br /&gt;
&lt;br /&gt;
INPUT:&lt;br /&gt;
    firstname&lt;br /&gt;
    lastname&lt;br /&gt;
    email &lt;br /&gt;
    idnumber&lt;br /&gt;
    login &lt;br /&gt;
    authentication method (optional , default= manual ?)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Adds a new user to the user database &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    id or false&lt;br /&gt;
&lt;br /&gt;
==delete user==&lt;br /&gt;
INPUT:&lt;br /&gt;
    idnumber  or &lt;br /&gt;
    email or &lt;br /&gt;
    id or&lt;br /&gt;
    login&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    User is marked as deleted&lt;br /&gt;
    All it&#039;s role assignments are destroyed &lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true/false&lt;br /&gt;
&lt;br /&gt;
==add course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    name&lt;br /&gt;
    shortname&lt;br /&gt;
    format (default topics)&lt;br /&gt;
    idnumber &lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Adds a new course to the course table&lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    id or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==delete course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    name OR&lt;br /&gt;
    shortname  OR&lt;br /&gt;
    idnumber OR&lt;br /&gt;
    id&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Deletes a course from the course table&lt;br /&gt;
    &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==enrol student to course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    course unique Id (Moodle&#039;s ID or idnumber or shortname)&lt;br /&gt;
    student unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Assign student role to course &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==unenrol student from course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    course unique Id (Moodle&#039;s ID or idnumber or shortname)&lt;br /&gt;
    student unique id (Moodle&#039;s ID or idnumber or login or email)&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    remove student role from course &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;/div&gt;</summary>
		<author><name>Ppollet</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/403/en/index.php?title=Development:Web_services&amp;diff=28648</id>
		<title>Development:Web services</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/403/en/index.php?title=Development:Web_services&amp;diff=28648"/>
		<updated>2007-11-13T10:14:28Z</updated>

		<summary type="html">&lt;p&gt;Ppollet: /* delete course */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page is to decide on a STANDARD list of CORE web service functions that we should support in Moodle (by XMLRPC, REST and SOAP) as an API for those writing code to work against Moodle.&lt;br /&gt;
&lt;br /&gt;
Please add new functions if there&#039;s functionality you want that isn&#039;t covered (we can refactor/whittle at the end).&lt;br /&gt;
&lt;br /&gt;
==add user==&lt;br /&gt;
I think we should require all data needed for a successful &amp;quot;first login&amp;quot; to Moodle without popping him out the profile page to fill in all missing required data. This may require extra inputs such as city, description ... (unsure of the full list depending of Moodle version ?).&lt;br /&gt;
Also password should be &amp;quot;required&amp;quot; if authentication method is &amp;quot;internal&amp;quot; . &lt;br /&gt;
&lt;br /&gt;
INPUT:&lt;br /&gt;
    firstname&lt;br /&gt;
    lastname&lt;br /&gt;
    email &lt;br /&gt;
    idnumber&lt;br /&gt;
    login &lt;br /&gt;
    authentication method (optional , default= manual ?)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Adds a new user to the user database &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    id or false&lt;br /&gt;
&lt;br /&gt;
==delete user==&lt;br /&gt;
INPUT:&lt;br /&gt;
    idnumber  or &lt;br /&gt;
    email or &lt;br /&gt;
    id or&lt;br /&gt;
    login&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    User is marked as deleted&lt;br /&gt;
    All it&#039;s role assignments are destroyed &lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true/false&lt;br /&gt;
&lt;br /&gt;
==add course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    name&lt;br /&gt;
    shortname&lt;br /&gt;
    format (default topics)&lt;br /&gt;
    idnumber &lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Adds a new course to the course table&lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    id or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==delete course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    name OR&lt;br /&gt;
    shortname  OR&lt;br /&gt;
    idnumber OR&lt;br /&gt;
    id&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Deletes a course from the course table&lt;br /&gt;
    &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;/div&gt;</summary>
		<author><name>Ppollet</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/403/en/index.php?title=Development:Web_services&amp;diff=28647</id>
		<title>Development:Web services</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/403/en/index.php?title=Development:Web_services&amp;diff=28647"/>
		<updated>2007-11-13T10:13:11Z</updated>

		<summary type="html">&lt;p&gt;Ppollet: /* delete user */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page is to decide on a STANDARD list of CORE web service functions that we should support in Moodle (by XMLRPC, REST and SOAP) as an API for those writing code to work against Moodle.&lt;br /&gt;
&lt;br /&gt;
Please add new functions if there&#039;s functionality you want that isn&#039;t covered (we can refactor/whittle at the end).&lt;br /&gt;
&lt;br /&gt;
==add user==&lt;br /&gt;
I think we should require all data needed for a successful &amp;quot;first login&amp;quot; to Moodle without popping him out the profile page to fill in all missing required data. This may require extra inputs such as city, description ... (unsure of the full list depending of Moodle version ?).&lt;br /&gt;
Also password should be &amp;quot;required&amp;quot; if authentication method is &amp;quot;internal&amp;quot; . &lt;br /&gt;
&lt;br /&gt;
INPUT:&lt;br /&gt;
    firstname&lt;br /&gt;
    lastname&lt;br /&gt;
    email &lt;br /&gt;
    idnumber&lt;br /&gt;
    login &lt;br /&gt;
    authentication method (optional , default= manual ?)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Adds a new user to the user database &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    id or false&lt;br /&gt;
&lt;br /&gt;
==delete user==&lt;br /&gt;
INPUT:&lt;br /&gt;
    idnumber  or &lt;br /&gt;
    email or &lt;br /&gt;
    id or&lt;br /&gt;
    login&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    User is marked as deleted&lt;br /&gt;
    All it&#039;s role assignments are destroyed &lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true/false&lt;br /&gt;
&lt;br /&gt;
==add course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    name&lt;br /&gt;
    shortname&lt;br /&gt;
    format (default topics)&lt;br /&gt;
    idnumber &lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Adds a new course to the course table&lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    id or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==delete course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    name OR&lt;br /&gt;
    shortname  OR&lt;br /&gt;
    idnumber &lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Deletes a course from the course table&lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;/div&gt;</summary>
		<author><name>Ppollet</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/403/en/index.php?title=Development:Web_services&amp;diff=28646</id>
		<title>Development:Web services</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/403/en/index.php?title=Development:Web_services&amp;diff=28646"/>
		<updated>2007-11-13T10:08:06Z</updated>

		<summary type="html">&lt;p&gt;Ppollet: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page is to decide on a STANDARD list of CORE web service functions that we should support in Moodle (by XMLRPC, REST and SOAP) as an API for those writing code to work against Moodle.&lt;br /&gt;
&lt;br /&gt;
Please add new functions if there&#039;s functionality you want that isn&#039;t covered (we can refactor/whittle at the end).&lt;br /&gt;
&lt;br /&gt;
==add user==&lt;br /&gt;
I think we should require all data needed for a successful &amp;quot;first login&amp;quot; to Moodle without popping him out the profile page to fill in all missing required data. This may require extra inputs such as city, description ... (unsure of the full list depending of Moodle version ?).&lt;br /&gt;
Also password should be &amp;quot;required&amp;quot; if authentication method is &amp;quot;internal&amp;quot; . &lt;br /&gt;
&lt;br /&gt;
INPUT:&lt;br /&gt;
    firstname&lt;br /&gt;
    lastname&lt;br /&gt;
    email &lt;br /&gt;
    idnumber&lt;br /&gt;
    login &lt;br /&gt;
    authentication method (optional , default= manual ?)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Adds a new user to the user database &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    id or false&lt;br /&gt;
&lt;br /&gt;
==delete user==&lt;br /&gt;
INPUT:&lt;br /&gt;
    idnumber  or &lt;br /&gt;
    email or &lt;br /&gt;
    id &lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    User is marked as deleted&lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true/false &lt;br /&gt;
&lt;br /&gt;
==add course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    name&lt;br /&gt;
    shortname&lt;br /&gt;
    format (default topics)&lt;br /&gt;
    idnumber &lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Adds a new course to the course table&lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    id or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==delete course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    name OR&lt;br /&gt;
    shortname  OR&lt;br /&gt;
    idnumber &lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Deletes a course from the course table&lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;/div&gt;</summary>
		<author><name>Ppollet</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/403/en/index.php?title=Development:Web_services&amp;diff=28645</id>
		<title>Development:Web services</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/403/en/index.php?title=Development:Web_services&amp;diff=28645"/>
		<updated>2007-11-13T10:06:58Z</updated>

		<summary type="html">&lt;p&gt;Ppollet: /* add user */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page is to decide on a STANDARD list of CORE web service functions that we should support in Moodle (by XMLRPC, REST and SOAP) as an API for those writing code to work against Moodle.&lt;br /&gt;
&lt;br /&gt;
Please add new functions if there&#039;s functionality you want that isn&#039;t covered (we can refactor/whittle at the end).&lt;br /&gt;
&lt;br /&gt;
==add user==&lt;br /&gt;
I think we should require all data needed for a successful &amp;quot;first login&amp;quot; to Moodle without popping him out the profile page to fill in all missing required data. In particular password should be &amp;quot;required&amp;quot; if authentication method is &amp;quot;internal&amp;quot; . This may require extra inputs such as city, description ... (unsure of the full ist depending of Moodle version ?).&lt;br /&gt;
&lt;br /&gt;
INPUT:&lt;br /&gt;
    firstname&lt;br /&gt;
    lastname&lt;br /&gt;
    email &lt;br /&gt;
    idnumber&lt;br /&gt;
    login &lt;br /&gt;
    authentication method (optional , default= manual ?)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Adds a new user to the user database &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    id or false&lt;br /&gt;
&lt;br /&gt;
==delete user==&lt;br /&gt;
INPUT:&lt;br /&gt;
    idnumber  or &lt;br /&gt;
    email or &lt;br /&gt;
    id &lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    User is marked as deleted&lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true/false &lt;br /&gt;
&lt;br /&gt;
==add course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    name&lt;br /&gt;
    shortname&lt;br /&gt;
    format (default topics)&lt;br /&gt;
    idnumber &lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Adds a new course to the course table&lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    id or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==delete course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    name OR&lt;br /&gt;
    shortname  OR&lt;br /&gt;
    idnumber &lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Deletes a course from the course table&lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;/div&gt;</summary>
		<author><name>Ppollet</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/403/en/index.php?title=Development:Web_services&amp;diff=28644</id>
		<title>Development:Web services</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/403/en/index.php?title=Development:Web_services&amp;diff=28644"/>
		<updated>2007-11-13T10:00:29Z</updated>

		<summary type="html">&lt;p&gt;Ppollet: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page is to decide on a STANDARD list of CORE web service functions that we should support in Moodle (by XMLRPC, REST and SOAP) as an API for those writing code to work against Moodle.&lt;br /&gt;
&lt;br /&gt;
Please add new functions if there&#039;s functionality you want that isn&#039;t covered (we can refactor/whittle at the end).&lt;br /&gt;
&lt;br /&gt;
==add user==&lt;br /&gt;
&lt;br /&gt;
INPUT:&lt;br /&gt;
    firstname&lt;br /&gt;
    lastname&lt;br /&gt;
    email &lt;br /&gt;
    idnumber&lt;br /&gt;
    login &lt;br /&gt;
    authentication method (optional , default= manual ?)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Adds a new user to the user database &lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    id or false&lt;br /&gt;
&lt;br /&gt;
==delete user==&lt;br /&gt;
INPUT:&lt;br /&gt;
    idnumber  or &lt;br /&gt;
    email or &lt;br /&gt;
    id &lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    User is marked as deleted&lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true/false &lt;br /&gt;
&lt;br /&gt;
==add course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    name&lt;br /&gt;
    shortname&lt;br /&gt;
    format (default topics)&lt;br /&gt;
    idnumber &lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Adds a new course to the course table&lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    id or false&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==delete course==&lt;br /&gt;
INPUT:&lt;br /&gt;
    name OR&lt;br /&gt;
    shortname  OR&lt;br /&gt;
    idnumber &lt;br /&gt;
&lt;br /&gt;
OPERATION:&lt;br /&gt;
    Deletes a course from the course table&lt;br /&gt;
&lt;br /&gt;
OUTPUT:&lt;br /&gt;
    true or false&lt;/div&gt;</summary>
		<author><name>Ppollet</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/403/en/index.php?title=Book_resource&amp;diff=9553</id>
		<title>Book resource</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/403/en/index.php?title=Book_resource&amp;diff=9553"/>
		<updated>2006-05-13T12:44:22Z</updated>

		<summary type="html">&lt;p&gt;Ppollet: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Book}}&lt;br /&gt;
&lt;br /&gt;
Created by [http://moodle.org/user/view.php?id=12863&amp;amp;course=5 Petr Škoda], the &#039;&#039;&#039;Book&#039;&#039;&#039; module makes it easy to create multi-page resources with a book-like format. This can be used to build complete book-like websites inside of your Moodle course.&lt;br /&gt;
&lt;br /&gt;
Previously created websites can be imported directly into the Book module.  Books can be printed entirely or by chapter.&lt;br /&gt;
&lt;br /&gt;
The book module allows you to have main chapters and sub chapters, but it goes no deeper. In other words, sub chapters cannot have their own sub chapters. This was an intentional decision by the creator of the book module. He intended this to be a simple resource for teachers and students.&lt;br /&gt;
&lt;br /&gt;
The book module is not interactive. You can, however, link to choices, forums, etc., from within a book. And you can include multimedia objects like Flash movies in your book.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* [http://download.moodle.org/modules/  Download ]&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
&lt;br /&gt;
* Using Moodle [http://moodle.org/mod/forum/view.php?id=2633 Book module] forum&lt;br /&gt;
* [[Non-standard modules]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Teacher]]&lt;br /&gt;
[[Category:Module (non-standard)]]&lt;br /&gt;
&lt;br /&gt;
[[es:Book]]&lt;/div&gt;</summary>
		<author><name>Ppollet</name></author>
	</entry>
</feed>