Open main menu

Gramps β

Changes

Import from another genealogy program

No change in size, 22:56, 11 March 2015
The Master Genealogist (TMG)
tmg2gramps was designed to, '''"...convert what it can to a Gramps V2.2.6 xml file. This file can then be imported into Gramps, V2.2.6 or higher."''' Since then, Gramps has evolved. Testing has been done using tmg2gramps to convert a TMG v6 database and importing it to both Gramps 2.2.10 and 4.0.4. Despite being designed for Gramps 2.2.6, tmg2gramps works (at least in the test case) even better when importing to Gramps 4.0.4. Gramps 3.4.8 and 4.0.4 are more or less the same at the XML import level, so this should apply to importing to Gramps 3.4.8 as well.
 
===== Data tmg2gramps successfully converts =====
Some data that tmg2gramps successfully converted from a TMG v6 database which a GEDCOM 5.5 export from TMG did not, are as follows:
 
*"Witness" information.
 
*"Places" data from TMG are put into the correct, corresponding fields in Gramps. GEDCOM puts all TMG "Places" data into Gramps' single "Place Name" field.
 
*Various "notes" from TMG do not transfer over at all via GEDCOM and those that do are categorized simply as "General." tmg2gramps appears to transfer over most (if not all) the notes and breaks them into categories. The categories are not always entirely appropriate (see below regarding citations and "Source text" notes), but the information is there and can be corrected in Gramps.
 
