Family Historian User Group

Per tatewise's suggestion, starting a new thread on why this happens.

I have imported a GED from RootsMagic. One of the custom facts (and in that world facts and events were used interchangeably) that I used was imported as both Event and Attribute. I had previously created a FindAGrave fact that I used to store the FAG memorial number. This fact imported as both. Why did this happen?

As I understand things in FH, Events are just that, Events that happened. Attributes are some value associated with an individual. Using that as my guide, I can see where the FindAGrave fact would be an attribute in FH, not an event. If my definition is correct, I do like this concept and I think I can get used to it.

My question as to why it happens is so that I can figure out if I need to go back to RootsMagic and fix/correct some of my practices before I import another GED file that will become my 'live' file.

In RootsMagic checkout Lists > Fact Type List where all facts are defined similar to FH Tools > Fact Types.
Review events such as Birth, Census, Burial & Marriage that have Description: No.
Whereas attributes such as Occupation, Property & FindAGrave have Description: Yes, which is equivalent to the FH attribute Value.

When FH imports standard GEDCOM facts it knows which are Events and which are Attributes.
But when importing custom facts it uses whether there is a Description/Value to decide.
So those FindAGrave facts without a Description/Value become Events, whereas those with a Description/Value become Attributes and have an entry in the Window > Log Files > Exception report.

There are two solutions:

1. In RootsMagic ensure all FindAGrave facts have a Description before exporting to GEDCOM.
2. In FH use Change Any Facts Tag Plugin to convert all custom EVEN-FINDAGRAVE to _ATTR-FINDAGRAVE.
   OR since they have no Description/Value then simply delete all the custom Events.

This is an interesting response because when I created the FindAGrave fact in RM, I only use the description field. I unchecked Date and Place. So the people that I used FindAGrave on should all have content in the description field, and that is the memorial number. If I don't have a FAG memorial number, then that person should not even have a FindAGrave fact.

I ran a report in RM and found two persons that did have a FindAGrave fact without a memorial number. That explains why I got both Event and Attribute. It also gives me a starting place for the Obit and Military facts that behaved in the same manner. Thank you for the explanation.

While discussing importing, have you checked how_to:import_from_roots_magic|> Import from RootsMagic (RM)?

In particular, how_to:handling_unrecognised_data_fields|> Handling Uncategorised Data Fields (UDF)?

There are likely to be many UDF such as _UID and _SDATE that need to be investigated and resolved.

Before importing, I did read the Knowledge Base article that you suggested. I know there are several bit that are RM specific, such as _AMTID, _UID and _COLOR to clean up. I am assuming _COLOR is due to color coding in the file, which doesn't seem to exist in FH, at least not in the base program. Still exploring plugins also. I may also have forgotten to uncheck the RM specific details.

I am also working on figuring out how the Place Details field is imported. I use that to record addresses, names of hospitals, cemeteries and so on. It appears the become an address attribute if I am reading this the details correctly.

It appears that th FindAGrave situation that you helped resolve, still exists to some extent. When I used the plugin to change from Event to Attribute, it only altered the two people who had the FindAGrave event, but did not delete that event from the possible list. I am assuming this is because Events and Attributes apply across all projects, not just the current one. If so is there a safe way to blow out those settings or is it easier to uninstall/reinstall FH. Do I need to clean up any config files manually?

Most of those UDF (_AMTID, _COLOR) will be avoided if you untick Extra details (RM specific) in the RootsMagic export dialogue.

Yes, most customisations such as Tools > Fact Types apply across all Projects.
If you have manually defined the FindAGrave Event via Tools > Fact Types then that will remain even if there are no actual FindAGrave Events remaining in your Project data. Just delete the unwanted Fact Type definition.
It is similar to RootsMagic where you can have Fact definitions bit no actual Fact data entries.

It would be best to start a new thread to discuss Place and Address details as there are many options to consider.