Data Model – Entity Definitions

This page defines the principal conceptual entities used in the project’s data model.

Its purpose is to establish a shared and explicit understanding of what each entity represents before any technical implementation is undertaken.

These definitions describe meaning and responsibility, not database structure or software mechanics.

Scope

These definitions guide:

conceptual ER modeling
DBML and Cargo schemas
Page Schemas and forms
editorial workflows
interpretation of diagrams and documentation

If an entity definition is unclear or disputed, implementation must be postponed.

Conceptual overview

The model separates clearly between:

Storage → Files
Interpretation of files / sources → DigitalAssets
Subjects of research → HeritageObjects, Persons, Organizations
Narrative structure → ResearchChapters

The fundamental conceptual flow is:

File → DigitalAsset → Research Entity

Files provide storage. DigitalAssets provide interpretation and source metadata. Research entities provide historical meaning.

This separation prevents semantic confusion and keeps responsibilities explicit.

Core Research Entities

HeritageObject (HO)

Definition

A HeritageObject (HO) represents a historical, conceptual, or material entity that is the subject of study.

It answers the question:

“What is the thing we are studying?”

Examples

A HeritageObject may represent:

a sanatorium
a building
a document or register
a historically meaningful place
a room, component, or architectural element
a conceptual or functional unit (e.g. “medical practice”)

What a HeritageObject is not

A HeritageObject is:

not a digital file
not a person
not an organization
not a research chapter
not a technical database record

Structural behavior

HeritageObjects are recursive.

Each HeritageObject may:

have zero or one parent HeritageObject
have zero or more child HeritageObjects

This supports conceptual decomposition and hierarchical structuring.

Relationships

A HeritageObject may:

be documented by multiple DigitalAssets
designate one DigitalAsset as preferred representation
be linked to Persons with roles
be linked to Organizations with roles
have Persons or Organizations as holders
belong to multiple ResearchChapters
be tagged with Keywords

Purpose

HeritageObjects are the primary conceptual anchors of the research.

Person

Definition

A Person represents a historical individual with agency.

It answers the question:

“Who was involved historically?”

Examples

religious sisters
directors
architects
patients
shareholders
board members

What a Person is not

A Person is:

not a MediaWiki user account
not a HeritageObject
not an organization

Relationships

A Person may:

play roles in relation to HeritageObjects
play roles within Organizations
act as a holder of HeritageObjects
be documented by D*