Page 1 of 1

Export Gedcom File Plugin

Posted: 10 May 2016 10:32
by lastejas
Mike

Is it possible to add an option to this wonderful plugin whereby one can export Named Lists rather than just the whole file. I know you can export Named Lists via the File-Import/Export Opton, but this is just the basic export. Not suitable for loading into other systems.

The reason I ask this is because I have two trees on my TNG website derived from one Master Tree, which originally was held in Rootsmagic and I could export Named groups which import almost perfectly into TNG. I have moved everything over to FH but now I cannot export the two trees form FH in the TNG format. What I'm actually doing is using the Export Mod to created an RM version then importing this into RM and then Exporting the required named Groups. A long winded way, but the only way I can see of doing this.

Any help would be gratefull.

Re: Export Gedcom File Plugin

Posted: 10 May 2016 11:03
by tatewise
Rick,
Use File > Import/Export > Export > GEDCOM File to create a GEDCOM file based on a Named List.
Ensure the Exclude options are all unticked except Unconnected Records and review the other options.
After saving in the Public folder FH will ask Do you wish to view the exported file? so say Yes and then run the Plugin in the new FH that opens.

This technique will work for any subset selection, and is mentioned in the Help & Advice page, and I have added the above details to the F.A.Q. page.

Re: Export Gedcom File Plugin

Posted: 10 May 2016 13:21
by lastejas
Mike

Thanks for that, I didnt think of that method.

Will give it a go, but basically it is the same as I was doing with RM as a "middle man", but using FH twice to do the same thing.

Re: Export Gedcom File Plugin

Posted: 14 Sep 2016 16:00
by jclifford
If I RUN the plug-in in my normal project, I get the correct Options window.

But if I create a new GEDCOM either by using the Split Tree Helper of by using the named list method in this thread. I get an error message:

[string "C:\ProgramData\Calico Pie\Family Historian\..."]:638: Cannot Make Folder: no such file or directory.

Can you help, Mike?

Re: Export Gedcom File Plugin

Posted: 14 Sep 2016 16:19
by tatewise
Sorry, yes my mistake. I will post a fix ASAP.

The standalone exported Gedcom is not handled correctly.
A workaround is to use File > Project Window > New Project and create a new Project from the Gedcom.
Then the Plugin will run OK.

I am surprised that the Split Tree Helper output has a problem, because that should normally be run on a Project.

Re: Export Gedcom File Plugin

Posted: 14 Sep 2016 19:44
by jclifford
I was following what I thought were the instructions for Split Tree Helper - to export a copy gedcom and then open it and use the helper on that, so I must have missed something about using it on a project.

I have now used your workround and it worked OK. I uploaded the resulting Gedcom to a TNG site and the result was definitely improved as it had a list of witnesses below each original event but it doesn't show the link to the event in the details of each witness as FH does.

Also each person's detail page had a Note at the bottom listing everyone in the named list, which seems odd.

Re: Export Gedcom File Plugin

Posted: 15 Sep 2016 13:24
by tatewise
The FH Help for Split Tree Helper appears to date back to the V3 pre-Project era, so needs updating.
See glossary:split_tree_helper|> Split Tree Helper that advises using Copy Project.

See the Plugin Hep & Advice page plugins:help:export_gedcom_file:tng_the_next_generation|> Export Gedcom File ~ (TNG) The Next Generation including its link to plugins:help:export_gedcom_file:std_standard_gedcom_5.5|> Export Gedcom File ~ (Std) Standard Gedcom 5.5 which explains how:
  • Fact Witnesses are exported as a Principal fact Note entry, and a Witness synthetic Fact.
    This is because Witnesses are in the FH glossary:gedcom_extension_list|> GEDCOM Extension List not supported by TNG, and therefore cannot be linked as in FH.
    The synthetic Fact is probably not shown in TNG because you have overlooked setting the Accept data for all new Custom Event Types as advised under Import Details in the above Hep & Advice page.
  • Named List Entry details are exported as a synthetic Note Record.
    This is because Named Lists are in the FH glossary:gedcom_extension_list|> GEDCOM Extension List not supported by TNG.
    Either empty the Named List in FH before using Plugin, or in the Plugin on Extra Options tab, change the Named List Entry option to Remove entirely.

Re: Export Gedcom File Plugin

Posted: 15 Sep 2016 15:41
by jclifford
All working OK now thank you. I will try to make more use of the Knowledge Base in future.

I found that after importing from the gedcom with Accept All Custom Event Types selected, I had to go into Custom Event Types in the TNG admin menu and change some them from Ignore to Accept and then repeat the import - or do what TNG recommends and do the first import as Import Custom Event Types only then edit the event types and then do the full import.

Re: Export Gedcom File Plugin

Posted: 15 Sep 2016 20:21
by tatewise
Those Knowledge Base pages are also available via the Plugin Hep & Advice button.