Log in

No account? Create an account
29 March 2006 @ 08:09 pm
I haven't written on my blog for several days. Been busy trying to buy a new house. I must be insane to want to move all my genealogy stuff! I've spent some time thinking about another type of move. Moving my genealogy database over to Family Tree.

After Beta 1, I knew I needed to do several things to my database. I have two need to-do items and one want to-do item for my databases.

1. Get some type of event dates on all my people
2. Give everyone a Custom ID.
3. Combine all my databases together

The first item, get some type of event date on all my people, is so people that are living in the 1500's will show up as dead and not listed as living and unavailable for others to see. In Family Tree it will look for a death date or that they lived over 110 years ago otherwise they are listed as living. Even if their father lived in the 1500's and their children died in the 1600's. They need to be determined deceased in order to be accessible for others to see and merge into. I have a good number of people in my database that have no dates. I have to look at a lot of census records really fast and start putting estimates on my people.

The second and third item on my to-do list are tied together. Family Tree will accept GEDCOMs and it's best to do it with the UID turned on in your program. That way if you want to update your GEDCOM it's a simple matter of running the GEDCOM over the top of the old one and the UID will make sure your not getting duplication. Neat feature but I don't think it will work with my current system of multiple databases. I have duplicate people listed in my different databases. It's a major project to merge my four databases together. I thought about doing this for Family Tree. If it goes by UIDs then which one will it use for the people I always have to merge together from the separate lines. I determined that it will be best to have all my databases combined together and then make one big GEDCOM of it and submit it to Family Tree.

This decision means I will loose my ability to keep track of who comes from what family line. That's where item number two comes in - give them a Custom ID. I mentioned in an earlier article that I was creating Custom ID's or as in Legacy called User IDs. My ID system is their relation code to me. So I am putting on my Harris line a code like H3C2R, meaning Harris third cousin twice removed. My method of madness is that I will be able to search on everyone that starts with an H in the User ID field, tag them and then export them into a GEDCOM when I only want to share that line with someone. I think it a brilliant plan. I'm not sure if other genealogy programs will let you do something like that or not. But I know it will work for me.

So as you can see I have a lot on my plate. At least I don't have to worry about sources in my note field like some people have to. Got that problem fixed along time ago. Now it's on to getting ready for two different kinds of moves.

See ya tomorrow, for tomorrow is always another genealogy day!

Renee Zamora

1. Legacy has a feature to indicate if an individual is living or deceased. This indicator will not work in Family Tree - you must have a date to have it calculate if they are deceased or not.

2. Legacy's "Advanced Tagging" feature will not capture separate family trees from your main line. That is why I am forced to "code" everyone in my separate databases so I can maintain the name study I am doing in each of them. Not everyone is linked together in my databases.

3. Family Tree has a GEDCOM size limit currently of 20 MBs approximately 100,000 names. If your combined databases would be larger than this you might want to keep them separate.
Current Mood: busybusy