Added a Son on Source Linker with No Relationships with Parents
LegacyUser
✭✭✭✭
Jordi Kloosterboer said: There was a source for a christening of a son. When I added the son via source linker, it added the person but with no parents as the relationship. Therefore, when the page refreshed (in order to show the person I just added), it did not show the person I just added. There is no way to get to that new person except through my contributions. Although, it looks like the person was not created (so I didn't go to my contributions...). Anyway, so I just made a new person.
When I went to that new person it lists the duplicate that I made. I am going to just delete that person (after a week or so in case someone wants to investigate the profile) as I can since no one else has added to him.
What I am suggesting is to have some clause check that parental relationships are indeed added to newly made people via the source linker.
This is what was added on source linker: (no relationships added).
When I went to that new person it lists the duplicate that I made. I am going to just delete that person (after a week or so in case someone wants to investigate the profile) as I can since no one else has added to him.
What I am suggesting is to have some clause check that parental relationships are indeed added to newly made people via the source linker.
This is what was added on source linker: (no relationships added).
Tagged:
0
Comments
-
Jeff Wiseman said: That record you indicated has no source attached to it, but the "duplicate" has 3. I'm not sure what happened but you should just merge the GWCV-MZF Francis in to the more complete GWCJ-LS7 Francis before someone picks it up and starts doing incorrect ordinances on it.
That first record without the sources does not have the death date showing Francis died only 4-6 months after birth, so the second record is subject to someone reserving it and doing all of those ordinances which are not necessary.0 -
Jordi Kloosterboer said: I said I would delete it in a week, but I just deleted it.0
-
Jeff Wiseman said: That'll do it :-)
Just remember though that a PID is FOREVER. Once a record is created, it never goes away. "Deleting" the record doesn't really delete it at all. It just puts it into an "archived" state where it doesn't show up in normal database viewing and search operations.
Sorta like having a Trash Can on your desktop that can never be emptied. So for PIDs that are known to be duplicates, they can always be merged, even when someone else has touched them. And for PIDs that have ordinances recorded against them, it is better to merge them so that the ordinances aren't lost from view with the deleted PID0