Data Documentation
Abhiram Tadepalli
All the relevant data we have access to.
Nebula API
Has class sections from each semester with the following data:
Subject: “ACCT”
Catalog Number: “2301”
Section: “1”
Number of students per letter grade (A+, A, A-, B+, B, B-, C+, C, C-, D+, D, D-, F, P, CR, NC, I, W): 7
Instructors (Up to 6): “Zhang, Jieying”
ID: ID (as String)
First name: ““
Last name: ““
Titles: ““
Email: ““
Phone Number: ““
Office: ““
Profile URI: ““
Image URI: ““
Office Hours: array of type Meeting
Sections: array of IDs (as Strings)
A Meeting has the following properties:
Start Date: type Time
End Date: type Time
Meeting Days: array of Strings
Start Time: ““
End Time: ““
Modality: ““
Location: type Location
A Location has the following properties:
Building: String
Room: String
Map URI: String – this is the room’s location’s link at https://map.utdallas.edu/
https://github.com/UTDNebula/api-tools/blob/develop/scrapers/profiles.go#L56
ID: ID (as String)
Subject Prefix: ““
Course Number: ““
Title: ““
Description: ““
Enrollment Requirements: ““
School: ““
Credit Hours: ““
Class Level: ““
Activity Type: ““
Grading: ““
Internal Course Number: ““
Pre-requisites: CollectionReqiuirement
Co-requisites: CollectionReqiuirement
Co-or-pre-requisites: CollectionReqiuirement
Sections: array of ID’s (as String)
Lecture Contact Hours: ““
Laboratory Contact Hours: ““
Offering Frequency: ““
Catalog Year: ““
Attributes: array of objects
A CollectionRequirement has the following properties:
Name: String
Required int
Options: array of objects
ID: ID (as String)
Section Number: ““
Course Reference: ID (as String)
Section Co-Requisites: type CollectionRequirement
Academic Session: type AcademicSession
Professors: array of ID’s (as Strings)
Teaching Assistants: array of Assistants
Internal Class Number: ““
Instruction Mode: ““
Meetings: array of Meetings
Core Flags: array of Strings
Syllabus URI: ““
Grade Distribution: array of ints
Attributes: array of objects
Rate My Professor
The big number at the top that shows how “good” a professor is, overall, based on the rating distribution
Scale: 1.00 to 5.00; could be “N/A” if there are no ratings
RateMyProfessors’ categories for the rating: Good: 3.5-5, Average: 2.5-3.4, Poor: 1-2.4
Course Evaluations
As of 03-19-24, Course Evaluation Data is not accessible and will not be incorporated soon.