Family Historian User Group

Graham I suspect that this plugin is no longer supported and has been effectively replaced by Civil Registration Index in version 7 of Family Historian. Before you can use this plugin, you need to import (at least) the Civil Registration Index source template from the Essentials Collection (see Sour...

I've still continued to use this Add GRO Source plugin (1.3.4). On later death entries in the index it gives the actual date of birth as informed at the time of registration. Can this field be added to the plugin to create a corresponding birth fact in addition to the age field? Thanks, Graham Grah...

Thanks Mike

It all makes sense now.

I guess that when adding a new Civil Registration you are choosing Create Source... or Add New Source...? That will create another Source Record but with all the same details (as if it were a Method 1 'splitter' style). You should only do that the first time you are creating an entry for a new Type...

Mike The 'Record Civil Registration Data (UK)' plugin DEA is designed to work with Source Template 'Civil Registration Index' which uses the Method 2 'lumper' structure where there is only one Source Record for a particular type of registration (Birth, Marriage, Death, Divorce), particular Country, ...

I was working on the assumption that the best way to record Birth civil registration data was by using the Civil Registration Data (UK) plugin. This seems to favour Method 1 (Splitter) for citing sources. Following the Knowledge Base page for citing sources, method 2 seems to be more appropriate, si...

I have enhanced my original probate plugin to handle the UK Civil Registration data for birth, death and marriages UK; probate index and simple Baptism Registers. I tried the Record Civil Registration Data (UK) and Ancestral Sources, but with the limited information provided in these registers, a si...

When I posted my probate plugin, it was a 'work in progress' and lacked a degree of error checking; hence I suspect the errors that Teresa has experienced. I am pleased that David has managed to use my original code and adapted that to something that is his own personal style. I have expanded on my ...

Firstly to David I am glad that you was able to adapt it to meet your needs. It also has resulted in a response of other posts. To Nick, I would say that ancestral sources was the inspiration to my plugin. As he says there is a variety of ways that people will want to deal with the information they ...

Following from what Mike Tate said earlier: "This type of Standard Plugin combines the Source Preparation process and the DEA Plugin into one sequence of dialogues, but it might be worth discussing the pros and cons of the two approaches." considering to offer as a plugin in the plugin store is, at ...

David I am not sure why 2 sources were created. Because the plugin is designed for my needs, I know what fields I need to complete to get it working as I want it. There is no validation at this stage, so inevitably there may be bugs. There should 'know' all the places so that when you type into the ...

My background was in developing computer software to simplify data entry. The inspiration comes from Ancestral Sources. There isn't a 'probate' option in Ancestral Sources, or one in the plugin store, so I thought maybe a plug in could help me. Why not a Data Entry Assistant; that seems to rely on c...

Have replaced script header, hopefully correctly.

Attached is the code file.

continued:
The contents of the dialog form are added to the Text from Source in the source record: The source code is attached;

Is this of any interest to others?

Norman

I have been writing a plugin to record information from the probate record index in a simple one stage operation. Taking the source text from the probate index: Probate.jpg This information is recorded in a dialog form: Dialog.jpg Which then raises the appropriate probate, death and residence facts/...

Thanks for all your advice and encouragement. I now have a functional plugin that can create a probate event and, if appropriate, add the residence at time of death and add/update the death fact. It generates a source/citation record and links them into the the relevant fact/events. The input is via...

Thanks for your help/advice.

I have managed to get the source/citation records added and linked to the probate event and the death fact if appropriate.

This has been a good learning experience as well as being of practical use.

Thanks for this. As always, your knowledge and advice is invaluable. With many years writing software, my approach to this has been from the GEDCOM file, which would have been the easier option for me to work on. But where is the learning curve in that. I have been using Ancestral Sources to add inf...

Thanks Mike The NOTE2 type does the trick. I appreciate your advice on error handling. I was concentrating on functionality first, then building in error handling. As for the TEXT type, I was trying to generate a source record and include the text as part of that source. I am sure there is a better ...

I am trying to develop a pluging to add probate information I have written the following function to add items to the individual. function AddInfo(ptr, Type, Value) if Value==nil then return end infoPtr=fhGetItemPtr(ptr,'~.'..Type) if infoPtr:IsNull() then infoPtr= fhCreateItem(Type, ptr) end fhSetV...

I stand corrected.

I now appreciate that you can add a new occupation fact to the individuals profile. In all the years that I have used FMP, the occupation has always been overwritten and only the preferred occupation kept.

Thanks for the information, that will be very useful.

In my FMP Family Tree there is only ONE Occupation (and residence). In life, an individual will have multiple occupations and live at multiple addresses. Whist I can change these, there is still only the one you choose as being the most significant. In reality, all occupations an individual has had ...

I now appreciate that FMP does not generate a valid GEDCOM vers 5.5.1 file, although it identifies that version in the GEDCOM file. As a result I concede that it is fruitless to discuss this further. This renders the merge/compare function inappropriate when using FMP as the primary source of inform...

I'll retract the last comment; it is FMP that has the CONCatenation.

Is it the CONCatenation that the merge function cannot handle; although it seems to work for a FACT rather than an EVEN.

FMP produces a GEDCOM file with an EVEN.

FH produces a GEDCOM file with that changed that to a FACT. It is version 7 of FH that has the CONCatenation.

My issue is that FH does not recognise EVEN when merging a GEDCOM file.