tag:blogger.com,1999:blog-3793782800729950147.post1419165592092026502..comments2024-03-26T21:29:07.190-07:00Comments on Rejoice, and be exceeding glad...: Finding Francis -- Part TwoJames Tannerhttp://www.blogger.com/profile/02989059644120454647noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-3793782800729950147.post-32261316928074145612017-03-31T16:42:06.479-07:002017-03-31T16:42:06.479-07:00That might happen with some, but we will never giv...That might happen with some, but we will never give up trying and teaching. James Tannerhttps://www.blogger.com/profile/02989059644120454647noreply@blogger.comtag:blogger.com,1999:blog-3793782800729950147.post-65099656373076874202017-03-31T14:23:50.423-07:002017-03-31T14:23:50.423-07:00"There are no internal safeguards yet establi..."There are no internal safeguards yet established to assure that an addition to the Family Tree is supported by sources." It seems to me this is a huge issue that FamilySearch has simply turned a deaf ear to. If you look at the posts on this subject on Get Satisfaction, FS's response is always that "Community is the answer" and it's up to other users to patrol the tree and fix all the irresponsible changes. However, this approach is simply naive. Personally, I'm getting a bit tired of users who continually replace thoroughly sourced and documented data with the same old garbage that has been kicking around on Ancestral File for 50 years. Or, who blindly transfer data from their Ancestry Tree without even checking to see if the data is Family Tree might actually be correct. I have had experiences similar to yours where attempts to reason with users who are putting in erroneous data simply leads to an acrimonious email exchange. FS really needs to address this issue and implement some safeguards. If they continue to ignore this issue I think the seasoned genealogists are simply doing to get tired of fighting the battle and abandon Family Tree. Ted Johnsonhttps://www.blogger.com/profile/09810743230086342147noreply@blogger.com