I can't say I understand what you are getting at. As I said, I have only used small test files so far. Legacy created and attached a data value labeled "_UID" to each record. Ancestry.com apparently read those values and stored them in a field labeled "UID". When Ancestry.com wrote back a GEDCOM from the same records it included the original data in a field tagged as "UID". Legacy does not know what a UID field is, but you can re-map that field to one Legacy does recognize: "_UID", when you import the Ancestry GEDCOM.
The net result of all this is two Legacy databases: one original, and one containing changes made on Ancestry.com. Every record that is carried over from Legacy to the new, modified database includes a _UID data string that is unique for that record. There may be records introduced by Ancestry that did not include a UID field, frankly I don't know or care about that. I believe Legacy assigns its own _UID to each record when it imports, when the record doesn't already have one. Any such newly assigned _UID is not going to match any of the records in the original Legacy database. So, when you use Intellishare to merge the files, any records that match _UID's and all data are merged automatically; any records with matching_UID but different data are shown for verification; any completely new _UID's are appended to the merged files. The resulting database is the union of both merged databases, with all duplicates removed. If anyone knows of an error in what I've said here, please let me know. It may keep me from sending a lot of time spinning my wheels. Robert Mann Sandy Springs, GA -----Original Message----- From: [email protected] Sent: Tuesday, January 12, 2010 8:58 PM To: [email protected] Subject: Re: [LegacyUG] Exchange with Ancestry.com Round 2 Robert Could you describe the kinds of changes you made in Ancestry? IF Legacy's original export was not faulty, then it had no plain UID tag, and I much doubt an APID one. It follows that their source was almost certainly Ancestry, by processing error, systematic action, or as a consequence of the changes you made. If you were importing individuals into your tree while in Ancestry, then the tags may have been included. Your import and reexport might indicate something not readily apparent by the kind of comparison you made. A change in RINs might just reflect the import settings, and/or personnel deletion in Ancestry. I can't remember whether the source numbers are mapped from individual's data, or are file line locations. Either way, it looks like some significant size and/or structural arrangement change occurred during the re-import. Might just reflect elimination of the APID tagged line(s) and any depending CONC ones, but you'd need a more discriminating comparison to easily identify that. Re. messing with GEDCOMS: Intellishare seems to promote multiplication of parents. I've got 300-500 sets to delete, at something like 10 keystrokes each if I do it via Legacy. If I can locate and fix the links in the GEDCOM, I'll only need a handful of UIDs to find them. Things like that come up often. If one works with others using disparate programs and independently entered matching individuals, there's good reason to standardize UIDs, ideally to values adopted by IGI - if that ever happens. Can't do that in Legacy. Just examples... kb ----- Original Message ----- From: "Robert Mann" <[email protected]> To: [email protected] Sent: Tuesday, January 12, 2010 7:01:26 PM GMT -05:00 US/Canada Eastern Subject: RE: [LegacyUG] Exchange with Ancestry.com Round 2 ... imported the Ancestry GEDCOM into Legacy (remapping UID) and immediately exported it back out as a new GEDCOM ... ... The RIN's were different, and the source ID numbers were changed. I can't see any reason to mess with the GEDCOM files, unless there is something else you are trying to do besides transferring the data from Ancestry to Legacy. 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 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 To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
