Penn Computing

University of Pennsylvania
Penn Computing << go backback
ST_ACADEMIC_EVENT column definitions . Pennant Student Records Home . Data Warehouse Home

STUDENT ACADEMIC_EVENT table

(dwngss_ps.st_academic_event)

Explanation

The Student Academic Event table contains awards, honors, graduate milestones and other non-course events that need to be recorded on the student's official record. Academic events are associated with the student's level. Some academic events appear on the student's transcript. Some academic events are also non-course requirements. See notes below.

Source

The warehouse ST_ACADEMIC_EVENT table is refreshed in batch mode from the Operational Data Store (ODS), which gets its data from the Banner database. The ODS source tables are UPENN_ODS.SATURN_SHREVNT. In the online Pennant system, the data about students' activities can be viewed on the SHADEGR form.

Common Uses

  • Identify students who have received a specified honor or award.

 

Primary Key Indexed Data Elements Related Tables
ST_ACADEMIC_EVENT_PK
 

ST_DEGREE_PURSUAL

Cautions and notes

  • ST_ACADEMIC_EVENT can have multiple records for the same event code at the same level for the student. The warehouse table's primary key is based on multiple columns (PIDM, EVENT_CODE, ORIG_CODE, STUDENT_LEVEL, STATUS_OR_CRSE, EVENT_TERM, EFFECTIVE_DATE, ACTIVITY_DATE). For this reason, it is extremely difficult to get back just one row per student from this table; joins to this table will almost always return more than one row.
  • Academic events are often also events tracked in the Non-Course Requirements; the same event code will appear in both tables. This is especially true for events that are graduate benchmarks, such as the passing of a dissertation or thesis preliminary exam, which is both a non-course requirement and an academic event.
  • For graduate teaching requirements, the event code in the ST_ACADEMIC_EVENT table and in the ST_NONCOURSE_REQ table is 'TRQ.' Graduate students are usually required to complete multiple teaching requirements, all of which will have the event code 'TRQ.' The associated course used to fulfill the requirement appears in the 'Status_or_Crse' column in the ST_ACADEMIC_EVENT table. For events that are not 'TRQ' the 'Status_or_Crse' column will have the event status, e.g. "Satisfied" or "Waived", etc. The term in which a graduate student fulfilled the specific teaching requirement appears in the 'Event_Term' column in the ST_ACADEMIC_EVENT, and this will correspond to the 'Status_Term' column in the ST_NONCOURSE_REQ table. When joining these two tables for the purpose of looking at teaching requirements (event code 'TRQ'), use the student's ID, level, event code and term:
    where st_noncourse_req.penn_id = st_academic_event.penn_id
           and st_noncourse_req.student_level = st_academic_event.student_level
           and st_noncourse_req.status_term = st_academic_event.event_term
           and st_noncourse_req.noncourse_type = st_academic_event.event_code
           and st_academic_event.event_code = 'TRQ'
ST_ACADEMIC_EVENT column definitions . Pennant Student Records Home . Data Warehouse Home

 



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