Lynn,
This help entry explains the Ancestry APID Source Element:
https://tmgtogedcom.com/en/sources.htm#ancestry-apid-element
However, if you put the APID in the Citation Reference field, the "Ancestry APID Source Element" value doesn't matter because the APID is not a source element value.
If you search the .GED file for "_APID" you should see the value. It will appear like this:
3 _APID 1,6061::32975734
If you don't see that record, it's likely the citation was not included:
John
--
You received this message because you are subscribed to the Google Groups "TMG to GEDCOM" group.
To unsubscribe from this group and stop receiving emails from it, send an email to t2g-l+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/t2g-l/00bc01d6199b%24af73de80%240e5b9b80%24%40gmail.com.
Lynn,
For Ancestry, only the _APID record is necessary. I'm pretty sure Ancestry ignores the custom _CREF record. T2G writes the _CREF record in hopes that some GEDCOM reader will support it, possibly by a custom configuration where the user directs the program where to store the citation reference value.
A Perl script to add _APID will require you to run it every time you export. Also, some of my other programs will make use of APID values but right now they expect to find it in one of the places that T2G looks for it. For example, GedSite detects APIDs and adds a link to citations that contain one. (That may not be in the public version yet.) Second Site will get that feature next.
So, a better solution than a user-written script is for my programs, including T2G, to look a little harder for the APID values. It could parse APIDs from URLs that include "ancestry", "dbid=" and "h=". I'll probably add that to T2G, but I am not sure about its release date. I am busy with ORA right now.
John