Family Historian User Group

Use of Description field for Address and Value etc.: 2) I forgot valueless attributes also needs a line in the note! Perhaps the Attrib/Event indicator in the note can be subtle. I don't know...maybe a 1 char prefix like "~" or wrap the heading in {}...just a minor preference over putting ATTR or wh...

PLACe records...thinking aloud. The objective is purely to preserve FH data because FTM has no Place record. The FH data to preserve is Place name (which matches with the place tag in a Fact Note for example), lat/long, STAN and links/tags for media and notes. While FH has place records, I understan...

Use of Description field for Address and Value etc.: 2) What I am proposing is that the note always contains the address and value for consistency. We regard the note as master data not the Description. To differentiate, we put an indicator (such as _ATTR) in the note not in the Description (where i...

Mike, I see you've taken time to respond carefully to several areas in the KB Step 2. Your explanations and some sleep make it easier to focus so I've edited the KB a little where its easy, and where more words are required I've replied below to seek your thoughts. Use of Description field for Addre...

I now understand how you wish to preserve list data. Create a note containing references to list members and attach each member to this note. A couple of questions and feedback: There is only one 0 Note display field in FTM so all 0 NOTES are displayed together which is untidy (see below). One big n...

Yes I suppose disabling may be too radical. Yes it's true I suggested the "" vs ALIA option. I can never decide to be hard nosed or easy-going ! The option is a good idea because the name may get too long. The two additions sound good...without checking let's assumes FTM rejects everything it has no...

The presentation order and ideas for merging certain options are certainly tidier as far as an FTM export is concerned but this is a general export and I understand the compromises. Actually, we are very nearly telling users to take the FTM 2014 defaults on Tab 2 (PLAC records being the exception fo...

OK understood and very possibly true...

...I've noted at the base of KB Step 2 what we currently know and what we need to investigate before solving. I'm going to tie up loose ends first.

OK thought there was a KB lock problem...will continue with this media link investigation, then complete the testing and editing with KB then the new posting.

Interesting, either I am wrong or this is the cause of his problem...he should open the GEDCOM and check paths to be sure... WRONG: So far, all I can see is one can "link to existing media" or "add new media". The former is like FH. The latter (also similar to FH) lets you select a file from any fol...

I can't seem to edit KB Step 2, locked by tatewise but the 15 minute limit never ends....?

Glad to hear that being a pain is also motivating :) I'll get the new version and work thru. I'll try to check which fact tags now appear using recent posts and KB step 2 as a guide and for feedback. I'm quite certain this plugin and the others are much appreciated even if people don't understand fu...

Oh that's good news then..a couple are new to me. As a start, I would always put CAUS in the note. (B) For DEAT we should keep the tag line (so A and B). When the tag exists a CAUS event is created by FTM but on export I believe FTM puts it back as a CAUS child of DEAT. The tag line is OK and I pres...

Mike, I am following your lead in suggesting use of the note for all data that FTM has not got a specific field for and agree this is the simplest way. Remember my main input is researching FTM and trying to tell you what it has and has not got in the way of fields. As we know, FH's other data has t...

Rather than clutter the KB, here is brief feedback on "Fact tags" other than DATE, PLAC, Value and NOTE like email, web and phone. Given the plugin's default FTM options we get the following. Much as the options would suggest: 0 @I4548@ INDI 1 NAME 0 Fake person for source citations /?/ 1 EVEN Conta...

OK thanks...I'll pay attention to speed on future runs...

I'm using KB section 2 to organise my testing and to gradually provide feedback. Some restructuring of this page should make it simpler and potentially allow details and feedback on translation processing for which there are no options. I have set tab 2 back to the defaults for FTM (which we might d...

Mike, excellent news...it's a bit late at night for me now but I'll grab it tomorrow and start running thru. I took the step of moving my own data to Ancestry a little while ago. On one hand, I've made great progress with hints and citations and must say, I just cannot understand how anyone with any...

Citation note: I am hoping this export then re-export explains. This is an FTM Export: 0 @I2@ INDI 1 NAME Father /Smith/ Suffix 2 NOTE @N7@ 2 SOUR @S1@ 3 PAGE Citation Detail 3 DATA 4 TEXT Citation Text 3 _FOOT Reference Note Source Author, Source 1 Title (Source Publisher 4 CONC Location, Source Pu...

As far as I can see, citations can only be based on 2 SOUR (an event) not 1 SOUR (an INDI or FAM). Consequently, I demoted INDI citations to the first NAME but this is not possible with FAM as there are no guaranteed Facts which is why the fake Fact idea came up. If we have to create such a fact for...

Mike, would it be possible to deal with NICK and _USED as an option...either to the NAME in quotes or to ALIA.

The reason I say this is that the NAME might get too long to present well...a choice would be better?

Thanks Mike, good news...I'll take a little pause for breath then the opportunity to use FTM a little more and see what other topics we've might need to consider...not much I suspect although as round-tripping becomes more likely I start to think about the data we can't hold in FTM. I don;t yet unde...

I am starting to get more tired than I should be due to other matters so I hope I've addressed things sufficiently. Addresses, OK understood, duplication could go...address in note only. The alternative is to provide an option...if users want better visibility of address they can opt for the duplica...

Thanks Mike. I think we are getting close now, agreeing common terminology, determining how FTM works and deciding how best to approach things takes a little thought. We want simple rules if possible, to minimise exceptions and to make usability as straightforward as possible. I'm still considering ...

Yes FTM appears to import and export as we expected so we have control over its limited fields...we just need to make choices (or leave it as it is with one correction below). FH Plugin exports: 0 @I4548@ INDI 1 NAME 0 Fake person for source citations /?/ 1 EVEN Contact Value 2 TYPE Contact 2 DATE 1...