In Advance search, restrict the search to specific columns

[Labrus]

We illustrate this general issue with the following example. In we chose Loc (=locative case) in Morphology window, we get more results than needed, some constructions that appear as results do not contain "Loc" in their name (formula), for example #272, and they appear as results because it also has Location as a tag in Semantic role (a separate column in the database). This means that when searching for tags inside Morphology, the engine is pulling overlapping tags (e.g. Loc vs Location) from other columns in the database. Instead, the search should be restricted to a single column that corresponds to a give search category (for example, only Morphology, or any other)

[bast]

I plan to fix this one in time. But this will require some work inside the code.