3.3. Mapping the Data to the Default Schema
3.3.1. Viewing the Default Directory Schema
00core.ldiffile. The configuration schema used by earlier versions of the directory can be found in the
3.3.2. Matching Data to Schema Elements
- Identify the type of object the data describes.Select an object that best matches the data described in the site survey. Sometimes, a piece of data can describe multiple objects. Determine if the difference needs to be noted in the directory schema.For example, a telephone number can describe an employee's telephone number and a conference room's telephone number. Determine if these different sorts of data need to be considered different objects in the directory schema.
- Select a similar object class from the default schema.It is best to use the common object classes, such as groups, people, and organizations.
- Select a similar attribute from the matching object class.Select an attribute from within the matching object class that best matches the piece of data identified in the site survey.
- Identify the unmatched data from the site survey.If there are some pieces of data that do not match the object classes and attributes defined by the default directory schema, customize the schema. See Section 3.4, “Customizing the Schema” for more information.
Table 3.1. Data Mapped to Default Directory Schema
|Employee name||HR||person||cn (commonName)|
|Home phone number||HR||inetOrgPerson||homePhone|
|Office phone number||Facilities||person||telephoneNumber|
personobject class, which inherits from the
topobject class. This object class allows several attributes, one of which is the
commonNameattribute to describe the full name of the person. This attribute makes the best match for containing the employee name data.
personobject class, and the
userPasswordattribute is listed in the allowed attributes for the
personobject class. The home phone number describes an aspect of a person in an organization's enterprise network. This object corresponds to the
inetOrgPersonobject class in the directory schema. The
inetOrgPersonobject class inherits from the
organizationPersonobject class, which in turn inherits from the
personobject class. Among the
inetOrgPersonobject's allowed attributes is the
homePhoneattribute, which is appropriate for containing the employee's home telephone number.