Symbol search

The WebUI command line requests suggestions through its configured same-origin /autocomplete path. Symbol suggestions depend on the installation's instrument registry and the user's permitted commands. This manual does not supply a live registry or vendor data.

Lookup and indexes

The built-in lookup searches its configured registry fields, then ranks the matching instruments. The WebUI reads the collection and does not create indexes automatically. An operator should inspect the matching release's identity adapter and provision the required case-insensitive indexes against a disposable copy before changing a registry.

Index names and registry locations belong to the deployment. Case-insensitive matching requires compatible collation support; a plain index may still scan many keys. Backends without collation support can retain the fallback search behavior.

Public examples

Use symbols such as EXAMPLE and a generic DEMO source in documentation. Do not export registry snapshots, production collection names, holdings or vendor entitlements into screenshots. Measure lookup latency on your own representative test workload rather than assuming a performance figure from another installation.