Coveo Cloud Indexing Pipeline Extensions
Coveo Cloud Document Processing Manager provides stages during which you can modify programmatically how your items are indexed (see About the Indexing Process). To achieve this, you must create and apply indexing pipeline extensions (IPES) to your sources (see Indexing Pipeline Extension Overview).
Items processed during a rebuild operation in Sitecore are then sent to the Document Processing Manager for indexing . When you manually rebuild an external source through the Coveo Administration Console, or when a Coveo Cloud schedule triggers a scan of your external source, the external source documents are now fed to the Document Processing Manager. Hence, indexing pipeline extensions can be applied both to your Sitecore and external content.
You can create an indexing pipeline extension to modify the body of your items.
Choosing Between a Preconversion and a Postconversion Extension
An important stage of the Coveo Cloud Indexing Pipeline is the
Processing stage. During this stage, incoming items are converted to an index-ready format (see Processing). Coveo Cloud provides indexing pipeline extension stages prior to this conversion stage and after it. Coveo Cloud documentation is available to help you decide on the more appropriate indexing pipeline stage to choose (see Pre-Conversion Versus Post-Conversion).
Creating and Applying an Indexing Pipeline Extension
You’re now ready to create your indexing pipeline extension (see Add or Edit an Indexing Pipeline Extension). Have a look at the script samples available in the Coveo Cloud documentation to help you get started (see Indexing Pipeline Extension Script Samples).
To remove sections of indexed HTML from your Sitecore items, you can use our Sitecore-specific example extension code.