Community

Product DocsMenu

Creating an OpenText Content Server Connector Mapping File

The Coveo connector for OpenText Content Server (OTCS) has no mapping file by default. When the name of metadata found on OTCS documents matches the name of CES system or custom fields, the metadata are automatically mapped.

When you need to more accurately control where and how metadata is mapped on your items, you must create and use a mapping file that respects the schema of the standard mapping file (see Standard Mapping File Schema).

Examples: You need a mapping when you want to: 

  • Customize the HTML body for items of a specific type.

  • Concatenate two or more OTCS metadata in a CES field.

  • Map an OTCS metadata value to a CES field for which names do not match.

To create and use an OTCS connector mapping file

  1. Using an administrator account, connect to the Coveo Master server.

  2. Using a text editor:

    1. Create the mapping file.

      You can start with the following commented sample mapping file. 

      <?xml version="1.0" encoding="utf-8" ?>
<Mappings><!-- Review the ValidationSchemaVersion1.xsd to view the available fields and attributes -->
    <Version>1</Version><!-- Mandatory node to identify the mapping file version. Do not modify. -->
    <CommonMapping><!-- Optional. Any Mapping defined within this section will be applied to all documents. -->
        <Title>%[title]</Title>
    </CommonMapping>
    <Mapping type="Document"><!-- Optional. This is a specific mapping. The fields and elements described will only be applied to items of type "Document".
                                  Values for OpenText Content Server are the type of nodes. -->
        <Body>This is a body</Body>
        <PrintableUri>http://www.coveo.com</PrintableUri>
        <Fields>
            <Field name="field1">%[metadata1]</Field>
        </Fields>
    </Mapping>
    <DefaultMapping> <!-- Optional. This is the default mapping. It will be applied to any item that was not mapped to a specified mapping -->
        <ClickableUri>www.clickableuri.com</ClickableUri>
    </DefaultMapping>
</Mappings>

    2. Respecting the mapping file format, customize the file using the following tips:

      • Use OTCS node types to create specific <Mapping type="..."> tags in the mapping file.

        You can easily find the values to enter in this tag from the Type of items in OpenText Content Server.

        Example: When you want to manage OTCS Discussion fields, in the OTCS Workspace, simply hover a discussion item. The tooltip indicates the value to enter in the Mapping type tag.

        In the mapping file, you would create the <Mapping type="Discussion"> node.

      • The connector populates the special OTCSFileType metadata with the type of OTCS documents. This metadata is useful to create a facet based on the types of items found in OTCS.

    3. Save the file using a name of your choice in the [Index_Path]\Config\ folder.

    4. Save your changes.

What's Next?

Assign your customized mapping file in your OpenText Content Server source (see Configuring and Indexing an OpenText Content Server Source).

People who viewed this topic also viewed