Home

 

Profiles attributes


Overview

Choose from among the predefined Profiles attributes to identify the job, contact, and associated information attributes that are included in the Profiles user interface. The following tables list the predefined Profiles attributes that are available in the Profiles user interface, and specify whether each attribute can be edited by users. The table also lists the Profiles database properties that correspond to each attribute, where applicable.

Keep in mind that the information that is present in the user interface originally comes from another source before being populated into the Profiles database. The mapping from the LDAP directory to the Profiles database can be customized, as can the mapping from the Profiles database to the user interface. This mapping means that, in some cases, the attributes listed below might not be present in the LDAP source, so the attributes might display as empty in the user interface.


Job information attributes

Attribute label Attribute name Can be set to be edited Profiles database property
Address 1 workLocation.address1 No Filled using the fill_workloc script.
Address 2 workLocation.address2 No Filled using the fill_workloc script.
Assistant secretaryName Yes Filled by referencing the Secretary entry in the Employee table.
Assistant e-mail secretaryEmail Yes Filled by referencing the Secretary entry in the Employee table.
Assistant number secretaryUid Yes PROF_SECRETARY_UID
City workLocation.city No Filled using the fill_workloc script.
Country countryDisplayValue No Filled similarly to the workLocation attributes, but using the fill_country script rather than fill_workloc.
Country code countryCode No PROF_ISO_COUNTRY_CODE
Department number deptNumber Yes PROF_DEPARTMENT_NUMBER
Department title departmentTitle Yes Filled similarly to the work location attributes, but using the fill_department script rather than fill_workloc. See the example below.
Employee number employeeNumber Yes PROF_EMPLOYEE_NUMBER
Employee type employeeTypeDesc No PROF_EMPLOYEE_TYPE
Is manager isManager Yes PROF_IS_MANAGER
Job title jobResp Yes PROF_JOB_RESPONSIBILITIES
Manager number managerUid Yes PROF_MANAGER_UID
Organization organizationTitle No Filled similarly to the work location attribute. See the example below.
Postal code workLocation.postalCode No Filled using the fill_workloc script.
Shift shift Yes PROF_SHIFT
State workLocation.state No Filled using the fill_workloc script.


Contact information attributes

Attribute label Attribute name Can be set to be edited Profiles database property
Alternate e-mail groupwareEmail Yes PROF_GROUPWARE_EMAIL
Alternate last name alternativeLastname Yes PROF_ALTERNATE_LAST_NAME
Building bldgId Yes PROF_BUILDING_IDENTIFIER
Calendar link calendarURL Yes PROF_CALENDAR_URL
Courtesy title courtesyTitle Yes PROF_COURTESY_TITLE
Fax number faxNumber Yes PROF_FAX_TELEPHONE_NUMBER
Floor floor Yes PROF_FLOOR
Free or busy time link freeBusyUrl Yes PROF_FREEBUSY_URL
IP telephony number ipTelephoneNumber Yes PROF_IP_TELEPHONE_NUMBER
Mobile number mobileNumber Yes PROF_MOBILE
Name displayName Yes PROF_DISPLAY_NAME
Native first name nativeFirstName Yes PROF_NATIVE_FIRST_NAME
Native last name nativeLastName Yes PROF_NATIVE_LAST_NAME
Office officeName Yes PROF_PHYSICAL_DELIVERY_OFFICE
Office e-mail email Yes PROF_MAIL
Office number telephoneNumber Yes PROF_TELEPHONE_NUMBER
Pager ID pagerId Yes PROF_PAGER_ID
Pager number pagerNumber Yes PROF_PAGER
Pager service provider pagerServiceProvider Yes PROF_PAGER_SERVICE_PROVIDER
Pager type pagerType Yes PROF_PAGER_TYPE
Preferred first name preferredFirstName Yes PROF_PREFERRED_FIRST_NAME
Preferred language preferredLanguage Yes PROF_PREFERRED_LANGUAGE
Preferred last name preferredLastName Yes PROF_PREFERRED_LAST_NAME
Time zone timezone Yes PROF_TIMEZONE


Associated information attributes

Attribute label Attribute name Can be set to be edited Profiles database property
About me description Yes PROF_DESCRIPTION
Background experience Yes PROF_EXPERIENCE
Blog link blogURL Yes PROF_BLOG_URL

 

Example

The following example shows how the work location attribute is filled from the Profiles database. The PROF_WORKLOCATION property in the employee record (table 1) points to a complete definition in the Work location table (table 2).


Employee table

PROF_UID PROF_WORKLOCATION
<name> <work_location>


Work location table

PROF_WORK_LOCATION PROF_CITY PROF_STATE
<work_location> <city> <state>

All of the user interface fields, such as, Address 1, Address 2, and so on, are included in the Work location table and are referenced using the key in the Employee table. The Work location table is populated using a CSV file using an IBM Tivoli Directory Integrator script called fill_workloc.sh. Here is an example of a line from the fill_workloc file:

If a field in the table is not supplied, then the column is blank.

 

Related tasks

Customizing the Profiles user interface
Map fields manually
Manually populating the Profiles database

+

Search Tips   |   Advanced Search