15,534
edits
Changes
→tmgviewer
{{Languagesman tip|Tips on importing from other genealogy programs}}There are several ways to import your family tree genealogy into Gramps from another program. The best way option depends on what program you want to copy provide the information from. But all import processes start with having a Gramps database (called a [[Genealogy_Glossary#family_tree|Family Tree]]) open and waiting to receive your family information. You could import directly into an existing Gramps Tree that already contains the fruits of many hours of research and organization. But since all Genealogy programs make different assumptions about how to organized and transfer data, that would not be a good practice. Their exported data might be a chaotic mess that mangles your nice, clean genealogy in Gramps. We recommend start by [[Start_with_Genealogy#Create_a_Family_Tree|creating a fresh, empty Tree]] and then importing... even if it is just as a test run. Once the imported data is in Gramps, you can explore what needs cleaning. Maybe their export stored a duplicate of every place and source for the genealogy rather than building a hierarchy for each or even using the same identifiers. [[Gramps_{{Version manual}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_3#Merging_records|Merging]] duplicate [[Merge_two_places|Places]] and Sources now will be much easier when there is a sole source for all the data. There are free Third-party Addon tools some users have created and shared to [[Import_Merge_Tool|make merging forked Trees easier]]. You can use this pruned Tree as a stepping stone to a cleaner import. It is always safer to import data already in Gramps format.
== Gramps to Gramps==
This is the easy one. The simplest and safest method to move all your information from one Gramps program to another on a different computer is to choose {{man menu|Family Trees -> Export}} from the first Gramps. Follow the instructions, choosing {{man label|Gramps Package}} for the format to save. And do not forget to disable privacy filter& living person filters.
Copy the file created by Gramps to the destination computer. Then in its Grampson that computer, choose {{man menu|Family Trees -> Import}} and select the transferred file.=== What's not included? === {{Template:Backup Omissions}}
== Standard GEDCOM as transfer tool==
Most programs for family history can export and import [[GEDCOM]] (.ged) files. But, because the GEDCOM data file specification has not been updated since 1996, every genealogy tool has had to take liberties to shoehorn their data into something that has been long outgrown. You're unlikely to find anyone using a fully compliant and ''standard'' GEDCOM format. So always make a backup before importing any GEDCOM file.
# Check the documentation for your program to learn how to create a GEDCOM file with all your data.
# In Gramps, choose the '''Family Trees''' icon in the toolbar, or in the menu {{man menu|Family Trees -> Manage Family Tree}}, to open the Family Tree Manager. Create a new family tree, choose a name, and click on the {{man button|Load Family Tree}} button to open.
# Now that a family tree is loaded, select {{man menu|Family Trees -> Import}} from the menu.
For example, it doesn't import all of a person's events and notes. It does import/export birth, death, and marriage events---and notes for those events, people, and marriages.
For more details on this format see [[Gramps 45.2 1 Wiki Manual - Manage Family Trees: CSV Import and Export]].
== Addon ==
'''Please also feel free to provide feedback on broken scripts or incorrect ''fixes'''''
-----
=== Ancestry.com ===
OlderGEDCOM files produced by Ancestry.com were not fully readable by Gramps 2.0.x GEDCOM export files had a relationship compatibility faults in their GEDCOM format and 2.2.x (Relationship lost).This is Bug#{{bug|899}}'':fixed for , beginning with the 3.0''release, Gramps handles this seamlessly. AlsoIn a test done in 2016, you can use {{bug|899}}:'''grampifyAncestry.pl''' com had corrected that fault in their GEDCOM format and their newer files are also recognized for fixing broken proper import into Gramps, But some GEDCOM generated by Ancestryidiosyncracies remain.com, however this is no longer necessary
These notes are based on work importing a gedcom with 2000 individuals and 60000 lines of information into Gramps V4.2.5.
==== Records not imported ====
There were around 8000 lines that were listed reported as "not imported". They were the following categories:* '''_APID''' records comprise the majority of messages - they are a record type specific to Ancestry internal cross-referencing identifiers and probably meaningless anywhere else.
* many '''NOTES''' records are listed as ignored because they are ''empty'' - checking the gedcom shows this to be correct.
* a very small number show as "''Tag recognised but not supported''". This coincided with duplicated source entries ''SOUR'' linked to the same source object but with ''_APID'' subrecords having different values.
There were 5 events that in the source gedcom were given as ''1 BIRT Y'' with no subordinate records. Gramps apparently rejected these as "''events were referenced, but not found''". They are valid according to the GEDCOM specification, but quite redundant since all they say is that the person was born.
==== Source objects ====
The empty source objects are not deleted, but are replaced by entries with a note and the title "unknown".
You can click on ''Sources'' in the navigator, select one and view the associated ''Notes'' tab, which should just show the associated warning inserted by Gramps Check and Repair. Provided there is nothing useful in the Notes, you can select all these "Unknown", ''edit->remove''.
==== Notes ====
Select ''Notes'' under the navigator. For each individual, family or source object a note will be created listing all the gedcom problems for that object, starting with the text "Records not imported into ..." . Scroll down to these lines (ensure pages are sorted by ''Preview''. Alternatively, create a suitable filter: enter "^Records not imported into" into the text box (without the quotes), enable "Use regular expressions" and click Find.
You may wish to select and remove all of these, provided you have established there are no significant errors in the import. The blank '''NOTES''' and the Ancestry-specific '''_APID''' records are of no use here, and they ''cannot be re-exported'' for reading back into an Ancestry tree.
==== Dates ====
Ancestry seems to allow some date options that aren't consistent with the restrictions of GEDCOM standard. Their export does not always convert these to the [http://wiki-en.genealogy.net/GEDCOM/DATE-Tag valid GEDCOM date format].
There seems to be no automated method to fix these. These are identified in a default configuration by displaying the bad dates in bold in the display area. Gramps will fix some if you simply open an event and then save; others need manually editing.
A more efficient way to check is use {{man menu|Tools->Utilities->Verify the Data}} and enable "Identify Invalid Dates"
==== Dates Final cleanup of Ancestry's empty export records ====A search for unused objects ({{man menu|Tools->Family Tree Repair->Remove unused objects}}) can identify and delete any remaining problems. ==== additional Ancestry seems notes ====[https://progeny.zendesk.com/hc/en-us/articles/215558727-How-to allow a wider range -export-your-data-out-of dates to be used, and does not always convert these to the valid GEDCOM date format-Ancestry-com How To: export your data out of Ancestry.com] There seems to be no automated method to fix these[https://www. These are identified in a default configuration by displaying the bad dates in bold in the display areareuniontalk. Gramps will fix some if you simply open an event com/forum/using-software-hardware-with-reunion/9126-ancestry-apid-tags-and then save; others need manually editing-reunion More about Ancestry.com's APID record identifiers]
=== Evidentia ===
GEDCOM is currently the only option for copying your data out of Family Tree Maker and into Gramps. Follow the instructions above for [[#Standard GEDCOM as transfer tool|Standard GEDCOM]].
{{man tip|1=Recommended Reading|2=When Ancestry startled Family Tree Maker (FTM) proponent Keith Riggle by announcing it's retirement, he posted a frank critique of exchanging data between FTM & Gramps v4.0 in [https://genealogytools.com/replacing-family-tree-maker-part-8-importing-your-ftm-tree-into-gramps-4/ Family Tree Software Alternatives, part 8] article of the [https://genealogytools.com/ Genealogy Tools] blog.<br>''extensively revised for Gramps 5.0 on 8 Aug 2018''}}
==== If you do not have access to Family Tree Maker ====
(Tested with FTW file created by Family Tree Maker 2006)
=== Heredis ===
''With editor (like gedit ot note++) find and replace '''« > »''':''
'''Like: ''' _CLS, _FIL LEGITIMATE_CHILD, _UST MARRIED, SIGN...
1 BIRT > 1 BIRT Y
2 ASSO @398195I@ > 1 ASSO@398195I@
FILE X:\YYY\Photos\ > FILE /media/ZZ/YYY/Photos/
Description Type
There would be a way to assign some fields in attributes instead of events. It's a mix up.
By ''Ifs, Oct 25 2011''
====Known issues====
=== MySlänk MinSläkt === MinSläkt (MyFamily) is a Swedish genealogy program for Windows by [http://www.dannbergsdata.se/ Dannbergs Data]. <!-- the following section is commented out (hidden) until the importing GEDcom Confidence section is written ==== GEDCOM ==== Instructions for exporting GEDcom from MinSläkt ===== Known issues ===== You can set Confidence levels for your [[Gramps_Glossary#source|Sources]] in the [[Gramps_{{Version manual}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Citation_information|Citation Editor]]. These Confidence levels correspond to the [[Gramps_Glossary#gedcom|GEDCOM]] [http://wiki-en.genealogy.net/GEDCOM/QUAY-Tag QUAY] tag.
=== Pro-Gen ===
# 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.2_Wiki_Manual_Gramps_{{Version manual}}_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.
https://github.com/girimonti/TMG-Working-Group
==== tmgviewer Gramps Addon TMG importer ====
An attempt at reading a TMG file Directly from python. (Does not use TMG's Genbridge).
* [[Addon:TMGimporter]] - WIP - Not released yet.- Abandoned
See {{bug|7591}} for more details and tests.
==== tmgtogedcom ====
TMG to GEDCOM includes a template for exporting from TMG into Gramps. In addition to the commonly-supported GEDCOM records like people, names, events, families, citations, sources, and exhibits, the template helps produce a GEDCOM that supports:
* Witnesses and role labels
* Flag values as Gramps Attributes
See {{bug|7591}} and [https://www.tmgtogedcom.com/en/template-gramps.htm John Cardinal's project ]
=== Visuged ===
