1 / 13

MA Education Data Warehouse

MA Educational Data Warehouse Project MADOE and School District Collaboration Maureen Chew MADOE MA Digital Govt Summit 12/11/2007. Project background Data warehouse goals and objectives District participation DOE and district collaboration Collaboration techniques.

alaqua
Download Presentation

MA Education Data Warehouse

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. MA EducationalData Warehouse ProjectMADOE and School DistrictCollaborationMaureen Chew MADOEMA Digital Govt Summit 12/11/2007

  2. Project background Data warehouse goals and objectives District participation DOE and district collaboration Collaboration techniques MA Education Data Warehouse

  3. Enable the Department and public schools to make full use of the information at our disposal in order to enable all students to meet the high standards necessary for success. How? ~ Consolidate the Department’s student, assessment, educator, program, and financial data into a single system for analysis and reporting; and ~ Provide a standardized, low-cost data warehousing system to all districts in the Commonwealth to address the pervasive and increasing need for local educational data analysis. Purpose

  4. What it is • ‘Dashboard’ of reports and queries • Based on extracts from DOE and district databases • Pre-built reports to answer common questions • Flexible tools to respond to new questions What it isn’t • Not a tool to update or change data • Not a replacement for District’s local SIS

  5. Why a state-wide project? • Leverage statewide purchasing power for pricing • Invest once in the infrastructure required to support data warehousing instead of many times • Load MCAS data from the source • Make certified Student snapshots available for comparison • Load District Staff data in 2008 from statewide file

  6. Licensure Staff SIMS Curriculum Frameworks Programs Finance MCAS MEPA Locations Data Warehouse State loaded Integrated, historical information District loaded Students District and school data teams using powerful analysis and reporting tools. Schedules Attendance & Discipline Grades Local Assess- ments Courses Current Staff Future Warehouse data

  7. To rollout the data warehouse to users within the participating districts Provide state data to all districts for reporting and analysis To allow districts to upload local data to both analyze and incorporate in custom reports To train the district users in: End user proficiency Report writing Uploading and validating local data Data warehouse goals and objectives

  8. 56 districts have participated through Title IID Federal technology grants These early adapters have worked with us to provide input, feedback and requirements to the success of the project District participation

  9. Data warehouse process Extract Validation Report District Extract Staging Table Validate staged extract Upload to Drop Box ACCEPT or UPDATE REJECT Data Warehouse Validate loaded data Extract discarded District collaboration Table Validation Report

  10. Warehouse policies on state and local data Extract guide creation and updates File upload and validation procedures Requirements gathering Warehouse reports Warehouse cubes DOE and District Collaboration

  11. Project Steering Committee meetings User Group Sessions Pilot testing of new functionality Weekly Webex sessions Tips and Tricks Collaboration Techniques

  12. How does new data sets, cubes and reports get added to the warehouse? 1. User groups 2. DW Steering Committee 3. DOE Decision User groups identify analysis area, reports, etc… New data, cubes and reports may come out of those meetings. DOE will review and make a final decision. Final decisions will be put on the list for the next Development Phase. Those “new data” suggestions will go to the DW Steering Committee at intervals where they will be ranked and prioritized. 4. Warehouse Team 5. End User DOE warehouse team will schedule these in the next development phase to gather technical and functional requirements and build the requested items in the warehouse. Once in the warehouse the DW team will create documentation if necessary and send comm. To end users notifying them of the new items now available.

  13. Reach out to all MA school districts Work with Districts to create budget Training Consulting Professional Development Drive DW use down to classroom level Shoot for Statewide Implementation! Next Steps

More Related