We need a "not a match" function for relationships
The ability to declare two records not a match has done much to prevent incorrect merges. Along these same lines, we need a "not a match" for relationships. For example, I have an ancestor who is continually linked to parents that are not related to him in any way. The documentation is very solid that this particular couple is not his parents. However, because old Family Group Records erroneously listed him in that family, he is continually linked to the same incorrect parents. I would like a way to declare him "not a child of" those parents. This would function similarly to the not a match. We could hit the button ADD CHILD or ADD PARENT and if we tried to add a parent or child using a specific PID, we would have an option to declare "NO RELATIONSHIP." We would have a field where we could list all the reasons and sources that explain why there is no relationship between these individuals, and then when another patron tried to connect those two PIDs, the no relationship reason statement would come up to explain the reason the addition is incorrect. I also think the process should check the merge histories for any PIDs that have specifically been marked as no relationship. It should not only apply to the active PID.
Another (possibly easier to program) idea would be that we could place a "not related" note somewhere on the page, and then any time someone tried to add any child or any parent to the record, the "not related" note would first come up for the contributor to read before being able to add any relationships to the record.
I feel like the alert note has been helpful to stabilize the details screen, but I don't feel like "not related" information works well in that alert note. I think it would be more productive to be able to make the not related information more PID and relationship specific if possible.