This how-to guide is for school districts and charter schools to export child progress monitoring data from CLI Engage to upload to the Early Childhood Data System (ECDS), part of the Texas Student Data System (TSDS). CLI Engage’s XML data export tool was developed and tested with the Texas Education Agency to facilitate efficient exporting from CLI Engage and uploading to TEA.
The XML File Download tool can be used to export child assessment data from the CIRCLE Progress Monitoring System and Texas Kindergarten Entry Assessment.
ECDS PreK and Kindergarten submissions are due on different dates for the 2019-20 school year:
Read Our FAQs for additional information.
Before using the XML File Download tool on CLI Engage, we strongly recommend confirming that TSDS IDs were uploaded for all students. Refer to this how-to guide for more information: Student TSDS ID Verification Information
Login to CLI Engage and scroll down to the administrative section on the dashboard and click the button for the “XML File Download” button.
Note: Community/district administrators and specialists, school specialists, and principals can access this tool. Access can be granted to others upon request. Please submit a help ticket for assistance.
Your school district or charter school may have used the CIRCLE Progress Monitoring System and/or the Texas Kindergarten Entry Assessment this year. Also, teachers may have assessed children in more than one language. If so, you will export child progress monitoring data from each assessment tool and each language separately. Follow the same steps to export results for either assessment and/or language, as needed.
CIRCLE Progress Monitoring PreK XML Details:
Texas Kindergarten Entry Assessment XML Details:
Your school district or charter school may have assessed children in more than one language. If so, you will export child progress monitoring data from each language separately. Follow the same steps to export results for either language. Select “CIRCLE Progress Monitoring English.”
Select Community or District.
Select Schools. To generate a report for all schools in your district, “Select all.” DO NOT select your “Demo School.”
Select Wave 1 or Wave 3 (these were formerly both checked off) – we have updated this step so that you can generate the reports separately. We recommend you run & submit Wave 1, then after that is successful, you run & submit Wave 3:
Use the DOB range fields (optional) to limit the data exported into your XML report for students within a certain age group, calculated as of 9/1/19. The table below details the high and low age limits to include in the DOB range fields, if desired.
Click “Generate Report.”
After a few minutes refresh the page. The Status column will change from “Pending” to “Succeed,” and the Action column will either show 2 icons or “No Data.”
If you see “No Data” under the “Action” column, your students don’t have TSDS IDs listed in CLI Engage. The XML export tool will only export scores for students with TSDS IDs.
Please see the how-to guides linked at the bottom of the page to update TSDS IDs for your students.
If you see icons under “Action,” review the “Missing TSDS ID Report.” This report shows the Students with an invalid 10-digit TSDS ID. Students with an invalid TSDS ID will not be exported from CLI Engage and NOT included in the exported XML file. If needed, update students’ TSDS IDs in CLI Engage and repeat all steps to download an updated XML file before submitting to TEA. For more information, please see related resources at the bottom of the page.
Note: CLI Engage will not confirm the validity of the TSDS ID with TSDS, only confirm that students’ have a 10-digit number in the field for “TSDS ID.” School districts/charter schools should confirm that students’ TSDS IDs were uploaded correctly to CLI Engage.
Once the Student TSDS IDs are updated, click to “Download XML File” and submit to TEA. The XML files will export into a zipped folder. As a reminder, this XML export tool was designed to export child progress monitoring data from CLI Engage in the correct format for uploads to ECDS. Therefore, there is no need for district/charter staff to manipulate these files to conform to TEA’s requirements. If you have questions about TEA’s ECDS portal, please contact TEA directly (email@example.com).
Repeat the process (steps 4-11), if needed, to export student results in Spanish for CIRCLE Progress Monitoring, or student results in TX-KEA for either language.
For assistance using the XML File Download on CLI Engage, please submit a help ticket: www.texasschoolready.org/help.
For Policy questions regarding assessments can be sent to: firstname.lastname@example.org
For ECDS uploading technical issues, submit a TIMS ticket at: https://tealprod.tea.state.tx.us/TSDS/Support
If you receive an error message from TEA, here are important points about the way the XML files are produced in Engage:
The XML report uses the Student Assessment Language value (which can be changed at the Student page, or with Class Roster Management, or Student BUP, or Single Roster) and the Exclusion status on the assessment view to include or not Students and their scores.
When the measure is Excluded, nothing is reported for that Student.
If Math or Social Emotional Behaviors need to be excluded, all of their sub-measures need to be excluded; if one measure is not, the -999 score will be reported.
Measures not Administered
If there is no score on a measure, the XML file will have a score of -999 which, for TEA, means “Not Administered”.
Since the XML files must have the Administration Date for all scores, the system provides the date stamped in the database when the Teacher clicked “Submit” after completing each measure for each child, or when Offline scores were synced.
In the case of a -999 score, the database does not have any date; the XML process has to produce a date with different rules for each Wave:
Some Districts may find fatal errors when submitting their reports to ECDS. Some of those fatal errors are conflicts between the Assessment Administration Date and the enrollment date on TEA’s side.
I.e., a Student enrolled in the District on 8/25/19, was created in Engage on 9/1/19, and was assessed on 9/20/19 for Wave 1 except for one measure, let’s say Math, and left the District on 1/8/20. In this case, 4 scores for Wave 1 will be reported with the 9/20/19 date and Math will be reported as -999 on 9/1/19. This submission will not produce fatal errors because on TEA’s side the Student the Student belonged to the District on 9/1/19 and 9/20/19.
The recommendation is to run XML reports for Wave 1 only, identify possible data conflicts, submit to ECDS and fix the date-related errors by:
Each solution will depend on the number of errors to fix and Districts should consider if there is a valid reason to do such modifications. If the Student was not enrolled in the District during their assessment window for Wave 1, it is perfectly valid to Exclude the measures or alter the TSDS ID to prevent those records being included on the XML files. Similarly, if a Student’s Special Education plan, known as IEP, indicates that the student should not be assessed, it is perfectly valid to do the same.
Once Wave 1 data has been submitted successfully, restore the original values (Grade Level or TSDS ID)
A Student Results Export report with the following measures, for both, English and Spanish, one Wave at a time, will be very useful:
If you need guidance with the solutions listed above, please submit a Help Ticket and our Client Support Team will assist further.
This document was last modified on: January 21, 2020