Obsolete:Site-wide groups: Difference between revisions
From MoodleDocs
No edit summary |
|||
Line 21: | Line 21: | ||
# Cohorts are visible in role assignment pages just like people, you can enrol a cohort in a course all with a particular role. A checkbox would allow you to choose whether cohort changes are mirrored as enrolments in future. | # Cohorts are visible in role assignment pages just like people, you can enrol a cohort in a course all with a particular role. A checkbox would allow you to choose whether cohort changes are mirrored as enrolments in future. | ||
We could do more, but | We could do more, but is this simple idea enough for 99% of requirements? | ||
===Design 2?=== | ===Design 2?=== |
Revision as of 06:17, 21 January 2009
Requirements
Please add concise descriptions of why you need site-wide groups here. There are quite a few different use cases around.
- We want to put a whole class of people into a group so that we can easily enrol and unenrol them together from numerous courses. (If people leave that group, should they be unenrolled from the courses?)
- We want to present a different theme to each group (with a common login page only).
- What else?
Terms
It might be confusing to think of these as part of the groups systems we have already .... perhaps it's a different complementary system?
Possible plans for discussion
Design 1
- Let's call them cohorts and keep this separate from existing groups system.
- Admin can use an admin interface to define cohorts (with name, icon, description, forced theme etc)
- Admin can use the admin interface to add users to one or more cohorts (one person could be in Students, First Year Students, and CM3004)
- Cohorts are visible in role assignment pages just like people, you can enrol a cohort in a course all with a particular role. A checkbox would allow you to choose whether cohort changes are mirrored as enrolments in future.
We could do more, but is this simple idea enough for 99% of requirements?
Design 2?
See also
The main tracker bug is MDL-11826