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 -----
From: "Garnet Quigley" <[email protected]>
To: <[email protected]>
Sent: Monday, March 01, 2010 9:25 AM
Subject: Re: [LegacyUG] What is the _APID Gedcom Tag?


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.

Garnet


Robert Carneal USA wrote:
> That might be it, Evert. I was thinking:
> A[ncestry] P[erson]ID.  I was comparing them to RINs.
>
> Robert
>
> At 2009-11-04  09:41 AM, you wrote:
>> just a gues A (ncestry) P (ublication) ID
>> Evert
>>
>> 2009/11/4 Mike Fry <[email protected]>:
>> > Like one or two others, I have been experimenting with downloading
>> a GEDCOM
>> > file from Ancestry to see how the sources are imported.
>> >
>> > Well, the first thing to note is that they import in Basic Format!
>> >
>> > Having said that, I notice that the import procedure seems to have
>> one or
>> > two problems with a particular, Ancestry-defined tag - _APID. Does
>> anyone
>> > have any idea what this tag is trying to convey? It's not al all
>> obvious
>> > from an examination of the downloaded GEDCOM text, what the tag is all
>> > about.
>> >
>> > In the  a g file generated from the import procedure, I see many
>> messages of
>> > the following form:-
>> >
>> >    Main Record: 0 @S1029350835@ SOUR
>> > * Unrecog. Line for a Source  Record: 1 _APID 7572
>> >  Placed in  Note : _APID 7572
>> >
>> > These, together with one or two more explicit errors that I can't
>> correct
>> >
>> >    Main Record: 0 @P4193015077@ INDI
>> >  Sub Section: 1 SEX M
>> > * Unrecog. Line for an Individual  Record: 2 SOUR @S1029764659@
>> >  Placed in  Note - James W P Wall: SEX: SOUR @S1029764659@
>> >  PAGE Class: RG10; Piece: 1800; Folio: 159; Page: 28; GSU roll:
>> 838798.
>> >  NOTE
>> >
>> http://search.ancestry.co.uk/cgi-bin/sse.dll?db=uki1871&h=14518996&ti=5538&indiv=try&gss=pt
>>
>> >  NOTE
>> >  DATA
>> >  TEXT Name:  James W P WallBirth:  abt 1865 in Cley, Norfolk,
>> EnglandDeath:
>> >                 _APID 7619::14518996
>> >
>> >
>> > --
>> > Best regards,
>> > Mike Fry
>




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





--------------------------------------------------------------------------------



No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 9.0.733 / Virus Database: 271.1.1/2713 - Release Date: 02/28/10
08:34:00




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



Reply via email to