1. TEDS Texas Education Data Standards

2. TEDS is the new set of documented standards that will be used for TSDS PEIMS, Dashboard, Unique ID, and Core Collection Submissions. It will eventually replace the Legacy Data Standards. The standards include:  Data Reporting Requirements  Data Element Descriptions  Responsibilities of LEA, ESC, and TEA  Data Collection Requirement Descriptions What is TEDS?

3. TEDS Documentation http://www.texasstudentdatasystem.org/TSDS/TEDS/ TEDS_Latest_Release /

4. Sections in TEDS

5. The Introduction Section includes the Table of Contents, the Forward, the Preface, and the Acknowledgements for the Texas Education Data Standards (TEDS). Introduction to TEDS

6. Data Submission Specifications and Responsibilities TEDS Section 1

7. Provided in this section: Brief descriptions of TEDS, PEIMS, and TSDS The descriptions of the interchange schemas used to load data to the EDW (Education Data Warehouse) The As-of-Dates and Submission Due Dates Responsibilities of the LEA (Local Education Agency), ESC (Education Service Center), and TEA (Texas Education Agency). Data Submission Specifications and Responsibilities

8. There are 18 different interchange files that are used for the TSDS system. The files are created in XML format. The files have a specific naming convention. Not all files are used for each submission. The files must be loaded in a specific order. TSDS Interchanges

9. Interchanges and Loading Order 1. InterchangeEducationOrganizationExtension10. InterchangeStudentGradeExtension 2. InterchangeEducationOrgCalendar11. InterchangeStudentTranscriptExtension 3. InterchangeMasterScheduleExtension12. InterchangeStudentProgramExtension 4. InterchangeStudentExtension13. InterchangeAssessmentMetadata 5. InterchangeStudentParentExtension14. InterchangeStudentAssessment 6. InterchangeStudentEnrollmentExtension15. InterchangeStudentCohort 7. InterchangeStaffAssociationExtension16. InterchangeSSAOrganizationAssociationExtension 8. InterchangeStudentAttendance Extension17. InterchangeFinanceExtension 9. InterchangeStudentDisciplineExtension18. InterchangeStudentRestraintEventExtension

10. Position1-678-101112-202122-333435 DescriptionDistrict Code _Campus ID_Collection Code _Timestamp_Interchange XML Naming Convention Examples: 220950_000_2016FALL1_201509281015_InterchangeEducationOrganizationExtension.xml 220950_000_2016MDYR1_201512101015_InterchangeFinanceExtension.xml

11. CodeCode Description FALL1PEIMS Fall First Submission FALL2PEIMS Fall Resubmission FALL3PEIMS Fall Working Collection MDYR1PEIMS Mid-Year First Submission MDYR2PEIMS Mid-Year Resubmission MDYR3PEIMS Mid-Year Working Collection SUMR1PEIMS Summer First Collection SUMR2PEIMS Summer Resubmission SUMR3PEIMS Summer Working Collection EXYR1PEIMS Extended Year First Submission EXYR2PEIMS Extended Year Resubmission EXYR3PEIMS Extended Year Working Collection TSDSTSDS studentGPS Dashboards and Core Collections Collection Codes

12. Data Submission Requirements TEDS Section 2

13. Provided in this section:  Chart of Data File Layouts  Chart of Complex Types and the associated collection(s)  Descriptions of each complex type and extension schemas  Business rules, reporting requirements, and data samples Section 2 – Data Submission Requirements

14. Data Reporting Categories

15. This category provides information about the Local Education Agency (LEA or District) and the Education Service Center (ESC) servicing the LEA including demographics and performance rating indicators. A Complex Type Chart is included that provides the element information, XML name, simple name, submissions, field length and type, and associated code tables for each element in the Education Organization Category. The business rules for this category are also included in this section as well as data samples, and any special reporting requirements Section 2.1 Education Organization Category

17. Sample of Education Organization in XML File

18. This category provides financial data for the ESC and LEA such as actual, budget, and shared services arrangement. A Chart of the ActualExtension Complex Type is included which provides element information, XML Name, simple name, submissions, field length and type, and code tables for element. The business rules for this category are also included in this section, as well as Resource Guide Models, data samples, and any special reporting requirements. Section 2.2 Finance Category

20. Sample of Finance in XML File

21. This category provides personnel, demographic, assignment, teaching, and attendance information for district staff. Charts of staff related complex types are included in this section which provides element information, XML Name, simple name, submissions, field length and type, and code tables for element. The business rules for this category are also included in this section, as well as data samples and any special reporting requirements. Section 2.3 Staff Category

