Metadata query engine indexing of custom metadata

Content Platform Tenant Management Help

Version
9.7.x
File Size
4269 KB
Audience
anonymous
Part Number
MK-95HCPH002-19

By default, when custom metadata indexing is enabled for a namespace, the metadata query engine indexes the content properties for that namespace and not the full text of custom metadata. If the namespace doesn’t have any content properties (that is, it’s not associated with any content classes that have content properties), no custom metadata is indexed.

You can choose to have the metadata query engine index the full text of custom metadata. If you enable this option, the metadata query engine indexes both content properties, if any exist, and the full text of custom metadata.

With content properties, the metadata query engine indexes only the values that you determine are of interest. When indexing the full text of custom metadata, the metadata query engine indexes each word individually.

For example, suppose an object has this XML in its custom metadata:

<doctor>
    <name>Lee Green</name>
</doctor>
<patient>
    <name>Paris Black</name>
</patient>

If you’ve defined the Doctor_Name and Patient_Name properties, the metadata query engine index includes:

Lee Green
Paris Black

If full text indexing is enabled, the metadata query engine index includes:

doctor name Lee Green name doctor patient name Paris Black name patient

In this case, to use the metadata query API to find the objects that have a doctor named Lee Green, users would need to query for custom metadata containing “doctor.name.Lee Green.name.doctor”. This kind of query can become very complex when elements are nested to deeper levels or when they have attributes.