2022-02-28 Pre-Registration (CourseLeaf Path)

2022-02-28

Main topic: Where we are, next steps

Where we are:

  • Identified incoming students and their primary majors and a selection for appropriate courses

  • Select one of the following

  • Cannot include narratives, must follow a format

  • Can format as wildcard SOCI 1XXX (any 1000-level SOCI course)

  • We have edit access to replace spreadsheet (edits done on nextcatalog site: https://nextcatalog.tulane.edu/nsoreg/)

  • “Or”: try for Option A and if Option A is closed, register for Option B

  • Without “Or”: 50% of the population sees Option A and the other 50% sees Option B

  • Set up each four letter code with counts. For pre-meds, create a code and a number count even if they’re not in the respective major. (For us, it’s about 40% of the incoming class.)

  • To submit ZZPM (pre-med) Column 1 Student ID, Column 2 which of the environments are they going to run.

  • How this helps us manage enrollment in our sections

  • Report by student shows what we attempted to register them for and the outcome (success/fail)

  • Course 1 - best option, Course 2, worst option, Course 3 best option, etc.

 

Next Steps

  • Earliest rough draft is after continuing students register - week of 4/18 - can even use last year’s counts if needed

    • Spring reg for continuing, April 6

    • 400 incoming Honors have already registered, deposit deadline May 1 > clean up primary majors if they changed > run this CL tool (2nd week May)

  • After rough draft, we can make changes

  • To have CL register, they need access to the API. They need the Banner Student API. (This is separate from the bridge.)

    • API set up url looks like /studentapi/api

    • IP address of the API: 12.2.169.16

  • Registration will take about 45 minutes to push, but it’s done one at a time, so there won’t be a hard load on the system.

 

Discussion

CL needs category counts from us.

Encrypting IDs an issue?

No. We need to figure out how to send the IDs to CL securely, which can be done. (ID, major, whether or not they’re pre-med)

How is this working at other schools?

  • Can be used for all populations (UPenn http://courses.upenn.edu > explore programs, Degree audit & advising) Demo at E-Live in Denver next week

    • hooks to degree audit (not plans)

    • system can tell students what’s missing from their registration cart

    • allows requesting permission

    • add/drop/swap - manage classes

    • registration cart - look ahead audit

    • “imagine this as my program”

  • Is reporting available? Yes.

    • Course demand report

    • Planned - # students with the course in the cart

    • Not-Yet-Planned

    • Cart - for specific sections, Plan - for a course

  • Registration optimization

    • 2 weeks to build

    • Institution adjusts

    • push optimized reg results pushed into SIS (approx 90 minutes)

    • Students adjust schedules

    • Optimization is fluid. Student #30 can be pushed to Student #31 if one of the 30 didn’t get their chosen section and this section is their second choice.

  • Choices

    • Priority, first alternative, second alternative

  • Reserved seating