23. Sample of Staff in XML File

24. This category provides student demographic information, student attendance, enrollment and leaver information, special programs, course history, discipline, and assessment information. Charts of student related complex types are included in this section which provides element information, XML Name, simple name, submissions, field length and type, and code tables for element. The business rules for this category are also included in this section, as well as data samples and any special reporting requirements. Section 2.4 Student Category

26. Sample of Student in XML File

27. This category represents the student-teacher classroom link. It contains information about the section such as the course, section number, class period, and population served. It also includes the class Id number which links the teacher, student, and section to each other. Charts of course section related complex types are included in this section which provides element information, XML Name, simple name, submissions, field length and type, and code tables for element. The business rules for this category are also included in this section, as well as data samples and any special reporting requirements. Section 2.5 Campus Course Section Category

29. Sample of Course Section in XML File

30. This category represents the student assessments, specifically the definitions of the assessments, the learning objectives, learning standards, and assessment items. Charts of assessment related complex types are included in this section which provides element information, XML Name, simple name, submissions, field length and type, and code tables for element. The business rules for this category are also included in this section. The assessments are only used for the dashboards. Currently, if the district approves, TEA will load STAAR and EOC assessments for the district. TEA is working on furure uploads for TELPAS, SAT and ACT. Districts can upload local assessments, but the files must meet the requirements and formatting outlined in this section. Section 2.6 Assessment Category

31. This category represents student cohorts and is used to report associations between students and teachers. Charts of cohort complex types are included in this section which provides element information, XML Name, simple name, submissions, field length and type, and code tables for element. The business rules for this category are also included in this section, as well as data samples and any special reporting requirements. The cohorts are used for the ECDS KG and ECDS PK submissions as well as for the dashboards. Section 2.7 Cohort Category

33. Sample of Cohort in XML File

34. Description of Data Elements TEDS Section 3

35. Provided in this section:  Description of data elements  Description of data elements by category  Description of data elements by sub-category  Description of data elements by complex type  Definitions of each data element  Description of information found in definitions (see handout) Section 3 – Description of Data Elements

36. This section includes a table of contents which lists the sub- categories by code and complex types with page numbers, Submission Charts, and the Data Elements. Submission charts of data elements by sub-category are included. These charts include:  Element ID  Element name  XML name  Submissions  Potential Future Use Section 3.1 Education Organization Category Description of Data Elements

40. This section includes a table of contents which lists the sub- categories by code and complex types with page numbers, Submission Charts, and the Data Elements. Submission charts of data elements by sub-category are included. These charts include:  Element ID  Element name  XML name  Submissions  Potential Future Use Section 3.2 Finance Category Description of Data Elements

44. This section includes a table of contents which lists the sub- categories by code and complex types with page numbers, Submission Charts, and the Data Elements. Submission charts of data elements by sub-category are included. These charts include:  Element ID  Element name  XML name  Submissions  Potential Future Use Section 3.3 Staff Category Description of Data Elements

48. This section includes a table of contents which lists the sub- categories by code and complex types with page numbers, Submission Charts, and the Data Elements. Submission charts of data elements by sub-category are included. These charts include:  Element ID  Element name  XML name  Submissions  Potential Future Use Section 3.4 Student Category Description of Data Elements

52. This section includes a table of contents which lists the sub- categories by code and complex types with page numbers, Submission Charts, and the Data Elements. Submission charts of data elements by sub-category are included. These charts include:  Element ID  Element name  XML name  Submissions  Potential Future Use Section 3.5 Campus Course Section Category Description of Data Elements

56. This section includes a table of contents which lists the sub- categories by code and complex types with page numbers, Submission Charts, and the Data Elements. Submission charts of data elements by sub-category are included. These charts include:  Element ID  Element name  XML name  Submissions  Potential Future Use Section 3.6 Assessment Category Description of Data Elements

60. This section includes a table of contents which lists the sub- categories by code and complex types with page numbers, Submission Charts, and the Data Elements. Submission charts of data elements by sub-category are included. These charts include:  Element ID  Element name  XML name  Submissions  Potential Future Use Section 3.7 Cohort Category Description of Data Elements

64. Description of Codes TEDS Section 4

