Family Historian User Group

Good news and a lot of work...I hope it has simplified things, for the future also...I'll take a good look and get back...BTW I think "pretty tags" is a marketing concept worthy of copyright :) Initial Observations: I note the improved grouping of extra options and indeed the change of defaults...I ...

I think the two options is what I am suggesting as option A and B - pretty versus return trip. The only difference is the level/tags are replaced by pretty text using a translation table. The same processing everywhere else...just a final lookup on moving to the note. Actually the two options might ...

A further test: What went in: 0 @I3525@ INDI 1 NAME Ian Gerald /Smith/ 2 SOUR Source 1 2 NOTE Note 1 2 SOUR Source 2 2 NOTE Note 2 2 NOTE @N11@ 2 SOUR @S218@ 2 SOUR Source 3 2 NOTE Note 3 2 SOUR @S218@ 2 SOUR Source 4 2 NOTE @N13@ 2 NOTE Note 4 1 SEX M 1 BIRT 2 SOUR Source 1 2 NOTE Note 1 2 SOUR Sou...

Mike...thinking further about the simpler way of preserving data... ...this very simple approach works well for users wishing to employ FTM for matches then return data to FH. However, the lack of pretty formatting compromises those wishing to simply move to FTM or use Ancestry for presentation purp...

Had a quick look at your idea...need to think a little but fully support anything that is simpler to code, explain, deal with the unexpected... ...in essence I take it that all FH data (for INDI, FAM indeed all appropriate record types) will go in a note and then, where FTM has an appropriate field,...

Here are the test results - will get to your latest message shortly. In summary, Fact citations and Fact Notes work whereas citations and notes attached to Fact, Plac do not. WHAT WENT IN 0 @I3525@ INDI 1 NAME Ian Gerald /Smith/ 1 SEX M 1 BIRT 2 SOUR This is a local SOUR tag under 1 BIRT 2 NOTE This...

Synthetic Sources: I think changing the default on ROOT is a good idea. As far as all defaults are concerned my thinking is to try to preserve all the data users might want on the basis few read the small print! I think documenting clearly that Named Lists can be excluded and the simple rule that on...

I think the use of Source records to hold the data works well. As far as presentation is concerned it is a shame that Source records without a citation result in disabled Links, Notes and Media tabs. One can still double click the source to the record. This is the reason I manually linked my sources...

OK as long as you know what's happening and are happy...thanks.

I've looked at the links (citations) to the omega sources using the latest plugin with the Source warning record. The sources with links are: File Root Named List (when there are list members) Place Rec (only Spouse Sealing Place works FAM, SLGS - no others) The sources without links are: Place Rec ...

Please refer to KB Step 2. [ MIKE's comments in brackets. ] UDF The currently known issues resulting in UDF when importing from FTM to FH are few and as follows: REPO, EMAIL and then CONC child tags on REPO, NAME and REPO, PHON and REPO, EMAIL and INDI, OCCU and INDI, EDUC. [ CONC & maybe CONT can p...

OK, sounds comprehensive = a lot of work done by you and a lot of testing and some documentation required now! I'll try to address it over the next day or three. Surely, there's not much that doesn't export now?

The notes below are intended to respond to the questions regarding INDI, RFN also INDI & FAM, SUBM also FAMC, PEDI. Also I added 2 FAMCs - I happen to know links to several parents can occur in FTM. I think we already know SUBM and SUBN data does not appear to import to FTM. Plugin exported (edited)...

Sorry for a late reply...I'm sure the posting was shorter when I first looked... Thanks for feedback on SUBN. Some overkill there I think! Yes REFN to record note for consistency sounds good. There are three matters I need to learn about and investigate...what is the UDF matter? Your info regarding ...

Of course Jane you are right...yes using Save Diagram As...PDF...I've reduce the zoom to 25% and it fits...many thanks...

In Family Tree Maker it is possible to export a chart to a one page PDF. In FH this only occurs when the output is relatively small otherwise it becomes a multi-page PDF. A multipage PDF makes navigating a chart more difficult and less pleasant to read. Perhaps FTM's PDF handler ir more capable that...

SUBM/SUBN - summary: it appears FTM does nothing although it throws import errors. 2 SUBM records created and 2 SUBN records created both with links to the first SUBM. The 2 SUBMs exported but only 1 SUBN. Notably it appears FH allows creation of multiple SUMN but only saves one to the GEDCOM. I not...

Ah ha...most interesting - known issue...I'll run the query. EDIT: the download link fails. The alternative is use the All Facts query, add CAUSe field, exclude is %FACT.CAUS% is nul - also exclude DIV and DEAT events if you wish...I simply sorted the output. MIKE'S EDIT: I have informed Jane about ...

You mentioned the long list of further enhancements in progress...good news. I look forward to testing and seeing them in action. I try to ensure that all known development matters are at least listed in KB Step 2 rather than scattered around the forum where they may have been discussed, sometimes i...

This is strange but here is the data from the Plugin then FH. The first observation is that there is a CAUS tag against BIRT in the FH Gedcom so it's not the plugin. This tag also displays in FH's expanded record list yet I couldn't create a CAUS there if I tried. Clearly there has been an earlier d...

Yes I see the contradiction...can't remember, will check.

Its late so I'll get to running thru the list and KB step 2 with a fresh head on Tuesday - sound good tho. I guarantee we've missed several things...we should foresee the unforeseeable. For testing I use a copy or two of my live data and add additional data to it for testing, FTM is OK with several ...

I've found the cause of death appearing not only as it should (event and note) but also as the cause in a note against their spouses birth event. Notably the position of the spouse was one before the person with the valid cause.

I wonder if this just affects cause of death.

Use of Description field for Address and Value etc
I'm responding to a point I thought you made and just can't imagine what you think I'm trying to get you into. Let me know if you want my phone number.

Yes its hard sometimes :) Simpler on the phone if necessary. Plenty of room for misunderstandings, frustrations and lack of answers...just the way it is. Despite almost obsessive input of time not everything is certain or tested - and nobody has all the answers. It's just you and me, unforeseen obst...