Workaround for Birth-only relationships
Quote from Tom Holden on 2024-07-03, 1:06 pmVersions 4-10 of RM make no distinction in lineage outputs among the various parent-child relationships users are allowed to set in the Edit Person dialog. This can result in confusion for the user and unwanted clutter for some purposes when relationships such as adoption or step are followed instead of or in addition to birth. A previous workaround addressed part of the problem by setting the last family viewing history to birth family (See Children - Set Lineage to Birth ). However, it did nothing for the outputs of the Set Relationships and Relationship Calculator tools. The latter may describe the relationship via an adoptive line rather than the blood line as in this post in the RM Community.
It was suggested by RM Support to break the adoptive link before running Set Relationships but that is untenable to carry out and restore when there are multiple non-birth relationships in a tree. And RM does not make it easy to find them. But the concept is valid if it were a user option in the Set Relationships dialog. This script illustrates how trivial a process it could be while empowering those with basic SQLite operations to have a viable workaround while waiting for RM to deliver needed functionality around the types of parent-child relationships.
Versions 4-10 of RM make no distinction in lineage outputs among the various parent-child relationships users are allowed to set in the Edit Person dialog. This can result in confusion for the user and unwanted clutter for some purposes when relationships such as adoption or step are followed instead of or in addition to birth. A previous workaround addressed part of the problem by setting the last family viewing history to birth family (See Children - Set Lineage to Birth ). However, it did nothing for the outputs of the Set Relationships and Relationship Calculator tools. The latter may describe the relationship via an adoptive line rather than the blood line as in this post in the RM Community.
It was suggested by RM Support to break the adoptive link before running Set Relationships but that is untenable to carry out and restore when there are multiple non-birth relationships in a tree. And RM does not make it easy to find them. But the concept is valid if it were a user option in the Set Relationships dialog. This script illustrates how trivial a process it could be while empowering those with basic SQLite operations to have a viable workaround while waiting for RM to deliver needed functionality around the types of parent-child relationships.
Uploaded files:Quote from kevync on 2024-07-05, 8:49 amcreative solution -- thanks for sharing.
Fortunately I have only a handful of known adoptions in my database.
For someone who has dozens (or more)-- this would be quite useful
creative solution -- thanks for sharing.
Fortunately I have only a handful of known adoptions in my database.
For someone who has dozens (or more)-- this would be quite useful