* Gedcom Export FROM Legacy FT

For users to report plugin bugs and request plugin enhancements; and for authors to test new/new versions of plugins, and to discuss plugin development (in the Programming Technicalities sub-forum). If you want advice on choosing or using a plugin, please ask in General Usage or an appropriate sub-forum.
Post Reply
User avatar
ronk
Superstar
Posts: 428
Joined: 19 Feb 2016 22:50
Family Historian: V7
Location: MN, USA
Contact:

Gedcom Export FROM Legacy FT

Post by ronk » 11 Mar 2016 20:27

Noticed this sometime ago after migration from Legacy to FH, and then export from FH to TNG, but was working on other more important items so left this go.

When exporting from Legacy, followed the procedures; specifically to
Tick Move Event Descriptions to the Event Notes field.
. Wasn't sure what effect that would have at the time.
a1.jpg
a1.jpg (60.96 KiB) Viewed 3056 times
Below are TNG and Editor captures of Before and After migration from Legacy to FH (both exporting to TNG):
a2.jpg
a2.jpg (111.36 KiB) Viewed 3057 times
a3.jpg
a3.jpg (97.63 KiB) Viewed 3057 times
You can see two items have become Notes, and so have moved to the bottom of the webpage. I was wondering why it was recommended to move the descriptions to notes. Does FH not recognize them otherwise?

Ron
Ron Krzmarzick~~ FH 7.0.20 TNG 14.0.2 website Roots & Relatives Remembered, Laragon 5.0, Win 11 pro

User avatar
tatewise
Megastar
Posts: 27087
Joined: 25 May 2010 11:00
Family Historian: V7
Location: Torbay, Devon, UK
Contact:

Re: Gedcom Export FROM Legacy FT

Post by tatewise » 11 Mar 2016 21:19

I should have checked, and at the time requested you review the options, but it seems that Legacy considers all facts to be Events even though it is a GEDCOM dialogue and it should differentiate between Events and Attributes.

In FH/GEDCOM 5.5 the Events cannot have values/descriptions, whereas Attributes can.

So it is best to NOT tick that Legacy option, and let the FH import move the Event values/descriptions to the Note field. The only possible snag is where the Event already has a Note whereupon a hidden 2nd instance Note gets created (I think). An alternative import Preference moves each value/description to an _UNCAT UDF field instead, which can then be merged with any Note field using a Plugin.

None of above applies to Attributes like Occupation which will retain their value/dewscription.

If all the above is a correct analysis, then that KB advice needs correcting.
Mike Tate ~ researching the Tate and Scott family history ~ tatewise ancestry

User avatar
ronk
Superstar
Posts: 428
Joined: 19 Feb 2016 22:50
Family Historian: V7
Location: MN, USA
Contact:

Re: Gedcom Export FROM Legacy FT

Post by ronk » 12 Mar 2016 05:32

I decided to rebuild the FH gedcom with the Legacy Export leaving the move event box unticked to alter the handling of events for the migration to FH. Occupation/Religion/etc now presented as desired in FH and TNG, as well as LFT.

The change moved over 800 of 4600 notes back to occupation/religion/immigration labeled areas in TNG.

Agreed, that perhaps the Import from Legacy advice for event option should be modified or clarified.

Ron
Ron Krzmarzick~~ FH 7.0.20 TNG 14.0.2 website Roots & Relatives Remembered, Laragon 5.0, Win 11 pro

Post Reply