Hi Garnet Just going through the import gedcom process - select file (Legacy does an analysis), untick "Put unrecognised items into notes field", click "customise" (you should now get the unrecognised items, that you need to move to "items not to be imported" - I don't have a file to play with, so assume you simply highlight the _APID tag and then click "remove" to move from one box to the other - or drag it there). Alternatively if you map to a recognised item pick something like research notes or to do, then do another export and import cycle to exclude that tag on the second run - you will be doing a convert it on the first run.
Is the hyperlink quoted below ending up in the right place? Cheers, Brett ----- Original Message ----- From: "Garnet Quigley" <[email protected]> To: <[email protected]> Sent: Monday, March 01, 2010 5:14 PM Subject: Re: [LegacyUG] What is the _APID Gedcom Tag? Thanks for the input Brett. Not sure if it is just me, but I can't seem to find a way to exclude something from the "unrecognized items" box. I see how to exclude from those items that Legacy offers to import. I experimented with mapping the unrecogized item _APID to one that Legacy does recognize then excluding that item from import, but probably not surprisingly that did not work. And I would up with hundreds or more of the following errors: > Record: 0 @P281953773@ INDI > Sub Section: 3 TEXT > http://trees.ancestry.com/pt/AMTCitationRedir.aspx?tid=14852117&pid=281953773 > > * Unrecog. Line for an Individual Record: 2 _APID 1030::0 > Placed in Note - Argotta Franks: TEXT: _APID 1030::0 I am creating a new dataset so merging with an existing dataset is not an issue. I tried again with a fresh dataset, and clicked the "Clear the unrecognized media list before each import" just in case that was somehow relevant. But again no luck. Before throwing in the towel and moving on to option 3, perhaps you or Brian in support could tell me if excluding something from the "unrecognized items" box is possible. Thanks to both of you for your efforts. Garnet BMcL Robinson wrote: > Hi Garnet > > I am not sure of exactly the problem you are having, but working through > it > "logically": > 1 When you import the custom tag (starting with underscore) should come > up for either excluding or mapping to a Legacy standard tag. Given that > the > tag appears to be an Ancestry ID tag that you may never want you could > exclude it (= the simple answer). > 2 If you want the data imported that you could map it to a tag in the > available Legacy set (either std GEDCOM 5.5 or Legacy custom) during the > import - perhaps something like Research notes, where the data could be > out > of "harms way". > 3 Both 1 and 2 above assume things are working in Legacy as they > should, > and the data will either not appear at all, or be imported to the chosen > location (tag). However if this is not the case then you can introduce an > intermediate step to edit the gedcom file you have from Ancestry (a copy > of > course!!). This will definitely fix the problem, but can take a bit of > investigation depending on the extent of the "corruption". In essence you > use a text editor (eg MS Word, saving as a .TXT file, then renaming as a > .GED file) to find the tag you don't want and replace with the one that > you > do. Then the import into Legacy will be with your edited and hence "clean" > file and import anomalies should be prevented. If you want to go down this > path and need a bit more help let me know. > 4 I assume that you will do the import in two stages - first import the > .GED into a new empty Legacy dataset, then secondly merge what you want > (all > <-> nothing) with your existing data. > > Cheers, Brett > > ----- Original Message ----- > What is the best way to handle the _APID when importing the ged from > Ancestry.com into Legacy 7.4 Deluxe? A couple of years ago there used > to be another problem tag, _EID if I remember correctly, for which I > used Legacy's substitute tag _UID for the conversion. And it seemed to > either solve the problem or at least remove it from sight. I tried > using the same _UID as a substitute tag this time, but Legacy still > created hundreds of notes for the unrecognized _APID. Thanks for a > solution if there is one. 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
