I run a large one-name study which is currently predominately UK based. The odd entries in there for the USA are were someone has migrated in recent years. The current database contains in excess of 26,000 people I have been working separately on a new set of data in Family Historian, I find it much easier to add people quickly there as you can use drag and drop on a chart to add people. This file contains the over 2,500 people descended from the earliest Halstead that arrived in the US in the 1640's. I want to import this file ultimately into the main TMG database but thought that it would be easier to import it into a separate TMG project first. The problem then is how to compare the two to see where the duplicates might be. I then realised that I can add a separate dataset into the existing project and I am struggling to understand exactly how it works. Can someone give me some simple pointers. If I have it as a separate dataset in the existing project can I easily import it into the master dataset? Regards John Hanson Researcher, The Halsted Trust Website - www.halstedresearch.org.uk

At 8/15/2015 04:31, John Hanson wrote: >I run a large one-name study which is currently predominately UK based. The >odd entries in there for the USA are were someone has migrated in recent >years. The current database contains in excess of 26,000 people > >I have been working separately on a new set of data in Family Historian, I >find it much easier to add people quickly there as you can use drag and drop >on a chart to add people. This file contains the over 2,500 people descended >from the earliest Halstead that arrived in the US in the 1640's. > >I want to import this file ultimately into the main TMG database but thought >that it would be easier to import it into a separate TMG project first. The >problem then is how to compare the two to see where the duplicates might be. >I then realised that I can add a separate dataset into the existing project >and I am struggling to understand exactly how it works. > >Can someone give me some simple pointers. > >If I have it as a separate dataset in the existing project can I easily >import it into the master dataset? Any import into TMG must be into a new data set. That new data set could be in an existing project _or_ in a new project. Since a data sets in a project is completely separate from any other data set in that project, it really makes no difference (except person preference) as to which way an import is done. With an import into an existing project, a step would be saved of merging project _if_ that is anticipated. The Data Set Manager of a project allows a data set to be enabled or disabled. If a data set is disabled, all data (persons, sources, repositories, exhibits, etc.) in that data set are effectively hidden and cannot be seen or manipulated in any way until such time as that data set is enabled. With this in mind, if I were planning to import data into TMG with the aim of eventually merging that data into an existing data set, I would import into the project containing the proposed target data set. I could then enable/disable the data sets that are/are not of interest as I had need _or_ I could simply have them all enabled to see all the data. I do this often with client data sets in my main project because if is not unusual for me to have someone in my main data set that is also in the client data set. I can then easily copy from one data set to the other as I have need. (I can also _move_ person(s) from one data set to the other - but I _usually_ prefer copying as that is less hazardous to the original data set). TMG Help has good discussions of both copying & moving persons between data sets. Having said all this, it really comes down to personal preference. Importing into an existing project may save a few keystrokes (the later merging of projects) but that really is not that big a deal if one feels safer. Having multiple projects does mean that the data from one data set (in say project A) cannot be easily compared with data from a data set in project B. Of course, one can do this by having two instances of TMG open, so this isn;t really a big disadvantage either. So, really, flip a coin and tip it toward the way you feel more compfortable. Lee

