ICT:Data Model Entity Definitions - v 4.0: Difference between revisions
No edit summary |
Layout enhanced |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
= Data Model – Entity Definitions = | = Data Model – Entity Definitions version 4.0 = | ||
This page defines the principal conceptual entities used in the project’s data model. | This page defines the principal conceptual entities used in the project’s data model. | ||
| Line 6: | Line 6: | ||
These definitions describe meaning and responsibility, not database structure or software mechanics. | These definitions describe meaning and responsibility, not database structure or software mechanics. | ||
== Scope == | == Scope == | ||
| Line 20: | Line 17: | ||
If an entity definition is unclear or disputed, implementation must be postponed. | If an entity definition is unclear or disputed, implementation must be postponed. | ||
== Conceptual overview == | == Conceptual overview == | ||
| Line 43: | Line 37: | ||
This separation prevents semantic confusion and keeps responsibilities explicit. | This separation prevents semantic confusion and keeps responsibilities explicit. | ||
= Core Research Entities = | = Core Research Entities = | ||
== HeritageObject (HO) == | == HeritageObject (HO) == | ||
| Line 59: | Line 47: | ||
''“What is the thing we are studying?”'' | ''“What is the thing we are studying?”'' | ||
=== Examples === | === Examples === | ||
| Line 71: | Line 57: | ||
* a room, component, or architectural element | * a room, component, or architectural element | ||
* a conceptual or functional unit (e.g. “medical practice”) | * a conceptual or functional unit (e.g. “medical practice”) | ||
=== What a HeritageObject is not === | === What a HeritageObject is not === | ||
| Line 82: | Line 66: | ||
* not a research chapter | * not a research chapter | ||
* not a technical database record | * not a technical database record | ||
=== Structural behavior === | === Structural behavior === | ||
| Line 92: | Line 74: | ||
* have zero or one parent HeritageObject | * have zero or one parent HeritageObject | ||
* have zero or more child HeritageObjects | * have zero or more child HeritageObjects | ||
=== Relationships === | === Relationships === | ||
| Line 106: | Line 86: | ||
* be tagged with Keywords | * be tagged with Keywords | ||
* be associated with one or more Places | * be associated with one or more Places | ||
=== Purpose === | === Purpose === | ||
HeritageObjects are the primary conceptual anchors of the research. | HeritageObjects are the primary conceptual anchors of the research. | ||
== Person == | == Person == | ||
| Line 123: | Line 99: | ||
''“Who was involved historically?”'' | ''“Who was involved historically?”'' | ||
=== Examples === | === Examples === | ||
| Line 134: | Line 108: | ||
* board members | * board members | ||
What a Person is not | |||
A Person is: | A Person is: | ||
| Line 142: | Line 115: | ||
* not a HeritageObject | * not a HeritageObject | ||
* not an organization | * not an organization | ||
=== Relationships === | === Relationships === | ||
| Line 154: | Line 125: | ||
Roles belong to relationships, not to the Person entity itself. | Roles belong to relationships, not to the Person entity itself. | ||
=== Purpose === | === Purpose === | ||
Persons model historical agency, responsibility, and participation. | Persons model historical agency, responsibility, and participation. | ||
== Organization == | == Organization == | ||
| Line 171: | Line 137: | ||
''“Which collective body acted or was responsible?”'' | ''“Which collective body acted or was responsible?”'' | ||
=== Examples === | === Examples === | ||
| Line 180: | Line 144: | ||
* institutions | * institutions | ||
* managing bodies | * managing bodies | ||
=== What an Organization is not === | === What an Organization is not === | ||
| Line 190: | Line 152: | ||
* not a Place | * not a Place | ||
* not a MediaWiki user group | * not a MediaWiki user group | ||
=== Relationships === | === Relationships === | ||
| Line 201: | Line 161: | ||
* be documented by DigitalAssets (reports, articles, archival material) | * be documented by DigitalAssets (reports, articles, archival material) | ||
* be located in a Place | * be located in a Place | ||
=== Purpose === | === Purpose === | ||
Organizations model collective responsibility and institutional continuity. | Organizations model collective responsibility and institutional continuity. | ||
== Place == | == Place == | ||
| Line 220: | Line 176: | ||
Places provide spatial context only and do not possess agency or responsibility. | Places provide spatial context only and do not possess agency or responsibility. | ||
=== Examples === | === Examples === | ||
| Line 233: | Line 187: | ||
* a country | * a country | ||
* a historically named or former location | * a historically named or former location | ||
=== What a Place is not === | === What a Place is not === | ||
| Line 247: | Line 199: | ||
Collective or governing bodies must be modeled as Organizations. | Collective or governing bodies must be modeled as Organizations. | ||
=== Structural behavior === | === Structural behavior === | ||
| Line 263: | Line 213: | ||
Room → Building → Site → City → Region → Country | Room → Building → Site → City → Region → Country | ||
=== Relationships === | === Relationships === | ||
| Line 272: | Line 220: | ||
* locate HeritageObjects | * locate HeritageObjects | ||
* provide creation or depiction context for DigitalAssets | * provide creation or depiction context for DigitalAssets | ||
=== Purpose === | === Purpose === | ||
| Line 285: | Line 231: | ||
Places separate '''where''' from '''who''' and '''what''', preserving conceptual clarity. | Places separate '''where''' from '''who''' and '''what''', preserving conceptual clarity. | ||
= Digital Representation and Sources = | = Digital Representation and Sources = | ||
== DigitalAsset (DA) == | == DigitalAsset (DA) == | ||
| Line 303: | Line 244: | ||
A DigitalAsset is the human, scholarly layer that gives meaning to a file. | A DigitalAsset is the human, scholarly layer that gives meaning to a file. | ||
=== Core principle === | === Core principle === | ||
| Line 312: | Line 251: | ||
Each file that requires interpretation has its own DigitalAsset. | Each file that requires interpretation has its own DigitalAsset. | ||
=== Examples === | === Examples === | ||
| Line 325: | Line 262: | ||
* a portrait | * a portrait | ||
* a letter or archival record | * a letter or archival record | ||
=== Relationship to Files === | === Relationship to Files === | ||
| Line 337: | Line 272: | ||
Files are storage. | Files are storage. | ||
DigitalAssets are interpretation. | DigitalAssets are interpretation. | ||
=== Recursive behavior === | === Recursive behavior === | ||
| Line 349: | Line 282: | ||
This models provenance and processing chains. | This models provenance and processing chains. | ||
=== Relationship to research entities === | === Relationship to research entities === | ||
| Line 358: | Line 289: | ||
* Persons | * Persons | ||
* Organizations | * Organizations | ||
=== Spatial context === | === Spatial context === | ||
| Line 368: | Line 297: | ||
* place of discovery | * place of discovery | ||
* or other relevant spatial association | * or other relevant spatial association | ||
=== Publication and citation role === | === Publication and citation role === | ||
| Line 379: | Line 306: | ||
* rights information | * rights information | ||
* publication suitability | * publication suitability | ||
=== What a DigitalAsset is not === | === What a DigitalAsset is not === | ||
| Line 389: | Line 314: | ||
* not a historical object itself | * not a historical object itself | ||
* not merely technical metadata | * not merely technical metadata | ||
=== Purpose === | === Purpose === | ||
| Line 400: | Line 323: | ||
* serve as scholarly sources | * serve as scholarly sources | ||
* support referencing and citation | * support referencing and citation | ||
== File (External System Entity) == | == File (External System Entity) == | ||
| Line 412: | Line 333: | ||
They gain research meaning only through DigitalAssets. | They gain research meaning only through DigitalAssets. | ||
= Research Structure = | = Research Structure = | ||
== ResearchChapter == | == ResearchChapter == | ||
| Line 428: | Line 344: | ||
''“Where does this belong in the research story?”'' | ''“Where does this belong in the research story?”'' | ||
=== Characteristics === | === Characteristics === | ||
| Line 438: | Line 352: | ||
* may be thematic or chronological | * may be thematic or chronological | ||
* may overlap with other chapters | * may overlap with other chapters | ||
=== Structural behavior === | === Structural behavior === | ||
| Line 445: | Line 357: | ||
Chapters may contain subchapters. | Chapters may contain subchapters. | ||
=== Relationships === | === Relationships === | ||
* a Chapter may include multiple HeritageObjects | * a Chapter may include multiple HeritageObjects | ||
* a HeritageObject may belong to multiple Chapters | * a HeritageObject may belong to multiple Chapters | ||
=== Purpose === | === Purpose === | ||
ResearchChapters organize interpretation rather than historical reality itself. | ResearchChapters organize interpretation rather than historical reality itself. | ||
= Supporting Concepts = | = Supporting Concepts = | ||
== Keywords == | == Keywords == | ||
| Line 468: | Line 371: | ||
They support discovery but do not define structure. | They support discovery but do not define structure. | ||
== Roles == | == Roles == | ||
| Line 485: | Line 385: | ||
Roles belong to relationships, not to entities themselves. | Roles belong to relationships, not to entities themselves. | ||
== Treatment of Uncertainty (Certainty) == | == Treatment of Uncertainty (Certainty) == | ||
| Line 495: | Line 393: | ||
Many statements involve approximation or interpretation. | Many statements involve approximation or interpretation. | ||
=== Design decision === | === Design decision === | ||
| Line 507: | Line 403: | ||
Uncertainty is not stored structurally. | Uncertainty is not stored structurally. | ||
=== Rationale === | === Rationale === | ||
| Line 517: | Line 411: | ||
* increase editorial burden | * increase editorial burden | ||
* convey less information than descriptive notes | * convey less information than descriptive notes | ||
=== How uncertainty is expressed === | === How uncertainty is expressed === | ||
| Line 527: | Line 419: | ||
* explicit notes | * explicit notes | ||
* citations to DigitalAssets | * citations to DigitalAssets | ||
=== Future extension === | === Future extension === | ||
| Line 535: | Line 425: | ||
Until then, descriptive practice remains the standard. | Until then, descriptive practice remains the standard. | ||
== Status == | |||
This document defines the agreed conceptual meaning of the entities – Version 4.0 and 4.1. | |||
4.1 is only different in a number of added attributes for automatic namegeneration. | |||
All ER diagrams, DBML definitions, schemas, and implementations must conform to these definitions. | All ER diagrams, DBML definitions, schemas, and implementations must conform to these definitions. | ||
Latest revision as of 15:50, 30 January 2026
Data Model – Entity Definitions version 4.0
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
- Spatial context → Places
- Narrative structure → ResearchChapters
The fundamental conceptual flow is:
File → DigitalAsset → Research Entity → Place
Files provide storage. DigitalAssets provide interpretation and source metadata. Research entities provide historical meaning. Places provide spatial context.
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
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
- be associated with one or more Places
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 DigitalAssets (portraits, letters, biographies, articles)
Roles belong to relationships, not to the Person entity itself.
Purpose
Persons model historical agency, responsibility, and participation.
Organization
Definition
An Organization represents a historical collective actor with institutional continuity.
It answers the question:
“Which collective body acted or was responsible?”
Examples
- religious congregations
- companies
- associations
- institutions
- managing bodies
What an Organization is not
An Organization is:
- not a person
- not a HeritageObject
- not a Place
- not a MediaWiki user group
Relationships
An Organization may:
- play roles in relation to HeritageObjects
- include Persons with roles
- act as holder of HeritageObjects
- be documented by DigitalAssets (reports, articles, archival material)
- be located in a Place
Purpose
Organizations model collective responsibility and institutional continuity.
Place
Definition
A Place represents a geographical or spatial location.
It answers the question:
“Where is or did this exist or occur?”
Places provide spatial context only and do not possess agency or responsibility.
Examples
A Place may represent:
- a city
- a village
- a building
- a site or complex
- a region or landscape
- a country
- a historically named or former location
What a Place is not
A Place is:
- not a person
- not an organization
- not a HeritageObject
- not an actor with responsibility
Places have no agency.
Collective or governing bodies must be modeled as Organizations.
Structural behavior
Places are recursive.
Each Place may:
- have zero or one parent Place
- have zero or more child Places
This supports geographic hierarchies.
Examples:
Room → Building → Site → City → Region → Country
Relationships
A Place may:
- locate Organizations
- locate HeritageObjects
- provide creation or depiction context for DigitalAssets
Purpose
Places:
- provide structured geographic information
- support querying and filtering by location
- prevent misuse of Organizations for spatial data
- avoid storing locations as free text
- enable future geographic extensions such as mapping or spatial search
Places separate where from who and what, preserving conceptual clarity.
Digital Representation and Sources
DigitalAsset (DA)
Definition
A DigitalAsset (DA) represents the research interpretation and extended metadata of exactly one digital file.
It answers the question:
“How do we interpret and describe this specific digital file as a research source?”
A DigitalAsset is the human, scholarly layer that gives meaning to a file.
Core principle
One DigitalAsset corresponds to exactly one File.
There is never a grouping of multiple files inside one DigitalAsset.
Each file that requires interpretation has its own DigitalAsset.
Examples
A DigitalAsset may represent:
- a photograph
- a scanned document
- an OCR transcription
- a cropped derivative
- a newspaper article
- a portrait
- a letter or archival record
Relationship to Files
A DigitalAsset:
- always references exactly one File
- does not manage storage
- does not replace MediaWiki file handling
Files are storage. DigitalAssets are interpretation.
Recursive behavior
DigitalAssets are recursive.
A DigitalAsset may:
- derive from another DigitalAsset
- have multiple derived children
This models provenance and processing chains.
Relationship to research entities
A DigitalAsset may document one or more:
- HeritageObjects
- Persons
- Organizations
Spatial context
A DigitalAsset may optionally reference a Place to record:
- place of creation
- place depicted
- place of discovery
- or other relevant spatial association
Publication and citation role
DigitalAssets may additionally store:
- bibliographic citation text
- repository information
- permalinks
- rights information
- publication suitability
What a DigitalAsset is not
A DigitalAsset is:
- not a file
- not a container of files
- not a historical object itself
- not merely technical metadata
Purpose
DigitalAssets exist to:
- separate meaning from storage
- provide rich research metadata
- document provenance
- serve as scholarly sources
- support referencing and citation
File (External System Entity)
Definition
A File is a physical digital object managed by MediaWiki.
Files are external to the conceptual research domain and provide storage only.
They gain research meaning only through DigitalAssets.
Research Structure
ResearchChapter
Definition
A ResearchChapter represents a conceptual or narrative unit of interpretation.
It answers the question:
“Where does this belong in the research story?”
Characteristics
A ResearchChapter:
- structures interpretation
- is not merely a date range
- may be thematic or chronological
- may overlap with other chapters
Structural behavior
ResearchChapters are recursive.
Chapters may contain subchapters.
Relationships
- a Chapter may include multiple HeritageObjects
- a HeritageObject may belong to multiple Chapters
Purpose
ResearchChapters organize interpretation rather than historical reality itself.
Supporting Concepts
Keywords
Keywords provide flexible thematic tagging.
They support discovery but do not define structure.
Roles
Roles qualify relationships between entities.
Examples:
- creator
- owner
- restorer
- shareholder
- board member
- holder
Roles belong to relationships, not to entities themselves.
Treatment of Uncertainty (Certainty)
Conceptual position
Uncertainty is inherent in historical research.
Many statements involve approximation or interpretation.
Design decision
The data model deliberately does NOT implement:
- certainty entities
- confidence scores
- high/medium/low levels
- probability flags
Uncertainty is not stored structurally.
Rationale
Formal certainty levels:
- create false precision
- oversimplify interpretation
- increase editorial burden
- convey less information than descriptive notes
How uncertainty is expressed
Use:
- precise wording
- ranges or approximate values
- explicit notes
- citations to DigitalAssets
Future extension
Structured certainty may be added only if clear analytical needs arise.
Until then, descriptive practice remains the standard.
Status
This document defines the agreed conceptual meaning of the entities – Version 4.0 and 4.1.
4.1 is only different in a number of added attributes for automatic namegeneration.
All ER diagrams, DBML definitions, schemas, and implementations must conform to these definitions.