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 this file of exported entries: glossary_of_common_terms_20101214.xml.
Please feel free to add new words here!
A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z | ALL
Currently sorted First name ascending Sort by: Last name | First name
Firebird is a fully featured and powerful RDBMS and is derived from Borland InterBase 6.0 source code, which has more than 20 years of handling databases from just a few KB to many Gigabytes with good performance and almost free of maintenance!
It is open source and has no dual license. Below is a list of some of the Firebird’s major features:
Firebird is financially supported by Firebird Foundation which get his founds from company donations and paid membership subscriptions.
See http://www.firebirdsql.org/ for more information.
autonomous system (AS)
An Autonomous system (AS) is a collection of IP networks and routers under the control of one entity (or sometimes more) that presents a common routing policy to the Internet
In Moodle, the term "context" may have a specific meaning.
A Moodle context is a place where permissions are assigned to a user (usually through a role). In Moodle, contexts are layered in a hierachry. Some examples: a site is the overall context; each course category is a context in the site; each course is a context in it's course category; each topic/section is a context and the resources and activities in a topic/section are contexts. Blocks, filters and special pages are contexts that are at minimum part of the site context. Permissions are passed down automatically. For example, a user who has a teacher role in a course will be assigned that role when a Forum context is created. Roles for individuals or groups can be changed in a context. This makes it possible for one user to be a teacher in one context and a student in another.
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.
Abbreviation for Hope That Helps (or Hope This Helps).
Originally from Usenet, but now appearing in emails and forums, it's sometimes put at the end of a reply which suggests a possible solution to a problem.
A Bitnami Stack provides a single application LAMP, WAMP or MAMP for Moodle installations. This approach offers a good solution to Users who want a test site on a stand alone computer. The Bitnami Stack also provides a more stable environment for adding additional PHP applications than other, similar solutions.
Good Luck With That One Buddy! - Usually a reference to a reasonable position, view, or situation that is seen as being untenable or unachievable because of the lack of co-operation of others, usually for their own, often non-logical or unreasonable, perceptions.
I Am Not A Developer - a response when answering technical question if suggesting an action that may need more input from a Moodle Developer.
In My Not So Humble Opinion - usually reserved for something we are an expert at or an issue we feel strongly supportive, or otherwise, of.