Date: Thu, 28 Mar 2024 18:57:14 -0500 (CDT) Message-ID: <542941504.30174.1711670234997@PUBEDFIPRDWEB5.public.local> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_30173_164741379.1711670234991" ------=_Part_30173_164741379.1711670234991 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
A conceptual overview of the example that follows is co= ntained in the "Concep= tual Overview of How to Create a Custom Interchange Schema" section of = the Ed-Fi Data Standard: Developers' Guide documentation.
To illustrate how one would apply the Ed-Fi Data Model = for information exchange, consider how one would use the Ed-Fi Core XML Sch= ema to develop an interchange for a student transcript interchange from a h= igh school to a post-secondary institution.
The requirement is for a student transcript interchange= that would be appropriate for a high school or LEA to send to a post-secon= dary institution. For this interchange, the student transcript should have = the following information:
For this requirement, a single interchange is desired t= hat encapsulates one student=E2=80=99s data in one interchange file.
Referring to the Ed-Fi UML models, the desired informat= ion is reflected in the Assessment, Enrollment, Graduation, Student Academi= c Record, and Student Identification and Demographics models, as shown in t= he next set of figures.
=
Student Assessment Model (click to enlarge)
Enrollment= Model (click to enlarge)<= /span>
<= br>
Student Acade= mic Record Model (click to enlarge)
Student Ident= ification and Demographics Model (click to enlarge)
The preceding figures highlight the entities and the as= sociations required for the Student Transcript interchange in the UML model= s.
From this analysis, the following entities and associat= ions from the Ed-Fi Core XSD need to be included in the interchange:= p>
Table: Entities and Associations to Inclu= de in Interchange
Domain Required Information = td> | Ed-Fi Entities and Associations= p> |
Student identification = and contact information |
Student |
Standard NCLB demograph= ics, omitting any details on disabilities |
Student |
K=E2=80=9312 enrollment= history indicating the various schools attended |
StudentSchoolAssociatio= n |
Academic record showing= semester and final grades and credits earned for each secondary course tak= en |
CourseTranscript |
Scores for the yearly s= tate standardized tests (summary scores only) |
StudentAssessment = td> |
Yearly and final credit= s earned and grade point average (GPA) |
StudentAcademicRecord= p> |
Graduation plan and dat= e graduated |
StudentSchoolAssociatio=
n |
The student transcript interchange is meant to be stand= -alone, not requiring that the receiving system have any preloaded informat= ion. Thus any extended reference types used must have all of the informatio= n necessary for the receiving system.
We examine the selected entities and associations for r= eference types that are reference entities not identified to be included in= the interchange:
Table:=E2=80=82Examine Reference Types
Ed-Fi Entities and Associations= p> |
References Internal to the Interchange |
References External to the Interchange |
Student |
<none> |
<none> |
StudentSchoolAssociatio= n |
StudentReference | SchoolReference |
StudentAcademicRecord= p> |
StudentReference |
<none> |
CourseTranscript | StudentReference |
<none> |
ReportCard |
StudentReference |
<none> |
Grade |
StudentSectionAssociati= onReference |
GradingPeriodReference<= /p> |
StudentSectionAssociati= on |
StudentReference |
<none> |
Section |
CourseReference |
SchoolReference |
Course |
<none> |
EducationOrganization R=
eference |
StudentAssessment = td> | StudentReference | AssessmentReference = |
Examining each of the external references res= ults in the following conclusions:
With the required entities and associations identified,= the interchange schema file, EXTENSION-InterchangeHSGeneratedStudentTransc= ript-Extension.xsd, is created, including the Ed-Fi-Core.xsd. As described = earlier, an element is created for the interchange with an unbounded OR for= each of the required complex types, as depicted below:
Interchange Schema diagram
This results in the final interchange schema file as sh= own below:
<?xml= version=3D"1.0" encoding=3D"UTF-8"?> <!-- (c)2015 Ed-Fi Alliance, LLC. All Rights Reserved. --> <xs:schema xmlns:xs=3D"http://www.w3.org/2001/XMLSchema" xmlns=3D"http:/= /ed-fi.org/0200" targetNamespace=3D"http://ed-fi.org/0200" elementFormDefau= lt=3D"qualified" attributeFormDefault=3D"unqualified"> =09<xs:include schemaLocation=3D"Ed-Fi-Core.xsd"/> =09<xs:element name=3D"InterchangeHSGeneratedStudentTranscript"> =09=09<xs:complexType> =09=09=09<xs:choice maxOccurs=3D"unbounded"> =09=09=09=09<xs:element name=3D"Student" type=3D"Student"/> =09=09=09=09<xs:element name=3D"StudentSchoolAssociation" type=3D"Studen= tSchoolAssociation"/> =09=09=09=09<xs:element name=3D"StudentAcademicRecord" type=3D"StudentAc= ademicRecord"/> =09=09=09=09<xs:element name=3D"CourseTranscript" type=3D"CourseTranscri= pt"/> =09=09=09=09<xs:element name=3D"ReportCard" type=3D"ReportCard"/> =09=09=09=09<xs:element name=3D"Grade" type=3D"Grade"/> =09=09=09=09<xs:element name=3D"StudentSectionAssociation" type=3D"Stude= ntSectionAssociation"/> =09=09=09=09<xs:element name=3D"Section" type=3D"Section"/> =09=09=09=09<xs:element name=3D"Course" type=3D"Course"/> =09=09=09=09<xs:element name=3D"StudentAssessment" type=3D"StudentAssess= ment"/> =09=09=09=09<xs:element name=3D"School" type=3D"School"/> =09=09=09</xs:choice> =09=09</xs:complexType> =09</xs:element> </xs:schema>
Find out more about how to develop solutions based on the Ed-Fi Data Sta= ndard v2.0: