Family Historian User Group

ADDR: Unless I'm losing it more than I already recognise, FTM does not even have an ADDR field for INDI and FAM. It's Facts simply comprise a Date, Place and Description (with note, sour, obje etc.) this latter being the famous Value. This Description is where an attribute Value displays and where a...

Other things: An FH or plugin Gedcom contains "1 _STAT Unmarried Couple" and as expected this displays in FTM as a _STAT event (bad cursor issue) with a value of "Unmarried Couple". We FH people therefore regard _STAT as an attribute. However, not surprisingly it gets exported as: 1 EVEN Unmarried C...

OK, thanks. I will try to remember where I was at but am having to track back so hope I'm not getting confused. Let me share my thinking and see if you agree. FH's concept of attributes is that they have a value whereas an FH event does not. Attributes and Events differ in FH but are all simply Fact...

Good news....! 2) Thanks 16/18) Mostly yes but I may not fully understand "FH custom _ATTRibute becomes EVENt with ADDRess value, and _ATTRibute value moved to labelled NOTE". I can't remember now what FTM does exactly but surely if it's an attribute (custom or not) the value should go to value and ...

Rssults on 20) REPO fields Import file: 0 @R1@ REPO 1 NAME Lexicon verfolgter Musiker und Musikerinnen (Hamburg Uni musicians database) 1 EMAIL http://www.lexm.uni-hamburg.de/content/below/index.xml 1 EMAIL second email 1 PHON Phone1 1 PHON Phone2 1 ADDR Address1 1 ADDR Address2 1 NOTE @N99999@ Disp...

2) I haven't seen other problems and don't know the spec but I do understand why a 2 SOUR and children would be odd appearing in the middle of a NOTE and its CONC/CONTs. I'd don't want to bash the FTM guys too much :) 16/18) Yes in a word. The exception (which we ignore) is DEAT, CAUS which FTM does...

REPO data is maximised as follows (both export and reimport checked): NAME 388 chars of data ADDR 945 chars EMAIL 566 chars PHON 496 chars Will try CrLf in the address: results, separate lines can be entered but on export CrLf do not exist, CONT records do not exist and on reimport the field display...

Sorry when things change along the way...its not a straight path...trying to avoid frustrations... 16 and 18) I'll try to clarify ADDR and FTM's use of CAUS. For DEAT it creates a CAUS event which on export it puts back as a sub tag of the DEAT event - no action required. On DIV, CAUS it does nothin...

If I am correct, it's because the NAME details being moved to the 1 NOTE need to be written before any citation for that 1 NOTE? The issue lies in these lines for an INDI: 1 NOTE Studied under Schradieck (Hamburg and Leipzig), Joachim and Wieniawski (Berlin). Gave Paul Dessau his first violin when a...

Mike...not been through your response yet because struggling with number 2, the import errors. Looking for clues... I get: Line 1251: error 8 : "CONT" subordinated to wrong item. Line ignored. It occurs 24 times. I presumed it found 24 items together at that file position however when it runs it qui...

Thanks for the input Adrian and Peter. Peter, yes I agree your description although looking again at the underlying data we're going to have to work out some terminology. I'll try to define some if I may... FTM labels the middle top as Source Citations so we'll go with that. A Source can have multip...

I'm building up this test list with a few comments so it's a WIP. OK:FTM does not like files without BOM - a matter for user instructions ?:Line 1251: error 8 : "CONT" subordinated to wrong item. Line ignored. It appeared 24 times against the same line so in one place only. Investigating what this i...

This is the Sources screen to help elaborate on the different use of Citations in FTM. citations.png This sources screen has four panels: On the left is a list of Sources. Top middle are the Citations for the selected Source. Bottom middle are the events cited by the Citation. Right are the text det...

Wow! A lot of enhancements. I've been buried in dealing with hints and am winning slowly. In the process I've learnt a little more about citations which I will write up soon. Give me a little time and I'll run thru all your hard work and comment properly. Its sounding good !

OK yes that explains their use of RESI.

Yes method 2, those are all sources. I exported FTM to FH and ran a source query then pasted.

One thing I mention elsewhere once but not above is that FTM doesn't import Census events. Potentially there is a data loss here (attached notes, objects etc). OK almost understood...it seems to group into separate databases. Here are some sources: "Connecticut, Marriage Index, 1959-2012" "England &...

Thanks Mike. I tend to refer to Census when thinking about citations because I regard them as more complicated than some other citations purely because one document affects several people. I don't wish to exclude BMD or any other citation in doing so. As far as the document>citation>event relationsh...

The matter of the Citation Reference Note needs discussion before I clutter the KB with information and proposed solutions. I don't know all the facts but hopefully have sufficient to set out the issue and get assistance with a solution. The rough outline follows (corrections welcome): Citations are...

Thanks Mike. As you can imagine the first issue was a pain to find and remains a pain to address. I am concerned what else FTM "secretly" does differently with it's own data...some things may be useful, some an obstruction and certainly this is not consistent GEDCOM handling ! I am also without a so...

Mike, as mentioned, with round trip in mind, at Step 6 of the KB I have tried to identify NOTE and other interesting records that FTM handles. Alongside I mentioned observations about the way these are exported from FTM. I have just started looking at the way such FTM data is imported as this might ...

Ah ha so you are still moving ADDR (1st line) to value...and also dealing with complex addresses, indeed all data using a note...

Best of both...thanks.

Thanks for the info...only one matter really: Moving ADDR (etc.) to the note works, however, the way FTM presents data makes the Description field (Value) an ideal place for it where possible. Conversely, I support the desire to store perhaps ALL necessary FH fields in a note and in manner that can ...

Adrian

Thanks for letting us know about this - I noted anomalies too.

With the "place" aspect of what we are trying to do at least users have some choice. Either fit in with Ancestry however imperfect, or use the structured leading comma approach in FH. I'm undecided...do you have any advice...?

I see no signs of dim ! Please remember I am not documenting solutions. I am documenting at the earliest opportunity and for discussion my observations and enhancing these until they hopefully become solutions at some point later. Yes clearly we need to put data in a note first, this being the prefe...

Mike, I've looked into local NOTE and NOTE record usage for the round trip - see at the bottom of KB Step 6. In summary it looks like we can note data on the 0 INDI, 0 FAM, 1 Event, 2 Citation, 0 OBJE, 0 SOUR but not REPO or _PLAC.