View VMD_Application

Card of view VMD_Application

Name

VMD_Application

Comment

See MD_Application in the StarsProspect package.

Dimensional Type

Dimension


SQL query of the view VMD_Application

select
MD_App_SurrogateKey,
MD_App_AppRPlusPKID,
MD_App_StudentRPlusPKID,
MD_App_StatusCategory,
MD_App_Status,
MD_App_RequirementRule,
MD_App_EntryTerm,
MD_App_EntryTermYear,
MD_App_AdmitCondition,
MD_App_IsPrimaryApp
from
MD_APPLICATION


List of incoming view references of the view VMD_Application

Name

Child Table/View

ViewReference_101

VMF_Yield


List of referenced objects of the view VMD_Application

Name

MD_Application


List of diagrams containing the view VMD_Application

Name

ViewsProspectDiagram


List of permissions of the view VMD_Application

Grant

User

SELECT,VIEW DEFINITION

FinancialAidReader

SELECT,VIEW DEFINITION

ProspectViewReader


List of view columns of the view VMD_Application

Name

Data Type

Comment

Length

MD_App_SurrogateKey

numeric

 

 

MD_App_AppRPlusPKID

int

Unique identifier for application (different from that of student).

 

MD_App_StudentRPlusPKID

int

Unique identifier for student (different from that of the application).

Note that this attribute is not a business key for MD_Application, and it should not be used for joins, since an application might be submitted then later reassigned to (or deleted and recreated for) a new student with a different ID, e.g., as a result of a merge/de-duplication. Such operations can leave "orphaned" student identifiers as well as orphaned applications (which no longer exist in the system of record).

We do not delete orphaned applications from this attribute's dimension table, because orphaned applications will automatically be ignored when used in conjunction with any fact table, because nothing in the fact table will join to the orphaned application.

 

MD_App_StatusCategory

varchar(32)

Generalized/broader version of applicationt status. Coalesces detailed application states into broader categories. E.g., applications that are complete, or that have triggered a waitlist response, etc. are all listed as 'applied.'

 

MD_App_Status

varchar(64)

Detailed application status. Cf. MD_App_StatusCategory (which is more general, and typically more useful).

 

MD_App_RequirementRule

varchar(32)

Specifies what set of requirements are applied to the application. Example values: Regular Decision, Transfer, Winter Early Decision.

 

MD_App_EntryTerm

char(7)

Projected term for which a student is applying for entrance (typically, but not always a fall term), in a given application.

 

MD_App_EntryTermYear

int

Projected year for which a student is applying for entrance, in a given application. Students may, naturally, end up submitting multiple apps (e.g., one for regular admission as a freshman, then another for admission as a transfer student a year or two later).

 

MD_App_AdmitCondition

varchar(32)

This field is used, at Carleton (as of 2011) to tell us how an application came into the system. Typical values are either "RW-Carleton App Web" or "CM-Common App Mail."

 

MD_App_IsPrimaryApp

char(3)

If a student submits multiple applications for the same entry term (often this happens by accident), we designate one or another as the primary.