80 likes | 193 Views
This document provides an overview of key data warehousing concepts, including definitions of data, information, databases, and data warehouses. It explains the purpose of a data warehouse, highlighting its role in collecting, merging, and storing data from various sources to aid decision-making. The benefits of data warehousing, such as improved consistency and quicker report generation, are discussed, alongside potential risks like data accuracy concerns and development costs. The text also outlines steps taken and proposed next actions for enhancing reporting options.
E N D
Data Warehousing - 101 January 16, 2009 Kristine Vreugdenhil, MS
Definitions • Data - A collection of facts usually collected as the result of experience, observation or experiment. Datais often viewed as a lowest level of abstraction from which information and knowledge are derived. • Information - A collection of facts or data; the meaning given to data by the way it is interpreted. • Database - A structured collection of records or data.
Definitions (continued) • Transactional Database – A database in which data is modified. Examples of Transaction Databases include BiTech, Zangle, Oasys, Edulog, etc. • Data Dictionary – A centralized repository of information about data such as meaning, relationships to other data, origin, usage and format.
Definitions (continued) Data Warehouse – A copy of transaction data specifically structured and formatted for queries and reporting. A repository of an organization’s electronic data used for reporting and analysis. A well-designed data warehouse includes a data dictionary.
Purpose of a Data Warehouse • To collect, merge, and store data, often from multiple sources or databases, for the purpose of decision-making and ongoing progress monitoring. • Pre-processing of data
Data Warehouse Benefits • Central location for most-to-all reports. • Improved consistency and accuracy. • Fewer processing delays. • Transaction data is protected in a separate database. • New Reports may be added quickly with or without technology department intervention. • Ability to track data longitudinally.
Data Warehouse Risks • Reports may not be used • Accuracy & relevancy of data • Potential for information overload • Staff education and learning curve • Development and maintenance costs • Is the value-added worth it?
Progress to Date & Next Steps • Evaluation of reporting options – Fall 2007 • District staff needs assessment – February 2008 • Proposal for District Leadership staff – final draft completed