For completeness' sake, I'm adding the results of the discussions with Celcat support and our findings. To summarise, we have defined 'common' modules once, e.g. 'Functional Skills' as they can be delivered within any course within any Curriculum Area. This way we don't incur data redundancy. When we define a course, we relate the modules to the course, so in this case, 'Functional Skills' will be related to many courses. We now timetable a Group, with the 'Functional Skills' module, and when complete, we run a Course Timetable Report. What happens is that our timetable report now shows ALL events where 'Functional Skills' has been timetabled, irrespective of Course, Department, Room, Staff etc., etc. Celcat support have confirmed that the Course Timetable Report extracts all modules related to that course and then extracts all events where each module is present - 'it just works this way'. So, I guess the moral is, either (a) incur data redundancy by declaring the same module multiple times or (b) don't use the Course timetable report. |