*tmg2gramps appears to transfer all TMG Tags to Gramps as "Events." (However, see [[Import_from_another_genealogy_program#Known_issues_3 |below]] for some minor issues related to this.) GEDCOM transfers some, but not nearly all TMG Tags.
 
===== Known issues =====
Here are some known issues that have occurred when using tmg2gramps:
 
#Events in Gramps from unique [http://tmg.reigelridge.com/Tags.htm TMG tags] sometimes have minor issues. For example a TMG Birthilleg tag will definitely show up in Gramps as an "Event" with all of the correct information, but it will not be designated as a birth -- so if you look at that person in a chart in Gramps, the birth field will remain empty until you change the Birthilleg "Event" to a Birth "Event" (and you can mark the birth as illegitimate in a note).
#Any Godparent relationships won't convert at all. However, each one of them is displayed by tmg2gramps once it is finished, so they can easily be copied and pasted to a document for manually entering into Gramps later.
#Any information regarding a citation is put into a "Source text" note in Gramps. The "Source text" is associated with both the "Source" itself and the specific "Citation," so all the information is there, even if the description being a "Source text" is not accurate. Also, this leaves the "Volume/Page" field in the "Citation" blank, even if there is a volume or page number in the "Source text." An adequate but not perfect fix for this is to edit the XML file directly (''after'' exporting it from Gramps) and do a find / replace of type="Source text" with type="Citation" -- this turns each "Source text" note into a "Citation" note. The "Volume/Page" field remains blank, but presumably that information is now in the "Citation" note which is not entirely inappropriate.
#If two people are married, the "Family" screen in Gramps indicates in "Relationship Information" that their "Type" of relationship is "Unknown" rather than "Married." An example of the ramifications of this are that when printing a Narrated Website Report of John Doe who in reality was married to Jane Doe, and they had children, Jane Doe will not appear on the chart and the chart will not indicate that they were a married couple, though the marriage itself will be indicated as an "Event." To fix this issue, an adjustment must be made prior to importing the tmg2gramps generated XML file to Gramps. Under Gramps {{man menu|Edit-> Preferences-> Display}} the "Default family relationship" can be set to "Married" (or any of the others). Upon importing the database, all Family Relationship Information "Types" will then be set to "Married." Of course any Family unions that are not marriages will then need to be corrected, but you can set the default "Type" to be whatever the majority of your Families are.
#Related to the above issue, any "Disconnected individuals," married or otherwise, will remain disconnected. A TMG GEDCOM export and Gramps import designates a married couple as a "Family" whether or not they have any children -- the "Disconnected individual" count is at zero -- this is the Gramps recommended practice. For couples without any children, a tmg2gramps import will not recognize the relationship as a "Family" -- hence, the marriage is an "Event" and the unrelated spouse is considered a "Disconnected individual." Also, even if the family does have children, perhaps due to distant consanguinity, they will not appear as "Family." Fixing this gets complicated -- you can go through the "Disconnected individual" list from the statistics of your database and manually create each missing "Family" that way, but that will still leave others that are potentially lost needles in a haystack. They can be found by [http://sourceforge.net/p/gramps/mailman/message/32487230/ running custom filters on the Person Filter Editor]. You will then be able to clearly see all the individuals who have marriages, but which tmg2gramps did not recognize as a "Family." You can then create each "Family" manually yourself.
#Any external media files may not be found. This can be resolved by correcting their path using the [[Gramps_4.0_Wiki_Manual_-_Tools#Media_Manager... |Gramps Media Manager]].
#Certain unique characters may not import properly into Gramps. Most accented characters did, but an "ñ" in TMG was imported to Gramps as "ń" -- a TMG GEDCOM import into Gramps did not have this problem. It is easily fixed by editing the XML file directly and doing a find / replace.
===== Running tmg2gramps =====
In coming up with the above instructions, participants in the [http://sourceforge.net/p/gramps/mailman/gramps-users/ Gramps-Users mailing list] were extremely helpful. The original tmg2gramps [http://www.cohsoft.com.au/tmg2gramps/README.tmg2gramps README] file also provided insight, and the external site [http://homepage.ntlworld.com/hamamelis/linux/tmg2gramps.htm 'TMG to GRAMPS how I did it using tmg2gramps script'] provided the initial inspiration.
 
===== Data tmg2gramps successfully converts =====
Some data that tmg2gramps successfully converted from a TMG v6 database which a GEDCOM 5.5 export from TMG did not, are as follows:
 
*"Witness" information.
 
*"Places" data from TMG are put into the correct, corresponding fields in Gramps. GEDCOM puts all TMG "Places" data into Gramps' single "Place Name" field.
 
*Various "notes" from TMG do not transfer over at all via GEDCOM and those that do are categorized simply as "General." tmg2gramps appears to transfer over most (if not all) the notes and breaks them into categories. The categories are not always entirely appropriate (see below regarding citations and "Source text" notes), but the information is there and can be corrected in Gramps.
 
*tmg2gramps appears to transfer all TMG Tags to Gramps as "Events." (However, see [[Import_from_another_genealogy_program#Known_issues_3 |below]] for some minor issues related to this.) GEDCOM transfers some, but not nearly all TMG Tags.
 
===== Known issues =====
Here are some known issues that have occurred when using tmg2gramps:
 
#Events in Gramps from unique [http://tmg.reigelridge.com/Tags.htm TMG tags] sometimes have minor issues. For example a TMG Birthilleg tag will definitely show up in Gramps as an "Event" with all of the correct information, but it will not be designated as a birth -- so if you look at that person in a chart in Gramps, the birth field will remain empty until you change the Birthilleg "Event" to a Birth "Event" (and you can mark the birth as illegitimate in a note).
#Any Godparent relationships won't convert at all. However, each one of them is displayed by tmg2gramps once it is finished, so they can easily be copied and pasted to a document for manually entering into Gramps later.
#Any information regarding a citation is put into a "Source text" note in Gramps. The "Source text" is associated with both the "Source" itself and the specific "Citation," so all the information is there, even if the description being a "Source text" is not accurate. Also, this leaves the "Volume/Page" field in the "Citation" blank, even if there is a volume or page number in the "Source text." An adequate but not perfect fix for this is to edit the XML file directly (''after'' exporting it from Gramps) and do a find / replace of type="Source text" with type="Citation" -- this turns each "Source text" note into a "Citation" note. The "Volume/Page" field remains blank, but presumably that information is now in the "Citation" note which is not entirely inappropriate.
#If two people are married, the "Family" screen in Gramps indicates in "Relationship Information" that their "Type" of relationship is "Unknown" rather than "Married." An example of the ramifications of this are that when printing a Narrated Website Report of John Doe who in reality was married to Jane Doe, and they had children, Jane Doe will not appear on the chart and the chart will not indicate that they were a married couple, though the marriage itself will be indicated as an "Event." To fix this issue, an adjustment must be made prior to importing the tmg2gramps generated XML file to Gramps. Under Gramps {{man menu|Edit-> Preferences-> Display}} the "Default family relationship" can be set to "Married" (or any of the others). Upon importing the database, all Family Relationship Information "Types" will then be set to "Married." Of course any Family unions that are not marriages will then need to be corrected, but you can set the default "Type" to be whatever the majority of your Families are.
#Related to the above issue, any "Disconnected individuals," married or otherwise, will remain disconnected. A TMG GEDCOM export and Gramps import designates a married couple as a "Family" whether or not they have any children -- the "Disconnected individual" count is at zero -- this is the Gramps recommended practice. For couples without any children, a tmg2gramps import will not recognize the relationship as a "Family" -- hence, the marriage is an "Event" and the unrelated spouse is considered a "Disconnected individual." Also, even if the family does have children, perhaps due to distant consanguinity, they will not appear as "Family." Fixing this gets complicated -- you can go through the "Disconnected individual" list from the statistics of your database and manually create each missing "Family" that way, but that will still leave others that are potentially lost needles in a haystack. They can be found by [http://sourceforge.net/p/gramps/mailman/message/32487230/ running custom filters on the Person Filter Editor]. You will then be able to clearly see all the individuals who have marriages, but which tmg2gramps did not recognize as a "Family." You can then create each "Family" manually yourself.
#Any external media files may not be found. This can be resolved by correcting their path using the [[Gramps_4.0_Wiki_Manual_-_Tools#Media_Manager... |Gramps Media Manager]].
#Certain unique characters may not import properly into Gramps. Most accented characters did, but an "ñ" in TMG was imported to Gramps as "ń" -- a TMG GEDCOM import into Gramps did not have this problem. It is easily fixed by editing the XML file directly and doing a find / replace.
==== TMG-Working-Group ====
80
edits