Citation Entity
Overview
A Citation entity represents a specific reference to evidence that supports genealogical conclusions. Citations link to Source entities and provide detailed information about where evidence was found within the source.
File Format
All GENEALOGIX files use entity type keys at the top level:
# Any .glx file (commonly in citations/ directory)
citations:
citation-birth-record:
source: source-parish-register
properties:
locator: "Page 45"
text_from_source: "John Smith, born 15 January 1850"Key Points:
- Entity ID is the map key (
citation-birth-record) - IDs can be descriptive or random, 1-64 alphanumeric/hyphens
Core Concepts
Citation vs. Source
- Source: A bibliographic resource (book, document, database, website)
- Citation: A specific reference to information within a source
One source can have many citations referencing different pages or sections.
Fields
Required Fields
| Field | Type | Description |
|---|---|---|
| Entity ID (map key) | string | Unique identifier (alphanumeric/hyphens, 1-64 chars) |
source | string | Reference to Source entity |
Optional Fields
| Field | Type | Description |
|---|---|---|
repository | string | Reference to Repository entity |
media | array | References to Media entities |
properties | object | Vocabulary-defined properties (see Citation Properties) |
notes | string | Free-form notes about the citation |
Properties
The following are standard properties from the default vocabulary; archives can define additional properties by extending the vocabulary:
| Property | Type | Description |
|---|---|---|
locator | string | Location within source (e.g., 'Page 45', 'Film 1234567, Image 87', 'Entry 123') |
text_from_source | string | Transcription or excerpt from the source |
source_date | date | Date when the source recorded the information |
accessed | date | Date when an online source or digital record was last accessed |
url | string | Direct web address for the specific cited material (e.g., a permalink to a record or image viewer) |
original_place_name | string | Verbatim place name from the source before normalization to a place entity (e.g., "The Town Of Oakdale" vs the normalized place reference) |
external_ids | string (multi) | Identifiers from external systems for the specific cited record (e.g., FamilySearch ARK, Ancestry record ID) |
See Also: Citation Properties Vocabulary
Usage Patterns
Simple Citation to Book
citations:
citation-marriage-record:
source: source-parish-register
properties:
locator: "Page 125"
text_from_source: "John Smith married to Mary Jones, 15 May 1850"Note: The id is the map key (citation-marriage-record), not a separate field.
Citation with Online Source
citations:
citation-census-online:
source: source-ancestry-census
properties:
locator: "Schedule 7, piece 1123, Image 87342534"
text_from_source: |
Name: John Smith
Age: 35
Occupation: Blacksmith
Place of Birth: Leeds, Yorkshire, EnglandCitation to Archive Document
citations:
citation-will-john:
source: source-probate-wills
repository: repository-probate
properties:
locator: "Page 23, Item 1876/X/150, Film 100234"
text_from_source: |
I, John Smith, being of sound mind, do hereby
bequeath all my goods and chattels...Citation with Media References
citations:
citation-photo:
source: source-photo-collection
media:
- media-john-photo
properties:
locator: "Album 1, page 5"
notes: "Photo provides visual evidence of person's appearance"Citation in Assertions
Citations are primarily used within Assertions to provide evidence:
assertions:
assertion-birth-john:
subject:
person: person-john-smith
property: born_on
value: "1850-01-15"
citations:
- citation-parish-birth
- citation-census-birth
confidence: high
notes: "Primary source from parish register"File Organization
Note: File organization is flexible. Entities can be in any .glx file with any directory structure. The example below shows one-entity-per-file organization, which is recommended for collaborative projects (better git diffs) but not required.
Citation files are typically embedded in assertion documents or organized by source:
sources/
├── books/
│ └── source-book001.glx
│ └── citations/
│ ├── citation-01.glx
│ └── citation-02.glx
└── online/
└── source-ancestry.glx
└── citations/
├── citation-01.glx
└── citation-02.glxOr more commonly, citations are referenced by ID from assertions.
GEDCOM Mapping
| GLX Field | GEDCOM Tag | Notes |
|---|---|---|
| Entity ID (map key) | (synthetic) | Not in GEDCOM |
source | SOUR | Source reference |
properties.locator | SOUR.PAGE | Location within source (GEDCOM PAGE is free-form text, not just page numbers) |
properties.text_from_source | SOUR.TEXT, SOUR.DATA.TEXT | Transcribed text |
properties.source_date | SOUR.DATA.DATE | Date when source recorded the information |
properties.external_ids | SOUR.EXID | External identifiers (GEDCOM 7.0 EXID within source citation context) |
Validation Rules
- Source ID must reference an existing Source entity
- Properties should follow the citation_properties vocabulary
- Text transcriptions should accurately represent source material
- Repository, if specified, must exist
Evidence Hierarchy
Citations are part of the GENEALOGIX evidence chain. See Core Concepts - Evidence Chain for the complete evidence chain from Repository → Source → Citation → Assertion.
Schema Reference
See citation.schema.json for the complete JSON Schema definition.
See Also
- Source Entity - Bibliographic resource
- Assertion Entity - Evidence conclusions
- Repository Entity - Where sources are held