Ambiguous and Vague Column Names

• Ambiguous and vague column names should contain a prefix for clarity, or in some situations, the source table name.
• Examples: CS_LEVL_CODE, STDN_LEVL_CODE (differentiates between course-section and student level codes) or SPRIDEN_ID (ID only would be too vague.  Could also use USFID).

Back to Top

Code Value Column Names

• Column groupings should start with a common prefix.
• Examples: LEVL_CODE, DEPT_CODE 

Back to Top

 Description Column Names

• Description column names should end in DESC.
• Examples: COLL_DESC, FUND_DESC

Back to Top

Flag Column Names

• Flag columns contain only one of two values which is often a one character value (e.g. Y/N).  These column names should end with FLG, except when the source column name ends in IND (indicator), in which case, it's okay to use IND, instead of FLG.
• Examples: REG_FLG (values: 1/-1) VET_FLG (values: Y/N), UGDC_ADMIT_FLG (values: 1/0)

Back to Top

Count and Summation Column Names

• Count and summation column names should end with CNT or TOTAL.
• Examples: WEB_TRANS_CNT, CREDIT_HRS_TOTAL

Back to Top

Column Groupings

• Column groupings should start with a common prefix.
• Examples: ML_STREET_LINE1, ML_STREET_LINE2, ML_CITY, ML_STATE, ML_ZIP

Back to Top

Data

Types and Lengths

• Data types and lengths should be the same as the source column, unless data conversion is incorporated into the process.
• PIDM  NUMBER(8), BIRTH_DATE  DATE

Back to Top

State and Operational Reporting, SVC4010, AISteam@usf.edu