PDF

DATA SUBMISSION RULES

 

A district's data are validated using business validation rules to verify that the data is complete, reasonable, meaningful, and accurate. Each rule has the following indicators:

 

Column	Values	Description
Rule Type	Field Validation	Data is checked according to their complex type definition to ensure uniqueness and completeness. ·         Fields that have been specified as the unique key will be used to verify that no duplicate keys are reported. ·         Fields that have been specified as mandatory will be verify so that none are blank or not reported.
	Business Context	Data will be verified for business context to ensure the integrity of the database and compliance with data standards.   Some context rules compare data element fields within a single data category type item, while others compare data element fields across different data category types. Finally, some context rules evaluate data that is aggregated in some way (summed, averaged) with thresholds or other criteria
Rule #		Unique number to identify each rule. The first five numbers of the rule correlates to the subcategory code of the data being validated.
Rule Text		Logical text explaining the rule.
Business Meaning		Explanation of the rule using business terminology.
Error Level	F	Fatal: Indicates a critical error in the data. Neither an LEA or an ESC can mark data "complete" with fatal errors. Data with fatal error(s) will not be accepted by TEA for any TSDS collection and must be corrected.
	S	Special Warning: Indicates a potential discrepancy in the data that must be scrutinized carefully and corrected when needed.
	W	Warning: Indicates a possible error or inconsistency. A Warning error must be reviewed for data accuracy.
TSDS	Y or blank	Indicator of whether this rule applies to data for a TSDS Core Collection.
PEIMS Sub		Indicator of the PEIMS submission(s) to which this rule applies
	1	Fall
	2	Mid-Year
	3	Summer
	4	Extended Year
Rule Applies To	Y or blank	Indicator of the organization types to which this rule applies, either ESC, District, Campus, and/or Charter.   Collection: Rules can apply to: ESC District Campus Charter Class Roster N Y Y Y ECDS-KG N Y N Y ECDS-PK N Y N Y ECDS-Private PK N N Y N PEIMS Y Y Y Y RFT N Y N Y SPPI-14 N Y N Y   For rules that are shared between collections but apply to different organization types, the Rule Applies To columns will display the least restrictive collection (generally PEIMS). More restrictive collections will be governed by the assumptions in the table above.   For example, rule 40100-9999 is shared between PEIMS and ECDS-KG. TEDS will display Y in the Rule Applies To District column and Y in the Rule Applies To Campus column. ·         For PEIMS: the rule applies to district and campus validations. ·         For ECDS-KG: the rule applies to district validation. The rule does not apply to campus validation because the blanket assumption from the table above that ECDS-KG rules do not apply to campus validations.

 

 

 

 

STAFF PAYROLL CALCULATED VALUES

 

Full Time Equivalents (FTEs) are calculated in the following manner:

 

If NUMBER-DAYS-EMPLOYED is greater than or equal to 187 then FTE = PERCENT-DAY-EMPLOYED divided by 100.

 

If NUMBER-DAYS-EMPLOYED is less than 187, then FTE =

(PERCENT-DAY-EMPLOYED divided by 100) X (NUMBER-DAYS-EMPLOYED)
                                                        187

 

Base Salary is the total of all PAYROLL-AMOUNTs where PAYROLL-ACTIVITY-CODE is 80.

 

FTE Salary is Base Salary divided by FTE.

 

 

 

 

SEPTEMBER 1, 2019 AGE CALCULATION ALGORITHM FOR STUDENTS

If the Birth Year is either of the calendar years spanned by the school year, then calculated Age is 0.

 

Otherwise, the Birth Year is subtracted from the first year the calendar years spanned by the school year resulting in the Age. For example, for the 2019-2020  school year, the Birth Year is subtracted from 2019.

 

The Age is then adjusted for the month and day to get September 1 Age.

• If the Birth Month is Before September, then no adjustments are needed.
• If the Birth Month is After September, then 1 is subtracted from the Age.
• If the Birth Month Is September and the Birth Day is after the first, then 1 is subtracted from the Age.
• If the Birth Month Is September and the Birth Day is the first, then no adjustments are needed.

 

Unless otherwise specified in a rule, Age refers to September 1 Age.

 

 

 

 

SPECIAL NOTE ABOUT ATTENDANCE CONTEXT RULES

Due to the complex nature of attendance reporting, certain assumptions must be made so that each rule is performed uniformly throughout the submission, based on the wording of the rule. Depending on the wording, the rule will perform the evaluation based on data reported on one individual item, aggregated data reported on more than one item, data across data category types, or any combination of the three. The following wording assumptions apply to attendance rules.

 

"For each Attendance data item" - This wording limits the rule to one individual attendance item, meaning one instance of the complex type.

 

"For a particular" - This wording will cause the rule to search for all attendance items with identical matching values for the specified element(s), add the attendance data if applicable, then perform the evaluation.

 

"Matching" items - Rules which refer to "matching" elements/items will compare data across related data category types (Special Education Attendance item to an Attendance item, etc.). The items match when they contain identical values for certain data element fields in each item. The type of Special Programs Reporting Period Attendance is identified based upon ATTENDANCE-EVENT-INDICATOR. The following situations occur:

 

1. Some items are related based on matching values for element(s) specified in the rule text.

 

2. For non-flexible attendance rules, if no element(s) is specified for matching using “for a particular” or a list of elements, the attendance items are related based on matching values for these elements from the key of each of the items:

• DISTRICT-ID
• TX-UNIQUE-STUDENT-ID
• CAMPUS-ID-OF-ENROLLMENT
• INSTRUCTIONAL-TRACK-INDICATOR-CODE
• REPORTING-PERIOD-INDICATOR-CODE
• GRADE-LEVEL-CODE

For example, when a Special Education Attendance rule refers to a "matching" Attendance data item, data from the Special Education Attendance data item will be compared to data from the Attendance data item that contains identical values for the 6 key fields listed above.

 

3. For flexible attendance rules, if no element(s) is specified for matching using “for a particular” or a list of elements, the attendance items are related based on matching values for these elements from the key of each of the items:

• DISTRICT-ID
• TX-UNIQUE-STUDENT-ID
• CAMPUS-ID-OF-ENROLLMENT
• INSTRUCTIONAL-TRACK-INDICATOR-CODE
• REPORTING-PERIOD-INDICATOR-CODE
• GRADE-LEVEL-CODE
• FLEXIBLE-ATTENDANCE-PROGRAM-TYPE-CODE

 

For example, when a Special Education Flexible Attendance rule refers to a "matching" Flexible Attendance data item, data from the Special Education Flexible Attendance data item will be compared to data from the Flexible Attendance data item that contains identical values for the 7 key fields listed above.