Ability to export selected records to a Gedcom

JonAxtell · Post by **JonAxtell** » 05 Feb 2007 09:13

First off, I realise that the Split Tree Helper function is available, but the current method is clunky, long winded, you need to remember various steps, is unnecessarily complicated, and not intutitive. Especially when you would just like to export a small selection of records as a one off for someone else. I understand that the underlying database for FH is the Gedcom file itself, so no export is really needed since the file itself can be copied. However ...

When I select Files->Export->Gedcom I expect to be able to export the program's current state of the 'database'. I also expect to see options to allow me to limit the amount of information exported. This is normal because most occasions when exporting a Gedcom is because you want to give someone else the results of your research but a lot of the times its not necessary to give them all the information or even some information is private. So options to allow selection of subsets of the database by query, to remove information based on living or private flag should be available.

ID:2159

YouTube · Post by **Jane** » 05 Feb 2007 10:38

Other than the fact that you need to save the file as a new name first doesn't split tree do all that you are asking for?

JonAxtell · Post by **JonAxtell** » 05 Feb 2007 18:06

As I said, the Split Tree Helper Function does the job, but in a very awkward manner. If I'm going to be sending a Gedcom to someone as a one off - to save my current file, then strip the information out, then remember to switch back to my main file is a real pain. Not forgetting that when you switch back to your main Gedcom, you've lost your place since the file is reloaded. It's also a counter intuitive way to go about exporting a file. 99.9% of programs that export data do it by creating the file and exporting data to it (with such steps hidden from the user), not ask you to copy your own file then remove information from it.

The best solution would be that when you select File->Export->Gedcom the split tree helper function copies the file itself (why should the user do an extra manual step when the program can do it?), works on the copy stripping off the information, and leaves you in your main Gedcom where you were without reloading the file.

One final point, to have a prompt appear on screen telling you you can't do something is not good UI design, especially with so much information in it. Either don't show the facility at all (so no File->Export->Gedcom) or implement it properly.

ajax10084 · Post by **ajax10084** » 01 Apr 2007 15:32

What I would like to do is display a selected diagram, descendants of xyz say, hide the individuals I don't want, then export only the individuals displayed in the diagram to a gedcom file.

ajax10084 · Post by **ajax10084** » 01 Apr 2007 15:35

Also, to add to above, I would like to be able to generate a report from a diagram in the same way as outlined above.

ireneblackburn · Post by **ireneblackburn** » 01 Apr 2007 16:17

Split tree helper might be a bit clunky sometimes, but I have always found it easy to use, and I am no programmer. If I am only sending limited information I have often used a diagram including the BMD dates and census entries and emailed the saved diagram to correspondents. It is ideal if you are just sending a few closely related people. It is then up to the person you to whom I have sent it whether or not they put the information into their database.

Irene B

pricero1 · Post by **pricero1** » 01 Apr 2007 20:50

See the article at:

Post by **nsw** » 02 Apr 2007 12:11

Robin's link brings up an error because the > at the end is included in the url.

Link is

http://www.fhug.org.uk/cgi-bin/index.cg ... ews&id=139

pricero1 · Post by **pricero1** » 02 Apr 2007 12:16

Thanks, Nick.

ajax10084 · Post by **ajax10084** » 05 Apr 2007 21:51

Robin Price - brilliant, thanks. Though about named lists and wanted to do that but couldn't find out if or how.
Don't find the help files a lot of help sometimes.

Family Historian User Group