Train the algorithm to recognize invalid SPs
According to policy, if a couple was never married, and never lived together, and never had any sort of a relationship, they should not be sealed. In the system, if the couple had a child together, the couple can be listed as the child's parents, and the couple will be listed together as the parents of the child, but the system allows the patron to delete the relationship between the couple so that no relationship exists between the man and the woman that gave birth to this child. Deleting the couple relationship appropriately removes the Sealing to Spouse option so that a patron "Cannot Request--Not Available." The system also places this note: "These people do not have a couple relationship but are the parents of a child. If they were married or lived together as husband and wife, add a couple relationship to link them as spouses, so that you can request the sealing. If they were never married or never lived together as husband and wife, do not have them sealed." I agree that this message is in compliance with current policy.
However, current policy would also dictate that a child cannot have a valid sealing to parents who were never sealed to each other. I understand that an SP could be done, but that SP will not be valid until the parents are sealed to each other. In the cases where the child's parents do not have a valid sealing (and never will have a valid sealing), it seems like a waste of resources to seal the child to these parents, particularly if the child is already sealed to his/her "real" parents who raised the child.
Please fix the algorithm so that if a child is connected to parents who do not have a couple relationship, then the child's SP to those parents will be listed as "Cannot Request--Not Available."
I'm particularly interested in this because I have an ancestor who was ****, resulting in the birth of her son. Knowing the child's biological father is useful information, but the child should not be sealed to that father since the child's parents should certainly never be sealed to each other. I have placed notes all over the child's record, but another patron has come along and shared that SP with the temple (even though the child is already sealed to his "real" parents and has no need of another SP).
Please fix the algorithm to recognize that if a couple has no couple relationship, then a child cannot be sealed to that couple. This seems like an easy fix that would prevent a fair amount of invalid temple work.