G5 Person

This page describes how the notion of person is handled in g5 database.
The structure of a person is given by src/model/Person.yml
Table definition is in src/model/db-create
create table person (
    id              serial primary key,
    slug            varchar(255) unique not null,
    ids_in_sources  jsonb not null,
    partial_ids     jsonb not null,
    name            jsonb not null,
    sex             char(1),
    birth           jsonb not null,
    death           jsonb not null,
    occus           jsonb not null,
    trust           char(1),
    acts            jsonb not null,
    history         jsonb not null,
    issues          jsonb not null,
    notes           jsonb not null

Person ids

Unique ids

Every person of the database has 2 unique ids:
  • Person slug, its g5 unique id (see definition in page G5 database).
    These can be read by humans and are used to build the public URL of a person in opengauquelin.org.
  • Id generated by the database (serial in postgresql, equivalent of autoincrement in mysql).
    These are used to associate person to groups.

Ids in sources

Field ids_in_sources is a jsonb key value map giving the local ids of a person within its information sources.
As a person is ALWAYS related to at least one information source, this field is never empty.

For example, Georges Dumas is present in files A1, A6 and Müller's 1083 physicians:
select ids_in_sources from person where slug='dumas-georges-1866-03-06';
{"a2": "241", "a6": "282", "afd5": "325"}

Partial ids

While field ids_in_sources represents the local ids of a person within precise information sources, the notion of partial ids permit to identify the person within several meaningful contexts. These "meaningful contexts" are information sources of higher level (parent sources of precise sources).
One person can be associated to one or more partial ids.
A given partial id concerns a subset of the database.

The following partial ids are defined in g5 database :
Source slugDefinitionExample
lerrcpGauquelin unique idA3-543
mullerMüller unique idM2-163
ertelErtel unique idES-3548
cparaComité Para unique idCP-245
csicopCSICOP unique idCS-504
cfeppCFEPP unique idCF-546
wdWikidata unique idQ161247
select ids_partial from person where slug='dumas-georges-1866-03-06';
{"lerrcp": "A2-241", "muller": "M5-325"}


This field permits to keep a trace of the transformations done on a person.
Each history entry contains the raw data used to modify the person, and the values that were retained to modify the peron.
This is useful to identify the errors in the original files, and is used for debug and verification puropse.


Array of strings describing the potential problems existing on some values of the field.
A basic implementation permit to store an array of issue within a person, but this mechanism needs to be bettered (introduce issue types and store the issues in a separate table).

Person name

  official:         # As written in the birth certificate
  nobl:             # nobiliary-particle: de d' di del von...
  fame:             # stage, scene
    full:           # ex Mistinguett or Stromae
  alter: []         # alternative names, like nicknames, or author names
TODO Write explanations

Birth and death dates