Family Historian User Group

Contrary to what David says, FH V7 does support the INDI.NAME.TYPE field on the All tab. However, until we know how your explanation of the origin of a Name imports into FH it is difficult to give a precise solution. We need a screenshot similar to David's for one of your All tabs with the Name fiel...

I agree with all the earlier suggestions.

An example of text editing is that my TMG import has custom name tags showing names as they were in a native country. In FH these names are lumped together under a.k.a. without the explanation of the origin. Using "a.k.a." basically removes the intention of the alternate name usage such as native n...

Welcome to the FHUG. The challenge you face is something that users often encounter as they discover the need for organised Source Citations. You have sensibly identified the two techniques of starting from scratch versus updating your current Project. I believe that most users opt for the second te...

Peter, it sounds like that is where you went wrong. Originally, I believe you had Individual in file selected. Therefore, to add a Name: you must << Select an Individual record from the list in the righthand pane one at a time and click Add for each one to compile a list of Associated Individuals in...

As Lorna requests, please explain the type of text edit you need to perform. There is no general text editor that allows arbitrary changes to the contents of an Individual box. All text changes must be controlled via the Diagram > Options > Text Scheme . Lorna has suggested using a Record Flag but i...

I have just discovered another way to hide those coloured ribbons.
Right-click on a box with a coloured ribbon and chose Format..., then tick Prevent Linking as Duplicate.
That allows each coloured ribbon to be hidden or revealed selectively box by box.

Thank you, Mike, again, for the clarification. I had tried double-clicking the appropriate Fact type but there was nothing. However, I have now set Godparents to Just a Name and hope that will sort that aspect out. Changing Godparents from Individual in file to Just a name may not materially change...

Your last posting has done that. There is no formal sign-off.

With problems like this, it is useful to be very specific about the settings you used in AS and a screenshot helps too. e.g. Baptism > Further Info tab > Association: Godparents set to Just a name and on clicking Edit... the Method: is Witness Role . If your AS setup is the same then the Baptism eve...

Well, it depends on what data relationships you enter! You entered your birth father as Unknown and on his tab included yourself on his Children: list. However, on your 'surrogate' father's tab you are NOT included on his Children: list. Those relationships are shown as you desire. However, your ste...

Whoops, sorry, forgot about the way the Status: affects Diagram partnership connecting lines.
However, it will never get set by an import from another product.

In the All Individuals standard Query, the Relationship to Root column shows the relationship to the File Root person. I assume that your Individual record is the File Root and not your wife's Individual record. If your wife is the File Root then your stepson will be shown in the Query correctly as ...

Hi Glenn,
That imported Divorce event is perfectly OK and is standard GEDCOM.

The FH Status: Divorced is only for when you know they are Divorced but have no Divorce event Date or Place details.
It is a non-standard GEDCOM extension invented by FH so will not be supported by any other products.

By default, FH does not differentiate between blood relatives and step, foster, or adoptive relationships. Anyway, unless you have definitive DNA/blood proof, you cannot be 100% sure that blood relatives really are such. The parent Rel ationship details can identify the relationship to each parent, ...

Yes, if you are always the researcher then it is hardly worth preserving.
In FH it could be recorded in a Source Citation Note, or by using the new Source Templates, metafields could be defined to hold that sort of information.

It sounds as if you are really getting to grips with the RY3 migration. I think you are saying those 120 entries are 2 PLAC without any subsequent placename. Yes, they can be ignored. I'm not sure the RIN number is anything to do with _PPT because they have the same level digit. Anyway, if you have ...

Sorry, I can't think of any shortcuts to that.
You will just have to review each Source record in the Sources tab of the Records Window.

Yes, it is a bit tricky. Function parameters such as that are typically dependent on context. In this case, the Query type is Individual, so any blank parameter that refers to an Individual record will default to %INDI%. However, as you found in the Sentence Template context that does not work. Simi...

GRO BMD Certificates are in the public domain and can be obtained by anyone for a fee. So does the fact that they must be bought impose any copyright? Anyway, the process to follow to remove unwanted Media is as follows. Use your filter method and put all the GRO Media records to be deleted into a N...

This is related to your recent posting 20881|Relationship expression . The syntax is =Relationship( Record(9999,"I"), %INDI%, TEXT, 1 ) as before but no { curly brackets } and %INDI% not %CUR_PRIN% in this context. Where 9999 is your Record Id number. Ditto for =RelationCode( Record(9999,"I"), %INDI...

Try the =Relationship(...) function or =RelationCode(...) function but I'm not sure how they can be used to identify direct versus indirect relationships.

Unfortunately the %INDI% data reference does not work in the Sentence Template context and %CUR_PRIN% must be used. Also, the function needs to be enclosed in { curly brackets } . i.e. {=Relationship( Record(9999,"I"), %CUR_PRIN%, TEXT, 1 )} The full Sentence Template would then be: {%CUR_PRIN%} is ...

Tom, I cannot see much wrong with what is shown in your screenshots. I suspect you have been investigating folders that you have not inspected before! C:\Users\...\Documents\Family Historian Projects\ correctly holds your Project folders (and maybe some other stuff). The only entry that is a little ...

IMO, you should consider two forms of Simple Citation Template for FH. The current template is very much a Simple Citations Lumper Template because so many details are in the Citation. In FH if there are multiple identical Citations derived from one Source there will be multiple copies of a lot of d...