Jump to content

ICT:Data Model Entity definitions: Difference between revisions

From Costa Sano MediaWiki
Mngr (talk | contribs)
Bots, Bureaucrats, club, ict, Interface administrators, research, Suppressors, Administrators
1,027 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
 
(One intermediate revision by the same user not shown)
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 conceptual entities of the project.
 
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 responsibility, not database tables, Cargo structures, or software mechanics.


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 ==
== Scope ==
Line 12: Line 15:


* Conceptual ER modeling
* Conceptual ER modeling
* Future Cargo table design
* Cargo or database schemas
* Page Schemas and forms
* Page Schemas and forms
* Editorial workflows
* Editorial workflows
* Interpretation of diagrams and documentation
If an entity definition is unclear or disputed, implementation must be postponed.
== Conceptual overview ==
The model distinguishes clearly between:
* '''Storage''' → Files
* '''Interpretation of files''' → DigitalAssets
* '''Subjects of research''' → HeritageObjects, Persons, Organizations
* '''Narrative structure''' → ResearchChapters
The fundamental semantic flow is:
File → DigitalAsset → Research Entity
DigitalAssets provide meaning to files.
Research entities provide historical meaning to DigitalAssets.
= Core Research Entities =


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


== HeritageObject (HO) ==
== HeritageObject (HO) ==
Line 22: Line 50:
=== 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 29: Line 57:
=== Examples ===
=== Examples ===


A HeritageObject may represent:
* A sanatorium
* A sanatorium
* A building
* A building
* A historically meaningful place (e.g. “Historical Ostend”)
* A historically meaningful place
* A functional or conceptual component of a larger entity (e.g. “Medical practice in the sanatorium”)
* A document or register
* A functional or conceptual part of a larger entity (e.g. “Medical practice”)


=== What a HeritageObject is not ===
=== What a HeritageObject is not ===


A HeritageObject is:
A HeritageObject is:
* Not a digital file
* Not a digital file
* Not a person
* Not a person
* 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 49: Line 78:


Each HeritageObject may:
Each HeritageObject may:
* Have zero or one parent HeritageObject
* Have zero or one parent HeritageObject
* Have zero or more child HeritageObjects
* Have zero or more child HeritageObjects


This supports conceptual decomposition, for example:
This supports conceptual decomposition.
* Sanatorium Ostend
 
** External architecture
Example:
** Internal organization
 
* Sanatorium
** Architecture
** Equipment
** Medical practice
** Medical practice


This structure replaces former notions of object sets or collections.
=== Relationships ===
 
A HeritageObject may:
 
* Be documented by multiple DigitalAssets
* Be linked to Persons with roles
* Be linked to Organizations with roles
* Have Persons or Organizations as holders
* Be included in multiple ResearchChapters
* Be tagged with Keywords


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


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


== DigitalAsset (DA) ==
== Person ==


=== Definition ===
=== Definition ===


A '''DigitalAsset (DA)''' represents a curated, semantic representation of something, usually a HeritageObject or part of it.
A '''Person''' represents a historical individual with agency.


It answers the question:
It answers the question:
: ''“What digital material do we have that represents or documents something?”''
: ''“Who was involved historically?”''


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


A DigitalAsset may represent:
* Sister Maria
* A photograph (as a concept)
* A director
* A scan of a document
* An architect
* A map
* A patient
* A plan or drawing
* A shareholder
* A group of related digital derivatives
 
=== What a Person is not ===


=== What a DigitalAsset is not ===
A Person is:


A DigitalAsset is:
* Not a MediaWiki user
* Not a file
* Not a HeritageObject
* Not a HeritageObject
* Not public-facing content by default
* Not an organization


=== Relationship to files ===
=== Relationships ===


A DigitalAsset may reference:
A Person may:
* One or more files in the File: namespace
* Multiple formats or derivatives of the same material


Example:
* Play roles in relation to HeritageObjects
: One DigitalAsset → TIFF master + JPG derivative + OCR PDF
* Play roles in relation to Organizations
* Be documented by DigitalAssets (photos, documents, biographies)
* Act as a holder of HeritageObjects


Files may change over time while the DigitalAsset remains stable.
Roles belong to relationships, not to the Person entity itself.


=== Structural behavior ===
=== Purpose ===


A DigitalAsset:
Persons model historical agency, responsibility, and participation.
* May have a parent DigitalAsset (derivative relationship)
* May be linked to one or more HeritageObjects
* Is attached to the most specific relevant HeritageObject


=== Purpose ===


DigitalAssets exist to:
* Separate meaning from storage
* Group files meaningfully
* Support derivatives and versions
* Manage publication decisions
* Document provenance


== Actor (Historical Person) ==
== Organization ==


=== Definition ===
=== Definition ===


An '''Actor''' represents a historical person involved in the subject matter of the research.
An '''Organization''' represents a historical collective actor with institutional continuity.


