Student Data Feeds
Class Levels
Class levels are used in various filters within Stellic for administrative users to search for specific students. This is a required value in the student profile. This list below will be used to populate a dropdown within the platform.
Expected feed filename: class_level.csv
Samples: CSV
Field | Description | Requirement |
| Used as the foreign key to the student_basic.class_level feed data sent for each active student. This id value should correspond with the code/id for the student’s class level in the SIS. This column can be a maximum of 50 characters in length.
Examples: “1”, “2” | required |
| The label used to define the student level within the Stellic platform. This value will display in dropdowns in Stellic. This column can be a maximum of 50 characters in length. Examples: “Freshman”, “Year 1”
Use in platform:
Description: In the Students tab, after searching for a student (or group of students), the class level name appears under the student’s name. | required |
| This value determines the order in which these levels should display in filters. This value can match the class_level_id if it is numeric. Must be a numeric value.
Examples: “1”, “2” | required |
Registration Status
Registration Status is an optional data element used within Stellic to indicate the student's status of a particular section or course during the planning process. The “registration_status_name” below will be used to indicate the status of the particular enrollment record within the platform. The combination of registration_status_id and registration_reason_id columns is used as the foreign key to the student_course.registration_status_id and registration_reason_id feed data sent for each student enrollment record. For those institutions whose SIS does not include a “reason” value (only a status code), the registration_reason_id can be blank. Stellic will use the status and reason codes in combination.
This tab should be completed in conjunction with the determination of what registration status options should be sent in the feed in the first place. Most institutions send only enrollment records that reflect values sent on a student's transcript and would remove all dropped classes from the feed. Some institutions choose to include waitlisted classes as an option for visibility during the planning and registration process but doing so is optional (though highly recommended if students are completing registration through Stellic).
Expected feed filename: registration_status.csv
Samples: CSV
Field | Description | Requirement |
| The unique identifier from your SIS that is associated with each student enrollment record. This value is a foreign key to the optional student_course feed value for the ‘registration_status_id’ column. This column can be a maximum of 100 characters in length.
Examples: “E”, “WL” | required |
| Only required for SISs that use this functionality (e.g., PeopleSoft). The unique identifier from your SIS for the reason associated with the registration status. This value is a foreign key to the optional student_course feed value for the ‘registration_reason_id’ column. Stellic will create a unique combination of registration_status_id and registration_reason_id to match on values in the student_course feed. This column can be a maximum of 100 characters in length.
Examples: “ENRL”, “WAIT” | required if applicable |
| The value that should be displayed in Stellic associated with the registration_status_id and registration_reason_id combination value. This value will be displayed next to each enrollment record within the Stellic platform to indicate the status of the enrollment. This column can be a maximum of 100 characters in length.
Examples: “Enrolled”, “Waitlisted” | required |
| A value that indicates for this particular status how the enrollment should operate within the platform. This value must be one of the following:
| required |
Repeat Codes
Institutions typically manage repeated courses within the SIS, often with complex rules for determining which enrollments should be considered. There are two ways that repeats are “counted” within Stellic and the platform can operate on its own or receive your SIS repeat codes to ensure enrollments are counted in the same way as your SIS. Those two options are whether the course can count toward program requirements and whether it should count toward the student’s GPA. Both can be indicated with settings for each repeat code record.
A note for some SISs: you may have additional values to differentiate repeat codes by other types such as graduate or undergraduate. Stellic doesn’t need these designations unless the Counts toward Degree or Counts Toward GPA values differ for the same “Code” across these levels. If so, you will need to use a unique code to distinguish between these options and those codes will need to be used correctly within the student_course feed (perhaps as a concatenated value of the level plus the code).
Expected feed filename: repeat_code.csv
Samples: CSV
Field | Description | Requirement |
| This is the repeat code that is connected to each enrollment. If not set directly within your SIS, you may need to review enrollment records to determine what this value is so it can be used as the foreign key to the student_course.repeat_code value. This column can be a maximum of 30 characters in length.
Examples: “REP”, “ORIG” | required |
| This is the value that is displayed in the Stellic platform for the enrollment record when the repeat_code_id value is applied. This column can be a maximum of 150 characters in length. Examples: “Repeated Course”, “Original Course Attempt” | required |
| A TRUE/FALSE value that indicates if an enrollment record with this repeat_code_id should be allowed to count toward program requirements (TRUE) or not (FALSE). A FALSE value will prevent this course from being used toward any audit requirements and the course will display in the Unapplied section of the audit with an indicator that it was marked as repeated. | required |
| A TRUE/FALSE value that indicates if an enrollment record with this repeat_code_id should be allowed to count toward a student’s GPA (TRUE) or not (FALSE). Institutions that have a grade forgiveness policy and indicate it for some of a student’s enrollment records would make those repeat codes indicating forgiveness as FALSE. | required |
Advisor Role
Advisor role is an optional value but is used by many SISs and should be defined in Stellic if the institution is sending the student_advisor feed in which roles are included. It is used within Stellic to display the name of the advisor’s role on the student profile.
Expected feed filename: advisor_role.csv
Samples: CSV
Field | Description | Requirement |
| Used as the foreign key to the student_advisor_role_id feed data sent for each advisor. This column can be a maximum of 50 characters in length.
Examples: “SC”, “ACAD” | required |
| Used to display the name associated with the advisor_role_id and applied to the student’s advisor in the student’s profile in Stellic. This column can be a maximum of 150 characters in length.
Examples: “Success Coach”, “Academic Advisor” | required |
Graduation Application Status
For institutions that use graduation clearance functionality in Stellic, this record tracks whether a student has applied to graduate for a set of programs in Stellic (within the student credential record). This record manages the complete clearance process within Stellic, from initial application through final awarding (or cancellation/denial as needed). Upon completion, this record pushes data back to the institution for use in institutional business processes.
Expected feed filename: grad_application_status.csv
Samples: CSV
Field | Description | Requirement |
| The status value of this application. This value must match a grad_application_status_id value from the grad_application_status feed.
Example: "AW", "AD" | required |
| The predefined value for the status value that aligns with Stellic graduation application/clearance functionality.
Allowable type values:
| required |
Student Profile
Expected feed filename: student_basic.csv
Samples: CSV
Field | Description | Requirement |
| Unique identifier for a student. These values must match the user attribute that is passed via SSO (often a username or ID number). This value should not change over time (should persist through name changes, changes in enrollment status, etc. so Stellic can continue to use it to match on the same value across time and data feeds). This value will be visible in the platform and is the primary search value used for finding students and filters. This column can be a maximum of 50 characters in length.
Examples: “d815017”, “001356897” | required |
| The internal id number (used in the SIS for identification and lookup) for the student. The column is required in the data feed. However, this is not a required value but is very helpful if your institution uses this value for searching for students (either student_username or student_id can be used for searching along with a student’s name).
Examples: “jsmith”, “js0189” | Optional |
| The student’s first name. This column can be a maximum of 30 characters in length. | required |
| The student’s last name. This column can be a maximum of 30 characters in length. | required |
| If different from the official/legal first name. Displayed on the student profile and can be located through search as well. If this value is supplied, Stellic will load this value for the student’s name instead of the first_name value above (and only the preferred_name will be available in searches). This column can be a maximum of 30 characters in length. | Optional |
| Preferred student pronouns. Limited to 50 characters in length. | Optional |
| The official institutional email associated with the student’s record. Will be used for communication if the student opts in to email communication for notes, etc.
This column is “required” since it is necessary for data sync of this feed to operate and a student’s email must be present for notifications within the platform. A student record with no email still allows access to the platform but functionality triggered by emails like notifications will not occur until a valid email address is included in a following data sync. This column can be a maximum of 250 characters in length.
Examples: “jterry@mit.edu” | required |
| The student’s entry term to the institution. This value controls the program audit that is applied to the student based on audit scope criteria. The term name must match a valid term type from your institutional configuration sheet Term Type tab along with the year value.
Examples: “fall 2020” | required |
| The level associated with the student (will change over time). This value must match a value supplied in the id column of the Student Levels tab of the configuration sheet (a foreign key to this column). This value is used to filter groups of students in the platform. For institutions with multiple student levels, this should be the primary level for the student at the time. Additional, program-based levels can be supplied in the student program feed. Examples: “sophomore”, “3” | required |
| One of the valid enrollment level values for the institution. This is required to support level-differentiation functionality within the platform. This should be the student’s primary level if they are enrolled in multiple programs, each with different levels (the individual program levels are specified in the student_program feed).
Validation Note: Must match Enrollment Level ID values on the Enrollment Levels tab of the configuration sheet for the institution.
Examples: “UGRD”, “Grad”, etc. | required if applicable |
| The primary teaching location/branch campus to which the student belongs. This value must match a value supplied in the id column of the Campus tab of the configuration sheet (a foreign key to this column). Use this column if only one campus location is known for the student.
Example: “nyc” | Optional |
current_campus_id recommended | The current teaching location/branch campus to which the student belongs. This value must match a value supplied in the id column of the Campus tab of the configuration sheet (a foreign key to this column). Example: “nyc” | Optional |
school_ids recommended | List of schools with which the student is affiliated. This value is used to filter groups of students in the platform. This value must match a value supplied in the id column of the Schools tab of the configuration sheet (a foreign key to this column). Multiple values should be pipe-delimited. Example: “scs”, “cfa”, “cse” | Optional |
department_ids recommended | List of departments with which the student is affiliated. This value is used to filter groups of students in the platform. This value must match a value supplied in the id column of the Departments tab of the configuration sheet (a foreign key to this column). Multiple values should be pipe-delimited. Example: “hci”, “arch” | Optional |
gpa recommended | Cumulative GPA of the student (will change over time) Examples: “3.66” | Optional |
| Username of the primary advisor {only one value should be included in this field]. Primary advisor is a specialized role in Stellic and is indicated as such on the student’s profile if included. This role may also have special permissions and functions in Stellic functionality (i.e., workflows). If the institution’s SIS does not designate an advisor as primary, this can be left blank and all advisors can be included in the advisors column below.
This value must match the user attribute that is passed via SSO (often a username or ID number). This value must also exist in the user feed file (which is how we link to names and other information for display in the platform).
Examples: “aferguson” | Optional |
| List of any advisors that are not considered primary. These values must match the user attribute that is passed via SSO (often a username or ID number). These values must also exist in the user feed file (which is how we link to names and other information for display in the platform).
Examples: [“pele”, “rkane”]
Alternatively, advisor information, along with role details, can be sent in the student_advisor feed. If so, this column can be excluded. | Optional |
| The term when a student is expected to graduate. For institutions with multiple programs that can each have their own expected graduation term, this should be the primary one for the student at the time based on institutional priority (i.e., the earliest one). Additional, program-based grad terms can be supplied in the student program feed. This value is used to filter groups of students in the platform.
Examples: “spring 2024”, “Fall 2025” | Optional |
| The term of the general education catalog requirements that should be applied to a student (typically in a universal requirement in the Stellic audit). This may be stored as a catalog year in the SIS. In such cases, this should be converted to the fall term of that catalog year.
Examples: “fall 2021”, “Spring 2024” | Optional |
| List of courses that can be taken without meeting the prereqs. Multiple values should be pipe-delimited.
Examples: [“ARTH 5411”] | Optional |
| List of section_ids (must match valid values from schedule_basic feed) that the student has been granted permission to take. Some SISs support student_based permissions per class section that require advanced entry of the student’s ID into the SIS. This list will be used to identify a student with permission to register without restriction (such sections with restrictions will indicate to other students that permission is required). Multiple values should be pipe-delimited.
Examples: [“2341-15222”, “2341-15472”] | Optional |
| A phone number for the student at which they can receive text-based (SMS) communication through the Stellic platform. Must include the country code along with the number (e.g., the country code for the United States is +1) with no spaces or other characters (like (, ), or -). Formatted as a string to allow for the country code (with +).
Example: “+11234567890” | Optional |
| Boolean specifying whether the institution has received consent from the student to send messages to the text_phone number above. Defaults to FALSE. If this is FALSE, the student will be presented with a choice in the Stellic platform to opt in to text communications.
Example: “TRUE”, “FALSE” | Optional |
Student Program Enrollment
Expected feed filename: student_program.csv
Samples: CSV
Field | Description | Requirements |
| Unique identifier for the program enrollment. This can be the key value from your SIS or a unique combination of data (e.g., program code plus student id). Examples: “161921” | required |
| The SIS username for the student. Used to link to the student basic feed and other student feeds. Examples: “d815017” | required |
| Unique identifier for the student’s program. This value must match the “program_id” value on the program feed provided (the foreign key for that record). There should be one row/record for each program for each student.
Examples: “MIN-5541” | required |
| Unique identifier for the student’s concentration. This value can be your SIS concentration code or key value from the database. This value must match the “id” value on the concentration feed provided (the foreign key for that record).
This value is required if concentrations (or other sub-program types) are used for your institution. Stellic realizes that some students may have a concentration and some may not have a value which is fine. In the event a student has multiple active concentration records for a program these values can be pipe-delimited.
Examples: “ROB”, “14511”, “PMED|BIOCHEM” | required if applicable |
| Boolean flag that indicates the completion status for this program record for the student. Equivalent to “graduated” for this program. Allows the institution to send prior program records for a student to both display on the student’s profile and connect to program requirements as appropriate.
Audit functionality will show these certified programs at the bottom of the audit in “collapsed mode” with any courses that were used toward audit requirements linked to the prior programs so they do not apply to current program audits.
Format: “TRUE”, “FALSE” | Optional |
| The completion date for this program record for the student. Equivalent to “graduation date” for this program. Allows the institution to send prior program records for a student to both display on the student’s profile and connect to program requirements as appropriate. 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. | Optional |
| The order in which program requirements are displayed and processed in the audit for this student. If multiple programs are included in a student_credential record and the “is_primary_major” value is not sent in the feed, the lowest “order” value determines the primary program associated with credential requirements. Example: “1”, “3” | Optional |
| The catalog term that should be used to apply degree requirements to the student (if different from the term_joined value in the student basic feed). This may differ from a catalog for a student’s general education requirements (supplied in the student basic feed). This may be stored as a catalog year in the SIS. In such cases, this should be converted to the fall term of that catalog year.
Example: “Fall 2020” | required if applicable |
| Boolean flag that indicates if this value is the primary major for a student. This might be considered the first major if there are multiple or may rely on some other indicator in the SIS that determines the “primary” status. If multiple programs are included in a student_credential record, this determines the primary program associated with credential requirements.
Format: “TRUE”, “FALSE” | Optional |
Student Course Enrollment
Functional Requirement Statement:
The student_course feed should include all enrollment records for all active students that will be using the Stellic platform (should match the definition of "active students" that is used for the other student feeds). These records are to include all records meeting the following criteria at the time the feed is generated (changes in data values from the last feed will be synchronized as Stellic evaluates deltas). These enrollment records will be used to apply toward student program requirements in audits. As such, included records should be all internal (residential) enrollment records, all articulated transfer records, and all awarded records from tests/exams for the institution. Any alternative credit that is used in program audit requirements should also be included (i.e., block transfer record for completion of an AA degree).
These records will typically match what is included on a student’s transcript. As such, dropped enrollments should be excluded but withdrawn should be included (with appropriate grade and registration status). Institutions that will implement registration through Stellic typically choose to include waitlisted courses (if the institution utilizes such functionality) along with the appropriate registration status values. In addition, all enrollments for all program levels (undergraduate, graduate, etc.) should be included (program requirement constraints will effectively determine the application toward appropriate program requirements).
Appropriate repeat code values should be included based on your SIS designation. These records can also include appropriate tags for individual enrollment records to facilitate audit requirements but such records will be institution-specific and can also be added at a later time if applicable.
Expected feed filename: student_course.csv
OPTION: Stellic typically expects this data to be sent in a single file. However, some SISs store this data in different tables and the combined feed extract is quite large (since it includes all enrollment data for all students in the feed). Typically, when produced, this requires that all such data is combined in the feed through unions or other means. The Stellic pipeline can accommodate and load this data as separate feeds but the filenames must match the following (not all are required):
student_course_enrollment.csv (internal enrollment data from the institution)
student_course_transfer.csv (transfer articulation enrollment data)
student_course_test.csv (test credit enrollment data)
student_course_other.csv (other credit enrollment data)
student_course_in_cart.csv (shopping cart enrollment data, if used in the SIS)
All feeds should contain the exact same column headers even when sourced from different table data in the SIS (though some columns may be blank/null for some feeds).
Samples: CSV
Field | Description | Requirement |
| Unique identifier for the course enrollment. This can be the key value from your SIS or a unique combination of data (e.g., term code plus course/section code plus student id). This value is a key for the record for API connections or other real time integration.
Examples: “161921” | required |
student_username required | The SIS id number for the student. Used to link to the student basic feed and other student feeds. Examples: “d815017” | required |
section_id required | The unique section identifier for this enrollment. For institutional enrollments (not transfer or test records) this value must match a value supplied in the ‘id’ column of the section (schedule_basic) feed linked to this enrollment. For transfer or test credit, this value will be blank (not linked to a specific section record). Examples: “156798”, “Fall2020-16759” | required |
course_code required | A concatenated combination of the subject and number from the course feed that follows your course pattern. Examples: “MATH 428” | required |
term_name required | The term associated with the class section in your SIS. Must match a valid term value from your institution’s configuration sheet. Examples: “fall”, “Spring” | required |
year required | The calendar year of the term associated with the class section record. Examples: “2019” | required |
sub_term | The name of the sub-term or session code associated with this enrollment record. This must be submitted for the planner to validate display session information within a term. This value must match the sub_term value in the schedule_basic feed where applicable. The values included here must match those defined in the Sub-Terms tab in config to properly include the order in which they will display. This value should be the display name and not a code (unless you want the code to display to users in the platform). Examples: ”Summer 1”, “Sub-term 2” | required if applicable |
units required | Units/credits that the student received Examples: “3.0” | required |
course_topic_id required if applicable | The unique identifier used to link this enrollment to a specific topic id (only required if course topics are supplied and topic codes are used for specific program requirements). Must match codes supplied in the course topic feed as a foreign key. Examples: “2”, “8927” | required if applicable |
campus_id required if applicable | The campus/teaching location at which this course was taken. Must match a valid id value from the Campus tab of your institution’s configuration sheet. Examples: “florence” | required if applicable |
enrollment_level_id required if applicable | One of the valid enrollment level values for the institution. Only one level value can be associated with each enrollment record for a student. This allows audit functionality to limit which enrollment records can apply based on audit constraints (including potential double-counting constraints across levels).
Validation Note: Must match Enrollment Level ID values on the Enrollment Levels tab of the configuration sheet for the institution.
Examples: “UGRD”, “Grad”, etc. | required if applicable |
grade_scheme required if applicable | The grading scheme under which the student received a grade for this course. Must match a valid Grade Scheme value from the Grades tab of your institution’s configuration sheet. Examples: “PPS” | required if applicable |
grade_option_id required if applicable | The grading option under which the student received a grade for this course. Must match a valid Grade Option value from the Grades tab of your institution’s configuration sheet. Examples: “GRD” | required if applicable |
final_grade required | The final grade posted for this student’s enrollment record. This value is compared to the Grades tab date in the configuration sheet to determine applicability to program requirements and GPA calculated within Stellic.. Must match a valid Letter value from the Grades tab of your institution’s configuration sheet. Examples: “A-” | required |
mid_semester_grade recommended | A mid-term progress grade supplied for the student. This value is only for display purposes (not used in GPA calculations, etc.) and will be replaced by the final_grade value if present. If enabled, these values can be searched for within filters when present. Examples: “B+” | Optional |
is_transfer required if applicable | Boolean specifying whether this course was transferred in. Defaults to FALSE. This value is required if the institution will be sending transfer equivalency records that are matched to institutional course codes (typical). Format: “TRUE”, “FALSE” | required if applicable |
is_exam required if applicable | Boolean specifying whether this course was awarded based on an examination. Defaults to FALSE. This value is required if the institution will be differentiating exam records from other enrollment records (institution-based registration records and transfer records). Format: “TRUE”, “FALSE” | required if applicable |
is_residency required if applicable | Boolean specifying whether this course is considered resident credit at the institution (to differentiate from transfer or exam credit completed elsewhere). Defaults to TRUE. This value is required if the institution must track resident credit for program requirements. Format: “TRUE”, “FALSE” | required if applicable |
course_attribute_ids recommended | List of attributes or tags associated with the enrollment record for an individual student that can be used to indicate applicability of the record toward program requirements. Only needed when the individual student record attribute differs from the course or section level attribute values. This value is limited to 100 characters in length for each attribute. Multiple attributes are allowed and should be pipe-delimited. Examples: [“Correspondence”, “Humanities|Correspondence”, “COMM”] | Optional |
repeat_code_id
| Identifier for any repeat code associated for this course (must also be specified in the institution’s configuration sheet and only include foreign keys to those values). This is optional and only required if the enrollment records supplied in the feed do not filter out this information from the institution’s side. Repeat codes and actions should also be defined in the configuration sheet. Examples: “RC”, “NC” | Optional |
registration_status_id | An indicator if this enrollment record is currently registered or some other status that isn't considered fully registered (typically, only active enrollments that are included on a transcript are included in the enrollment feed but temporary status codes or withdrawn statuses may also be included). This value is defined in the registration_status feed. Examples: “W”, “pre registered” | Optional |
registration_reason_id recommended | This value may not be used by the SIS and can be blank if not defined. This value is defined in the registration_status feed. In combination with the registration_status_id, this value indicates if this enrollment record is currently registered or some other status that isn't considered fully registered. This value is used in combination with the registration_status_id above to determine the student’s registration status in this course enrollment. Examples: “WAIT”, “ENRL” | Optional |
metadata recommended | Note: this should only be supplied for transfer/test records and not all student enrollments. Optional course record information that can be displayed in the Stellic platform to assist students and advisors. This is used to provide additional transfer record information or for exam credits to indicate the original requirement on which this record is based. Displays in the platform along with the value “Transferred from” preceding the metadata value. This column can be a maximum of 200 characters in length. Examples: “MATH 150 College Algebra from Basic Community College”, “AP World History, score 4” | Optional |
| A list of tags associated with the student’s individual enrollment record. This field is highly flexible and can accommodate both strings and codes. Multiple values should be pipe-delimited.
Example: “Resident Credit”, “Resident Credit|In-State Transfer” | Optional |
| Boolean value whether this class enrollment is the enrollment component or not
Format: “TRUE”, “FALSE” | Optional |
Student Advisors
Optional—It is possible for a student to have more than one advisor and Stellic uses the word advisor loosely so it can be a primary advisor, faculty advisor and even extend to other roles like residence advisor, financial aid advisor, etc. Add multiple rows to associate a single student to multiple advisors. This feed is only required if advisor roles/titles are included or to manage advisor permissions by program, etc. Use of this feed also requires the submission of the advisor_role configuration feed.
Expected feed filename: student_advisor.csv
Samples: CSV
Field | Description | Requirement |
| The SIS username for the student. Used to link to the student basic feed and other student feeds. Examples: “161921” | required |
| Unique username for the advisor. These values must match the user attribute that is passed via SSO (often a username or ID number). These values must also exist in the user feed file (which is how we link to names and other information for display in the platform).
Examples: “57568” | required |
| Role/designation for this advisor. This value must match the “advisor_role_id” value on the advisor_role feed provided (the foreign key for that record).
Examples: “ACAD” | Optional |
| Unique identifier for the program. This value must match the “id” value on the program feed provided (the foreign key for that record).
Example: “BSME”, “MIN-CHEM” | Optional |
Stellic supports multiple advisor roles per advisor/student connection. In such cases, the advisor_role_name (from the advisor_role feed) will be displayed in the student’s profile record as a comma-separated list:
Student Credentials
This record is used to group a student’s programs to know which programs are being completed at a given time. For example, a student completing a major and minor at the same time would be grouped under this credential record to indicate they are being completed at the same time (e.g., BA degree with a major in Statistics and minor in Economics). Students can have multiple credential records indicating completion (graduation) of programs at different times (e.g., BS degree with a major in Statistics completed first and MBA degree completed later would be two different student_credential records).
Expected feed filename: student_credential.csv (formerly student_diploma.csv)
Samples: CSV
Field | Description | Requirement |
| Unique identifier for the student credential record. This can be the key value from your SIS or a unique combination of data (e.g., credential code plus student id; does not vary by term). This value must be unique but may be repeated in the student_graduation_application feed (if there are multiple applications/status for the same group/combination of student programs). This column can be a maximum of 100 characters in length.
Examples: “186971-ECON” | required |
| The SIS username for the student. Used to link to the student basic feed and other student feeds.
Examples: “d815017” | required |
| Unique identifier for the student’s credential record (a grouping of program values that the student will complete/graduate from at one time). This value must match the “credential_id” value on the credential feed provided (the foreign key for that record).
Examples: “ECON”, “CS_Degree” | required |
| Unique identifier for the student’s program. This value must match the “program_id” value on the program feed provided (the foreign key for that record). This value will also be found in the “program_id” column of the student_program feed.
In the event a student has multiple active program records, these values must be pipe-delimited.
Examples: “MIA”, “ECON_MJR|ART_MNR” | required |
Student Graduation Application
For institutions that utilize graduation clearance functionality in Stellic, this record is used to identify whether a student has applied to graduate for a set of programs in Stellic (in the student credential record). This record is used to manage the clearance process within Stellic, from application to awarding (or cancellation/rejection as needed). Once completed, this record will be used to push data back to the institution for use within institutional business processes.
Expected feed filename: student_grad_application.csv
Samples: CSV
Field | Description | Requirement |
| Unique identifier for the student graduation application record. This can be the key value from your SIS or a unique combination of data (e.g., credential code plus student id plus term plus application status). If the student has multiple applications for the same term (e.g., the first application was “rejected” status), this will need to be made unique for each occurrence. This column can be a maximum of 100 characters in length.
Examples: “186971-ECON-2218” | required |
| Unique identifier for the student credential record. This value must match the “student_credential_id” from the student_credential feed. Stellic will use this value to connect the graduation application record to a student. In case of multiple applications with different statuses and/or graduation terms for the same program grouping, this value will be repeated in this feed.
Examples: “186971-ECON” | required |
| The term when a student is expected to graduate from this program (for institutions with multiple graduation terms). This value is used to filter groups of students in the platform. Term names included must match configuration formatting (including capitalization).
Examples: “spring 2024”, “Fall 2023 | required |
| The status value of this application. This value must match a “grad_application_status_id” value from the grad_application_status feed. Example: “AW”, “RJ” | required |