Should I or even can I restore the Church created ID# that I merged with the one I created?
I questioned but was told it didn't matter which record I kept.
I now understand I should have kept the record from the church where the ID number starts with a KW instead of keeping the record I had created for my husband. Should I try to restore this and remerge under the church created record? Several things have been changed since.
Merged Richard W Rich KWHW-X5K with LX81-4CZ
Thank you! Shelba Rich
Best Answers
-
Hello @Shelba Rich
It does not matter which ID is kept in a merge. An ID does not provide information about the person or the source of the information.
IDs are automatically assigned when a new record is created. The records which start with KW are just those records which were added to FamilySearch in one particular time/batch. A whole heap of "membership" records were entered into FamilySearch at the same time so those IDs started with the same two letters . . . KW.
You don't need to restore and remerge.
regards
2 -
Shelba
I am just another 'lowly' User/Patron ...
[ And, I happen to be a Member of the Church ... ]
Just in passing ...
I am sorry; but, I have to disagree, with that 'Comment', by 'Kerrebee' ...
UNLESS, the 'FamilySearch Person Identifier' (PID), of an individual/person (ie. in this case, one who is/was a Member of the Church), actually "Predates" (ie, "Created" BEFORE - I think 2014), the PID created (or, associated ), by the "System", from their "Membership Record", in the Church; THEN, the PID, created, by "System", from their "Membership Record", in the Church, SHOULD ALWAYS be RETAINED; as, the "Surviving" PID, in ANY "Merge'/"Combine".
As, more often that NOT, 'FamilySearch' "Support", is USUALLY required, to do remedial work, behind the scenes, to Correct/Fix things, in such "Merges"/"Combines", that have been "Messed" up (eg. a PRIME example; being, "Temple" Work).
Of course, one can say, that it does not matter; and, technically, they may be correct, in that any problems/issues caused, can be remedially corrected/fixed, behind the scenes, by 'FamilySearch' "Support"; but, such, should NOT be required.
I for one, WANT My PID, that was created (or, associated), by the "System", from My "Membership Record", in the Church, to BE the "Surviving" PID, is ALL cases, for future "Merges"/"Combines", when I die.
I DO NOT want, another "Duplicate" PID, of (the former, "Living") ME, from ANOTHER User's/Patron's 'FamilySearch' Account, to be ALLOWED, to be the "Surviving" PID, in ANY future "Merges"/"Combines", when I die.
I know, for a fact, that there are a number of "Duplicates", of the "Living" ME. Residing, in the "Private Spaces", of the 'FamilySearch' Accounts, of OTHER "Living" Users/Patrons. At least, one of each, for my Wife and each of our Children, not to mention those for our, "Immediate"; and, "Extended", Family members and relatives.
I have been a vocal advocate, of 'FamilySearch' (ie. the "System"), REQUIRING; and, ONLY allowing, the PID, that was created (or, associated), by the "System", from an individual's/person's "Membership Record", in the Church, to BE the "Surviving" PID, is ALL cases, for future "Merges"/"Combines", when that individual/person dies.
Unfortunately ...
Such seems to be, 'falling on deaf ears' ...
So ...
That Said ...
Your Question: Should I or even can I restore the Church created ID# that I merged with the one I created?
Short Answer: YES; Yes; yes ...
When I come across them, I ALWAYS "Restore", ANY PID, of an individual/person, that was "Deleted" (ie. "Archived") through a "Merge"/"Combine"; where, that PID was either, an ORIGINAL (Record) individual/person, from "New.FamilySearch" (or, before); OR, was created (or, associated), by the "System", from their "Membership Record", in the Church; and, then, I "Re-Merge"/Re-Combine" those individuals/persons; so that, that "Restored" PID, is the "Surviving" (Record) individual/person, in each and very case.
I hope, that this may help/assist; and, I hope, that this may also provide, some additional, insight; and, perspective.
Brett
1
Answers
-
Hello dear @Brett .
I am interested in your statement "I for one, WANT My PID, that was created (or, associated), by the "System", from My "Membership Record", in the Church, to BE the "Surviving" PID, is ALL cases, for future "Merges"/"Combines", when I die."
Can I humbly ask why that is important to you? I would like to understand your perspective.
The IDs in FamilySearch are not formal church membership records. Records which are created in FamilySearch today/tomorrow/last week for church members do not start with KW. My ID does not start with KW - when I die, how will my children know which ID is the important one which should be kept?
Just interested.
0 -
-
I have family members who are not members of the Church and they have IDs that start with KW. Like @Kerrebee noted above, that was just the batch they were assigned when they were brought over from the old nFS system in the beginning of the seeding of the FamilySearch Family Tree. My children are members and their IDs start with KN and LH.
0 -
@Shelba Rich , my understanding is that the PID xxxx-xxx is really just a number in base 30. Unlike the numbers we usually use in base 10 with digits 0 1 2 3 4 5 6 7 8 9, base 30 has thirty digits, 0-9 plus 26 letters from the alphabet minus 6 vowels. So no particular meaning other than just a unique number assigned to a given profile.
2 -
I used to often find a remark appeared when I was about to merge two IDs - explaining they could only be merged in one way. Perhaps that is still the case and it's just that I haven't experienced this lately.
I guess the engineers could apply some code that differentiated between the "Church ID" and those created by Family Tree users. If not, I doubt if most users (especially those who are not "LDS") are going to trouble themselves over which way around they should be carrying out their merges.
(Sorry if I have misunderstood and this is just a "Church account" issue and doesn't apply to our work in public accounts.)
0 -
From my understanding, the more complete PID (number of sources, etc) should survive the merge. The software typically sets it up that way. There may be on occasion where each PID has an equal completeness rating (if that is what it is called) and the user has to decide which one to retain as the survivor in the merge.
1 -
Perhaps that is still the case and it's just that I haven't experienced this lately.
That is still the case. I experienced it several times today.
0
