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

From Gramps
Jump to: navigation, search
(Archiving a Family Tree -- Easy backup)
(warning : privacy filters)
 
(39 intermediate revisions by 7 users not shown)
Line 4: Line 4:
  
  
{{languages}}
+
{{man index|Gramps 3.0 Wiki Manual - Main Window|Gramps 3.0 Wiki Manual - Entering and Editing Data: Brief|3.0}}
 +
 
 +
{{languages|Gramps_3.0_Wiki_Manual_-_Manage_Family_Trees}}
  
  
 
== Starting a New Family Tree ==
 
== Starting a New Family Tree ==
 +
[[Image:Dbmanager01.png|right|thumb|250px|Fig. 3.1. Starting Family Trees ]]
 +
 +
  
 
To start a new Family Tree, choose ''' Family Trees ->Manage Family Trees ''' or select the {{man button|Family Trees}} button from the toolbar. This will open the Family Tree Manager.
 
To start a new Family Tree, choose ''' Family Trees ->Manage Family Trees ''' or select the {{man button|Family Trees}} button from the toolbar. This will open the Family Tree Manager.
  
[[Image:Dbmanager01.png]]
 
  
Select the {{man button|New}} button and GRAMPS will add a new Family Tree entry to the list of Family Trees. To change its name from the default ''Family Tree 1'', click on the name and type in a new name.
 
  
Now select {{man button|Load Family Tree}} to open the new, empty Family Tree.
 
  
  
 +
Select the {{man button|New}} button and GRAMPS will add a new Family Tree entry to the list of Family Trees. To change its name from the default ''Family Tree 1'', click on the name and type in a new name.
 +
 +
Now select {{man button|Load Family Tree}} to open the new, empty Family Tree.
  
 
== Opening a Family Tree ==
 
== Opening a Family Tree ==
  
To open a Family Tree, either choose ''' Family Trees ->Manage Family Trees ''' or click the {{man button|Family Trees}} button on the Toolbar. The {{man label|Family Tree Manager}} will appear and you'll see a list of all the Family Trees known to GRAMPS. An icon will display under {{man label|Status}} beside any Family Tree that is currently open. Select the tree you want to open, and open it by double-click or with the {{man button|Load Family Tree}} button.
+
To open a Family Tree, either choose ''' Family Trees ->Manage Family Trees ''' or click the {{man button|Family Trees}} button on the Toolbar. The {{man label|Family Tree Manager}} will appear and you'll see a list of all the Family Trees known to GRAMPS. An icon will display in the {{man label|Status}} column beside any Family Tree that is currently open. Select the tree you want to open, and open it by selecting the {{man button|Load Family Tree}} button. Alternatively you can double-click on the desired Tree.
  
 
To open a recently accessed Family Tree, choose either ''' Family Trees ->Open Recent ''' or the down arrow next to the {{man button|Family Trees}} button and select the Family Tree from the list.
 
To open a recently accessed Family Tree, choose either ''' Family Trees ->Open Recent ''' or the down arrow next to the {{man button|Family Trees}} button and select the Family Tree from the list.
Line 27: Line 32:
 
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 Tree. To indicate this mode, the title of the main window will be appended with '''(Read Only)''' text.
 
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 Tree. To indicate this mode, the title of the main window will be appended with '''(Read Only)''' text.
  
If a family tree contains archives (snapshots of previous version), you will be able to open them too by the same procedure.
+
== 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. '''TODO link to page explaining how.''' 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 best to always create a new family tree by creating a new GRAMPS family tree (database) and importing your XML/GEDCOM data into it.
+
GRAMPS allows you to open certain databases that have not been saved in GRAMPS' own file format from the command line. '''TODO link to page explaining how.''' 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.
  
 
{{man note| 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.}}
 
{{man note| 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.}}
Line 38: Line 43:
 
Select the family tree you want removed, and click the {{man button|Delete}} button.  
 
Select the family tree you want removed, and click the {{man button|Delete}} button.  
  
This wil '''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.
+
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.
  
