Mic,
Quick, write a program that accepts census data and cemetery data, and
allows transferring the data to a genealogy program via gedcom format!
Or, write a program that will take the data from existing census and
cemetery programs and moves it to a genealogy program via the gedcom
procedure.
My wife has been asking for this for many years.
Legacy has great merging capabilities, and would allow matching and
merging people based on names, dates, places, etc. Using the same
"RIN" number in both programs is then a waste of time.
The program should also include fields like general notes and other
fields commonly used in genealogy programs. Even occupation, which is
sometimes given on headstones.
There have been cemetery and census programs, but I have never been
able to convince the author that the data should be transferable to a
genealogy program using the gedcom procedure.
One thing that would be very useful is a multiyear census form with an
added column on the far right that shows the calculated age for a
person on the census date. I add this as a check for verifying I have
the correct person and family. Some age variation is expected from
year to year for many reasons.
Jay
From: "Mic Zoodsma" <[EMAIL PROTECTED]>
Cut.
Re census data: Shosh, I have just started using Clooz (hoping to
avoid
developing my own Access2000 module!) to help organize all the
peripheral
information I gather. It allows me to import names exported from
Legacy;
conversely, I can also export names from Clooz and bring them into
Legacy if
they "prove" themselves. Even for those records that will never belong
as a
real part of my Legacy data, there is still an interest on my part in
correlating that data (neighbors, families that have migrated together
but
never married, etc.). My only complaint is that Clooz is limited re
census
data to the official census form fields for a particular year. What I
am
working on (and very close to completing) is making sure Clooze uses
the
same internal ID number as Legacy so that I can write reports (using
Access
or another ODBC query/reporting tool, such as EUREKA:Reporter, Crystal
Reports, etc.) that make sense of both sets of data. I could do the
same
with Excel templates (mentioned in another post on this topic), and
"read"
them with Access. The important thing, I feel, is making sure to
retain the
Legacy ID# (RIN). For easy of entry, Excel might even be easiest, and
certainly the most flexible (for those of us who always say "if
only....") -
I often copy tables of census search results (and other types of
data!)
directly from my browser to Excel very quickly and then manipulate it
slightly to fit Clooz format. I'm thinking the "Clooz format" step is
a bit
cumbersome, and since the Clooze datamodel is exceedingly simple
anyway, may
stick with the Excel data, which is quite easy to rearrange and format
for
use anywhere.
:-) I also work in IT (data warehousing), where the overriding
principle is
being able to tie information from multiple sources. Maybe together we
can
come up with a wonderful -and simple-new add-on that lets Legacy and
Clooze/external data users painlessly "tie" their data together????
To unsubscribe: http://www.legacyfamilytree.com/LegacyLists.asp
