Penn Computing

University of Pennsylvania
Penn Computing << go backback
CM_PROPOSAL_HISTORY_KEY data element index . Curriculum Management Tables and Data Elements . Data Warehouse Home

CM_PROPOSAL_HISTORY_KEY Table

dwcat_cm.cm_proposal_history_key

Explanation

Contains file keys and temporary identifiers for joining the collection's data back to the source database, and path components for finding the a record in the online Courseleaf application.

Common Uses

  • Join from CM_PROPOSAL to the related history tables. Note: this join is already part of the Curriculum Management universe.
  • (For developers only: create a link to the staging tables refreshed nightly from tcfdb.)
Primary Key Indexed Data Elements Related Tables
PROPOSAL_ID PROPOSAL_ID CM_PROPOSAL
CM_PROPOSAL_HISTORY
 
 

Cautions

  • Contains multiple rows per proposal. When TCTYPE = 'tca' that is used to populate the row in CM_PROPOSAL_HISTORY with a 'Y' in the MOST_RECENTLY_APPROVED_YN column. This is the main purpose and function of this table. People who are writing queries generally do not need this table; they can use the MOST_RECENTLY_APPROVED_YN columns in the history tables.
  • Developers: tckeys are dynamic in the source; do not save the "LATEST_TCKEY" in a downstream system and expect it to continue to work indefinitely.


Questions about this page? Email us at da-staff@isc.upenn.edu

Information Systems and Computing
University of Pennsylvania
Information Systems and Computing, University of Pennsylvania