Changes

Jump to: navigation, search

Import from another genealogy program

1,874 bytes added, 06:44, 7 January 2017
Ancestry.com
=== Ancestry.com ===
 
{{stub}}
Older
This is Bug#{{bug|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 tests 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 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.
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 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.
=== Evidentia ===
6
edits

Navigation menu