May 9th Town Hall

1. May 9th Town Hall • Purpose • Goal - is to provide a weekly forum to answer LEA questions on Data Pipeline and inform LEA’s on any upcoming news and updates. Support at: datapipeline.support@cde.state.co.us

2. Webinar Etiquette • Mute Your Phone (*# Mutes and Un-mutes Individual Phones) • Enter your Name and your District when logging into the webinar (no password will be needed) • For today’s event, we will hold the Q&A session at the end of the presentation: • Type it in the Chat Box for a response OR • Raise Your Hand: • A presenter will call your name • After your name is called, un-mute your phone and speak your question/comment • Please be respectful of others time; we may need to have a separate conversation later to best help you

3. Introductions • CDE Staff Introductions

4. Talking Points • Teacher Student Data Link • Vendor Update • Data Pipeline Pilot Update – • Special Education Discipline, RITS and EDIS • Tagging • Data Pipeline Website • District Exchange of Data

5. 5 Teacher/Student Data Link • Pilot update • Two districts participated in the phase I pilot • Phase II scheduled to begin 5/13/13 • CDE needs a contact from each district. Please send contact info to vance_c@ cde.state.co.us and/or severson_a@cde.state.co.us • TSDL Interchange • Interchange opens 9/1/13 • Required collection HB-13-1219 • TSDL Snapshot • Snapshot will be created over the summer 2013 • Intent is to collect data all year long with a final snapshot approval around September 2014. More to come…..

6. 6 Vendor Update • CDE • Infinite Campus update • Student Interchange – June 2013 • Title I tab for Services Collection, Title I Interchange – July 2013 • SPED Discipline Interchange – July 29, 2013 • SPED IEP Interchange – August 2013 • Teacher/Student Data Link Interchange - TBD • Weekly vendor calls • Districts • Work with your vendor to test the files to ensure that are working correctly. • Update Directory with your vendor data

7. 7 RITS/EDIS Pilot Phase II RITS/EDIS Phase II Pilot Summary All districts encouraged to test the system. The more that we can find and address now the smoother it will be when we go live July 1st , 2013. Please e-mail any issues, concerns, and/or suggestions. If you would please include screen shots in your e-mail correspondence. Debbie Puccetti Puccetti_d@cde.state.co.us 303-866-6612

8. 8 RITS/EDIS Go Live Training RITS Data Pipeline Training If you have not already registered for the upcoming RITS training you may do so at: To register for the trainings please visit https://www.surveymonkey.com/s/2013RITSDataPipelineTraining The trainings will include : • Submitting a RITS READ file • Using the Match Tool when submitting a RITS READ file • Submitting a RITS Batch file • Cognos Reports Stay Tuned for information on EDIS Data Pipeline Training sign up and dates to be announced soon

9. Special Education Discipline Pilot • Special Education Discipline Pilot Update

10. 10 Student October Pilot Phase II All districts encouraged to test the system. The more that we can find and address now the smoother it will be when we go live September 1st , 2013. Please e-mail any issues, concerns, and/or suggestions. If you would please include screen shots in your e-mail correspondence. Kevin Smith Data Analyst smith_kevin@cde. state.co.us 303-866-6723 THANK YOU

11. 11 Tagging at interchange level • Issue – Collection data could overlap • For example, the Student October collection requires multiple fields for a student be reported as of a pupil enrollment date of October 1st. (pupils attendance info or public school funding status) • December count collection information must be reported as of December 1st. • Districts want to report the most recent values for pre-coded labels • The data for all three of these collections could overwrite each other and an incorrect value could be pulled into a collection.

12. 12 Tagging at interchange level • Solution – Tagging • Districts can load data in the interchange and tag the records for the Student October collection or December Count. • Districts can continue to load a file with the most up to date values for the pre-coded labels collection. • Tagging the records allows multiple sets of data to exist at the interchange level.

13. 13 Tagging at interchange level • How does it work? • Districts load a file with records they would like tagged. When districts load the data they select the tag name (For example: Student October or December Count). • The tag name is applied to each record in the file and the record is stored in a holding table. • Districts can continue to load students with more current information. These records are tagged with none indicating no tag is selected.

14. 14 Tagging at interchange level • Sample screen shot – default tag is none

15. 15 Tagging at interchange level • How does it work? • The snapshot will pull the data on a priority basis. If two records exist for the same primary key, the record which is tagged will be pulled over the record which is not tagged. • The file format remains the same whether records are tagged or not. • LEAs can maintain tagged records in the interchange separate from the ‘current values’ stored in the interchange

16. 16 Tagging at interchange level • This is an optional feature - districts do not have to use tagging. • Tagging provides a way for districts to have Student October, December Count, and pre-coded label data in the interchange at the same time. • Tagging is only available with file uploads. • Tagging was designed based on LEA feedback and suggestions

17. 17 Tagging Questions? • Tagging is in the design review phase • Pilot set for June 2013 • Other questions?

18. Data Pipeline Website • Update on the Data Pipeline Website http://www.cde.state.co.us/DataPipeline/index.asp

19. District Exchange of Data Four types of data Assessment/Growth English Language Learner Discipline IEP Obtained opinion from Attorney General’s office Districts must include notice to parents through enrollment process Data may be shared if student enrolls in another district Purpose is to alert receiving district Contact other district Determine details of information presented Initiated by student transfer SASID must match Not detention center related Accessibility E-mail alerts- 30 days to retrieve file District assigned individuals may access CDE can generate after purged, but cannot access

20. District Exchange of Data- Discipline Reaction Data Elements

21. District Exchange of Data- Discipline Reaction Data Elements (cont.)

22. District Exchange of Data- Discipline Reaction File Format

23. Questions • Questions?