Family Historian User Group

So if someone is making extensive use of a particular application to manage their genealogical tasks where the application has a particular function that marks it out as different to the run of the mill to do list, could they add details? I was using a combination of "My Tasks" in Microso...

Untill the entire process and the symptoms you describe are repeatable no solution can be devised. Hi Mike Let's put this problem to one side for the moment. There were only the handful of instances of the problem in the dataset, so I have amended those manually. I have now moved on to checking far...

Hi Mike I am fairly sure that this is the Pre-Load Source Clean file that you require. Thanks. Paul 1 NAME William Banfield Gallway /FRIFT/ 1 SEX M 1 ADDR William Banfield Gallway FRIFT 2 CONT (1841) - Manuden Street 2 CONT Manuden 2 CONT Essex 1 BIRT 2 DATE 1817 2 PLAC Falmouth Cornwall 1 BAPM 2 DA...

I'm confused (again)! Your relevant snippets show: Original Gedcom :- 1 OCCU 1841 - Coach Maker 1 OCCU 1851 & 1871 - Coachbody Maker 1 OCCU 1861 & 1873 - Coachmaker 1 OCCU 1873 - Wheelwright Pre-Load Source Clean Gedcom (showing just the OCCU facts derived from above) :- 1 OCCU Coach Maker ...

That problem with importing & is unexpected. Please post a sample snippet of Generations GEDCOM as exported from Generations and used as import to FH after the Generations Pre-Load Source Clean plugin showing the Occupation : 1881 & 1891 Coal Miner text. Hi Mike "Coal Miner" was a...

To be honest, I was expecting feedback & questions for Fixing Dates and Date Phrases and Check Project Statistics & Exceptions, so did not want to muddy the waters with the plugin for Cause of Death. I have added the Cause of Death conversion to the Generations Fact Fixes plugin Version 0.2...

Review Cause of Death facts. Rather than having a separate Fact, conventionally the Cause of Death is recorded in the Death event in its Cause field. If you only have a handful of Cause of Death facts then each text value can be manually moved to the Death event Cause field and the Cause of Death f...

The remaining two steps are: FHUG Knowledge Base Fixing Dates and Date Phrases which repairs malformed Date fields in Facts. Just run the Find Date Phrases plugin, and the Fix Date Fields plugin, then review what is still malformed if anything. FHUG Knowledge Base Check Project Statistics & Exc...

Review Cause of Death facts. Rather than having a separate Fact, conventionally the Cause of Death is recorded in the Death event in its Cause field. If you only have a handful of Cause of Death facts then each text value can be manually moved to the Death event Cause field and the Cause of Death f...

The 0 Links means nothing is linked to them. Since there are no @N anywhere, we have not overlooked any 'broken' links. So those 27 Note records can be deleted, unless they contain anything you need to keep. See FHUG Knowledge Base Delete One or Many Records for how to delete them. Good morning Mik...

Assuming that fixed all the cases it is designed to fix we are now onto the four tidying up steps. So the first step is to open the Records Window and in the Notes tab review the Links column. Are they mostly if not all 0 ? Use Edit > Find... , enter Search For: @N and ensure only these three are t...

tatewise wrote: ↑03 Apr 2022 14:05
I had assumed you had run Generations Fact Fixes on each imported dataset after using Change Any Fact Set.

Hi Mike

Yes, I had run it at that point !

Thanks.

Paul

There are a few more tidying up steps that can be usefully performed: Delete any unused records, such as Note records with no Links Review Cause of Death facts Fixing Dates and Date Phrases Check Project Statistics & Exceptions Hi Mike You produced a new plugin at 1 April 2022 at 14.12 :- "...

Since there have been no UDF associated with Source Citations I suspect you don't have that problem, so let us assume you can bypass that advice. That is not surprising since none of your screenshots has shown any evidence of any Source Citations at all. Hi Mike That's another skeleton in the cupbo...

I can't wait :D Hello Mike Yesterday, I imported nine further Generations datasets into FH, comprising of tens of thousands of individuals. After the usual use of plugins, I completely cleared all of my UDF lists, and I was left with a total of 27 stray notes, which I felt was a very acceptable out...

I have decided to fix the Probate (INDI.PROB) Note problem as it is imported currently using a plugin. The other two plugin fixes I provided earlier have been combined with this third fix into one new plugin. It now also produces a Result Set of all the conversions it performs so you can review the...

Events ~ Probate Notes ~ Probate Events ~ Travel Notes ~ Travel Those pairs could be assigned the same GEDCOM Tag so that they merge into one fact in FH if that is appropriate. Probate GEDCOM Tag PROB is a Standard GEDCOM Event. "An event of judicial determination of the validity of a will. Ma...

Hello Mike and thanks for that This is one individual :- 0 @I2@ INDI 1 NAME Elizabeth /BANFIELD/ 1 SEX F 1 ADDR Elizabeth BANFIELD 2 CONT (1841) - Leicester Square 2 CONT St Anne Soho 2 CONT Westminster 1 BIRT 2 DATE 1789 2 PLAC St Anthony Cornwall 1 DEAT 2 DATE 8 JUL 1869 2 PLAC Harrow on the Hill ...

Hello Mike I am pleased to say that you won't need to work "blind". For practice, I have actually imported that dataset into FH twice, but as two different projects with two different names. I have manually corrected the probate problem in one of those projects, but have kept the errors in...

Probate Since there are only three facts, they can be fixed manually... Copy & Paste the date part of the Note Text into the Date box of the Probate fact on the Facts tab of the Property Box. Copy & Paste the remainder of the Note Text into the Note box of the Probate fact on the Facts tab ...

Good evening Mike and Ken I think that it is fair to say that my objective is to safely and accurately move all of my data from Generations from FH, and to import it into FH in a format that will facilitate a subsequent tidying-up exercise. It is a job that I should have undertaken some time ago, bu...

Licence The problem is caused by the Licence fact being created as an Event instead of an Attribute. So there is nowhere for the Change Any Fact Tag plugin to put the 'value' 1st wedding - Yes . Therefore the plugin saves that 'value' in the Source Note. If you are happy for the Licence fact to rem...

Probate Since there are only three facts, they can be fixed manually... Copy & Paste the date part of the Note Text into the Date box of the Probate fact on the Facts tab of the Property Box. Copy & Paste the remainder of the Note Text into the Note box of the Probate fact on the Facts tab ...

Hello Mike I've spent most of the day assigning Gedcom tags, exporting. importing and the like on various different datasets. This seems to have been successful, although I have a good deal more visual checking to do. However, I have hit two problems involving data arriving in FH, but with FH not ne...

Since there are only two events, I suspect it will be easier to delete those two Individual 'Divorce' UDF and manually create a standard Family Divorce fact for the couple as I mentioned earlier. ( I assume the two UDF are for the two people who were divorced. ) The things you referred to as missin...