It answers the question:
It answers the question:
: ''“Who was involved in this historically?”''
: ''“Which collective body acted or was responsible?”''


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


Actors may include:
* Religious congregations
* Doctors
* Companies
* Directors
* Institutions
* Religious figures
* Associations
* Other identifiable historical individuals
* Managing bodies
 
=== What an Organization is not ===


=== What an Actor is not ===
An Organization is:


An Actor is:
* Not a person
* Not a MediaWiki user account
* Not a HeritageObject
* Not a HeritageObject
* Not an organization
* Not a MediaWiki user group


=== Relationships ===
=== Relationships ===


An Actor may:
An Organization may:
 
* Play roles in relation to HeritageObjects
* Play roles in relation to HeritageObjects
* Belong to Organizations
* Have Persons playing roles within it
* Have relationships with other Actors (e.g. family, succession)
* Be documented by DigitalAssets (articles, reports, archival documents)
* Act as a holder of HeritageObjects
 
=== Purpose ===
 
Organizations model collective responsibility and institutional continuity.
 
 


All such relationships are explicitly described and qualified by:
= Digital Representation =
* Role
* Certainty


=== Purpose ===


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


== Organization ==
== DigitalAsset (DA) ==


=== Definition ===
=== Definition ===


An '''Organization''' represents a historical collective actor.
A '''DigitalAsset (DA)''' represents the research interpretation and extended metadata of '''exactly one''' digital file.


It answers the question:
It answers the question:
: ''“Which institution or group acted as a unit in history?”''
: ''“How do we interpret and describe this specific digital file as a source?”''
 
A DigitalAsset is the human, research-oriented 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 ===
=== Examples ===


Organizations may include:
* A photograph and its description
* Religious congregations
* A scanned document
* Associations
* An OCR transcription
* Institutions
* A cropped or processed derivative
* Managing bodies of sanatoria
* A newspaper article scan
* A portrait of a person
 
=== 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 (parent)
* Have multiple derived children
 
This models:
 
* variants
* processing steps
* derivatives
* provenance chains
 
=== Relationship to research entities ===
 
A DigitalAsset may document one or more:
 
* HeritageObjects
* Persons
* Organizations


=== What an Organization is not ===
DigitalAssets represent sources about research subjects.


An Organization is:
=== What a DigitalAsset is not ===
* Not a person
* Not a HeritageObject
* Not a MediaWiki group


=== Relationships ===
A DigitalAsset is:


An Organization may:
* Not a file
* Be related to HeritageObjects (e.g. ownership, management)
* Not a container of files
* Have members (Actors)
* Not a historical object itself
* Play roles over time
* Not merely technical metadata


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


Organizations allow modeling of institutional continuity and collective action.
DigitalAssets exist to:
 
* Separate meaning from storage
* Provide rich research metadata
* Record provenance
* Link sources to research subjects
 
 


== ResearchChapter (or Period) ==
== File (External System Entity) ==


=== Definition ===
=== Definition ===


A '''ResearchChapter''' represents a conceptual or narrative unit of the research.
A '''File''' is a physical digital object managed by MediaWiki.
 
Examples include:
 
* images
* scans
* PDFs
* audio or video files
 
=== Modeling status ===
 
Files are:
 
* Outside the conceptual research domain
* Managed entirely by MediaWiki
* Included only as external reference entities
 
Files provide storage only.
They gain research meaning only through a DigitalAsset.
 
 
 
= Research Structure =
 
 
 
== ResearchChapter ==
 
=== Definition ===
 
A '''ResearchChapter''' represents a conceptual or narrative unit of interpretation.


It answers the question:
It answers the question:
: ''“In which phase or thematic period does this belong in the research story?”''
: ''“Where does this belong in the research story?”''
 
=== Characteristics ===
 
A ResearchChapter:
 
* structures interpretation
* is not merely a date range
* may be thematic or chronological
 
=== Structural behavior ===


=== Examples ===
ResearchChapters are '''recursive'''.


ResearchChapters may include:
A Chapter may contain subchapters.
* Initial ideas and congresses
* Berck-sur-Mer experiments
* First Belgian coastal sanatoria
* Delcroix family generations


=== What a ResearchChapter is not ===
Top levels often represent time slices.
Lower levels often represent themes.


A ResearchChapter is:
Time is descriptive, not defining.
* Not merely a date range
* Not a HeritageObject
* Not a place


=== Relationships ===
=== Relationships ===


* A ResearchChapter may include multiple HeritageObjects
* A Chapter may include multiple HeritageObjects
* A HeritageObject may belong to multiple ResearchChapters
* A HeritageObject may belong to multiple Chapters


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


ResearchChapters model interpretation and narrative structure rather than historical reality itself.
ResearchChapters organize interpretation rather than historical reality itself.
 
 
 
= Supporting Concepts =
 
 
 
== Keywords ==
 
Keywords provide flexible thematic tagging.


