My entire project for my family is becoming unimaginable. I therefore consider the pros and cons of splitting up a branch for each of my grandparents. However, overlaps occur, so if you think it's a good idea, how do you handle these coincidences? — Regards Kurt Hansen

Kurt, Why is your site unmanageable? Splitting your project into pieces will increase some of the maintenance (source templates, event definitions), and if the same person appears in more than one line, you'll have that duplication as well. I recommend that you stick with one project and solve whatever issue is making the site unmanageable. John -----Original Message----- From: Morsø Anecentral <[email protected]> My entire project for my family is becoming unimaginable. I therefore consider the pros and cons of splitting up a branch for each of my grandparents. However, overlaps occur, so if you think it's a good idea, how do you handle these coincidences?

At 3/10/2018 04:54, Morsø Anecentral wrote >My entire project for my family is becoming >unimaginable. I therefore consider the pros and >cons of splitting up a branch for each of my >grandparents. However, overlaps occur, so if you >think it's a good idea, how do you handle these coincidences? I have a single project with a single data set for some 62, 000 persons. The great majority of these persons is in a single "tree: (all related in some way). A few hundred other persons can be classed as being in about 60 others trees of from 1 (mostly) to 30 persons. These others are unrelated persons to the "main tree". Many are just witnesses (ministers, friends and best men/maid(en) of honor at marriages, etc.). A few of these larger other trees are families that I think must be related to persons in the 'main tree'. I enter them with the intention of making the connection when I find out how they are related. I prefer a single data set project because I don't have to switch to another project (or data set) to work with some other family group which is quite often. A single data set also means that I don't have duplicate people that need updating. This is the main reason for a database -- you enter something once and then forget it. One of the reasons that my data set is so large is that I include a large number of all descendants of my ancestors. This gives me all my cousins to many degrees of cousinship. The main reason that I do this is to resolve brick walls by "going in the back way" to find the right person. Another reason is that my wife's genealogy is also in my main project. At one time, I considered splitting her data and my data, but there was too much duplication across the families. Most of these are as witnesses although there are others. For example, my 2GGM is the aunt of my wife's 2C2R and the 2C2R was named for my 2GGM. With both our families having roots in the same place for over 250 years, it is not unusual to find family connections across what would be almost unrelated families. The problem is that since we are all related around here, we can't talk about someone as they are related. <g> Now, having said all this, I must say that in addition to the one project, at any one time , I have about a dozen other projects or data sets (mostly 100 persons or less each) . These are mainly created for exchange with other researchers or created from data sent by other researchers. This last is to review the sent data to ensure that these are actually "my" people and to verify the data in comparison with what I already have. Thus, I resolve any conflicts with new data and my own data before any new data is added to my main project. Most of these small projects/data sets are then deleted (though I may make a backup for my archives). In addition, I often have a few other projects -- mostly fairly small. These are for clients and rarely have any connection to anyone in my main project. Even when I have a client having a connection to someone in my main project, I like to keep the client project separate until I finish that project. Then, I will often merge than client project into my main project, make a backup of the client project and then delete the client project. In this way, I keep just the one main project and the few smaller projects that are of current interests. The rest is deleted and not ever a confusion factor. One last thought. There are a number of TMG users who have much larger projects than I -- many in the range of 200,000 persons. At least one has over 450,000 persons. I know some of this project duplicates part of my main project, but do not know the composition of the rest of his project. That part of my project comes close to being a one-name study with the hope of eventually getting back to it Irish/Scottish roots. Interestingly, we have never really compared what we each have although we have shared data at times. Just some of my thoughts - Lee