Managing Items and Permissions
- Adding or Updating a Single Basic Item in a Shared Push Source
- Adding or Updating a Single Item in a Push Source
- Deleting an Item and Optionally its Children
- Deleting Old Items in a Push Source
- Managing Batches of Items in a Push Source
- Pushing Item Data
- Understanding Push Source Item Metadata
- Simple Permission Model Definition Examples
- Complex Permission Model Definition Example
- Understanding the parentId Property
- Item Models
Understanding Push Source Item Metadata
A metadata is a key-value pair that typically provides a single specific piece of information about an item (e.g., its author name, its indexing date, etc.). You can push as many distinct metadata key-value pairs as you need with each individual item you add or update in a Push source.
To be of any use, a metadata needs to somehow populate at least one field in the index of your Coveo Cloud V2 organization. By default, when the Coveo Cloud V2 indexing pipeline processes a Push source item, it automatically attempts to use each incoming metadata to populate a field of the corresponding name in the index. The target Push source may also be configured with custom mapping rules to complement this behavior.
In summary, if you intend to include a metadata key-value pair along with an item you add or update in a Push source, you should first ensure that a matching field exists in your index (see Creating Fields), unless you want to define your own custom mapping rules to deal with this metadata (see Managing the Mapping Configuration of a Source).
The following diagram provides a simplified overview of the process that populates fields with metadata for incoming Push source items:
The articles in this section provide information to help you push item metadata adequately.