Difference between revisions of "Gramps 4.2 Wiki Manual - Manage Family Trees"

From Gramps
Jump to: navigation, search
(Exporting data)
m (Protected "Gramps 4.2 Wiki Manual - Manage Family Trees": fix protection (lost after migration!) ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite)))
 
(29 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{grampsmanualcopyright}}
 
 
 
{{man index|Gramps 4.2 Wiki Manual - Categories|Gramps 4.2 Wiki Manual - Manage Family Trees: CSV Import and Export|4.2}}
 
{{man index|Gramps 4.2 Wiki Manual - Categories|Gramps 4.2 Wiki Manual - Manage Family Trees: CSV Import and Export|4.2}}
 
 
{{languages|Gramps_4.2_Wiki_Manual_-_Manage_Family_Trees}}
 
{{languages|Gramps_4.2_Wiki_Manual_-_Manage_Family_Trees}}
 
 
{{#vardefine:chapter|5}}
 
{{#vardefine:chapter|5}}
 
{{#vardefine:figure|0}}
 
{{#vardefine:figure|0}}
{{out of date}}
 
 
A detailed exploration of the day-to-day use of Gramps. In this Chapter we give a detailed overview of how you can manage your family trees, as well as share your data with other genealogists.
 
A detailed exploration of the day-to-day use of Gramps. In this Chapter we give a detailed overview of how you can manage your family trees, as well as share your data with other genealogists.
  
 
== Starting a new Family Tree ==
 
== Starting a new Family Tree ==
  
[[Image:ManageFamilyTrees-40.png|right|thumb|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Starting Family Trees]]
+
To start a new Family Tree, choose the menu {{man menu|Family Trees ->Manage Family Trees...}} or select the toolbar {{icon|ance}}{{man button|Family Trees}} button or use the [[Gramps_4.2_Wiki_Manual_-_Keybindings|keybinding]] {{man key press|CTRL|O}}. This will open the {{man label|[[Gramps_4.2_Wiki_Manual_-_Manage_Family_Trees#Family_Trees_manager_window|Family Trees]]}} manager window.
 
 
To start a new Family Tree, choose the menu {{man menu|Family Trees ->Manage Family Trees...}} or select the toolbar {{icon|ance}}{{man button|Family Trees}} button or use the [[Gramps_4.2_Wiki_Manual_-_Keybindings|keybinding]] {{man key press|CTRL|O}}. This will open the {{man label|Family Trees}} manager window(See Fig. 5.1).
 
  
 
Select the {{man button|New}} button and to add a new Family Tree entry to the list of Family Trees. To change its name from the default ''<code>Family Tree 1</code>'', select the name and press the {{man button|Rename}} button then type in a new name.
 
Select the {{man button|New}} button and to add a new Family Tree entry to the list of Family Trees. To change its name from the default ''<code>Family Tree 1</code>'', select the name and press the {{man button|Rename}} button then type in a new name.
  
 
To open the new, empty select the Family Tree and either double click or press the {{man button|Load Family Tree}} button to load.
 
To open the new, empty select the Family Tree and either double click or press the {{man button|Load Family Tree}} button to load.
 +
{{-}}
 +
=== Family Trees manager window ===
 +
 +
[[Image:ManageFamilyTrees-40.png|right|thumb|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Starting Family Trees]]
 +
 
{{-}}
 
{{-}}
  
Line 52: Line 50:
 
== Backing up a Family Tree ==
 
== Backing up a Family Tree ==
  
*The safest way to backup your Gramps Family Tree is to export without privacy options and filters to '''Gramps XML''' format (or '''Gramps XML Package''' to include items from your Gallery) and copy the resultant file to a safe place, preferably in a different building.
+
The safest way to backup your Gramps Family Tree is to export without privacy options and filters to '''Gramps XML''' format (or '''Gramps XML Package''' to include items from your Gallery) and copy the resultant file to a safe place, preferably in a different building.
  
 
=== Backup dialog ===
 
=== Backup dialog ===
Line 92: Line 90:
 
*Gramps version 4.2 :
 
*Gramps version 4.2 :
 
  ~/.gramps/gramps42/gramps.ini
 
  ~/.gramps/gramps42/gramps.ini
 
  
 
*You can use the Archive feature (see next section) to store snapshots of your Family Tree. These snapshots can be used as simple backups, very useful if you want to try something that you might later want to undo. However this method should not be used for standard backups, as it will not survive a hard disk crash or most of the other disasters that can befall a computer.
 
*You can use the Archive feature (see next section) to store snapshots of your Family Tree. These snapshots can be used as simple backups, very useful if you want to try something that you might later want to undo. However this method should not be used for standard backups, as it will not survive a hard disk crash or most of the other disasters that can befall a computer.
Line 179: Line 176:
  
 
Importing allows you to transfer data from other genealogy programs into a Gramps Family Tree. Gramps can import data from the following formats:
 
Importing allows you to transfer data from other genealogy programs into a Gramps Family Tree. Gramps can import data from the following formats:
* [[#Gramps_XML_and_XML_Package_import|Gramps XML]] (.gramps file extension)
+
* [[#Gramps_XML_and_XML_Package_import|Gramps XML]] (<code>.gramps</code> file extension)
* [[#Gramps_XML_and_XML_Package_import|Gramps XML Package]] (.gpkg file extension)
+
* [[#Gramps_XML_and_XML_Package_import|Gramps XML Package]] (<code>.gpkg</code> file extension)
* [[#Gramps_CSV_import|GRAMPS CSV Spreadsheet]] - comma separated values (.csv file extension)
+
* [[#Gramps_CSV_import|Gramps CSV Spreadsheet]] - comma separated values (<code>.csv</code> file extension)
* [[#GRAMPS_V2.x_database_import|GRAMPS V2.x database]] (.grdb file extension)
+
* [[#GRAMPS_V2.x_database_import|GRAMPS V2.x database]] (<code>.grdb</code> file extension)
* [[#GEDCOM_import|GEDCOM]] (.ged file extension)
+
* [[#GEDCOM_import|GEDCOM]] (<code>.ged</code> file extension)
* GeneWeb (.gw file extension)
+
* GeneWeb (<code>.gw</code> file extension)
* Pro-Gen (.def file extension)
+
* Pro-Gen (<code>.def</code> file extension)
  
 
===Import Family Tree dialog===
 
===Import Family Tree dialog===
[[File:xxx.png|thumb|right|400px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} xxxxx]]
 
  
To import data, select the menu {{man menu|Family Trees ->Import}} or the [[Gramps_4.2_Wiki_Manual_-_Keybindings#2|keybinding]] {{Man key press|CTRL|I}}. Either the {{man label|Undo history warning}} dialog will open if you attempt to import into an existing Family Tree (Note that you can only import data into an existing database so if you are transferring all your data from another program or from an older version of Gramps, then first create a new empty Family Tree and then import the data into it.) or the '''{{man label|Import Family Tree}}''' dialog will open, asking you to specify the file you wish to import.
+
{{man note|Note that you can only import data into an existing database|So if you are transferring all your data from another program it is recommended that you create a new empty Family Tree and then import the data into it}}
 +
 
 +
<!--[[File:xxx.png|thumb|right|400px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} xxxxx]]-->
 +
 
 +
First create a [[Gramps_4.2_Wiki_Manual_-_Manage_Family_Trees#Starting_a_new_Family_Tree|new empty Family Tree]]. Then select the menu {{man menu|Family Trees ->Import}} or the [[Gramps_4.2_Wiki_Manual_-_Keybindings#2|keybinding]] {{Man key press|CTRL|I}} to import data or restore a previously saved Gramps Family Tree (from an older version of Gramps or the current version) the '''{{man label|Import Family Tree}}''' dialog will open, asking you to specify the file you wish to import.
 +
 
 +
If you attempt to import into an existing Family Tree the {{man label|Undo history warning}} dialog will open giving you the opportunity to stop the import and create a new Family Tree, unless you are deliberately attempting to merge data.
  
 
{{man warn|Data loss with some formats |It is important to note that there is no direct one-to-one correspondence between all the features of Gramps and those of GEDCOM or GeneWeb or Pro-Gen. Therefore, when importing from any of these formats data may be lost. Details of data that may be lost from GEDCOM is given [[#GEDCOM_import|below]].}}
 
{{man warn|Data loss with some formats |It is important to note that there is no direct one-to-one correspondence between all the features of Gramps and those of GEDCOM or GeneWeb or Pro-Gen. Therefore, when importing from any of these formats data may be lost. Details of data that may be lost from GEDCOM is given [[#GEDCOM_import|below]].}}
Line 206: Line 208:
 
=== Gramps XML and XML Package import ===
 
=== Gramps XML and XML Package import ===
  
The Gramps [[XML]] and Gramps [[XML]] Package database are the native Gramps formats. There is no risk of information loss when importing from or exporting to these formats.
+
The Gramps [[XML]] and Gramps [[XML]] Package database are the native Gramps formats. There is no risk of information loss when importing (restore) from or exporting to these formats.
  
 
*Gramps [[XML]] (.gramps): The Gramps [[XML]] file is the standard Gramps data-exchange and backups format, and was also the default working-database format for older (pre 2.x) versions of Gramps. Unlike the GRAMPS V2.x grdb format, it is architecture independent and human-readable. The database may also have references to non-local (external) media objects, therefore it is not guaranteed to be completely portable (for full portability including media objects in the Gramps [[XML]] package (.gpkg) should be used). The Gramps [[XML]] database is created by exporting (Menu {{man menu|Family Trees ->Export...}}) to that format.
 
*Gramps [[XML]] (.gramps): The Gramps [[XML]] file is the standard Gramps data-exchange and backups format, and was also the default working-database format for older (pre 2.x) versions of Gramps. Unlike the GRAMPS V2.x grdb format, it is architecture independent and human-readable. The database may also have references to non-local (external) media objects, therefore it is not guaranteed to be completely portable (for full portability including media objects in the Gramps [[XML]] package (.gpkg) should be used). The Gramps [[XML]] database is created by exporting (Menu {{man menu|Family Trees ->Export...}}) to that format.
Line 216: Line 218:
 
=== Gramps CSV import ===
 
=== Gramps CSV import ===
  
*The GRAMPS CSV Spreadsheet format allows importing and exporting of a subset of your Gramps data in a simple spreadsheet format. See [[Gramps 4.2 Wiki Manual - Manage Family Trees: CSV Import and Export|CSV Import and Export]] for more information.
+
*The Gramps CSV Spreadsheet format allows importing and exporting of a subset of your Gramps data in a simple spreadsheet format. See [[Gramps 4.2 Wiki Manual - Manage Family Trees: CSV Import and Export|CSV Import and Export]] for more information.
  
 
=== GEDCOM import ===
 
=== GEDCOM import ===
  
[[File:GEDCOM-import-report.png|right|400px|thumb|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} GEDCOM import report - example results.]]
+
When you import information from GEDCOM, Gramps main window will show you a [[Gramps_4.2_Wiki_Manual_-_Main_Window#Status_Bar_and_Progress_Bar|progress bar]]. When the GEDCOM import finishes, the {{man label|Import Statistics}} window and the '''{{man label|GEDCOM import report:}}''' windows show any data that was not imported. The '''{{man label|GEDCOM import report:}}''' details most of the GEDCOM lines that were either ignored or could not be understood (Most likely as they are not part of the GEDCOM 5.5.1 standard. See [[GEDCOM Extensions]]). The contents of the GEDCOM line (or lines where there are continuation lines) are also shown. In some cases, the lines may not be exactly what is contained in the input GEDCOM file, because the line is reconstructed following some processing.
 
 
When you import information from GEDCOM, Gramps main window will show you a progress bar. When the GEDCOM import finishes, the '''GEDCOM import report:''' window shows any data that was not imported. The '''GEDCOM import report:''' details most of the lines that were either ignored or could not be understood (Most likely as they are not part of the GEDCOM 5.5 standard. See [[GEDCOM Extensions]]). The contents of the line (or lines where there are continuation lines) are also shown. In some cases, the lines may not be exactly what is contained in the input GEDCOM file, because the line is reconstructed following some processing.
 
  
 
Gramps uses a different 'data model' from GEDCOM and therefore some data in GEDCOM cannot be imported into Gramps (See [[Gramps and GEDCOM]]).
 
Gramps uses a different 'data model' from GEDCOM and therefore some data in GEDCOM cannot be imported into Gramps (See [[Gramps and GEDCOM]]).
Line 240: Line 240:
 
{{-}}
 
{{-}}
  
This section describes any GEDCOM data that cannot be directly represented in Gramps, and how it is
+
==== Import Statistics dialog ====
handled. For additional information on the limits of GEDCOM imports (and exports), please read the section on [[Gramps and GEDCOM]].
+
{{-}}
 +
==== GEDCOM import report dialog ====
 +
[[File:GEDCOM-import-report.png|right|400px|thumb|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} GEDCOM import report - example results.]]
  
==== HEADer, SUBMitter and SUBmissioN ====
+
{{-}}
 +
==== GEDCOM import limitations ====
 +
This section describes any GEDCOM data that cannot be directly represented in Gramps, and how it is handled. For additional information on the limits of GEDCOM imports (and exports), please read the section on [[Gramps and GEDCOM]].
  
Gramps has no direct representation of this data, and hence all information there has to be stored
+
===== HEADer, SUBMitter and SUBmissioN =====
in other objects. Depending on a [[Gramps_4.2_Wiki_Manual_-_Settings#General|General preferences]]
+
 
setting, a 'default source' object may be created. If this is created, then much of the data is
+
Gramps has no direct representation of this data, and hence all information there has to be stored in other objects. Depending on a [[Gramps_4.2_Wiki_Manual_-_Settings#General|General preferences]] setting, a 'default source' object may be created. If this is created, then much of the data is stored in that {{man label|Source}}, or in {{man label|Repositories}} attached to that source.
stored in that {{man label|Source}}, or in {{man label|Repositories}} attached to that source.
 
  
 
     HEADER:=
 
     HEADER:=
Line 314: Line 317:
 
* RFN and RIN are ignored
 
* RFN and RIN are ignored
  
==== INDIvidual ====
+
===== INDIvidual =====
  
 
The INDIVIDUAL_RECORD is stored as a Gramps {{man label|Person}} record, except as indicated in bold below.
 
The INDIVIDUAL_RECORD is stored as a Gramps {{man label|Person}} record, except as indicated in bold below.
Line 388: Line 391:
 
* Individual attribute structure, type, date, place structure, address structure, age, agency, cause and multimedia link are all ignored.  
 
* Individual attribute structure, type, date, place structure, address structure, age, agency, cause and multimedia link are all ignored.  
  
==== FAM_RECORD ====
+
===== FAM_RECORD =====
  
 
The FAM_RECORD is stored as a Gramps {{man label|Family}} record.
 
The FAM_RECORD is stored as a Gramps {{man label|Family}} record.
Line 412: Line 415:
 
* The REFN and REFN:TYPE are stored as {{man label|Attributes}} of the {{man label|Family}}, but if there is more than one REFN, it may not be clear which TYPE is associated with which REFN.
 
* The REFN and REFN:TYPE are stored as {{man label|Attributes}} of the {{man label|Family}}, but if there is more than one REFN, it may not be clear which TYPE is associated with which REFN.
  
==== SOURCE_RECORD ====
+
===== SOURCE_RECORD =====
  
 
The SOURCE_RECORD is stored as a Gramps {{man label|Source}} record, except as indicated in bold below.
 
The SOURCE_RECORD is stored as a Gramps {{man label|Source}} record, except as indicated in bold below.
Line 443: Line 446:
 
* DATA and its subsidiary records are ignored
 
* DATA and its subsidiary records are ignored
  
==== REPOSITORY_RECORD ====
+
===== REPOSITORY_RECORD =====
  
 
The REPOSITORY_RECORD is stored as a Gramps {{man label|Repository}} record, except as indicated in bold below.
 
The REPOSITORY_RECORD is stored as a Gramps {{man label|Repository}} record, except as indicated in bold below.
Line 459: Line 462:
 
* REFN, REFN:TYPE and RIN are ignored
 
* REFN, REFN:TYPE and RIN are ignored
  
==== MULTIMEDIA_RECORD ====
+
===== MULTIMEDIA_RECORD =====
  
 
The MULTIMEDIA_RECORD is stored as a Gramps {{man label|Media}} record, except as indicated in bold below.
 
The MULTIMEDIA_RECORD is stored as a Gramps {{man label|Media}} record, except as indicated in bold below.
Line 480: Line 483:
 
* REFN, REFN:TYPE and RIN are ignored
 
* REFN, REFN:TYPE and RIN are ignored
  
==== NOTE_RECORD ====
+
===== NOTE_RECORD =====
  
 
The NOTE_RECORD is stored as a Gramps {{man label|Note}} record, except as indicated in bold below.
 
The NOTE_RECORD is stored as a Gramps {{man label|Note}} record, except as indicated in bold below.
Line 498: Line 501:
 
== Exporting data ==
 
== Exporting data ==
  
{{Out of date|TODO Need to update this content.}}
+
 
  
 
{{man note| Export is saving a copy |When you export, you are saving a copy of the currently opened database. Exporting creates another file with a copy of your data. Note that the database that remains opened in your Gramps window is NOT the file saved by your export. Additional editing of the currently opened database will not alter the copy produced by the export.}}
 
{{man note| Export is saving a copy |When you export, you are saving a copy of the currently opened database. Exporting creates another file with a copy of your data. Note that the database that remains opened in your Gramps window is NOT the file saved by your export. Additional editing of the currently opened database will not alter the copy produced by the export.}}
Line 518: Line 521:
  
 
===Filters and privacy===
 
===Filters and privacy===
 +
 +
[[Image:ExportAssistantGEDCOM-ExportOptions-40.png|right|450px|thumb|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Export assistant: Filters and privacy export options]]
  
 
Gramps allows you to export a database into common file formats.
 
Gramps allows you to export a database into common file formats.
Line 533: Line 538:
 
Sometimes, it is not always obvious from the data if someone is actually alive. Gramps uses an advanced algorithm to try to determine [[Gramps_4.2_Wiki_Manual_-_Probably_Alive|if a person could still be alive]]. Remember, Gramps is making its best guess, and it may not always be able to guess correctly all the time. Please double check your data.
 
Sometimes, it is not always obvious from the data if someone is actually alive. Gramps uses an advanced algorithm to try to determine [[Gramps_4.2_Wiki_Manual_-_Probably_Alive|if a person could still be alive]]. Remember, Gramps is making its best guess, and it may not always be able to guess correctly all the time. Please double check your data.
 
{{-}}
 
{{-}}
 +
 
=== Export into Gramps formats ===
 
=== Export into Gramps formats ===
  
Line 546: Line 552:
 
{{-}}
 
{{-}}
 
=== Exporting into the GEDCOM format ===
 
=== Exporting into the GEDCOM format ===
{{out of date}}
+
 
  
 
[[Image:ExportAssistantGEDCOM-ExportOptions-40.png|right|450px|thumb|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Export assistant: GEDCOM Export options]]
 
[[Image:ExportAssistantGEDCOM-ExportOptions-40.png|right|450px|thumb|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Export assistant: GEDCOM Export options]]
  
Gramps allows you to export a database into the common GEDCOM format. See [[Gramps and GEDCOM]] for a specification of data which is not exported when exporting to GEDCOM (use Gramps XML for a full export). Gramps provides options that allow you to fine tune your export (see Fig.4.8).
+
Gramps allows you to export a database into the common GEDCOM format. See [[Gramps and GEDCOM]] for a specification of data which is not exported when exporting to GEDCOM (use Gramps XML for a full export). Gramps provides options that allow you to fine tune your export.
  
 
*Filters on People and Notes: Filters allow you to export a limited amount of data, based on the criteria you select.
 
*Filters on People and Notes: Filters allow you to export a limited amount of data, based on the criteria you select.
Line 564: Line 570:
 
=== Export into other formats ===
 
=== Export into other formats ===
  
*Web Family Tree: Exporting to Web Family Tree will create a text file that can be used by the Web Family Tree program. Export options include filter selection and the ability to limit data on living people to that of their family ties.
+
==== GeneWeb ====
 +
*GeneWeb: Exporting to GeneWeb will save a copy of your data into a popular web genealogy format. To find out more about GeneWeb and its format, visit http://www.geneweb.org
 +
 
 +
==== Gramps CSV Spreadsheet format ====
 +
*Gramps CSV Spreadsheet format: Allows exporting (and importing) a subset of your Gramps data in a simple spreadsheet format. See [[Gramps 4.2 Wiki Manual - Manage Family Trees: CSV Import and Export|CSV Import and Export]] for more information. Also, see  [[Gramps_4.2_Wiki_Manual_-_Settings#Export_View|Export Display]] .
  
*GeneWeb: Exporting to GeneWeb will save a copy of your data into a popular web genealogy format. To find out more about GeneWeb and its format, visit http://cristal.inria.fr/~ddr/GeneWeb/en/.
+
==== Web Family Tree ====
 +
*Web Family Tree: Exporting to Web Family Tree will create a text file that can be used by the Web Family Tree program. Export options include filter selection and the ability to limit data on living people to that of their family ties. To find out more about Web Family Tree and its format, visit http://www.simonward.com/cgi-bin/page.pl?family/tree
  
*vCalendar and vCard: Exporting to vCalendar or vCard will save information in a format used in many calendaring and addressbook applications, sometimes called PIM for Personal Information Manager.
+
==== vCard ====
 +
*vCard: Exporting to vCard will save information in a format used in many addressbook applications, sometimes called PIM for Personal Information Manager. For more information on the format see: https://en.wikipedia.org/wiki/VCard
  
*Gramps CSV Spreadsheet format: Allows exporting (and importing) a subset of your Gramps data in a simple spreadsheet format. See [[Gramps 4.2 Wiki Manual - Manage Family Trees: CSV Import and Export|CSV Import and Export]] for more information. Also, see  [[Gramps_4.2_Wiki_Manual_-_Settings#Export_View...|Export Display]] .
+
==== vCalendar ====
 +
*vCalendar: Exporting to vCalendar will save information in a format used in many calendaring applications, sometimes called PIM for Personal Information Manager. For more information on the format see: https://en.wikipedia.org/wiki/ICalendar#vCalendar_1.0
 
{{-}}
 
{{-}}
  
Line 582: Line 595:
  
 
{{man index|Gramps 4.2 Wiki Manual - Categories|Gramps 4.2 Wiki Manual - Manage Family Trees: CSV Import and Export|4.2}}
 
{{man index|Gramps 4.2 Wiki Manual - Categories|Gramps 4.2 Wiki Manual - Manage Family Trees: CSV Import and Export|4.2}}
 +
 +
{{grampsmanualcopyright}}
  
 
[[Category:Documentation]]
 
[[Category:Documentation]]

Latest revision as of 01:31, 23 February 2020

Previous Index Next


A detailed exploration of the day-to-day use of Gramps. In this Chapter we give a detailed overview of how you can manage your family trees, as well as share your data with other genealogists.

Starting a new Family Tree

To start a new Family Tree, choose the menu Family Trees ->Manage Family Trees... or select the toolbar ChartsFamily Trees button or use the keybinding CTRL+O. This will open the Family Trees manager window.

Select the New button and to add a new Family Tree entry to the list of Family Trees. To change its name from the default Family Tree 1, select the name and press the Rename button then type in a new name.

To open the new, empty select the Family Tree and either double click or press the Load Family Tree button to load.

Family Trees manager window

Fig. 5.1 Starting Family Trees


Opening a Family Tree

To open a Family Tree, either choose the menu Family Trees ->Manage Family Trees... or click the Toolbar Family Trees button. The Family Tree Manager will appear and you will see a list of all the Family Trees known to Gramps. In the Status column an icon (looks like an open folder) will display beside any Family Tree that is currently open. Select the tree you want to open, and open it by selecting the Load Family Tree button. Alternatively you can double-click on the desired Family Tree.

To open a recently accessed Family Tree, choose either the menu Family Trees ->Open Recent or the down arrow next to the Toolbar Family Trees button and select the Family Tree from the list.


Gnome-important.png
Read Only Mode

If you do not have "write permissions" for the selected Family Tree, it will be opened in a Read Only mode. In this mode, the data may be viewed, but no changes will be made to the Family Tree. To indicate this mode, the title of the main window will be appended with (Read Only) text.

Opening a GEDCOM or XML database

Gramps allows you to open certain databases that have not been saved in Gramps own file format from the command line, see Command line references. These include XML and GEDCOM databases. But you should be aware that if the XML or GEDCOM database is relatively large, you will encounter performance problems, and in the event of a crash your data can be corrupted. Hence, it is normally better to create a new Gramps family tree (database) and import your XML/GEDCOM data into it.

Gramps-notes.png
Opening databases

XML and GEDCOM databases require all data to be held in memory and don't contain indexes. Gramps native format is a database that only reads the data needed. Thus, for a large family tree the data can be accessed quicker and more efficiently by not using XML or GEDCOM.

Gnome-important.png
GEDCOM Editing

Please keep in mind that some information in a GEDCOM file may be lost during import into Gramps as well as export back to GEDCOM. Simply opening and viewing the file will not change it. However, if any changes were made and they were not abandoned upon exit, exiting Gramps will save the data, with possible data loss.

Deleting a Family Tree

Select the family tree you want removed, and click the Delete button.

This will completely remove the tree, with no possibility to retrieve the data. Consider taking a backup of your data by exporting to the GRAMPS XML format, and storing that file.

Renaming a Family Tree

You can rename a Family Tree (or an archive of it) by selecting the tree you want to rename and clicking Rename. You can also click on the name in the list of trees.

In either case, you just type in the new name to have it take effect.

Backing up a Family Tree

The safest way to backup your Gramps Family Tree is to export without privacy options and filters to Gramps XML format (or Gramps XML Package to include items from your Gallery) and copy the resultant file to a safe place, preferably in a different building.

Backup dialog

Fig. 5.2 Making a backup

From the menu simply select Family Trees > Make Backup..."

The Gramps XML Backup window will appear.

You can enter the path where the backup should be stored manually or using the path selector button.

You can enter a file name manually or use the automatically generated file name.

You can either choose to Include(default) or Exclude the Media:.

Gramps-notes.png
Note

This is just a regular XML export, except that no data is filtered out. You can import these as usual with any exported file.


Advanced settings

You can also define the pattern for the backup filename by setting the paths.quick-backup-filename in the ~/.gramps/gramps42/gramps.ini key file like the following:

[paths]
quick-backup-filename='%(filename)s_%(year)d-%(month)02d-%(day)02d.%(extension)s'

You can use any of the following keywords in the pattern:

  • filename
  • year
  • month
  • day
  • hour
  • minutes
  • seconds
  • extension :
    • .gpkg(default) if you include media.
    • .gramps if you exclude media.

Use the appropriate ~/.gramps/gramps{XX}/gramps.ini key file.

  • Gramps version 4.2 :
~/.gramps/gramps42/gramps.ini
  • You can use the Archive feature (see next section) to store snapshots of your Family Tree. These snapshots can be used as simple backups, very useful if you want to try something that you might later want to undo. However this method should not be used for standard backups, as it will not survive a hard disk crash or most of the other disasters that can befall a computer.
  • For advanced users: each database is stored in its own subdirectory under ~/.gramps. A manual backup can be made by backing up this directory.

Archiving a Family Tree

Tango-Dialog-information.png
Note

The Archive option is only present if GNU Revision Control System (RCS) is present so that Gramps can use it. You normally need to install this separate from Gramps.

You can easily archive and timestamp family trees with Gramps use of GNU Revision Control System or RCS if installed. For this to be possible this utility must be installed on your computer.

To make an archive :

Fig. 5.3 Archive a Family Tree example
  1. load your Family Tree.
  2. click on the Toolbar ChartsFamily Trees button (it displays Connect to a recent database when you hover over it).
  3. click on the family tree you have just loaded: the Archive button should appear.
  4. click on Archive and you will be asked to enter a "Revision comment - Version description" for your archive.

After archiving, the list of family trees will now show your original family tree with a right-pointing triangle on its left.

  • Click on the triangle to display the archive name.(Click again to collapse the archive list).

Archives can be deleted, renamed and Extracted.


Extracting a Family Tree Archive

Fig. 5.4 Selecting a version to extract

If you click on an archive, the Extract button becomes visible. Click on this to obtain the extracted archive. It will appear in the family tree list as <name of original tree>:<name of archive> and is now an independent family tree. This can be a useful way of preserving an archive, because archives disappear if the originating tree is deleted; and they are not incorporated into a Portable Gramps XML export of the tree.

Simply highlight the archive you want to restore, and select the Extract button.

Fig. 5.5 Extracted version shown

Gramps will transfer the archive into a new Family Tree. The Family Tree name is based on the original name and the archive name (see also Archiving a Family Tree).


Unlocking a Family Tree

Fig. 5.6 Locked Family tree -Example Dialog

When Gramps opens a tree, it locks the tree, preventing you or anyone else opening it at the same time. A second copy of Gramps will be able to open another family tree, but the tree already open will appear with the lock icon, indicating you cannot open it. Closing the tree in the first copy of Gramps will make it available to be opened in the second copy.

If you could open the same Family Tree in two Gramps at once, it is likely your data would be damaged.
In the unlikely event of a crash of Gramps, the family tree will be left in a locked state. To unlock the tree:

Fig. 5.7 Database is locked
  • If Gramps has been set to open a tree automatically on startup, then you will see the 'Database is locked' dialogue. Click on the Close button and the Family Tree Manager will appear. Choose the locked family tree and then click the Load Family Tree button. The 'Break the lock' dialogue will appear.


Fig. 5.8 Break the lock on the "Family Tree Example" database? - Dialog
  • Click the Break lock button that will be available. Only do this if you are sure no other copy of Gramps is using this Family Tree.


Repairing a damaged Family Tree

Fig. 5.9 Repairing a Family Tree

Should your Family Tree become damaged or corrupted in some way, Gramps Family Tree Manager will display a red Error icon in the Status column.

To have Gramps attempt to repair the damage, select the Family Tree and then click the Repair button.

This will attempt to rebuild your Family Tree from the backup files that are automatically created on exit.


Saving changes to your Family Tree

Gramps saves your changes as soon as you apply them. This means, for example, that any time you click OK when using Gramps, your changes are immediately recorded and saved. There is no separate "save" command.

You can undo changes you have made by selecting the menu Edit ->Undo. If you select this command repeatedly, your most recent changes will be undone one at a time. To roll back multiple commands at a time, you can use the menu Edit dialog.

If you want to return your Family Tree to the way it was when you opened it, select the menu Family Trees ->Abandon Changes and Quit. (This is just like quitting without saving in other programs.)

If you would like to save a copy of your Family Tree under a different name, you will need to export it and then import it into a new Family Tree. The Gramps XML database format is recommended for this purpose.

Importing data

Gramps-notes.png
Importing vs. opening

Please recognize that importing a Family Tree is different from opening a Family Tree. When you import, you are actually bringing data from another Family Tree into a Gramps Family Tree. When you open a file, you are editing your original file.

Importing allows you to transfer data from other genealogy programs into a Gramps Family Tree. Gramps can import data from the following formats:

Import Family Tree dialog

Gramps-notes.png
Note that you can only import data into an existing database

So if you are transferring all your data from another program it is recommended that you create a new empty Family Tree and then import the data into it


First create a new empty Family Tree. Then select the menu Family Trees ->Import or the keybinding CTRL+I to import data or restore a previously saved Gramps Family Tree (from an older version of Gramps or the current version) the Import Family Tree dialog will open, asking you to specify the file you wish to import.

If you attempt to import into an existing Family Tree the Undo history warning dialog will open giving you the opportunity to stop the import and create a new Family Tree, unless you are deliberately attempting to merge data.

Gnome-important.png
Data loss with some formats

It is important to note that there is no direct one-to-one correspondence between all the features of Gramps and those of GEDCOM or GeneWeb or Pro-Gen. Therefore, when importing from any of these formats data may be lost. Details of data that may be lost from GEDCOM is given below.

Gramps-notes.png
Reorder Events generated by other programs

Some programs from which you have imported data may not order the events as you expect. Gramps provides help for reordering events according to your preference. See the Sort Events tool.

GRAMPS V2.x database import

GRAMPS V2.x database (.grdb): Prior to Gramps Version 4.2, this native Gramps database format was a specific form of the Berkeley database (BSDDB) with a special structure of data tables. This format was binary and architecture-dependent. It was very quick and efficient, but not generally portable across computers with different binary architecture (e.g. i386 vs. alpha).

Import from the GRAMPS V2.x database format is only supported by Gramps version 3.0.x. Import of V2.x into Gramps V3.0.x will not loose any data.

Gnome-important.png
Import from the Gramps V2.x format is not supported by Gramps 4.2.

If you have an old V2.x database, then you must import it into Gramps V3.0.x, export it from there to Gramps XML (or Gramps XML Package), and then import it into Gramps 4.2.

Gramps XML and XML Package import

The Gramps XML and Gramps XML Package database are the native Gramps formats. There is no risk of information loss when importing (restore) from or exporting to these formats.

  • Gramps XML (.gramps): The Gramps XML file is the standard Gramps data-exchange and backups format, and was also the default working-database format for older (pre 2.x) versions of Gramps. Unlike the GRAMPS V2.x grdb format, it is architecture independent and human-readable. The database may also have references to non-local (external) media objects, therefore it is not guaranteed to be completely portable (for full portability including media objects in the Gramps XML package (.gpkg) should be used). The Gramps XML database is created by exporting (Menu Family Trees ->Export...) to that format.
  • Gramps XML package (.gpkg): The Gramps XML package is a compressed archive containing the Gramps XML file and all media objects (images, sound files, etc.) to which the database refers. Because it contains all the media objects, this format is completely portable. The Gramps XML package is created by exporting ( Menu Family Trees ->Export... ) data in that format.

If you import information from another Gramps database or Gramps XML database, you will see the progress of the operation in the progress bar of Gramps main window. When the import finishes, a feedback window shows the number of imported objects. If the imported data originates from the very family tree in which you import the data, the import feedback gives suggestions about what could be merged; the merge is not done automatically for you. If you want to merge basic genealogy data automatically, consider CSV Spreadsheet Export/Import.

Gramps CSV import

  • The Gramps CSV Spreadsheet format allows importing and exporting of a subset of your Gramps data in a simple spreadsheet format. See CSV Import and Export for more information.

GEDCOM import

When you import information from GEDCOM, Gramps main window will show you a progress bar. When the GEDCOM import finishes, the Import Statistics window and the GEDCOM import report: windows show any data that was not imported. The GEDCOM import report: details most of the GEDCOM lines that were either ignored or could not be understood (Most likely as they are not part of the GEDCOM 5.5.1 standard. See GEDCOM Extensions). The contents of the GEDCOM line (or lines where there are continuation lines) are also shown. In some cases, the lines may not be exactly what is contained in the input GEDCOM file, because the line is reconstructed following some processing.

Gramps uses a different 'data model' from GEDCOM and therefore some data in GEDCOM cannot be imported into Gramps (See Gramps and GEDCOM).

The main exceptions are:

  • Some GEDCOM attribute structures are treated as Gramps Attributes and therefore many of the GEDCOM Primitive Elements cannot be stored.
  • The DATA elements of a SOURCE_RECORD (indicating the events recorded and responsible agency) are ignored.
  • Any source citations on notes are ignored.
  • Many GEDCOM Primitive Elements do not have exactly corresponding data elements in Gramps, and they are therefore stored as Attributes or Data with appropriate names, normally the GEDCOM tag. This applies particularly to the header, submitter and submission GEDCOM records and particular fields like REFN, RFN, RIN and AFN.
Fig. 5.10 Import report:Example of top level indicating omitted data
Fig. 5.11 Import report:Example of a note indicating omitted data

Where data is stated to be 'ignored', its omission is reported in the feedback at the end of import, and it is included in a note attached to a relevant object.

Where data is stated to be 'silently ignored', it is (at present - this may be regarded as a lacuna), not reported and not included in a note.


Import Statistics dialog


GEDCOM import report dialog

Fig. 5.12 GEDCOM import report - example results.


GEDCOM import limitations

This section describes any GEDCOM data that cannot be directly represented in Gramps, and how it is handled. For additional information on the limits of GEDCOM imports (and exports), please read the section on Gramps and GEDCOM.

HEADer, SUBMitter and SUBmissioN

Gramps has no direct representation of this data, and hence all information there has to be stored in other objects. Depending on a General preferences setting, a 'default source' object may be created. If this is created, then much of the data is stored in that Source, or in Repositories attached to that source.

   HEADER:=
        n HEAD                                          {1:1}
          +1 SOUR <APPROVED_SYSTEM_ID>                  {1:1}  (Data item of the 'default source')
            +2 VERS <VERSION_NUMBER>                    {0:1}  (Data item of the 'default source')
            +2 NAME <NAME_OF_PRODUCT>                   {0:1}  (Data item of the 'default source')
            +2 CORP <NAME_OF_BUSINESS>                  {0:1}  (Repository of the 'default source')
              +3 <<ADDRESS_STRUCTURE>>                  {0:1}  (Repository of the 'default source')
            +2 DATA <NAME_OF_SOURCE_DATA>               {0:1}  (Data item of the 'default source')
              +3 DATE <PUBLICATION_DATE>                {0:1}  (Data item of the 'default source')
              +3 COPR <COPYRIGHT_SOURCE_DATA>           {0:1}  (Data item of the 'default source')
          +1 DEST <RECEIVING_SYSTEM_NAME>               {0:1*} (Data item of the 'default source')
          +1 DATE <TRANSMISSION_DATE>                   {0:1}  (Data item of the 'default source')
            +2 TIME <TIME_VALUE>                        {0:1}  (Data item of the 'default source')
          +1 SUBM @<XREF:SUBM>@                         {1:1}  (Data item of the 'default source')
                                                               (Also used to determine the SUBMITTER_RECORD)
                                                               (that should be stored as the database owner)
          +1 SUBN @<XREF:SUBN>@                         {0:1}  (ignored)
          +1 FILE <FILE_NAME>                           {0:1}  (Data item of the 'default source')
          +1 COPR <COPYRIGHT_GEDCOM_FILE>               {0:1}  (stored as the Publication information of the 'default source')
          +1 GEDC                                       {1:1}
            +2 VERS <VERSION_NUMBER>                    {1:1}  (Data item of the 'default source')
            +2 FORM <GEDCOM_FORM>                       {1:1}  (Data item of the 'default source')
          +1 CHAR <CHARACTER_SET>                       {1:1}  (Data item of the 'default source')
            +2 VERS <VERSION_NUMBER>                    {0:1}  (Data item of the 'default source')
          +1 LANG <LANGUAGE_OF_TEXT>                    {0:1}  (Data item of the 'default source')
          +1 PLAC                                       {0:1}
            +2 FORM <PLACE_HIERARCHY>                   {1:1}  (see below)
          +1 NOTE <GEDCOM_CONTENT_DESCRIPTION>          {0:1}  (note attached to the 'default source')
            +2 [CONT|CONC] <GEDCOM_CONTENT_DESCRIPTION> {0:M}
            
   * NOTE: Submissions to the Family History Department for Ancestral
     File submission or for clearing temple ordinances must use a
     DESTination of ANSTFILE or TempleReady.

The PLAC FORM is stored internally and used to govern the interpretation of places (in accordance with the GEDCOM specification).

The SUBMISSION_RECORD (there should be only one, but this is not checked) is stored as a Data item of the 'default source'

    SUBMISSION_RECORD:=
        n @<XREF:SUBN>@ SUBN                            {1:1]
          +1 SUBM @<XREF:SUBM>@                         {0:1}
          +1 FAMF <NAME_OF_FAMILY_FILE>                 {0:1}
          +1 TEMP <TEMPLE_CODE>                         {0:1}
          +1 ANCE <GENERATIONS_OF_ANCESTORS>            {0:1}
          +1 DESC <GENERATIONS_OF_DESCENDANTS>          {0:1}
          +1 ORDI <ORDINANCE_PROCESS_FLAG>              {0:1}
          +1 RIN <AUTOMATED_RECORD_ID>                  {0:1}

SUBMITTER_RECORDs (there may be more than one) are stored as Repository records attached to the 'default source' except as indicated in bold below. The SUBMITTER_RECORD that corresponds with the SUBM record in the HEADER is used to set the database owner q.v.

   SUBMITTER_RECORD:=
        n @<XREF:SUBM>@   SUBM                          {1:1}
          +1 NAME <SUBMITTER_NAME>                      {1:1}
          +1 <<ADDRESS_STRUCTURE>>                      {0:1}
          +1 <<MULTIMEDIA_LINK>>                        {0:M}
          +1 LANG <LANGUAGE_PREFERENCE>                 {0:3}
          +1 RFN <SUBMITTER_REGISTERED_RFN>             {0:1}
          +1 RIN <AUTOMATED_RECORD_ID>                  {0:1}
          +1 <<CHANGE_DATE>>                            {0:1}
  • Mutimedia link is ignored
  • LANG is ignored
  • RFN and RIN are ignored
INDIvidual

The INDIVIDUAL_RECORD is stored as a Gramps Person record, except as indicated in bold below.

   INDIVIDUAL_RECORD: =
        n @<XREF:INDI>@  INDI                           {1:1}
          +1 RESN <RESTRICTION_NOTICE>                  {0:1}
          +1 <<PERSONAL_NAME_STRUCTURE>>                {0:M}
          +1 SEX <SEX_VALUE>                            {0:1}
          +1 <<INDIVIDUAL_EVENT_STRUCTURE>>             {0:M}
          +1 <<INDIVIDUAL_ATTRIBUTE_STRUCTURE>>         {0:M}
          +1 <<LDS_INDIVIDUAL_ORDINANCE>>               {0:M}
          +1 <<CHILD_TO_FAMILY_LINK>>                   {0:M}
          +1 <<SPOUSE_TO_FAMILY_LINK>>                  {0:M}
          +1 SUBM @<XREF:SUBM>@                         {0:M}
          +1 <<ASSOCIATION_STRUCTURE>>                  {0:M}
          +1 ALIA @<XREF:INDI>@                         {0:M}
          +1 ANCI @<XREF:SUBM>@                         {0:M}
          +1 DESI @<XREF:SUBM>@                         {0:M}
          +1 <<SOURCE_CITATION>>                        {0:M}
          +1 <<MULTIMEDIA_LINK>>                        {0:M}
          +1 <<NOTE_STRUCTURE>>                         {0:M}
          +1 RFN <PERMANENT_RECORD_FILE_NUMBER>         {0:1}
          +1 AFN <ANCESTRAL_FILE_NUMBER>                {0:1}
          +1 REFN <USER_REFERENCE_NUMBER>               {0:M}
            +2 TYPE <USER_REFERENCE_TYPE>               {0:1}
          +1 RIN <AUTOMATED_RECORD_ID>                  {0:1}
          +1 <<CHANGE_DATE>>                            {0:1}
   
  • Link to submitter, ancestor interest and descendent interest indicators are silently ignored.
  • The alias indicator ("An indicator to link different record descriptions of a person who may be the same person") is stored as an Association called 'Alias'.
  • The REFN and REFN:TYPE are stored as Attributes of the Person, but if there is more than one REFN, it may not be clear which TYPE is associated with which REFN.

Handling of the INDIVIDUAL_ATTRIBUTE_STRUCTURE is rather complicated. The following tags:

  • EDUC (Scholastic achievement),
  • NMR (Count of marriages),
  • OCCU (Occupation),
  • PROP (Possessions),
  • RELI (Religious affiliation),
  • RESI and
  • TITL (Nobility title)

are all treated as Gramps Events and the associated information is stored in the event structure. The details following the main tag (shown in brackets in the list above) are stored as the Description of the Event. The <EVENT_DESCRIPTOR> following the TYPE tag will overwrite the Description if the <EVENT_DESCRIPTOR> is not the attribute name.

The following tags:

  • CAST (Caste name),
  • DSCR (Physical description),
  • INDO (National ID Number),
  • NATI (National or tribal origin),
  • NCHI (Count of Children) and
  • SSN (Social Security Number)

are all treated as Gramps Attributess and most of the fields except the details following the main tag (shown in brackets in the list above), the source citation and the note structure are ignored, as indicated in bold below.

   INDIVIDUAL_ATTRIBUTE_STRUCTURE: =
        n  CAST <CASTE_NAME>                            {1:1}
          +1 <<EVENT_DETAIL>>                           {0:1}
             etc.
   
   EVENT_DETAIL: =
        n  TYPE <EVENT_DESCRIPTOR>                      {0:1}
        n  DATE <DATE_VALUE>                            {0:1}
        n  <<PLACE_STRUCTURE>>                          {0:1}
        n  <<ADDRESS_STRUCTURE>>                        {0:1}
        n  AGE <AGE_AT_EVENT>                           {0:1}
        n  AGNC <RESPONSIBLE_AGENCY>                    {0:1}
        n  CAUS <CAUSE_OF_EVENT>                        {0:1}
        n  <<SOURCE_CITATION>>                          {0:M}
          +1 <<NOTE_STRUCTURE>>                         {0:M}
          +1 <<MULTIMEDIA_LINK>>                        {0:M}
        n  <<MULTIMEDIA_LINK>>                          {0:M}
        n  <<NOTE_STRUCTURE>>                           {0:M}
        
        
  • Individual attribute structure, type, date, place structure, address structure, age, agency, cause and multimedia link are all ignored.
FAM_RECORD

The FAM_RECORD is stored as a Gramps Family record.

   FAM_RECORD:=
        n @<XREF:FAM>@   FAM                            {1:1}
          +1 <<FAMILY_EVENT_STRUCTURE>>                 {0:M}
          +1 HUSB @<XREF:INDI>@                         {0:1}
          +1 WIFE @<XREF:INDI>@                         {0:1}
          +1 CHIL @<XREF:INDI>@                         {0:M}
          +1 NCHI <COUNT_OF_CHILDREN>                   {0:1}
          +1 SUBM @<XREF:SUBM>@                         {0:M}
          +1 <<LDS_SPOUSE_SEALING>>                     {0:M}
          +1 <<SOURCE_CITATION>>                        {0:M}
          +1 <<MULTIMEDIA_LINK>>                        {0:M}
          +1 <<NOTE_STRUCTURE>>                         {0:M}
          +1 REFN <USER_REFERENCE_NUMBER>               {0:M}
            +2 TYPE <USER_REFERENCE_TYPE>               {0:1}
          +1 RIN <AUTOMATED_RECORD_ID>                  {0:1}
          +1 <<CHANGE_DATE>>                            {0:1}
  • The link to submitter is silently ignored.
  • The REFN and REFN:TYPE are stored as Attributes of the Family, but if there is more than one REFN, it may not be clear which TYPE is associated with which REFN.
SOURCE_RECORD

The SOURCE_RECORD is stored as a Gramps Source record, except as indicated in bold below.

   SOURCE_RECORD:=
        n @<XREF:SOUR>@ SOUR                            {1:1}
          +1 DATA                                       {0:1}
            +2 EVEN <EVENTS_RECORDED>                   {0:M}
              +3 DATE <DATE_PERIOD>                     {0:1}
              +3 PLAC <SOURCE_JURISDICTION_PLACE>       {0:1}
            +2 AGNC <RESPONSIBLE_AGENCY>                {0:1}
            +2 <<NOTE_STRUCTURE>>                       {0:M}
          +1 AUTH <SOURCE_ORIGINATOR>                   {0:1}
            +2 [CONT|CONC] <SOURCE_ORIGINATOR>          {0:M}
          +1 TITL <SOURCE_DESCRIPTIVE_TITLE>            {0:1}
            +2 [CONT|CONC] <SOURCE_DESCRIPTIVE_TITLE>   {0:M}
          +1 ABBR <SOURCE_FILED_BY_ENTRY>               {0:1}
          +1 PUBL <SOURCE_PUBLICATION_FACTS>            {0:1}
            +2 [CONT|CONC] <SOURCE_PUBLICATION_FACTS>   {0:M}
          +1 TEXT <TEXT_FROM_SOURCE>                    {0:1}
            +2 [CONT|CONC] <TEXT_FROM_SOURCE>           {0:M}
          +1 <<SOURCE_REPOSITORY_CITATION>>             {0:1}
          +1 <<MULTIMEDIA_LINK>>                        {0:M}
          +1 <<NOTE_STRUCTURE>>                         {0:M}
          +1 REFN <USER_REFERENCE_NUMBER>               {0:M}
            +2 TYPE <USER_REFERENCE_TYPE>               {0:1}
          +1 RIN <AUTOMATED_RECORD_ID>                  {0:1}
          +1 <<CHANGE_DATE>>                            {0:1}
  • DATA and its subsidiary records are ignored
REPOSITORY_RECORD

The REPOSITORY_RECORD is stored as a Gramps Repository record, except as indicated in bold below.

   REPOSITORY_RECORD: =
        n @<XREF:REPO>@ REPO                            {1:1}
          +1 NAME <NAME_OF_REPOSITORY>                  {0:1}
          +1 <<ADDRESS_STRUCTURE>>                      {0:1}
          +1 <<NOTE_STRUCTURE>>                         {0:M}
          +1 REFN <USER_REFERENCE_NUMBER>               {0:M}
            +2 TYPE <USER_REFERENCE_TYPE>               {0:1}
          +1 RIN <AUTOMATED_RECORD_ID>                  {0:1}
          +1 <<CHANGE_DATE>>                            {0:1}
  • REFN, REFN:TYPE and RIN are ignored
MULTIMEDIA_RECORD

The MULTIMEDIA_RECORD is stored as a Gramps Media record, except as indicated in bold below.

   MULTIMEDIA_RECORD:=
        n @<XREF:OBJE>@ OBJE                            {1:1}
          +1 FORM <MULTIMEDIA_FORMAT>                   {1:1}
          +1 TITL <DESCRIPTIVE_TITLE>                   {0:1}
          +1 <<NOTE_STRUCTURE>>                         {0:M}
          +1 <<SOURCE_CITATION>>                        {0:M}
          +1 BLOB                                       {1:1}
            +2 CONT <ENCODED_MULTIMEDIA_LINE>           {1:M}
          +1 OBJE @<XREF:OBJE>@     /* chain to continued object */  {0:1}
          +1 REFN <USER_REFERENCE_NUMBER>               {0:M}
            +2 TYPE <USER_REFERENCE_TYPE>               {0:1}
          +1 RIN <AUTOMATED_RECORD_ID>                  {0:1}
  • It is expected that there will be a 'FILE' tag to indicate the file holding the multimedia object. This usage is taken from GEDCOM 5.5.1, but the ability in GEDCOM 5.5.1 to have more than one <MUTIMEDIA_FILE_REFN> and having the FORM, TYPE and TITL subsidiary to the FILE gedcom_line is not supported (a later FILE may overwrite an earlier one - there is no error checking).
  • BLOB is ignored
  • REFN, REFN:TYPE and RIN are ignored
NOTE_RECORD

The NOTE_RECORD is stored as a Gramps Note record, except as indicated in bold below.

   NOTE_RECORD:=
        n @<XREF:NOTE>@ NOTE <SUBMITTER_TEXT>           {1:1}
          +1 [ CONC | CONT] <SUBMITTER_TEXT>            {0:M}
          +1 <<SOURCE_CITATION>>                        {0:M}
          +1 REFN <USER_REFERENCE_NUMBER>               {0:M}
            +2 TYPE <USER_REFERENCE_TYPE>               {0:1}
          +1 RIN <AUTOMATED_RECORD_ID>                  {0:1}
          +1 <<CHANGE_DATE>>                            {0:1}
  • source citation ignored
  • REFN, REFN:TYPE and RIN are ignored

Exporting data

Gramps-notes.png
Export is saving a copy

When you export, you are saving a copy of the currently opened database. Exporting creates another file with a copy of your data. Note that the database that remains opened in your Gramps window is NOT the file saved by your export. Additional editing of the currently opened database will not alter the copy produced by the export.

Exporting allows you to share any portion of your Gramps database with other researchers as well as to enable you to transfer your data to another computer. Gramps can export data to the following formats: Gramps XML, GEDCOM, Gramps XML Package, Web Family Tree, GeneWeb, and CSV Spreadsheet formats.

To export data, choose Menu Family Trees ->Export... or the keybinding CTRL+E. This will bring up the Export Assistant dialog.

Export Assistant dialog

Fig. 5.13 Export Assistant: Start screen

The Export Assistant pages will guide you through the format selection (see Fig 5.14), file selection, and format specific export options. After a final confirmation page, the export will be performed according to the choices you have made. At any time, you can click the Back button and revise any selection, and then go forward to redo the export.


Fig. 5.14 Export Assistant: Choose the output format screen


Filters and privacy

Fig. 5.15 Export assistant: Filters and privacy export options

Gramps allows you to export a database into common file formats.

It provides options that allow you to fine tune your export.

  • Filters on People and Notes: Filters allow you to export a limited amount of data, based on the criteria you select.
  • Do not include records marked private: Check this box to prevent private records from being included in the exported file.
  • Restrict data on living people: Check this box to limit the information exported for living people. This means that all information concerning their birth, death, addresses, significant events, etc., will be omitted in the exported file. If you choose this option, you will be given additional options to limit further the data on living people. For example, you can choose to substitute the word Living for the first name (see your settings); you can exclude notes; and you can exclude sources for living people.
  • Do not include not related records: Check this box to prevent not related records from being included in the exported file.

Sometimes, it is not always obvious from the data if someone is actually alive. Gramps uses an advanced algorithm to try to determine if a person could still be alive. Remember, Gramps is making its best guess, and it may not always be able to guess correctly all the time. Please double check your data.

Export into Gramps formats

Gnome-important.png
Privacy Filters

It is important to verify your privacy options on Exporter. Do not enable filters or privacy options for Gramps XML backups.

  • Gramps XML database export (.gramps): This format is the standard format for data-exchange and backups (see the related .gpkg format below for full portability including media objects). Exporting into Gramps XML format will produce a portable database. As XML is a text-based human-readable format, you may also use it to take a look at your data. Gramps guarantees you can open XML output of older versions of Gramps in newer version of Gramps (not the other way around though!).
  • Gramps package export (.gpkg): Exporting to the Gramps package format will create a compressed file that contains the Gramps XML database and copies of all associated media files. This is useful if you want to move your database to another computer or to share it with someone.
  • Export to CD: Exporting to CD will prepare your database and copies of all media object files for recording onto a CD. To actually burn the CD, you will need to go to the GNOME burn:/// location, which can be accessed by navigating through Nautilus: After exporting to CD, select Go ->CD Creator in the Nautilus menu. Your database directory will show up. To burn it to the CD, click the CD icon on the Nautilus toolbar, or select File ->Write to CD in the Nautilus menu.

If a media file is not found during export, you will see the same Missing Media dialog you encounter with GEDCOM export.

Exporting into the GEDCOM format

Fig. 5.16 Export assistant: GEDCOM Export options

Gramps allows you to export a database into the common GEDCOM format. See Gramps and GEDCOM for a specification of data which is not exported when exporting to GEDCOM (use Gramps XML for a full export). Gramps provides options that allow you to fine tune your export.

  • Filters on People and Notes: Filters allow you to export a limited amount of data, based on the criteria you select.
  • Do not include records marked private: Check this box to prevent private records from being included in the exported file.
  • Restrict data on living people: Check this box to limit the information exported for living people. This means that all information concerning their birth, death, addresses, significant events, etc., will be omitted in the exported file. If you choose this option, you will be given additional options to limit further the data on living people. For example, you can choose to substitute the word Living for the first name (see your settings); you can exclude notes; and you can exclude sources for living people.
  • Do not include not related records: Check this box to prevent not related records from being included in the exported file.


Export into other formats

GeneWeb

  • GeneWeb: Exporting to GeneWeb will save a copy of your data into a popular web genealogy format. To find out more about GeneWeb and its format, visit http://www.geneweb.org

Gramps CSV Spreadsheet format

  • Gramps CSV Spreadsheet format: Allows exporting (and importing) a subset of your Gramps data in a simple spreadsheet format. See CSV Import and Export for more information. Also, see Export Display .

Web Family Tree

  • Web Family Tree: Exporting to Web Family Tree will create a text file that can be used by the Web Family Tree program. Export options include filter selection and the ability to limit data on living people to that of their family ties. To find out more about Web Family Tree and its format, visit http://www.simonward.com/cgi-bin/page.pl?family/tree

vCard

  • vCard: Exporting to vCard will save information in a format used in many addressbook applications, sometimes called PIM for Personal Information Manager. For more information on the format see: https://en.wikipedia.org/wiki/VCard

vCalendar


Moving a Gramps 2.2 databases to Gramps 3.x

Gnome-important.png
Import from the Gramps V2.x format is not supported by Gramps 4.2.

If you have an old V2.x database, then you must import it into Gramps V3.0.x, export it from there to Gramps XML (or Gramps XML Package), and then import it into Gramps 4.2.

To move your Gramps data from version 2.x to version 4.2.x you must import the v2.x database into an earlier Gramps v3.0.x program and then either save the database and import it into Gramps 4.2.x, or export the database in XML format from the earlier Gramps version and import it into Gramps 4.2.x.

Please refer to the User Manual for earlier versions of Gramps for instructions on the import of v2.x databases into Gramps v3.x.

Previous Index Next


Gnome-important.png Special copyright notice: All edits to this page need to be under two different copyright licenses:

These licenses allow the Gramps project to maximally use this wiki manual as free content in future Gramps versions. If you do not agree with this dual license, then do not edit this page. You may only link to other pages within the wiki which fall only under the GFDL license via external links (using the syntax: [https://www.gramps-project.org/...]), not via internal links.
Also, only use the known Typographical conventions