...
Since the level in the sort works the same as the display and keywords it means that we can add additional text to the sort, and this can be used to our advantage to ensure that the order of the different types of entities found can be displayed to the user in a certain order. For example if we search enabled suburbs, roads and property addresses then we could use the sort field to ensure that suburbs are always listed first then followed by roads and then properties (regardless of how "well" the actual results match the search). To do this with our previous example we could change the level1 tag of the sort to
| Code Block | |
|---|---|
| xml | xml |
| linenumbers | true | <level1>0020 ${suburb} ${name}</level1>
|
...
The first format has a single line for each group of synonyms with the alternatives separated by a comma, for example:
| Code Block | |
|---|---|
| none | none |
| linenumbers | true | ST,STR,STREET |
And the seconds format has the original word followed by an equals sign and a space separated list of alternatives, for example:
| Code Block | none | none | linenumbers | true
|---|
abandon=vacate revoke=vacate vacate=abandon revoke |
...
To switch to the older method of generating indexes you can set
| Code Block | ||
|---|---|---|
| ||
<geometryFirst>true</geometryFirst>
|
...