Namespaces and Page Types

This page explains how the wiki is organized.

It describes the different namespaces used in the project and what they are for.

Understanding namespaces helps contributors know:

where to create pages
what kind of content belongs where
how research material differs from documentation

What is a namespace?

A namespace is simply a prefix in front of a page name.

Examples:

HO:Sanatorium Ostend
DA:Facade photograph 1923
Research:Procedure – DigitalAsset
ICT:Cargo setup notes

The prefix tells you what kind of page it is.

Think of namespaces like folders or sections in a library.

They keep different types of information separated and organized.

Why do we use namespaces?

The project contains different kinds of content:

research data
sources
public writing
documentation
technical notes

Mixing everything together would quickly become confusing.

Namespaces allow us to:

keep research material separate from technical documentation
make page purposes immediately clear
simplify searching and browsing
prevent accidental editing of system pages

Overview of namespaces

Main namespace (no prefix)

Example: Sanatorium Ostend

Purpose

Public and narrative content.

This is where:

articles
public pages
summaries
story-driven texts
exhibition-style pages

belong.

These pages are readable by a broad audience.

They may:

include images
cite sources (DigitalAssets)
present conclusions

They are the presentation layer of the project.

Think of it as

The published result.

HO: (HeritageObjects)

Example: HO:Sanatorium Ostend

Purpose

Conceptual research subjects.

HeritageObjects represent:

buildings
places
documents
objects
functional or conceptual units

These pages answer:

"What is the thing we are studying?"

They contain:

descriptions
structure (parent/child)
links to sources
links to people and organizations

Think of it as

The subjects of research.

DA: (DigitalAssets)

Example: DA:Facade photograph 1923

Purpose

Sources and evidence.

Each DigitalAsset represents:

exactly one file
one interpretable source

Examples:

photograph
scan
newspaper article
letter
archival record

DigitalAssets:

describe the file
store metadata
record provenance
provide citation information
link to the subjects they document

Public pages should cite DigitalAssets as sources.

Think of it as

The evidence.

Research:

Example: Research:Procedure – DigitalAsset

Purpose

Research and editorial guidance.

These pages explain:

how to work with the system
procedures and workflows
editorial rules
citation practices
modeling principles
project philosophy

They are written for:

researchers
contributors
volunteers

They help explain not only how to fill in forms, but why.

Think of it as

The research handbook.

ICT:

Example: ICT:DBML schema

Purpose

Technical and administrative documentation.

These pages contain:

database design
schemas
system configuration
bots and scripts
installation notes
maintenance procedures

They are intended for:

administrators
system maintainers
technical staff

Most contributors will never need to edit these pages.

Think of it as

The technical manual.

File: (MediaWiki built-in)

Example: File:Facade_1923.jpg

Purpose

Physical storage of uploaded files.

Files are:

images
scans
PDFs
audio/video

Files themselves contain no research meaning.

They gain meaning only through DigitalAssets.

Contributors should:

upload files
then create a DigitalAsset describing them

Do not treat File pages as research pages.

Think of it as

Storage only.

How these parts work together

The system follows this logic:

File → DigitalAsset → HeritageObject/Person/Organization → Public page

Meaning:

Files store
DigitalAssets interpret
Research entities give meaning
Public pages present the story

Each namespace supports one step in this chain.

Practical advice

When creating content, ask:

If you are writing a public article → Main namespace If you describe a historical subject → HO: If you document a source or file → DA: If you explain how to work → Research: If you configure the system → ICT:

If unsure, ask before creating pages in a new location.

Summary

Namespaces are simply organization tools.

They help keep:

research
sources
presentation
documentation
technical setup

clearly separated.

This makes the system easier to understand, maintain, and use.

Each page type has a purpose. Choosing the correct namespace keeps the project coherent.