| Data
element |
Definition |
|
AFFILIATION_CODE
Indexed -
yes (logical PK)
Format - varchar2 (4)
May be null? yes
|
Code
used to identify an affiliation of a member of Penn Community.
Affiliations are a form of association to the university.
top
|
|
AFFILIATION_DESCRIPTION
Indexed -
no
Format - varchar2 (300)
May be null? yes
|
The full
description for the Affiliation Code.
Some sample affiliations:
Penn Student (affiliation code 'ST')
Penn Faculty (affiliation code 'FC')
Penn Full-Time Staff (affiliation code 'SF')
Clinical Practices of U of PA (affiliation code 'CPUP')
top
|
|
COLLECTS_ADDRESS_FLAG
Indexed -
no
Format - varchar2 (1)
May be null? yes
|
Whether or
not an mailing address is to be collected online for the Affiliation.
top
|
|
CREATABLE_ONLINE_FLAG
Indexed -
no
Format - varchar2 (1)
May be null? yes
|
Whether or
not a particular Affiliation can be created online (some Affiliations
must come from a batch feed, for instance: SRS for a student affiliation
('ST'), or Payroll for an employee affiliation ('TS', 'SF', 'FC',
etc).
top
|
|
DEPENDENT_FLAG
Indexed -
no
Format - varchar2 (1)
May be null? yes
|
Whether the
Affiliation is allowed to create a Dependent PennID affiliation.
Certain types of affiliations are allowed to associate another
Penn Community member - for instance, a Faculty member may have
a spouse PennID and affiliation associated. If an affiliation
that is allowed a dependent is inactivated, the Dependent Affiliation
is also inactivated.
top
|
|
LIFESPAN
Indexed -
no
Format - number (5)
May be null? yes
|
The length
of time in days for which a particular Affiliation exists before
it expires. Some affiliations will have a very short lifespan
(library patrons, conference attendees; others may have an indefinite
lifespan. If a lifespan is based upon information
coming from a batch load (UPHS, PENNPAY, SRS), this field will
be populated with '00000'.
top
|
|
PERSISTENT_FLAG
Indexed -
yes
Format - varchar2 (1)
May be null? yes
|
Whether or
not a particular affiliation is 'persistent'. A persistent
affiliation requires SSN, date of birth and name (non-persistent
affiliations don't require SSN and date of birth). Persistent
affiliations have a conflict-resolution process applied, so that
uniqueness is ensured within Penn Community.
top
|
|
UPDATES_PENNCARD_FLAG
Indexed -
no
Format - varchar2 (1)
May be null? yes
|
Whether the
Penncard person table (pcadmin.person) will hold be sent any information
for the individual associated with this particular Affiliation.
Members of Penn Community may or may not be eligible to
obtain a Penncard.
top
|
