Search for content in message boards

Family Tree Re-Organization Suggestions

Family Tree Re-Organization Suggestions

Posted: 9 Dec 2012 2:25AM GMT
Classification: Query
Surnames: Thames
Please forgive the long-winded post, but any help or suggestions would be greatly appreciated.

I recently took over a genealogy website that was originally started under the premise that three phonetically similar surnames (Thames-Tims-Timms) were related. Over the last few years, DNA testing has ruled this out, so there's no longer any reason for these three names to be linked together on the website. I'm playing with the idea of creating three separate sites under the main domain that link to the separate surnames.

All of the submitted lineage data was put into the same tree (leaving numerous open branches). I took the single gedcom and imported into FTM, but now I'm stuck on the best way to re-organize this into three separate trees?

Can anyone offer me any suggestions on the most efficient way to re-organize all of this information?


Dustin

Re: Family Tree Re-Organization Suggestions

Posted: 12 Dec 2012 3:58AM GMT
Classification: Query
No good answer here, but a similar question. I have a very large database where most of my maternal grandparents' families came through Pennsylvania, with much crossing of genealogical lines. Any suggestions on how to split my tree up in a way that will keep information from being duplicated? Thanks.

Re: Family Tree Re-Organization Suggestions

Posted: 13 Dec 2012 12:27AM GMT
Classification: Query
I am in the opposite side of the situation. I have about 20 trees that I started over the years and have been gradually merging them into a single large tree with several branches. I got tired of discovering the same person in two or more separate trees and realizing that I had already updated the person in one tree and was duplicating my research.

When I first started merging the trees, I figured that I would find a few duplicate individuals in each merge session. I ended up finding over 3000 duplicate individuals when all was said and done.

If you have a stable database that can handle the large tree, my opinion is to keep them in the same tree. You can always set up your filters to separate the website into the three branches, but with one single database file.
per page

Find a board about a specific topic

  • Visit our other sites:

© 1997-2014 Ancestry.com | Corporate Information | New Privacy | Terms and Conditions