Institutional Research at the University of Indianapolis features a networked approach where functional experts are located in key areas for data gathering, analysis, and to support data informed decision-making. A linked system of reporting and communication ensures that diverse needs of the campus community are met.
The Office of Institutional Research (IR) compiles data to address operational needs, satisfy compliance, and to inform strategic planning. From our website you can travel to the “Data Dictionary” to review definitions or request new definitions be completed, you can review data in “Data Sets” that is drawn from various sources, and custom data requests can be made by following the “Data Request” link. Although decentralized in its approach, the Office of Institutional Research is part of the Provost’s support structure.
Developing an Institutional Data Dictionary and Identification of Reporting Needs
As part of a larger process to improve institutional research and access to data for decision-making across the institution, the University adopted Data Cookbook to house our data dictionary. The University received feedback through participation in its Strategy Forum (2017), its Comprehensive Quality Report (2016), and its Systems Appraisal (2014) where the need for progress was noted with respect to collecting data, analyzing and putting information to good use. Past changes in the University’s organization of institutional research going from a centralized model with one office to a decentralized model with data stewards across campus have prompted HLC reviewers from the same timeframe to request clarification of the system for institutional research. The development of a data dictionary was one of three projects planned to lead to the improvement of data usage and data knowledge for purposes of decision-making and reporting. Because anyone may submit definitions for review with any level of completeness, the tool allows both self-service learning and the ability for users to communicate gaps in documentation.
Key functional areas with data managers include, but are not limited to,
Heath Mock, email@example.com
Jeremiah Rang, firstname.lastname@example.org
James Wilson, email@example.com
Greg Smith, firstname.lastname@example.org
Eric Patberg, email@example.com
Andrea Stranak, firstname.lastname@example.org
Jennifer Outlaw, email@example.com
Abigail Hale, firstname.lastname@example.org
Enid Herrera, email@example.com