powered by CADENAS

Manual

Manual

5.9.2.14. Search index creation

Index order numbers dependent on value ranges

[Note] Note

In order for value ranges to be considered when searching and their single values to be found, they have to be indexed.

For catalogs without value ranges there is no need for indexing.

If the number of possible combinations resulting from value ranges is too high, there is no need for indexing as well, but a ReverseConfig is used, which also enables successful finding of value range values.

So the setting has to be correctly set in all cases.

TestMeta will display a warning, if there are value ranges but no ReverseConfig or value ranges cannot be resolved (and so cannot become part of the Lucene index). Then the modeler has to set the option Index order numbers dependent on value ranges on Yes, in order to avoid the error message or apply a ReverseConfig (see Section 5.8.2.1.15.16, “ Reverse TypeCode Rule Editor ”).

More important information can be found under Section 3.2.16, “Classification according to CNSORDERNO / CNSTYPECODE ”.

The setting is performed on catalog and project level.

[Tip] Tip

If there is a need for indexing basically, it makes sense to apply following rule:

If there are many projects to be indexed in the catalog, then it is recommended to set Yes on catalog level, there are little, then No.

Afterwards adjust the deviations on project level. Default is Use catalog setting, for deviations set Yes or No.

[Note] Note

If the setting is changed to "Yes", after this the full-text search index has to be created anew.

Setting options on catalog level:

Value range:

  • Yes:

    VARSEARCHRESOLVEORDERNO=1
    
  • No: (default)

    VARSEARCHRESOLVEORDERNO=0

    or key VARSEARCHRESOLVEORDERNO not available

    [Note] Note

    Since the feature is new[a], most catalogs still might have the default setting "No". (Then on project level there is still the default setting Use catalog setting.)

    [a] April 2018

On catalog level the key VARSEARCHRESOLVEORDERNO is found in $CADENAS_DATA/23d-libs/<catalogname>/dir.prj.

Setting options on project level:

For each project the catalog setting can be overwritten. Except when setting Use catalog setting, then the catalog setting is used. And this is the default.

  • Yes:

    VARSEARCHRESOLVEORDERNO=1
  • No:

    VARSEARCHRESOLVEORDERNO=0
  • Use catalog setting: (default)

    ("Catalog setting" is the setting on the root node of catalog.)

    Key VARSEARCHRESOLVEORDERNO not available

On project level the key VARSEARCHRESOLVEORDERNO is found in the project file.