Final Chapter Architecture

This page documents the final, endorsed structure for CHAPTER, PLACE, and ORGANISATION within the research platform. It reflects the architectural simplification reached after analysis and Excel validation.

1. CHAPTER Structure (Flat, Non‑Recursive)

The CHAPTER entity is now:

Flat (no recursion)
Non‑hierarchical
Narrative-only
Max. 3 characters
Two families:
- Txx — time‑based narrative chapters
- Xxx — thematic or contextual chapters

There are no subchapters such as T00a, T00b, etc. All narrative subdivision is handled by PLACE and ORGANISATION.

Examples

T00 – Before the main period
T01 – Early developments
T02 – First migrations
T06 – WW2
T07 – Post‑war period

X00 – Methodology
X01 – Sources
X02 – Transport & technology
X03 – Family context

CHAPTER codes remain stable and short to keep asset numbering clean.

2. PLACE Structure (Recursive, 6‑Character Codes)

PLACE is the primary engine for narrative subdivision. It remains:

Recursive (multi‑level hierarchy)
Geographical
User‑defined
Using full 6‑character codes
The natural source of “subchapter‑like” separation

PLACE captures geographical storylines such as:

WW2 in Ostende
Children in Alton
Children in Bristol
Sanas in Italy and Germany

Example PLACE Hierarchy

EUROPE
  UK
    ALTON
    BRIST
  BELGIUM
    OSTEND
ITALY
GERMANY

PLACE codes (6 chars) are used directly in asset numbering.

3. ORGANISATION Structure (Recursive, 6‑Character Codes)

ORGANISATION is also recursive and captures institutional storylines.

It remains:

Recursive
User‑defined
6‑character codes
Parallel to PLACE in structure and purpose

Example ORGANISATION Hierarchy

SANAS
  SANAS-IT
  SANAS-DE

This allows assets to be grouped by institutional context.

4. Asset Numbering (Clean, Stable)

Asset numbering uses:

<Chapter.Code> – <Place.Code OR Organisation.Code> – <Counter(5)>

Because CHAPTER is flat and fixed-length, numbering remains clean and aligned.

Examples

T06-OSTEND-00012
T00-ALTON-00013
T00-BRIST-00014
T00-UKPRE-00015

This structure automatically groups assets by:

Chapter (narrative period)
Place (geographical storyline)
Organisation (institutional storyline)

No subchapter codes are needed.

5. Why Subchapters Are No Longer Needed

Subchapters were originally used to subdivide narrative chapters (e.g., CH06a, CH00b). After analysis, it became clear that:

These subdivisions were geographical or institutional, not structural.
PLACE and ORGANISATION already provide natural, recursive subdivision.
Adding subchapter codes would pollute asset numbering.
CHAPTER should remain a top‑level narrative container only.

Therefore:

Subchapters are now expressed through PLACE and ORGANISATION, not through CHAPTER.

6. Benefits of the Final Architecture

Clean, stable CHAPTER codes
Powerful recursive PLACE and ORGANISATION hierarchies
Natural narrative subdivision without extra fields
Clean asset numbering
Strong filtering for publications (Chapter + Place + Organisation + Keywords)
Easy to explain to club members
Successor‑friendly and future‑proof

7. Status

This structure has been validated through Excel analysis and is ready for presentation to the club members for endorsement. Once approved, it becomes the final, stable architecture for all future research, publications, and digital heritage workflows.