Legacy Gedcoms are a superset of Ged 5.5. I did my testing almost 10 years ago and determined then that Legacy Geds were the way to go. I do not recall which specific features it adds, but there were some specific features added. BTW, you can export the tags, and TNG can display them, but I have not tried to tweak their use to make them meaningful so I know ignore them.
Media Preference is imported. A recent fix that a few of us Legacy users have insisted upon is that only the preferred media for the individual is now used on import as the default media for TNG.
There may be tags you do not wish to import. Most can be deleted in the Legacy export customization (see below), but others can be excluded in the TNG Custom Events admin tool. EG, there are some Legacy Source system tags that can only be excluded in the TNG Custom Events tool.
Some suggestions for Legacy Gedcom export customizations... WHEN EXPORTING A GEDCOM FOR TNG.... (A Gedcom for archive, I exclude nothing!)
1/ On the main Gedcom export page, check the option to convert formatting codes to HTML and to make web friendly spaces. The second is necessary if you want any note data with spacing to have the spacing retained.
2/ On customization page, you probably want to exclude several of the options, like To-Do. I do not export Addresses, LDS, Research notes (Those are notes not meant for publication.), medical notes (but I do export cause of death), and maybe a couple of other options that I decided I did not need to export. I also have a number of specific tags I have chosen not to export. (eg, Tags, _UID, etc.) After some experience., you will decide what works for you. You want to export Legacy's Q Dates as "Between... and... " dates for TNG, but when trying to archive your Legacy family file in Gedcom, you want to retain the Q Date.
3/ I now create all of my TNG databases using UTF-8 character set and export my Legacy Gedcoms with UTF-8. I do this because I had a file with a Lithuanian family and several of the characters in their names were not in the ASCII character set. Since then, I have had more issues like this. Further, UTF-8 is more or less the standard character set for most major applications; eg, WordPress. Darrin recently added on my prodding an improved install option to create UTF character set tables for TNG.
4/ Although TNG has ability to geocode locations, I do "all" my Geocoding in Legacy and upload that data to TNG. This gives me more control. I said "all" because Legacy does not export Geocoding attached to Media. In general, you going to have to setup all of your media in TNG *once* because most of the options are not part of Legacy. Subsequent, Gedcom uploads though will remember what you have already setup.
--> I have advised another new Legacy-TNG user to go slow on adding their media. Meaning, try the options until you get the upload to work like you want both initially and on subsequent uploads.
--> Also, do not forget to setup in TNG all of the cemeteries you wish to place headstones in ahead of time.
5/ The data model between TNG and Legacy is close, but there are differences. One that I came across that changed how I used Legacy was that TNG does not have the option to add media to Source citations. Such media just do not get imported. An example of this could be a citation for a census listing that logically you might wish to attach an image of the census. TNG cannot do that. You would have to attach it to the master source. or the event. But we will say in Legacy you have 1000 citations for the 1900 census, each with the census image, you can imagine what would happen if you cite that source... I attach the images (when I use them) to the census event.
The child status feature needs to be fixed by Legacy so that it can be imported.
I hope this message is helpful.
john.
At 03:39 PM 3/26/2015, Ward Walker wrote:
I am a recent TNG user. I have been using the GEDCOM 5.5.1 option for export from Legacy, because the TNG documentation implied that GEDCOM 5.5 was required.
Is the option to export for Legacy simply a superset of the 5.5.1 option? What would it give me that I donât already have? (The child/parent relationship is in both.) Might it also give me things that I donât actually want to see in the TNG representation? I can see at a glance that the Legacy option adds To-Do list items, Legacy tags and a flag for Preferred child or spouse. I imagine that TNG ignores these.
I agree that Child Status would be very good to add to TNG, and it is currently not in the 5.5.1 export option. There is also no place to edit this status in manually in TNG (other than using Notes or Events).
Ward
From: CE WOOD
Sent: Thursday, March 26, 2015 1:51 PM
To: [email protected]
Subject: RE: [LegacyUG] Issue with Gedcom Export of Child Status
The reason I asked is because Darrin advised me against using GEDCOM 5.5.1.
Perhaps the problem some experience comes from not using the Legacy GEDCOM, thinking it is for use with Legacy only.
CE
Date: Thu, 26 Mar 2015 00:16:18 -0400
To: [email protected]
From: [email protected]
Subject: RE: [LegacyUG] Issue with Gedcom Export of Child Status
CE,
The issue is not which version of Gedcom you use. However, when I export a Gedcom for import to TNG, I always use the Legacy style export as this exports all of the information and so I have only a small information lossage.
This Child Status feature is one of the most important pieces that is lost.
john.
At 09:56 PM 3/25/2015, CE WOOD wrote:
- What GEDCOM version do you use?
- CE
- From: [email protected]
- To: [email protected]
- Subject: RE: [LegacyUG] Issue with Gedcom Export of Child Status
- Date: Wed, 25 Mar 2015 18:05:02 -0700
- Hmmm. On my TNG website, the "child relationship" seems to show properly as the "Relationship" under a parent on a child's Personal Information page
- ...
- Donald Quigley
- Escondido, CA
- Quigley Doyle Family Tree
- http://www.donquigley.net
- -----Original Message-----
- From: John B. Lisle [mailto:[email protected]]
- Sent: Wednesday, March 25, 2015 1:49 PM
- To: [email protected]
- Subject: [LegacyUG] Issue with Gedcom Export of Child Status
- Hi,
- A user recently reported to me that Child Status attributes, such as Stillborn, Twin, Adopted, etc., were not being imported into his TNG web site from a Legacy Gedcom file.
- Analysis shows that Legacy is exporting the Child Status in Gedcom, and can import those Legacy Gedcoms properly back into in Legacy. But the TNG web publishing application that many Legacy users use does not import the tag that Legacy uses to report Child Status. (Legacy currently exports it as an attribute of the child in the family structure.)
- --> IE, none of your Child Status attributes have EVER been imported into TNG. Maybe this OK with you? Maybe you have never noticed? Further analysis shows that Legacy's approach to Child Status seems to be unique among the major genealogy products and, although the best (as far as I am concerned) actually, may not be optimal. In reality, there is no consistency in how various products implement Child Status attributes, if they handle them at all.
- Consequently, the TNG developer has less incentive to provide the fix for this mis-match with Legacy. As this has been a problem for 10+ years with, supposedly, only myself and one other user expressing concern over this to Legacy, I would like to know if other users have seen this and would like to see this resolved. Getting something resolved - and quickly - will require having many folks second that this is an issue for them.
- --> Let me emphasize that this is not a Legacy bug. Legacy itself works fine. This is a mis-match in the interface between two products. Also, do you know of any other programs where the current Child Status implementation is causing a problem from Legacy Gedcoms?
- Thanks for listening,
- john.
- nashua, new hampshire
Legacy User Group guidelines:
http://www.LegacyFamilyTree.com/Etiquette.asp
Archived messages after Nov. 21 2009:
http://www.mail-archive.com/[email protected]/
Archived messages from old mail server - before Nov. 21 2009:
http://www.mail-archive.com/[email protected]/
Online technical support: http://support.legacyfamilytree.com
Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com).
To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