The project vs dataset question reminds me of a question of my own. My main project (which has several data sets) has my own family. However, over the years I've also created a project for one of my friends and a project that contains many of my friends, with their birthdays and miscellaneous data. I've kept the friend projects separate because I've never intended to share them with family, whereas I occasionally do send my brother a backup file of the family project. Can I add the friend projects to my family project (simplifying sourcing) but keep them out of backups of the family dataset(s)? Karla On Sat, Aug 15, 2015 at 10:55 AM, Lee Hoffman/KY via <tmg@rootsweb.com> wrote: > At 8/15/2015 04:31, John Hanson wrote: > > > > > >If I have it as a separate dataset in the existing project can I easily > >import it into the master dataset? > > Any import into TMG must be into a new data set. That new data set > could be in an existing project _or_ in a new project. Since a data > sets in a project is completely separate from any other data set in > that project, it really makes no difference (except person > preference) as to which way an import is done. > > [...] > With this in mind, if I were planning to import data into TMG with > the aim of eventually merging that data into an existing data set, I > would import into the project containing the proposed target data > set. I could then enable/disable the data sets that are/are not of > interest as I had need _or_ I could simply have them all enabled to > see all the data. I do this often with client data sets in my main > project because if is not unusual for me to have someone in my main > data set that is also in the client data set. I can then easily copy > from one data set to the other as I have need. (I can also _move_ > person(s) from one data set to the other - but I _usually_ prefer > copying as that is less hazardous to the original data set). TMG > Help has good discussions of both copying & moving persons between data > sets. > > >

Lee Thanks you for thoughts. I must admit that having been "shown" TMG by someone and it was more Second Site that I wanted, I learnt by their mistakes. I should have remembered my own early computing days and gone back to basics and learnt it myself from scratch - but then most of us these days want to hit the road running and TMG isn't that easy! Two datasets in the same project does seem the more logical and the reason for importing it into a separate dataset of course is to make it easier to tidy it up first. Now to fine an easy day to find the people that appear in both sets! Regards John Hanson Researcher, The Halsted Trust Website - www.halstedresearch.org.uk -----Original Message----- From: Lee Hoffman/KY [mailto:azchief@bellsouth.net] Sent: 15 August 2015 18:56 To: John Hanson; tmg@rootsweb.com Subject: Re: [TMG] New project or new dataset At 8/15/2015 04:31, John Hanson wrote: >I run a large one-name study which is currently predominately UK based. >The odd entries in there for the USA are were someone has migrated in >recent years. The current database contains in excess of 26,000 people > >I have been working separately on a new set of data in Family >Historian, I find it much easier to add people quickly there as you can >use drag and drop on a chart to add people. This file contains the over >2,500 people descended from the earliest Halstead that arrived in the US in the 1640's. > >I want to import this file ultimately into the main TMG database but >thought that it would be easier to import it into a separate TMG >project first. The problem then is how to compare the two to see where the duplicates might be. >I then realised that I can add a separate dataset into the existing >project and I am struggling to understand exactly how it works. > >Can someone give me some simple pointers. > >If I have it as a separate dataset in the existing project can I easily >import it into the master dataset? Any import into TMG must be into a new data set. That new data set could be in an existing project _or_ in a new project. Since a data sets in a project is completely separate from any other data set in that project, it really makes no difference (except person preference) as to which way an import is done. With an import into an existing project, a step would be saved of merging project _if_ that is anticipated. The Data Set Manager of a project allows a data set to be enabled or disabled. If a data set is disabled, all data (persons, sources, repositories, exhibits, etc.) in that data set are effectively hidden and cannot be seen or manipulated in any way until such time as that data set is enabled. With this in mind, if I were planning to import data into TMG with the aim of eventually merging that data into an existing data set, I would import into the project containing the proposed target data set. I could then enable/disable the data sets that are/are not of interest as I had need _or_ I could simply have them all enabled to see all the data. I do this often with client data sets in my main project because if is not unusual for me to have someone in my main data set that is also in the client data set. I can then easily copy from one data set to the other as I have need. (I can also _move_ person(s) from one data set to the other - but I _usually_ prefer copying as that is less hazardous to the original data set). TMG Help has good discussions of both copying & moving persons between data sets. Having said all this, it really comes down to personal preference. Importing into an existing project may save a few keystrokes (the later merging of projects) but that really is not that big a deal if one feels safer. Having multiple projects does mean that the data from one data set (in say project A) cannot be easily compared with data from a data set in project B. Of course, one can do this by having two instances of TMG open, so this isn;t really a big disadvantage either. So, really, flip a coin and tip it toward the way you feel more compfortable. Lee