male to male temple ordinance work
Harry Curser LLSZ-WHF, is sealed to Thomas Ward (MP3PT-KJP.
Their is only one record that says he is a girl, and when you look at original record 1911 Census. There has been a transcription error . as well as all the other part of the record that doesn't make sence
sharon tarr
Answers
-
This has got to be a record. Harry has 21 data error flags on him.
The place to start is the Change Log to determine what is going on here. First I have to stress one confusing aspect of the Change Log. If you see the red or blue person icon in front of a name and date, that simply is a banner notation of the current information on the person, not what the information was at the time of the Change Log entry.
Begin by going to the very start of the Change Log where you can see that "Harry" was originally Eliza:
The 2017 Sealing was for Thomas Ward and Eliza and that was who she was at that point. In 2018 someone determined that Eliza was Eliza Warrington and so changed her name to that and was able to put her with her parents (I'll leave it up to you to determine if that was correct). In May of this year, someone merged Eliza Warrington with an Eliza. (Again I'm not going to try to confirm if that was correct.)
Basically things look good as of May 2022 aside from confirming research. Then things to badly downhill. On June 15, 2022, these changes were made:
You can filter the Change Log to more easily see the effect of these changes.
For the name:
One thing you can see here is that the Reason Statement has nothing to do with the latest name change. It was the reason why Warrington was added as Eliza's last name.
For the birth date:
Again you can see that the reason statement was obviously not changed.
To have such blatantly ridiculous changes, I suspect the person who made them is very new to Family Tree and should be contacted to be gently and politely informed he kind of messed up or is one of the continued large group of people who do not realize that Family Tree is a single database we all work in together and thought he was just fooling around "in his own tree" without affecting anyone else.
In any event, this is very easy to fix. For the name and birth, go back to the filtered Change Log and click Restore on the next most recent value:
Then go and detach the source that was added on June 15, 2022, and remove the residence that was added that date:
That will get Eliza back to herself and probably eliminate all 21 data error in one blow.
This is a good example of how useful the Change Log is and how important being very familiar with how to read and use it is.
A great presentation by Kathryn Grant about the Change Log can be viewed here:
From 2021: https://www.youtube.com/watch?v=xvDgxulfroc
Updated or expanded version from this year (I haven't watched this one but all her presentations are outstanding): https://fh.lib.byu.edu/2022/05/27/more-mysteries-of-the-change-log-revealed-kathryn-grant-26-may-2022/
I have not made any corrections for you. That is your job.
2 -
@Norm Jones , it's to bad this discussion was moved to the Temple Category. I understand why but the real issue was not about the Temple but about a somewhat common FS issue, the hijacking of an individual and transforming them into another. This was a great example of that and @Gordon Collett's explanation of the change log and how to fix the problem I am sure would be of interest to many Family Tree users, not just to those who are members of the Church and concerned with Temple work.
1
