Open main menu

Gramps β

Addon:GeneanetForGramps

Gramps-notes.png

Please use carefully on data that is backed up, and help make it better by reporting any comments or problems to the author, or issues to the bug tracker
Unless otherwise stated on this page, you can download this addon by following these instructions.
Please note that some Addons have prerequisites that need to be installed before they can be used.
This Addon/Plugin system is controlled by the Plugin Manager.
An Addons Offline Manual is available for review.

Gnome-important.png
Unofficial addon

This addon is not distributed through the Gramps Project. Complying with Geneanet copyright restrictions is not compatible with GPLv2 licensing terms. So it may only be distributed though third-parties.

The GeneanetForGramps addon allows you to import ancestors and descendants for a selected person from the Geneanet website.

Usage

Once this addon and its Prerequisite has been installed:

  • Select Menu Tools > Family Tree Processing -> Import Geneanet data for Gramps...
Gnome-important.png
Undo history warning

Proceeding with this tool will erase the undo history for this session. In particular, you will not be able to revert the changes made by this tool or any changes made prior to it. If you think you may want to revert running this tool, please stop here and backup your database.

  • From the Undo history warning dialogue you can choose Stop or Proceed with the tool.
Import from Geneanet into Gramps
  • The Geneanet Import Options tab is displayed with the following:
    • Center Person: - Person to process in Geneanet (by default the active one)
    • Genanet URL: - The URL on the Geneanet' site corresponding to the person selected in Gramps and from who you want to import ancestors and descendants. Note that in Gramps the person should have the same birth and death date so it works.
    • [ ] Import ascendants: - Check that box if you want to import ancestors of the person (False by default).
    • [ ] Import descendants: - Check that box if you want to import descendants of the person (False by default).
    • [ ] Import spouses: - Check that box if you want to import spouses of the person (False by default).
    • Level of import: Number of upper or lower parsing you'll do in the Geneanet tree. If you choose 2 (default), you'll get parents and grandparents, children and grandchildren. Be careful by using large numbers as the parsing can then take a long time.
    • [ ] Force import: Force overwrite of existing Gramps fields in a person replaced by the Geneanet Filed (False by default).
    • Verbosity: Increase the versbiosity in the text window where Gramps has been launched (from 0 to 4, 1 by default)

Once you have made your choices, you can either choose Close or Execute to launch the import.

Note that for the parsing to work, you need to have the same firstname/lastname and birth date/death date for the person in both Gramps and Geneanet. Using force mmay overwrite this security.

Tips

Make a try by just importing ancestors to check it's working correctly for you, and the you can add more persons. Limit the level of import when starting at 2 before increasing once you verified it's working for you. Note that the plugin can also be called from the CLI:

usage: GeneanetForGramps.py [-h] [-v] [-a] [-d] [-s] [-l LEVEL]
                            [-g GRAMPSFILE] [-i ID] [-f]
                            [searchedperson]

Import Geneanet subtrees into Gramps

positional arguments:
  searchedperson        Url of the person to search in Geneanet

optional arguments:
  -h, --help            show this help message and exit
  -v, --verbosity       Increase verbosity
  -a, --ascendants      Includes ascendants (off by default)
  -d, --descendants     Includes descendants (off by default)
  -s, --spouses         Includes all spouses (off by default)
  -l LEVEL, --level LEVEL
                        Number of level to explore (2 by default)
  -g GRAMPSFILE, --grampsfile GRAMPSFILE
                        Full path of the Gramps database (under
                        $HOME/.gramps/grampsdb)
  -i ID, --id ID        ID of the person to start from in Gramps
  -f, --force           Force processing

Prerequisites

For the addon to work you will need to install both the Request and lxml Python modules.

Requests

Install the python module Requests otherwise you will get the following error:

2020-12-06 10:29:40.191: WARNING: _manager.py: line 308: Plugin error (from 'GeneanetForGramps'): No module named 'requests'

lxml

Install the python module lxml otherwise you will get the following error:

2020-12-07 00:22:41.100: WARNING: _manager.py: line 308: Plugin error (from 'GeneanetForGramps'): No module named 'lxml'

SQLite only supported

Also note that you need to use a SQLite DB (based on API-DB) and NOT a BSDDB for the plugin to work. When using a BSDDB base you'll get the following error:

