| Overview | Importing This File |
| Video Explaining This File | Products That Use This File |
| Populating This File | Next: Academic Terms |
Overview
This file establishes the organizational structure to be used for access and reporting. It should not be automated and any changes require significant discussion with Campus Labs Support. However, the initial file that you load manually can be created from a script and should reflect data found in the SIS.
The organizational chart may include both academic affairs and student affairs depending on how your products are licensed. The units should represent the “lived” experience on campus and describe offices rather that people (this is not a human resources organizational chart). Think about where your reporting needs lie, along with your identified goals. Discuss what units your campus needs with your onboarding consultant.
Video Explaining Organizational Units
Best Practices for Populating Organizational Units
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.
Suggested SIS Tables
Important Information About Importing This File
Import Order
Organizational Units must be sent and uploaded BEFORE any other course data is sent to Campus Labs.
Record Updates
Once an Organizational Unit has been created it cannot be deleted. It is important to have your Organizational Unit file as accurate as possible before it is imported. The name, acronym, parent identifier and type of a unit can be updated by importing an updated file with the new information.
Products that use Organizational Units
| Product | Required | Optional | Not Applicable |
| Baseline - Rubrics |  |
||
| Beacon |  |
||
| Course Evaluations | |
||
| Engage | |
||
| Insight | |
||
| Outcomes | |
||
| Planning | |
Requirements for populating this file can be found in the Core Data Dictionary.
Comments