This page is a guide to event fields in 25Live and how they match up to the various data points in your student information system.
|Field in 25Live
|In Your SIS
An event's name is a combination of several fields:
This depends on SIS type:
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.
|An event's organization is based on either a section's department code or subject code, then passed through translation rules in LYNX.
|These contact roles are determined by the system integration between LYNX and 25Live.
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.
|The description contains all instructor names, even if they are not added as contact roles.
This is only visible in 25Live if an event has multiple meeting patterns. It includes the following:
Can be configured to any of the following, depending on SIS type:
|Displays the number of registered students
When sections are cross-listed, combined, or otherwise bound, both expected and registered headcount can be any of the following:
Locations in 25Live are matched to the SIS based on one of the following:
Requirements for the Optimizer are based on:
|Categories and Custom Attributes
|Many LYNX configurations add categories or custom attributes to an event in 25Live based on SIS data, including term codes, campus codes, and more.