Exporting a gedcom to TNG strategy - ideas
Posted: 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?
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?