There’s already another (stagnant) rule request list thread. Unfortunately, you could could get buried in infinite rule request work. There’s another request that asks for a tutorial on creating Rules. But that might be sidestepped with the SQL supprt … since there are so many tutorial in existence on building those queries. (Although something intoductory about the Gramps database model might help.)
However, @Davesellers has a point about the existing filter rules being a bit thin in the Families category. Both in finding families that match criteria and in finding secondary objects of specific families.
Merging interactively could be greatly steamlined if there was an (efficient!) winnower of objects related to a family.
Say that there was a rule to find the Families (both as a child and parent) of the Active Person.
Then a matched set of Family Rules for each object type:
- find
<object type>under[family](where[family]could be a list of IDs) - find
<object type>under<family filter](which be an Active Family filter)
And where these rules had options to include:
- Family level objects and/or Family Member objects
- full drill-down of secondary objects. (So a search for Citations would even find the Citation for the Media object attached to marriage Family event of the 3rd child.)
Essentially, the (full drill-down including Family and Personal secondary objects) Rules would work with the same subset of objects that are already exported for a selected person. So the winnowing functionality already exists elsewhere.
So… with the families of active Person filtered in the Families, you could walk through selecting the merging all the duplicate families within 1 degree of separation. Then step through each category, merging the duplicate people of the active family, then all the duplicate Events, Places, Repositories, Sources, Citations, Media, Notes.
Doing this step through Person-by-Person would be massively more cycles (and error prone) than Family-by-Family.