This special cousin painstakingly input all this info into a genealogy program, shared printouts with family. Eventually, she uploaded her family tree to a genealogy site, kindly making it public and allowing me to add to it on her behalf in the last few years.
Now I'm updating our joint research on in-laws (including her in-laws) to add documents and facts that have become available in recent years. It's a fun genealogical journey and I hope to turn up some paperwork that will help fill in a few blanks (maiden names, birth places, death places, etc.) Already I've corrected mistranscribed names and incorrect birth places, linking sources as evidence.*
I felt a bit sad that few of these in-laws (and their in-laws and FAN club) were already on public family trees--and when they were, they weren't shown accurately--so I'm fixing that to show my love for in-laws and to honor my cousin's research from back in the day 😃 By adding my cousin's in-laws as well as my own distant cousins and hubby's distant cousins plus their in-laws, I'm paying it forward in gratitude for those who began the research in the past.
*Linda, in her comment, notes that correcting inaccurate info online can be frustrating because folks can change things back or simply ignore evidence that is contrary to their trees. I totally agree--which is why I don't correct on FamilySearch but I do post accurate info and evidence on Ancestry, plus on Find a Grave, and I do share accurate info on WikiTree. Over the long term, I've seen some corrected info gradually percolating through the public family trees. 😀
I admire you for correcting online information, but I've found it's pretty much hopeless when others insist their info is correct (even in the face of primary evidence) and/or they simply change the details back to the incorrect version.
ReplyDeleteYou are so right...which is why I don't bother to correct on FamSearch but I do show correct info with sources on Ancestry and share correct info with citations on WikiTree, as well!
Delete