One Purdue

Student Reporting Glossary

A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z

business concept diagram The Cognos business concept diagrams are subdivided into logical groups of ODS reporting views; groups of these are called business views. (Business views are not database objects like Oracle views.) Each business view contains ODS reporting views, one of which is the primary reporting view.
composite view Views within Banner that contain the information that will be extracted into the ODS. The extract transfer load (ETL) process pulls information from the composite views and loads it into the composite tables of the ODS. In some cases, functions are used to calculate new data that will be created from source data and loaded into the ODS.
freeze table Subsets of columns for tables that are loaded according to predefined “events” (e.g., snapshots of enrollment data at the beginning and end of terms and snapshots of admission applications received by week).
hierarchical display rule table

Display rules allow us to customize how data stored in the ODS is displayed in reporting views. For hierarchical display rules tables, display rules determine the order in which a particular type of data should be retrieved.

For example, hierarchical display rules (for applicable non-slotted views): The PERSON_ADDRESS and ADDRESS_ BY_RULE view displays one address per entity per ADDRESS_RULE to be used for mailing purposes. The mailing address displayed is based on the hierarchical display rules created to determine which address types should be retrieved for the mailing address. Several hierarchical display rules have been created based on priority for differing business processes so that if “address type 1” does not exist, insert “address type 2,” etc. To invoke the ADDRESS_BY_RULE reporting view rule, add a filter/where clause that states “where ADDRESS_RULE = LOCALADDR.” This will retrieve the first current address found in the source system for the LOCALADDR heirarchy.

Access Student Reporting Data Knowledge Base

list of values (LOV) table LOV tables enable users to create pull-down lists of values and their descriptions in their reporting applications. These values are extracted from validation tables in the source system.
positional slot table

Used to denormalize repeating concepts from multiple rows to multiple columns. Slot tables store data values for a specific code related to a base table. For example, the TEST_SCORES_SLOT table in the ODS stores all valid test score values that were loaded from the source system to the ODS. The system pulls data from the composite tables according to the defined system codes. Since the system only needs to check for specific code values as needed, using slot tables optimizes the speed of user queries.

For example, positional display rules (for slotted views): This data is stored in a vertical presentation as “one row per person, per test type, per test date.” The corresponding TEST_SLOT view provides an alternative horizontal presentation that “flattens” the data to “one row per person with the details of (up to) seven test score types.” Positional display rules are required to define which seven test scores will be included, and in what position or order they will appear within this “slotted” presentation. These display rules will be used to build the underlying MST_TEST_SLOT table. In this example, the highest test score value for a test type is presented in the TEST_SLOT table as defined by the Test Score Rule.

Access Student Reporting Data Knowledge Base

primary reporting view A primary reporting view is the view to which all other views in the business view are joined. It contains the main facts that will be in queries against the business view.
Purdue modified information Any references to composite views in the metadata that end with “_PU” indicates it is a Purdue enhancement. Names of modified reporting views will not be renamed in order to assure backward compatibility to existing queries and reports written against them prior to any enhancement. Additional fields could be added to reporting views at any time and will be announced via Cognos student user groups.
reporting view Data from each ODS composite table is presented in one or more reporting views. These are the views used to create reports within the ODS. Users will use Cognos as their report writing tool to access these views and build reports.
Social Security number Referred to as “Tax IDs” in Banner, Social Security numbers are restricted and accessible only to those with defined business needs. Purdue University identification numbers (PUIDs) should be used as unique identifiers for all individuals.

Top of page



Purdue University, West Lafayette, IN 47907 USA, (765) 494-4600
© 2008 Purdue University. An equal access/equal opportunity university.

PDF files can be viewed in Adobe Acrobat Reader.