Skip to content

Add HasNotAttributeBase filter - #2488

Open
soig wants to merge 1 commit into
gramps-project:masterfrom
soig:HasNotAttributeBase
Open

Add HasNotAttributeBase filter#2488
soig wants to merge 1 commit into
gramps-project:masterfrom
soig:HasNotAttributeBase

Conversation

@soig

@soig soig commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

This enables to look for persons that do NOT have a particular attribute (eg: looking for people w/o occupation in order to know which ones we need to find that info in eg: their mariage act)

@soig
soig force-pushed the HasNotAttributeBase branch from 4561d87 to b5ea8f6 Compare August 5, 2026 09:40
Enable to look for persons that do NOT have a particular attribute
(eg: looking for people w/o occupation in order to know which ones we
need to find that info in eg: their mariage act)
@soig
soig force-pushed the HasNotAttributeBase branch from b5ea8f6 to f120bee Compare August 5, 2026 09:53
@dsblank

dsblank commented Aug 5, 2026

Copy link
Copy Markdown
Member

Hey @soig, how is this different using a filter for people that have an attribute, and using the checkbox "Return values that do not match the filter rules"?

@soig

soig commented Aug 6, 2026

Copy link
Copy Markdown
Contributor Author

@dsblank It's not the same b/c inverting results means that I cannot combine it wither other filters.
See my workflow : I'm creating a filter with that rules (not having "occupation") plus 2 rules :

  1. born between eg 1860 and 1930
  2. ascendants of XX

This enables me to look for a subset of people and find out who miss that info, and thus who I need to doble check their mariage in order to find their occupation.
I usually start from one people (me, my wife, one my cousins), choose him/her as the ascendant, then go up by batches (hence the "born between X & Y")
This makes the search manageable, eg one batch a week.

If I'd use the existing rule "has an attribute", then if I seltected "Return values that do not match the filter rules", it wouldn't work with the other rules "ascendants of X" & "born between Y & Z", it would basically return every people but for those in that very small subset.

@dsblank

dsblank commented Aug 6, 2026

Copy link
Copy Markdown
Member

@soig, you can nest custom filters inside other custom filters. So you can make one filter that negates a rule, and then use that filter from others. In isn't convenient (we're working on that) but that is the way Gramps was designed. Otherwise we'd have double the number of filters just to negate them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants