Categories
Purpose:
Categories have long been a confusing part of the Shuksan system. They are
provided via the whatami tool and other tools to many different applications
but have had very little documentation provided with them. This document will
attempt to give a better understanding of what categories are and how they
should be used.
Background:
The primary role categories is to define Uniform Access (UA) service sets for
UW NetIDs. Categories also define a UW NetID's affiliations as well as
defining a UW NetID's type. These three roles have caused a large increase
in the number of categories and have created confusion and complexity in
Shuksan. Over the past couple of years the
number of categories has expanded from 8 to roughly 40. There are many
categories that only exist to define different affiliations and have the
exact same UA service sets. There categories that were created to distinguish
the UW NetID type. There are also categories that only define a
service set and do not define an affiliation, which makes it confusing to
when attempting to look at affilations.
The person registry team is in the process of providing a better way to
show affilations and will most likely provide something that
defines UW NetID type.
At the point that this is developed there should no longer be a dependance
upon categories to show affiliations and it will not only greatly decrease
the complexity of categories but it will also limit the applications
interested in categories to only ones who are tied to UA services.
Categories can be associated with a source record as a primary source
category or a as an extended source category. They can also be associated
with the UW NetID record as a sourceless extended category.
Scope:
This document focuses on the types and affiliations of category. It does not
specify the service set each category has.
Source Codes:
Below is a list of the data sources in the shuksan table. For more information
on source codes visit the whatami v1 support pages.
| Code | Source | Short Description |
| 1 | Faculty/Staff | UW Employee Database (HEPPS) |
| 2 | Student | UW Student Database (SDB) |
| 3 | Clinician | Clinician feed from MCIS |
| 4 | AVF | Auxiliary Validation File - Maintained by C&C accouting office |
| 7 | Advance | Feed from database used by the Office of Developement and the Alumni Association |
UW NetID Types:
There are four different types of UW NetIDs. With a few exceptions, the
UW NetID Type can be determined by looking at the category and source.
| Code | Name | Short Description |
| P | Personal | A UW NetID that belongs to a single person for life. |
| S | Shared | A group UW NetID. |
| R | Reserved | A system account that should not generally be used to authenticate. |
| T | Temporary | An account that is used by a single person but only temporarily. |
Categories:
| Category | eduPerson Affiliation | Name | UW NetID Type | Source(s) |
| 1 | Source 2: student, member Source 4: affiliate | Undergraduate Student | P | 2,4 |
| 2 | Source 2: student, member Source 4: affiliate | Graduate Student | P | 2,4 |
| 3 | | External | S | 4 |
| 4 | Source 1: employee, staff, member Source 4: affiliate | UW staff | P | 1,4 |
| 5 | Source 1: employee, faculty, member Source 4: affiliate | Faculty | P | 1,4 |
| 6 | | System overhead | R | 4 |
| 7 | | Other (retired) | | |
| 8 | | Billed accounts (research) | S | 4 |
| 10 | | Mail List | R | 4 |
| 11 | | Departmental Accounts | S | 4 |
| 12 | | Course Accounts | S | 4 |
| 13 | affiliate | Clinician | P | 3,4 |
| 14 | employee, staff, member | Student Employee | P | 1 |
| 15 | affiliate | Affiliate Employee | P | 1 |
| 16 | alum | Alumni | P | 7 |
| 17 | affiliate | Clinician (NetId only) | P | 3 |
| 18 | student, member | EO Techfee Student | P | 2 |
| 19 | student, member | Non-Techfee Student | P | 2 |
| 20 | affiliate | Applicant | P | 2 |
| 21 | | SAO Account | S | 4 |
| 22 | | Clinical Supplemental | S | 4 |
| 23 | | Clinical Supplemental (no svc) | S | 4 |
| 24 | | Supplemental Account (no svc) | S | 4 |
| 25 | affiliate | Person (no svc) | P | 4 |
| 26 | affiliate | Patient | P | 3 |
| 27 | | C&C System Administration | S | 4 |
| 28 | affiliate | Development Affiliate | P | 7 |
| 29 | affiliate | MyUW.net Paid | | |
| 30 | | Caccluster (retired) | | |
| 31 | | Grandfathered 2MB Student | | |
| 32 | | MGH staff | | |
| 33 | | Temporary Patron | T | 4 |
| 34 | member | Retired Staff | P | 4 |
| 35 | member | Retired Faculty | P | 4 |
| 36 | | Red User | | |
| 37 | | Shiva User | | |
| 38 | | Green/Bank User | | |
| 39 | affiliate | DLC Student | P | 4 |
| 40 | affiliate | DLC Educator | P | 4 |
| 101 | | Temporary #1 | R | |
| 102 | | Temporary #2 | R | |
Detailed descriptions:
Undergraduate Student (1):
- SDB Source - If you want to completely understand when a person will
receive an undergraduate category 1 or any other
category from the student database you will need to read the
derivation of SDB category document, however
basically this category represents an undergraduate student from the SDB Source.
In order to be in this category the individual must have a
sdb_class
code of greater than 0 and less than 7 and have one of the following
sdb_status codes:
sdb_status: Description:
A Admitted for a future quarter and has confirmed intent
to enroll by paying the Enrollment Confirmation Deposit.
E Actively enrolled for the current quarter. This is higher
than the official 10th day count because that count
excludes extension students and others not taking any
state-funded classes.
P Not enrolled for the current quarter, but have registered
for a future quarter.
X Former Student
- AVF Source - Several different individuals end up in the AVF with a primary category of 4.
- Student not Currently Eligible - Undergraduate students that are
temporarily not eligible for computing services through the SDB but have
been deemed eligible for service.
- Snapshot Accounts - When a snapshot is created of an individual's
account for a Supoena, PRO office request, AG request then if the account is
owned by a UW Student the account is assigned category 4.
Graduate Student (2):
- SDB Source - To get a more complete understanding of who will be assigned
this category read the derivation of SDB category
document. The category represents graduate students including graduate
students on leave. Any individual in the SDB with a sdb_class code of greater than 6 and one of the following status codes is assigned a a category 2.
sdb_status: Description:
A Admitted for a future quarter and has confirmed intent
to enroll by paying the Enrollment Confirmation Deposit.
E Actively enrolled for the current quarter. This is higher
than the official 10th day count because that count
excludes extension students and others not taking any
state-funded classes.
L Graduate students not enrolled now, but on an approved
leave of absence.
P Not enrolled for the current quarter, but have registered
for a future quarter.
X Former Student
- AVF Source - Student not Currently Eligible - Graduate students that are temporarily not eligible for computing services through the SDB but have been deemed eligible for service.
External (3):
- AVF Source - There are a small number of groups outside the UW who have
been grandfathered UW group accounts. These are pay through with an external
budget number. We do not create new accounts but this category is here to
honor existing acounts.
UW staff (4):
Faculty (5):
System overhead (6):
- AVF Source - System accounts and listproc lists.
Other (retired) (7):
This category used to identify all shared accounts. The need to specify
different UA service sets for shared resources made this category obsolete.
It is no longer used.
Billed accounts (research) (8):
- AVF Source - Billed group accounts for faculty or staff at the UW who
want to use UW computing recources for projects not affiliated with the
University.
Mail List (10):
- AVF Source - Entries are made for mailman lists in order to reserve UW NetID
name space for @u.washington.edu forwarding.
Departmental Accounts (11):
- AVF Source - Departmental accounts support the electronic
presence of a UW department or unit, or support business of the unit
requiring multiple people to have access to a single account.
Course Accounts (12):
- AVF Source - Course accounts support the activities of a single
UW course or course section.
Clinician (13):
- Clinician Source -
- AVF Source - Snapshot Accounts - When a snapshot is created of an
individual's account for a Supoena, PRO office request, AG request then if it
is a Clinician the account is assigned category 13.
Student Employee (14):
Affiliate Employee (15):
- HEPPS Source -This is derived directly from the Employee Type field in the UW HR database. The following Employee Type is
given a category 15.
Employee Type: Name:
V Affiliate
The only type V affiliates that are currently imported into the Person Registry
are the Howard Hughes Affiliates (job class 0998).
There are plans to import the rest of the affiliates into personreg.
An affiliate is a person who works on campus at least 3 days a week with a
minimum appointment of 1 year who is not an employee. Some examples of
affiliates that are in HEPPS are, State Auditors, Halibut Commission
employees, Assistant Attorney Generals, and Henry Art Gallery Employees. There are currently 4 job classes with a type V employee type:
Job Class Service Set / Description
0996 not in use
0997 Affiliates w/ Campus directory information
0998 Howard Hughes Affiliates
0999 Affiliates w/ Campus directory and Husky card.
Alumni (16):
Clinician (NetId only) (17):
EO Techfee Student (18):
Non-Techfee Student (19):
Applicant (20):
SAO Account (21):
Clinical Supplemental (22):
- AVF Source - Specialized UW Medicine departmental accounts that may be used to communicate patient-identifiable health information (PHI).
Clinical Supplemental (no svc) (23):
- AVF Source - Specialized UW Medicine departmental accounts that may be used to communicate patient-identifiable health information (PHI) but are only assigned a password and forwarding (no other services).
Supplemental Account (no svc) (24):
- AVF Source - There are several different types of cat 24 accounts:
- Vendor Accounts - accounts for for venders to test authentication with UW NetIDs.
- Group Accounts w/ no services - group accounts that only need @u
forwarding and the ability to authenticate.
Person (no svc) (25):
- AVF Source - Minimum service sponsored inviduals - Individuals who only get @u email forwarding and a password.
Patient (26):
- Clinician Source - Patients entered by UW Medicine ITS on a very small
scale for several trials.
C&C System Administration (27):
This is an extended category to give permission for special UA service sets to a
UW NetID.
Development Affiliate (28):
MyUW.net Paid (29):
This category is a sourceless extended category used to provide MyUW.net
services to MyUW.net customers.
Caccluster (retired) (30):
This category was originally used to identify individuals with a NDC account
(Red, Shiva, Bank, or Green). It is no longer used.
Grandfathered 2MB Student (31):
This is a category to permit a specific set of former students for access to
a 2 MB email INBOX on the UW mailer cluster.
MGH staff (32):
This is a category to give special permission to Computing & Communications
Client Services and Learning Technologies consultants for specific UA services.
Temporary Patron (33):
- AVF Source - Temporary reusable UW NetIDs that are currently used on a small
scale by several different groups.
Retired Staff (34):
- AVF Source - Used to continue UA services of retired staff. This is not
a good category to use to determine if someone is retired.
Retired Faculty (35):
- AVF Source - Used to continue UA services of retired faculty. This is not
a good category to use to determine if someone is retired.
Red User (36):
This extended category identifies that someone has a red account and is
therefor eligible for special UA computing services.
Shiva User: (37)
This extended category identifies that someone has a shiva account and is therefor eligible for special UA computing services.
Green/Bank User (38):
This extended category identifies that someone has a bank or green account and is therefor eligible for special UA computing services.
DLC Student (39):
DLC Educator (40):
Temporary #1 (101)::
For internal testing only.
Temporary #2 (102):
For internal testing only.