Supplemental user data for Profiles

Mapping user data

You can map additional user data to supplemental tables within the Profiles database and then display that data in a user's profile.

When the LDAP directory provides a code or abbreviation for a particular setting, the supplemental table can provide extra data. For example, an employeeType of P in the LDAP directory might correspond to Permanent. If the employee-type table is populated with data such as p;permanent, this extra data can be displayed in the profile.

The profiles_tdi.properties file stores the settings that determine how the files are formatted.

This step is mandatory if one or more entities have been selected as the Group By filter in Metrics. Otherwise, when you categorize the Metrics report by this entity, the report will show an unknown value, not the descriptive name of the entity in the chart. Metrics have three default Group By attributes: country, organization and title. The country and organization attributes are in the supported list.

The mapping task for Profiles maps your user data to the following entities:

Fill countries

Add country data to each profile. Use Country code script ./fill_country.sh or fill_country.bat to populate the Country table.

Fill departments

Add department data to each profile. Use Department code script ./fill_department.sh or fill_department.bat.

Fill organization

Add organization data to each profile. Use Organization code script ./fill_organization.sh or fill_organization.bat.

Fill employee types

Add employee-type data to each profile. Use Employee type code script ./fill_emp_type.sh or fill_emp_type.bat

Fill work locations

Add location data to each profile. Use Work location code script ./fill_workloc.sh or fill_workloc.bat.

CSV files

A CSV (comma separated value) file is required as input for each of these tasks.

country_table_csv_separator=;
country_table_csv_file=isocc.csv

department_table_csv_separator=;
department_table_csv_file=deptinfo.csv

emp_type_table_csv_separator=;
emp_type_table_csv_file=emptype.csv

organization_table_csv_separator=;
organization_table_csv_file=orginfo.csv

workloc_table_csv_separator=;
workloc_table_csv_file=workloc.csv

The separator character separates the different tokens in each line. The second property is the name of the file, relative to the solution directory.

The first token is the code. The next attributes are read in order for each additional field. No other fields are required.

The data that can be populated in these tables is usually provided as two values per line: code;description.

Fields that you do not require in your mapping can be omitted from the file; this example uses only one addr field.