Entity- An Entity is a table or view listed in the QQ_ENTITY table. The Primary Entity is identified to be used in any Profile Type, and the JOIN clause will be created from the Primary Entity to any other entities used in that Profile Type. Entities are provided to you by Default Database Update (DDU).

Attribute- In many cases, attributes are columns if the value is derived from one of the entities used in that Profile Type. However, sometimes a specific attribute value (for example, Lead Instructor Last Name) is derived by creating joins to entities. This computed attribute does not exist in the database but can be derived by joining SECTION_MASTER.LEAD_INSTRUCTOR_ID with NameMaster.ID_NUM. Another example of a computed attribute is a student's permanent address. STUDENTS_PERM_ADDRESS1 does not exist in the database but is derived by joining STUDENT_MASTER.ID_NUM with AddressMaster.ID_NUM and retrieving a specific *LHP address code. For the computed attribute to be available, the entity to which the computed attribute is linked must be included in the Profile Type. Different types of attributes (numeric, character, integer, etc.) can be used for queries, and it is not unusual to have multiple attributes (for example, for Location or Division). When an attribute uses a code table, the attribute's enumerated query is stored in the QQ_ATTRIB table.

Attributed are provided to you by Default Database Update (DDU).

Profile Type- Profile Types are used to group and list all possible entities that will be used for a specific type of query. For example, If Current Enrollment queries use tables from the Registration, Admissions, and Student Life modules, all tables from these modules will be available in the Profile Type drop-down list. However, all Current Enrollment query sets will not use all tables assigned to that Profile Type. Profile Types are stored in the QQ_PROFILE_TYPE table. If Profile Type has a Profile that is being used in J1 processes, that Profile Type must have at least one Key Attribute defined. These Key Attributes should not be modified because they are being used as the connecting blocks between the query results and the process. The Key Attributes are stored in the QQ_PROFILE_KEY_ATTRIB table.

Profile Types are provided to you by Default Database Update (DDU) and cannot be deleted. Also, you cannot create Profile Types.

Profile- A Profile is a subset of a Profile Type and is stored in the QQ_PROFILE table. Each Profile can target a smaller set of queries. For example, all Current Enrollment queries that include Admissions information can be grouped under one Profile and all Current Enrollment queries that include Student Life can grouped under another Profile. Both Profiles will "belong" to the same Current Enrollment Profile Type. When a Profile has been defined, Definitions using the Profile information can be created.

Each Profile has its own set of entities (i.e., subset of the Profile Type entities) stored in the QQ_PROFILE_ENTITY table.

Each Profile also has its own set of attributes that are linked to the profile entities.

Each Profile has its own security stored in the QQ_PROFILE_GROUP table.

Some Profiles are provided to you by Default Database Update (DDU), and these Profiles should not be modified unless the documentation for that Profile states differently.

Definition- A Definition is a subset of a Profile. You (if you have proper security) and/or your IT Administrator can create unlimited Definitions using the Entities and Attributes assigned to each Profile, customize the Attribute label, identify prompts, and assign default values.

Query- A Query is a subset of a Definition. You can save each new query results or override existing query results. For example, you may have two queries: one for Natural Science majors and one for Business majors. All selection values will be saved in the QQ_QUERY_FILTER_DETAIL table, and you can designate the query as "public" or "private". Each query can have its own results (output attributes) that are stored in the QQ_QUERY_RESULT_DETAIL table. You can customize the column label; indicate the display order; and choose, add, or remove any of the resulting attributes.

The Query security is stored in the SECURITY_OWNER table.