TMG-L Archives

Archiver > TMG > 2005-01 > 1106242809


From: Lee Hoffman <>
Subject: Re: Wishlist (was RE: [TMG] Individual Narrative issues)
Date: Thu, 20 Jan 2005 12:42:37 -0500
References: <4.2.0.58.20050118162630.05113b00@pop.well.com><200511910209.927004@Terry3><6.2.0.14.0.20050120083121.02ee4510@pop.compuserve.com>
In-Reply-To: <6.2.0.14.0.20050120083121.02ee4510@pop.compuserve.com>


Karla Huebner wrote:
>I'd like for there to be an option to share Tag Types, Source Types,
>Styles, and what not among datasets or even among projects. While I can
>imagine situations where one would want these to be separate, it seems to
>me that more often one would want to use the same templates, so to speak.
>I've got three projects, two of which have several datasets each, but
>while only two datasets really get much use (the other datasets are
>imported material that might eventually prove useful), I'd like to have
>the same tags and such available for everything. What if I had finally
>gotten my Source Types set up to my satisfaction (that'll be the
>day...)--I'd certainly want these miracle Source Types available for
>everything. As for Tag types, it's very easy to ignore whatever isn't
>useful for a particular dataset/project.
>
>If I were a professional genealogist with many projects, I'd feel
>especially strongly about wanting to have my working tools available while
>keeping the projects separate.

When you create a new data set, you have to option of including any or all
of the following from one data set in the new data set:
-- Master Source List, categories, templates, and elements.
-- Master Repository List
-- Tag Type List, global sentence structures, and Roles.
-- Master Place List.
-- Flags
-- Name and Place Styles.

Thus you can include any or all of these as desired. You can then copy the
current project (with this new data set) to another new project (e.g.,
different project name) and delete all but the new data set. This new
project with just the one data set can them be merged with other projects
and then data sets can be merged with the data sets of that project to
carry the above data into other data sets.

Like Terry, I recommend that all data be kept in a single data set in a
single project. The more I do that with my own data, the more I like it.

On the other hand, I do have a few projects of clients that I keep separate
(although most of these do eventually wind up being incorporated in my main
data set). My main reason for keeping them separate (for a while) is that
I only want that specific data for reports. In a few cases, the data in
the clients project as very closely intertwined with other data that I have
in my main project and data set. But I usually do not want that data to
show on reports going to the client -- at least not right away.

So when I create a new data set, I can start with the basic data from my
main data set including all the customized Source Types, Tag Types,
Sentences, and Roles, Name and Place Styles, and Flags.


Lee Hoffman/KY
TMG Tips: <http://www.tmgtips.com>;
My website: <http://www.tmgtips.com/lhoffman>;
A user of the best genealogy program, The Master Genealogist (TMG)


This thread: