Glossary of common terms
This glossary defines a number of words you will see used often in discussions about Moodle - you'll find them highlighted throughout this course.
If you wish to import this glossary to your Moodle site, you can download this file of exported entries: glossary_of_common_terms_20101214.xml.
Please feel free to add new words here!
Currently sorted By last update ascending Sort chronologically: By last update
permission | ||
|---|---|---|
A permission is a part of a role which allows or denies a someone to use a feature or function of Moodle. There are over 450 different permissions settings in any Moodle role. Each permission has 1 of 4 states that can be assigned to it: "not set", "allow", "prevent", and "prohibit. Editing or creating new roles on the site level can be complicated. In part because of the hierarchical nature of contexts. In many contexts, roles or permissions can be overridden, and the permitted user will see a shortened list of permissions appropriate to the context. | ||
Interface | |||
|---|---|---|---|
In general an interface is the boundary across which two systems communicate. There are many software interfaces within Moodle, for example, such as the interface a module uses to communicate with the core product, or the interface used to send mail. Usually, though, this term refers to the interface between software and human beings: the user interface. In Moodle, for example, this is what we see and click on in the web browser and in our mail programs, and it provides ways for us to access, understand and change the database at the heart of any Moodle site. The design of such an interface requires collaboration between software developers and users to make it "user-friendly" (and maximise overall usability). A very important requirement for interfaces is standardisation, which reduces the amount of learning that users need to do to explore the features in the software. Moodle has had informal standards in the past, but we are currently writing a more formal specification to help Moodle's many developers produce a more consistent interface, and remove some of the irregular, inefficient or hard-to-learn interfaces that have crept into various corners of Moodle. With Moodle, interface issues should be discussed in the forums most appropriate to them - if you wish to raise discussion about an interface in the Chat module, use the Chat forum. If you have a specific bug or request to report, please use the bug tracker. | |||
MUA | ||
|---|---|---|
OP | ||
|---|---|---|
Short for Original Poster, in other words the person starting the discussion. | ||
 | AMPPS | |
|---|---|---|
Plesk | |||
|---|---|---|---|
Plesk is a commercial hosting management program that can be used to manage the account management interface. Plesk can be used for multiple distros of Linux (Ubuntu, Redhat, Cloud Linux, Debian) and Windows Server 2008 and 2012 servers. | |||
MariaDB | |||
|---|---|---|---|
MariaDB is community developed database based on popular database MySQL. MariaDB was forked from MySQL, and maintains many of the same features, APIs and commands used in MySQL. MariaDB can be accessed for administration using PHPMyAdmin, the same tool used for MySQL. MariaDB uses the "XtraDB" storage engine which is a drop-in replacement of InnoDB used by MySQL and a new storage engine called Aria. | |||
MSSQL | |||
|---|---|---|---|
One of the database types supported by Moodle's implementation of the database interface layer. There are a large number of implementations of MSSQL, and it would appear that Moodle works with the latest versions. | |||
MySQL | ||
|---|---|---|
MySQL is the world's most popular open source database, recognized for its speed and reliability. | ||