I think you missed the point I was making that maybe genealogy programs and documents should be more rigorous in using names that distinguish blood relatives from non-blood ‘relatives’. “Uncle by marriage” then would be more accurate than “uncle” in my example of the man married to my mother’s sister.
Sorry! You are right, I missed that.
that might explain things (and what I suspected) — but without knowing what logic is used – not exactly helpful – guessing the script is maybe done for efficiency vs “practical use”. Now, from that point it gets a big complicated on who want what and does want what. I would lean toward most people preferring Blood. However, this also connects back to my enhancement suggestion to have options and rules of how/when/what methods are used (or not)
From what I have found looking thru many dual relationships–
Set Relationships is going to calculation based on the first relationship it finds FROM THE PATERNAL SIDE OF THIS GROUP OF FAMILIES UNLESS it is a direct ancestor or aunts/uncles by marriage or sis-in-law/bro-in-law or son-in-law/dau-in-law – which is why all hubby’s maternal 3rd gg-uncles are listed as spouse of 3rd gg-aunts who are the paternal side of this equation— this side of
the equation means that the paternal/ maternal side can change every time you go back 1 more generation…
1 Like
actually that makes sense (well in a way). And once again goes back to my feature enhancement request.(Rules/Options for setting relationships)
I have developed a solution to the problem of color coding using RM 10.0.1’s new Set Relationships. Basically, the solution does not use the Set Relationships data in the RM database at all. Instead, it simply follows the parent-child links and the spouse-spouse links on its own. All relatives are color coded red and all spouses of relatives are color coded green. A person who is both a relative and a spouse of a relative is color coded red. The spouse of the base person for the relationships is color coded green unless he or she is a relative of the base person. The spouse of an aunt or uncle is color coded green unless they are also a relative of the base person.
I’m going to post my solution to Tom’s SQLite site. It may take me few days to get it cleaned up for public consumption.
I still think the new Set Relationships feature in RM 10.0.1 needs to be adjusted so that it will show a relative relationship in preference to a spouse of a relative relationship when both relationships exist.
Even though the solution is SQLite and cannot be accomplished from the RM user interface, it’s easy enough to describe the general algorithm.
- Clear all color codes
- Color code a base person (usually yourself) to be red.This person is hardwired into the script and has nothing to do with RM’s root person.
- Color code all parents of red people as red. Repeat until all ancestors are color coded red. Actually, these first three steps could be done in the RM user interface and the ancestors can be color coded by RM without any repeats on your parts. All of the following steps require SQLite.
- Color code all children of parents who are red as red (one or both parents can be red). Repeat until all such children are color coded.
- Color code all spouses of people who are not yet color coded and who are spouses of someone who is red as green. This step doesn’t need any repeats.
My actual script has a lot more colors and nuance than that for in-laws and such, but that’s the basic idea. I’m not set up to run recursive scripts, so I just repeat steps #3 and #4 until nobody else is modified. It sounds pretty crude, but I can complete steps #3 and #4 in just a few seconds each. Maybe I’ll look into recursive scripts, but I really don’t need them just for my own personal use.
2 Likes