...
- entity fields
- association fields
- entity fields with geo data
- association fields with geo data
- document fields
This page has been organized into the following sections, for ease of localization
| Table of Contents |
|---|
Format
| Code Block |
|---|
{
"display": string,
"searchIndex": {
"entityFilter":string, // (regex applied to entity indexes, plus starts with "+" or "-" to indicate inclusion/exclusion, defaults to include-only)
"assocFilter":string, // (regex applied to new-line separated entity indexes in associations, starts with "+" or "-" to indicate inclusion/exclusion, defaults to include-only)
"entityGeoFilter":string, // (regex applied to entity indexes if the entity has geo, starts with "+" or "-" to indicate inclusion/exclusion, defaults to include-only)
"assocGeoFilter":string, // (regex applied to new-line separated entity indexes in associations with geo, starts with "+" or "-" to indicate inclusion/exclusion, defaults to include-only)
"fieldList": [ string ], // (comma-separated list of doc fields, starts with "+" or "-" to indicate inclusion/exclusion, defaults to include-only)
"metadataFieldList": [ string ], // (comma-separated list of doc fields, starts with "+" or "-" to indicate inclusion/exclusion, defaults to include-only)
}
} |
...
| Anchor | ||||
|---|---|---|---|---|
|
The source example indicates how to include all discovered metadata values into the search index. The string encompasses all returned valuesIn this example, the title is not indexed, no entities of type keyword or topic, or associations containing the string "theme" are indexed, and only a few metadata fields.
| Code Block |
|---|
}, {
"searchIndex": {
"fieldList":"-title",
"entityFilter": "-Keyword|Topic",
"assocFilter": "-.*theme.*",
"metadataFieldList": "fieldSet1,fieldSet2.indexable"
}
}
]
} |
| Panel |
|---|
Footnotes: Legacy documentation:
Legacy documentation:
|