Managing search and indexing for an individual namespace

Content Platform Tenant Management Help

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

You can change the search and indexing settings for an individual namespace at any time. You can:

  • Enable or disable search.

    Disabling search also:

    • Disables all indexing for the namespace
    • Removes the objects in the namespace from the metadata query engine and HCP search facility indexes
    • Deletes the list of excluded annotations for the namespace
    • Deletes all associations the namespace has with any content classes
  • If search is enabled:
    • Enable or disable indexing. Disabling indexing also disables custom metadata indexing for the namespace. However, it does not remove objects in the namespace from the indexes.

      By default, when you create a namespace with search enabled, indexing is also enabled.

    • Add or delete associations between content classes and the namespace.
  • If indexing is enabled, enable or disable indexing of custom metadata. Disabling custom metadata indexing also disables metadata query engine indexing of the full text of custom metadata.

    If you disable custom metadata indexing after it has been enabled, custom metadata that has already been indexed is not removed from the index.

    By default, when you create a namespace with search enabled, indexing of custom metadata is disabled.

  • If indexing of custom metadata is enabled:
    • Enable or disable metadata query engine indexing of the full text of custom metadata. If you disable this option after it has been enabled, custom metadata text that has already been indexed is not removed from the index.
    • Specify annotations to be excluded from metadata query engine indexing of custom metadata. Annotations are excluded by name. So, for example, you could exclude all annotations named miscellaneous. Users cannot query for objects based on the content of excluded annotations.

You can also reindex an individual namespace at any time. You might do this, for example, if you associate additional content classes with the namespace.