G5 Person | Open Gauquelin database

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,
    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) - a string like abonneau-pierre-1854-01-10.
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 by postgresql (the database management system) to link persons to other entities, like 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 (often 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 slug	Definition	Example
lerrcp	Gauquelin LERRCP unique id	A3-543
g55	Gauquelin 1955 unique id	02-284
muller	Müller unique id	M2-163
ertel	Ertel unique id	ES-3548
cpara	Comité Para unique id	CP-245
csicop	CSICOP unique id	CS-504
cfepp	CFEPP unique id	CF-546
wd	Wikidata unique id	Q161247

select ids_partial from person where slug='dumas-georges-1866-03-06';

{
    "lerrcp": "A2-241",
    "muller": "M5-325"
}

Build history

Field history permits to track the initial raw values and the transformations done on a person data during the build process of the database.
Each history entry contains the raw data used to modify the person, and the values that were retained to modify the person.
To identify the errors in the original files, debug and check data.

Build notes

Field notes contains

Person name

The name of a person is modeled by this structure:

name:
  full:
  family:
  given:
  nobl:
  official:
    family:
    given:
  spouse: []
  alter: []

name.full, name.given, name.family and name.nobl represent the name commonly used to designate a person.
These can be different from the official name.
It can be either the "real" name of the person, or a pseudonym.
Can be full (ex: "Mistinguett" or "Stromae") or composed, like "Edith" (name.given) "Piaf" (name.family).
name.nobl : nobiliary-particle: de d' di del von...
WARNING Field name.family does NOT contain the nobiliary-particle, stored in name.nobl.
name.official represent the exact spelling of the name, as written in the birth certificate.
For noble persons, name.official.family represents the raw name as written in the certificate, then it contains nobiliary-particle.
If the person has several given names, name.official.given contains them all.
name.spouse : array of spouse names (in general, used for married women). This field is informative only ; if the person is known using her spouse name, this information must be repeated in field name.family.
name.alter: Array of alternative names. For example Boris Vian (a french writer) wrote a book using the name of Vernon Sullivan.

Birth and death dates

In database, stored in the fields birth and death of a Person.
These fields contain a json string with this structure:

{
    "date": "1891-07-18 08:00",
    "date-ut": "1891-07-18 07:51",
    "tzo": "+00:09:21",
    "notime": null,
    "lmt": null,
    "place": {
        "c1": null,
        "c2": "33",
        "c3": "",
        "cy": "FR",
        "lg": -0.5805,
        "lat": 44.84044,
        "name": "Bordeaux",
        "geoid": 3031582
    }
}

Note the redundant information, as date-ut + tzo = date

The field note of person is a json string used to store information about the person.
Field notes.tzo is used to report timezone computation.

{
    "tzo": {
        "err": "IT1 End of WW2",
        "trust": 0
    }
}

{
    "tzo": {
        "err": "IT1 End of WW2",
        "trust": 0
    }
}

Links with other entities

TODO