After reading, all I can think about is how baffled the Nazarene would have been if someone had explained all of this to him on the shores of Galilee.
And Jesus spoke to the multitudes, saying: "My beloved brethren, harken to MySQL and CUDA programming for the redemption of the dead. Beware merges and follow best practice with Common Table Expression (CTE) or a VIEW that limits the row set in the target, lest your brother or sister be left unbaptized and damned. And God help you if ChatGPT incorrectly renames your non-Mormon great-great-great-grandfather before he is baptized."Tangata Nevawhatever wrote:For Frenchy, I did create a record using the name and vitals from Find-a-Grave. I often do this as a tool to help locate an extant record when the search fails to find it because the information I have is incomplete or not quite right (in this case Frenchy was a nickname). As a result, as I hoped I would, I found an earlier record (using his real name Marceau). I then merged my record into that earlier record.
One of the side activities that all members can do is correct and standardize records. It doesn’t have to be records for their relatives. There is even a tool (The New Volunteer Opportunities on the FamilySearch website landing page) for members to assist with standardizing place names. But in my case, it is even more appropriate because Wanda IS a relative and therefore Frenchy is an in-law relative.
For Wanda, I found her record, and connected her to Marceau (i.e., Frenchy). This is also an appropriate action to take (even if Wanda was not my relative).
Once I knew that Wanda was a relative, I also added some details and sources to their records.
The Family History Department is even starting to use A.I. now to help with these kinds of record improvements, because the missionaries and members can not keep up with it.