== Place (Modeling Rule) ==
They support discovery but do not define structure.


=== Definition ===


A '''Place''' is modeled explicitly only when it is itself an object of historical study.


=== Rule ===
== Roles ==


* Historically meaningful places → modeled as HeritageObjects
Roles qualify relationships between entities.
* Pure geographic information → modeled as attributes


Example:
Examples:
* “Historical Ostend” → HeritageObject
* “City: Ostend” → attribute


=== Purpose ===
* creator
* owner
* restorer
* shareholder
* board member
* holder


This allows places to:
Roles are attributes of relationships, not of entities themselves.
* Have DigitalAssets (maps, plans)
* Evolve historically
* Participate in research chapters


== Certainty ==


=== Definition ===


'''Certainty''' represents the degree of confidence in an assertion.
== Certainty (future extension) ==


It answers the question:
Certainty expresses confidence in an assertion.
: ''“How sure are we about this claim?”''


=== Application ===
It qualifies statements such as:


Certainty qualifies:
* roles
* Relationships
* attributions
* Roles
* dates
* Attributions
* interpretations
* Dating
* Interpretations


=== What Certainty is not ===
Certainty is attached to relationships or claims, never to entities.


Certainty is:
This concept is reserved for later implementation.
* Not a property of an entity itself
* Not absolute truth


=== Purpose ===


Certainty makes interpretation explicit and avoids false precision.


== Status ==
== Status ==


This document is a working conceptual glossary.
This document defines the agreed conceptual meaning of the entities – Version 3.1.


The ER model should not be finalized until these definitions are accepted and understood.
All ER diagrams, DBML definitions, and technical implementations must conform to these definitions.

Latest revision as of 14:53, 23 January 2026

Data Model – Entity Definitions

This page defines the principal conceptual entities of the project.

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 responsibility, not database tables, Cargo structures, or software mechanics.


Scope

These definitions apply to:

  • Conceptual ER modeling
  • Cargo or database 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 distinguishes clearly between:

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

The fundamental semantic flow is:

File → DigitalAsset → Research Entity

DigitalAssets provide meaning to files. Research entities provide historical meaning to DigitalAssets.


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 sanatorium
  • A building
  • A historically meaningful place
  • A document or register
  • A functional or conceptual part of a larger entity (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.

Example:

  • Sanatorium
    • Architecture
    • Equipment
    • Medical practice

Relationships

A HeritageObject may:

  • Be documented by multiple DigitalAssets
  • Be linked to Persons with roles
  • Be linked to Organizations with roles
  • Have Persons or Organizations as holders
  • Be included in 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

  • Sister Maria
  • A director
  • An architect
  • A patient
  • A shareholder

What a Person is not

A Person is:

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

Relationships

A Person may:

  • Play roles in relation to HeritageObjects
  • Play roles in relation to Organizations
  • Be documented by DigitalAssets (photos, documents, biographies)
  • Act as a holder of HeritageObjects

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
  • Institutions
  • Associations
  • Managing bodies

What an Organization is not

An Organization is:

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

Relationships

An Organization may:

  • Play roles in relation to HeritageObjects
  • Have Persons playing roles within it
  • Be documented by DigitalAssets (articles, reports, archival documents)
  • Act as a holder of HeritageObjects

Purpose

Organizations model collective responsibility and institutional continuity.


Digital Representation

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 source?”

A DigitalAsset is the human, research-oriented 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 photograph and its description
  • A scanned document
  • An OCR transcription
  • A cropped or processed derivative
  • A newspaper article scan
  • A portrait of a person

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 (parent)
  • Have multiple derived children

This models:

  • variants
  • processing steps
  • derivatives
  • provenance chains

Relationship to research entities

A DigitalAsset may document one or more:

  • HeritageObjects
  • Persons
  • Organizations

DigitalAssets represent sources about research subjects.

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
  • Record provenance
  • Link sources to research subjects


File (External System Entity)

Definition

A File is a physical digital object managed by MediaWiki.

Examples include:

  • images
  • scans
  • PDFs
  • audio or video files

Modeling status

Files are:

  • Outside the conceptual research domain
  • Managed entirely by MediaWiki
  • Included only as external reference entities

Files provide storage only. They gain research meaning only through a DigitalAsset.


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

Structural behavior

ResearchChapters are recursive.

A Chapter may contain subchapters.

Top levels often represent time slices. Lower levels often represent themes.

Time is descriptive, not defining.

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 are attributes of relationships, not of entities themselves.


Certainty (future extension)

Certainty expresses confidence in an assertion.

It qualifies statements such as:

  • roles
  • attributions
  • dates
  • interpretations

Certainty is attached to relationships or claims, never to entities.

This concept is reserved for later implementation.


Status

This document defines the agreed conceptual meaning of the entities – Version 3.1.

All ER diagrams, DBML definitions, and technical implementations must conform to these definitions.

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