6
edits
Changes
→Dates
== 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 Gramps Package}} for the format to save. And do not forget to disable privacy filter.
Copy the file created by Gramps to the destination computer. Then in its Gramps, choose {{man menu|Family Trees -> Import}} and select the transferred file.
# Check the documentation for your program to learn how to create a GEDCOM file with all your data.
#* If you have a choice, GEDCOM 5.5 Standard is usually the safest type of GEDCOM.
# 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 family tree, give it choose a good name, and click on the {{man button|Load Family Tree}} button to open.# Now that a Family family tree is loaded, choose in the menu select {{man menu|Family Trees -> Import}}from the menu.# Locate the GEDCOM file created by your program, and choose select {{man button|Open}}.
{{man warn| Check The Results Verify the data |Check your data carefully once imported into Gramps. There are many things GEDCOM does not support that may be lost during transfer. In addition, many commercial programs do not create standard GEDCOM files. While effort is given to import as many files while preserving as much data as possible, Gramps aims to support the GEDCOM 5.5. 1 standard.}}
Ensure that your media files are transferred too, and found by Gramps. In the menu {{man menu|Tools -> Utilities}}, you will find the {{man label|Media Manager}}, with which you can change the path of your media objects to the new path if needed.
== Addon ==
[[GEDCOM Extensions]] should be able to handle unofficial GEDCOM extensions.
== Import instructions from for different programs ==
=== Ancestrologie ===
Ancestrologie seems to produce non-standard gedcom GEDCOM for some kinds of data. In general such problems should be repaired prior to importing into Gramps.
==== Programs for fixing some of the known problems ====
Download and uncompress (gunzip) to obtain executable scripts. Some additional explanations and data interpretations (or guesses) may be found in the comments.
2 NOTE APPX=Ancestrologie/2007.0.0.761 DATX=_ANCES_XINSEE 75111
The data (in this case 75111) may be absent or extend to CONT lines.
The non-standard elements converted to APPX notes include:
; _ANCES_CLE_FIXE : Special internal reference : "Who they are ?"; _ANCES_ORDRE : Considered non-critical, events classification ; _ANCES_XACTE : Non-critical (certificat found = 1); _ANCES_XINSEE : INSEE geographical code (evidently ''simplified 5-digit''); EVEN F : Invalid EVENTS_RECORDED format in a SOUR record; EVEN I : (Same); LIEU : A subdivision of place, is not our place but a division; XTYPE : These seem to be OBJE subordinates; XIDEN : Considered non-critical, media object used for primary media (photo); XMODE : (file is not present at the FILE address) In addition, one other change, replaces a non-standard "FILA" item to the gedcom GEDCOM 5.5.1 generic FACT item (in INDIVIDUAL_ATTRIBUTE_STRUCTURE) provided for exactly this kind of data.
1 FILA Enfant légitime
1 FACT Enfant légitime
2 TYPE FILA
'''Users are invited to correct/clarify the above information or notify us of additional problems with non standard gedcom GEDCOM or gedcom GEDCOM extensions.'''
'''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 and 2.2.x (Relationship lost).This is Bug#{{Out_of_datebug|899}}'':fixed for 3.0''. Also, you can use {{bug|899}}:'''grampify.pl''' for fixing broken GEDCOM generated by Ancestry.com, however this is no longer necessary In a test done in 2016, Ancestry.com have fixed the relationship compatibility faults in their gedcom format and their files import into Gramps, but with some issues.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 as "not imported". They were the following categories:* '''_APID''' records comprise the majority of messages - they are a record type specific to Ancestry 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.Those three import failure types do not create any problem for use with Gramps, and can be ignored, however you should make a point of carefully scanning the import report to ensure there were no failures for other reasons. The GEDCOM layout used by Ancestry for each item seems to not be consistent, and might change depending on the time at which the initial entry was made into the Ancestry.com tree.==== Scan for Errors====Use the ''Tools-> Family Tree Repair->Check and repair Database''. Any media objects in the Ancestry.com tree will not be imported, but each will have a caption and url that will not generally work without being able to login to an active Ancestry.com account. Depending on your intended actions with regard to media, you can keep these or select for Gramps to ''remove missing objects''. 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 a wider range of dates to be used, and does not always convert these to the valid GEDCOM produced date format.There seems to be no automated method to fix these. These are identified in a default configuration by Ancestrydisplaying the bad dates in bold in the display area.com is not fully readable by Gramps 2.0.x will fix some if you simply open an event and 2.2.x (Relationship lost)then save; others need manually editing.This A more efficient way to check is Bug#{{bug|899}}use '':fixed for 3.0Tools->Utilities->Verify the Data''. Also, you can use {{bug|899}}:and enable "Identify Invalid Dates" ==== Final cleanup====A search for unused objects (''Tools->Family Tree Repair->Remove unused objects'grampify.pl''' for fixing broken GEDCOM generated by Ancestry.com) can identify and delete any remaining problems.
=== Evidentia ===
If you do source- and evidence-based genealogy research, you might use this (purchaseablecommercial) program to help you follow the [http://www.bcgcertification.org/resources/standard.html Genealogical Proof Standard] (GPS). If so, you need to understand which information [http://evidentiasoftware.com/evidentia-step-by-step Evidentia] will and will NOT export and import via GEDCOM.
====General Tipstips ====
When you are entering information into Evidentia (about people, places, sources, etc.), be sure that it is typed EXACTLY as you entered it into Gramps. This makes it more likely that it will transfer successfully from one program to another.
====People=========IMPORT INTO Import into Evidentia as Subjectssubjects =====
First, export individuals from your Gramps database into a GEDCOM file, either your entire database, or just those people you are currently researching. Next, import those people into Evidentia as what the program calls "Subjects" under the "List Manager" option.
=====What Evidentia IMPORTS imports and EXPORTSexports =====Evidentia will only save enough data so that you can clearly identify which person you are researching. Evidentia can IMPORT import and EXPORT export these basic GEDCOM fields about a Personperson:* ; @I0000@ INDI (person: Person's ID number, called a "Reference number" in Evidentia)* ; NAME Lakshmi /Wolowitz/ (full : Full name)* ; GIVN Lakshmi (given or first : Given name)* ; SURN Wolowitz (surname or last name): Surname* ; SEX F (gender): Gender* ; BIRT (birth : Birth year)
====Events and Factsfacts ====
As mentioned above, Evidentia can import the Event (sometimes called Fact) of a person's birth. However, that is the ONLY event that can be imported in the current version.
=====Manually add Facts INTO facts into Evidentia=====
The main use for Evidentia is to properly cite and "prove" facts (or events) about people. So, you are required to enter those facts into Evidentia as a "Claim Type", attached to a specific Subject (person), and supported by source citations.
=====EXPORT Export some types of Facts facts to Gramps=====
Evidentia has most of the main types of claims you'd expect (birth, residence, etc.) and will export them to the usual GEDCOM fields. If a Claim Type doesn't exist in the original list, though you have to add it. It is unclear if an added Type will export to GEDCOM.
====Sources & and Citations=========Manually add to Evidentia FIRSTfirst =====Enter your Sources sources and Citations citations into Evidentia FIRSTfirst. Only after you've finished creating your proofs in Evidentia should you then import your Source Citations source citations into Gramps.
There are two reasons to follow this workflow:
* First, Evidentia currently has no way to import your Sources sources or Citationscitations, so entering here first means you don't have to enter them twice.
* Second, Evidentia makes it easier to use the 170 source citation TEMPLATES templates from Elizabeth Shown Mills, so your sources and citations will be properly formatted!
=====Match your Source Title source title and Source Abbreviation source abbreviation =====When a Source source is exported FROM from Evidentia, it uses the "Source Title" for BOTH both the Title title (TITL) AND and the Abbreviation abbreviation (ABBR) fields in GEDCOM. So, if you've already created Sources in Gramps, use the SAME same text in both of these fields, as well as in both programs.
=====Complete Publication publication information Exported exported =====Evidentia exports a FULL full and complete reference listing (PUBL) for each Sourcesource, which includes the Titletitle. So you might want to exclude the Title title of Sources sources from the Complete Individual Report complete individual report in Gramps to avoid duplication.
=====Citation Title title only used in Evidentia=====Citation Titles titles are only used within the Evidentia program, and don't effect grampsGramps. So, choose whatever pattern you like for naming them.
====Claims & Proofand proof ====
===== Default GEDCOM export =====
When you export a "Subject" into a GEDCOM file, Evidentia's default export will automatically include that person's:
* individual Individual information: id, name, gender* claim Claim type: facts, events, or attributes* source Source information: title, abbreviation, and full publication info (PUBL)* full Full citation (PAGE)
If you entered a date (DATE) or place (PLAC) for a particular claim (event/fact), that will also be exported, so be sure to type the place name in precisely to avoid creating duplicates in Gramps.
===== Evidentia-specific GEDCOM export =====
Evidentia's GEDCOM export does NOT not include the full Proof Report (although you could save that report as a PDF and add manually add it to your media in Gramps). If you do use Evidentia's recommended export settings, the claim analysis will be added as a note to the citation, and the proof conclusion will be added as a note to the event/fact. For example:
* Citation Note with the Claim Analysis: "The 'Citation Title 1' asserts that Lakshmi Wolowitz was 30 years old when this census was taken in 1840.
The age given in the 1840 census suggests that Lakshmi was born about 1810. However, the accuracy of census data varies widely."
* Event Note with Proof Conclusion: "Until given stronger evidence of Lakshmi's birth date, it can only tentatively be concluded that she was born in 1810."
=== Family Tree Maker (FTM)===
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]].
====If you do not have access to Family Tree Maker:====
(Tested with FTW file created by Family Tree Maker 2006)
* Download and install the free MyHeritage Family Tree Builder:
* File > Export GEDCOM...
====Specific instructions for FTM2005:Family Tree Maker 2005 ====
Select File->Export File->Entire File...
In file dialog, enter a filename and select "GEDCOM(*.GED)" from the "Save as type" dropdown.
In the "Export to GEDCOM" dialog, set the following:
* Select "Abbreviate tags"
Media objects must be imported manually. It's a painfully laborious process. Here's a trick that might help ease the pain: Bring up the "Scrapbook" view on any family member. Hit Press F2. This , which lists all individuals. By double-clicking on an entry, it will take you to that individual's scrapbook page. Hitting Pressing F2 again will bring up the list at the point where you left off.
{{man note|Description or value associated to event on place field|Gramps made an exception for Family Tree Maker, which violates the GEDCOM spec by using the PLAC field to store the description or value associated with the event. Unfortunately, Gramps cannot fix all errors and tries to do the best for properly importing user data.}}
# Double dates use the first date rather than the second
====Programs for fixing some of the known problems====
====Experimental way====
==== Gedcom ====
GenoPro can generate custom (invalid) gedcom GEDCOM [http://sourceforge.net/mailarchive/message.php?msg_id=27539893] but also better one [http://sourceforge.net/mailarchive/message.php?msg_id=27547464].
==== GenoPro to Gramps ====
=== Heredis ===
'''Modifications of gedcom GEDCOM from Heredis to import in Gramps'''
''With editor (like gedit ot note++) find and replace '''« > »''':''
====Known issues====
According to "''Ancestris''" wiki, Gedcom GEDCOM generated by Heredis may :
# Add some empty tag - need to add Y on most event DEAT, MARR, MARC, DIV.
# Not properly manage sources and repositories
There are some alternatives to Gedcom GEDCOM generated by Heredis :
* Heredis format to Gedcom GEDCOM : [http://sourceforge.net/projects/hr2ged/ project on sourceforge].
* A python library to "read-only" Heredis file : [http://sourceforge.net/projects/hrlib project on sourceforge].
* Heredis format to Database : [http://loic.fejoz.free.fr/hr2db/ project (in french)].
This is the easy option, but much of your data may not transfer correctly. Try it first anyway in case it works for you.
Read this first: [http://tmgmjh-nm.reigelridge.comnet/GED-EXPT.HTML TMG™ GEDCOM Export - Guide to Limitations and Issues ©MJH(Michael J. Hannah)][http://archiver.rootsweb.ancestry.com/th/read/TMG/2014-09/1409969819]
Then with that in mind:
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.
{{man note|Note|The official version of tmg2gramps does not work with well with TMG v8 databases, because of changed relation types. This can be corrected with a modified tmg2gramps.pl file, which can be downloaded [[Media:Tmg2gramps-v8.gz|here]] or [https://github.com/sam-m888/tmg2gramps/tree/master/tmg2gramps-v8 here]. To apply this upgrade, you must first unpack the official download, and then overwrite the tmg2gramps.pl file with the version above.}} ===== 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 ===== Running Here are some known issues that have occurred when using tmg2gramps to convert a TMG v6 database and importing it to Gramps v4.0.4-1: # 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.2_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. ===== Preparing to run tmg2gramps ===== Successfully running tmg2gramps for the first time can be a bit daunting for non-programmers, but is still of course quite feasible. The following instructions were written based on using a TMG v6 database and running tmg2gramps on Linux Ubuntu 14.04. ====== Copy your TMG projects folder ======Before beginning, copy your entire TMG '<code>projects</code>' folder to your linux home folder. It is also a good a idea to keep a backup copy of your TMG '<code>projects</code>' folder for posterity, just in case you may someday need it. On Windows XP, the TMG '<code>projects</code>' folder is located here: <code>C:\Program Files\The Master Genealogist\projects</code> ====== Rename your copied TMG projects folder ======Once you've copied it, rename the copied '<code>projects</code>' folder to '<code>tmgdata</code>' ====== Convert TMG filenames to lowercase ======Now, in order to run tmg2gramps properly on linux, it is necessary to make sure the contents of '<code>tmgdata</code>' is all lowercase, including extensions. The easiest way to achieve this is to open your linux terminal and navigate to the '<code>tmgdata</code>' directory. Once there, simply type this at the command prompt:
Now, make sure that you can connect to the database with the appropriate password and privileges by typing:
You can now exit MySQL:
This will display all the files listed in the folder...and prepare to run tmg2gramps. Make sure that you know the original The name of your TMG project (or projects if you have more than one) will be the name of the file that you are going to convertprecedes the underscores. The For example below makes the following assumptions, if your project (or one of your projects) is called 'smith,' you will see files such as:
==== TMG-Working-Group ====
==== tmgviewer ====
An attempt at reading a TMG file Directly from python and does . (Does not use TMG's Genbridge). * [[userAddon:sam888TMGimporter]]- WIP - Not released yet.
See {{bug|7591}} for more details and tests.
According to a "''Ancestris''" wiki, GEDCOM generated by Visuged 8.40.0 seems to definitively corrupt your data !
# Partials Partial sources
# Repositories are lost
# BAPT, ASSO are lost
