Legacy, like certain other programs, assigns a UID number to any record you enter, keeps those it finds with records already having them, and I think generates one for any record without one. Any GEDCOM created by Legacy should have the numbers on lines headed by _UID. It would be odd for Ancestry to systematically remove the underline and return all converted to UID. A minor Ancestry programming error might cause that to be used just for records you entered there, or if you imported a record there, it might have been so tagged. Subsequent complaint by Legacy on re-importing doesn't say whether all were UID, or that all original _UIDs were preserved but one or more UIDs were added. Since the fix is obvious, unless added UIDs had bad values, it's not a big deal. There's still the APID tag to explain and understand though. This is a Legacy Users Group, so the real question is whether it is safe to assume that equating UID to _UID is OK, and is discarding the APID data the optimum action?
Your description of the way Intellishare should work is accurate, except that different data aren't "shown for verification" but identified and presented for you to choose which to keep - with an initial Legacy default guess and an environment that makes even substantial editing or fact checking convenient. I haven't seen problems with facts, but suspect that there may be a bug regarding link management. kb ----- Original Message ----- From: "Robert Mann" <roem...@bellsouth.net> To: LegacyUserGroup@LegacyUsers.com Sent: Tuesday, January 12, 2010 9:51:38 PM GMT -05:00 US/Canada Eastern Subject: RE: [LegacyUG] Exchange with Ancestry.com Round 2 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 Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyusers.com/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/legacyusergr...@legacyfamilytree.com/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
