Entidades

Una entidad en el estándar Gedcom es un componente genealógico principal, como un individuo, una familia, una fuente de información o una nota. También puede ser un objeto multimedia, como un vídeo o un registro de audio.

En un archivo Gedcom, una entidad es un registro identificado por un número de identificación y un grupo de etiquetas que especifican sus características.

Las diversas características genealógicas asociadas a una entidad se denominan propiedades: nacimiento, matrimonio, fecha, lugar, acontecimiento, texto, dirección, etc.

Ancestris sigue el estándar Gedcom lo más fielmente posible y utiliza los mismos conceptos de entidad y propiedad.

La organización de la información de cada entidad sigue la gramática precisa del estándar. Esta gramática ofrece varias posibilidades para almacenar la información. Para ver estas distintas posibilidades en Ancestris, utilice el editor Gedcom.

Las 7 categorías de entidades

Existen siete categorías de entidades en el estándar Gedcom. Una entidad siempre pertenece a una, y sólo a una, de estas siete categorías.

Cada categoría tiene sus propias propiedades. Sin embargo, independientemente de la categoría a la que pertenezcan, todas las entidades operan según los mismos principios. Estos se describen a continuación.

En Ancestris, todas las entidades son fácilmente accesibles desde la Tabla de Entidades.

Individuos

Un individuo, o persona, es un ser humano, vivo o fallecido. Es el componente principal de cualquier genealogía.

En el estándar Gedcom, una persona se define mediante la etiqueta INDI y tiene un número de identificación que puede ser prácticamente cualquier cosa. En Ancestris, este ID comienza con la letra I.

Apariencia en Ancestris :   INDI Individuo

Las principales propiedades de un individuo son:

• un nombre, formado por un nombre y un apellido, y posiblemente formado por otros elementos del nombre.
• acontecimientos como el nacimiento, el matrimonio, la ocupación y muchos otros.
  
• relaciones con otros individuos en la genealogía.

Los eventos y las relaciones son probablemente las partes más interesantes de tu genealogía porque son las piezas de información que te permitirán comprender la vida de tus antepasados ​​y las historias que podrían contarte.

NOMBRE: nombre de una persona. Esta etiqueta puede repetirse si la persona es conocida con varios nombres.

Sintaxis Gedcom:

NAME Lt. Cmndr. Joseph /Allen/ jr.

En este ejemplo, se considera jr. como sufijo del nombre. Toda la información se introdujo únicamente en la etiqueta NAME sin utilizar ninguna subetiqueta.

El estándar Gedcom proporciona una estructura detallada para almacenar el nombre de un individuo y especificar todos los elementos posibles de un nombre, en particular NICK y NSFX, que se colocan al final de NOMBRE.

GIVN : (nombre de pila) Nombre de pila. Su valor debe ser idéntico al de la etiqueta NAME. Es una etiqueta opcional. Los distintos nombres de pila se separan con una coma.

NICK: (apodo) Un nombre familiar o apodo, que se utiliza además del apellido o en lugar de este.

NPFX : (prefijo del nombre) Prefijo del nombre. Un elemento del nombre que precede al apellido (por ejemplo, Maestro, General, Doctor, etc.)

SPFX: (prefijo de apellido) Partícula que precede al apellido. Complemento del nombre que precede al apellido y que no se debe tener en cuenta al ordenar los apellidos. Los distintos artículos o prefijos de apellido se separan con una coma, por ejemplo, en el nombre “de la Cruz”, este valor debe ser “de, la”.

SURN : (apellido) Apellido de nacimiento, apellido. Los distintos apellidos se separan con una coma.

NSFX : (sufijo de nombre) Sufijo de apellido. Complemento del nombre, artículo, que sigue al apellido y que no se debe tener en cuenta al ordenar los apellidos. Los diferentes sufijos de nombre se separan con una coma. Ejemplo: mayor, hijo.

NOTA: Nota sobre el individuo

SOUR: Fuente de información que acredita la existencia y las características del individuo.

ALIA: (alias) Enlace con otra entidad individual, que indica que esta persona actual podría ser un duplicado de la otra y que una de las dos debería eliminarse eventualmente. Significa que las dos personas son la misma persona con un nombre diferente. Se deben usar dos etiquetas NAME para eso, dentro de una sola entidad individual.

Family

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. co-living). Most often, one or more children are associated with it.

A family is therefore a structure bringing together two or more individuals (spouse, children) as well as a set of specific properties such 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 :  FAM Family

Media

A Media, or 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 :  OBJE multimedia element

Warning ! There are two kinds of multimedia elements: the entity and the property. These two kinds 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 re-enter 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 please 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 :  NOTE Note

Warning ! There are two kinds of notes: the entity and the property. These two kinds 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 re-enter 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 on how to organze sources and repositories.

Appearance in Ancestris :  SOUR Source

Warning ! There are two kinds of sources: the entity and the property. These two kinds 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 re-enter the characteristics of the source as many times as you would need it.

Submitter

A submitter is a person who collects information to contribute to the construction of a genealogy file.

This person is likely to be one of the authors of the genealogy, or any genealogists likely to provide the Ancestris user with their genealogical information.

In the Gedcom standard, a submitter is defined by the SUBM tag and it has an ID number starting with the letter B in Ancestris.

Appearance in Ancestris :  SUBM Submitter

Repository

A repository is a place where genealogy sources can be found (documents, books, audio recordings, films, etc.). It can be a physical building (e.g. archive, cemetery), or a website (e.g. the website of the archive service).

Repository entities maintain a close relationship with source entities. A repository is likely to contain several sources, a source belongs to a repository.

In the Gedcom standard, a repository is defined by the REPO tag and it has an ID number starting with the letter R in Ancestris.

Appearance in Ancestris :  REPO Lieu de stockage

Header entity

The header 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. Refer to the File Properties page for more details.

Identification number of an entity

The ID number is an identification number assigned to each entity, within the same category. In order to avoid the creation of possible duplicates, this number is obviously unique.

Moreover, this particular number always has the same form, namely a letter followed by a certain number of digits. Each category of entity being associated with a particular letter, the first letter of the ID number indicates the category to which it belongs.

The user does not have to worry about assigning a new ID number when creating a new entity: this numbering is carried out automatically by Ancestris.

Note that in the Tools / Preferences / Editions / Identification number menu, a check box can be activated to reuse the ID numbers left available by entities that have been deleted.

Also, you can always change ID numbers later once entities have been created. Use the Generate ID Numbers tool for that.