Cross-Listing Procedures for Data-entry in PS

Note: This document is subject to change due to the forthcoming Oracle PeopleSoft system upgrade from version 8.0 to 8.9.

Introduction

The College Registrar’s Working Group (CRW) was charged with the task of defining procedures for entering cross-listed courses into PeopleSoft (PS.) There are three types of course relationships: cross-listed, co-listed and cross-level.

Cross-Listed Courses

Cross-listed courses are identical in all aspects except its “offering” subject and number (plus other associated information on the offering.) All cross-listings have the same short title, long title, description and academic requirements. In PeopleSoft we will call these multiple offering courses.

Co-Listed Courses

Co-listed courses are connected to another by similar subject matter, but do not have to have the same academic requirements, such as components, requisites, topics, etc. Usually one or more of the components are taught in the same classroom and by the same faculty. In PeopleSoft co-listed courses will not be set up as a multiple offering course, but as two separate courses joined at the class level as co-meeting classes (combined sections.)

Cross-Level Courses

Cross-level courses are connected to another course or courses by similar subject matter. Cross-level courses do not have the same academic requirements. Cross-level courses are taught usually within the same department and are usually graduate and undergraduate levels courses. In PeopleSoft cross-level courses will not be set up as a multiple offering course, but as two separate courses joined at the class level as co-meeting classes (combined sections.)

Assumptions

The Associate Deans of the colleges will determine a university wide approval process for cross-listed courses. Cross-listed courses impact transcripts, degree progress, Courses of Study and class rosters. There needs to be a process where all cross-listed offerings have been approved and the offering departments/colleges have “signed off” on the cross-listing. This is especially important for out of college course offerings. This approval process would also include course offerings that decide to not to cross-list, whether it is the “parent” or the “child” course offering or the course is not offered any more.

Decisions Made

• For cross-listed courses, the first offering on the course will be considered the “parent” offering. The “parent” course offering will be responsible for all the academic information for the course. Financial arrangements and considerations (deals made on the side by colleges) should be kept separate from the course information.
• The actual recording of the “parent” and “child” course offering relationship will be on the class level.
• For course data entry, the “parent” offering will enter all course information and all offering information for the course.
• The “parent” offering controls all the information for the course. The “child” offering should not make any changes on the course.

Other Considerations

Process for on-going maintenance. Examples: “child” offering no longer wants to cross-list, “parent” course no longer is offering the course. How do we handle that in PeopleSoft? This will need to be tested and procedures developed.