1 / 8

Incorporating Texas Higher Education Coordinating Board Data in an Institutional Data Warehouse

Incorporating Texas Higher Education Coordinating Board Data in an Institutional Data Warehouse. Dr. David Wierschem Jeremy McMillen Dr. Randy McBroom. Drivers for Building a Coordinating Board Data Warehouse. Outcomes Assessment Climate Accountability from Legislators

quamar-riley
Download Presentation

Incorporating Texas Higher Education Coordinating Board Data in an Institutional 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. Incorporating Texas Higher Education Coordinating Board Data in an Institutional Data Warehouse Dr. David Wierschem Jeremy McMillen Dr. Randy McBroom

  2. Drivers for Building a Coordinating Board Data Warehouse • Outcomes Assessment Climate • Accountability from Legislators • THECB Data is used for funding purposes • Could use for strategic management

  3. What is a Data Warehouse? • A data warehouse is a subject oriented, integrated, non-volatile, and time variant collection of data in support of management decisions (Inmon, 1996). • Takes a ‘snapshot’ in time to provide for a consistent data source, which is often difficult to accomplish off of an operational system. • THECB Data establishes a historical source of data that has already gone through data cleansing.

  4. What Information is in THECB Data? • Student Information (001 – Fall, Spring & Summer) • TASP Data (002 – Fall, Spring, Sum I & Sum II) • Course Information (004 – Fall, Spring & Summer) • University Room Use (005 – Fall) • End of Semester Report (006 – Fall, Spring & Summer) • Faculty Data (008 – Fall & Spring) • Graduating Student Report (009 -- Fall) • Admissions Information (00B, Fall)

  5. Why a Data Warehouse? • Allow easy access to data from a variety of sources and platforms with relatively easy integration • Control for the discrepancies in data by migrating the management information system (or data warehouse) from a dynamic data store (operational/ transactional) to a static data store • Being able to conduct extensive data mining. • Allows for integration with other data sources for more complex analysis.

  6. Integration • Iterative issues of submissions/ resubmissions could be reduced; thereby improving the quality and timeliness of data submissions. • Strategic utilization of THECB data could be enhanced if the timeline were reduced. • Building relational databases to allow for expansion of knowledge about reported data.

  7. Develop ment Analysis Maintenance Initial Organization Testing Design Implementation Data Warehouse Development Methodology – System Development Life Cycle

  8. Contacts • David Wierschem, Assistant Professor of Management Information Systems david_wierschem@tamu-commerce.edu (903)886-5923 • Jeremy McMillen, Director of Institutional Research jeremy_mcmillen@tamu-commerce.edu (903)886-5509 • Randy McBroom, Assistant to the President for Planning and Institutional Effectiveness randy_mcbroom@tamu-commerce.edu (903)886-5926 Texas A&M University-Commerce P.O. Box 3011 Commerce, TX 75429-3011

More Related