Family Historian User Group

This may belong in the Importing forum but I will ask here first. I believe I have asked this question before but I can't seem to find the answer either in my notes or in the knowledge base.

When I import a project and look at the listing of facts for a particular person There are conventions in the display that I can't figure out.

Some facts have a yellow star before the fact and some do not. This seems to apply to both custom facts and standard facts.

Others have fact name followed by a colon.

I have created two facts called Realestatebuy and Realestatesell They both have the colons but only one gets the star

The way I have it set up is I duplicated all my custom facts from Rootsmagic 7 in FH7 creating the sentences and roles in FH to match what I had in RM7.

Also when importing FH creates new facts for all my custom facts even though they are also in FH. I then can go into the fact list and delete all the newly created facts (Rootsmagic Import) thus defaulting to the facts in the custom fact set otherwise FH uses the new facts that were just created and ignores the facts that I created earlier. Is this the correct sequence for me?

The facts with a yellow star have the Preferred Fact Flag set. Right-click the fact and check Fact Flags.
Presumably, RM has a similar feature and the FH direct import is simply replicating your setting in RM.

Custom facts with a colon are Attributes (that can have a value after the colon) as opposed to Events that cannot.
That is part of the FH import process to handle RM facts that have a value.

In FH V7 the FH direct import creates a RootsMagic Import (project) fact set that is local to the Project.
It offers the ability to define Sentence Templates, Roles and other Fact Type settings just for those imported custom facts.
But if you already have global Fact Type definitions for those facts, just delete the RootsMagic Import (project) fact set.

Mike,

Thank you I will add this to my notes so I won't forget.

If I define a fact in RM with a description field then FH imports that as an attribute. If that same fact does not allow a description then FH imports that as an event. I cannot select in RM if a fact is an event or an attribute but it is decided solely by the presence of a description or not. That discovery uncovered some of my discrepancies during import.

I'll be glad when our group can all convert to FH so the import wont be as important.

The problem of the same fact with and without a description importing to FH as both an attribute and an event occurs for many products whether direct import or via GEDCOM.
The user is then faced with using the Change Any Fact Tag plugin to convert the events to attributes and return to the single fact they started with in the original product.

It is a longstanding issue caused partially by the way the GEDCOM specification is worded.

You could raise that problem with CP via http://www.calico-pie.com/osticket/open.php because it should be feasible to make all facts with the same name and type imported from another product to generate just one fact in FH.