Jump to content

ICT:Data Model Entity definitions: Difference between revisions

From Costa Sano MediaWiki
Newer edit →
Mngr (talk | contribs)
Bots, Bureaucrats, club, ict, Interface administrators, research, Suppressors, Administrators
1,013 edits
VisualWikitext
Created page with "= Conceptual Definitions of Principal Entities = This page defines the meaning of the principal entities used in the data model. Its purpose is to ensure a shared understanding of each entity before finalizing the ER model and starting any technical implementation. The definitions are conceptual, not technical, and should be read as design intent rather than database specification. == Scope == These definitions apply to: * Conceptual ER modeling * Future Cargo tabl..."
 
No edit summary
Line 1: Line 1:
= Conceptual Definitions of Principal Entities =
= Data Model – Entity Definitions =


This page defines the meaning of the principal entities used in the data model.
This page defines the principal entities used in the data model.


Its purpose is to ensure a shared understanding of each entity before finalizing the ER model and starting any technical implementation.
Its purpose is to establish a shared and explicit understanding of what each entity represents, before any technical implementation is undertaken.


The definitions are conceptual, not technical, and should be read as design intent rather than database specification.
These definitions are conceptual. They describe meaning and intent, not database or software mechanics.


== Scope ==
== Scope ==
Line 15: Line 15:
* Page Schemas and forms
* Page Schemas and forms
* Editorial workflows
* Editorial workflows
* Interpretation of diagrams and documentation


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


== HeritageObject (HO) ==
== HeritageObject (HO) ==
Line 22: Line 23:
=== Definition ===
=== Definition ===


A '''HeritageObject (HO)''' represents a historical, conceptual, or material entity that is relevant to the research subject and has meaning in its own right, independent of how it is documented.
A '''HeritageObject (HO)''' represents a historical, conceptual, or material entity that is the subject of study.


It answers the question:
It answers the question:
Line 33: Line 34:
* A building
* A building
* A historically meaningful place (e.g. “Historical Ostend”)
* A historically meaningful place (e.g. “Historical Ostend”)
* A functional or conceptual component of a larger entity (e.g. “Medical practice in the sanatorium”)
* A functional or conceptual part of a larger entity (e.g. “Medical practice in a sanatorium”)


=== What a HeritageObject is not ===
=== What a HeritageObject is not ===
Line 42: Line 43:
* Not an organization
* Not an organization
* Not a research chapter
* Not a research chapter
* Not a database record
* Not a technical database record


=== Structural behavior ===
=== Structural behavior ===
Line 58: Line 59:
** Medical practice
** Medical practice


This structure replaces former notions of object sets or collections.
This structure replaces earlier notions of object sets or collections.
 
=== Relationship to Digital Assets ===
 
A HeritageObject:
* May be linked to multiple DigitalAssets
* May designate one DigitalAsset as the '''preferred''' representation
 
Multiplicity and representational choice are managed at the HeritageObject level.


=== Purpose ===
=== Purpose ===


HeritageObject is the central anchor of the model.   
HeritageObject is the central conceptual anchor of the model.   
All other entities ultimately relate to one or more HeritageObjects.
All other entities ultimately relate to one or more HeritageObjects.


Line 69: Line 78:
=== Definition ===
=== Definition ===


A '''DigitalAsset (DA)''' represents a curated, semantic representation of something, usually a HeritageObject or part of it.
A '''DigitalAsset (DA)''' represents the extended metadata and interpretation of '''exactly one''' digital file.


It answers the question:
It answers the question:
: ''“What digital material do we have that represents or documents something?”''
: ''“How do we interpret and describe this specific digital file?”''
 
A DigitalAsset can be understood as the human, research-oriented layer that gives meaning to a file.
 
=== Core principle ===
 
'''One DigitalAsset corresponds to exactly one File.'''
 
There is no grouping of multiple files inside a single DigitalAsset.


=== Examples ===
=== Examples ===


A DigitalAsset may represent:
A DigitalAsset may represent:
* A photograph (as a concept)
* A photograph file and its interpretation
* A scan of a document
* A scanned document file
* A map
* An OCR-generated PDF file
* A plan or drawing
* A cropped or processed derivative of another file
* A group of related digital derivatives


