Organizational Units

However, the initial file that you load manually can be created from a script and should reflect data found in the SIS.

OrgUnitIdentifier source

The unique organizational unit identifiers defined in this file are used to link courses, sections, and academic programs to their appropriate organizational units. If a particular organizational unit is intended to link to any other file, its identifier MUST be present in the SIS in a way that can be mapped to the courses, sections, and academic programs. Before you build your organizational units, assess what types of identifiers are linked to your course and section data. These stipulations do not apply to any organizational units that are not intended to contain courses.

Levels and Parentage

Because this file establishes a hierarchical structure, each organizational unit must have a parent identifier linking it to the unit to which it belongs. Each level of the hierarchy also has a type, defined by an enumerated value as listed in the data dictionary. An organizational unit can be the parent unit of a unit with the same type.

Only one unit should be labeled with the Type Institution, and only the Institution Organizational Unit should have a blank field for the Parent Identifier column.  All other Organizational Units will need to have that field populated.

If you are building this file from a script, each unit will need to map to its parent in the SIS or be defined by case statements.