Cross-List Options : Course - Edit

NON-SHARED FIELD CHANGES (e.g. Subject Code/Catalog Number/Requisites Change) - 

1. One proposal for each of the courses changing their non-shared field information will need to be submitted.
   1. *HOWEVER, the proposals will need to be submitted one at a time, and secondary proposals will need to wait to be submitted until a previous request has been fully approved and the changes implemented. If multiple proposals are submitted and processed at the same time, it will cause errors when the changes are being implemented.
2. If multiple courses are changing AND information in shared fields is changing -
   1. Submit a proposal for one of the courses that includes all of the needed changes (including changes with shared and non-shared fields).
   2. Wait for the proposal to be fully approved and the shared field changes implemented to all the courses in the cross-listing.
   3. Then, one-at-a-time submit proposals for the other courses in the cross-listing that need to change their non-shared information.
   4. *As specified above, if multiple proposals are submitted and processed at the same time, it will cause errors when the changes are being implemented.

SHARED FIELD ONLY CHANGES - 

1. Submit only one proposal with the required changes. This proposal should route to all impacted departments for approval and the changes will be applied to all courses in the cross-listing upon being fully approved. 

1. The courses need to be similar enough to justify being cross-listed.
2. To be cross-listed, courses need to have the same PeopleSoft Course ID. Therefore, the course that is being added to the existing cross-listing will lose its ID, essentially becoming a new course. So, rather than submitting an edit proposal the following should happen -
   1. Submit a proposal to inactivate the course that will be losing its Course ID.
   2. Submit a new course proposal requesting to be added to the existing cross-listing.
      1. You will need to select a new catalog number on the new course proposal as there is a renumbering policy that prohibits the re-use of a number for at least 5 years after it has been inactivated. And our office recommends NOT reusing catalog numbers, when possible, to avoid confusion in degree audits and on the backend.

1. Rather than submitting a course-edit proposal, a new-course proposal should be submitted instead.
   1. If other changes to shared course information need to happen, make those changes on the new course proposal and specify in the 'Reasons the Changes Are Being Requested' field the changes you're making and why. If this isn't included our office will consider the courses to be a mismatch and will not accept the proposal. We need to know that the changes are intentional and desired to be applied to all courses in the cross-listing.

This type of request is not allowed and there is a rule on the form to prevent it from being submitted. 
If the courses have changed enough to no longer be cross-listed, then an in inactivation proposal will need to be submitted for the courses that have changed (or the entire cross-listing) and new course-proposals will need to be submitted. 

1. The courses need to be similar enough to justify being cross-listed.
2. To be cross-listed, courses need to have the same PeopleSoft Course ID. Therefore, the course that is being added to the existing cross-listing will lose its ID, essentially becoming a new course. So, rather than submitting an edit proposal the following should happen -
   1. Submit a proposal to inactivate the course that will be losing its Course ID.
   2. Submit a new course proposal requesting to be added to the existing cross-listing.
      1. You will need to select a new catalog number on the new course proposal as there is a renumbering policy that prohibits the re-use of a number for at least 5 years after it has been inactivated. And our office recommends NOT reusing catalog numbers, when possible, to avoid confusion in degree audits and on the backend.

1. The courses need to be similar enough to justify being cross-listed.
2. To be cross-listed, courses need to have the same PeopleSoft Course ID. Therefore, only one of the existing courses will retain its PeopleSoft Course ID and the others will essentially be new courses. So, rather than submitting an edit proposal the following should happen -
   1. Submit a proposal to inactivate the course that will be losing its Course ID. This will need to be done for all courses losing their ID.
   2. Submit a new course proposal requesting to be added as a cross-listing to the existing course. This will need to be done for all courses that lost their ID.
      1. You will need to select a new catalog number on the new course proposal(s) as there is a renumbering policy that prohibits the re-use of a number for at least 5 years after it has been inactivated. And our office recommends NOT reusing catalog numbers when possible to avoid confusion in degree audits and the backend.

1. Rather than submitting a course-edit proposal, a new-course proposal should be submitted instead.
   1. If other changes to shared course information need to happen, make those changes on the new course proposal and specify in the 'Reasons the Changes Are Being Requested' field the changes you're making and why. If this isn't included our office will consider the courses to be a mismatch and will not accept the proposal. We need to know that the changes are intentional and desired to be applied to all courses in the cross-listing.