|
Name |
|
|
Comment |
See documentation on MD_CarletonDepartment in the DimsOrganization package. |
|
Dimensional Type |
Dimension |
|
select |
|
Name |
Child Table/View |
|
ViewReference_83 |
|
|
ViewReference_103 |
|
|
ViewReference_119 |
|
|
ViewReference_144 |
|
|
ViewReference_228 |
|
|
ViewReference_240 |
|
|
ViewReference_245 |
|
Name |
Code |
Type |
Target Package |
|
View |
|||
|
View |
|||
|
View |
|
Name |
|
Grant |
User |
|
SELECT,VIEW DEFINITION |
EmployeeReader |
|
SELECT,VIEW DEFINITION |
EnergyReader |
|
SELECT,VIEW DEFINITION |
IssueTrackingReader |
|
SELECT,VIEW DEFINITION |
SpaceReader |
|
Name |
Data Type |
Comment |
Length |
|
MD_CarlDept_SurrogateKey |
numeric |
|
|
|
MD_CarlDept_Abbreviation |
char(5) |
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. |
|
|
MD_CarlDept_Name |
varchar(64) |
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). |
|
|
MD_CarlDept_College |
varchar(64) |
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. |
|
|
MD_CarlDept_CIPCode |
varchar(12) |
|
12 |
|
MD_CarlDept_Division |
varchar(64) |
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. |
|
|
MD_CarlDept_IsAcademic |
varchar(7) |
"Yes" if a department is considered academic. "No" if it is considered administrative. Otherwise, "Unknown" (should generally not occur, in practice). |
|
|
MD_CarlDept_Status |
varchar(16) |
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. |
|
|
|
|