=== What a DigitalAsset is not ===
Each of these is a separate DigitalAsset if it is a separate file.
 
=== Relationship to Files ===
 
A DigitalAsset:
* Always references exactly one File
* Does not manage file storage
* Does not replace MediaWiki file handling


A DigitalAsset is:
Files are managed entirely by MediaWiki.
* Not a file
DigitalAssets describe and interpret them.
* Not a HeritageObject
* Not public-facing content by default


=== Relationship to files ===
=== Recursive behavior ===


A DigitalAsset may reference:
DigitalAssets are '''recursive'''.
* One or more files in the File: namespace
* Multiple formats or derivatives of the same material


Example:
A DigitalAsset may:
: One DigitalAsset → TIFF master + JPG derivative + OCR PDF
* Have a parent DigitalAsset (e.g. original → derivative)
* Have zero or more child DigitalAssets


Files may change over time while the DigitalAsset remains stable.
Recursion is used to model:
* Variants
* Derivatives
* Processing steps
* Interpretative lineage


=== Structural behavior ===
=== Relationship to HeritageObjects ===


A DigitalAsset:
A DigitalAsset:
* May have a parent DigitalAsset (derivative relationship)
* Is linked to one or more HeritageObjects
* May be linked to one or more HeritageObjects
* Always attaches to the most specific relevant HeritageObject
* Is attached to the most specific relevant HeritageObject
 
A HeritageObject may reference many DigitalAssets, but each DigitalAsset interprets only one file.
 
=== What a DigitalAsset is not ===
 
A DigitalAsset is:
* Not a file
* Not a container of multiple files
* Not a public-facing object by default
* Not a historical object itself


=== Purpose ===
=== Purpose ===
Line 112: Line 145:
DigitalAssets exist to:
DigitalAssets exist to:
* Separate meaning from storage
* Separate meaning from storage
* Group files meaningfully
* Provide rich, research-oriented metadata
* Support derivatives and versions
* Record provenance, role, and certainty
* Manage publication decisions
* Support controlled selection of representations
* Document provenance
 
== File (External System Entity) ==
 
=== Definition ===
 
A '''File''' is a physical digital object managed by MediaWiki.
 
Examples include:
* Image files
* Scanned documents
* PDFs
* Other uploaded media
 
=== Modeling status ===
 
Files are:
* Not owned by the data model
* Not defined conceptually within the research domain
* Included in diagrams only as external reference entities
 
File lifecycle, storage, and technical metadata are fully managed by MediaWiki.
 
=== Relationship to Digital Assets ===
 
Each File:
* Is referenced by exactly one DigitalAsset
* Has meaning in the project only through its DigitalAsset
 
Files are storage.
DigitalAssets are interpretation.


== Actor (Historical Person) ==
== Actor (Historical Person) ==
Line 124: Line 186:


It answers the question:
It answers the question:
: ''“Who was involved in this historically?”''
: ''“Who was involved historically?”''
 
=== Examples ===
 
Actors may include:
* Doctors
* Directors
* Religious figures
* Other identifiable historical individuals


=== What an Actor is not ===
=== What an Actor is not ===
Line 146: Line 200:
* Play roles in relation to HeritageObjects
* Play roles in relation to HeritageObjects
* Belong to Organizations
* Belong to Organizations
* Have relationships with other Actors (e.g. family, succession)
* Have relationships with other Actors


All such relationships are explicitly described and qualified by:
All such relationships are qualified by:
* Role
* Role
* Certainty
* Certainty
Line 154: Line 208:
=== Purpose ===
=== Purpose ===


Actors model historical agency, responsibility, authorship, and influence.
Actors model historical agency, responsibility, and influence.


== Organization ==
== Organization ==
Line 162: Line 216:
An '''Organization''' represents a historical collective actor.
An '''Organization''' represents a historical collective actor.


It answers the question:
Examples include:
: ''“Which institution or group acted as a unit in history?”''
 
=== Examples ===
 
