PENNERA_PEOPLE Table - Data Element Index
Select a data element to view its definition and its indexed, format, and
null values.
Data element |
Definition |
ADDRESS1
Indexed - no
Format - varchar2 (35)
May be null? yes |
The first line of the person’s current (or last known) mailing
address, per the person's PennERA Profile.
The value for ADDRESS1 may be stored in upper case or in mixed case.
(For example, if a University employee entered the information in the
Online Directory in mixed case, it is in mixed case in the PENNERA_PEOPLE
table.) Allow for both upper and lower case when setting record selection
conditions on ADDRESS1.
If the person has not entered another value in his or her PennERA Profile,
the first line of the address is the default value that was loaded based
on the person’s affiliation with the University. For faculty, staff,
and post-doctoral appointees who have entered Street1, City, State, and
Zip/Postal for their Work address in the Online Directory, the default
for ADDRESS1 is Street1 from the Online Directory. If their Work address
in the Online Directory is incomplete, ADDRESS1 is the building associated
with the University mail code, per the person’s employee record.
For students, the default for ADDRESS1 is the first line of the current
mailing address, per the person’s SRS record. For UPHS affiliates,
the default for ADDRESS1 is the name of the division of the University
of Pennsylvania Health System, per the person’s Penn Community
record. For research affiliates, the default for ADDRESS1 is null. (However,
if a person's only active Penn affiliation is as a member of the research
community, but the person had another affiliation with Penn in the past,
the default for ADDRESS1 is the same as its default for that past affiliation.)
Examples: ‘WALNUT WEST’; ‘Clinical Care Associates,
UPHS’, 'Penn Student Health Service'
Values:
List of values not available
PennERA Source: Login; Profile - General screen; Name and Contact Information
section; Address subsection; the first line of the Address
|
ADDRESS2
Indexed - no
Format - varchar2 (35)
May be null? yes |
The second line of the person’s current (or last known) mailing
address, per the person's PennERA Profile.
The value for ADDRESS2 may be stored in upper case or in mixed case.
(For example, if a University employee entered the information in the
Online Directory in mixed case, it is in mixed case in the PENNERA_PEOPLE
table.) Allow for both upper and lower case when setting record selection
conditions on ADDRESS2.
If the person has not entered another value in his or her PennERA Profile,
the second line of the address is the default value that was loaded based
on the person’s affiliation with the University. For faculty, staff,
and post-doctoral appointees who have entered Street1, City, State, and
Zip/Postal for their Work address in the Online Directory, the default
for ADDRESS2 is Street2 from the Online Directory. If their Work address
in the Online Directory is incomplete, the default for ADDRESS2 is the
street associated with the University mail code, per the person’s
employee record. For students, the default for ADDRESS2 is the second
line of the current mailing address, per the person’s SRS record.
For UPHS affiliates, the default for ADDRESS2 is the name of the organization
of the University of Pennsylvania Health System that is responsible for
the person’s employee record, per the person’s Penn Community
record. For research affiliates, the default for ADDRESS2 is null. (However,
if a person's only active Penn affiliation is as a member of the research
community, but the person had another affiliation with Penn in the past,
the default for ADDRESS2 is the same as its default for that past affiliation.)
Examples: ‘3401 WALNUT STREET’; 'Penncare OB/GYN & Midwifery'; ‘Penn
Tower - Lower Lobby’
Values:
List of values not available
PennERA Source: Login; Profile - General screen; Name and Contact Information
section; Address subsection; the second line of the Address
|
ADDRESS3
Indexed - no
Format - varchar2 (35)
May be null? yes |
The third line of the person’s current (or last known) mailing
address, per the person's PennERA Profile.
The value for ADDRESS3 may be stored in upper case or in mixed case.
Allow for both upper and lower case when setting record selection conditions
on ADDRESS3.
If the person has not entered another value in his or her PennERA Profile,
the third line of the address is the default value for ADDRESS3, which
is null.
Example: '34th & Civic Center Blvd.'
Values:
List of values not available
PennERA Source: Login; Profile - General screen; Name and Contact Information
section; Address subsection; the third line of the Address
|
CITY
Indexed - no
Format - varchar2 (18)
May be null? yes |
The city of the person’s current (or last known) mailing address,
per the person's PennERA Profile.
The value for CITY may be stored in upper case or in mixed case. (For
example, if a University employee entered the information in the Online
Directory in mixed case, it is in mixed case in the PENNERA_PEOPLE table.)
Allow for both upper and lower case when setting record selection conditions
on CITY.
If the person has not entered another value in his or her PennERA Profile,
the city is the default value that was loaded based on the person’s
affiliation with the University. For faculty, staff, and post-doctoral
appointees who have entered Street1, City, State, and Zip/Postal for
their Work address in the Online Directory, the default for CITY is City
from the Online Directory. If their Work address in the Online Directory
is incomplete, the default for CITY is the city associated with the University
mail code, per the person’s employee record. For students, the
default for CITY is the city of the current mailing address, per the
person’s SRS record. For UPHS and research affiliates, the default
for CITY is null. (However, if a person's only active Penn affiliation
is as a member of the research community, but the person had another
affiliation with Penn in the past, the default for CITY is the same its
default for that past affiliation.)
Example: ‘PHILADELPHIA’, 'Kennett Square'
Values:
List of values not available
PennERA Source: Login; Profile - General screen; Name and Contact Information
section; Address subsection; City
|
COMMONS_ID
Indexed - no
Format - varchar2 (40)
May be null? yes |
A character string that is the person’s unique username within
the eRA Commons. Letters in COMMONS_ID are stored in upper case. The
value is null for people that either do not have an eRA Commons username,
or have not entered it in their PennERA profiles.
Examples: ‘DAVINCI’, ‘JACKSONL1’
Note: COMMONS_ID stores the Commons ID per the person’s PennERA
profile. Investigators are instructed to enter their eRA Commons username
in the Commons ID field on PennERA’s Profile / General screen.
- An eRA Commons username may be from 6 to 20 characters long, and
may contain only letters and numerals, but the Commons ID on PennERA’s
Profile / General screen stores up to 40 characters, and the characters
are not limited to letters and numerals.
- If the person made an error when entering the Commons ID on PennERA’s
Profile / General screen, COMMONS_ID stores the erroneous value that
was entered.
- The eRA Commons username is not case sensitive. People may use
upper case and/or lower case letters when entering their Commons
IDs on PennERA’s Profile / General screen. To make record selection
and sorting easier for those generating reports, all letters in COMMONS_ID
are stored in upper case.
- If the person has an eRA Commons username, but has not entered
it in the Commons ID field on PennERA’s Profile / General screen,
COMMONS_ID is null.
Grants.gov provides the ability to submit applications electronically
to federal sponsors. The eRA Commons allows the National Institutes
of Health (NIH) to receive applications electronically from Grants.gov
and validate them against agency-specific business rules. It also provides
a way for NIH and individuals with an eRA Commons user name (Commons
ID) to communicate electronically after submission. Assignment, review
outcome, and summary statement information is available through the
eRA Commons. A person must have a Commons ID before he or she can use
PennERA to submit a grant application electronically to federal agencies
that use the eRA Commons to retrieve electronic proposals from Grants.gov
(such as NIH, AHRQ, and CDC). Proposals submitted electronically through
Grants.gov to other federal agencies (such as NSF) do not require a
Commons ID.
Values:
List of values not available
PennERA Source: Login; Profile - General screen; Name and Contact
Information section; Commons ID
|
COUNTRY
Indexed - no
Format - varchar2 (3)
May be null? yes |
The 3-character code identifying the country of the person’s
current (or last known) mailing address, per the person's PennERA Profile.
If the person has not entered another value in his or her PennERA
Profile, the country is the default value that was loaded based on
the person’s affiliation with the University. For faculty, staff,
and post-doctoral appointees, the default for COUNTRY is ' USA'. For
students, the default for COUNTRY is the code for the country of the
current mailing address, per the person’s SRS record. For UPHS
and research affiliates, the default for COUNTRY is null. (However,
if a person's only active Penn affiliation is as a member of the research
community, but the person had another affiliation with Penn in the
past, the default for COUNTRY is the same as its default for that past
affiliation.)
Values:
List of values not available
PennERA Source: Login; Profile - General screen; Name and Contact
Information section; Address subsection; Country
|
DATE_CREATED
Indexed - no
Format - date
May be null? no |
The date the person’s record was created in the GENIUS module
of PennERA.
Example: 09/15/2003
Values:
List of values not available
PennERA Source: GENIUS (the Global Expertise Network for Industry,
Universities, and Scholars)
|
EMAIL
Indexed - no
Format - varchar2 (80)
May be null? yes |
The person’s current (or last known) E-mail address, per the person's
PennERA Profile.
If the person has not entered another value in his or her PennERA
Profile, the E-mail address is the default value that was loaded based
on the person’s affiliation with the University. For faculty,
staff, and post-doctoral appointees, the default for EMAIL is the E-mail
address per the person’s employee record. For students, the default
for EMAIL is the E-mail address, per the person’s SRS record.
For UPHS affiliates, the default for EMAIL is null. For other affiliates,
the default for EMAIL is the E-mail address per the person’s
Penn Community record.
Examples: ‘DOE@ISC.UPENN.EDU’; ‘doe@sas.upenn.edu’
Values:
List of values not available
PennERA Source: Login; Profile - General screen; Name and Contact
Information section; Email
|
ERA_IDENTIFIER
Indexed - yes
Format - varchar2 (40)
May be null? yes |
The 15-character code used internally by the PennERA system to uniquely
identify the person in the GENIUS module of PennERA.
In the PENNERA_PEOPLE table, there are two different unique identifiers
for an investigator: PENN_ID and ERA_IDENTIFIER. PENN_ID is the identification
number assigned by the University. ERA_IDENTIFIER is the identification
code assigned by, and used internally by, the PennERA system. For a given
record, PENN_ID will not have the same value as ERA_IDENTIFIER. PENN_ID
is the person identifier that is recommended for use by those querying
the PENNERA_PEOPLE table; ERA_IDENTIFIER is not recommended.
The substring of a person's ERA_IDENTIFIER from character 7 through
14 is usually, but not always, the same as the person's PENN_ID. The
numeric portion of a person's ERA_IDENTIFIER is never the person's Social
Security Number.
There is one PENNERA_PEOPLE record per person (PENN_ID or ERA_IDENTIFIER).
Example: UPENN-100397059
Values:
List of values not available
PennERA Source: GENIUS (the Global Expertise Network for Industry, Universities,
and Scholars)
|
ERA_PRIMARY_ORG
Indexed - yes
Format - char (4)
May be null? yes |
The 4-character code for the current (or last known) ERA primary organization
(‘org.’) for the person, per the GENIUS module of PennERA.
The ERA primary org. is the org. flagged as the primary department in the
person’s PennERA Profile.
The ERA primary org. is used only for security purposes. Some
of those who query the PennERA data in the Data Warehouse have
org.-based authorization, rather than University-wide authorization.
For example, when Jane Doe is named in a proposal as the Principal
Investigator, Dr. Doe’s ERA primary org. is one of the orgs.
that is checked by the system to determine whether someone querying
the PennERA Proposals data with org.-based authorization is allowed
to see the secured data elements for that proposal. If Dr. Smith
is not (or was not) on the University payroll, she has no home
org. and no (job) appointment orgs.—so it is her ERA primary
org. alone that determines whether someone with org.-based authorization
is allowed to see the secured data elements for the proposal. Although
it is used to secure certain data elements in the Data Warehouse,
the ERA primary org. is not used by the University’s business
processes.
For Penn staff, the ERA primary org. is the primary (job) appointment
org. For Penn faculty, it is the primary academic (job) appointment
org., which will not be the same as primary appointment org. for
those faculty holding administrative positions. For Penn employees
whose job appointments are all on the executive payroll, ERA primary
org. is ‘8000’ ('General University Special '). For
Penn students, the ERA primary org. is the organizational equivalent
of their home Division (for example, ‘0200’, School
of Arts and Sciences.) For investigators from the University of
Pennsylvania Health System (UPHS), the ERA primary org. is ‘2100’ ('Health
System '). For members of the research community who are otherwise
not affiliated with Penn, the ERA primary org. is ‘8760'
('Research Services').
To facilitate Organization-based security in other tables, ERA_PRIMARY_ORG
is set to '.' if it would otherwise be null.
Example: 4261 (DM-Rheumatology)
Values:
Refer to the ORG_CODES table for values.
PennERA Source: Login; Profile - General screen; Name and Contact Information
section; Department subsection; the org. code for the Department flagged
as Primary |
ERA_PRIMARY_ORG_SCH_CTR
Indexed - yes
Format - char (2)
May be null? yes |
The 2-character code for the school or center for the ERA_PRIMARY_ORG.
That identifies the current (or last known) ERA primary organization
(‘org.’) for the person. The ERA primary org. is the org.
flagged as the primary department in the person’s PennERA Profile.
Although it is used to secure certain data elements in the Data Warehouse,
the ERA primary org. is not used by the University’s business processes.
If the ERA_PRIMARY_ORG is '.', the ERA_PRIMARY_ORG_SCH_CTR is also
'.'.
Example: 40 (School of Medicine)
Values:
Refer to the CNAC_CODES Table for values. The code
for a school or center is the same as the first 2
characters of the CNAC.
|
FIRST_NAME
Indexed - no
Format - varchar2 (25)
May be null? yes |
The person’s current (or last known) first name, per his or
her profile in PennERA, stored in upper case. For the person's first
name as it is stored in PennERA (where the value might be in mixed case),
see FNAME_AS_IS.
If the person has not entered another value in his or her PennERA
Profile, FIRST_NAME reflects the person’s current (or last known)
first name, per his or her Penn Community record.
See also M_INITIAL, LAST_NAME, NAME, NAME_FLIPPED, SALUTATION, and
SUFFIX.
Examples: 'LEONARDO', 'LA TOYA'
Values:
List of values not available
PennERA Source: Login; Profile - General screen; Name and Contact
Information section; Name subsection; First
|
FNAME_AS_IS
Indexed - no
Format - varchar2 (25)
May be null? yes |
The person’s current (or last known) first name, per his or
her profile in PennERA, as it is stored in PennERA (where the value might
be in mixed case). For the person's first name stored in upper case,
see FIRST_NAME.
If the person has not entered another value in his or her PennERA
Profile, FIRST_NAME_AS_IS is the person’s current (or last known)
first name, per his or her Penn Community record.
Note: If records are sorted by FNAME_AS_IS, values that include lower
case letters do not appear in the order expected. For example, 'JUDITH'
would appear before 'Jane'. Use FIRST_NAME if you wish to sort records
by the person's first name.
See also M_INITIAL_AS_IS, LNAME_AS_IS, NAME_AS_IS, NAME_FLIPPED_AS_IS,
SALUTATION_AS_IS, and SUFFIX_AS_IS.
Examples: 'Leonardo', 'La Toya'
Values:
List of values not available
PennERA Source: Login; Profile - General screen; Name and Contact
Information section; Name subsection; First
|
HOME_ORG
Indexed - yes
Format - char (4)
May be null? yes |
The 4-character code for the current (or last known) home organization
(‘org.’) for the person. The home org. is the org. that owns
the person's employee record and is responsible for its maintenance. HOME_ORG
is set to '.' if there is no employee record for the person. (Because the
HOME_ORG is one of the data elements used to secure the data in other tables,
it is set to '.' if it would otherwise be null.)
Example: 4261 (DM-Rheumatology)
Values:
Refer to the ORG_CODES table for values.
Source: EMPLOYEE_GENERAL.HOME_DEPT_ORG where PENNERA_PEOPLE. PENN_ID =
EMPLOYEE_GENERAL.PENN_ID
|
HOME_SCH_CTR
Indexed - yes
Format - char (2)
May be null? yes |
The 2-character code for the school or center for the HOME_ORG. That
is the current (or last known) home organization (‘org.’) for
the person. The home org. is the org. that owns the person's employee record
and is responsible for its maintenance. HOME_SCH_CTR is set to '.' if there
is no employee record for the person.
Example: 40 (School of Medicine)
Values:
Refer to the CNAC_CODES Table for values. The code
for a school or center is the same as the first 2
characters of the CNAC.
Source: EMPLOYEE_GENERAL.HOME_SCHOOL_CTR where PENNERA_PEOPLE. PENN_ID
= EMPLOYEE_GENERAL.PENN_ID
|
LAST_NAME
Indexed - no
Format - varchar2 (25)
May be null? yes |
The person’s current (or last known) last name, per his or her
profile in PennERA, stored in upper case. For the person's last name
as it is stored in PennERA (where the value might be in mixed case),
see LNAME_AS_IS.
If the person has not entered another value in his or her PennERA
Profile, LAST_NAME reflects the person’s current (or last known)
last name, per his or her Penn Community record.
See also FIRST_NAME, M_INITIAL, NAME, NAME_FLIPPED, SALUTATION, and
SUFFIX.
Examples: 'DA VINCI', 'JACKSON'
Values:
List of values not available
PennERA Source: Login; Profile - General screen; Name and Contact
Information section; Name subsection; Last
|
LAST_UPDATED
Indexed - no
Format - date
May be null? yes |
The date the person’s record was last updated in the GENIUS module
of PennERA.
Example: 10/28/2003
Values:
List of values not available.
PennERA Source: GENIUS (the Global Expertise Network for Industry, Universities,
and Scholars)
|
LNAME_AS_IS
Indexed - no
Format - varchar2 (25)
May be null? yes |
The person’s current (or last known) last name, per his or her
profile in PennERA, as it is stored in PennERA (where the value might
be in mixed case). For the person's last name stored in upper case, see
LAST_NAME.
If the person has not entered another value in his or her PennERA
Profile, LNAME_AS_IS is the person’s current (or last known)
last name, per his or her Penn Community record.
Note: If records are sorted by LNAME_AS_IS, values that include lower
case letters do not appear in the order expected. For example, 'SUTTON'
would appear before 'Sanchez'. Use LAST_NAME if you wish to sort records
by the person's last name.
See also FNAME_AS_IS, M_INITIAL_AS_IS, NAME_AS_IS, NAME_FLIPPED_AS_IS,
SALUTATION_AS_IS, and SUFFIX_AS_IS.
Examples: 'da Vinci', 'Jackson'
Values:
List of values not available
PennERA Source: Login; Profile - General screen; Name and Contact
Information section; Name subsection; Last
|
M_INITIAL
Indexed - no
Format - char (1)
May be null? yes |
The middle initial of the person’s current (or last known) name,
per his or her profile in PennERA, stored in upper case. For the person's
middle initial as it is stored in PennERA (where the value might be in
mixed case), see M_INITIAL_AS_IS.
If the person has not entered another value in his or her PennERA
Profile, M_INITIAL reflects the person’s current (or last known)
middle initial, per his or her Penn Community record.
See also FIRST_NAME, LAST_NAME, NAME, NAME_FLIPPED, SALUTATION, and
SUFFIX.
Example: Y
Values:
List of values not available
PennERA Source: Login; Profile - General screen; Name and Contact
Information section; Name subsection; Middle
|
M_INITIAL_AS_IS
Indexed - no
Format - char (1)
May be null? yes |
The middle initial of the person’s current (or last known) name,
per his or her profile in PennERA, as it is stored in PennERA. The value
is not guaranteed to be in upper case. For the person's middle initial
stored in upper case, see M_INITIAL.
If the person has not entered another value in his or her PennERA
Profile, M_INITIAL_AS_IS is the person’s current (or last known)
middle initial, per his or her Penn Community record.
Note: If records are sorted by M_INITIAL_AS_IS, values are lower case
letters do not appear in the order expected. For example, 'U' would
appear before 'a'. Use M_INITIAL if you wish to sort records by the
person's last name.
See also FNAME_AS_IS, LNAME_AS_IS, NAME_AS_IS, NAME_FLIPPED_AS_IS,
SALUTATION_AS_IS, and SUFFIX_AS_IS.
Example: Y
Values:
List of values not available
PennERA Source: Login; Profile - General screen; Name and Contact
Information section; Name subsection; Middle
|
MAILSTOP
Indexed - no
Format - varchar2 (10)
May be null? yes |
The person’s current (or last known) University intramural mail
code, per the person's PennERA Profile.
If the person has not entered another value in his or her PennERA
Profile, the MAILSTOP is the default value that was loaded based on
the person’s affiliation with the University. For faculty, staff,
and post-doctoral appointees, the default for MAILSTOP is the University
mail code per the person’s employee record. For all other affiliates,
the default for MAILSTOP is null.
Example: 6228
Values:
List of values not available
PennERA Source: Login; Profile - General screen; Name and Contact
Information section; Address subsection; Mail Stop Code
|
NAME
Indexed - yes
Format - varchar2 (52)
May be null? yes |
The person’s current (or last known) name, per his or her profile
in PennERA, stored in upper case. The name may be up to 52 characters
long, and is stored in the format ‘LASTNAME,FIRSTNAME I’ (with
no spaces around the comma, and no period after the middle initial).
NAME is useful when sorting information by the person’s name.
If the person has not entered another value in his or her PennERA
Profile, NAME reflects the person’s current (or last known) name,
per his or her Penn Community record.
For the person's name as it is stored in PennERA (where the value
might be in mixed case), in the format ‘LASTNAME,FIRSTNAME I’,
see NAME_AS_IS.
See also FIRST_NAME, M_INITIAL, LAST_NAME, NAME_FLIPPED, SALUTATION,
and SUFFIX.
Examples: ‘DA VINCI,LEONARDO’, 'JACKSON,LA TOYA Y'
Values:
Refer to the PENNERA_PEOPLE Table for values.
PennERA Source: Login; Profile - General screen; Name and Contact
Information section; Name subsection; Last, First, and Middle
|
NAME_AS_IS
Indexed - no
Format - varchar2 (52)
May be null? yes |
The person’s current (or last known) name, per his or her profile
in PennERA, as it is stored in PennERA (where the value might be in mixed
case). The name may be up to 52 characters long, and is stored in the
format ‘LASTNAME,FIRSTNAME I’ (with no spaces around the
comma, and no period after the middle initial).
If the person has not entered another value in his or her PennERA
Profile, NAME_AS_IS reflects the person’s current (or last known)
name, per his or her Penn Community record.
For the person's name stored in upper case, in the format ‘LASTNAME,FIRSTNAME
I’, see NAME.
Note: If records are sorted by NAME_AS_IS, values that include lower
case letters do not appear in the order expected. For example, 'SUTTON,JUDITH
U' would appear before 'Sanchez,Jane C'. Use NAME if you wish to sort
records by the person's name.
See also FNAME_AS_IS, M_INITIAL_AS_IS, LNAME_AS_IS, NAME_FLIPPED_AS_IS,
SALUTATION_AS_IS, and SUFFIX_AS_IS.
Examples: ‘da Vinci,Leonardo', 'Jackson,La Toya Y’
Values:
Refer to the PENNERA_PEOPLE Table for values.
PennERA Source: Login; Profile - General screen; Name and Contact
Information section; Name subsection; Last, First, and Middle
|
NAME_FLIPPED
Indexed - no
Format - varchar2 (52)
May be null? yes |
The person’s current (or last known) name, per his or her profile
in PennERA, stored in upper case. The name may be up to 52 characters
long, and is stored in the format ‘FIRSTNAME I LASTNAME’.
(Note that there is no period after the middle initial; if there is no
middle initial, there is only one space between FIRSTNAME and LASTNAME).
If the person has not entered another value in his or her PennERA
Profile, NAME_FLIPPED reflects the person’s current (or last
known) name, per his or her Penn Community record.
For the person's name as it is stored in PennERA (where the value
might be in mixed case), in the format ‘FIRSTNAME I LASTNAME’,
see NAME_FLIPPED_AS_IS.
See also FIRST_NAME, M_INITIAL, LAST_NAME, NAME, SALUTATION, and SUFFIX.
Examples: ‘LEONARDO DA VINCI’, 'LA TOYA Y JACKSON'
Values:
Refer to the PENNERA_PEOPLE Table for values.
PennERA Source: Login; Profile - General screen; Name and Contact
Information section; Name subsection; First, Middle, and Last
|
NAME_FLIPPED_AS_IS
Indexed - no
Format - varchar2 (52)
May be null? yes |
The person’s current (or last known) name, per his or her profile
in PennERA, as it is stored in PennERA (where the value might be in mixed
case). The name may be up to 52 characters long, and is stored in the
format ‘FIRSTNAME I LASTNAME’. (Note that there is no period
after the middle initial; if there is no middle initial, there is only
one space between FIRSTNAME and LASTNAME).
If the person has not entered another value in his or her PennERA
Profile, NAME_FLIPPED_AS_IS reflects the person’s current (or
last known) name, per his or her Penn Community record.
For the person's name stored in upper case, in the format ‘FIRSTNAME
I LASTNAME’, see NAME_FLIPPED.
See also FNAME_AS_IS, M_INITIAL_AS_IS, LNAME_AS_IS, NAME_AS_IS, SALUTATION_AS_IS,
and SUFFIX_AS_IS.
Examples: ‘Leonardo da Vinci', 'La Toya Y Jackson'’
Values:
Refer to the PENNERA_PEOPLE Table for values.
PennERA Source: Login; Profile - General screen; Name and Contact
Information section; Name subsection; First, Middle, and Last
|
PENN_ID
Indexed - yes
Format - char (8)
May be null? no |
The 8-digit identification number assigned to a person by the Penn Community
system. No two persons have the same PennID. However, a person may have
more than one PennID. For example, say Dr. John Doe had a sponsored project
in 1990, but his Social Security number was not recorded in the Research
Services System (RSS, the system then used to track proposals and awards).
Dr. Doe left the University after project ended. When the RSS data was
converted to PennERA, there was no record in Penn Community for Dr. Doe.
Because his Social Security number was not available, a PennERA-specific
PennID (beginning with a ‘P’) was created for him. In 2003,
Dr. Doe returned to the University, and was assigned a numeric PennID (for
example, 10039706). Dr. Doe would then have two PennIDs, but one could
not tell from looking at the data that both PennIDs identify the same person.
In the PENNERA_PEOPLE table, there are two different unique identifiers
for an investigator: PENN_ID and ERA_IDENTIFIER. PENN_ID is the
identification number assigned by the University. ERA_IDENTIFIER
is the identification number used internally by the PennERA system.
For a given record, PENN_ID will not have the same value as ERA_IDENTIFIER.
PENN_ID is the person identifier that is recommended for use by
those querying the PENNERA_PEOPLE table; ERA_IDENTIFIER is not
recommended.
There is one PENNERA_PEOPLE record per person (PENN_ID or ERA_IDENTIFIER).
Examples: ‘P1000194’ (Lisa Jay); ‘10006336’ (Herman
Gluck)
Values:
Refer to the PENNERA_PEOPLE Table for values.
PennERA Source: Login; Profile - General screen; Name and Contact
Information section; Employee ID
|
PHONE
Indexed - no
Format - char (18)
May be null? yes |
The person’s current (or last known) telephone number, per the
person's PennERA Profile.
If the person has not entered another value in his or her PennERA
Profile, the telephone number is the default value that was loaded
based on the person’s affiliation with the University. For faculty,
staff, and post-doctoral appointees, the default for PHONE is the first
work phone number, per the person’s employee record. For students,
the default for PHONE is the current telephone number, per the person’s
SRS record. For other affiliates, the default for PHONE is null.
Example: 2158987200
Values:
List of values not available
PennERA Source: Login; Profile - General screen; Name and Contact
Information section; Phone
|
PRI_ACAD_ORG
Indexed - yes
Format - char (4)
May be null? yes |
The 4-character code for the organization (‘org.’) of the
person’s current (or last known) primary academic job appointment.
PRI_ACAD_ORG is set to '.' if the person's employee record includes no
academic job appointments, or if there is no employee record for the person.
(Because the PRI_ACAD_ORG is one of the data elements used to secure the
data in other tables, it is set to '.' if it would otherwise be null.)
If the person has more than one academic job appointment, the
primary academic appointment is the one with the most important
faculty class. For further information on how the primary academic
appointment is determined, see the explanation in the Cautions
section of the documentation for the EMPLOYEE_GENERAL table.
Example: 4261 (DM-Rheumatology)
Values:
Refer to the ORG_CODES table for values.
Source: EMPLOYEE_GENERAL.PRI_ACAD_DEPT_ORG where PENNERA_PEOPLE.
PENN_ID = EMPLOYEE_GENERAL.PENN_ID
|
PRI_ACAD_SCH_CTR
Indexed - yes
Format - char (2)
May be null? yes |
The 2-character code for the school or center for the PRI_ACAD_ORG. That
is the organization (‘org.’) of the person’s current
(or last known) primary academic job appointment. PRI_ACAD_SCH_CTR is set
to '.' if the person's employee record includes no academic job appointments,
or if there is no employee record for the person.
If the person has more than one academic job appointment, the
primary academic appointment is the one with the most important
faculty class. For further information on how the primary academic
appointment is determined, see the explanation in the Cautions
section of the documentation for the EMPLOYEE_GENERAL table.
Example: 40 (School of Medicine)
Values:
Refer to the CNAC_CODES Table for values. The code
for a school or center is the same as the first 2
characters of the CNAC.
Source: ORG_CODES.CENTER_CODE where ORG_CODES. ORGANIZATION_CODE
= PENNERA_PEOPLE. PRI_ACAD_ORG
|
PRI_APPT_ORG
Indexed - yes
Format - char (4)
May be null? yes |
The 4-character code for the organization (‘org.’) of the
person’s current (or last known) primary job appointment. PRI_APPT_ORG
is set to '.' if there is no employee record for the person. (Because the
PRI_APPT_ORG is one of the data elements used to secure the data in other
tables, it is set to '.' if it would otherwise be null.)
The primary appointment org. is the org. where the person has
his or her primary job appointment, per the University’s
employee census logic. For information on how the primary appointment
is determined, see the explanation in the Cautions section of the
documentation for the EMPLOYEE_GENERAL table.
Example: 4261 (DM-Rheumatology)
Values:
Refer to the ORG_CODES table for values.
Source: EMPLOYEE_GENERAL.PRIMARY_DEPT_ORG where PENNERA_PEOPLE.
PENN_ID = EMPLOYEE_GENERAL.PENN_ID
|
PRI_APPT_SCH_CTR
Indexed - yes
Format - char (2)
May be null? yes |
The 2-character code for the school or center for the PRI_APPT_ORG. That
is the organization (‘org.’) of the current (or last known)
primary job appointment for the person. PRI_APPT_SCH_CTR is set to '.'
if there is no employee record for the person.
The primary appointment org. is the org. where the person has
his or her primary job appointment, per the University’s
employee census logic. For information on how the primary appointment
is determined, see the explanation in the Cautions section of the
documentation for the EMPLOYEE_GENERAL table.
Example: 40 (School of Medicine)
Values:
Refer to the CNAC_CODES Table for values. The code
for a school or center is the same as the first 2
characters of the CNAC.
Source: ORG_CODES.CENTER_CODE where ORG_CODES. ORGANIZATION_CODE
= PENNERA_PEOPLE.PRI_APPT_ORG
|
SALUTATION
Indexed - no
Format - varchar2 (5)
May be null? yes |
The optional title currently used (or last known to be used) before
the person's name, per his or her profile in PennERA. The value (if it
is not null) is stored in upper case, and might or might not end with
a period. For the person's salutation as it is stored in PennERA (where
the value might be in mixed case), see SALUTATION_AS_IS.
If the person has not entered another value in his or her PennERA
Profile, SALUTATION reflects the person’s current (or last known)
salutation, per his or her Penn Community record.
See also FIRST_NAME, M_INITIAL, LAST_NAME, NAME, NAME_FLIPPED, and
SUFFIX.
Examples: DR, DR., MS, MS.
Values:
List of values not available
PennERA Source: Login; Profile - General screen; Name and Contact
Information section; Name subsection; Salutation
|
SALUTATION_AS_IS
Indexed - no
Format - varchar2 (5)
May be null? yes |
The optional title currently used (or last known to be used) before
the person's name, per his or her profile in PennERA. The value (if it
is not null) is stored as it is in PennERA (where the value might be
in mixed case), and might or might not end with a period. For the person's
salutation stored in upper case, see SALUTATION.
If the person has not entered another value in his or her PennERA
Profile, SALUTATION_AS_IS is the person’s current (or last known)
salutation, per his or her Penn Community record.
See also FNAME_AS_IS, M_INITIAL_AS_IS, LNAME_AS_IS, NAME_AS_IS, NAME_FLIPPED_AS_IS,
and SUFFIX_AS_IS.
Examples: DR, Dr., MS, Ms.
Values:
List of values not available
PennERA Source: Login; Profile - General screen; Name and Contact
Information section; Name subsection; Salutation
|
STATE
Indexed - no
Format - varchar2 (3)
May be null? yes |
The code for the state portion of the person’s current (or last
known) mailing address, per the person's PennERA Profile. For U.S. addresses,
STATE ought to be the 2-character U.S. Postal Service code for the state.
If the person has not entered another value in his or her PennERA
Profile, STATE is the default value that was loaded based on the person’s
affiliation with the University. For faculty, staff, and post-doctoral
appointees who have entered Street1, City, State, and Zip/Postal for
their Work address in the Online Directory, the default for STATE is
State from the Online Directory. If their Work address in the Online
Directory is incomplete, the default for STATE is the state associated
with the University mail code, per the person’s employee record.
For students, the default for STATE is the state of the current mailing
address, per the person’s SRS record. For UPHS and research affiliates,
the default for STATE is null. (However, if a person's only active
Penn affiliation is as a member of UPHS or the research community,
but the person had a University employee or student affiliation with
Penn in the past, the default for STATE is the same as it was for that
past affiliation.)
Example: PA (Pennsylvania)
Values:
List of values not available
PennERA Source: Login; Profile - General screen; Name and Contact
Information section; Address subsection; Country
|
STATUS
Indexed - no
Format - varchar2 (3)
May be null? yes |
The code that indicates whether or not the person is actively affiliated
with the University, per the Penn Community system.
Values:
A the person is an active member of the
Penn Community
I the person is an inactive member of the
Penn Community
PennERA Source: GENIUS (the Global Expertise Network for Industry, Universities,
and Scholars)
|
SUFFIX
Indexed - no
Format - varchar2 (5)
May be null? yes |
The current (or last known) modifier (if any) at the end of the person's
name, per his or her profile in PennERA. The value (if it is not null)
is stored in upper case, and might or might include periods. For the
person's suffix as it is stored in PennERA (where the value might be
in mixed case), see SUFFIX_AS_IS.
If the person has not entered another value in his or her PennERA
Profile, SUFFIX reflects the person’s current (or last known)
suffix, per his or her Penn Community record.
See also FIRST_NAME, M_INITIAL, LAST_NAME, NAME, NAME_FLIPPED, and
SALUTATION.
Examples: JR, JR., III, PHD, M.D.
Values:
List of values not available
PennERA Source: Login; Profile - General screen; Name and Contact
Information section; Name subsection; Suffix
|
SUFFIX_AS_IS
Indexed - no
Format - varchar2 (5)
May be null? yes |
The current (or last known) modifier (if any) at the end of the person's
name, per his or her profile in PennERA. The value (if it is not null)
is stored as it is in PennERA (where the value might be in mixed case),
and might or might include periods. For the person's suffix stored in
upper case, see SUFFIX.
If the person has not entered another value in his or her PennERA
Profile, SUFFIX_AS_IS is the person’s current (or last known)
suffix, per his or her Penn Community record.
See also FNAME_AS_IS, M_INITIAL_AS_IS, LNAME_AS_IS, NAME_AS_IS, NAME_FLIPPED_AS_IS,
and SALUTATION_AS_IS.
Examples: JR, Jr., III, PhD, M.D.
Values:
List of values not available
PennERA Source: Login; Profile - General screen; Name and Contact
Information section; Name subsection; Suffix
|
ZIP
Indexed - yes
Format - char (10)
May be null? yes |
The zip code of the person’s current (or last known) address, per
the person's PennERA Profile. The value may be up to 10 characters long.
If the person has not entered another value in his or her PennERA
Profile, the zip code is the default value that was loaded based on
the person’s affiliation with the University. For faculty, staff,
and post-doctoral appointees who have entered Street1, City, State,
and Zip/Postal for their Work address in the Online Directory, the
default for ZIP is Zip/Postal code from the Online Directory. If their
Work address in the Online Directory is incomplete, the default for
ZIP is the zip code associated with the University mail code, per the
person’s employee record. For students, the default for ZIP is
the zip code of the current mailing address, per the person’s
SRS record. For UPHS and research affiliates, the default for ZIP is
null. (However, if a person's only active Penn affiliation is as a
member of UPHS or the research community, but the person had a University
employee or student affiliation with Penn in the past, the default
for ZIP is the same as it was for that past affiliation.)
Example: 19103
Values:
List of values not available
PennERA Source: Login; Profile - General screen; Name and Contact
Information section; Address subsection; Zip
|
Questions about this page? Email us at da-staff@isc.upenn.edu
|