Indexing Pipeline Customization Tools Overview

This article provides an overview of the Coveo Cloud tools and features that you can use to customize how each candidate item is processed through the Coveo Cloud V2 Indexing Pipeline. You can sometimes choose between a few tools to achieve the same indexing customization goal, but some of them may impact performance, or may only be available for certain connectors.

As a developer, your first choice might be to use indexing pipeline extensions (IPEs) because they are scripts and offer great flexibility. However, IPEs can also decrease indexing performance, and there is often another tool or feature that can achieve the same goal with less overhead.

The article lists customization tools starting with the ones that are the most appropriate to use either because of their effectiveness, ease of use, or performance optimization.

URL Filters

Indexing Goal

Control the indexing scope, choosing which repository pages or sections to include in your source.

How to Use

Advantages

  • Efficiently processed by the Crawling stage.

  • Wildcard or regex flexibility.

  • For Web sources, easy configuration from the administration console (see Add or Edit a Web Source).

Disadvantages

  • Only applicable to URL based source types (e.g., Web and Sitemap).

  • For Sitemap sources, configuration from the source JSON can be challenging.

Mappings

Indexing Goal

  • Extract original document metadata values to populate specific Coveo index fields.

  • Customize or create an index item body for object-based source types, such as Salesforce or a database.

How to Use

Advantages

  • Efficiently processed by Mapping stage.

  • Conditional mappings based on item type.

  • Can concatenate one or more metadata and include personalized text with the Literal option.

  • Can edit body content (see Add or Edit a Body Mapping).

  • Can get metadata values from a specific stage with the origin suffix (see Mapping Rules Syntax).

Disadvantages

  • Cannot programmatically process metadata values.

Web Scraping Configuration

Indexing Goal

  • Exclude specific web page sections.

  • Extract specific content to create metadata.

  • Create sub-items.

How to Use

Advantages

  • Efficiently processed by the Crawling stage.

  • Coveo Labs Chrome extension is available to easily create web scraping configurations (see web-scraper-helper).

  • Exclusion of repeating web page parts from index (e.g., header, sidebar, footer) (see Exlusion).

  • Extraction of content from HTML elements with XPATH and CSS locators to enrich metadata (see Selectors).

  • Splitting web page parts into multiple index items (see SubItems).

Disadvantages

  • Only available for Web and Sitemap sources.

  • Requires developers skills to create the JSON web scraping configuration and take full advantage of XPATH and CSS expressions.

Indexing Pipeline Extension

Indexing Goal

  • When it is not possible with the above tools to:

    • Add/modify metadata.

    • Add/modify data streams.

    • Reject items (in pre-conversion scripts).

    • Exclude specific web page sections.

  • Use external resources and services (e.g., use an image recognition API to inject metadata).

  • Add/modify item permissions (e.g., for a Push source for which the crawler does not associate permissions).

How to Use

Advantages

  • Availability of Coveo Labs Chrome extension to get samples and test indexing pipeline extensions (see Coveo extension manager).

  • Accessibility to third party services and databases.

  • Flexibility of Python language and available libraries (see Python Modules Available to IPEs).

  • Extension code reuse with conditional execution and extension parameters.

  • Index item processing to:

Disadvantages

  • Requires developer skills to create the Python scripts.

  • Each extension execution affects indexing performance.

  • Limit of 10 indexing pipeline extensions per organization.

  • Extension script execution limited to 5 seconds.