Instructors

Scope

Determine whether there are any instructor assignments that should be excluded from your imports to Data Management based on local practices or usage goals. These decisions should align with the scope decisions made in building the Course and Section files.

Data Relationships

The Instructors file references two identifiers that are defined in other files: SectionIdentifier and PersonIdentifier. These identifiers must either be present on the instructors assignment tables or be able to be mapped through another table or view to match the identifiers used in the Sections and Accounts files.

Instructor Role

This field should be populated with “Primary” or “Secondary” using case statements based on the data in the SIS.

Term Logic

Term logic for instructors depends on institutional policies and processes. Consider when instructors are added to sections, how many changes are made before the term begins, and whether you can automate a Remove Instructors file (see the section below). For example, if instructor assignments change frequently in the lead-up to the term and you are unable to automate removing instructors, it may be wise to begin loading instructors closer to the start of the term. If you can automate removal, consider loading them earlier to capture a more comprehensive view of processes on campus. Balance these decisions with an assessment of how long before the term faculty will need access to their rosters within the tools. The Instructor term logic should then run through the end of the term, so that any changes to instructor data that happen throughout this time period is brought over each night.