* Exporting a gedcom to TNG strategy - ideas

Importing from another genealogy program? This is the place to ask. Questions about Exporting should go in the Exporting sub-forum of the General Usage forum.
Post Reply
User avatar
paultt
Famous
Posts: 114
Joined: 18 Jan 2005 21:59
Family Historian: V7
Location: Hampshire, England
Contact:

Exporting a gedcom to TNG strategy - ideas

Post by paultt » 18 Dec 2020 11:36

Exporting a gedcom to TNG strategy - ideas?
I ran three projects under v6.2.7, each of differing size and content, and exported a gedcom from each project to import into my three different websites running under TNG. My process was to
1. do any pre-export tasks in each project
2. Save and exit with a Medium Backup
3. Navigate to the project.fhdata folder and make a copy of the gedcom, renaming it (newgedcom)and saving into the same folder.
4. Double Click the newgedcom to load it into FH.
5. Run Split Tree Helper to remove a specific set of people(privacy rules) via query listing them, and any unlinked media, notes, source, repository, submitters and All named Lists.
6. Saved this newgedcom, and ran Mike's magic Export Gedcom File Plugin with all TNG favourable settings, dumping the output gedcom into my xampp localhost TNG gedcom folder.
7. Ran my normal TNG import routines, and when satisfied it worked correctly, upload the database to the relative live website.
Now I have all three projects under V7. If I run the same steps as above, I get a warning on step 4 saying that this is now a standalone gedcom and will not have all the functionality of a project, and suggest importing it into a 'new project' What, if any, functionality will I lose that will affect using the Export Gedcom function? I suspect almost nothing? Split Tree Helper does not 'clean up' the Research notes or Source Template definitions, so it looks like the built in Export Gedcom will be the way to go and not use the Split Tree Helper. So
1. as above
2. as above but don't exit.
3. Run the inbuilt Export Gedcom function, add all persons and then use the query to remove the unwanted 'private' persons, and exit FH.
4. Load the exported gedcom from 3 into FH - same loss of functionality warning
5. Run Mike's magic Export Gedcom File Plugin as per 6 above
6. as per 7 above.
I would welcome any comments or further advice on this process. How do the other users of TNG control their exports? Any differences in steps?

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

Re: Exporting a gedcom to TNG strategy - ideas

Post by tatewise » 18 Dec 2020 12:05

Paul, I've moved this to the Importing and Exporting Forum that is more appropriate.

Your new process is like the KB Exporting a Family Tree with/without Media for Export to Website Without Sensitive Data.

For Project only features see KB Understanding Projects under Project Benefits none of which affect your export process.
P.S. There may be some other Project only features in FH v7.0 but not sure. [ EDIT: Local Project only Fact Sets. ]

BTW:
My Export Gedcom File plugin can remove all Named Lists, Source Templates & Research Notes using the Extra Options tab.
Named List Entry top left.
Source Template and Research Note penultimate row.
Mike Tate ~ researching the Tate and Scott family history ~ tatewise ancestry

Post Reply