What does the 'courses' classification do?  I can see it only relates to modules.  I use 'groups' to differentiate programmes as this has more relationships than courses.

I understand the concept that courses can be used to link modules.

In the FE sector, certain modules are common to more than one course. If that is the case, how does CELCAT determine the timetabled events for that module as related to one course as opposed to when that module is timetabled as part of another? Are the generated reports indeed course specific?

Further to that, a full time course may run over a period of up to 4 years. The individual modules related to that course will be delivered in one of the years over which the course is run. How would CELCAT determine the timetable for each of the associated year groups? I do realise that I could enter each 'group' in turn, but it would be far easier to select a course and get timetables for each of say 4 year groups (Who may be divided into sub-groups A, B, C etc. for the larger groups, so 4 x 3 = 12 timetables).

We haven't used the course option to date but I intend to do so in the future.

Hi Martin and others

I've tried to set up courses (with linked modules) in the past and never had much success.  I can't work out how to link groups to the master course.  So would be great to know who the whole system of courses/groups/modules works.

Margo

The relationship of courses, groups and modules is obviously causing some confusion. A proper guide would be useful (Yes I have read the manual).

The central point seems to be the group. The ability to nest groups pulls together the year groups on the course and the sub-groups within the year (Using the 'Add Groups' button on the 'Members' tab of the 'Groups' record. The modules can then be added for each particular group as 'preferred' resources.

What confuses me is:

What does the nesting of groups actually achieve?

There does not seem to be any inheritance going on. i.e. Create a top level group to represent the course (non-schedulable), Create groups for each of the years (non-schedulable) and finally create groups to represent the year sub-groups A, B, C etc (schedulable). Each sub-group within the year group will be taking the same modules, so it would be useful to assign the modules to the year group and for them to be inherited by the year sub-groups. Also it would be useful to assign students to each of the sub-groups and for them to be inherited by the year groups and thereby to the course top group (All students in the year, all students on the course over all of the years). So basically preferences downwards and members upwards.

Is there a document somewhere that describes the rationale of the way groups etc. have been implemented?

Some guidance please.