I created filters for all close relatives, male descendants, children and spouses of current person (name genealogy), relationship paths etc…
But, most reports don’t filter… Which is a real shame. Do I really first need to export a smaller subset of my family tree, then import it in a new tree, to be able to create those reports the way I want them?
Most reports are built to satisfy a specific need for a user. And since reports are often a first foray into hacking Gramps, they generally start simplistic in design with few options. The options that tend to be targeted first are things that CANNOT be done with a simple workaround… like a filtered export.
That’s why filters tend to be bolted on later.
It seems like documenting how to add a filter option to an existing report would be a lovely expansion page to the “Adapt a built-in Report” wiki article. Right now, it is just an un-validated shell about about how to properly fork a built-in report so that you can experiment.
But an article about how to add a filter option would make it a USEFUL set of documentation. (Started the “example of a gramplet with a custom filter configuration option” topic Sep 2024) And along with adding a Sorting option article, it might get a some people playing with improving our reports.
Both articles are beyond my Python experience levels.
That report name doesn’t sound familiar. Since you’re in the Netherlands, maybe you’re looking at a Dutch translation? Help us find the same example in English.
Ok. Thanks for that clarification that “family members with the same surname” is a custom filter you have created.
But help us find a specific Report where you want to apply this filter but where that option does not exist.
Was it “6.3 Descendant Tree”, “6.4 Family Descendant Tree”, “7.5 Descendant Report”, “7.7 Detailed Descendant Report”? Or maybe one of the four add-on reports related to “Descendant”?
7.7 The detailed descendant Report would be very nice!
But I think it could be useful in nearly every report.
I don’t know much about the programming of Gramps, but I can imagine it could be a good addition in a general reports framework.
You could create a .gramps (xml) export using one of your filters and then create a temp database to import the file. Then you can run a report that is restricted to the people you want.
Maybe not ideal but it is a way to get the reports that you want/need.
That is what I have been doing up to now !
Just seems a shame, filters is one of the very strong points of gramps. Just not used to its full potential.
It’s been awhile since this thread had any activity.
Perhaps we could use the built-in Complete Individual Report to illustrate the parts of enabling a People filter option in a Text Report ? (It also does Sorting so that’s a bonus example.)
Hello Brian,
I adapted my version of the Detailed descendants Report quite a bit now, and because of that feel a bit more confident in programming for Gramps.
Filters are easy because they just consist of a list of handles. So instead of working your way through the entire database, you just work through the filter.
The harder part is probably adding the GUI selection in the Report for selecting the filter. And doing so without breaking stored configuration options and “Books” that reference the Report.
My report will be adapted to my “special needs” , so not really suitable as an add on.
Gramps has given me a lot though, and if I get the filter to work I will add the filter possibility to some other reports.
Perhaps you could look through those while creating adding a filter to your adapted report? They could use some love and be improved.
There are a lot of reports. So gathering encouraging a group of people to rackle upgrading reports would have a lot of benefits.
It would give people confidence to build and publish new reports and maybe create a collaboration resource. It would be nice if someone came up with a more intuitive replacement Label for “Report options (2)”!