Organizations may include:
* Religious congregations
* Religious congregations
* Institutions
* Associations
* Associations
* Institutions
* Managing bodies
* Managing bodies of sanatoria


=== What an Organization is not ===
=== What an Organization is not ===
Line 179: Line 228:
* Not a HeritageObject
* Not a HeritageObject
* Not a MediaWiki group
* Not a MediaWiki group
=== Relationships ===
An Organization may:
* Be related to HeritageObjects (e.g. ownership, management)
* Have members (Actors)
* Play roles over time


=== Purpose ===
=== Purpose ===
Line 200: Line 242:
: ''“In which phase or thematic period does this belong in the research story?”''
: ''“In which phase or thematic period does this belong in the research story?”''


=== Examples ===
=== Characteristics ===
 
ResearchChapters may include:
* Initial ideas and congresses
* Berck-sur-Mer experiments
* First Belgian coastal sanatoria
* Delcroix family generations
 
=== What a ResearchChapter is not ===


A ResearchChapter is:
A ResearchChapter:
* Not merely a date range
* Is not merely a date range
* Not a HeritageObject
* Reflects interpretation and structure
* Not a place
* May overlap with other chapters


=== Relationships ===
=== Relationships ===
Line 222: Line 256:
=== Purpose ===
=== Purpose ===


ResearchChapters model interpretation and narrative structure rather than historical reality itself.
ResearchChapters model narrative and interpretative structure rather than historical reality itself.
 
== Place (Modeling Rule) ==
 
=== Definition ===
 
A '''Place''' is modeled explicitly only when it is itself an object of historical study.
 
=== Rule ===
 
* Historically meaningful places → modeled as HeritageObjects
* Pure geographic information → modeled as attributes
 
Example:
* “Historical Ostend” → HeritageObject
* “City: Ostend” → attribute
 
=== Purpose ===
 
This allows places to:
* Have DigitalAssets (maps, plans)
* Evolve historically
* Participate in research chapters


== Certainty ==
== Certainty ==
Line 250: Line 262:
=== Definition ===
=== Definition ===


'''Certainty''' represents the degree of confidence in an assertion.
'''Certainty''' expresses the degree of confidence in an assertion.


It answers the question:
It answers the question:
Line 264: Line 276:
* Interpretations
* Interpretations


=== What Certainty is not ===
=== Important note ===


Certainty is:
Certainty is:
* Not a property of an entity itself
* Not a property of an entity itself
* Not absolute truth
* Always attached to a statement or relationship


=== Purpose ===
=== Purpose ===
Line 276: Line 288:
== Status ==
== Status ==


This document is a working conceptual glossary.
This document defines the current, agreed-upon conceptual meaning of the entities.


The ER model should not be finalized until these definitions are accepted and understood.
The ER model and all implementation work must conform to these definitions.

Revision as of 17:57, 19 January 2026

Data Model – Entity Definitions

This page defines the principal entities used in the 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 are conceptual. They describe meaning and intent, not database or software mechanics.

Scope

These definitions apply to:

  • Conceptual ER modeling
  • Future Cargo table design
  • Page Schemas and forms
  • Editorial workflows
  • Interpretation of diagrams and documentation

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

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 historically meaningful place (e.g. “Historical Ostend”)
  • A functional or conceptual part of a larger entity (e.g. “Medical practice in a sanatorium”)

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, for example:

  • Sanatorium Ostend
    • External architecture
    • Internal organization
    • Medical practice

This structure replaces earlier notions of object sets or collections.

Relationship to Digital Assets

A HeritageObject:

  • May be linked to multiple DigitalAssets
  • May designate one DigitalAsset as the preferred representation

Multiplicity and representational choice are managed at the HeritageObject level.

Purpose

HeritageObject is the central conceptual anchor of the model. All other entities ultimately relate to one or more HeritageObjects.

DigitalAsset (DA)

Definition

A DigitalAsset (DA) represents the extended metadata and interpretation of exactly one digital file.

It answers the question:

“How do we interpret and describe this specific digital file?”

A DigitalAsset can be understood as the human, research-oriented layer that gives meaning to a file.

Core principle

