- DATA VIEW NAME
- UGRD_PROSPECT_COMMUNICATION
- OVERVIEW
- This data view contains all of the undergraduate admissions communication records for undergraduate prospects including those who have applied for undergraduate admissions. Communication records are used to detail the admissions’s letters and materials that are sent to an individual including admissions decision letters. Though the financial aid offcie uses communication codes as well, those codes are excluded from this data view. Communication records are also used to detail recruitment activities including the attendance at recruitment events, e-mail recruitment, and phone recruitment. In addition, communication records track incoming information like an ACT test score. The Comm_Context_Descr field is the most helpful in understanding the communication code.
- LOAD FREQUENCY
- The data in this view is refreshed daily.
- DATA CUSTODIAN
- Undergraduate Admissions Office
Contact: David Leszczynski - AUTHORIZATION
- You must receive approval to access data from the data custodian. For information about how to get authorized for InfoAccess data views, connect to the InfoAccess Home Page
- SPECIAL
CONSIDERATIONS - Please note that there are a large number of communication codes to choose from and there are new codes added with some frequency. The Comm_Context_Descr field and the Comm_Method field are the most helpful in understanding the communication code.
- QUESTIONS
- Contact: Division of Information Technology Help Desk
Phone: 264-HELP (4357) - LAST UPDATED
- 04/2005 – New view created.
- DATA FORMATS
- Primary Key Columns are identified with an asterisk(*)
- Alphanumeric Data
- VARCHAR2( N) (N) = maximum length. Field contains letters and/or numbers. Trailing blanks are eliminated.
Example: VARCHAR2 (5) could contain ‘ABC12’ or ‘ABC’ or ‘A’ - Numeric Data
- NUMBER (N) (N) = length. Field contains only numbers.
NUMBER (X,Y) = format for numbers with decimal positions.
X = total number of digits
Y = the number of digits after the decimal
Examples: NUMBER (6) represents 250012 NUMBER (6,2) represents 2500.12 - Date
- DATE – Date can be in various formats. Date functions available with your query tool can be used to format the date.
Examples: DATE (YYYYMMDD), DATE (YYDDD), DATE (DD-MM-YY)
| Column Name | Format | Description | ||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| *Communication_Key | NUMBER(15) | A unique identifier that is system generated. A surrogate key. It is based on ID and Sequence_Number. | ||||||||||||||||||||||||||
| Prospect_Key | NUMBER(15) | Surrogate key of prospect table. Match this key on this table to same key on Ugrd_Prospect view. | ||||||||||||||||||||||||||
| ID | VARCHAR2(11) | ISIS personal Identifier. It will never be changed throughout the individual’s relationship with the University. This is not the same as Campus_ID. Only 10 characters are in use. | ||||||||||||||||||||||||||
| Sequence_Number | NUMBER(5,0) | The order in which the communication code was added on the record starting with 1. Some communication codes are added after the communication was completed. The result is that the sequence number is not a reliable indicator of chronological order. The Comm_Date field should be used to determine chronology. | ||||||||||||||||||||||||||
| Administrative_Function | VARCHAR2(4) | Valid values: ADMA (Admissions) ADMP (Admissions Program) EVNT (Event) GEN (General) PROP (Prospect Program) PROS (Prospect) |
||||||||||||||||||||||||||
| Comm_Category | VARCHAR2(6) | Used in the set-up of communication codes. The category is not a uniquely identifying value. | ||||||||||||||||||||||||||
| Comm_Context | VARCHAR2(6) | Used in the set-up of communication records. The context is not a uniquely identified value. | ||||||||||||||||||||||||||
| Comm_Context_Descr | VARCHAR2(30) | Long description of the communication context. | ||||||||||||||||||||||||||
| Comm_Context_Descr10 | VARCHAR2(10) | Short description of the communication context. | ||||||||||||||||||||||||||
| Comm_Method | VARCHAR2(1) | Communication method. Valid values:
|
||||||||||||||||||||||||||
| Comm_Date | DATE | Assigned date of the communication code. | ||||||||||||||||||||||||||
| Comm_System_Date | DATE | System date and time that the communication code was put on the ISIS record. | ||||||||||||||||||||||||||
| Completed_Comm_Ind | VARCHAR2(1) | Indicator specifying the communication was successful. | ||||||||||||||||||||||||||
| Completed_Date | DATE | Date communication was completed. In some instances this date will be the same as the Comm_Date, for letters it signifies when the letter printed. | ||||||||||||||||||||||||||
| Comm_Direction | VARCHAR2(4) | Valid values: IN, OUT, PERS (in person), NULL. | ||||||||||||||||||||||||||
| Unsuccessful_Ind | VARCHAR2(1) | Indicator specifying the communication was unsuccessful. | ||||||||||||||||||||||||||
| Outcome_Reason_Descr | VARCHAR2(30) | If the outcome was unsuccessful this field may detail the reason. Not all unsuccessful communications have an outcome reason. | ||||||||||||||||||||||||||
| Letter_Code | VARCHAR2(3) | Value identifying the letter code. Null is a valid value since not all communication codes are letters. | ||||||||||||||||||||||||||
| Extract Date Time | DATE | The date and time these data were extracted. Format : YYYYMMDD HH24:MI:SS |