When an import job is run the system compares the SIS section and meeting records to the section and meeting records in Astra Schedule that match the parameters in the job. If the section or meeting does not exist, it is inserted as a new record as described above. If the record exists in Astra Schedule and the SIS activity date is more recent than the activity date in Astra Schedule, then the record is updated to reflect changes.
During the record comparison, section records are identified using the combination of term and a unique key (SISKEY). The unique key may be a value provided in the SIS or a combination of values used to create a unique value. Section meeting records are identified similarly. Depending on the SIS data structure, an additional component such as the table row ID may be used to help determine the identity of records.