> For the complete documentation index, see [llms.txt](https://center-for-the-integration-of-id.gitbook.io/generate-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://center-for-the-integration-of-id.gitbook.io/generate-documentation/data-integration-toolkit/overview.md). # Overview CIID Data Integration Toolkit Overview ### Purpose of the CIID Toolkit The CIID Data Integration Toolkit contains action-oriented steps and corresponding resources to help State Education Agencies (SEAs) and technical assistance (TA) providers integrate their IDEA Part B data with their State Longitudinal Data Systems (SLDSs) using the Common Education Data Standards (CEDS). The Toolkit provides a road map of typical steps and tasks required for successful data integration using CEDS; it draws directly from state experiences and reflects current data management best practices. The Toolkit provides instructions for project managers and IT staff as they prepare for, complete, and sustain data integration projects. ### Who Should Use the Toolkit? Users of the Toolkit may include: * State Special Education Directors * Data Governance Coordinators * Part B Data Managers * IT Staff * EDFacts Coordinators * Data Stewards SLDS Staff It is important for members of SEA data integration teams to review the Toolkit steps and identify the\ responsible team member(s) based on the state needs and staff responsibilities.\ The roles and responsibilities for each position vary widely by state, depending on the size of the department, whether the IT department is integrated into the SEA or belongs to a separate agency, and the structure of the agency. This toolkit refers to data stewards and subject matter experts (SMEs) according to the following general definitions: * the data steward works directly with data, understands business rules, and has familiarity with data quality requirements. * the SME has a deep knowledge of the program requirements and needed business rules as well as a firm grasp of the data. * Part B data managers, EDFacts Coordinators, or other staff may serve as a data steward, the SME or both, depending on their role and the task at hand. Project teams can use the Toolkit to plan and support integration efforts in their SEAs in collaboration with CIID TA providers or on their own in collaboration with their colleagues. To access additional integration resources or receive TA from CIID, contact or visit CIIDTA.org. ### How to Use the Toolkit This toolkit outlines the major steps and supporting tasks required to complete any data integration project. Each task description details * [ ] **Step 1.** Define goals for integration * [ ] **Step 2.** Establish structured documentation and project plan for data integration work * [ ] **Step 3.** Organize data elements for integration and document it using CEDS * [ ] **Step 4.** Implement and perform extract, transform and load (ETL) procedures * [ ] **Step 5.** Review and validate sustainable data integration process The steps of this toolkit are not limited to data integration; the toolkit can also serve as a general project management tool. The artifacts produced while completing the steps support data governance structures that can be expanded beyond IDEA data and establishes strong data governance principles and sustainable practices. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://center-for-the-integration-of-id.gitbook.io/generate-documentation/data-integration-toolkit/overview.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.