TMG-L Archives
Archiver > TMG > 2003-06 > 1054650974
From: Terry Reigel <>
Subject: Re: [TMG] Copying Master Lists and Custom settings.
Date: Tue, 3 Jun 2003 10:36:14 -0400
In-Reply-To: <1c7.a7bf8f8.2c0c6ccf@aol.com>
On Mon, 2 Jun 2003 05:03:11 EDT, wrote:
>I am grateful to Terry for answering this query. I would
>also like publicly to salute Terry's site and his
>introduction for new users.
You're welcome. And thanks for the kind words.
>The first step is to transfer settings to a new data set.
>However, TMG 5 does not make a distinction between source
>settings (types and output styles) and sources specific to
>a data set (one family). The add data set screen will not
>allow one to carry across source types (for instance
>Caroline's UK sources) without also taking across the
>Master list of sources.
>It is an important step therefore to delete the master
>list of sources from the new data set, and as far as I can
>see, this can only be done individually.
The current method of copying all the source data to a new dataset
has existed for some time -- at least it was that way in TMG4. I
don't recall ever seeing this discussed before, but I agree with you
that it seems less than useful. I've never been able to figure out
why one would want to copy the MSL, but can see wanting to copy the
source types, as you want to do. I would think it more useful if the
MSL were a separate item from the Source Types and Source Elements.
>This brings me to deletions in general. During my struggle
>to merge, I found myself at one stage not only with
>duplicate sources but with individuals also entered three
>times. Although I could do a multiple selection for
>deletion, (i.e. by record number, the whole group latest
>merged) I was unable to delete the duplicates. Even the
>deletion of one individual was rejected by TMG because of
>existing links. While this may be a necessary safeguard
>against accidental deletion, it forced me to delete the
>whole project and start again from scratch (back up). How
>can one delete groups of individuals in TMG? And what is
>the point of being able to select for mass deletion, if
>one is not permitted to execute the command?
Well, you can delete a group at one time if you have previously
removed all the links of each member of the group (at least I expect
you can -- I haven't tried it). But that's a nasty task. I expect it
is intended as a safeguard, as you say. But some way around it would
be helpful, I think. In the past, I've seen the suggestion that
instead of deleting a group -- copy everyone else to a new dataset. I
think something more direct would be helpful.
>The problem of duplication arose because as a newcomer, I
>had difficulty in distinguishing between the merging of
>projects and the merging of data sets. This was discussed
>on the list yesterday — but as far as I can see is not
>clearly explained in the user's book. One might have
>expected merging of projects to merge some settings also.
>What settings are transferred at this stage?
Since the datasets within a project are highly independent, they are
not generally impacted by a merging of projects. So far as I know the
only setting that are potentially impacted are those under Current
Project Options in Preferences -- these are the Project level
preferences. Of these, the one that I see as of the most potential
impact to the datasets is the one for Source Categories -- Lackey,
Mills, or Custom -- if they are not already set the same for both
projects.
>Can one
>assume that a merge of two data sets will duplicate master
>sources and individuals but will not duplicate source
>types?
Yes, except that if individual source types in the two datasets are
in any way different, both types appear in the merged dataset. For
example, if you have customized the Baptismal Record source type in
one dataset and not the other, in the merged dataset you will see
both a Baptismal Record and Baptismal Record1 source type.
>I also misinterpreted the on screen instructions on
>merging data sets. When asked which set I wished to remain
>untouched, I selected the one I wanted to keep. Whereas
>one should select the one which is merely the vehicle
>carrying the settings.
I agree the wording of that screen is confusing. I have to read it
several times every time I use it to get it right.
>Having made the wrong choice, I
>then chose the other option. One should be warned that
>changing one's mind at this point will merge two copies of
> one's original dataset.
I don't know that I agree with this one -- you're asking that the
program keep track of your previous merges and figure out how they
relate to one another. Given an almost endless set of possible
actions a user might take, with any number of different datasets and
perhaps major modifications to each of them in between merges, I
don't see how it could do that.
>My current position is that I would like to use TMG
>because of the research advantages in its person view and
>alternate Birth and name tags. But I am struggling with
>TMG problems with handling custom source types, source
>text, and custom source type reports.
Are there issues we might be able to help with? You have previously
posted some of them, and we've tried to help, but it sounds like you
may have others.
Terry
This thread: