https://docs.moodle.org/test/api.php?action=feedcontributions&feedformat=atom&user=Jmark93 2026-09-17T18:41:04Z User contributions MediaWiki 1.43.5 https://docs.moodle.org/test/index.php?title=Internalmail_module&diff=23309 2007-05-16T05:37:48Z

<p>Jmark93: /* Versions available */</p> <hr /> <div>The '''Internalmail module''' provides an internal email system that works within Moodle. Each user can have his or her own internal mailbox to send and receive messages from the moodle site users.<br /> <br /> ==Why use internalmail==<br /> Why would one use internalmail?<br /> * Because Moodle providers don't have to provide internet email acounts to their users.<br /> * Because if email is to be used as a tool for education there has to be a way to track the status of the messages.<br /> * Because internalmail provides course contextual folders.<br /> * Because internalmail is trully spam free.<br /> http://www.lsi.upc.edu/%7Emalier/internalmail/webmail.gif<br /> ==Versions available==<br /> The first Internalmail Module was developed for Moodle 1.4. Then came along the version 2.0 (2.1, 2.2. and 2.3 ) for Moodle 1.5 and the version 2.4x for Moodle 1.6.<br /> <br /> Rigth now ( Jan 2007) Internalmail does not work for Moodle 1.7, but this will be fixed very soon.<br /> <br /> Also, DFWikiteam is preparing a third version of Internalmail.<br /> <br /> ==Uses and future==<br /> Since UPC [http://atenea.upc.edu] (and lots of other installations) is using Internalmail, we can be sure that the module will be maitained and updated....in due time.<br /> <br /> ==See also==<br /> <br /> * [http://moodle.org/mod/forum/discuss.php?d=22744 Internalmail Discussion @ Moodle.org]<br /> * [http://morfeo.upc.es/crom/course/view.php?id=4 InternalMail Home Page] <br /> * [http://morfeo.upc.es/crom/mod/wiki/view.php?id=22&amp;page=view/Internalmail+Guide&amp;gid=0&amp;uid=0 InternalMail Users Guide]<br /> * [http://appserv.lsi.upc.es/palangana/moodle/course/view.php?id=18 Old InternalMail Home Page]<br /> * [[Dfwiki module]]<br /> <br /> [[Category:Teacher]]<br /> [[Category:Modules (non-standard)]]</div>

Jmark93 https://docs.moodle.org/test/index.php?title=Roles_and_capabilities&diff=19776 2007-01-30T20:36:14Z

