HomeTutorialsTrees and GEDCOM downloads


Trees and GEDCOM downloads — 11 Comments

  1. I have an Export question. I have a TNG tree with 24000+ people which i made from ancestry.com stuff. Now I find it is flawed as the people are Pxxxx instead of Ixxxx ID’s. I was hoping to export the ensire databse as a GEDCOM fix it in some tool and then make a new corrected tree. Possible?

    • You would be better off exporting it into some kind of database, where there are more tools available for data manipulation, instead of as a GEDCOM. If, for example, you got it into a database such as MySQL, or even as a spreadsheet. Both tools have ways to substitute Pxxxx int Ixxxx format. You say that you have the information already as a TNG site. So wouldn’t individuals already use the Ixxxx identification, which is the standard in TNG?

      • after the fact, I found out that importing a ancestry.com sourced GEDCOM into TNG has issues. The individuals become P rather than I and that the TNG merge function will not work with P, just I

        • The ‘P’ must have been created within Ancestry (P for People?). Not by TNG. And yes, that would defeat any merging with other TNG information.

          • My problem is that I added a bunch of people within TNG before I realized that, so now have a mix of I and P.

    • There is a setting in TNG that will allow you to use the ‘P’ prefix instead of the default ‘I’. This will permit you to work with the Ancestry GEDCOM, which uses the ‘P’ code. Go into your Admin panel, then Settings >> General Settings >> Prefixes and Suffixes. Change the Person Prefix to = P. Then, when you import your GEDCOM from Ancestry, set the import to “Replace all current data”, to overwrite the previous information. Assuming that you want your TNG site to be synchronized to Ancestry.
      In doing this, you are now stuck with individual prefix = ‘P’. That should not be a problem unless you also work with GEDCOM files outside of Ancestry.

        • I think I could strighten out a lot of things if I could just export my whole tree as a GEDCOM and then reimport it. But I get the 1/2 way through the export process but don’t see how to save the gedcom

          • If you just export your GEDCOM out of TNG, and then re-import it into TNG, that does not fix the prefix of ‘P’ for individuals. Saving the GEDCOM: Assuming you are talking about exporting out of TNG (and not out of Ancestry), after clicking on the Export button, you should see a “Finished Exporting GEDCOM” message, followed by a link “Download GEDCOM”. Instead of left-clicking that link, do a right-click. In the popup window, choose “Save link as …”. That brings up another pop-up window, a file explorer. Note that the suggested filename to save will end in .ged. So select the directory that you want the file, perhaps change the file name, keep it as a .ged file, and you should now have your GEDCOM on your home computer.

  2. Hi Jim, Being very new to TNG and genealogy, I followed the instructions on set up and even reviewed your advice on using the “Don’t allow users to download GEDCOM files” and the other do not allow boxes. However last night I was on the site as a public visitor, decided to check settings, I was able to print to pdf, and on opening the pdf file the links were enabled just like I was on the site, I could print the entire tree. What did I do wrong ? Thanks, Greg

    • Greg: if you look at the screenshot in the article, it shows three checkboxes. The article only discussed the middle box: “Don’t allow users to download GEDCOM files”. Note the third box: “Don’t allow users to create PDF files”. Now, there is another page you need to review.
      Log in as Admin, go to the Administration page >> Setup >> Configuration >> General Settings >> Site Design and Definition. Scroll 2/3 down the page. Note the 3 choices: “Show Login/Logout Link”, “Show Share Link” and “Show Print Link”. These boxes control the visibility of icons in the upper-right of your pages. Just set the Print link to “No” and that should take care of your concern.
      Jim Benedict

Leave a Reply

Your email address will not be published. Required fields are marked *