One DigitalAsset corresponds to exactly one File.

There is no grouping of multiple files inside a single DigitalAsset.

Examples

A DigitalAsset may represent:

  • A photograph file and its interpretation
  • A scanned document file
  • An OCR-generated PDF file
  • A cropped or processed derivative of another file

Each of these is a separate DigitalAsset if it is a separate file.

Relationship to Files

A DigitalAsset:

  • Always references exactly one File
  • Does not manage file storage
  • Does not replace MediaWiki file handling

Files are managed entirely by MediaWiki. DigitalAssets describe and interpret them.

Recursive behavior

DigitalAssets are recursive.

A DigitalAsset may:

  • Have a parent DigitalAsset (e.g. original → derivative)
  • Have zero or more child DigitalAssets

Recursion is used to model:

  • Variants
  • Derivatives
  • Processing steps
  • Interpretative lineage

Relationship to HeritageObjects

A DigitalAsset:

  • Is linked to one or more HeritageObjects
  • Always attaches to the most specific relevant HeritageObject

A HeritageObject may reference many DigitalAssets, but each DigitalAsset interprets only one file.

What a DigitalAsset is not

A DigitalAsset is:

  • Not a file
  • Not a container of multiple files
  • Not a public-facing object by default
  • Not a historical object itself

Purpose

DigitalAssets exist to:

  • Separate meaning from storage
  • Provide rich, research-oriented metadata
  • Record provenance, role, and certainty
  • Support controlled selection of representations

File (External System Entity)

Definition

A File is a physical digital object managed by MediaWiki.

Examples include:

  • Image files
  • Scanned documents
  • PDFs
  • Other uploaded media

Modeling status

Files are:

  • Not owned by the data model
  • Not defined conceptually within the research domain
  • Included in diagrams only as external reference entities

File lifecycle, storage, and technical metadata are fully managed by MediaWiki.

Relationship to Digital Assets

Each File:

  • Is referenced by exactly one DigitalAsset
  • Has meaning in the project only through its DigitalAsset

Files are storage. DigitalAssets are interpretation.

Actor (Historical Person)

Definition

An Actor represents a historical person involved in the subject matter of the research.

It answers the question:

“Who was involved historically?”

What an Actor is not

An Actor is:

  • Not a MediaWiki user account
  • Not a HeritageObject
  • Not an organization

Relationships

An Actor may:

  • Play roles in relation to HeritageObjects
  • Belong to Organizations
  • Have relationships with other Actors

All such relationships are qualified by:

  • Role
  • Certainty

Purpose

Actors model historical agency, responsibility, and influence.

Organization

Definition

An Organization represents a historical collective actor.

Examples include:

  • Religious congregations
  • Institutions
  • Associations
  • Managing bodies

What an Organization is not

An Organization is:

  • Not a person
  • Not a HeritageObject
  • Not a MediaWiki group

Purpose

Organizations allow modeling of institutional continuity and collective action.

ResearchChapter (or Period)

Definition

A ResearchChapter represents a conceptual or narrative unit of the research.

It answers the question:

“In which phase or thematic period does this belong in the research story?”

Characteristics

A ResearchChapter:

  • Is not merely a date range
  • Reflects interpretation and structure
  • May overlap with other chapters

Relationships

  • A ResearchChapter may include multiple HeritageObjects
  • A HeritageObject may belong to multiple ResearchChapters

Purpose

ResearchChapters model narrative and interpretative structure rather than historical reality itself.

Certainty

Definition

Certainty expresses the degree of confidence in an assertion.

It answers the question:

“How sure are we about this claim?”

Application

Certainty qualifies:

  • Relationships
  • Roles
  • Attributions
  • Dating
  • Interpretations

Important note

Certainty is:

  • Not a property of an entity itself
  • Always attached to a statement or relationship

Purpose

Certainty makes interpretation explicit and avoids false precision.

Status

This document defines the current, agreed-upon conceptual meaning of the entities.

The ER model and all implementation work must conform to these definitions.

Retrieved from "https://mwiki.costasano.club/index.php?title=ICT:Data_Model_Entity_definitions&oldid=114"