Skip to main content

Entities (STLM)

An entity in the Gedcom standard is a main genealogical component such as an individual, a family, a source of information or a note. It can also be an multimedia object such as a video or a audio record.

In the Gedcom file, an entity is a record identified by an identification number and a group of tag specifying its characteristics.

The various genealogical characteristics associated with an entity are called properties: birth, marriage, date, place, event, text, address, etc.

Ancestris follows the Gedcom standard as closely as possible and uses the same concept of entity and property.

The organization of information for each entity follows the precise grammar of the standard. This grammar provides several  possibilities to store the information. To see these various possibilities in Ancestris, use the Gedcom editor.

 

The 7 categories of entities

There are seven categories of entities in the Gedcom standard. An entity always belongs to one, and only one, of these seven categories.

Each category has its dedicated properties. However, regardless of the category to which they belong, all entities operate according to the same principles. There are described below.

In Ancestris, all entities are easily accessible from the Entity Table.

 

Individual

An individual, or a person, is a human being, living or deceased. It is the primary component of any genealogy.

In the Gedcom standard, an individual is defined by the INDI tag, and has an identification number which could nearly be anything. In Ancestris, this ID starts with the letter I.

Appearance in Ancestris : Ancestris gedcom tag sexm.png Ancestris gedcom tag sexf.png Ancestris gedcom tag sexin.png INDI Individual

Main properties

The main properties of an individual are:

  • a name, made of a first name and a lastname, and possibily made of other name elements.
  • events such as birth, marriage, occupation, and many others.
  • relationships with other individuals in the genealogy.

Events and relationships are probably the most interesting parts of your genealogy because they are the pieces of information that you will let you understand the life of your ancestors and the stories they could tell you.

Ancestris gedcom tag name.png NAME : name of an individual. This tag can be repeated if the individual is known under several names.

Gedcom syntax:

NAME Lt. Cmndr. Joseph /Allen/ jr.

In this example jr. is considered the suffix of the name. All the information was entered only in the NAME tag without using any sub-tag.

The Gedcom standard provides a detailed structure to store the name of an individual, and specify all the possible elements of a name, in particular NICK and NSFX which are placed at the end of NAME.

Ancestris gedcom tag name.png GIVN : (given name) First name. The first name (s) of an individual: its value must be identical to that in the NAME tag. It is an optional tag. The different first names are separated by a comma.
Ancestris gedcom tag name.png NICK : (nick name) A familiar name or nickname, which is used in addition to, or instead of, the last name.
Ancestris gedcom tag name.png NPFX : (name prefix) Name prefix. An element of the name that precedes the lastname (e.g. Master, General, Doctor, etc.)
Ancestris gedcom tag name.png SPFX : (surname prefix) Particle before the Lastname. A complement to the name which is preceding the name, and which is not to be taken into account when sorting lastnames. Different articles / name prefixes are separated by a comma, for example in the name “de la Cruz”, this value must be “de, la”.
Ancestris gedcom tag name.png SURN : (surname) Lastname at birth, family name. Different surnames are separated by a comma.
Ancestris gedcom tag name.png NSFX : (name suffix) Lasname Suffix. A complement to the name, an article, which follows the last name, and which is not to be taken into account when sorting lastnames. Different name suffixes are separated by a comma. Example: eldest, son.
Ancestris gedcom tag note.png NOTE : Note about the individual
Ancestris gedcom tag sour.png SOUR : Source of information proving the existence and the characteristics of the individual.
Ancestris gedcom tag sexin.png ALIA : (alias): Link with another individual entity, indicating that this current individual could be a duplicate of the other one and that one of the two should be removed enventually. It does mean that the two persons are the same person with a different name. One should use two NAME tags for that, within one single individual entity.

 

Famille

A family is a couple of human beings, living or deceased, united either by a legal union (e.g. marriage) or by a de facto union (e.g. cohabitation). Most often, one or more children are associated with it.

A family is therefore a structure bringing together two individuals as well as a set of specific properties, such as children, as well as the various events associated with it (marriage, divorce, etc.)

In the Gedcom standard, a family is designated by the FAM tag and receives an ID number starting with the letter F in Ancestris.

Appearance in Ancestris : Ancestris gedcom tag fam.png FAM Family

 

Multimedia element

A Multimedia Element is a photo, an audio or video document (a photograph, an audio recording, a film, a copy of a document, etc.) generally intended to be associated with one or more individuals or families or to be associated with a source.

In the Gedcom standard, a multimedia element is defined by the OBJE tag. It has an ID number starting with the letter M in Ancestris.