65. Provided in this section:  Alphabetical listing of the names of the code tables that coincide with the data elements in Section 3  Description of the information in the code tables “C” = PEIMS Code Tables “DC” = Dashboard Code Tables  Code Tables in Numeric Order Explanations Translations Helpful Links Section 4 – Description of Codes

67. Sample of PEIMS Code Table

68. Sample of PEIMS Code Table with Explanations and Helpful Links

69. Sample of Dashboard Code Table

70. Business Rules & Validations TEDS Section 5

71. This section defines the business rules and validations that are applied to submitted data. When data does not pass validation one of the following error level results are possible:  F = fatal  S = special warning  W = warning Section 5: TEDS Business Rules

73. PEIMS Data Submission Summary

74. A district's data are validated against business and field validation rules to verify that all required data category types have been submitted. The data submission specifications found above refer to the submission(s) in which the data category type is required or allowed. The data category type may not be reported in any submission other than that specified. A district's data are validated against business and field validation rules detailed below to verify that the data is complete, reasonable, meaningful, and accurate. Each business rule has the following indicators shown:  Error level: Indicator of the severity of the error where F = fatal, S = special warning, and W = warning.  Sub: Indicator of which PEIMS submission(s) to which this rule applies, where 1 = Fall, 2 = Mid-Year, 3 = Summer, and 4 = Extended Year.  Rule Applies To: Indicator of the organization types to which this rule applies, either ESC, District, Campus, and/or Charter. If a rule applies to an organization type, that column will contain an "X". If a rule does NOT apply to an organization type, that column will be blank. Data Submission Rules

75. The PEIMS Data Standards XML schema ensures that the data files from school districts adhere to a common structure and consist of valid elements and attributes. An XML extract file must be syntactically perfect or it is rendered as unacceptable by an XML parser. Restrictions control acceptable values for XML data elements. In combination with an element’s declared data type, restrictions enable the XSD validation process not only to validate the structure of the XML file but also to validate the data values contained within the file against its XML schema definition. The XML schema also enforces length restrictions for a given element by either an exact length, minimum length, or maximum length. Many simple type elements within the PEIMS XSD have a restriction that limits the domain of acceptable values. PRE-LOAD AND VALIDATION RULES

76. Data element fields are validated against their data element descriptions as provided in Section 8.3 according to these general field validation rules: Data Type  Numeric data type elements must contain numeric characters and not have leading spaces.  Name Field and Coded data type elements must contain only the characters listed with those data types in Section 8.3.  Coded data type elements that contain a value must not contain any blanks within the value. Domain - If the element has a domain of values specified in Section 8.3, the reported value must fall within the specified domain. Pattern - For each individual position of the data element, the reported value must contain only the data type and characters allowed by the defined pattern. Code Table - If an element has a code table, the reported value must be in the specified code table. Data Element General Field Validation Rules

78. XML XSD Schemas TEDS Section 6

80. Section 6: Ed-Fi Core Schema

81. Section 6: Tx-Core Extension Schema

82. Interchange Schemas TEDS Section 7

84. Interchange Education Organization Extension.xsd - Schema

85. Interchange Education Organization Extension.pdf – Collection Reqs

86. Interchange Education Organization Extension.xml – Data Sample(s)

87. PEIMS-Interchange Education Organization Extension.xml

88. TEDS Appendices

90. Appendix B: TEDS Alphabetical List of Data Elements and Associated Complex Types

91. Appendix C: TEDS List of Data Elements by Element ID and Associated Complex Types

92. Appendix D: PEIMS Leaver Reason Codes and Documentation Requirements

93. Leaver Reason Codes and Documentation Requirements

94. Appendix P: PEIMS Data Submission Guide

95. Shared Services Arrangement Example #1

96. TEDS Change Logs

97. This section serves as a central location for the TEDS change logs for the 2015-2016 school year. The change logs are listed in order by the release date. 2015-2016 TEDS Change Logs

98. Post Addendum Version Change Log

99. eDM Error Dictionary Excel

100. The eDM Error Dictionary serves as a means to interpret errors when loading XML files into the eDM. In the Excel format the columns can be sorted and a search feature is available. eDM Error Dictionary – Excel Format

101. The eDM Error Dictionary serves as a means to interpret errors when loading XML files into the eDM. In the PDF format a search feature is available and reference links are provided. eDM Error Dictionary – TSDS PDF Format

102. The eDM Error Dictionary serves as a means to interpret errors when loading XML files into the eDM. In the PDF format a search feature is available and reference links are provided. eDM Error Dictionary – TSDS PEIMS PDF Format