Student Academic Record Domain - Best Practices
Contents
Sample Course Transcript Mapping
The following is a sample course transcript showing mappings to the Ed-Fi data model. Each circled number corresponds to an element in the Ed-Fi Data Standard; elements are listed below by number.
# | Description | Ed-Fi Entity | Ed-Fi Element | Condition(s) |
|---|---|---|---|---|
1 | Student | Student | FirstName LastSurname |
|
2 | Street Address | StudentEducationOrganizationAssociation.Address | StreetNumberName | AddressType = [SIS Default] |
3 | City/State/ZIP | StudentEducationOrganizationAssociation.Address | City StateAbbreviationDescriptor PostalCode | AddressType = [SIS Default] |
4 | Phone | StudentEducationOrganizationAssociation.Telephone | TelephoneNumber | TelephoneNumberType = [SIS Default] |
5 | Date of Birth | Student.BirthData | BirthDate |
|
6 | Place of Birth | Student.BirthData | BirthCity |
|
7 | Gender | StudentEducationOrganizationAssociation | SexDescriptor |
|
8 | Credits Earned | StudentAcademicRecord.CumulativeEarnedCredits | Credits | StudentAcademicRecord.SchoolYear = [Most Recent School Year] |
9 | Weighted GPA | StudentAcademicRecord.GradePointAverage | GradePointAverageValue | StudentAcademicRecord.SchoolYear = [Most Recent School Year] GradePointAverageTypeDescriptor = 'Weighted' IsCumulative = TRUE |
10 | Unweighted GPA | StudentAcademicRecord.GradePointAverage | GradePointAverageValue | StudentAcademicRecord.SchoolYear = [Most Recent School Year] GradePointAverageTypeDescriptor = 'Unweighted' IsCumulative = TRUE |
11 | School Year | StudentAcademicRecord | SchoolYear |
|
12 | Semester | StudentAcademicRecord | TermDescriptor |
|
13 | Code | CourseTranscript.CourseReference | CourseCode | CourseTranscript.StudentAcademicRecordReference → StudentAcademicRecord.SchoolYear = '2019 - 2020' CourseTranscript.StudentAcademicRecordReference → StudentAcademicRecord.TermDescriptor = 'Fall Semester' |
14 | Course | CourseTranscript.CourseReference | CourseTitle | CourseTranscript.StudentAcademicRecordReference → StudentAcademicRecord.SchoolYear = '2019 - 2020' CourseTranscript.StudentAcademicRecordReference → StudentAcademicRecord.TermDescriptor = 'Fall Semester' |
15 | Grade | CourseTranscript | FinalLetterGrade | StudentAcademicRecordReference → StudentAcademicRecord.SchoolYear = '2019 - 2020' StudentAcademicRecordReference → StudentAcademicRecord.TermDescriptor = 'Fall Semester' |
16 | Credits | CourseTranscript.EarnedCredits | Credits | CourseTranscript.StudentAcademicRecordReference → StudentAcademicRecord.SchoolYear = '2019 - 2020' CourseTranscript.StudentAcademicRecordReference → StudentAcademicRecord.TermDescriptor = 'Fall Semester' |
17 | GPA | StudentAcademicRecord.GradePointAverage | GradePointAverageValue | StudentAcademicRecord.SchoolYear = '2019 - 2020' StudentAcademicRecord.TermDescriptor = 'Fall Semester' IsCumulative = FALSE |
18 | Cumulative GPA | StudentAcademicRecord.GradePointAverage | GradePointAverageValue | StudentAcademicRecord.SchoolYear = '2019 - 2020' StudentAcademicRecord.TermDescriptor = 'Fall Semester' IsCumulative = TRUE |
Student Transcript Use Cases
Historical Records for Transfer Students
When students transfer into a new school district, they will have a history of completed courses from past school years that needs to be documented in the new district's SIS, in order to document graduation requirements, provide for transcripts for postsecondary school applications, and other reasons.
A common issue that arises when pulling this data into the ODS is the course records are associated with schools and districts that are not present in the new current data store. Therefore the required CourseCode and EducationOrganization references may be missing.
In this case, there are two recommended solutions:
If credit is being given for a course taken in a previous school year, an equivalent course may be found in the current data context. In this case, the CourseTranscript record should include the equivalent CourseCode in the Course reference. The new district or school applying the credit would then become the EducationOrganization reference as it is the entity accepting those credits towards the student's transcript.
Alternatively, the CourseCode can be set to not resolve. Ed-Fi has introduced as of Data Standard 3.2 the notion that certain references may be "potentially logical" only – i.e., that the entity referred to may not exist in the current context and may only be a "logical" reference. This status applies to CourseTranscript.CourseCode
Info for Ed-Fi Platform Users
Users of the Ed-Fi ODS can set this entity to not resolve. Please consult the ODS documentation for details.
Ticket reference:
- DATASTD-1559 - Getting issue details... STATUS
Course Transcript Data for a Course with Multiple Parts
Students who take multiple parts of the same course within the same term are unable to keep multiple transcript records because the data submissions would being overridden. This is a common use case for online schools that enroll students in multiple parts of the same course. These records will utilize the same CourseCode and TermType (e.g., "Year Round").
Proposed options for this issue are:
When the issue is an online course that has a single "Year Round" Session, create more granular Session records that can "roll up" to the Year Round StudentAcademicRecord. In this instance, cumulative credits would be added to the Year Round StudentAcademicRecord and credits for individual course parts would be spread across Semesters, Grading Periods, Marking Periods, etc..
Alternatively, if a student is truly enrolled in multiple parts of the same course at the same time (i.e., in the same more granular Session), the CourseTranscript could be used to only reference the credit-bearing course (i.e. the CourseCode for the LEA) for which the student received credits, and not the parts by which that course was satisfied. Those other parts might be captured elsewhere in the model as Sections.
Ticket references:
- DATASTD-1073 - Getting issue details... STATUS
- ODS-4612 - Getting issue details... STATUS
- DATASTD-1555 - Getting issue details... STATUS
Note
One proposed solution is to create a collection of sub-entities on CourseTranscript that can track incremental changes to credits earned. This would not be a breaking change to the model and the proposal is being tracked in DATASTD-1442.