Export Gedcom File - Ancestry - Tips
Posted: 24 Mar 2022 12:24
As an aside to the Export Gedcom File - Ancestry (20488) thread; my 2pennyworth. Uploading to Ancestry trees is a pain, in many more ways than I will detail here. Although most detail is uploaded (with or without Mike's excellent Export Gedcom File), even if you know where the detail is, it takes many clicks to find it and when you do, text is often put into a long string so very difficult to follow.
I think one should appreciate what Ancestry trees are about. It is primarily for ease of use for Ancestry subscribers who develop their tree on Ancestry, easily attaching sources provided by Ancestry. This also keeps those users with Ancestry. I am not decrying this as for many people it is far easier, it is a just pity Ancestry did not make Gedcom import better, although one wonders if this is a business model design! Many of "us" use Ancestry trees as a "shop window" or DNA thrulines or hints, so we have to accept the limitations therein.
Before running Export Gedcom File, and when I have time, I have a rather laborious routine to upload to make the tree easier to view on Ancestry.
But, the main thing I like to do, on a copied FH project, is use the plugin CopyFactToManyIndividuals
(see https://www.fhug.org.uk/forum/viewtopic ... 233#p72233, I don't think it is verified for v7 but on a copied project nothing to lose)
for a fact that has a PLACe field of "see https://gw.geneanet.org/jimlad68 for more&better displayed info" (why PLACe; it displays better in Ancestry trees), I also add some note text.
This then directs viewers to Geneanet trees which in my mind display a Gedcom file so much better, is quick to upload and overwrites the existing Gedcom, rather than a forced new one as in Ancestry trees.
However, I am worried for the future as Ancestry have bought out Geneanet, and look what they did to the simple but excellent Rootsweb trees!!
P.S. I think mike's plugin Copy Fact to Chosen Records will also copy a fact, using a slightly different method
https://www.fhug.org.uk/forum/viewtopic ... 292#p72292
I think one should appreciate what Ancestry trees are about. It is primarily for ease of use for Ancestry subscribers who develop their tree on Ancestry, easily attaching sources provided by Ancestry. This also keeps those users with Ancestry. I am not decrying this as for many people it is far easier, it is a just pity Ancestry did not make Gedcom import better, although one wonders if this is a business model design! Many of "us" use Ancestry trees as a "shop window" or DNA thrulines or hints, so we have to accept the limitations therein.
Before running Export Gedcom File, and when I have time, I have a rather laborious routine to upload to make the tree easier to view on Ancestry.
But, the main thing I like to do, on a copied FH project, is use the plugin CopyFactToManyIndividuals
(see https://www.fhug.org.uk/forum/viewtopic ... 233#p72233, I don't think it is verified for v7 but on a copied project nothing to lose)
for a fact that has a PLACe field of "see https://gw.geneanet.org/jimlad68 for more&better displayed info" (why PLACe; it displays better in Ancestry trees), I also add some note text.
This then directs viewers to Geneanet trees which in my mind display a Gedcom file so much better, is quick to upload and overwrites the existing Gedcom, rather than a forced new one as in Ancestry trees.
However, I am worried for the future as Ancestry have bought out Geneanet, and look what they did to the simple but excellent Rootsweb trees!!
P.S. I think mike's plugin Copy Fact to Chosen Records will also copy a fact, using a slightly different method
https://www.fhug.org.uk/forum/viewtopic ... 292#p72292