LYNX is a bridge between two separate databases: your student information system (SIS) and 25Live. The same objects exist in both (such as sections, classrooms, subject codes, etc) but may have different names. In order to keep them all related, LYNX maintains a list of rules to translate between these two databases.
The Data Translations area of LYNX is where you set up the translation rules between your SIS and 25Live.
Adding Translation Rules
To add or change translation rules in LYNX:
- Log in to LYNX and select Configuration > Data Translations from the More menu in the upper right.
- Double-click the translation group you wish to edit, or select it and click Edit.
- Click Edit or Delete on any line to modify an existing rule.
- Click Add New Rule in the lower left to create a new rule.
- Use the boxes provided to select specific items in your SIS or 25Live. LYNX provides suggestions based on what you type.
- When editing or creating a translation rule, you can make it inactive. LYNX will behave as though the rule does not exist, but it is not deleted.
You must reimport extract sets for any changes to translation rules to take effect. Note, courses/events may not import unless they are part of an active extract set.
When to revise your translations
Typically you will not need to change anything configured here after your initial installation unless your system has changed. You may occasionally need to modify your data translation rules if:
- Another term code category has been created
- You have new campuses or buildings in your system
- Departments have been added or removed since the last term
- There are new room requirements you want the Schedule25 Optimizer to recognize
Note that all these changes also require data changes in 25Live, so make sure any new data has also been entered in 25Live.
How Translation Rules Work
All translation rules operate on the same basic principle: If you see X in the SIS, import it as Y in 25Live. (The rules are applied in reverse when exporting.) Each translation group in LYNX has two types of rules: those which call out a relationship between specific items, and those which set up a general pattern for everything else to follow.
Typically a single general rule is all that is needed for a LYNX translation group to function.
Some rules are very precise about what translations they represent. In the example below, the term code 2020WHFA is translated to the event category Fall 2020. This means that every time LYNX encounters this specific term code, it will match it to an exact category in 25Live.
Other rules are slightly broader but still targeted at a specific set of items. In this example, every term code ending in FA (such as 2020WHFA, 2021WHFA, 2022WHFA) is translated into the same event category, Fall Term. This rule takes care of all fall terms without requiring an administrator to set up a distinct rule for each term code.
General ("Else") Rules
General rules exist as a backup option for all the cases not covered by specific rules. Every set of translation rules has a single rule labeled "Else" which cannot be deleted, only edited. LYNX applies this rule whenever there are no other rules it could use instead.
"Else" rules are set up differently from other rules. Instead of typing in selections for IF and THEN, you make a single selection. The options depend on the data being translated, but generally include:
- No translation (Use when you don't want LYNX to match this data with anything in 25Live)
- SIS data (Most common option; LYNX will look for 25Live data which matches a code or description field in the SIS exactly)
- Specific target (Use when you want to map all SIS data to a single "default" target)
Often an "Else" rule is all you need, most commonly when you have constructed your 25Live data to match your SIS data. In the example below, a single "Else" rule maps a translation between subject codes in the SIS and organization names in 25Live. When LYNX imports sections, it will use organizations whose names exactly match the subject codes.
Previewing Translated Results
Before importing anything to 25Live, you can check your work to make sure that all your translation rules are set correctly.
Click View Translated Results below any set of translation rules to open the translation results preview window.
In the window that appears, you'll see a list of all the original data in the SIS (in this case, term codes) as well as the way LYNX will translate it. The Valid? column on the right indicates whether a match is found in 25Live.
Data Translation Groups
There are over a dozen total translation groups supported by LYNX, but only a few are visible at any given time. LYNX automatically hides any groups which are not relevant to your configuration. (Such as hiding department code translations when you have chosen to use subject codes for your 25Live organizations.)
The full list of translation groups is presented below, along with the SIS types supported by each. (Please note that LYNX Universal supports all translation groups.)
Some SIS data elements can be translated into multiple fields in 25Live; each translation group is managed separately.
Academic Career Code
|Combines the building code with the (untranslated) room code to match a 25Live location.|
|Campus Code||Time Zone||All|
Only used by multi-campus institutions.
See the "how time zones are mapped in 25Live" note on LYNX Settings - General.
All SIS types can append campus codes to the organization name.
Banner, Campus Solutions, and Universal can append institution codes.
Facility ID (Location)
If multiple SIS instructor roles are mapped to the same contact role in 25Live (as with an Else rule), then the first instructor in the SIS will be the only one added in 25Live.
Feature preferences are used by the Schedule25 Optimizer.
Section Type Code
Allowed event states:
|All||Banner, Campus Solutions, and Universal can append institution codes.|
|Subterm Code||Event Category|
|Known as "Part of Term" in Banner.|
|In addition to matching specific codes, rules can match Starts With or Ends With.|