Development:Cohorts: Difference between revisions
| Line 125: | Line 125: | ||
# New options for sync with external groups in auth or enrol plugins | # New options for sync with external groups in auth or enrol plugins | ||
= | =Implementation steps= | ||
# add db tables and cohort membership UI | |||
# add option to assign role to all cohort users (one time only, no sync) | |||
# enrolment rewrite | |||
# cohort enrolment plugin | |||
=Upgrade= | =Upgrade= | ||
Revision as of 13:08, 17 April 2010
Note: This article is a work in progress. Please use the page comments or an appropriate moodle.org forum for any recommendations/suggestions for improvement.
| Cohorts | |
|---|---|
| Project state | Proposal |
| Tracker issue | MDL-21781 |
| Discussion | n/a |
| Assignee | Petr Škoda (škoďák) |
Moodle 2.0
Goals
Site-wide groups (aka cohorts) is one of the most requested missing features.
- Simplify manual enrolments - instead of enrolling students one by one, it would be possible to enrol a cohort with single click.
- Cohort enrolment plugin - new enrolment plugin synchronising users in cohort with enrolments in a course (including role assignment and group membership)
- Synchronisation with external systems - some external systems do not know the actual courses, they only contain some user groups, at present we do not have a simple way to reuse these groups in Moodle.
- Partially replace meta courses - metacourse is a confusing concept for many people, there are several unsolved problems and performance issues.
- Replace category enrolments - category enrolments have major design issues and are not compatible with proposed enrolment changes.
DB tables
Table cohort definition of site-wide groups (aka cohorts)
| Field | Type | Default | Description |
|---|---|---|---|
| id | int(10) | auto-incrementing | |
| contextid | int(10) | foreign key, references context.id | |
| name | char(255) | human readable cohort name | |
| idnumber | char(100) | unique identifier of the cohort, can be used in external systems | |
| description | text | longer description | |
| descriptionformat | int(2) | text format | |
| contactid | int(10) | foreign key, optional user id of person responsible for the cohort | |
| source | char(100) | full plugin name of a component responsible for assignment of users (ex: auth_ldap, etc.), NULL means manual assignments | |
| timecreated | int(10) | timestamp, creation date | |
| timemodified | int(10) | timestamp, last modification |
Context specified can be system or course category level, defining of cohort a course context would not make much sense.
Table cohort_members stores cohort members
| Field | Type | Default | Description |
|---|---|---|---|
| id | int(10) | auto-incrementing | |
| cohortid | int(10) | foreign key, references cohort.id | |
| userid | int(10) | foreign key, references user.id | |
| timeadded | int(10) | timestamp, when added |
New capabilities
- moodle/cohort:assign - add/delete members (only for manual assignment cohorts with source == null)
- moodle/cohort:contactassigns - course contact user may add/delete members (only for manual assignment cohorts with source == null)
- moodle/cohort:manage -add/delete/move cohorts
- moodle/cohort:view - view membership and use cohort elsewhere
Context id defined in cohort table is used for access control only, the cohort may be actually used in any context (this may happen when moving courses, categories or cohorts).
User interface
- Cohort edit link in CONTEXT_SYSTEM and each CONTEXT_COURSECAT- most probably from the settings block
- Option for manual cohort enrolment - part of new enrolment UI
- New UI in cohort enrolment plugin
- New options in group creation UI
- New options for sync with external groups in auth or enrol plugins
Implementation steps
- add db tables and cohort membership UI
- add option to assign role to all cohort users (one time only, no sync)
- enrolment rewrite
- cohort enrolment plugin
Upgrade
No upgrade required in 2.0 because it is a completely new feature.
Complex upgrade code will be necessary for replacement of category enrolments (there is no way this could work with proposed enrolment tables). The replacement of meta courses is optional because we could implement a separate new meta course enrolment plugin.
