Filter out people for exports and reports

Old topic, but perhaps there’s an update.

I have an extensive ancestry list. (It’s huge!) To ensure I have reached a dead end with each branch and leaf, I close off each one with an additional entry for both parents: SURNAME = x (example, Fred Charlemagne, father: surname = x, mother: surname = x). Exporting this to a relational graph report, I can’t find a way to filter out these dead ends by SURNAME or any other method.

Using GrampsAOI64 2.5.4

Set all these “x” surname persons to be Private.
Make a backup before doing mass changes

You can do this with the Set Privacy tool with a Name Filter (using Regular Expressions parameters for exact matches, not pattern matches)

You can also use one of the sample Privacy SuperTool scripts to update the Privacy of selected objects.

Your exports and Reports have a GUI option to exclude Private persons. So you won’t have to backtrack to write a custom filter.

1 Like

select the Use regular expression to exactly match “x” or “X” (?<![\w])x(?![\w])
(select the Case sensitive option in the rule to only find the specified “x” in lower case only.)

A little confused regard the follow-up images. Are these images coming from the Set Privacy Tool? I just installed the 1.0.16 addon and restarted Gramps. The Privacy Tool window is a dead end! The Person Filter combo box will not progress to any screens or additional filtering. The only options are how far back in years do you want to set privacy to the ENTIRE DATABASE!

These are from the People category Custom Filter editor
and the dialog when + adding (via the People category Edit Rule dialog) to a custom filter (including how to search for a rule by part of its name and a tooltip showing some RegEx operators.)

You can create the Custom Filter with the Filter Gramplet, test the filtering resuts in the flat list People view, and …if the results are correct… use the Custom Filter with the Set Privacy addon tool

Thank you for clarifying. I got the filter set; however, the Set Privacy Tool’s Person, Event and Media filter combo boxes are set for the entire database and NO other options. So, this addon will set everyone in the entire database to private for up to 2000 years if I select Execute


.

Sometimes Addon plugins do not monitor the Gramps internal “signals” for changes. In this case, the change was that you added a new Custom Filter. But the addon fails to check for new filters added during this session and the tool has an old list in its menus.

The workaround is to quit Gramps and restart it. The new Custom Filter should now appear in the menu.

(Yes, this is a bug. And it should be reported. But the workaround should ‘get you through the night’)

1 Like

YEP! That did it! Solved!
Appreciate the help!

Where was this topic raised before? (linking it to this answer would close another thread.)

Well, well, well, well. The filter set a bunch of people to private, but I don’t know who. If I export the whole set using the filter I still get a bunch of x placeholders and a serious cutdown list of actual ancestors. Always make a backup before making such edits, yeah.

Any idea how I can get a list of everyone marked private? And possibly undo this? I already tried Abandon Changes and Quit.

View → Configure… the flat list view to show the Last Changed, Number of Parents, and Private columns
Apply and Close the Configure People - Person View dialog

Sort on Last Changed column with the New at the top. The timestamp tells you which were changed and how recently. The Number of parents tells you if they were the right Persons. The Private tell you if the Privacy was actually set.

OK. No one was marked private. And a correction, all ancestors are there in the export.

Backed up data set. Going to try the Set Privacy Tool again. This time not supplying years to check because the x placeholders do not have dates.

1 Like

AAAAAND results this time! X placeholders were marked private!


1 Like

Big Tree. If 22,989 were set to be Private, how many people are in that tree in total ?

Your capture was also in the Grouped People by Name view. That interferes with the Last Changed sort. It collapses the other "not named ‘x’ " people who might have been inadvertently set to Private at the same time.

About 50K in the tree. There are some rabbit trails I later found that were bad but kept them in the DB. But 3 grandparents with super pedigrees in Medieval Europe, though. The number keeps climbing.

1 Like