File "/users/gnucash/.gramps/gramps51/plugins/GeneanetForGramps/GeneanetForGramps.py",
line 1339, in find_grampsp
    ids = db.get_person_gramps_ids()
AttributeError: 'DbBsddb' object has no attribute 'get_person_gramps_ids'

You can Convert a BSDDB Family Tree to SQLite and then export from the previous and import into the new.

See also

Discourse discussion forum threads

Gramps-User maillist threads

Gramps-Devel maillist threads

Contents

GedcomforGeneanet Exporter

A complementary Exporter plugin (Greffons) is available at GitHub in Grocanar's repository: GedcomforGeneanet.

This plugin is an "improvement" of Geneanet's gedcom export. It provides the following features:

  • Export of cookies for events
  • Management of non-marital relationships
  • Including media paths
  • Exclude repository names in sources
  • Removing absolute paths in file path
  • Removing the “Merged Gramps ID” attribute
  • Added source quality to source description
  • Creation of a zip archive of the affected media
  • Removed support for the anychar standard from Gedcom 5.5
  • Management of common names
  • Exporting citation attributes
  • Export of an individual's census information with an optional extended format
  • Export of locations in geneanet format
  • Indication of the name of the place on the date of the event
  • Indication of alternative place names
  • Removal of optional address structure
  • Management of the display of titles of nobility
  • Addition of affiliation sources such as Individual Notes

Features

  • Export of cookies for events
  • Special case for baptisms
For baptisms If you have defined a CUSTOM role, the male person will be the Godfather and the female person will be my Godmother.
  • Witnesses and role.
For individual events other than baptism, all roles are assimilated to witnesses given the poverty of the GEDCOM standard. However, the extend_role option allows you to display the role but it will then be on two lines.
  • Management of non-marital relationships
For unmarried couples their status is no longer married.
  • Exclude repository names in sources
This allows you to exclude the repository name in the source name.
  • Removing absolute paths in file path
If the option is enabled this removes the path in the FILE tag. This generally allows you to delete user information in the gedcom file.
  • Removing the “Merged Gramps ID” attribute
This attribute is of no interest and is deleted during export.
  • Removed support for the anychar standard from Gedcom 5.5
Geneanet does not implement the anychar standard of the Gedcom5.3 standard which requires doubling the @ characters. So the dates exported to GRAMPS in an alternative calendar are not rendered well. This option removes the doubling of @.
  • Management of common names
Allows you to export the usual first name by indicating it between ".
  • Exporting citation attributes
Allows you to export the attributes of a citation. This makes it possible, for example, to indicate the URL of an act.
  • Exporting an individual's census information
Allows you to export information for an individual in a census in the form of event notes. If we select the extended format, it will display not only the information related to the individual but the information of all individuals in the household.
  • Export of locations in geneanet format
Geneanet imposes a format for place names that is not compatible with gramps. This option allows you to generate the title in geneanet format during export while retaining the automatic generation of the title in GRAMPS.
  • Indication of the name of the place on the date of the event
Indicate in a note the name of the place on the date of the event.
  • Indication of alternative place names
Indicate in notes the alternative names of the place.
  • Removal of optional address structure
The Gedcom standard allows the inclusion of an optional address structure for locations. This is the default operation of GRAMPS. But this causes a problem when importing Geneanet.
  • Management of titles of nobility
In the geneanet display we lose a certain amount of information and the title does not appear in the chronology. To have a clearer and more complete display I create on the fly a title type event which includes in a more complete way the information contained in the title of nobility event.
  • Addition of affiliation sources such as Individual Notes
GRAMPS allows you to put a source concerning the parentage of a person. This is interesting when you do not have birth or baptism certificates but you have a source allowing you to establish filiation such as a will. However, this is not provided for in the GEDCOM. This option allows you to add a Note to the individual.

Use an additional program

This option allows you to launch an additional library. When the option is activated, we generate their lienWii (Permalink?) for each individual in a table which is indexed by the handle of the individuals. This array is passed as a parameter in the function call

self.Extobj.run(filename,self.database,self.GENEWEBURL)

This function is contained in the ExtProg.py file.

This allows, for example, to make lists of people who can be included in the family chronicle. An example is provided which generates a list of all individuals in the database. Everyone can therefore adapt this code to their needs.