Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Cross-listing courses with SoPA involves an agreement between SoPA and the non-SoPA department offering the course. This type of cross-listing differs from the traditional cross-listing schema designed to allow students from multiple programs to experience the same content while registered for different course numbers. The SoPA cross-listing instead allows SoPA students taking non-SoPA courses to be assessed at the SoPA tuition rate.
  1. The student should initiate the correct form which should be signed by the student, instructor, and department head offering the course.

  2. Once complete, the form should be sent to the SoPA Associate Dean of Academic Advising, Ilianna Kwaske.

  3. Once approved, SoPA the ADAA will communicate this back to the department offering the course. Requesting the cross-list will also be communicated in the approval.

  4. The department will create the section and SoPA cross-list.

Adding the cross-list

Navigate to the section using the CRN in SSASECT. Click the More Information button.

The first field in the supplemental data table that opens is “CS-Cross List”, which is the field we’re updating. To see all values, click the lookup/search button.

Click Filter.

In the Description field, use search terms related to the subject of the course. In this example we are looking for an Art course. Use “%” as a wild card character for more relevant results. Click Go.

Because this is a SoPA cross-list, you’re looking for codes that start with “PA” (Professional Advancement), so PAAH is Art History and PAAT is Art Studio. Choose the option that best matches the course content. Click Select. Save.

About the CS-Cross List field

What’s the significance of the code options?

  • For Accounts Receivable (Mike Pilman) purposes, any value - even just “SOPA” allows the AR process to bill at the SoPA tuition rate.

  • We are unsure of how the code selected affects what’s displayed on the class schedule.

  • SoPA may use the codes for reporting and perhaps for revenue sharing. (Contact Christa Payne/Philip Lopez for more info.)

Applying the tuition policy

Tuition assessment is based on the student’s admitted school and course/section. Only applicable to undergraduate students whose primary program in term is with SoPA, and that student's registered non-SoPA course(s) has a non-null value in the CS X-list field.

The CS X-list field is not used to apply the highlighted policy. The highlighted policy is applied based on student primary program with NTC and registered course college (= 'PA') and/or registered course part of term (= 'SPE' or 'SPL' or 'SPF').

Revenue sharing

Theoretically - a graduate department could open a graduate course to undergraduates. That decision would be independent from this field value.

For the CS-Cross List field, they need to find agreement to accept a lower rate of tuition from undergraduate SoPA students (not null), or not (null). If agreed (not null), SoPA would be the receiver of revenue in this scenario, as the student's primary program school, so the graduate department would also need to enter into a revenue sharing agreement with SoPA to transfer revenue via journal entry (or not). Transfers if this nature are typically performed by mutual agreement and action by the Asst. Dean's of Finance from each school.

  • No labels