Family Historian User Group

Mike, Sorry if my last answer was too cryptic. Bottom line is all is OK. I had recently put in the 'died' event for 40 or so individuals, and apparently exported after saving, but didn't exit and reopen FH. Thanks for explaining how this happened. Usually 'saving' your work is sufficient, but in thi...

Mike, Sorry, I thought I had noted it, but obviously I didn't, that my snippets were from the exported file, not FH's data file. Indeed the DEAT Y is in the fh_data file, but it is was not carried forward to the exported file from that first time running the plugin. I was certain I 'saved' the file ...

These folks were added in several sessions several days ago.

I always saved before exiting FH, and had reopended FH several times after that. And have exported several times as well.

I will be out for an hour or so.


Ron

An example: 0 @I15355@ INDI 1 NAME ludmilla // 1 SEX F 1 DEAT 1 FAMS @F5104@ More examples from gedcom 1 FAMC @F4787@ 0 @I15348@ INDI 1 NAME Ulric /Urban/ 1 SEX M 1 DEAT 1 FAMS @F5469@ 0 @I15349@ INDI 1 NAME Andrea /Schwartz/ 1 SEX M 1 DEAT 1 FAMS @F5470@ 0 @I15350@ INDI 1 NAME Ursula // 1 SEX F 1 D...

Hi Tatewise! Way back when, did testing with you on the TNG import requirements and it has worked very well for me. It is evident this is an issue in FH, not your plugin. Yes, I have opened and closed (and saved) sessions in FH many times. Can I fix this with a Search and Replace somehow? However, t...

My first post in two years! Using the latest 'Export Gedcom File' with unchanged export parameters and noticed something has changed. Before, creating a fact of 'death' without any date would cause a DEAT 'Y' record to be exported. Now I see that the DEAT record is blank. This is causing TNG to assu...

Glad I could be of help debugging; sorry I took an indirect approach to show results first time.

OK, so I compared the Project Gedcoms, doing a Gedcom backup before the Cleanup Notes 1.2 execution. The results are essentially the same, with several citations to notes being dropped. The changes otherwise so minor, that I will likely not use this plugin if it has this peculiar result. The BEF is ...

Thanks Mike, yes I took that route to see TNG impact. And if nothing else has changed but the running of Cleanup Notes 1.2, wouldn't the export comparision of changes be caused by that?

I will compare the project gedcom, but I expect the same or similar results.

Sorry, you're right; I should have included that information. Target was TNG, and the snapshots were showing differences in output using the lastest Export Gedcom File V4.3, before and after the installation and run of Cleanup Notes. 1.2. I could run again to confirm if necessary.

Hi Jane, It wasn't notes that were lost, but a few citations to notes. I wasn't sure how to send files to you on FHUG. Clicking email doesn't seem to permit it. I have inserted an image of all differences from BeyondCompare of both exported gedcoms, which isn't of much use without the actual files, ...

I did a a test of Cleanup Notes 1.2 just released for FH 7. and did an export immediately after. I then compared a gedcom exported before and after running the plugin. The results were identical, except, several source citations to local notes were inexplicably removed from the output, so I have rev...

OK, thanks for clarifying. I neglected to mention the consistency error '@title' mismatch I was getting. I will rethink my approach. Thanks for the clarification. However, I will note that the uppercased name 4.3 version still found the proper .dat settings, because I compared with what I had in my ...

OK Mike, Thanks will no longer use the dot in the rename and see how that goes. You say only your plugins, so I take it only your plugins are written to ignore the version portion in the name (up to the dot) and thus load the proper prior plugin .dat settings. So with this procedure I need not renam...

I downloaded the just release v4.3. I first renamed the v4.2 plugin by putting '-V4.2' in its name, then inserted v4.3 in the fh_lua folder. The settings appear to have been preserved from 4.2 so ran the plugin. Then next loaded the renamed V4.2 plugin, but found that many of the settings had change...

Congrats to you Mike on the milestone! About 5 years ago, as a longtime LFT (LegacyFamiltyTree) user exporting to a TNG (The Next Generation) website, I was looking around for a new approach in PC-based genealogy software and decided on FH. I was impressed with it, but now needed to export to TNG fr...

Mike, I see you released Export Gedcom File V4.2 and I have tested it out with both LFT and TNG options. Not that it seems to have affected the resulting import, but I was just curious why, for LFT, the gedcom record "1 form jpg " was changed to "1 form jpeg ". I did note the TNG option gedcom was a...

Mike,

Perhaps still an FH7 work in progress, but in the Plugin Store for the Export Gedcom File, this link returns an error:
(+) Full Data and (-) Brief Data offer two levels of data export as explained in the GEDCOM Export Mode advice.

Is that the best order for users, or would it be better to put Import Details immediately after the Introduction, with the technical Export Details later? I guess in sequence of process, it should be after the Introduction. But in planning, the export details need be studied before importing. So, s...

I ran a test and confirmed the new prefix assignment to import option in TNG 13 works. The import process successfully altered all person records from 'I' to 'P'.

tatewise wrote: ↑

06 Jan 2021 14:49

Two things.

1. If I modified the Export Gedcom File file to use P instead of I it would be a user-configurable option.
   I am disappointed you would think otherwise.

Are you addressing Paul, or myself? I don't believe I gave any reason for disappointment, did I?

With confirmation from TNG's author, the problem was resolved on the TNG side, apparently, by T NG v13 , released this fall. I missed a item in the version enhancement list which indicates a new tick box option was provided in Admin:Setup:Import Settings to have the Admin:Setup:Prefix setting assign...

Hi Paul, But without a TNG script modification (which appears to hardcode 'I' and not use the Admin setting variable), and with a setting of 'P', TNG will still leaves unaltered, the incoming gedcom 'individual records' as 'I', or whatever they might be. I have posted a code suggestion on the TNG fo...

Mike and RonK Before you go changing anything, I have been importing gedcoms from FH for over 15 years with 'replace all' You can set TNG to I or anything else. see Mike, hold off changing those help areas until we get clarification and agreement on what happens in the TNG import process with the p...

Mike, TNG lets one assign a prefix, but only on data entry, not on import. It was just a long shot question. Not so important as to make a change to Export Gedcom plugin just for me. I changed to 'P' prefix a couple years ago, never thought to ask you about it. LegacyFamilyTree, my prior PC genealog...