Family Historian User Group

I have only just started using FH and slowly getting to grips with its excellent features.

Exploring a newly generated UDF report, it seems most of the problems involve the use of CONC fields associated with SOUR data

e.g.
In FTM12, my citation detail: reads " London Metropolitan Archives, Saint John, Battersea, Register of marriages, P70/JN, Item 010"
Which results in the following entries in the exported GEDCOM:

1 NAME William Thomas /WEBB/
2 SOUR @S6@
3 PAGE London Metropolitan Archives, Saint John, Battersea, Register of
4 CONC marriages, P70/JN, Item 010

Q1. Is there a text limit on PAGE? If not, why isn't CONC being applied on import?
Q2. After editing the relevant source details in FH to correct this, how does one remove the actual UDF's? They don't seem to appear in the individuals property box.

Mike

Mike, the FTM export is misusing the Where Within Source (PAGE) field, which in GEDCOM does NOT allow CONC or CONT tags, that are only allowed on a limited class of long-text fields such as Note (NOTE), Address (ADDR), Text From Source (TEXT), Author (AUTH), Publication Info (PUBL), and Note Records (TEXT).

See how_to:handling_unrecognised_data_fields|> Handling Unrecognised Data Fields for advice on handling UDF such as they are visible in the Property Box on the All tab, and can be listed by the Unidentified Data Fields (UDF) List Plugin that allows them to be easily bulk deleted from its Result Set.

I don't think FH applies a text limit on the PAGE tag, although the GEDCOM specification does impose line length limits.

I presume you have seen how_to:import_from_family_tree_maker|> Import from Family Tree Maker (FTM) but I do not know if FTM has any option to inhibit text fields being CONCatenated.

Mike,

Thanks for that. I knew they must have been imported somewhere, just couldn't see where.

As the data that is 'unknown' is important, I won't be going down the bulk deletion path, but will be correcting and deleting them as I go.

Thanks