Upload
jeffry-marvin-campbell
View
215
Download
0
Tags:
Embed Size (px)
Citation preview
MA EducationalData Warehouse ProjectMADOE and School District
Collaboration
Maureen Chew MADOE
MA Digital Govt Summit 12/11/2007
MA Education Data Warehouse
• Project background
• Data warehouse goals and objectives
• District participation
• DOE and district collaboration
• Collaboration techniques
Purpose
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.
What it isn’t• Not a tool to update or change data• Not a replacement for District’s local SIS
• ‘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 is
• 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
Why a state-wide project?
Warehouse data
Staff
SIMS
MCASMEPA
Finance
Students
Courses Staff
LocalAssess-ments
Locations
SchedulesGrades
Attendance & Discipline
Licensure
ProgramsCurriculum
Frameworks
State loaded
District loaded
Data Warehouse
Integrated, historical information
District and school data teams using powerful analysis and reporting tools.
Current
Future
Data warehouse goals and objectives
• 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
District participation
• 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
Data warehouse process
Data
Warehouse
Validate loaded
data
TableValidation
Report
District Extract
Upload to Drop Box
Staging Table
Validate staged extract
ExtractValidation
Report
Extract discarded
ACCEPT orUPDATE REJECT
District collaboration
DOE and District Collaboration
• Warehouse policies on state and local data
• Extract guide creation and updates
• File upload and validation procedures
• Requirements gathering
• Warehouse reports
• Warehouse cubes
Collaboration Techniques
• Project Steering Committee meetings
• User Group Sessions
• Pilot testing of new functionality
• Weekly Webex sessions
• Tips and Tricks
How does new data sets, cubes and reports get added to the warehouse?
1. User groups
User groups identify analysis area, reports, etc… New data, cubes and reports may come out of those meetings.
Those “new data” suggestions will go to the DW Steering Committee at intervals where they will be ranked and prioritized.
DOE will review and make a final decision. Final decisions will be put on the list for the next Development Phase.
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.
2. DW Steering Committee
3. DOE Decision
4. Warehouse Team
5. End User