Jump to content

Research:Data Model Overview

From Costa Sano MediaWiki

Data Model Overview

This page explains, in plain language, how information is organized in the Costasano Heritage Database.

It is intended for:

  • club members
  • contributors
  • reviewers
  • non-technical readers

No technical knowledge is required.

The goal is simply to understand:

What kinds of things do we describe, and how do they relate to each other?


Purpose

The database helps us:

  • describe historical objects
  • record people and organizations
  • attach documents and photographs
  • organize research into chapters
  • keep everything clearly connected

It is essentially a structured way of answering:

  • What are we studying?
  • Who was involved?
  • Where did it happen?
  • Which sources document it?
  • How do we tell the story?


The main concepts

The system uses a small number of clearly defined concepts.


HeritageObject

The thing we study.

Examples:

  • the sanatorium
  • a building
  • a room
  • a document
  • a historically meaningful place

This is usually the starting point of research.


Person

An individual involved historically.

Examples:

  • directors
  • sisters
  • architects
  • patients


Organization

A collective body acting with responsibility.

Examples:

  • congregations
  • institutions
  • companies
  • associations


Place

A geographical location.

Examples:

  • a city
  • a building
  • a site
  • a region

Places describe where things are located.

They are not actors.


DigitalAsset

A digital source that documents something.

Examples:

  • a photograph
  • a scanned document
  • a letter
  • a newspaper article
  • a PDF

DigitalAssets give meaning to files and serve as research sources.


File

The physical stored file in the system.

Files provide storage only.

They gain research meaning only through DigitalAssets.


ResearchChapter

A chapter in the research narrative.

Chapters help structure interpretation and storytelling.


How these concepts work together

In simple terms:

  • HeritageObjects are documented by DigitalAssets
  • DigitalAssets are stored as Files
  • Persons and Organizations are linked to HeritageObjects
  • Places describe where things are located
  • ResearchChapters organize the story

This keeps:

  • meaning
  • sources
  • and structure

clearly separated.


Hierarchies (recursive structures)

Some things can contain smaller things of the same kind.

For example:

  • a building contains rooms
  • a chapter contains subchapters
  • a region contains cities

This allows us to describe complex structures naturally.

(See: ICT:Recursive Structures Explained)


Identifiers and numbering

DigitalAssets and some other entities receive automatic identifiers such as:

 CH03-ROM-0007

These identifiers:

  • ensure uniqueness
  • make items easy to find
  • are generated automatically

Files use the same identifier as their DigitalAsset.

(See: ICT:Numbering and Identifier Policy)


What contributors need to know

Contributors do NOT need to worry about technical details.

They only need to:

  • enter clear information
  • choose the correct entities
  • upload files with the suggested names

The system handles numbering and organization automatically.


Next steps

The technical implementation (database structure, forms, and automation) will be prepared separately by the system maintainer.

Contributors only need to review:

  • whether the concepts make sense
  • whether anything important is missing
  • whether the terminology is clear

Feedback is welcome.


Status

Conceptual overview for contributors – Version 4.0