DigCompLMSAdmin competenties
Voltooingsvoorwaarden
DigCompLMSAdmin is a competency framework for Moodle administrators, designed by Moodle Academy based on the DigCompEdu framework for educators.
It informs our Administrator Learning Pathway and consists of:
It informs our Administrator Learning Pathway and consists of:
- 4 general thematic areas (Infrastructure, Operation, Integration, Practice) covering:
- 8 areas of competence (Implementation, Maintenance and Support, Site Structure, User Management, Site appearance/UX, Monitoring, Plugins and Extensions, Professional Practice) incorporating:
- 31 competences as in the graphic and glossary entries below.
This framework by Moodle Academy (Moodle Pty Ltd) is licensed under CC BY 4.0. Original framework on Moodle.Academy and in .csv format on MoodleNet: DigCompLMSAdmin.
›
Read more about how you should attribute this work.
Blader door de woordenlijst met deze index
Speciale tekens | 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 | Alles
1 |
|---|
1.1 InstallationSet up an LMS on a suitable hosting environment.
| |
1.2 SecurityIncorporate good practice in embedding security in the LMS.
| |
1.3 PrivacyEnable agreed privacy procedures appropriate to the institution and location.
| |
1.4 Site policyEnable agreed site policies appropriate to the institution and location.
| |
2 |
|---|
2.1 PerformanceUse recommended performance measures for optimisation and scalability.
| |
2.2 UpgradingImplement an agreed policy of regular upgrades.
| |
2.3 Year end / RolloverIncorporate regular backups and resets in line with institutional requirements.
| |
2.4 Support structuresSupport learners and staff to use the LMS.
| |
3 |
|---|
3.2 Course / Category managementOrganise the LMS learning pathways in line with the needs of the institution.
| |
3.3 Repositories / PortfoliosSelect the appropriate standard repositories and portfolios for learning and teaching.
| |
4 |
|---|
4.1 AuthenticationIdentify, enable and monitor authentication methods relevant to the institution.
| |
4.2 EnrolmentIdentify, enable and monitor enrolment methods relevant to the institution.
| |
4.3 RolesAssign, adapt and create roles appropriately.
| |
4.4 Capabilities and PermissionsMake thoughtful use of permissions to extend or restrict capabilities.
| |
5 |
|---|
5.1 NavigationUse appropriate settings and features to ensure users can easily locate everything in the LMS.
| |
5.2 CustomisationBrand or personalise the LMS with standard or contributed options.
| |
5.3 AccessibilityEnsure the LMS meets official accessibility standards.
| |
5.4 InclusionEnsure access on mobile devices, via mobile browsers and the mobile app, and mobile-friendly courses.
| |
6 |
|---|
6.1 Site reportsRun, create and, where appropriate share, relevant site reports with appropriate stakeholders.
| |
6.2 Course reportsUnderstand and promote the use of course reports.
| |
6.3 AnalyticsCritically evaluate and implement where appropriate learning analytics.
| |
6.4 Event monitoringCritically evaluate and implement where appropriate event monitoring.
| |
7 |
|---|
7.1 Integration policyImplement and update plugins and other integrations in line with an institutional policy.
| |
7.2 Community contributionsInstall agreed useful plugins from the Moodle Plugins directory.
| |
7.3 Commercial add-onsConnect to agreed purchased integrations such as Student Management systems or LMS integrations.
| |
7.4 LTIEvaluate and implement requested External tools, mindful of appropriate security and privacy settings.
| |
7.5 Web servicesUnderstand and, where appropriate, enable and use relevant web services.
| |
7.6 Open Educational Resources (OER)Enable and promote the sharing of open content via Moodle.net.
| |
8 |
|---|
8.1 Community troubleshooting and collaborationReport bugs and raise queries in the Moodle community via the Tracker and Moodle.org and contribute to the Moodle docs. Contribute within the organisation's local or regional communities.
| |
8.2 Reflective practiceEngage in post-upgrade reviews, discussions with other admins, personal journals/blogging and participate in digital professional development.
| |