Academic Calendar
This feed contains core academic calendar data that controls platform functionality. It connects to specific values in your institutional configuration feeds (noted as _id columns below). Some columns are useful if needed while others are required. The event_type values are key to control the platform functionality for each term.
Calendar dates in Stellic can be controlled by studentset. A “studentset” is a combination of seven data elements (campus_id, school_id, department_id, program_id, enrollment_level_id, student_level_id, and student_tag_id) that identifies a “group” of students whose records contain these identifiers (through the student feeds referenced above). These values are optional (blank studentset calendar dates will automatically be applied to all students) and will limit dates to be visible to only those students in the studentset. The data across a single row is all combined with an AND but any variations that would otherwise be an OR would need to be entered as separate rows. This may mean that date values that apply to specific populations may need to be duplicated in order to display for only those populations.
Related Term and Year are used when the date falls in a particular term but is related to a different term. An example is an event for the “Schedule Release of Summer 2023” which will occur during Spring 2023 (mid-March). This date is in Spring 2023 but is related to Summer 2023 (released in advance of the term).
Stellic supports multiple "schedule_out" dates by campus (not by studentset) but only one "term_begin" and ""term end"" date for the entire institution. If additional term variations are needed, please talk with your Stellic implementation team about Stellic's contextualized term functionality.
The "grades_due" event_type controls when ungraded courses will fall into the Unapplied section of audits. If your institution has a grading deadline that is substantially later than the end of the term, you may want to use the later grading deadline date as the term end value but enter an appropriate Event Description for display for users. The only limitation is that the "grades_due" cannot extend beyond the "term_end" date for the following term in sequence.
Expected feed filename: calendar.csv
Samples: CSV
Field | Description | Field requirement |
| The date associated with this calendar event. For date ranges of "general" events, please add a record for the beginning date and a second record for the ending date. Please ensure the date format is %Y-%m-%d or full year, followed by numeric month, followed by numeric day (with leading zeros as needed), all separated by hyphens.
Examples: "2021-08-21" | required |
| The display description associated with this event record. This will be visible within the Stellic platform (at least to administrative users if the following value is FALSE). This column can be a maximum of 100 characters in length.
Examples: "Schedule released for summer 2023" | required |
| The platform supports the following
term_end — when a term ends (and when the current term should roll forward); only one
| required |
| The term associated with the calendar date record. Must match a valid term name (not term code) from your institution's configuration sheet.
Examples: "fall" | required |
| The calendar year of the term associated with the calendar date record.
Examples: "2019" | required |
| For the "schedule_out" event_type, this term value must be used when the date falls within the begin and end dates of a particular term but is related to a different term. For example, the "schedule_out" release of Summer 2023 class section data may happen during Spring 2023. This date occurs in Spring 2023 but is related to Summer 2023.
Example: "Summer" | required if applicable |
| For the "schedule_out" event_type, this calendar year value must be used when the date falls within the begin and end dates of a particular term but is related to a different term.
Examples: "2020" | required if applicable |
| For dates that are applicable by studentset (see above), this is the campus identifier for the student. A student must have this campus identifier to see this date record. In addition, it is possible to enable the date class sections for this specific campus_id becomes visible in the platform through the "schedule_out" event_type (the only value that can drive this functionality in addition to term_name/year). | optional |
| For dates that are applicable by studentset (see above), this is the school identifier for the student. A student must have this identifier to see this date record.
Example: "sophomore", "3" | optional |
| For dates that are applicable by studentset (see above), this is the school identifier for the student. A student must have this identifier to see this date record.
Examples: "hci", "arch" | optional |
| For dates that are applicable by studentset (see above), this is the enrollment level identifier for the student. A student must have this identifier to see this date record.
Examples: "UGRD", "grad" | optional |
| Boolean flag which specifies if the event should be visible to students in the platform. Defaults to FALSE.
Format: "TRUE", "FALSE" | optional |
| For dates that are applicable by studentset (see above), this is the program identifier for the student. A student must have this identifier to see this date record.
Examples: "MIN-5541" | optional |
| For dates that are applicable by studentset (see above), this is the school identifier for the student. A student must have this identifier to see this date record.
Examples: "scs", "cfa" | optional |
| For dates that are applicable by studentset (see above), this is the school identifier for the student. A student must have this identifier to see this date record.
Examples: "hci", "arch" | optional |