Introduction
The Next Generation is a popular, Internet-based, genealogy product. See the Migration Guide for the recommended TNG settings. Visit The Next Generation of Genealogy Sitebuilding (TNG) for product details.
It offers one of the more complete GEDCOM implementations and supports Witnessed/Shared Events but is dissimilar to FH and other products.
So the default is to convert the Fact Witnesses & Roles to Fact local Notes, with the option to use hyperlinks to open the personal records.
The hyperlinks need a Tree ID entered in the Project Header record, Receiving System field, using the format TNG: tree1 or TNG = family3.
Most modes of Multimedia Conversion are supported depending on how Media files are to migrate to TNG. Features include _PRIM Y tags for preferred Individual Media photos and _TYPE tags for Media Keywords.
The Character Set Encoding defaults to UTF-8 with all Unicode characters supported.
Choose ISO-8859-1 for the TNG alternative English ISO option that omits many Unicode characters.
The [[private]] Text Option defaults to Include private text but remove the [[ ]].
The Rich Text Formatting defaults to Change rich text into HTML 5 format so most text formatting is retained.
See both the (TNG+) Full Data Export Details and (TNG-) Brief Data Export Details below.
Migration Guide
In TNG apply the following settings to upload the exported GEDCOM & Media. If this is not the first upload, then you may need to clear the tree in TNG first.
Administration > Setup > Configuration > General Settings
Paths and Folders
To support the _TYPE tag apply the following settings.
Set all five Media Collection folders to media.
In Import Settings leave Local…Path(s) blank and Import file name only set.
Also, review the If no birth date... and If no death date… assumptions.
Language
Either leave the default Unicode English UTF-8 encoding, or choose the English ISO encoding.
Event / Attribute Types > Edit Existing Type
Apply these settings for Individual records.
Set the CENS tag to Accept to import Census Events.
Create a custom _FLGS tag to accept Living & Private flags, etc, but only one is imported per Individual.
Create a custom _USED tag and set Display Order to -1 to import the Given Name Used field and position it before Events.
Create a custom NAME tag with Display label *AKA and Display Order of -1 to import multiple instance Alternate Names and position them before Events. The leading asterisk (*) positions those names higher in the list of Other Events in the Advanced Search.
Each FH Custom Event/Attribute will need a matching EVEN Type/Description definition.
Choose Select Tag: EVEN – Event and in Type/Description: enter the TYPE name of each Custom Event/Attribute.
Notice how the displayed name can be defined for each language, which is particularly useful for Fact Witness synthetic facts.
It may be easier to set Accept data for all new Custom Event Types in the GEDCOM Import options below.
Import/Export > GEDCOM Import
To avoid upload time-outs, it is best to transfer the GEDCOM file to the TNG GEDCOM folder, and Media files to the media folder, using an FTP utility to choose the FH Plugin Export folder and the Project…TNG UTF8.ged or Project…TNG ISO.ged file and Media files to upload.
(TNG+) Full Data Export Details
All the (Std+) Full Data Standard GEDCOM Release 5.5 rules apply except as defined below.
Individual & Family Records (INDI, FAM)
★ Given Name (_USED)
See Extra Options tab Given Name 2 _USED:
The Given Name Used field is converted from 2 _USED to 1 _USED for the setting shown above.
★ Record Flags (_FLGS)
See Extra Options tab Record Flags 1 _FLGS:
Custom Record Flags are retained, but only one Flag per Individual record is imported by TNG.
★ Fact Witnesses (_SHAR, _SHAN)
See Extra Options tab Witness Role 2 _SHA%u:
If a Tree ID exists in the Project Header record, Receiving System field, with the format TNG: tree1 or TNG = family3 then the Fact Witness names become hyperlinks to their records.
See above for handling of the Fact Witness synthetic custom Event/Attribute fact types.
★ Custom Attribute (_ATTR, FACT)
See Extra Options tab Custom Attribute 1 _ATTR: or 1 FACT:
Each custom Attribute is converted to a custom EVENt with the value retained on the tag line instead of a local Note.
See above for handling of the custom Event/Attribute fact types.
★ Individual Alias (ALIA)
Each Alias is converted to a synthetic custom Event using the EVEN tag with any value on the same line.
★ Fact E-mail, Website, Fax Number (_EMAIL, EMAIL, _WEB, WWW, FAX)
See Extra Options tab Fact E-mail 2 _EMAIL: or 2 EMAIL: & Fact Website 2 _WEB: or 2 WWW: & Fact Fax No. 2 FAX:
These become GEDCOM 5.5.1 tags as follows: 2 _EMAIL or EMAIL to 2 EMAIL and 2 _WEB or WWW to 2 WWW and 2 FAX to 2 PHON
Repository & Submitter Records (REPO, SUBM)
★ Record E-mail, Website, Fax Number (_EMAIL, EMAIL, _WEB, WWW, FAX)
See Extra Options tab Record E-mail 1 _EMAIL: or 1 MAIL & Record Website 1 _WEB: or 1 WWW & Record Fax No. 1 FAX:
These become GEDCOM 5.5.1 tags as follows: 1 _EMAIL or EMAIL to 1 EMAIL and 1 _WEB or WWW to 1 WWW and 1 FAX to 1 PHON
Media Records & Local Media Objects (OBJE)
★ Media (OBJE)
All links to Media Records and Local Media Objects are converted according to the Basic Options chosen.
For each OBJE Media item, the first of any entirely uppercase _KEYS Keyword is added to a _TYPE tag to specify its Media Collection. The Keyword Update plugin may be useful in setting these uppercase Keywords.
For each Individual record, the most preferred Media tab item without Exclude from Diagrams set, gains the _PRIM Y tag to identify the primary photo.
★ File Format (FORM)
Each FORMat tag is converted to GEDCOM 5.5.1 style subsidiary to the FILE tag.
★ Media Title (TITL)
Each TITLe tag is converted to GEDCOM 5.5.1 style subsidiary to the FILE tag, except in local Media Objects.
★ Keywords (_KEYS)
See Extra Options tab Media Keywords %d _KEYS:
For each OBJE Media item, the first of any entirely uppercase _KEYS Keyword is added to a _TYPE tag to specify its Media Collection. Any other Keywords are moved to a local Note with a Keywords: label.
Place Records (_PLAC)
★ Place Record (_PLAC)
See Extra Options tab Place Record 0 @P%d+@:
Each Place Record has its Record Ident deleted but other details retained for import to TNG.
(TNG-) Brief Data Export Details
All the (Std-) Brief Data Standard GEDCOM Release 5.5 rules apply together with the (TNG+) Full Data Export Details defined above, except as overridden below.
Individual & Family Records (INDI, FAM)
★ Fact Witnesses (_SHAR, _SHAN)
See Extra Options tab Witness Role 2 _SHA%u:
The Fact Witness synthetic fact local Note only lists the Principal person.
Return to the Export Gedcom File ‘GEDCOM Destination’ Advice help page.
Return to the Export Gedcom File main help page.
Plugin Export Gedcom File
Help content on this page is owned and provided by Mike Tate, the plugin's author, Calico Pie takes no responsibility for its content.