LYNX Settings - General

These settings can be found in the "General" area of LYNX's Configuration - Settings area. 

Setting

Notes

Delete Cancelled Imported Sections

When the Status Code Data Translation Table interprets a section as Cancelled in the SIS, this setting determines whether it will be retained in 25Live with a "Cancelled" event state or deleted entirely. 

If a section has an exam, the exam will be cancelled/deleted as well.

LYNX Notification Email Recipients

The listed recipients will be alerted with email updates for critical LYNX Status and System Messages as well as rare patches and updates required for the LYNX database schema. These alerts are intended for technical administrators rather than classroom schedulers.

System errors after a database copy

The process of copying production data into a test environment can trigger system errors that can be safely ignored. You may want to leave this setting blank in your test configuration so that administrators do receive irrelevant emails.

25Live Import Email Notifications

25Live Import Email Recipients

These settings control who will receive email updates when sections are imported and exported from LYNX, as well as how often those updates occur. These alerts are intended for schedulers rather than administrators.

Emails are sent on the basis of import "chunks" consisting of about 500 sections each. Thus, a term code consisting of 5,000 sections could generate up to 10 emails (one per chunk) if all sections are imported at once.

Imports (or exports) generate emails based on the severity of the import messages, which are classified as Error, Warning, or Info. Depending on your configuration, LYNX will send an email when a section is flagged with an error, an error/warning, or an error/warning/info message.

Academic Priority

Academic Priority Email Recipients

Academic Priority Email Recipient List

Academic Priority is the ability for LYNX to resolve classroom conflicts by unassigning an event scheduled in a classroom and booking an imported class in its place. If enabled, it will only replace non-academic events in conflict with assignments imported from the SIS.

Depending on your configuration, emails can be sent to the replaced event's Scheduler contact role and/or a list of addresses defined in LYNX. The recipient of the email is responsible for following up and finding a new location for the replaced event.

Define Section Time Zone by Campus Code

This setting enables the Campus Code to Time Zone Data Translation table. It is intended for schools that have multiple campuses in different time zones.

How Time Zones Are Mapped in 25Live

If you are a single-campus institution, the "else" rule is sufficient here. However, if you have multiple campuses across the country or the world you will find this very useful. Add a rule for each campus that sets it to the correct time zone, and when LYNX imports classes it will adjust their starting times relative to the system time zone in 25Live.

For example, a school has a campus in New York and one in Los Angeles. Because New York is the main campus, all class times are entered in the SIS using EST/EDT. With no translation configured, the first class of the day on both campuses shows up in 25Live as 9:00 am EST/EDT. Published calendars based on this data will be unreliable. With translation configured, the NY class is imported with a starting time of 9:00 am and the LA class is imported with a starting time of 6:00 am. This works better for both published calendars and the personal time zone preferences of LA users.

Filter Data by Institution Codes

Filtered Institution Codes

(Campus Solutions & Universal only)

These settings are designed to be used by schools that have multiple institutions that share a Campus Solutions or Universal database but need to separate 25Live/LYNX data by institution. 

Image: The Filter Data... setting is available for Campus Solutions and Universal instances.

If enabled for Campus Solutions instances, data in an extract set's criteria (such as campuses and subjects) is automatically filtered by institution code without needing to set import extract set criteria, and all data visible in the LYNX user interface is filtered according to this configuration.

If enabled in Universal instances, you may enter an institution code to filter section data in the LYNX-UI when an extract set is reviewed for import or export. Other data is not filtered. Note: This setting is disabled by default in Universal instances.

Because it involves some processing overhead, this setting should NOT be used by multi-institution schools that simply want to automatically filter out unused institution codes and prevent them from appearing in 25Live entirely. You will have better performance simply filtering them out using extract set criteria.

Filter Data by Campus Codes
(Universal only)
Image: Universal instances can Filter Data by Campus Codes.

Similar to the "Filter Data by Institution Codes" option above, Universal instances can filter by campus codes when enabled.

Because it involves some processing overhead, this setting should NOT be used by multi-institution schools that simply want to automatically filter out unused institution codes and prevent them from appearing in 25Live entirely. You will have better performance simply filtering them out using extract set criteria.