Mapping content server properties to collection fields

Mapping content server properties to collection fields enables you to make the content server properties searchable on the Search pane. It also enables you to make the information in the properties visible on the Search Results pane.

About this task

Important: Your ability to perform tasks depends on the roles that were assigned to you. Only icons and menu options for tasks that are associated with your roles are visible to you. Be aware that this topic might include information that is not relevant to your roles.

To map content server properties to collection fields:

Procedure

  1. On the Collections pane of the Administration page, click the Search Mapping tab of the collection for which you want to map content server properties to collection fields.
  2. Click the Add a new field to this collection icon.
  3. Select a content server property or attribute, and select its data type.
  4. Enter a name for the collection field that maps to the content server property or attribute. This name will be displayed on the Search pane.
  5. Enter the appropriate full-text search information.

    Specifying a value in the Text Index column enables eDiscovery Manager to perform a case-insensitive search when a user searches the associated content server property. Not specifying a value in the Text Index column means that eDiscovery Manager performs a case-sensitive search when a user searches the associated content server property.

    Specify $FULL_TEXT$ for the following kinds of content:
    • Content in custom collections
    • Content that is indexed by the default index setup (using Net Search Extender)
    Important: eDiscovery Manager requires a full-text index on email content before it can search that content.
    • Enter the Verity zone to search for this field. The zone must match the name that is specified in the Verity file, style.xml.
    • Enter the name of the field in the index model. The field name must match the XML element that is defined in the IBM® Content Collector model file, afu_mail_entire_cmp.xml (for the compound data model).
    • Enter the name of the field in the index model. The field name must match the XML element that is defined in the IBM Content Collector model file, afu_mail_entire.xml (for the bundled data model).
    • Enter the name of the field in the index model. The field name must match the XML element that is defined in the IBM CommonStore model file, cs_mail_entire.xml.
  6. Save the mapping information by clicking Save.
    Important: When mapping content server properties to collection fields, do not map the same property to two different collection fields with different Text Index values. For example, if you map the content server property ICCTo to a collection field called TO with a Text Index value of 'to' and you also map the content server property ICCTo to a collection field called RECIPIENTS with a Text Index value of 'recipients', a search on the TO collection field might use a Text Index value of 'to' or 'recipients'. Similarly, a search on the RECIPIENTS collection field might use a Text Index value of 'recipients or 'to'.

Results

Your changes are immediately visible to you. Your changes will take effect for all new eDiscovery Manager web client sessions and for all new tasks. Existing eDiscovery Manager sessions and currently running tasks will continue to operate under the configuration settings that were in place when the users of those sessions logged into the eDiscovery Manager web client.