I am getting ready to do a full import of my genealogical database from Rootsmagic 7.
I have encountered the following situation, among others.
I have several fact types that I have created and want to keep. I deleted many fact types that I did not need a specialized fact type for.
I created a single fact type in FH6 that exactly matches the fact type that I have in Rootsmagic.
I created a test project that has several people but one that uses all the new fact types that I created in Rootsmagic. When I import from RM I get a lot of error because the EVEN tag does not conform to FH6 but does seem to conform to GEDCOM standards. Other sites have noticed that the documentation shows both methods. However this is not the question here.
When I import the GEDCOM file it retains all the data but in a slightly different format than I expected. It appears to follow the path of using a generated fact type but I cannot locate where these generated fact types might be. Also the fact type that I created new in FH6 imported nicely from the fact type I created in Rootsmagic so that appears to be a viable the route to follow.
Any help would be appreciated
* Importing from Rootsmagic
-
TMG_refugee
- Diamond
- Posts: 97
- Joined: 14 Nov 2015 15:44
- Family Historian: V7
- tatewise
- Megastar
- Posts: 27089
- Joined: 25 May 2010 11:00
- Family Historian: V7
- Location: Torbay, Devon, UK
- Contact:
Re: Importing from Rootsmagic
See how_to:import_from_roots_magic|> Import from RootsMagic (RM) with advice on glossary:work_with_fact_sets|> Defining Imported Custom Facts.
I've lost track of how many times I've said it would help if explicit details are provided instead of vague "a lot of errors" or "a slightly different format than I expected".
So I am guessing, but here goes...
The EVEN Event Tag errors are complaining about values, that in some products are called details or references, being moved to the local Note field. That is because in GEDCOM v5.5 Events such as Birth, Marriage, Death cannot have a value, whereas Attributes such as Occupation, Possession, Religion can have a value. However, many products ignore that distinction, including RootsMagic, partly because in GEDCOM v5.5.1 that distinction has become blurred.
Any imported custom Events are unlikely to have a matching Tools > Fact Types definition. FH does not create a fact definition and just relies on default built-in settings. The Importing to Family Historian advice has an entry for glossary:work_with_fact_sets|> Defining Imported Custom Facts in which the Custom Facts from other Products explains how to reveal and create their definition.
I've lost track of how many times I've said it would help if explicit details are provided instead of vague "a lot of errors" or "a slightly different format than I expected".
So I am guessing, but here goes...
The EVEN Event Tag errors are complaining about values, that in some products are called details or references, being moved to the local Note field. That is because in GEDCOM v5.5 Events such as Birth, Marriage, Death cannot have a value, whereas Attributes such as Occupation, Possession, Religion can have a value. However, many products ignore that distinction, including RootsMagic, partly because in GEDCOM v5.5.1 that distinction has become blurred.
Any imported custom Events are unlikely to have a matching Tools > Fact Types definition. FH does not create a fact definition and just relies on default built-in settings. The Importing to Family Historian advice has an entry for glossary:work_with_fact_sets|> Defining Imported Custom Facts in which the Custom Facts from other Products explains how to reveal and create their definition.
Mike Tate ~ researching the Tate and Scott family history ~ tatewise ancestry
-
TMG_refugee
- Diamond
- Posts: 97
- Joined: 14 Nov 2015 15:44
- Family Historian: V7
Re: Importing from Rootsmagic
I probably put too much in my original question. It was not about either the EVEN tag or the importing errors.
The question was once FH imports my data what can I do about the sentence that is generated? With a fact type I would edit the sentence structure in that fact type. What are the possibilities with an imported fact that does not match any fact type in any form in FH?
I could create a new fact type in FH and then create a new fact using that newly created fact copy all the data from that imported fact into the new fact and then deleting the old mismatched fact from the import. Is this what I should do or is there a better way?
The question was once FH imports my data what can I do about the sentence that is generated? With a fact type I would edit the sentence structure in that fact type. What are the possibilities with an imported fact that does not match any fact type in any form in FH?
I could create a new fact type in FH and then create a new fact using that newly created fact copy all the data from that imported fact into the new fact and then deleting the old mismatched fact from the import. Is this what I should do or is there a better way?
- tatewise
- Megastar
- Posts: 27089
- Joined: 25 May 2010 11:00
- Family Historian: V7
- Location: Torbay, Devon, UK
- Contact:
Re: Importing from Rootsmagic
It seems you have not understood the advice for glossary:work_with_fact_sets|> Defining Imported Custom Facts in which the Custom Facts from other Products explains how to reveal and create their definition.
If the imported custom events are correctly formatted EVEN tag GEDCOM events then they are listed in Tools > Fact Types by ticking the Show Hidden option. Then you can use the Edit button to create a definition for them, define Sentence Templates, Roles, etc, etc, just like any other facts.
If they are not correctly formatted then they will be UDF that need handling differently.
See how_to:handling_unrecognised_data_fields|> Handling Uncategorised Data Fields (UDF).
If the imported custom events are correctly formatted EVEN tag GEDCOM events then they are listed in Tools > Fact Types by ticking the Show Hidden option. Then you can use the Edit button to create a definition for them, define Sentence Templates, Roles, etc, etc, just like any other facts.
If they are not correctly formatted then they will be UDF that need handling differently.
See how_to:handling_unrecognised_data_fields|> Handling Uncategorised Data Fields (UDF).
Mike Tate ~ researching the Tate and Scott family history ~ tatewise ancestry