Course Evaluation Data Dictionary for Eval25

 Note

This article is also available as a PDF file: Eval Data Dictionary.pdf

Tip: custom_data_field

It is possible to add a custom_data_field to the XML upload and be able to use it like any other field once it's in the system. For example, access restrictions, bindings, report filtering, etc.

The data dictionary includes options for custom fields. Use these to add whatever data you wish to your instance of Eval25. Once your file, including your new custom_data field(s), has been uploaded into Eval25, open a ticket in the Help Center (email support@collegenet.com) to let us know how the custom_data field(s) should be masked within Eval25. We will then change custom_data_n to appear however you wish. Please note that moving forward, however, the field(s) within your data file should still be loaded as custom_data_n

 

Course Evaluation Data Dictionary

Note for file generation:

  • The file may contain data for multiple sessions, but can only contain data for one term.
  • Required fields ("RF"), primary keys ("PK"), and foreign keys ("FK") are noted as appropriate.
  • All primary keys are required fields. 
  • All fields not marked as RF or PK are optional. 

Tables:

RF/PK/FK

data type

description

examples

school    
school_codePKvarcharabbreviated school name (PK)ENGR, EDUC
school_nameRFvarcharname of the school (required)School of Engineering, School of Education
     
department    
dept_codePKvarcharabbreviated department name (PK)EE, CW
dept_nameRFvarcharname of the department (major) (required)Electrical Engineering, Creative Writing
school_codeFKvarcharabbreviated school name, FK to school tableENGR, EDUC
     
course (section)    
course_idPKvarcharcourse CRN (PK)42725
offering varcharcourse offering number (PK)1, 2, 3 
sectionPKvarcharcourse section (PK)P07B, S05, 1, 2, 3
dept_codeFKvarchardepartment code, (PK); FK to department tableMUSIC, EE
subjectRFvarcharsubject of the course (required)Music, History, Drama, EE
numberRFvarcharcourse number (required)136A,  65A, 139W
course_name varcharcourse nameINTERMEDIATE POETRY WRITING,  SENIOR RESEARCH SEMINAR
type varcharcourse type for mapping survey questions to this type of coursesE, B, SEM (Seminar), LEC (Lecture), WKS (Workshop)
level varcharcourse level (Graduate / Undergraduate)GR, UG
class_size smallinthow many students in the class50, 12, 6
class_time varcharclass meeting time (combined for all days)7:00-9:00 TUTH, 7:00-7:50 W 
combined_section varcharidentifier used to combine the results of multiple cross-listed CRN sections (do not include tag for non-combined sections)2156
credit_hour varcharcredit hours for course3
eval_type varchararbitrary type for mapping survey questions to this type of coursesonline, on-campus, enrolled, non-enrolled
class_number varcharan alternate unique identifier for each course section. CRN.2354
topic_id varcharcourse topic id45
topic_title varcharcourse topic titleInto to Physics
instruction_mode varcharcourse instruction modeIn Person, Internet
location varcharcourse locationMain Campus
core_course varcharIdentifier of which courses fulfill general ed requirements (from class attributes)AREA 1
honors varcharHonors courseHonors
mean_code varcharCode used to group course means together in some reports (used by Stanford only at this point)Engineering
custom_data_1 varchar(30)Custom field for clients' own use. Maximum char limit of 30. 
custom_data_2 varchar(30)Custom field for clients' own use. Maximum char limit of 30. 
custom_data_3 varchar(30)Custom field for clients' own use. Maximum char limit of 30. 
custom_data_4 varchar(30)Custom field for clients' own use. Maximum char limit of 30. 
custom_data_5 varchar(30)Custom field for clients' own use. Maximum char limit of 30. 
custom_data_6 varchar(30)Custom field for clients' own use. Maximum char limit of 30. 
custom_data_7 varchar(30)Custom field for clients' own use. Maximum char limit of 30. 
custom_data_8 varchar(30)Custom field for clients' own use. Maximum char limit of 30. 
custom_data_9 varchar(30)Custom field for clients' own use. Maximum char limit of 30. 
custom_data_10 varchar(30)Custom field for clients' own use. Maximum char limit of 30. 
     
