This is not the best way exclude by surnames because i have a long list there. But I have no idea how do it more clear. I could create excludes similar filters 1 and 2 using “Exclude Ancestors of person ID2” and “Exclude Descendants of Ancestors” but it will also exclude Descendants of person with ID2. Maybe anybody has some propositions.
But the main question is how exclude one filter from another one? I want “Exclude” people from “Descendants of Ancestors” filter.
I tried do it in such way, but looks like it does not work, because I still receive the sane 1213 persons:
What I would like to add is that the filtering mechanism lacks some kind of designer with drag and drop, which can be used to combine existing filters in such a way that some of them include, others exclude search results. Of course, this is easy to say, but difficult to do. But maybe someone has some ideas or plans for the development of filters in this direction.
Add that Tag using the Add/Remove with your 1st Filter
Remove that Tag using the Add/Remove with your 2nd Filter
Reset the Filter Gramplet
filter on the Tag with the Filter Gramplet
If excluding the 2nd filter temporarily, you could Tag the 1st filter’s results, the use the Tag and find results that do not match the 2nd custom filter.
But experimenting with excluding Filters in combination is much more intuitive when using the Inverts in Kari’s experimental FilterParams tool.
The basic premise is to create the first filter so the people matching the filter is true. You have that with your first two filters.
To take people out of that filter; create a filter finding these people. To exclude them, set that filter to Return values that do not match the filter rules.
Then you can combine the filters. Filter 1 has to be true, and those who in filter 2 has to be true. People that are in both these filters will be the people you want.
The “Descendants of Ancestors” filter shows similarly in the FilterParams tool on my Windows system. It omits the rule label when there are multiple rules referencing the same <filter>.
I think it might be related to the way this tool consolidates control of parameters. The intent is to allow users to change all the rules (the ones that use the same parameter) simultaneously. It works fine for String parameters … but not for <filter> parameters.