<p>Jmark93: /* Roles */</p> <hr /> <div>{{Roles}}<br /> {{Moodle 1.7}}<br /> <br /> ==Roles==<br /> <br /> Previous Moodle versions had predefined, fixed roles. There was no easy way to change what a teacher, or student, for instance, could do. While fixed roles are adequate for many users, others require greater flexibility in regulating how users see and interact with the system. <br /> <br /> With Roles, authorized users may [[Manage roles|create]] any number of customized roles and assign them to users. From 1.7, an organization may create multiple roles so that, for instance, students assigned Role A could post to forums, while students assigned Role B are prevented from posting.<br /> <br /> ==Definitions==<br /> *A '''role''' is an identifier of the user's status in some context, for example ''teacher'', ''student'' and ''forum moderator''.<br /> *A '''capability''' is a description of a particular Moodle feature, for example ''[[Capabilities/moodle/blog:create|moodle/blog:create]]''. Capabilities are associated with roles.<br /> *A '''permission''' is [[Manage roles#Permissions|a value that is assigned]] for a capability for a particular role, for example ''allow'' or ''prevent''.<br /> *A '''context''' is a &quot;space&quot; in Moodle, such as courses, activity modules or blocks. Roles will only work if the role assignment is made at the correct context level. For example, a ''teacher'' role should be assigned at course context level, a ''forum moderator'' for a particular forum should be assigned at activity level, an ''administrator'' should be assigned at system level and so on.<br /> <br /> ==Contexts==<br /> <br /> The list of contexts in hierarchical order is as follows:<br /> *System context - accessible via the administrator's block (no parent)<br /> *Course category context - accessible via the course category page (parent = site)<br /> *Course context - accessible via the course administration block (old admin block) (parent = course category or site)<br /> *Module context - accessible whilst updating the module (parent = course)<br /> *Block context - accessible when editing mode is on (parent = site or course)<br /> *User context - accessible via the Roles tab in the user profile (parent = site)<br /> <br /> Inheritance will kick in if a role is assigned at a higher level. For example assigning a ''teacher'' to a course category will make this user the teacher for ALL courses within the category.<br /> <br /> ==Capabilities==<br /> <br /> Capabilities are aggregated and controlled via roles. Stated another way, a role consists of a list of capabilities for different possible actions within Moodle (e.g. delete discussions or add activities). With 1.7 it's now possible to have sophisticated yet flexible levels of control over participants and what they can or can't do.<br /> <br /> ==Upgrading to 1.7==<br /> <br /> The upgrade to 1.7 is as smooth as we could make it. The existing roles (admin, teacher, student etc.) and the existing capabilities will be automatically retained. This is done by creating default roles at site/course levels, and assigning the current users to these roles accordingly. The default roles will have default capabilities associated with them, mirroring what we have in 1.6. With no modifications, Moodle will operate almost exactly the same before and after the upgrade.<br /> <br /> ==See also==<br /> *[[Development:Roles]]<br /> *[[:Category:Capability]]<br /> *Using Moodle [http://moodle.org/mod/forum/view.php?id=6826 Roles and Capabilities forum]<br /> <br /> [[Category:Teacher]]<br /> [[Category:Administrator]]<br /> [[Category:Roles]]</div>

Jmark93 https://docs.moodle.org/test/index.php?title=Importing/exporting_glossaries&diff=18538 2006-12-09T14:01:55Z

<p>Jmark93: /* Glossaries in the future */</p> <hr /> <div>{{Glossaries}}<br /> <br /> ===Importing a glossary===<br /> <br /> There are two ways to import glossaries<br /> <br /> 1. Restoring the glossaries from a moodle course backup file containing the glossary. This method includes categories, images and attachments within glossary entries and if you also select users then the authors of entries are also imported if they were originally included in the backup.<br /> <br /> 2. Importing a specially formatted XML file in glossary format. This method only inports text, some HTML formatting and switches such as auto-linking, case specific and whole words linking. There is also a switch to import categories into which entries are automatically included.<br /> <br /> ====Some import issues====<br /> <br /> You can only import the XML file from within a glossary that already exists but you can import to a new glossary.<br /> <br /> In experimenting with import I have found that the import will fail often. Some reasons appear to be:-<br /> <br /> If there are mistakes in the XML file such as the &lt;entries&gt; tag being missing or the &lt;info&gt; tag being in the wrong place. May happen if you have constructed the XML file manually or with some sort of tool like mailmerge in Word and your template is wrong.<br /> <br /> If there are top bit set characters in the text of the entities like concepts, definitions or keywords. Replace things like &amp; with &amp;amp;<br /> <br /> If there are tabs or spaces between entries. Not sure if spaces cause problems but best to remove any bewtween the end of one tag and start of the next. e.g. Search and replace &gt; &lt; with &gt;&lt; via a text editor.<br /> <br /> In most cases the import is halted if any of these errors occur.<br /> <br /> Duplicates in the entries which clash with entries already when merging a glossary is usually not a problem.<br /> <br /> Warnings like <br /> <br /> Warning: exec() has been disabled for security reasons in /moodle/lib/uploadlib.php on line 603<br /> <br /> may not be the problem when importing but may distract one from dealing with problems with the format of the XML file.<br /> <br /> ===Exporting a glossary===<br /> <br /> There are two ways to export glossaries<br /> <br /> 1. Backing up glossaries only via a moodle course backup file. This method will also export any categories, embedded images and attached files within entries and any HTML formatting. If users are also exported authors of entries are also included.<br /> <br /> 2. Exporting a specially formatted XML file in glossary format. This will only export text, some HTML formatting and switches such as auto-linking, case specific and whole words linking.<br /> <br /> ====Some export Issues====<br /> <br /> You can only export the XML file from within a glossary.<br /> <br /> ===Glossaries in the future===<br /> <br /> The glossary module may eventually be replaced by the database module which will greatly improve import and export functionality.<br /> <br /> == See also ==<br /> <br /> *[http://download.moodle.org/docs/using_moodle/ch9_glossaries.pdf Using Moodle Chapter 9: Glossaries]<br /> *Using Moodle [http://moodle.org/mod/forum/discuss.php?d=54403 Any creative ideas/ stories for using glossaries] forum discussion<br /> <br /> [[Category:Teacher]]<br /> [[Category:Glossary]]<br /> [[Category:Modules]]<br /> <br /> [[fr:Importer/exporter un glossaire]]</div>

Jmark93