Schoolzilla's Graduation Plan data tables lay the groundwork for tracking students' progress toward meeting credit requirements for graduation.
These tables are only available if you have grades stored in Schoolzilla.
dimGraduationRequirement
- Use this table to determine the credit requirements for one or more graduation plans.
- Table contains:
- One row per graduation plan per credit area
- A summary row per graduation plan containing the total number of credits required for the plan
- Table can be joined to dimClass and dimStudent.
- Supported concepts include:
- Graduation plan name
- Credit area
- Total credits required per area
- A flag for which plan is the "default" graduation plan to be applied to a student's record if NULL in the student information system (SIS)
- Multiple graduation plans are included in this table. However, only one plan may be associated with a student's record at this time. The data model only supports linking credits earned; it does not support linking test data or other graduation requirement data, such as Oregon's Essential Skills, at this time.
- Join this table to the DimClassGraduationRequirementAssociation table using the GraduationRequirementKEY (note that it's the "Graduation Requirement KEY" (with spaces) in the DimClassGraduationRequirementAssociation table.)
dimClassGraduationRequirementAssociation
- Use this table to determine which classes are associated with a graduation plan
- Table contains one row per class (where class is a specific class and section combination)
- Table can be joined to dimClass and dimGraduationRequirement
- Join this table to the DimClass table using the classKEY
dimStudent
- This table contains demographic and other information specific to each student
- Relevant Columns
- GraduationPlanID: contains the graduation plan id associated with a student's record in the SIS
- Standardized_GraduationPlanID: contains the graduation plan id for the plan associated with a student's record in the SIS. If the student's graduation plan record from the SIS is NULL, this column will contain the plan specified via Data Configuration Settings. Note: the ability to specify a default graduation plan is not yet available.
- Only one graduation plan can be associated with a student's record at this time
Here is a schema of how these tables can be joined with tables in our Grades data block.
Supported Student Information Systems Detail
Aeries / Aeries API
- Aeries is unique in storing graduation requirements per-grad-level in the REQ table.
- For each graduation requirement, there is one column to store required credits for grades 9, 10, 11, and 12
- We unpivot these per-grade-level requirements and create a unique SystemGraduationRequirementID for every grade, requirement area, and specific graduation requirement.
- Graduation requirement names are populated from the COD table
- This requires entries for Table REQ, Column GRT to be populated.
- If no graduation requirement values are populated in this table, the graduation requirement name will just be the single character graduation requirement code
- A blank (not NULL) value is a valid graduation requirement code
- To determine course/graduation requirement associations, we use the SubjectArea1Code on the courses table to match with the Graduation Requirement SubjectAreaCode table
Aspen
- Graduation plans and requirements are populated from the GRADUATION_COURSE_REQUIREMENT and GRADUATION_REQUIREMENT tables.
- Students are linked to graduation plans using the GRADUATION_STUDENT_PROGRAM table
Ed-Fi
- Graduation plans and requirements are populated from the GraduationPlan and GraduationPlanType tables.
- To determine course/graduation requirement associations, we use the GraduationPlanCreditsByCourse.csv file. This file provides an explicit mapping using the IdentityCourseCode field.
eSchoolPlus
- Graduation requirements are populated from the MR_GRAD_REQ_DET table
- Unique SystemGraduationRequirementIDs are generated for every district, requirement group, student graduation year, and requirement code
- Graduation plans are generated by district, requirement group, and student graduation year
Illuminate
- To determine course/graduation requirement associations, we match using the course_requirement_category_id field
- Illuminate only allows for one 'is_grad_check' flag per school year. This flag is used to determine which of the various graduation plans in Illuminate is used for each year.
- Students have a 'course_requirement_id' field that stores a graduation plan year, which is then linked back to that year's grad plan that has 'is_grad_check' = 1
Powerschool
- We use multiple methods to try to determine a class/graduation requirement area association.
- If the CourseSource in the GradReq table is 'any' (typically used for electives classes) we use the value in the CreditType column from the GradReq table if it is populated. Otherwise, we use the value from the Name column in the GradReq table.
- If the CourseSource in the GradReq table is 'credittype' we simply use the value in the CreditType column from the GradReq table. If that is not populated, we use the value from the Name column in the GradReq table.
- For CourseSource values of "group" and "listed", we try to match courses from the GradReq table to the powerschool_Courses table in order to obtain the applicable CreditType value from the Courses table. If that is not populated, we use the value from the Name column in the GradReq table.
Synergy
- To determine course to credit area associations, we join courses to a credit area using the subject_area_1 column from the REV_EPC_CRS table.
- Schoolzilla only supports one graduation requirements set per graduation plan/diploma type. In Synergy, there is the possibility to have different requirements within the same plan based on the year or graduation. Schoolzilla will use only the requirements for the most recent year.
Tyler
- Tyler SIS does not support exporting graduation plans, it is required that a template be filled out and uploaded via MyData to populate your graduation plan tables.