Prepare Scheduled Unit Records

This page will discuss the fields to check and review in Scheduled Units recorded in Paradigm to match with the Rapla created Paradigm Session events.

Overview

Scheduled Unit records in Paradigm with the matching Paradigm Sessions event type created in Rapla should already exist before you attempt to sync the data from Rapla to Paradigm, see Trigger Import. This knowledge article will discuss the fields in your Schedule Unit records in Paradigm that you need to create, check and review if they're matching to your soon-to-be imported sessions in Rapla.

Time Period

All Paradigm Session event types created in Rapla should be within the Scheduled Unit’s Start Date and End Date fields in Paradigm which are also the same or within the Time Period (Academic Term) created in Rapla, see Create Time Periods.

Paradigm Scheduled Unit Fields

Each event in Rapla that differs in the following fields should have an equivalent Scheduled Unit record in Paradigm:

Unit Code

For each unique Unit Code Paradigm Session event type, there must be an equivalent Paradigm Scheduled Unit record in the system where the sessions are stored.

Campus

If you have multiple campuses, an event with the specific Campus or Home Institution value should be created and should have an equivalent Schedule Unit in Paradigm with the same Campus or Home Institution field.

Delivery Mode

If a Scheduled Unit has two delivery modes, e.g. Online and On-Campus, there should be two Scheduled Unit records in Paradigm each of them containing a different delivery mode, e.g. BEM101 Online and BEM101 On-Campus.

Last updated