OData Entities

The Purdue.io database is organized into a database of entities with different kinds of relationships to one other. This database is exposed via OData to allow API users to write flexible, powerful queries against course catalog data.

Below you'll find a list of each entity, and what kind of data it contains.

Course

<tr>
    <td>CourseId</td>
    <td>Guid</td>
    <td>A unique identifier for a specific course.</td>
</tr>

<tr>
    <td>Number</td>
    <td>String</td>
    <td>Course number in a 5 digit string, i.e. "26100".</td>
</tr>

<tr>
    <td>Title</td>
    <td>String</td>
    <td>Title of the course, i.e. "Multivariate Calculus".</td>
</tr>

<tr>
    <td>CreditHours</td>
    <td>Double</td>
    <td>Numeric value of credits for the course, i.e. "4.0".</td>
</tr>

<tr>
    <td>Description</td>
    <td>String</td>
    <td>Course description and/or notes, i.e. "Evening Exams Required".</td>
</tr>

<tr>
    <td>Subject</td>
    <td>Subject</td>
    <td>Subject entity.</td>
</tr>

<tr>
    <td>Classes</td>
    <td>Array&lt;Class&gt;</td>
    <td>A list of Class entities.</td>
</tr>

Property	Type	Description

Class

<tr>
    <td>ClassId</td>
    <td>Guid</td>
    <td>A unique identifier for a specific class.</td>
</tr>

<tr>
    <td>Course</td>
    <td>Course</td>
    <td>Course entity.</td>
</tr>

<tr>
    <td>Term</td>
    <td>Term</td>
    <td>Term entity.</td>
</tr>

<tr>
    <td>Campus</td>
    <td>Campus</td>
    <td>Campus entity.</td>
</tr>

<tr>
    <td>Sections</td>
    <td>Array&lt;Section&gt;</td>
    <td>A list of Section entities.</td>
</tr>

Property	Type	Description

Section

Class

<tr>
    <td>SectionId</td>
    <td>Guid</td>
    <td>A unique identifier for a specific section.</td>
</tr>

<tr>
    <td>CRN</td>
    <td>String</td>
    <td>The official number of a section that Purdue uses for reference, i.e. "13342".</td>
</tr>

<tr>
    <td>Type</td>
    <td>String</td>
    <td>The type of the section, i.e. "Lecture".</td>
</tr>

<tr>
    <td>RegistrationStatus</td>
    <td>String</td>
    <td>Status of the section's registration, i.e. "NotAvailable".</td>
</tr>

<tr>
    <td>StartDate</td>
    <td>DateTimeOffset</td>
    <td>Starting date of the section, i.e. "2015-01-12T00:00:00Z".</td>
</tr>

<tr>
    <td>EndDate</td>
    <td>DateTimeOffset</td>
    <td>Ending date of the section, i.e. "2015-01-12T00:00:00Z".</td>
</tr>

<tr>
    <td>Capacity</td>
    <td>Int32</td>
    <td>Maximum number of students that can enroll in the section, i.e. 108.</td>
</tr>

<tr>
    <td>Enrolled</td>
    <td>Int32</td>
    <td>Number of students currently enrolled in the section, i.e. 10.</td>
</tr>

<tr>
    <td>RemainingSpace</td>
    <td>Int32</td>
    <td>Number of seats available in the section, i.e. 98.</td>
</tr>

<tr>
    <td>WaitlistCapacity</td>
    <td>Int32</td>
    <td>Number of students allowed on the section's waitlist, i.e. 36.</td>
</tr>

<tr>
    <td>WaitlistCount</td>
    <td>Int32</td>
    <td>Number of students currently on the section's waitlist, i.e. 0.</td>
</tr>

<tr>
    <td>WaitlistSpace</td>
    <td>Int32</td>
    <td>Number of spaces available on the section's waitlist, i.e. 36.</td>
</tr>

<tr>
    <td>Class</td>
    <td>Class</td>
    <td>Class entity that this section belongs to</td>
</tr>

<tr>
    <td>Meetings</td>
    <td>Array&lt;Meeting&gt;</td>
    <td>List of meetings held in this section.</td>
</tr>

Property	Type	Description