Appearance in Ancestris : Ancestris gedcom tag obje.png OBJE élément multimédia

Warning ! There are two kinds of multimedia elements: the entity and the property. These two categories of media, although they have the same tag (OBJE), should not be confused.

  • The multimedia entity can be used by several other entities. It is therefore meant to be shared, collective or common. It is truly autonomous and can exist independently of the entities that refer to it. Example: a audio file specifying your analysis of a research involving several individuals.
  • The multimedia property is intended to qualify a single piece of information of the genealogy. It can only be used once. It is useless when taken out of its context, its connection to the information to which it relates. Example: a video of a newly born child. The multimedia property, unlike the multimedia entity, does not receive any ID number and is only valid for a single property, in a given entity. It can only exist within the entity that includes it. If the entity is deleted, the property disappears with it.

In summary, if the same multimedia object must be assigned to several individuals, several families, etc., it is more efficient to store it in the form of a object entity. Once entered, it will be possible to use it an infinite number of times. As a object property, you would have to reenter the link to the media file as many times as you would need it.

Warning ! Ancestris does not make any copy of your multimedia files. It just "refers" to the actual files. Ancestris will read them where you will need them in Ancestris. So do not erase them thinking that Ancestris made a copy of them.

 

Note

A note is a text information that can be associated with other categories of entities (individuals, families, multimedia elements, etc.) or with a property anywhere in the genealogy.

In the Gedcom standard, a note is defined by the tag NOTE and it has an ID number starting with the letter N in Ancestris.

Appearance in Ancestris : Ancestris gedcom tag note.png NOTE Note

Warning ! There are two kinds of notes: the entity and the property. These two categories of notes, although they have the same tag (NOTE), should not be confused.

  • The note entity can be used by several other entities. It is therefore meant to be shared, collective or common. It is truly autonomous and can exist independently of the entities that refer to it. Example: a text specifying your analysis of a research involving several individuals.
  • The note property is intended to qualify a single piece of information of the genealogy. It can only be used once. It is useless when taken out of its context, its connection to the information to which it relates. Example: a characteristic of a newly born child. The note property, unlike the note entity, does not receive any ID number and is only valid for a single property, in a given entity. It can only exist within the entity that includes it. If the entity is deleted, the property disappears with it.

In summary, if the same note must be assigned to several individuals, several families, etc., it is more efficient to store it in the form of a note entity. Once entered, it will be possible to use it an infinite number of times. As a note property, you would have to reenter the text of the note as many times as you would need it.

 

Source

A source is anything that defines the origin of a piece information. It can be a document, a book, a monument, etc.

It can also be a natural person: your great-grandmother can, for example, be qualified as a source, if she has transmitted a family history to you orally for instance.

This entity is intended to collect very precisely the various references (document title, symbol, act number, page, etc.) in order to allow any subsequent verification of the characteristics of other entities (in particular, individuals and families).

In the Gedcom standard, a source is defined by the SOUR tag and it has an ID number starting with the letter S in Ancestris.

Sources maintain a close relationship with other entities, repositories. A repository contains sources, and sources are located in repositories. Please refer to the following section for detailed considerations.

Appearance in Ancestris : Ancestris gedcom tag sour.png SOUR Source

Warning ! There are two kinds of sources: the entity and the property. These two categories of sources, although they have the same tag (SOUR), should not be confused.

  • The source entity can be used by several other entities. It is therefore meant to be shared, collective or common. It is truly autonomous and can exist independently of the entities that refer to it. Example: a marriage deed.
  • The source property is intended to qualify a single piece of information of the genealogy. It can only be used once. It is useless when taken out of its context, its connection to the information to which it relates. The source property, unlike the source entity, does not receive any ID number and is only valid for a single property, in a given entity. It can only exist within the entity that includes it. If the entity is deleted, the property disappears with it.

In summary, if the same source must qualify several events of individuals, families, etc., it is more efficient to store it in the form of a source entity. Once entered, it will be possible to use it an infinite number of times. As a source property, you would have to reenter the characteristics of the source as many times as you would need it.

 

Fournisseur d'informations Submitter

UnA fournisseur d'informationssubmitter estis unea personneperson physiquewho quicollects collecteinformation desto informationscontribute ento vue de participer à lathe construction d'unof fichiera degenealogy généalogie.file.

IlThis s'agitperson toutis d'abordlikely deto l'utilisateurbe d'one of the authors of the genealogy, or any genealogists likely to provide the Ancestris enuser trainwith detheir travaillergenealogical sur sa généalogie, mais également, d'autres généalogistes susceptibles de fournir à ce dernier différentes données qu'ils ont eux-mêmes trouvées.

