PENNERA_SECURITY Table - Data Element Index
Select a data element to view its definition and its indexed, format, and
null values.
Data element |
Definition |
ERA_IDENTIFIER
Indexed - no
Format - varchar2 (40)
May be null? yes |
The alphanumeric code used internally by the PennERA system to uniquely identify the person in the GENIUS module of PennERA. In the PENNERA_SECURITY table, ERA_IDENTIFIER identifies the PennERA user.
In the PENNERA_SECURITY table, there are two different unique identifiers for a person: PENN_ID and ERA_IDENTIFIER. PENN_ID is the 8-digit identification number assigned to the person by the University's Penn Community system. ERA_IDENTIFIER is the identification code assigned by, and used internally by, the PennERA system. In 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_SECURITY table; ERA_IDENTIFIER is not recommended.
The substring of a person's ERA_IDENTIFIER from character 7 through 14 is often, 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.
A person may have any number of PENNERA_SECURITY records, depending on whether they are a PennERA user, how many secured access roles they have for the Proposal modules, and how many ORGANIZATION_CODEs are associated with their role(s). See also PENN_ID, ORGANIZATION_CODE, ROLE_ID, and ROLE_NAME.
Examples: 'UPENN-100397059', 'FA58BA1F91BAF0F6E033'
Values: Refer to the PENNERA_PEOPLE table for values. |
ORGANIZATION_CODE
Indexed - yes
Format - varchar2 (4)
May be null? yes |
The 4-character alphanumeric code that is the unique identifier for the organization (org.) whose records the person can access in PennERA's
Proposal modules according to the privileges associated with the role.
An org. is a subdivision of the University created for management purposes.
- If the ORGANIZATION_CODE's value consists of 4 numerals, the code refers to a "child org."--a single org. with no descendants in the org. hierarchy. In PennERA's
Proposal modules, the values stored in org.-related data elements (such as the proposal responsible org.) are child orgs.
- If the ORGANIZATION_CODE's value includes any letters, the code refers to an org. parent or rollup group, which includes one or more other orgs. The person can access the records for all of the ORGANIZATION_CODE's descendants. For example, if the ORGANIZATION_CODE is IDOM (SL-Center for Sleep Parent), the person can access records for orgs. 4638 (ID-Institute for Diabetes, Obesity and Metabolism), 4642 (ID-Translational Center of Excellence in Type 1 Diabetes), 4797 (ID-Stable Isotope TracerKinetic), and 4805 (ID-Islet Cell Biology Core).
A person may have any number of PENNERA_SECURITY records, depending on whether they are a PennERA user, how many secured access roles they have for the Proposal modules, and how many ORGANIZATION_CODEs are associated with their role(s). See also ERA_IDENTIFIER, PENN_ID, ROLE_ID, and ROLE_NAME.
Examples: '0101' (Anthropology), '40XX' (Perelman School of Medicine Parent)
Values: Refer to the ORG_CODES table for values
|
PENN_ID
Indexed - yes
Format - varchar2 (8)
May be null? yes |
The unique 8-digit identification number assigned to the person by the Penn Community system. In the PENNERA_SECURITY table, PENN_ID identifies the PennERA user.
The PENNERA_SECURITY table stores two different unique identifiers for a person: PENN_ID and ERA_IDENTIFIER (the person's unique identification code assigned by, and used internally by, the PennERA system). In 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_SECURITY table; ERA_IDENTIFIER is not recommended.
A person may have any number of PENNERA_SECURITY records, depending on whether they are a PennERA user, how many secured access roles they have for the Proposal modules, and how many ORGANIZATION_CODEs are associated with their role(s). See also ERA_IDENTIFIER, ORGANIZATION_CODE, ROLE_ID, and ROLE_NAME.
Values: Refer to the PENNERA_PEOPLE table for values. |
ROLE_ID
Indexed - no
Format - varchar2 (20)
May be null? yes |
The alphanumeric code used internally by the PennERA system to uniquely identify the role whose privileges specify what data the person can access in PennERA's
Proposal modules.
PENNERA_SECURITY stores information on secured access roles that have been assigned to specific Proposals users. It does not store information on the users’ default access privileges. (By default, if the user is the proposal’s PI, they can access all of that proposal’s data in PennERA. All Proposals users—faculty, staff, and students—have this default access.)
A person may have any number of PENNERA_SECURITY records, depending on whether they are a PennERA user, how many secured access roles they have for the Proposal modules, and how many ORGANIZATION_CODEs are associated with their role(s). See also ERA_IDENTIFIER, PENN_ID, ORGANIZATION_CODE, and ROLE_NAME.
Values:
ROLE2 Module Administrator ROLE4 Profile Administrator ROLE5 Edit PD/PT ROLE17 School/Center Approver ROLE19 University Signing/Authorizing Official ROLE24 View Only PD/PT ROLE25 Edit PD/ View PT ROLE26 Department Approver
|
ROLE_NAME
Indexed - yes
Format - varchar2 (100)
May be null? yes |
The name that the Office of Research Services has assigned to the ROLE_ID. ROLE_NAME stores the unique description of the role whose privileges specify what data the person can access in PennERA's
Proposal modules.
PENNERA_SECURITY stores information on secured access roles that have been assigned to specific Proposals users. It does not store information on the users’ default access privileges. (By default, if the user is the proposal’s PI, they can access all of that proposal’s data in PennERA. All Proposals users—faculty, staff, and students—have this default access.)
A person may have any number of PENNERA_SECURITY records, depending on whether they are a PennERA user, how many secured access roles they have for the Proposal modules, and how many ORGANIZATION_CODEs are associated with their role(s). See also ERA_IDENTIFIER, PENN_ID, ORGANIZATION_CODE, and ROLE_ID.
Values:
Department Approver ROLE26 Edit PD/ View PT ROLE25 Edit PD/PT ROLE5 Module Administrator ROLE2 Profile Administrator ROLE4 School/Center Approver ROLE17 University Signing/Authorizing Official ROLE19 View Only PD/PT ROLE24
|
.
Questions about this page? Email us at da-staff@isc.upenn.edu
|