"Also Known As" name is not porting over correctly from Ancestral Quest v16.

Marshall Noker

I am just finishing uploading 12,000 individual names from my father's records in Ancestral Quest 16 (AQ) to FamilySearch (FS). Often, if the record already exists, the name may be spelled different. I want to keep the various names to make future searches easier. If I tell AQ to keep the name I am importing as "Also Known As", it saves it in FS as "Birth Name".

This is incorrect. I've talked to AQ people who say they send the data to FS exactly as FS requests. AQ acts as if it isn't their problem. So, is this a FS problem? How do I get developers from FS and AQ to talk to each other and identify the data fields that need to interact?

MandyShaw1

@Marshall Noker I am afraid you are going to have to ask AQ Support to raise this with FamilySearch, since it is their code that is getting the incorrect results (also, this Community doesn't deal with developer matters). Sorry we can't help.

Alan E. Brown

@Marshall Noker I did a quick experiment with AQ 16 and it worked just fine. The GEDCOM export of the names looks like this:

1 NAME Alan /Brown/

2 NICK Alan Nick Brown

2 _AKA Alan AKA Brown

2 _MARNM Alan Married Brown

And when I imported it in FamilySearch into a User Tree, it looks like this:

Note that the AKA field in AQ exported properly to GEDCOM and imported properly into a FamilySearch User Tree. So it appears that as long as what you do in AQ for an AKA results in a field labeled _AKA in the GEDCOM file, then FamilySearch handles it as expected. If AQ is not producing such a field, then you'll need to contact AQ Support.