Ron, Thanks for the explanation.
I agreed completely with what you say, but comparing and clicking thru 600 pictures is more like an hour and half rather than a few minutes. The problem is that the data used was a gedcom of approx 8500 persons tagged and created from my database of 220,000. I tagged everyone who had that particular cemetery as their burial place, then also included the parents, spouses and children in the gedcom, since they would also likely be buried at the same place. I did not want the 'volunteer' to have to add any persons. The gedcom was sent and they also used Legacy 7.5 to enter the links and pic captions Then they send the file back to me as a gedcom. But because Legacy doesnt export a COMPLETE (parental) Family group , I have all these 'not matching' families Now, if the question to include spouses, parents and children of tagged individuals ALSO asked about siblings of tagged persons, then there would be complete FAMC groups and exact matches when importing the data back into the original file, Thanks for taking the time to help out and think thru on this. Jay On Wed, Jun 18, 2014 at 5:05 PM, Ron Taylor <[email protected]> wrote: > Jay, > First, it is necessary to understand how the GEDCOM was used to insert the > new picture attachments. If it was done with a text editor, that could be > interesting. If the GEDCOM was loaded into some other genealogy program or > even another Legacy database and then the pictures were attached, the > updated file could again be exported to another GEDCOM and that GEDCOM > imported into a new Legacy database. > > If the only difference between the GEDCOM file and the Legacy file that > created it are the new picture attachments, you should be able to then > combine the data from the GEDCOM imported back into Legacy with the > original Legacy file and execute an Intellishare Merge. Every record that > has a new picture attached will bring up the original and the imported file > for review before merging but the only difference should be the picture > attached to the imported GEDCOM record. If that is the case you could > quickly click through the 600 records allowing them to merge. If there are > other fields that someone changed, those would obviously require more > evaluation before merging. > > It may be possible to merge that in a few minutes if it meets the > description I've given above. > Ron Taylor > > > On Wednesday, June 18, 2014 5:40 PM, Jay 1FamilyTree < > [email protected]> wrote: > > > > > I have someone who graciously helped me out in linking over 600 image > tombstones to the correct persons and added a Pic Caption and Pic Desc to > over 800 persons > > They entered this info into a gedcom I created from my Legacy7.5 database. > (I am still using ver 7.5 also) > > All I want to do is take the 800 or so persons that are linked to the 600 > or so images and merge them back into my original file. Updating only the > link, pic caption and pic descr. > > Anyone have any creative ideas to make that happen?? > > > > The standard merge process is so time consuming. > (because of diff family sizes, some with , some without spouses, etc. ) > > I even have a txt file listing of the new filenames that are now linked up > (there were already several hundred pic links to this same cemetery, so > they have the identical IDBPPic in the BR table.) > > Otherwise, I guess my next weekend will be spent > merging................................................................ > > > Thanks in advance for any help > Jay > > > Legacy User Group guidelines: > http://www.LegacyFamilyTree.com/Etiquette.asp > Archived messages after Nov. 21 2009: > http://www.mail-archive.com/[email protected]/ > Archived messages from old mail server - before Nov. 21 2009: > http://www.mail-archive.com/[email protected]/ > Online technical support: http://www.LegacyFamilyTree.com/Help.asp > Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and > on our blog (http://news.LegacyFamilyTree.com). > To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp > > > > > Legacy User Group guidelines: > http://www.LegacyFamilyTree.com/Etiquette.asp > Archived messages after Nov. 21 2009: > http://www.mail-archive.com/[email protected]/ > Archived messages from old mail server - before Nov. 21 2009: > http://www.mail-archive.com/[email protected]/ > Online technical support: http://www.LegacyFamilyTree.com/Help.asp > Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and > on our blog (http://news.LegacyFamilyTree.com). > To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp > Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