Il s'agit d'une structure permettant d'enregistrer les différentes coordonnées et références des personnes qui collectent des informations généalogiques.information.

DansIn lathe normeGedcom Gedcom,standard, una fournisseursubmitter d'informationsis estdefined désignéby parthe l'étiquetteSUBM tag and it has an ID number starting with the letter SUBMB etin reçoit un numéro ID commençant par la lettre B.Ancestris.

Appearance in Ancestris : Ancestris gedcom tag subm.png SUBM FournisseurSubmitter

d'informations

 : un individu ou une personne qui a rassemblé des informations dans un fichier ou les transmet à quelqu'un d'autre.

Lieu de stockage ou dépôtRepository

UnA lieu de stockagerepository ouis dépôta estplace unwhere sitegenealogy oùsources peuventcan êtrebe trouvées les sources d'une généalogiefound (documents, livres,books, enregistrementsaudio audio,recordings, films...films, etc.). IlIt peutcan s'agirbe d'una sitephysical physiquebuilding (e.g. archive, cemetary), or a website (e.g. the website of the archive départementale), ou bien d'un site Internet (le site Internet de l'archive départementale)service).

LesRepository sourcesentities etmaintain lesa dépôtsclose constituentrelationship deuxwith entitéssource différentesentities. quiA entretiennentrepository cependantis deslikely relationsto étroites.contain En effet, d'une part, un dépôt est susceptible de contenir plusieursseveral sources, d'autrea part,source lorsbelongs deto laa création d'une source, il est nécessaire de faire un lien vers son dépôt. Par voie de conséquence, il est plus logique et plus cohérent de créer le dépôt avant de créer la source.repository.

DansIn lathe normeGedcom Gedcom,standard, una lieurepository deis stockagedefined estby désignéthe parREPO l'étiquettetag and it has an ID number starting with the letter REPOR etin reçoit un numéro ID commençant par la lettre R.Ancestris.

NotationAppearance in Ancestris : Ancestris gedcom tag repo.png REPO Lieu de stockage : le lieu de stockage est l'endroit où les documents, enregistrements, et autres sources, sont entreposés.

 

 En-tête

Ancestris gedcom tag inconnu.png HEAD L'en-tête par lequel le fichier débute le Gedcom. L'en-tête contient les renseignements sur le fichier : version de la norme, auteur du fichier, organisation des juridictions, etc.

Sa création est prise en charge par Ancestris lors de la création d'un nouveau fichier. Vous n'aurez certainement pas besoin de le modifier par la suite.

Modification, consultation :  (n'oubliez-pas de faire une copie de sauvegarde).

 

NuméroHeader d'identification d'une entité entity

LeThe numéroheader entity is the first record of the Gedcom file. The header contains information about the file: version of the standard (5.5 or 5.5.1), the author of the file, structure of jurisdictions in places, etc.

Its creation is taken care of by Ancestris when creating a new file. You most probably will not need to change it after creation.

In Ancestris, it can be edited using the Menu > File > Properties.

 

Identification number of an entity

The ID estnumber unis numéroan d'identification affecténumber àassigned chaqueto entité,each àentity, l'intérieurwithin d'unethe mêmesame catégorie.category. AfinIn d'éviterorder lato créationavoid d'éventuelsthe doublons,creation ceof numéropossible estduplicates, bienthis évidemmentnumber is obviously unique.

ParMoreover, ailleurs,this ceparticular numéronumber particulieralways has the same form, namely a toujoursletter lafollowed mêmeby forme, à savoir une lettre suivie d'una certain nombrenumber deof chiffres.digits. Or,Each chaquecategory catégorieof d'entitéentity étantbeing associéeassociated àwith unea lettreparticular particulière,letter, lethe n°first letter of the ID indiquenumber sansindicates équivoquethe lacategory catégorieto dewhich laquelleit il relève.belongs.

L'utilisateurThe n'user does not have to worry about assigning a pas à se préoccuper d'attribuer un nouveau numéronew ID aunumber momentwhen decreating laa créationnew d'uneentity: nouvellethis entité :numbering cetteis numérotationcarried estout enautomatically effetby effectuée par Ancestris, de manière automatique.Ancestris.

OnNote noterathat quein lathe commande menu OutilsTools / PréférencesPreferences / ÉditionsEditions / NuméroIdentification d'identification,number autorisemenu, Ancestris,a lorsquecheck labox casecan àbe cocheractivated estto activée,reuse àthe réutiliserID lesnumbers numérosleft attribuésavailable àby desentities entitésthat ayanthave étébeen supprimées.deleted.

 

 

 

Back to top