1) On It's Really Not That Easy! (posted 28 August 2013):
a) Chris said: "The origin of Thomas Trowbridge of Dorchester & New Haven, as being from Taunton, Somerset, England is very clear. The Trowbridge Genealogy, shown in the episode, cites many original documents verbatim in the text, including on pages 46-47, portions of New Haven Land Records, volume 1, page 202 which state -
“ '… I Thomas Trowbridge of Taunton in ye County of Somerset, Gen. doe hereby make ordaine, constitute and depute and in my place and stead put my three sons Thomas Trowbridge and William Trowbridge of Newhaven and James Trowbridge of Dorchester in ye Bay in New England in ye ports of America beyond ye seas …'
"You can see the Trowbridge genealogy in its entirety at http://books.google.com/books?id=VWEbAQAAMAAJ&printsec=frontcover&dq=Thomas+Trowbridge+Genealogy&hl=en&sa=X&ei=5tEpUrvBB9e44APs_4DgDQ&ved=0CC0Q6AEwAA#v=onepage&q&f=false
"Other articles that detail the Trowbridge ancestry in England in considerable detail with documentation in include 'The Trowbridge Ancestry in England,' prepared for Francis Bacon Trowbridge [author of the above Trowbridge genealogy] by Donald Lines Jacobus, published in The American Genealogist, 71 (1942): 129-37; and Charles Fitch-Northen, 'The Trowbridge Ancestry,' The Genealogist, 9 (1988): 3-39."
"If you have not checked for details in the Warrant and Patent Registers, or looked at the copy of the original Survey (date of survey is part of the story), you can find them from the PA State Archives Land Office records gateway, here:
"Sometimes there are little details about someone's not having fulfilled some part of the land procedures in the registers, and occasionally the Surveyor also comments."
"I almost always use exact match so it keeps more of the unwanted search people out of the results. This means fewer people to scroll through and faster easier searching at least for me."
"The Dunham entries I wanted to work on I could not because they were IOUS (Individuals of Unusual Size) -- all of them. Guys with different names were smashed together as one person (when they were clearly not the same guy) and at the same time married to the same woman multiple times (when they should have been merged). Add to that the same kids multiple times and then multiple parents.
"And different people are editing them each thinking the guy is someone else. It is a mess.
"Yes, it is a nice thought/plan for 'one tree' but there is no good way to un-knot the spaghetti even with scissors. I'm in the process of submitting unmerge information to FamilySearch for them to do in newFamilySearch but it takes a couple days just color-coding person identifiers for just one Dunham guy and then writing it out who is really who. And I still don't know if they'll do the correction. All I wanted to do was source some information on my guys so the correct info was out there, but it is taking longer to get it cleaned up than it would to do the sourcing.
"I thought I was alone in this problem. It sounds like you got a case of it too."
2. Titles, like Governor, should be entered as a prefix, not as a suffix.
3. Christian names and surnames should be entered in standard upper and lower case format, e.g. Thomas Dudley, not Thomas DUDLEY
or THOMAS DUDLEY.
I am not saying the above rules are right or wrong. I just believe we need some rules."
"Some of my ancestors have more than 100 duplicates in FS-FT. How could one even select the least wrong version to start with, in less than a couple of hours (if the program were running a lot faster than usual)?
"Stuff that was extracted from actual records and put in IGI years ago appears now in FS-FT stripped of any identifying information as to source.
"In my forays I've found that as 'sources' and reasons for presenting some data, people are giving internet trees, message board posts and 'from GEDCOM.'
"And some entity identified only as 'FamilySearch' keeps adding wrong dates, spouse(s) and as many as several sets of wrong parents to individuals I look at occasionally because they are subjects of Widely Held Mistaken Beliefs in myriad publications and trees.
"In addition to those problems, given the hodgepodge of database sources, place-name problems, cultural/social biases and rather odd programming bugs, it's hard to see this as a really viable vehicle for genealogical accuracy."
"Left-click on the link (you can not open it in a separate tab or window in order to save it--another annoying feature) and an article with numerous links will open. I can not give you a URL because it does not have a separate URL from this 'product support' section. I do not know if this is a version of the Knowledge Document referred to in the manual, but it seems to cover the merging problem instances.
"Regarding the IOUS merging issues, so common among New England ancestors, these will disappear when FS-FamilyTree no longer synchronizes with the new.FamilySearch database. This is promised by early in 2014, when new.FamilySearch will become read-only and will be kept in existence for some unstated time period.
"There has been a delay in separating the two because the FS-FT program can not directly 'read' the material in new.FamilySearch, and there has been a major problem with transferring LDS Ordinance data to FT from n.FS and with developing the subroutine in FS-FT for handling LDS Ordinances.
"There will still be data-management problems with the IOUS individuals because the person-page will not display more than 100 versions of spouses, parents, etc. Only in a general tree search can you determine how many versions there might be for an individual and for each spouse. But such a search will not tell you how many permutations and combinations there may be."
"There is a message board for discussion of FamilySearch site issues, including FS-Family Tree:
"It has no topical subdivisions, and you can not sort posts by subject, but you can use the rather primitive keyword search at upper right to determine if your question or problem may already have been addressed there. Most problems that users have encountered have been discussed, some at great length."