GENBOX-L ArchivesArchiver > GENBOX > 2003-08 > 1060919072
From: "William T. Flight" <>
Subject: Re: [GENBOX] Merging Databases (wiping out places: caution)
Date: Thu, 14 Aug 2003 23:44:32 -0400
References: <FFEBLNNBNENFDKOPJEBPAECPDOAA.email@example.com> <001701c362d5$8cd596f0$0100a8c0@beth>
A word of caution about wiping out the default set of place names.
Unlike nearly every other genealogy program, places in Genbox are not a
simple "flat" list. They form a hierarchy, with lower place levels linking
to higher place levels, leading up to nations. This organization has several
advantages--for speeding data entry, advanced query capabilites, applying
filters, formatting options on reports, and more.
When importing data, Genbox attempts to link new place names into the set of
place names already known. It accomplishes this primarily by working
top-down, starting with the nations, states, and other names that it
recognizes, linking new place names beneath. It attempts to identify the
place levels of each comma-separated place name part (local site, city,
township, county, state, nation).
An essential part of this operation is the database itself: it uses the
stored place names as the base on which to build. There is no storage of
place names other than what is in the database. When all of the place names
have been removed, Genbox won't know Utah from France. The place hierarchy
that results from a GEDCOM import will likely by poorly organized: some
states may become countries or counties, local sites might be labeled as
cities, there may be a nation "United States" with 500 links below and
another nation "USA" with 700 links below, including both states "Illinois"
and "IL" in each, with their own lower levels.
When entering places manually, you can use the Magnify Place Dialog to
position each part at the correct level. If you plan to enter all of your
data that way, I don't see a problem, other than it will be tedious. <g> My
concern is rather that a GEDCOM import with an empty place database will not
give you satisfactory results. (Of course, if your GEDCOM has mostly Asian
or African place names, the default hierarchy won't be much help anyway.)
My recommendation is to keep the default place names--at least the nation
and state levels. If you find their presence in your database distracting,
we can probably think of more creative ways to "hide" them from view.
Perhaps some new filtering capabilities will do the trick...
William T. Flight
----- Original Message -----
From: "Beth Gay" <>
Sent: Thursday, August 14, 2003 10:32 PM
Subject: Re: [GENBOX] Merging Databases
> But back to what I am trying to do. I created a new database without the
> places so I wanted to open that database and my initial Coker database and
> place the names, sources, etc. in the new database but not the places and
> reenter the places. I am not fond of typing so I thought that I could drag
> and drop but I guess cut and paste will work just as well. There may be
> problems with this idea, so let me know. I could work on my places in my
> present database and export the file to a GB-file and rid myself of the
> in the places as Wim suggested.
|Re: [GENBOX] Merging Databases (wiping out places: caution) by "William T. Flight" <>|