![]() ![]() If so, you can check the Show more details checkbox to see more about the difference. Sometimes it may be difficult to determine enough about the difference to figure out what is going on. If an Action has been selected, the pane also includes a 'Result >' for each sub-object and item that has a difference. If no Action is made yet, the pane will show the 'Original >' and 'Imported >' state for each sub-object and item that has a difference. When an item in the top pane is selected, the lower pane shows the specific differences. Click on the column header to change the sort. You can sort the top pane by Status ( Object will be a sub-sort), Object, ID, Object Name/Description (will be grouped by Object) and Action. For example type '#I0103' to search for the individual with ID I0103. You can search for items by 'ID' field by typing '#' and then the characters to match. Or type 'magn' which is more likely to land on the right place. For example if you are looking for 'Smith, Magnes' in the 'amps' tree, you could type 'smi' which would jump the selection to the first of the lines containing these characters, and then use cursor up/down keys to find the 'Smith' you are looking for. The top pane must be active for this to work. You can search for items by Name by just typing characters to match. The top pane also shows the Object type ( Person, Family, Media etc.), its Gramps ID, an Object Name or Description, and the selected Action (more later). And Missing items were found in your current tree, but not in the imported tree. Added items are found only in your imported tree. ![]() ![]() Different items were found in both the current and imported trees, but had been changed in some way. The top pane shows a 'Status' which is one of Different, Added, or Missing. Items that were the same (since they were derived from the common Gramps tree) are not shown. The top pane is a scrollable and selectable view of individual items that were found to be different in your import. The bottom part provides control and 'Action' buttons and a hint that changes depending on what you are doing. When this is complete you end up with a three part window. When you have selected a file to import, the main tool window comes up and some progress meters pop up indicating the import and comparison process. You are then presented with the import file dialog, which shows '.gramps' files from your import location. The tool will start with an 'Undo history warning' that suggest that you back up your work. Once installed, it is run by using the Tools -> Family Tree Processing -> Import and Merge tool. The tool can be installed like any other Addon see Installing Addons in Gramps If something goes wrong, you will have a way to go back and start over. Back up your current tree BEFORE using this tool to merge. Mass changes mean more potential for mangling the data. This tool helps to merge these back together. But then I may forget to copy it back to my home desktop computer until after I've made more updates. I often take a copy of my tree on my laptop when traveling and sometimes I make updates while on the road. The derived trees need not be limited to those edited by someone else. You'd still need to hand compare every record. this tool won't be any easier than a manual merge after a standard import. Then the tool focuses you on just the changes.īut say the other user doesn't use Gramps, so you exported with GEDCOM (or another format) and got it back? Sorry. It depends on the two Trees sharing common internal handles (not just the user-editable IDs) to simplify ignoring unchanged records. That synchronization is what this tool is designed to facilitate. without losing the useful changes from either tree. You can't just give the person a fresh copy of your Tree because then their changes would be overwritten.Īt some point, you may want to merge the forks into a common tree. Programmers call this a 'fork.' (As in: when travelers come to a 'fork in the road' and each chooses different paths.) But the bottom line is that you now have two tree variants derived from a common Tree and you want share your updated Tree. (You can verify the Trees differ and log those revisions with the Database Differences addon report.) Then each person makes changes to the copy in their possession using Gramps locally. This tool this requires that the Family Tree being merged must be a Gramps Family Tree derived from a version of the currently loaded Family Tree.Ī situation occurs occasionally after giving someone a copy of your tree in our native Gramps XML format. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |