School Information
This configuration feed is typically pulled from the SIS with all possible values for active schools (or colleges/divisions, depending on institutional context). These school_id values are used in a variety of other feeds to represent the organizational structure of the institution. Schools serve as the parent level of the organizational structure elements in Stellic (with departments as child elements of each school). The school_name values will display in various dropdowns in the platform. School information is useful for filtering programs associated with the school in the program.csv feed and also students associated with the school in the student_basic.csv feed. It is also useful when assigning permissions to administrative users.
Expected feed filename: school.csv
Samples: CSV
Field | Description | Requirement |
| Unique identifier for the school. This value can be your SIS school code or key value from the database. This value must match the "school" value on the program, course, and student program data provided (this becomes the foreign key for those records).
Examples: "BUS", "ENGR" | required |
| The full long name for the school. This will display in filters when searching for programs, courses, and students overseen by a particular school. This column can be a maximum of 100 characters in length.
Examples: "Business College", "School of Engineering" | required |
Department Information
This configuration feed is typically pulled from the SIS with all possible values for active departments. These department_id values are used in a variety of other feeds to represent the organizational structure of the institution. Departments serve as the child level of the organizational structure elements in Stellic (with schools as the parent element of each department; at this time, only one school can be connected to each department). The school_name values will display in various dropdowns in the platform. Department information, like school information, is useful for filtering programs associated with the department in the program.csv feed and also students associated with the department in the student_basic.csv feed. It is also useful when assigning permissions to administrative users.
Subject codes should be included for those course subjects that are overseen or managed by the department. The Subject Codes should match Subject values that are submitted in the course feed file (subject codes missing here will not be linked to a particular department for searches but will still display in the overall course list).
Multiple subject codes can be associated with a department. If so, please include only one row per Department ID and separate Subject Codes with a pipe (|) character. It is also possible to have some departments that do not have Subject Codes associated with them. Those departments may be used for filters for programs or students and with permissions.
In addition, it is possible to have a course subject code associated with multiple departments. This is primarily used to drive the department-based audit constraint that allows the use of any courses associated with “X” department to be used to meet program requirements. So long as this is acceptable behavior, a specific subject code can be linked in multiple rows to different departments.
If there are some subject codes at the institution that don’t have an “owning” department, you can create a generic department ID that is at the institutional level (will also require that you have a School at this level since all departments must be associated with a valid School).
NOTE: If the institution does not use department information in any way this feed can be excluded. However, this will remove any department-based functionality within the platform (permissions, audit constraints, etc.).
Expected feed filename: department.csv
Samples: CSV
Field | Description | Requirement |
| Unique identifier for the department. This value can be your SIS department code or key value from the database. This value must match the "department" value on the program, course, and student program data provided (this becomes the foreign key for those records).
Examples: "ACC", "CS" | required |
| The full long name for the department. This will display in filters when searching for programs, courses, and students and can be found in audit constraints when selecting all courses offered by a particular department.
Examples: "Accounting", "Computer Systems" | required |
| This boolean value determines if a student connected to this department code will be considered an "undeclared" program. Stellic uses this flag to determine which students show as undeclared in filter criteria and is used in conjunction with a configuration setting regarding what data value determines undeclared status (no program, a specific department, or specific program value). Defaults to FALSE.
Example: "TRUE", "FALSE" | optional |
| The unique identifier for the school that oversees this department. Must match values of the school_id column on the school.csv feed for the institution. Also used in the Stellic platform to filter by school when searching programs. There is currently only the ability to link a department with one school record; if your institution supports multiple then only one must be identified for the data feed in some manner.
Example: "CFA" | optional |
| List of course subject codes overseen by this department. Must match values of the course feed course column which allows Stellic to link all courses under this subject code to a particular department.
Example: ["ACC", "CS", "15"] | optional |
Program Type
The program type configuration feed is a core value for the Stellic platform. It helps us differentiate between programs to determine those that are primary versus secondary and also allows users to filter between different program types that may be named similarly (e.g., a major vs. minor in Psychology). These values are displayed in program filters to allow users to differentiate between them. They are also useful in some audit constraints to restrict or allow requirements to count between different program types.
Expected feed filename: program_type.csv
Samples: CSV
Field | Description | Requirement |
| This boolean value (TRUE or FALSE) helps determine whether a program value is identified as a primary or secondary type. For example, it is expected that students will have at least one primary program type (e.g., major, certificate) applied in the student program feed; secondary programs could also be added but aren't required (e.g., minors). Stellic uses this flag to assist with ordering in audits. Also, only programs with Is Major marked as TRUE can have official pathways auto-applied to students. Finally, this helps identify which programs can be used in constraints that specify a 'major' type (such as "Constraints for total units").
Example: "TRUE", "FALSE" | required |
| This is a required value to help the Stellic platform determine the order in which programs with different types should be listed in a student's audit (we typically order those with Is Major marked as TRUE at the top as noted below). Must be a numeric value.
Example: "1", "2" | required |
| The unique identifier for the program type. Must match the 'type' column in the program feed. Some SIS's do not have this value associated with program codes so this must be created in the program query that generates the feed sent to Stellic. In such cases, we recommend that you create IDs that match the intended variations in your curriculum. It is quite common for these to include types like major, minor, and certificate. It is less common to use IDs like "additional major" (see discussion below under the Program feed about differentiating or combining program types from your SIS). This column can be a maximum of 100 characters in length.
Examples: "MAJ", "minor" | required |
| This is the name of the program type associated with the ID value. This name value will be presented in the Stellic platform in the list of filters so users can select between different program types so it is intended to be a user-friendly value. This column can be a maximum of 100 characters in length.
Examples: "Major", "Minor" | required |
Concentration Type
Concentrations are sub-programs in Stellic and are connected to a single program code. Stellic includes a default Concentration Type called “Concentration.” However, we recognize that institutions may use a variety of types of these sub-programs. For example, some institutions use Specializations or Tracks along with concentrations. This is an optional configuration value to include and is only needed if your institution uses multiple types or your default is called something other than “Concentration.”
Expected feed filename: concentration_type.csv
Samples: CSV
Field | Description | Requirement |
| Like the program type ID value, this should match the “concentration_type” column sent in the concentration feed. It may be a value from your SIS or created to differentiate between various types of sub-programs. This column can be a maximum of 100 characters in length.
Examples: “CONC”, “spec” | required |
| This is the name of the concentration type associated with the ID value. This name value will be presented in the Stellic platform in audits so users can select between different concentration types when audit-building so it is intended to be a user-friendly value. This column can be a maximum of 100 characters in length.
Examples: “Concentration”, “Specialization” | required |
Campus
The “campus_id” values below link to the values provided for each program and course feed record (if applicable). As such, this should match the values in your SIS that will be sent in your data files. We use this to display the friendly name of the campus for staff in Stellic when they are filtering programs and courses and for students when searching for courses by campus.
In addition, we encourage you to list both the first day of the class week at this campus for scheduling purposes as well as the time zone in which the campus is found.
Expected feed filename: campus.csv
Samples: CSV
Field | Description | Requirement |
| The unique identifier for your campus codes from your SIS. This value will match the 'campus' values supplied in the program, schedule, student, and user files. This column can be a maximum of 200 characters in length.
Examples: "NYC", "MAIN" | required |
| The user-friendly name of your campuses that will display to users in the Stellic platform. This is used for lists of filters (to select between campus offerings, for example), to display a student's primary campus to which they are associated, or the campus location for a particular class section. This column can be a maximum of 200 characters in length.
Examples: "New York City", "Main Campus" | required |
| The first day of the week for the schedule view for students who are identified with this campus code as their 'primary_campus' column in the student_basic feed (a required value).
Examples: "Monday", "Sunday" | Optional |
| This boolean value allows you to specify if a particular campus value should be hidden from filters in the platform. This campus_id can still be connected to programs, sections, and students (particularly for historical data) and will display if attached to these records but will not be present in filters for searching. Defaults to FALSE.
Example: "TRUE", "FALSE" | Optional |
| The default time zone for this particular campus location. Stellic allows a user to adjust their preferred time zone but will correctly adjust class start and end times (in the student's schedule view) associated with specific class meeting patterns based on the difference between the time zone associated with the campus location of the particular class section and the student. This column can be a maximum of 150 characters in length. These values should align with common database values for time zones. For a valid list, see the canonical values at Wikipedia.
Examples: "America/New_York", "Australia/Sydney" | Optional |
Degrees
This feed is used in the platform to promote searching by students and programs as well as show a default number of program years and units in the planning module (more detail is controlled in the program audit). If you have variations in the number of years across similar degree types, simply include what is a base level as these values can be adjusted easily (they simply serve as defaults). The Priority Order helps determine the order in which courses are applied to programs if the student is enrolled in multiple degree programs at the same time.
Expected feed filename: degree.csv
Samples: CSV
Field | Description | Requirement |
| Unique identifier for the degrees. This value can be your SIS department code or key value from the database. This column can be a maximum of 10 characters in length.
Examples: "BA", "MS" | required |
| The full long name for the degree. This Name value has limited application in Stellic but displayed in associated with the scope definition options for program requirements. This column can be a maximum of 100 characters in length.
Examples: "Bachelors of Arts", " Masters of Science" | required |
| The minimum number of units required to complete this degree. Must be a numeric value.
Examples: "180", "360" | required |
| The default number of years (in integer values) that will be shown in the plan for this degree. Must be a numeric value (whole integer).
Examples: "4", "2" | required |
| The priority of degree during degree audit completion (1 being the highest). Must be a numeric value.
Examples: "1", "2" | required |
| The Enrollment Level ID column data links back to valid Enrollment Level information for each degree. This value is required if enrollment level functionality is used.
Examples: "UGRD", "Grad" | required if applicable |
Grade Options
This value is required in Stellic though we recognize that some SISs don’t have the concept or some institutions may only define one type for use throughout all courses and enrollments. Nonetheless, at least one Grade Option value must be defined and used in the Grade tab in the configuration sheet as well as course and student_course feeds.
In addition, institutions that don’t assign letter grades for some courses (e.g. transfer credit) must define a different grade option (and mark it as Not Graded = TRUE). Otherwise, all such courses will fall to the “unapplied” section of a student’s audit after the term of registration. This can also be used in conjunction with lab courses that are specific audit requirements (so long as they are always considered passing).
Expected feed filename: grade_option.csv
Samples: CSV
Field | Description | Requirement |
| The grade_option values (or codes, if appropriate) link to the values provided for each course feed record. As such, this should match the values in your SIS that will be sent in your data files.
This value must be included in the course feed and also in the student_course (enrollment) feed to indicate if the student enrollment record uses a different grade option than the default for the course. The grade_option and grade_option_name values must both be unique (Stellic can't have different grade_option values with the same grade_option_name since only the grade_option_name value is visible within the platform). This column can be a maximum of 20 characters in length.
Examples: "GRD", "PF" | required |
| We use this to display the friendly name of the grade option for students in Stellic when they are reviewing courses (in the audit, planner, registration). The "grade_option" and "grade_option_name" values must both be unique (Stellic can't have different grade_option values with the same grade_option_name since only the grade_option_name value is visible within the platform). This column can be a maximum of 50 characters in length.
Examples: "Graded", "Pass/Fail" | required |
| This boolean column value indicates an audit type that should never be applied to a student's program requirements (functions like the Never Apply column on the Grades tab but one level above grades and for courses that may not have grades posted). Most institutions don't include audit grades in the enrollment values sent to Stellic but it can be used to include a complete list of enrollments for a student (still won't apply to program requirements) or as a potential transfer grade when evaluating all coursework on a student's transcript from an external institution.
Example: "TRUE", "FALSE" | required |
| This boolean value allows you to specify a particular grading option that might never receive a grade in your SIS. This is common with some SISs for a transfer grade type (for which the institution does not record specific transfer grades).
Grade Options marked as TRUE will be used in the audit automatically to apply credit to the student's program requirements without a grade present (otherwise, the options on the Grade tab control the application). This is not used in some SISs (where all grade options require a grade to be posted). If not used in your SIS, simply mark the value as FALSE (the default).
Note: Any Grade Options marked with Not Graded = TRUE will automatically be applied to audit requirements and considered passing (e.g., any transfer credit awarded by the institution, presumably because you are not sending ineligible transfer records in the feed). As noted above, if your institution differentiates secondary (i.e., lab) courses in program requirements from primary sections (or any other class types that are "combined"), you will instead need to send a valid grade type in the student_course feed and not use the Not Graded configuration option for Grade Option.
What happens if a student enrollment with a Grade Option that has the never_graded setting marked as TRUE later has a grade applied? In such instances, the settings for that particular Grade value in config will override this never_graded setting and apply based on audit constraints (i.e., minimum grade value) or application to program requirements.
Example: "TRUE", "FALSE" | required |
|
This boolean value allows you to specify if a particular grade option is always considered a non-lettered grade. In such cases, it will only be applicable in program requirements when a constraint is included to allow for non-letter graded courses.
Example: "TRUE", "FALSE" | required |
Grades
This feed allows institutions to provide grade setup details that will be used to appropriately identify how the course enrollments should be applied to program requirements and GPA calculations based on the links to the student enrollment data (which will include Letter [Grade in student_course feed], Grade Option, and Grade Scheme as needed).
Expected feed filename: grade.csv
Samples: CSV
Field | Description | Requirement |
| This determines if a course will regularly apply to program audit requirements by default or must be enabled only through the use of a special audit constraint to allow "non-letter grades" to count toward the requirement.
Examples: "TRUE", "FALSE" | required |
| Letter should correspond to any string presented as a Grade for a student enrollment record. This should match the final_grade values in the student enrollment feed. This column can be a maximum of 10 characters in length.
Examples: "A", " W" | required |
| Name is the display value for a grade in the platform. This column can be a maximum of 40 characters in length.
Examples: "Withdrawn", " Pass" | required |
| Used to process a GPA calculation within the platform. If the grade has no weight (not used toward GPA calculations) then enter NULL. By default, grades with null weight do not count towards GPA. A weight of 0 will negatively impact the GPA.
Examples: "4", "NULL" | required |
| This value is defined in the Grade Option tab and must match values that are sent in course and student_course feeds. Required if used in the SIS and will be submitted in the student_course feed. This becomes part of the primary key for grades if used (primary key includes grade_scheme, grade_option, plus letter). This column can be a maximum of 20 characters in length.
Examples: "GRD", " PF" | required if applicable |
| grade_order can be confusing as many SISs do this in the background (or don't handle it at all) but we make it explicit in the Stellic configuration. This allows your institution to indicate particular levels for grades to control how they will be applied. For example, is a P (Pass) grade equivalent to a B or higher?
This allows program constraints to accurately read all enrollment records with grades equivalent to that selected and apply them (without requiring individual letters to be applied). Must be a numeric value or NULL. We suggest you start with assigning "10" to your highest grade, such as A+=10, then start assigning other numbers to grades, counting in intervals of 20. Using these larger intervals provides adequate margins for you to assign relative value between two grades as you proceed. It's important to consider where non-traditional grades fit into the relative order. For example, if an audit requires a minimum grade of C, can a CR grade fulfill that requirement? If so, it will need to be ranked equivalent to or relatively higher than a C. Important Note: Stellic only supports having the same grade_order value per grade letter "family." That means that the first grade_order value will be loaded and used for all grades with the same letter, regardless of grade_scheme and grade_option. E.g., all grades with letter A will be enforced with a grade_order of 10 if the first grade in the feed is assigned a 10, even if other grades with a letter of A have different numbers.
Examples: "10", " 50" | required |
| This is used to address the overarching groups under which various Grade Options are found (Grade Scheme -> Grade Option -> Letter) and should include all values for enrollment records that will be passed in the student course feed (typically only used for Peoplesoft institutions). Required if used in the SIS and will be submitted in the student_course feed. This becomes part of the primary key for grades if used (primary key includes grade_scheme, grade_option, plus letter). This column can be a maximum of 10 characters in length. Examples: "SCS", "CFA" | required if applicable |
| Is this grade an in progress grade that will later be replaced by a permanent value? Not all SISs use in progress grades but Stellic needs to know if in progress grades are used so we can appropriately order courses for audit progress and planning. This field defaults to FALSE.
Examples: "TRUE", "FALSE" | required if applicable |
| A boolean value indicating whether this grade is considered exam/test credit (such as AP, CLEP credits). A value of TRUE indicates that this grade will be used to identify a student's course for use with an exam grade audit constraint (e.g., At most [x] courses/units with exam grade).
Examples: "TRUE", "FALSE" | required if applicable |
| A boolean value which indicates whether an enrollment record for a student with this grade should never be applied to program requirements, not even through an exception. A value of TRUE means a course with this grade will never fulfill audit requirements under any circumstance. An exception, such as a substitution or waiver, will not be able to force this course to fulfill audit requirements. If the grade has a numerical weight, it will factor into the program GPA. A value of FALSE means a course with this grade is allowed to fulfill audit requirements, either automatically, by constraint, or by exception, based on settings in the Counts Towards Degree, Is Transfer, and Is Exam columns.
Examples: "TRUE", "FALSE" | required if applicable |
| A boolean value indicating whether a grade is considered transfer credit (also managed via the student_course feed so this is an alternative approach to identifying transfer credit as needed). A value of TRUE indicates that this grade will be used to identify a student's course for use with a transfer grade audit constraint (e.g., At most [x] courses/units with transfer grade).
Examples: "TRUE", "FALSE" | required if applicable |
Enrollment Levels
Enrollment levels are used in various filters within Stellic for administrative users to search for specific programs, courses, or students. The enrollment_level_name will be used to populate a dropdown within the platform.
The enrollment_level_id column data is used as the foreign key to the course.level feed data sent for each active course and programs (program.level). It also applies to sections (schedule_basic.level) and student enrollments (student_course.program_level).
PeopleSoft Institutions: Level may differ from Careers in that Careers can be setup across levels. However, depending on institutional configuration, there could be significant (if not complete) overlap. Levels are intended to be broad categories of courses that don't typically overlap course requirements across different levels whereas Careers can certainly overlap but are designed to separate credit types and even allow for different transcript "buckets" (for differing GPA calculations, etc.).
Expected feed filename: enrollment_level.csv
Samples: CSV
Field | Description | Requirement |
| The enrollment_level_id is used as the foreign key to various columns in feeds (program.enrollment_level, course.enrollment_level, student_basic.class_level). This id value should correspond with the code/id for the enrollment level in the SIS. This column can be a maximum of 40 characters in length.
Examples: “UGRD”, “GR” | required |
| The label used to define the enrollment level within the Stellic platform. This is the value that will display in dropdowns in Stellic. This column can be a maximum of 100 characters in length.
Examples: “Undergraduate”, “Graduate” | required |
Credentials
The credential record is a program grouping that Stellic uses to determine a student’s progress toward a degree or certificate (e.g., BA degree with a major in Statistics and minor in Economics; BS degree with two majors—one in Statistics and another in Psychology). The credential record is one layer above programs in Stellic; multiple programs can be grouped under one credential record to indicate that a student is completing all of them at the same time.
These records may correspond to a specific record in your SIS or they may be a conceptual grouping. Regardless, this represents a grouping value that will be connected to programs (i.e., majors, minors, certificates), student program records. This can also be used to link to an application to graduate at a specific time.
Expected feed filename: credential.csv (formerly diploma.csv)
Samples: CSV
Field | Description | Requirement |
| One of the valid credential (program grouping) values for the institution. This value must be unique. It is present on the student_credential feed and will be used to group programs that a student is pursuing at the same time. This column can be a maximum of 100 characters in length. This identifier will not display in the platform in any way.
Examples: "ECON-BS", "GR_EDUC" | required |
| The label used to define the credential grouping within the Stellic platform. This is the value that will display in Stellic. This column can be a maximum of 100 characters in length.
Examples: "Economics, BS", "Graduate Education Degree" | required |
| One of the valid enrollment level values for the institution. This is required to support level-differentiation functionality within the platform. Validation Note: Must match enrollment_level_id values in the enrollment_levels feed for the institution.
Examples: "UGRD", "Grad" | required |
Course Attributes
The use of course attributes is powerful functionality within the Stellic platform. Course attributes function like course “categories” that can be used to fulfill audit requirements. Think of them like a dynamic course list that allows any course (or section) to which the attribute is linked to meet a specific program requirement. These attributes are typically linked to courses themselves but Stellic can support attributes at the section level too (see our guide to the use of attributes).
This feed allows you to send Stellic the attribute code and the display name associated with that attribute. The course_attribute value is then added to the course, schedule_basic, and student_course feeds as appropriate but the display value will show within the platform in class search functionality and associated with course and enrollment records for students.
Expected feed filename: course_attribute.csv
Samples: CSV
Field | Description | Requirement |
| The attribute code used within the SIS that will be linked to the course, section, or enrollment record. This may align with similar values in the SIS or be a “category” defined within the feed structure that links to course, section, and enrollment records. The course_attribute value can be a maximum of 100 characters in length.
Examples: “HUMN”, “HIST” | required |
| The label for the attribute that will display within the Stellic platform. This is the value that will display in dropdowns and associated with course and enrollment records in Stellic. The course_attribute_name value can be a maximum of 100 characters in length.
Examples: “Humanities”, “History Course” | required |
Terms
This feed is required to link term codes to term values in various feeds (unless the SIS does not support term codes). Many SISs use term codes to identify a particular term record (though some SISs only use a combination of term and year). This feed can be used to supply all past and future term values to Stellic which will then enable the platform to link these values to other feeds in support of registration activities.
Expected feed filename: term.csv
Samples: CSV
Field | Description | Requirement |
| The term "code" that is used in your SIS for this term record. This value is used in various feeds (i.e., schedule_basic) and API requests, particularly to support registration.
Examples: "145241", "1534" | required |
| The name associated with this term record. This name should correspond with the name values in the Term Types configuration.
Examples: "Fall", "Spring" | required |
| The calendar year (not academic year) associated with this term_id record.
Examples: "2019", "2022" | required |
Program Basic Information
Expected feed filename: program.csv
Program Use-case Considerations
Programs in Stellic are the basic building blocks for student audits. Your SIS may not call these programs (e.g., these are typically “plan codes” in PeopleSoft). In fact, degrees are connected to programs so you may need to think a bit differently about how “programs” are used in Stellic.
At the core Stellic expects to receive a single program ID for each distinct curriculum requirement. There are a number of ways that SISs are configured to make your business processes work. For example, many institutions will create multiple program codes to differentiate primary vs. secondary majors for IPEDS reporting purposes. However, in many cases, these program codes all lead to the same curriculum requirements.
In such cases, Stellic recommends that you “combine” these program IDs into one single value. This helps so you only need one audit to serve both program codes. That doesn’t require you to change the codes in your SIS but will necessitate that you send the primary program ID in the student_program feed (which will require you to do some data transformation in your student_program query). This will greatly simplify audit maintenance for the future (otherwise, you will need to maintain multiple audits that are ultimately the exact same).
Samples: CSV
Field | Description | Requirement |
| Unique identifier for the program. This value can be your SIS program code or key value from the database. This value must match the "program" value on the student program data provided (this becomes the foreign key for that record). This column can be a maximum of 100 characters in length.
Examples: "BA-FIN", "MIN-1524", "1453" | required |
| The full long name for the program. This will display on the Stellic Programs screen and is the primary identifier for viewing programs. This is a string field that can be up to 100 characters long so many institutions will include the names from their SIS program codes here. However, you can also choose to append other values that improve the functionality for your users.
For example, some institutions include the program ID in parentheses or brackets to help people who search by that value such as administrative users ("Psychology [P519]"). The values you include are totally up to you and you can update them over time as you refresh the program feed.
Examples: "BA in Finance", "Minor in Architecture", "BA in Finance (BFIN)" | required |
| One of the valid program types for the institutional partner. This will display on the Stellic Programs screen as an indicator next to the program name. Also used in the Stellic platform to filter by type when searching programs. Validation Note: Must match values in the program_type feed for the institution.
Examples: "major", "Minor" | required |
|
One of the valid enrollment level values for the institution. This is required to support level-differentiation functionality within the platform. Validation Note: Must match enrollment_level_id values in the enrollment_levels feed for the institution.
Examples: "UGRD", "Grad" | required if applicable |
| List of campuses where this program is offered. Must match values of the ID column on the Campus tab of the configuration sheet for the institution. This is used in filters for program search but can also be used to limit student selection of programs by their campus (institutional setting). Multiple values should be pipe-delimited.
Example: ["nyc", "milan"] | Optional |
| The degree that is awarded at the completion of this program (if any). This will display in the Stellic Program profile when viewing program records. Validation Note: Must match degree_id values of the Degree feed for the institution.
Examples: "BA", "MA", "27" | Optional |
| The unique identifier for the department that oversees this program. Must match values of the department_id column of the Department tab of the configuration sheet for the institution (or the Department data feed if used). Also used in the Stellic platform to filter by department when searching programs. Currently, a program can be linked to only one department.
Example: "ROB" | Optional |
| Boolean flag that determines the display status for this program in the platform. A FALSE value (default) indicates an active program that can be found in search functions, is being assigned to students, and for which audits are to be built. A TRUE value will hide this program from search functionality. Format: "TRUE", "FALSE" | Optional |
| This boolean value determines if a student connected to this program record will be considered an "undeclared" program. Stellic uses this flag to determine which students show as undeclared in filter criteria and is used in conjunction with a configuration setting regarding what data value determines undeclared status (no program, a specific department, or specific program value). Defaults to FALSE.
Example: "TRUE", "FALSE" | Optional |
| The full long text description of the program. This is used by students when searching programs. Can include as much formatted text as needed, including outcomes, objectives, etc. This column can be any length.
Examples: "The BS in computer science is designed to cover the fundamental…" | Optional |
| The unique identifier for the school that oversees this program. Must match values of the ID column on the Schools tab of the configuration sheet for the institution. Also used in the Stellic platform to filter by school when searching programs. Currently, a program can be linked to only one school.
Example: "CFA" | Optional |
| List of identifiers for staff that are affiliated with this program. The identifier should match the attribute that is passed in SSO authentication (username, id, etc.)
Example: ["jterry", "flampard", "156798"] | Optional |
| An optional identifier for a particular program type or value that is helpful to use for differentiator or filter within the platform. Multiple values should be pipe-delimited.
Examples: "Pre-Admission", "Dual Degree" | Optional |
Concentrations
This is an optional feed by highly recommended as most institutions often have multiple types of concentrations in their academic structure (e.g., concentration, specialization, track). Concentrations are sub-programs in Stellic and are connected to a single program code.
Expected feed filename: concentration.csv
Samples: CSV
Field | Description | Requirement |
| Unique identifier for the concentration record. This value can be your SIS concentration code or key value from the database. This column can be a maximum of 100 characters in length.
Examples: "ROB", "14511" | required |
| The full long name of the concentration/specialization/track. This will display within the student's audit and the student profile if selected. This column can be a maximum of 100 characters in length.
Examples: "Robotics", "American History" | required |
| The link to the program associated with the concentration. Concentrations can be linked to only one program. If multiple in your SIS, you will need to create unique concentration_id records for each concentration-program link (perhaps by concatenating the concentration key and program key from your SIS). Validation Note: Must match values from the "program_id" column in the program feed.
Examples: "BA-FIN", "MIN-1524", "1453" | required |
| One of the valid concentration types for the institutional partner. Defaults to "concentration." Validation Note: Must match values of the ID column on the Concentration Type tab of the configuration sheet for the institution.
Examples: "CON", "specialization", "TRK" | Optional |
Course Basic Information
Course Use-case Considerations
Along with Programs (and Concentrations), courses are the basic catalog data in the Stellic platform and used as the basic building blocks for program audits. Even institutions that are loading audits from their current system must supply courses that match existing records
Expected feed filename: course.csv
Samples: CSV
Field | Description | Requirement |
| The subject code plus course number of the course, separated by the institutional course code separator (defined in the configuration sheet—might be a space, hyphen, or no space if nothing is used). Stellic will pull the subject code from the initial portion of this value for use in subject code constraints for program requirements. This column can be a maximum of 20 characters in length.
How it appears: Course code appears at the top of course tiles on the courses tab, at the top of the course sidebar, and is the first text on any course element within an audit
Examples: "MATH 101", "CALC-121" | required |
| Unique identifier for the course. This may not be visible in your SIS but may instead be a database unique key used to identify this particular course offering.
Examples: "161921" | required |
| The full course title. This will display in the Stellic platform as students and administrative users search for courses. This column can be a maximum of 200 characters in length.
How it appears: Course name appears below the course code in course tiles in the courses tab, below course code in the course sidebar, and after course code in audits (where courses are shown as a separate element, not when listed within a concentration)
Examples: "Introduction to Linear Algebra" | required |
| Units/credits for the catalog course (class sections may differ; this is the general, default catalog offering). If it's a range, provide both minimum and maximum (if both are included, they should be submitted comma-delimited and be encapsulated in quotes to escape the commas). This will be used to display the typical units for the course in general course displays and planning functions in Stellic. Must be a numeric value (float).
How it appears: Course units show below course name in course tiles on the courses tab, and in the course sidebar. Will show as ‘credits’ or other if this is configured by the institution
Examples: "3.0", "3.0,6.0" | required |
| One of the valid enrollment level values for the institution. This is required to support level-differentiation functionality within the platform. Multiple level values are allowed per course but they must be pipe-delimited. Validation Note: Must match Enrollment Level ID values on the Enrollment Levels configuration feed.
How it appears: Course enrollment level is shown at the bottom of the course sidebar under the ‘Catalog Levels’ sub-heading.
Examples: "UGRD", "Grad", "UG | required if applicable |
| A list of all courses that can not be completed if this course is in the student's course history (anti-requisites). These courses will not be displayed as schedule options to students. In addition, if a student happens to have a secondary enrollment for both a course and its anti-requisite, the audit will exclude the second course completely from all programs in the students audit (treats it similar to a failed/excluded course from all student progress). There is a configuration setting that determines which occurrence should count toward the student's progress. Multiple items should be submitted pipe-delimited.
How it appears: Course anti-requisites are shown in the course sidebar under the ‘anti-requisites’ sub-heading
Examples: ["ARTH 451"] | Optional |
| List of courses that are corequisites of this course and can be scheduled concurrently. Will allow students to plan sections of these courses in the same term. Multiple items should be submitted pipe-delimited. The Stellic default is to treat multiples as if an OR condition (either option is acceptable).
How it appears: Course co-requisites appear in the course sidebar under the ‘Co-requisites’ sub-heading
Examples: ["CHEM 112L"] | Optional |
| List of attributes or tags associated with the course at the catalog level that can be used in search or in the degree requirements. These can be used to identify groups of courses in the degree audit that might fulfill requirements (i.e., specific general education categories). This value is limited to 100 characters in length for each attribute. Multiple attributes are allowed and should be pipe-delimited.
How it appears: Course attributes display in the course sidebar under the ‘Attributes’ sub-heading
Examples: [“Writing Intensive”, “Humanities|Correspondence”, “COMM”] | Optional |
| The full text description that is typically presented in the official course catalog. This will display along with other course information as students and administrative users search for courses. This description field can contain other metadata combined with the description as long as this information is not required for separate display or searching between courses (if this is required, your institution may be able to add additional columns of information to the data feed; check with your Stellic integration specialist for more details). This column can be any length.
How it appears: Course description displays in the course sidebar under the ‘Description’ subheading.
Examples: "This course is designed to cover the basics of the following core..." | Optional |
| List of courses that are cross-listed in the institutional catalog (can also be taken to meet a program requirement) or may no longer be active in the institutional catalog but are to be considered to meet program requirements in program audits (i.e., due to a course number change). This could include past courses that will be included in the student course (enrollment) feed, including transfer equivalencies. Should be submitted as the subject/number combination (course_code). Multiple items should be submitted pipe-delimited.
How it appears: Equivalent course codes are shown in the course sidebar under the ‘Course Equivalents’ sub-heading
Example: "MATH-101", "MATH-101 | Optional |
| What is the overall option (not grades themselves) at the catalog level for this course (this is the general, default catalog offering; grade options for individual class sections may differ)? Must include only one primary value and not all available options for the course (those are provided at the individual section or student enrollment level). Must match values of the Short Name column on the Grade Options tab of the configuration sheet for the institution.
Examples: "GRD", "PF" | Optional |
| Boolean flag which specifies if the course should be visible in the Course tab in the platform (and would be marked as "TRUE"). Inactive courses can be loaded into the platform to be used in audit requirements, application of pseudo-transfer courses, etc. but will not be searchable by students for planning. Stellic will "archive" inactive courses automatically (but allows for specificity of course equivalencies, repeatability, etc.). Format: "TRUE", "FALSE" | Optional |
| Boolean flag that indicates if this is a topic course (see explanation below under Course Topic Data to determine if required). Format: "TRUE", "FALSE" | Optional |
| A list of all courses that should be completed before this course can be taken (pre-requisites). This is a logical string formatted with ANDs, ORs, and course codes. Stellic can accommodate the following data elements: Course Codes - Most pre-reqs are lists of courses. This is simply the course subject plus number. Between the subject and number, you'll use whatever is defined in your configuration as expected course code structure (typically a space or hyphen, but sometimes not even a space). Must also be a valid course in your course feed.
For example, MATH 428, MATH-428, MTH428. Course Patterns - Stellic supports course patterns as pre-reqs. These must align to valid course code structures in your course feed, including any space or hyphen between the subject and number parts of the course code. To use a pattern, it must include either the asterisk (*) or tilde (~) character. To learn more about these course patterns to see more examples, see Understanding Course Code Ranges and Patterns in Stellic. Stellic can accommodate minimum grade values and matches across different grade options but uses the "letter" value for comparison. The grade should be sent following a "$" and the course to which it applies. The grade must be a valid grade in your grade setup.
For example: MATH 428 $B. Allow Concurrent Pre-requisite - Institutions can also indicate that a specific pre-requisite can be taken in the same term as the following course (concurrent enrollment). Indicate this in the same string by following the specific course with a "Y" for concurrent indicator. (No indicator is required if concurrent enrollment is not allowed.)
For example: MATH 428 $B Y would allow this pre-requisite to be taken concurrently. Test Scores - Stellic can accommodate tests as pre-reqs if those tests are defined and sent in the test and student_test feeds which are optional config/student feeds. For tests, we must receive the test code (defined in test config tab/feed) and score with an operator (typically ">=" for "greater than or equal to") between the test code and minimum score.
How it appears: Equivalent course codes are shown in the course sidebar under the ‘Course Equivalents’ sub-heading.
Examples: "(MATH 428 $B Y or ALG 458) and (CALC 301 or APCALC >= 4)" | Optional |
| A numeric value indicating the maximum number of times (attempts) a course can be repeated. A value in this column assumes the repeatable flags (boolean) in the prior column is marked as True. Must be a numeric value.
Example: "3" | Optional |
| A numeric value indicating the maximum number of units of this course that can be repeated. A value in this column assumes the repeatable flags (boolean) in the "repeatable" column is marked as True. Must be a numeric value.
Example: "6" | Optional |
| Boolean flag which specifies that if the course is repeated, it will contribute to total credits and requirements multiple times. Without this value marked TRUE, Stellic will assume the course is not repeatable and more than one attempt of the course will fall to "unmatched" in the student's audit. This applies to transfer and test-based credits as well (so these pseudo-courses may need to be specified in the feed to allow repeatability). This value is overridden by the "repeat_code" value in the student_course feed (if applicable).
How it appears: Course repeatable information is shown in the course sidebar under the ‘repeatable’ sub-heading
Format: "TRUE", "FALSE" | Optional |
| Peoplesoft institutions only: The requirement group code linked to this course instance. Stellic can import pre- and co-requisites directly from the PS requirement group tables (list provided by Stellic during the integration process). Colleague institutions only: The academic requirement id linked to this course instance. Stellic can import pre-requisites directly from the Colleague academic requirement tables (list provided by Stellic during the integration process). | Optional |
| The short course title (if your SIS supports such a field). This column can be a maximum of 50 characters in length.
Examples: "INTRO LIN ALG" | Optional |
Course Topic Data
Optional—a separate csv feed file is only necessary if your institution uses courses with “topics” that may change over time. These courses are typically repeatable options that might have a different emphasis based on when they are taught. The data elements that change with each offering must be included (typically things like title, units, attributes, etc.). The code is required if the topic is linked to a specific program requirement (audit) in order to link the student’s enrollment to the specific topic associated with the student’s enrollment record.
Expected feed filename: course_topic.csv
Samples: CSV
Field | Description | Requirement |
| A concatenated combination of the subject and number from the course feed that follows your course pattern (including the separator; must match values in the course feed).
Examples: "MATH-101", "CHEM 220" | required |
| Unique identifier for the course topic record. This may not be visible in your SIS but may instead be a database unique key used to identify this particular course topic.
Examples: "769801", "572131" | required |
| The topic name (title) associated with the specific topic record. This will be displayed in the Stellic platform for schedule review and planning purposes. This column can be a maximum of 200 characters in length.
How it appears: Course topic names are shown in the course sidebar under the ‘Topics’ sub-heading
Examples: "Literature & Film", "European History" | required |
| List of attributes or tags associated with the topic that can be used in search or in the degree requirements. These can be used to identify groups of courses in the degree audit that might fulfill requirements (i.e., specific general education categories). This is only needed if some topics for the course include the attribute while others do not. This value is limited to 100 characters in length for each attribute. Multiple attributes are allowed and should be pipe-delimited.
Examples: ["Writing Intensive", "Humanities | Optional |
| The full text description for the topic (that may differ from the overall course description). This column can be any length.
Examples: "This course is designed to cover the basics of the following core..." | Optional |
| Units/credits for the topic course. If it's a range, provide both minimum and maximum (if both are included, they should be submitted comma-delimited and be encapsulated in quotes to escape the commas). Must be a numeric value (float).
Examples: "3.0", "3.0,6.0" | Optional |