Attach Source to Living Private Person
Interesting that I can't attach a source to a private living person using this system, but I can with normal indexed sources and a source I make without the "Attach to Family Tree" process. Is this something that was left behind when we couldn't attach to living people, or is this meant to be like this?
Comments
-
What you are saying - and I have just confirmed this - is an image-only source cannot be attached to a living person, whereas an indexed source / record can.
Very strange - I would have thought it should be the other way around. As an image-only source can be attached to multiple IDs, there should be no reason for it not to be attached to both living and deceased persons.
On the other hand, if I attach an indexed source to a living person in error, I assume it is then not possible for another user to detach it and reattach to the correct ID. I say "assume" because I don't know what another user can see with regards to its attached / unattached status when they make a search. From my own account, I can see the tree symbol alongside the living person to whom I have attached the source - but what do other users see? Obviously not the ID of the living person in my private space!
Perhaps someone with access to two accounts can advise how a source attached to a living person in their account appears in, say, their spouse's account.
However, I don't want to detract attention from Jordi's post and hope he will get a direct answer to this, too.
0 -
This is a problem that FS needs to address. Here's hoping that they are still following these discussions.
0 -
Paul, if you attach an indexed source to a living person, other people can still attach that same source to their own living (or deceased) person too. They will not know if that source was attached to another living person outside of their private space. When the person dies and multiple people had attached that source to their respective living (or one deceased person) people, when that person is merged with the duplicates, duplicate sources will be found on the merged person page and will have to be manually detached making sure that notes are kept in the remaining source.
I have actually seen a source attached to multiple deceased people at a time too (especially when the source is not correct for one of the people).
There's a lot to think about if FamilySearch wants to make this better. But I think at the least, there should be some indicator on a person's profile page saying that there are duplicate indexed sources.
0 -
Jordi
Thank you for that clarification. However, unless via the Source Box, it is not possible to add an indexed record directly to more than one deceased person, as (in the source linker process) it has to be removed from the existing ID to which it is attached before adding to the "correct" ID.
0 -
Paul, Jordi's observation is really interesting if he has actually seen that (and I'm sure that he has). Yes, the way the source linker works prevents an index source from being attached to multiple PIDs. But it IS possible by copying it through the source box to get an index source attached to multiple different PIDs.
And although it is not visible to everyone, the same index source can be attached to different living PIDs.
However, It would now appear to me that by changing all of these living PIDs (that already have the same index source attached to them) to deceased, when you merge them all together you end up accumulating all of those duplicate SOURCEs into a single PID.
The merge tool obviously doesn't prevent this.
0 -
see this source for the wife was attached to both the correct person and her sister.
0 -
It looks like you already corrected the fact that the earlier born sister died the same year that she was born and therefor could not have been a wife. The link from that source to the infant who died should be removed.
This could also appear when there are two siblings that need to be merged.
0 -
The iOS Family Tree App has a different source linker.
It does allow an indexed source to be attached to more than one ID.
0
