powered by CADENAS


Manual  Index order numbers dependent on value ranges

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.

That means, the option Index order numbers dependent on value ranges has to be set correctly 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.

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.

In PARTproject -> Edit project -> tabbed page General -> Search index creation -> Index order numbers dependent on value ranges make the specific settings for catalog and project level, depending on whether order numbers should be indexed depending on value ranges or not. For more details see Section, “ Search index creation ”.

This setting can also be performed automatically. On this see Section, “"Resolve check" Plugin”.