Please update or expand this section.
The GrampsPseudonymTree example data is used to provide a self-explanatory & predictable Tree structute for testing, for exploring through charting options & filter rules, and for experimenting.
It is offered as an alternative to the example.gramps file and supports a different learning modality. The GrampsPseudonymTree is more abstract and tries to avoid becoming obscured by non-essential detail. The idea is to avoid losing clear sight of the Tree's trunk & branches behind the leaves.
The file is corrupt and does not work GrampsPseudonymTree(02Feb2020).gz file ideally will have an abstraction to represent the various relationships in Gramps.
The 'names' are actually generic labels of the relationship. This allows sample reports, charts & filters to be run where the abstracted results automatically self-document & build their own lookup key. It is useful for verifying results when developing an addon. If designing a 'book' collation of reports, running the book design on this abstracted Tree of data can produce the foundation for a 'how to interpret this book' section.
This abstracted data helps verify that the database was polled correctly and the data placement is appropriate. Also, when generating indexed output based on a Genealogical Numbering System, the output can be directly compared to the relationship without the need for a lookup or search in the database.
About the file
Gramps recognizes 2 variants of files labeled with the .gramps file format extension. There is a plain text file in a XML (extensible markup language) structure & a GNU gzip compressed archive containing that first variant format.
The actual downloadable file is a standard Gramps backup file which uses the compressed variant. (The original 70K XML text file of the Tree compresses to a 9K archive.) This not only provides a faster download but also has a built-in checksum integrity validation to ensure the file transferred without damage.
Unfortunately, the wiki doesn't permit the Gramps extension for uploads. But since Gramps uses the typical gzip format as its own archival format and merely substitutes the .gramps extension for .gz normal extension) files, we'll use the more-standard .gz extension. After downloading, you can change the extension back to .gramps for full Gramps compatibility.
Follow these steps to load the example family tree:
- Click the linked file at the top of this page
- Find the
GrampsPseudonymTree(02Feb2020).gzdownloaded to your system.
Since the file is named
GrampsPseudonymTree(02Feb2020).gz, you must rename it to
GrampsPseudonymTree(02Feb2020).grampsbefore the Gramps import tool will recognize it. You can copy this renamed file to a temporary location or import it directly from this directory.
- on MS-Windows AIO
C:\Program Files\GrampsAIO64-X.X.X\share\doc\gramps\example\gramps(On MS-Windows ensure you can see hidden files; see User Directory:MS Windows)
- On Apple MacOS the example database is not included in the MacOS AIO(All in one package) and you may download the files from here and import the Family Tree. (On MacOS ensure you can see hidden files; see: User Directory:Mac OS X)
- on MS-Windows AIO
- Start Gramps
- To create a new family tree Family Trees > Manage Family Trees... select the New button. Give it some name to indicate that is a disposable tree, such as "pseudo"
- Open this new family tree. It will be empty.
- In Gramps, use Family Trees > Import... to import
Import Statistics of the GrampsPseudonymTree(02Feb2020).gramps family tree
Number of new objects imported:
Grafting multiple Import branches together into a bigger test Tree
You can duplicate this branch to make a more varied Tree. Usually, repeated imports of the same data is a very bad idea and make a mess of duplicates. But since this is a pseudo Tree, with placeholders instead of real people, duplicates are simply assumed to be non-duplicates.
As an example:
- repeat the import
- rename the newer "1 Progenitor" as "4 iii.(spouse) son-in-law"
- copy the "4 iii.(spouse) son-in-law" to the clipboard
- navigate the Relationship view to the remaining Progenitor's 3rd child, a daughter called "4 iii. Daughter"
- drag "4 iii.(spouse) son-in-law" from the clipboard to the empty husband spot.
The 2 imported branches are now grafted together. This also creates a 'blended' step-family example... the renamed "4 iii.(spouse) son-in-law" has another spouse & offspring.
Connecting to the example Media Objects
There are no example Media Objects (JPEG and PNG images) provided.l