student    
student_idPK/RFvarcharunique identifier of student951045103
student_firstnameRFvarcharstudent first nameWilliam
student_preferredname
varchar
student preferred name
When left blank, first name will be used
Will
student_middlename varcharstudent middle nameAdam
student_lastnameRFvarcharstudent last nameSmith
student_emailRFvarcharstudent email addresswillasmith@collegenetu.edu
student_career varcharstudent careerUGRD
student_gender varcharstudent genderM
student_acad_level varcharstudent academic level10
student_ethnicity varcharstudent ethnicityBlue
student_age varcharstudent age21
student_cum_gpa varcharstudent cumulative gpa2.21
student_acad_plan varcharstudent academic planArt
     
instructor    
instructor_idPK/RFvarcharunique identifier of instructor950312387
instructor_firstnameRFvarcharinstructor first nameJennifer
instructor_preferredname
varcharinstructor preferred name
When left blank, first name will be used
Jenn
instructor_middlename varcharinstructor middle nameEva
instructor_lastnameRFvarcharinstructor last nameBell
instructor_emailRFvarcharinstructor email addressjebell@collegenetu.edu
instructor_type (deprecated) varchartype of instructorfulltime
can_edit_viewable bit (1 or 0)If the Instructor Release Reports feature is on, can this instructor edit his/her report release? 0 for no, 1 for yes1
viewable bit (1 or 0)If the Instructor Release Reports feature is on, can others view his/her reports? 0 for no, 1 for yes0
     
term    
term_idPKvarcharunique identifier of the term1094
term_descr varcharname or title of the term2011-2012 Spring
     
session    
session_idPKvarcharunique identifier of the session1, 0001, 1234
session_title varchartitle of the sessionSummer Session 1
session_start_dt varcharstart date of the session (required if you want the session automatically created during loading)2011-05-25, 2011-10-06 9:01 PM, 2011-10-06 21:01:00
session_end_dt varcharend date of the session (required if you want the session automatically created during loading)2011-05-25, 2011-10-06 9:01 PM, 2011-10-06 21:01:00
session_report_dt varcharreport date for the session 2011-05-25, 2011-10-06 9:01 PM, 2011-10-06 21:01:00
session_description varcharname or title of the session Summer Session 1
     
form    
form_codeRFvarcharform code to bind course-instructor to particular form; values as entered in Form EditorMAIN, LANG
     
TA*    
taRFbit (1)Always set this to 1 in your XML file to differentiate between "parent" courses and TA courses. In addition, you need to add a <ta_type> tag that is set to 2. 
course_idRFvarcharRequired to tie this TA course to its parent course. 
dept_codeRFvarcharRequired to tie this TA course to its parent course. 
offering varcharRequired to tie this TA course to its parent course. 
sectionRFvarcharRequired to tie this TA course to its parent course. 
session_id varcharOnly required if the term is session-based. 
form_code varcharNot required --- the TA form_code will default to the parent course form_code if excluded. 
instructor_idRFvarcharRequired to create the evaluation for this TA. 
instructor_firstnameRFvarcharRequired to create the evaluation for this TA. 
instructor_middlename varchar  
instructor_lastnameRFvarcharRequired to create the evaluation for this TA. 
instructor_email varchar  
instructor_type varcharNot required 
can_edit_viewable bit (1 or 0)If the Instructor Release Reports feature is on, can this instructor edit his/her report release? 0 for no, 1 for yes 
viewable  bit (1 or 0)If the Instructor Release Reports feature is on, can others view his/her reports? 0 for no, 1 for yes 
     
* TAs can be added by adding an XML element for each TA course/instructor combination and setting a TA flag to 1. Fields in the TA table marked as required are only necessary if TAs are being added.
     
Note: When associating a TA course with a parent course, the <ta> tag should be set to 1. In addition, to match with courses that share the same course id, rather than having to share a course id, department, offering, and section, add a <ta_type> tag that is set to 2. Type set to 1 TA courses will inherit most course information from their parent course, but type set to 2 TA courses will not.    
     
Note:    
(1) The file may contain data for multiple sessions, but only for one term. 
(2) To avoid manual work of mapping courses to particular sessions by Front-End interface, please include session_id in the data file (if the term is session-based)