- Available Source Types
- Content Retrieval Methods
- Source Permission Types
- Source Item Types
- Source Credentials Leading Practices
- Refresh vs Rescan vs Rebuild
- Edit a Source Schedule
- Edit Source Extensions
- Add or Edit a Source
- Security - Tab
- Manage Source Mappings
- Mapping Rule Syntax Reference
- Mapping Rules Hierarchy
- Edit a Source JSON Configuration
- JSON Modification Examples
- Understanding Crawling Performance
Mapping Rules Hierarchy
It is possible and recommended to have multiple mapping rules using different metadata to make sure your items are indexed with relevant values even if your preferred metadata could not be extracted.
A rule is successful if at least one metadata is mapped correctly to an index field or if the rule contains text.
Rules only containing text (no metadata names) are always successful.
Once a rule is successful, the other rules (if any) are ignored.
If no rule succeeds, the index field is left empty.
Here is a set of mapping rules applied to the
author index field. These rules appear in the same order in the Coveo Cloud V2 administration console, and will be applied starting from the top.
If the metadata
lastNamedoes not exist but
firstNamedoes, the rule is successful, meaning the field
authorwill contain the firstName metadata values. In such case, the following rules are ignored.
If both metadata in the first rule do not exist, the string contained in username will fill the field.
If none of the above metadata exist, then the string
Anonymouswill be the only value of the author field.
The rule will never apply in any circumstances since the third rule only contains text.