Family Historian User Group

Mike, They are recorded on Ancestry but by reference to the index record, not as a specific citation. I have already checked the GEDCOM file, the source record is generic i.e. to the relevant index, and the citation does not include anything specific like a page or district (unlike the census which ...

Mike, true for the Census, not true for BMD see example below, unless I have added them by hand later. I understand your comment about result sets, it would be nice if FH could treat query results as an updateable view (like Access DB), but I guess this is a minority wish list item. The birth dates ...

Thanks Mike, you are right that is my intention, but not in the short term, and I may just live with it. The next priorities are to capture the BMD district, volume and page references as the citation page reference, which annoyingly haven't come across in the GEDCOM, and to capture all of the censu...

With help elsewhere in this forum I have got my GEDCOM file exported from Ancestry and into FH and cleaned up the errors. I am now going through the imported data attempting to bring the data up to a reasonable standard. So far I have done the following Set the citation assessments using Jane's plug...

Peter
Thanks that seems to have worked this time.
Regards
Graham

Actual EXIF info Filename - IMG-20160802-WA0000.jpeg Make - LG Electronics Model - LG-D855 Orientation - Right top XResolution - 72 YResolution - 72 ResolutionUnit - Inch YCbCrPositioning - Centered ExifOffset - 162 ExposureTime - 1/12 seconds FNumber - 2.40 ISOSpeedRatings - 1550 ExifVersion - 0220...

I am having a similar problem, the image displays correctly in windows and IrfanView but is rotated in FH, see attachments of photo with EXIF data and multimedia window from FH.
Any further ideas?
Regards
Graham

Mike,
Excellent job see attachment. With a handful of exceptions the only UDF tags left now are _APID or APID (Military service) ones which can stay. Thanks very much for your help.
Regards
Graham

MIke, I fear I may have given you duff information about exactly where the tags were. I took a backup, ran the plugin, the notes didn't appear where I expected, so I undid the changes, and took a look at the ged file with notebook++ I have attached the results below. The _UNCAT tags seem to be under...

Mike,
adapting your plugin sounds like a great idea, I looked in the plugin store but couldn't find it, could you let me have a link please.
Regards
Graham

Adrian,
I think any marriage source which doesn't directly link the spouses would trigger this issue. I think my separate issue with duplicates was a failure to match to a preexisting marriage, for example when a full date was present and was not matched to a quarter date.
Regards
Graham

Mike, I added date filters to be safer, and that seemed to work, the top level census records are now in place :D I am now left with the relationship information which shows up as exceptions for example:- Record Type=Individual. Gedcom Id=P10. Record Number=10. l.321 - INFO ONLY: Detected & fixed fi...

Moving on from the Marriage discussion, the first few exceptions now look like this --------------------------------------------------------- Record Type=Individual. Gedcom Id=P7. Record Number=7. l.192 - INFO ONLY: Detected & fixed field format error (data loaded using Uncategorised Data Field): "1...

Adrian, please read my earlier post. I have removed all 48 Marriage related errors in Ancestry by ensuring there were two people linked to each marriage event by selecting a spouse (if necessary create one first), it did not then generate erroneous Marriage tags in the Individual record. Regards Gra...

Mike,
Excellent! You cited your evidence, Ancestry has got its marriage events wrong.
Regards
Graham

Marriage event exceptions. I have now resolved all of these (48 across 1120 people), having two marriage events for one actual marriage is an issue, but not what causes the exception. The exception is caused by not selecting the spouse in the marriage event, this is done automatically in Ancestry f...

I have found another type of anomaly, If a birth has entry has a description (see screenshot attached) this throws up the following exception: Record Type=Individual. Gedcom Id=P7. Record Number=7. l.224 - INFO ONLY: Detected & fixed field format error (data loaded using Uncategorised Data Field): "...

Mervyn, Thanks for the advice, I did already know how to fix the Ancestry marriages (I did it the other way around by looking at the fact I wanted to keep and associating the source, then deleting the redundant fact), normally I would have spotted this sooner, but I wasn't giving this tree my full a...

MIke, looking at the ones I posted, it is worse than that, there are actually two marriages erroneously recorded for this person, one from the marriage index, the other from family information (see screen shot) This might explain why one is against the individual as there is no spouse linked, so wha...

Mike, On the marriage events see screenshot below, the fact is correct but the citation has no information at all (despite the fact that this information is viewable on Ancestry including district, page etc. This is the raw output in the Ancestry ged file in notebook++ for this individual (too long ...

Mike, On the census data citations (See attached image) each census year has only one source, but the source reference is correct for this method, but the date is missing, as is the assessment. possible steps are: Step 1 fill in the date given the source Step 2 fill in the assessment to "Primary evi...

Mike, with no new fact sets and Unrecognised data not moved to comments I get this in imported extensions:- Individual Record 59: Converted tag '_MILT' to attribute 'Military Service' for about 20 records I also get quite a lot of exception reports starting with :- Family Historian Exception Report ...

Mike,
it was the original ged file downloaded from Ancestry
With 6.2.5 does the advice about not moving data to notes fields still apply or should I just restore defaults and import?
Regards
Graham

Mike, I have followed the instructions up to installing the "import from Ancestry or FTM plugin", when I ran this I got an error fhSetValueAsDate(ptr,datItem) failed INDI1.MARR.DATE in record ID 1 , followed by may other function failures on the same record field Any guesses as to what may be wrong?...

I couldn't spot any specific mention of 6.2 in the Ancestry import KB advice (I don't have FTM), does 6.2 change anything relevant?