img:is([sizes=auto i],[sizes^="auto," i]){contain-intrinsic-size:3000px 1500px} /*# sourceURL=wp-img-auto-sizes-contain-inline-css */

红杏视频

Skip to content

Import Institutional Data

Back to Table of Contents

Overview of Institutional Data Imports

The second step in preparing IASystem鈩� to manage course evaluations is to import three required institutional data files.聽 This data includes required information about instructors, courses, and class lists for each term.

Setup Term Step2

IASystem鈩� provides Excel (.xls) templates for all 3 file uploads; however, for large data sets we recommend that you save as a 鈥淐SV鈥� file and then import the data in that file format.聽 Please review the instructions and data definitions in each data file template.聽

Data uploads must occur in this order:

  1. Instructors
  2. Courses (Time Schedule)
  3. Class Lists (Students)

InstitutionalData

Upload Behavior and Dependencies for Institutional Datafiles

Institutional files are uploaded within聽滨础厂测蝉迟别尘鈩�聽one or more times per term to keep client faculty, student and course data up-to-date.

If re-importing data after the initial upload, please be aware that authorized users can also manage instructor and student data within a course via the Manage Instructors and聽Students feature. 聽Since institutional data imports are considered the primary data source, if a user modifies instructors or students in a course and datafiles are re-imported later in the term聽without the聽same updates, the institutional data being imported will override previous local edits.

Note: 聽It is important to ensure instructor and student edits are also updated in the聽original data source if data imports will be refreshed throughout the term. 聽An institution’s data imports are considered the primary data source and always “win.”

Instructors File

Import behavior:

  • Adds new and updates existing records.
  • Enduring list; preserves existing faculty records between terms.
  • First matches on username, then employee ID.

Dependencies: 聽None

Courses File

Upload behavior:

  • Adds new and updates existing records for a selected term.
  • Existing records not present in the upload file are left unchanged.
  • Does not remove courses that were in previous uploads.
  • Matches on unique course ID number within the term
  • Has an optional 鈥淎ssigned Instructor鈥� field that identifies if the course type is “Assigned Instructor”聽– A zero or blank field means this course is not an “Assigned Instructor” course type. 聽The number one (1) indicates this course is an “Assigned Instructor” course type.

Dependencies:

  • Course abbreviation must exist in institution course tree.
  • Instructor IDs must exist in IASystem from a Faculty File upload.

Joint Courses:

Representing joint sections is flexible within IASystem鈩�.聽 Here is an example of a Courses File upload template with three courses, each made up of three sections:

Course ID
Abbreviation
Number
Section
Title
Credits
Employee ID
Joint ID
90001 MATH 400 A Math 400 Test Course 5 Fac007
90002 MATH 400 B Math 400 Test Course 5 Fac007 90001
90003 MATH 400 C Math 400 Test Course 5 Fac007 90001
90004 MATH 401 A Math 401 Test Course 5 Fac007 90004
90005 MATH 401 B Math 401 Test Course 5 Fac007 90004
90006 MATH 401 C Math 401 Test Course 5 Fac007 90004
90007 MATH 402 A Math 402 Test Course 5 Fac007 90008
90008 MATH 402 B Math 402 Test Course 5 Fac007 90009
90009 MATH 402 C Math 402 Test Course 5 Fac007 90007

 

The following methods of joint course representation are commonly found at institutions and are supported within IASystem鈩�.

Parent-Child Joint Relationship

In the example above, the first two courses 鈥� MATH 400 and MATH 401 鈥� represent jointedness in a 鈥減arent-child鈥� or 鈥渢ree鈥� fashion.聽 One section was chosen (it doesn鈥檛 matter which) and all sections joint with it are assigned its Course ID.聽 In the MATH 400 example, the parent section has no Joint ID value; while in the MATH 401 example, the parent uses its own ID as its Joint ID.聽 Either way will work.

Circular Joint Relationship

The third course, MATH 402, represents jointedness in a circular fashion, where one section 鈥減oints to鈥� the next聽via the Joint ID value.

Note:聽 Please be aware that IASystem鈩� preserves courses and instructors, including jointedness, when they have an associated evaluation.聽

Class List File

File contains student user and class list data (the link between student and course) and creates both student user records and class list records.

Upload behavior

  • Adds new and updates existing records for a selected term.
    • Student records are added and updated, but never deleted
    • Class list records are added and deleted for any Course ID present in the file; if a file is re-imported in a specific term, dropped students will be removed from the course
  • For existing Course IDs not present in the file, their associated class list records are left unchanged
  • First matches on username, then student ID.
  • Has an optional 鈥淚nstructor ID鈥� field for students enrolled in “Assigned Instructor” courses; this identifier provides the ability to link a student to an instructor.

Dependencies:

  • Course IDs must exist in IASystem鈩� from a Courses File upload.