Dict-Physical

Table MD_CarletonDepartment

Card of table MD_CarletonDepartment

Name	MD_CarletonDepartment
Dimensional Type	Dimension
Comment	Dimension for Carleton-internal business units (departments and offices). Includes an "Unknown" department member, which is used any time a department is either unknown or cannot be associated with an activity or person that requires a department. Note that organizational departments (i.e., what we normally think of as departments and offices) are not the same as departments in the budget sense - which are just convenient ways of bundling up financial information and transactions. An organizational department may have authority over multiple budget-wise departments. And a budget-wise department may be utilized by multiple organizational departments. This dimension is distinct from MD_CarletonOrganization, which is for things like committees, etc. This dimension is more organizational/administrative. MD_CarletonOrganization is used primarily, as of 2010, for calculating faculty non-course-related workloads. Note that there is an 'Unknown' department, which makes it possible to eliminate certain NULL foreign key values from certain fact tables.

Check constraint name of the table MD_CarletonDepartment

CKT_MD_CARLETONDEPARTMENT

List of incoming references of the table MD_CarletonDepartment

Relationship_75

MF_PerPosition

MD_CarlDept_SurrogateKey

Relationship_116

MF_IssueTrackingTicket

MD_CarlDept_SurrogateKey

Relationship_130

MF_IssueTrackingAssetValue

MD_CarlDept_SurrogateKey

Relationship_137

MF_Room

MD_CarlDept_SurrogateKey

Relationship_253

MF_KeyedComputerInUse

MD_CarlDept_SurrogateKey

Relationship_254

MF_KeyedComputerSoftwareUsage

MD_CarlDept_SurrogateKey

Relationship_263

MF_KeyedComputerEvent

MD_CarlDept_SurrogateKey

List of diagrams containing the table MD_CarletonDepartment

DimsOrganizationDiagram

List of columns of the table MD_CarletonDepartment

MD_CarlDept_SurrogateKey

<None>

numeric

MD_CarlDept_Abbreviation

All-CAP Colleague department code (most are 4-char, but a few are 5). This is the business key for the department dimension. Use this attribute if you are looking more at financial/account-based organizational units. If you're looking more at what we think of as departments, use the full department name (inconvenient as it might be on a graph label). Note that the department abbreviation or code is the primary key in Colleague, from which the data is derived.

DW_Colleague5CharCode

char(5)

MD_CarlDept_Name

Full name ('description' in Colleague) of department. Business practice at Carleton dictates that some department abbreviations or 'codes' will correspond to a single department name, as in the case of Information Technology Services - a single department name that corresponds to multiple department abbreviations or 'codes' (ACS, ACNS).

DW_Department

varchar(64)

MD_CarlDept_College

Technically, departments (in Colleague) are leaf nodes in a hierarchy whose members are: division, college, and department. The college level is not currently used at Carleton.

DW_CodeDescLong

varchar(64)

MD_CarlDept_CIPCode

<None>

varchar(12)

MD_CarlDept_Division

Technically, departments (in Colleague) are leaf nodes in a hierarchy whose members are: division, college, and department. The college level is not currently used at Carleton. Divisions only just started being maintained as of 2010.

Note that the divisions also do not necessarily correspond to AAUP or HEDS division definitions (1=Fine Arts; 2=Humanities; 3=Social Sciences; 4=Natural Science; 5=Psychology; 6=Foreign Language; 7=Engineering; 8=Business and Law; 9=Education; 10=Medical (Nursing); 99=Unknown or unreported). They are, rather, internal Carleton constructs.

DW_CodeDescLong

varchar(64)

MD_CarlDept_IsAcademic

"Yes" if a department is considered academic. "No" if it is considered administrative. Otherwise, "Unknown" (should generally not occur, in practice).

This field is based on a complex query ("virtual field") in Colleague set up by Julie Latham, and may not, in every case, give exactly the anticipated result, due to the often arbitrary and fluctuating nature of organizational units at Carleton.

It is not altogether clear how useful this field actually is, or will be - although virtually everyone at Carleton appears convinced that it needs to be here.

DW_YesNoOrUnknown

varchar(7)

MD_CarlDept_Status

Current acceptable values for this field are: Active, Inactive. The default is "Unknown" but this in practice should not occur. Active departments are ones that exist as current, functioning units. Inactive ones are historical only.

DW_CodeDescShort

varchar(16)

MD_CarlDept_AuditKey

DW_AuditKey

bigint

MD_CarlDept_Timestamp

<None>

timestamp