Flexible Curriculum User’s Guide<>

Setting up cross-sessional modules and courses

What is a cross-sessional course?

Courses and modules* can be independent of the traditional ‘academic session’. These types of courses and modules are know as cross-sessional.

In previous versions of Quercus 8:

course instances and module instances were linked to academic sessions (usually equivalent to the academic year)

you could only set up one instance of a module for a given year — based on the assumption that a module would only be taught once on a particular course in a particular year

This gave rise to two issues:

Course instances that spanned more than one academic session would have to be recreated in each of the subsequent sessions and the students rolled over from one course to the next.

If you wanted to make the same module available at different times within the same year, or perhaps with slightly different options, you would have set up a ‘new’ module which would duplicate the core data in the original module.

Although you would know they were the same course or module, the software would not know they were linked – complicating reporting and giving rise to additional data maintenance tasks.

In contrast the new flexible curriculum features allow you to build courses and modules which are not linked to particular academic sessions. These courses and modules have start and end dates which can be set independently.

Cross-sessional and ‘traditional’ courses — comparison

Scenario

An institution’s archaeology qualification is split into three separate year-long courses: introduction, intermediate and advanced.

The courses are part-time and aimed at adult learners; the institution runs two instances of each course per year for different intakes of students.

The start and end dates of the first course instances coincide with the start and end dates for the academic session.

The start and end dates of the second course instances begin six months into the academic session and finish six months into the next academic session.

Implementation of the scenario without flexible curriculum using ‘traditional’ courses

In the example below, flexible curriculum is not enabled.

The courses that cross the academic session boundaries have to be split into two separate course instances (Part 1 and Part 2 in the diagram). Students have to rolled over from one course to another at the end of the academic session.

Implementation of the scenario with flexible curriculum using cross-sessional courses

In the example below, flexible curriculum is enabled. Courses can now cross academic session boundaries — so the courses no longer have to be split.

» For more information see:

Setting up courses based on academic sessions (‘traditional’ courses)

Setting up course instances that cross academic sessions

Setting up ‘traditional’ single-session module instances

Setting up module instances that cross academic sessions

Viewing cross-sessional courses

In the older Quercus 2.7 screen

The year (academic session) picker is available in the filter area in the top left of the earlier screen. All of the courses shown are linked to the 2010 session.

In the new Quercus 8 screen:

The year (academic session) picker is no longer in the filter area (though it will reappear if you set the session type to single session).

The Show Current check box appears above the list of modules.

The Session Type selector has been added to the filter area.

Session Type indicators have been added to the individual list rows (use the scroll bar at the bottom of the list to view these).

Setting up module instances that cross academic sessions

Note: When you are setting up a cross-sessional module instance you must set the session type before you save the module.

To set up a cross-sessional module instance

1In the Quercus Classic Interface navigate to the Module Maintenance screen of the appropriate course (Course Manager > Module Maintenance > Maintain).

2Select a module instance by clicking the Open Record icon.

The Module Instance Detail screen opens.

3On the first empty row, click in the Year field and enter a year.

Note: it is unimportant what year you enter if you are creating a cross-sessional module.

4Click the Open Record icon.

The Module Instance Detail screen opens.

5Choose Cross-sessional instance from the Sessional list.

Note: you must do this before you save the module.

6Enter other details you want to capture such as the Start and End dates and the number of Credits.

7Click the Save icon in the toolbar or press F10 to save the record.

8Click Previous to return to the list of module instances.

Setting up course instances that cross academic sessions

To set up a cross-sessional course instance

1In the Quercus Classic Interface navigate to the Module Maintenance screen of the appropriate course (Course Manager > Module Maintenance > View/Maintain).

2Select the course for which you want to set up the cross-sessional instance.

3Click the Instances button.

A list of instances associated with the course opens.

4Set the Session Type field in the filter area to Cross-sessional instance.

5Click in the Code field and enter a code for the new instance.

6Add the dates and location for the course.

7Scroll to the right and set the session type to Cross-sessional instance.

8Enter any other details you wish to add at this stage, such as the start and end date, the course location and the course structure.

9Click the Save icon in the toolbar or press F10 to save the record.

The course is saved with the Status set to Course Instance Open and the Mode of Study to Undergraduate (unless you entered alternative settings for these fields manually).

To create a course instance linked to an academic session by copying a similar instance

1Follow steps 1 to 4 of the To set up a cross-sessional course instance procedure (above).

2Click in the Code field of the instance you want to copy.

3Click the Create Like button.

A dialog appears asking you if you wish to continue.

4Click OK.

A new course instance is created with the code id_X where id stands for the identifying code of the original course instance. ‘_X’ is a placeholder which you can replace with a suitable identifier. All other details of the course will be copied including the Year, Start and End Dates and the course structure.