What Happens in the Automated Rostering (formerly District Data Exchange-DDE) Set-Up Process?
Automated Rostering keeps student, class, and teacher information up to date in CLI Engage. CLI Engage uses files from the district to add or update roster information. This article explains the main steps in the setup process.
Automated Rostering is a shared process between the district and CLI. It helps make sure students are assigned to the correct teacher and class in CLI Engage.
During setup, the CLI Help Center and Functional Teams will send feedback to the district’s technical contact through the Jira help ticket. The technical contact is the person who works with the district’s computer systems and student information system.
Step | Your District’s Step is | Purpose | Time to Complete | Responsible Party |
|---|---|---|---|---|
Request Automated Rostering Information | Review the information from CLI. | CLI sends the district the requirements for automated rostering. The district’s technical contact reviews the requirements and decides if the district can create the required files. | 1 hour | Automated response |
District Confirms It Can Create the Required Files | Confirm whether the district can create the required files. | The district’s technical contact reviews the requirements. They confirm whether the district can create the required files for automated rostering. | Varies by district | District technical contact |
Create the CLI Common Folder | Watch for the email that gives you access to the CLI Common folder. | While the district’s technical contact creates the files, CLI creates a CLI Common folder. This folder lets the district share student data safely with CLI. You will receive an email when you are added to the folder. For more information, review these resources: | 20 business hours | CLI Help Center |
Initial File Review | Review feedback from CLI. If changes are needed, update the files and send them back to CLI. | CLI reviews the district’s files to make sure all required files are included and appear complete.
| 20 business hours per review If the files need changes, the 20 business hours start again when CLI receives the updated files. | District technical contact and CLI Help Center |
Quality Review | Review feedback from CLI. If changes are needed, update the files and send them back to CLI. | CLI’s functional team reviews the district’s files to make sure all required information is accurate and in the correct format for automated rostering.
| 5 business days per review If the files need changes, the 5 business days start again when CLI receives the updated files. | District technical contact and CLI Functional Team |
File Preparation and Student ID Number Update | No action is needed during this step. | CLI’s database team prepares the files for upload into CLI Engage. The team tests the files to make sure they update correctly. After the files are prepared and tested, CLI updates existing student records with the ID numbers provided by the district’s technical contact. This helps reduce duplicate or missing students, teachers, and classes. After the Student IDs are updated, CLI moves the files to Production. | 5 business days | CLI Database Team |
Files in Production | No action is needed during this step. | CLI moves the final files into production. Rosters are updated over two days:
| 2 business days | CLI Functional Team |
If you need more help, please submit a help ticket.
Comments
@Brian Herod @Helene.Dendor @Obinna.Agbara
2 comments - For me it is not clear that “Automated Rostering Process” equates to DDE. I would include DDE in the title. Also, somewhere in the beginning of the article, spell out DDE.
After meeting with Miguel and Thao, we’ve updated the name and spelled out DDE.
@Thao.Yoder @Miguel Gallegos