25Live Fields vs SIS Data

An event's name is a combination of several fields:

1. Always includes the subject/department code, the course number, and the section number. (e.g. MATH 200 01)
2. If enabled, includes course record number and term code from the SIS
3. If enabled, adds the following codes when appropriate:
   1. "MMP" if the section has multiple meeting patterns
   2. "XL" if sections are cross-listed in your SIS
   3. "CS" if sections are combined in Campus Solutions
   4. "BG" if sections are bound in LYNX groups
   5. "OG" if sections are in overlapping groups determined by LYNX
   6. "BTB" if sections are bound with back-to-back binding

This depends on SIS type:

• Campus Solutions: Course Title
• Banner: Course Title or Section Short Title
• Colleague: Section Short Title
• Other: Section Title

Typically all sections have the same type, or else it is determined by section type or campus code.

If sections have different types, this is determined by translation rules in LYNX.

If enabled, the instructor from the SIS is matched to a contact record in 25Live based on their email address.

Tiebreakers between multiple instructors on a section are handled by translation rules.

This is only visible in 25Live if an event has multiple meeting patterns. It includes the following:

• Days of week (e.g. MWF)
• Start/end time in 24-hour format (e.g. 0815-0920)
• Meeting pattern type (e.g. LEC)
• First meeting date (e.g. 01/06)

Can be configured to any of the following, depending on SIS type:

• Maximum enrollment
• Requested room capacity (Campus Solutions, Colleague)
• Projected enrollment (Banner, Workday)

When sections are cross-listed, combined, or otherwise bound, both expected and registered headcount can be any of the following:

• Use the headcount defined for the group of sections in the SIS
• Sum the headcounts of all sections in the group and use the total for each individual section
• Each section keeps its own headcount

Locations in 25Live are matched to the SIS based on one of the following:

• Facility ID
• Building code and room code, divided by a separator (such as a space)

Requirements for the Optimizer are based on:

• Banner: Room Attribute Descriptions
• Campus Solutions: Room Characteristic Descriptions
• Colleague: Classroom Equipment Codes