== Rename a Family Tree ==
+
== Renaming a Family Tree ==
You can rename a Family Tree (or an archive of it) by selecting the tree you want to rename and click {{man button|Rename}}. You can also click on the name in the list of trees.  
+
You can rename a Family Tree (or an archive of it) by selecting the tree you want to rename and clicking {{man button|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
+
In either case, you just type in the new name to have it take effect.
  
== Unlock a Family Tree ==
+
== Backing up a Family Tree ==
 +
The safest way to backup your GRAMPS Family Tree is to export to '''GRAMPS XML''' format (or '''GRAMPS Package''' to include items from your Gallery) and copy the resultant file to a safe place, preferably in a different building.
 +
 
 +
You can use the Archive feature to store snapshots of your 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 ==
 +
You can easily archive and timestamp family trees with GRAMPS built-in use of [http://www.gnu.org/software/rcs/ GNU Revision Control System] or ''RCS''. For this to be possible this utility must be installed on your computer.
 +
 
 +
To make an archive, first make sure the tree you wish to archive is open. Then select the open family tree, and click the {{man button|Archive}} button. The archive will be listed under the tree from which it was created. Archives can be deleted and renamed.
 +
 
 +
== Restoring a Family Tree Archive ==
 +
[[Image:Dbmanager04.png|thumb|left|200px|Fig. 3.2 Selecting a version to restore]]
 +
Simply highlight the archive you want to restore, and select the {{man button|Restore}} button.
 +
[[Image:Dbmanager05.png|thumb|right|200px|Fig. 3.3 Restored version]]
 +
 
 +
 
 +
 
 +
 
 +
 
 +
 
 +
GRAMPS will transfer the archive into a new Family Tree. The Family Tree name is based on the original name and the archive name.
 +
 
 +
== Unlocking a Family Tree ==
 
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.  
 
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.
 
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, select the locked family tree, and click the {{man button|Unlock}} button that will be available. Only do this if you are sure no other copy of GRAMPS is using this family tree
+
In the unlikely event of a crash of GRAMPS, the family tree will be left in a locked state. To unlock the tree, select the locked family tree, and click the {{man button|Unlock}} 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 ==
 +
[[Image:Dbmanager07.png|thumb|right|250px|Fig. 3.4 Repairing a Family Tree]]
 +
 
 +
 
 +
 
 +
 
  
== Archiving a Family Tree -- Easy backup ==
 
You can easily backup and timestamp family trees with GRAMPS built-in use of [http://www.gnu.org/software/rcs/ GNU Revision Control System] or ''RCS''. For this to be possible this utility must be installed on your computer.
 
  
To make an archive or backup, select the family tree you want to backup, and click the {{man button|Archive}} button. The archive will be displayed under the tree from which it was created.
 
  
[[Image:Dbmanager04.png|Selecting a version to restore]]
+
Should your Family Tree become damaged or corrupted in some way, GRAMPS' Family Tree Manager will display a red Error icon in the {{man label|Status}} column.
  
== Saving Changes to Your Database ==
+
To tell GRAMPS to attempt to repair the damage, select the Tree and then click the {{man button|Repair}} button.
  
GRAMPS saves your changes as soon as you apply them. This means, for example, that any time you click {{man button|OK}} when using GRAMPS, your changes are immediately recorded and saved. There is no separate "save" command (although there is a "save as" command that we'll discuss later.)
+
This will attempt to rebuild your tree from the backup files that are automatically created on exit.
  
You can undo changes you've made by selecting ''' 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 using the {{man label|Undo History}} dialog available from the {{man label|Edit}} menu.
+
== Saving Changes to Your Family Tree ==
  
If you want to return your database to the way it was when you opened it, select ''' File ->Abandon changes and quit ''' . (This is just like quitting without saving in other programs.)
+
GRAMPS saves your changes as soon as you apply them. This means, for example, that any time you click {{man button|OK}} when using GRAMPS, your changes are immediately recorded and saved. There is no separate "save" command.
  
If you would like to save your database under a different name, you can do so by choosing ''' File ->Save as... ''' and specifying the name (and, optionally, the format) of your new database. Note that Save as will allow you to continue editing the newly saved database. If this is not what you want to do, you may wish to use the Export command instead.
+
You can undo changes you've made by selecting ''' 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 using the {{man label|Undo History}} dialog available from the {{man label|Edit}} menu.
  
 +
If you want to return your Family Tree to the way it was when you opened it, select ''' 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 ==
 
== Importing Data ==
Line 74: Line 110:
 
Importing allows you to bring data from other genealogy programs into a GRAMPS database. Currently, GRAMPS can import data from the following formats:
 
Importing allows you to bring data from other genealogy programs into a GRAMPS database. Currently, GRAMPS can import data from the following formats:
  
Another GRAMPS database (having the ''grdb'' file extension),
+
GRAMPS V2.x database (.grdb file extension)
  
GEDCOM
+
GEDCOM (.ged file extension)
  
GRAMPS XML
+
GRAMPS XML (.gramps file extension)
  
GRAMPS package
+
GRAMPS package (.gpkg file extension)
  
GeneWeb
+
GeneWeb (.gw file extension)
 +
 
 +
GRAMPS CSV Spreadsheet - comma separated values (.csv file extension)
  
 
{{man note| Importing vs. opening |Please recognize that importing a database is different from opening a database. When you import, you are actually bringing data from one database into a GRAMPS database. When you open a file, you are editing your original file.}}
 
{{man note| Importing vs. opening |Please recognize that importing a database is different from opening a database. When you import, you are actually bringing data from one database into a GRAMPS database. When you open a file, you are editing your original file.}}
  
To import data, select ''' File ->Import ''' . The '''Import database''' dialog will open, asking you to specify the file you wish to import.
+
To import data, select ''' Family Trees ->Import ''' . The '''Import database''' dialog will open, asking you to specify the file you wish to import.
 +
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 database and then import the data into it.
  
 
{{man warn| Data loss with some formats |It is important to note that the importing process is not perfect for GEDCOM and GeneWeb databases. There is a chance that some of the data in these databases will not be imported into GRAMPS.}}
 
{{man warn| Data loss with some formats |It is important to note that the importing process is not perfect for GEDCOM and GeneWeb databases. There is a chance that some of the data in these databases will not be imported into GRAMPS.}}
  
The GRAMPS database (grdb), GRAMPS XML, and GRAMPS package are all native GRAMPS formats. There is no risk of information loss when import or exporting to these formats.
+
The GRAMPS V2.x database, GRAMPS XML, and GRAMPS package are all native GRAMPS formats. There is no risk of information loss when importing from or exporting to these formats.
  
*GRAMPS database (grdb): The native GRAMPS database format is a specific form of Berkeley database (BSDDB) with a special structure of data tables. This format is binary and architecture-dependent. It is very quick and efficient, but not generally portable across computers with different binary architecture (e.g. i386 vs. alpha).
+
*GRAMPS V2.x database (grdb): Prior to Version 3.0, this native GRAMPS database format was a specific form of 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).  
  
*GRAMPS XML: The GRAMPS XML file was the default format for older versions of GRAMPS. Unlike the 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. The GRAMPS XML database is created by saving ( ''' File ->Save As... ''' ) or exporting ( ''' File ->Export... ''' ) data in that format
+
*GRAMPS XML: The GRAMPS XML file was the default format for older (pre 2.x) versions of GRAMPS. Unlike the 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. The GRAMPS XML database is created by exporting ( ''' Family Trees ->Export... ''' ) to that format.
  
*GRAMPS package: The GRAMPS 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 package is created by exporting ( ''' File ->Export... ''' ) data in that format.
+
*GRAMPS package: The GRAMPS 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 package is created by exporting ( ''' 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.
 
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.
 +
 +
The GRAMPS CSV Spreadsheet format allows importing and exporting of a subset of your GRAMPS data in a simple spreadsheet format. See [[Gramps 3.0 Wiki Manual - Manage Family Trees: CSV Import and Export|CSV Import and Export]] for more information.
  
 
== Exporting Data ==
 
== Exporting Data ==
 +
[[Image:Export-druid.png|right|thumb|200px|Fig.3.4 Export assistant: format selection]]
 +
'''Wait to update manual:''' The exporter is undergoing a major rewrite.
  
'''Wait to update manual:''' The exporter is undergoing a major rewrite.
 
  
[[Image:Export-druid.png|right|thumb|150px|Fig.3.xx Export assistant: format selection]]
 
  
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. Currently, GRAMPS can export data to the following formats: GRAMPS database (grdb), GRAMPS XML, GEDCOM, GRAMPS package, Web Family Tree, and GeneWeb.
+
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. Currently, GRAMPS can export data to the following formats: GRAMPS XML, GEDCOM, GRAMPS package, Web Family Tree, GeneWeb, and GRAMPS CSV Spreadsheet formats.
  
 
{{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.}}
  
To export data, choose ''' File ->Export ''' . This will bring up the '''Export''' assistant. Its pages will guide you through the format selection (see ''export-druid-fig'' ), file selection, and format specific export options (see ''gedcom-export-fig'' ). After a final confirmation page, the export will be performed according to the choices you have made. At any time, you can click the {{man button|Back}} button and revise any selection, and then go forward to redo the export.
+
To export data, choose ''' Family Trees ->Export ''' . This will bring up the '''Export''' assistant. Its pages will guide you through the format selection (see ''Fig. 3.4'' ), 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 {{man button|Back}} button and revise any selection, and then go forward to redo the export.
 +
 
 +
=== Export into GRAMPS formats ===
 +
 
 +
{{man warn|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. This format is compatible with the previous versions of GRAMPS.
  
=== Exporting into the GEDCOM format ===
+
*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.
  
GRAMPS allows you to export a database into the common GEDCOM format. It provides options that allow you to fine tune your export (see [image:Gedcom-export.png]gedcom-export-fig'' ).
+
If a media file is not found during export, you will see the same {{man label|Missing Media}} dialog you encounter with GEDCOM export.
  
*Encoding: Since different languages use different characters, it is important to tell a GEDCOM file what character set is used. The two formats traditionally accepted are ASCII and ANSEL. Since all ASCII characters are valid ANSEL characters, GRAMPS does not provide an option for ASCII.
+
=== Exporting into the GEDCOM format ===
 +
[[Image:Gedcom-export.png|right|thumb|200px|Fig.3.5.Export assistant: GEDCOM options]]
  
Because ANSEL is not commonly used, some genealogy programs will accept ANSI (more commonly known as ISO-8859-1) and Unicode character sets. Only select ANSI or Unicode if you know any program that attempts to read the GEDCOM file will understand these character sets.
+
GRAMPS allows you to export a database into the common GEDCOM format. It provides options that allow you to fine tune your export (see [[Media:Gedcom-export.png|gedcom-export-fig]] ).
  
 
*Filter: The filter allows you to export a limited amount of data, based on the criteria you select.
 
*Filter: The filter allows you to export a limited amount of data, based on the criteria you select.
  
 
*Target: While GEDCOM is a standard, not every program implements it in the same way. This can lead to data loss. GRAMPS can reduce the data loss in some cases. You can tell GRAMPS what program is the target, and GRAMPS will customize the exported file for that program. If your program is not listed, choose the "GEDCOM 5.5 Standard".
 
*Target: While GEDCOM is a standard, not every program implements it in the same way. This can lead to data loss. GRAMPS can reduce the data loss in some cases. You can tell GRAMPS what program is the target, and GRAMPS will customize the exported file for that program. If your program is not listed, choose the "GEDCOM 5.5 Standard".
 
*Copyright: Allows you to select a statement to describe your Copyright claim.
 
  
 
*Do not include records marked private: Check this box to prevent private records from being included in the exported file.
 
*Do not include records marked private: Check this box to prevent private records from being included in the exported file.
Line 136: Line 185:
 
This option allows specify where your image files are located. This is useful when you are transferring your GEDCOM file from one computer to another. It tells the program that is importing the data where your images are.
 
This option allows specify where your image files are located. This is useful when you are transferring your GEDCOM file from one computer to another. It tells the program that is importing the data where your images are.
  
[[Image:Gedcom-export.png|right|thumb|150px|Fig.3.xx.Export assistant: GEDCOM options]]
+
=== Export into other formats ===
  
=== Export into GRAMPS 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.
  
*GRAMPS database (grdb) export: Exporting to the GRAMPS native format will simply make a copy of your data under another name. Exporting to this format can also be useful if you have directly opened an XML or GEDCOM file and would like to save it as the grdb file.
+
*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/.
  
*GRAMPS XML database export: Exporting into GRAMPS XML format will produce a database compatible with the previous versions of GRAMPS. As XML is a text-based human-readable format, you may also use it to take a look at your data.
+
*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.
 
 
*GRAMPS package export: Exporting to the GRAMPS package format will create a compressed file that contains the 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.
+
*GRAMPS CSV Spreadsheet format: Allows exporting (and importing) a subset of your GRAMPS data in a simple spreadsheet format. See [[Gramps 3.0 Wiki Manual - Manage Family Trees: CSV Import and Export|CSV Import and Export]] for more information. Also, see [[Gramps_3.0_Wiki_Manual_-_Settings#Export_the_screen|Export Display]] .
  
=== Export into other formats ===
+
== Moving 2.2 databases to Gramps 3 ==
  
*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.
+
There are two ways of moving your Gramps data from version 2.2 to version 3; either directly importing your version 2.2 grdb file or by exporting to XML format first. Because of complexity in the way that version 2.2 stores data, exporting to XML is usually the most convenient and problem free way of moving your data to version 3.
  
*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/.
+
*Import 2.2 grdb file: In a Gramps 2.2 database, your data is stored in a grdb file along with one or more log files that are kept in directories found in the .gramps/env directory. To import your 2.2 data directly into Gramps 3, create a new database and select the option to import a Gramps 2.2 database. You need to make sure that you are running Gramps 3 from the same user you used to run Gramps 2.2 so that it has access to the same .gramps/env directory containing the log files that supplement your database. If you are running Gramps 3 from a different user or on another machine you need to make provisions to make the same .gramps/env directory and log files available. If you get an error saying "/tmp/tmpDkI5pO could not be opened" or something similar when attempt to import your database then it means that Gramps 3 cannot see all of the files that constitute your database.
  
*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.
+
*Gramps XML: With this approach firstly start up Gramps 2.2 and export your database to the Gramps XML format. The XML file is actually compressed and contained in a .gramps file. This file is portable, has no other dependent files and can be moved to wherever you have Gramps 3 installed. Next, start Gramps 3 and create an empty database using the Family Tree Manager and import the .gramps file.
  
  
 +
{{languages|Gramps_3.0_Wiki_Manual_-_Manage_Family_Trees}}
  
{{man index|Gramps 3.0 Wiki Manual - Main Window|Gramps 3.0 Wiki Manual - Entering and Editing Data: Brief}}
+
{{man index|Gramps 3.0 Wiki Manual - Main Window|Gramps 3.0 Wiki Manual - Entering and Editing Data: Brief|3.0}}
  
  
 
[[Category:Documentation]]
 
[[Category:Documentation]]

Latest revision as of 12:19, 11 August 2009

Now we turn to 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.

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


Previous Index Next



Starting a New Family Tree

Fig. 3.1. Starting Family Trees


To start a new Family Tree, choose Family Trees ->Manage Family Trees or select the Family Trees button from the toolbar. This will open the Family Tree Manager.



Select the New button and GRAMPS will add a new Family Tree entry to the list of Family Trees. To change its name from the default Family Tree 1, click on the name and type in a new name.

Now select Load Family Tree to open the new, empty Family Tree.

Opening a Family Tree

To open a Family Tree, either choose Family Trees ->Manage Family Trees or click the Family Trees button on the Toolbar. The Family Tree Manager will appear and you'll see a list of all the Family Trees known to GRAMPS. An icon will display in the Status column 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 Tree.

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

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 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. TODO link to page explaining how. 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 to GRAMPS XML format (or GRAMPS Package to include items from your Gallery) and copy the resultant file to a safe place, preferably in a different building.

You can use the Archive feature to store snapshots of your 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

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

To make an archive, first make sure the tree you wish to archive is open. Then select the open family tree, and click the Archive button. The archive will be listed under the tree from which it was created. Archives can be deleted and renamed.

Restoring a Family Tree Archive

Fig. 3.2 Selecting a version to restore

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

Fig. 3.3 Restored version




GRAMPS will transfer the archive into a new Family Tree. The Family Tree name is based on the original name and the archive name.

Unlocking a Family Tree

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, select the locked family tree, and click the Unlock 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. 3.4 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 tell GRAMPS to attempt to repair the damage, select the Tree and then click the Repair button.

This will attempt to rebuild your 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've made by selecting 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 using the Undo History dialog available from the Edit menu.

If you want to return your Family Tree to the way it was when you opened it, select 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

Importing allows you to bring data from other genealogy programs into a GRAMPS database. Currently, GRAMPS can import data from the following formats:

GRAMPS V2.x database (.grdb file extension)

GEDCOM (.ged file extension)

GRAMPS XML (.gramps file extension)

GRAMPS package (.gpkg file extension)

GeneWeb (.gw file extension)

GRAMPS CSV Spreadsheet - comma separated values (.csv file extension)

Gramps-notes.png
Importing vs. opening

Please recognize that importing a database is different from opening a database. When you import, you are actually bringing data from one database into a GRAMPS database. When you open a file, you are editing your original file.

To import data, select Family Trees ->Import . The Import database dialog will open, asking you to specify the file you wish to import. 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 database and then import the data into it.

Gnome-important.png
Data loss with some formats

It is important to note that the importing process is not perfect for GEDCOM and GeneWeb databases. There is a chance that some of the data in these databases will not be imported into GRAMPS.

The GRAMPS V2.x database, GRAMPS XML, and GRAMPS package are all native GRAMPS formats. There is no risk of information loss when importing from or exporting to these formats.

  • GRAMPS V2.x database (grdb): Prior to Version 3.0, this native GRAMPS database format was a specific form of 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).
  • GRAMPS XML: The GRAMPS XML file was the default format for older (pre 2.x) versions of GRAMPS. Unlike the 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. The GRAMPS XML database is created by exporting ( Family Trees ->Export... ) to that format.
  • GRAMPS package: The GRAMPS 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 package is created by exporting ( 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.

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.

Exporting Data

Fig.3.4 Export assistant: format selection

Wait to update manual: The exporter is undergoing a major rewrite.


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. Currently, GRAMPS can export data to the following formats: GRAMPS XML, GEDCOM, GRAMPS package, Web Family Tree, GeneWeb, and GRAMPS CSV Spreadsheet formats.

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.

To export data, choose Family Trees ->Export . This will bring up the Export assistant. Its pages will guide you through the format selection (see Fig. 3.4 ), 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.

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. This format is compatible with the previous versions of GRAMPS.
  • 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.3.5.Export assistant: GEDCOM options

GRAMPS allows you to export a database into the common GEDCOM format. It provides options that allow you to fine tune your export (see gedcom-export-fig ).

  • Filter: The filter allows you to export a limited amount of data, based on the criteria you select.
  • Target: While GEDCOM is a standard, not every program implements it in the same way. This can lead to data loss. GRAMPS can reduce the data loss in some cases. You can tell GRAMPS what program is the target, and GRAMPS will customize the exported file for that program. If your program is not listed, choose the "GEDCOM 5.5 Standard".
  • 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 GEDCOM 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; you can exclude notes; and you can exclude sources for living people.

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.

  • Reference images from path: Check this box to tell GRAMPS to use the specific path for your images when writing image references in GEDCOM.

This option allows specify where your image files are located. This is useful when you are transferring your GEDCOM file from one computer to another. It tells the program that is importing the data where your images are.

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.
  • 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.
  • 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 .

Moving 2.2 databases to Gramps 3

There are two ways of moving your Gramps data from version 2.2 to version 3; either directly importing your version 2.2 grdb file or by exporting to XML format first. Because of complexity in the way that version 2.2 stores data, exporting to XML is usually the most convenient and problem free way of moving your data to version 3.

  • Import 2.2 grdb file: In a Gramps 2.2 database, your data is stored in a grdb file along with one or more log files that are kept in directories found in the .gramps/env directory. To import your 2.2 data directly into Gramps 3, create a new database and select the option to import a Gramps 2.2 database. You need to make sure that you are running Gramps 3 from the same user you used to run Gramps 2.2 so that it has access to the same .gramps/env directory containing the log files that supplement your database. If you are running Gramps 3 from a different user or on another machine you need to make provisions to make the same .gramps/env directory and log files available. If you get an error saying "/tmp/tmpDkI5pO could not be opened" or something similar when attempt to import your database then it means that Gramps 3 cannot see all of the files that constitute your database.
  • Gramps XML: With this approach firstly start up Gramps 2.2 and export your database to the Gramps XML format. The XML file is actually compressed and contained in a .gramps file. This file is portable, has no other dependent files and can be moved to wherever you have Gramps 3 installed. Next, start Gramps 3 and create an empty database using the Family Tree Manager and import the .gramps file.


Previous Index Next