https://mwiki.costasano.club/index.php?action=history&feed=atom&title=ICT%3AFinal_Chapter_Architecture 2026-04-17T16:21:47Z Revision history for this page on the wiki MediaWiki 1.45.1 https://mwiki.costasano.club/index.php?title=ICT:Final_Chapter_Architecture&diff=1594&oldid=prev 2026-03-31T13:24:56Z

<p>Created page with &quot;= 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 — the...&quot;</p> <p><b>New page</b></p><div>= Final Chapter Architecture =<br /> <br /> This page documents the final, endorsed structure for CHAPTER, PLACE, and ORGANISATION within the research platform. <br /> It reflects the architectural simplification reached after analysis and Excel validation.<br /> <br /> == 1. CHAPTER Structure (Flat, Non‑Recursive) ==<br /> <br /> The CHAPTER entity is now:<br /> <br /> * Flat (no recursion)<br /> * Non‑hierarchical<br /> * Narrative-only<br /> * Max. 3 characters<br /> * Two families:<br /> ** Txx — time‑based narrative chapters<br /> ** Xxx — thematic or contextual chapters<br /> <br /> There are no subchapters such as T00a, T00b, etc. <br /> All narrative subdivision is handled by PLACE and ORGANISATION.<br /> <br /> === Examples ===<br /> <br /> T00 – Before the main period<br /> T01 – Early developments<br /> T02 – First migrations<br /> T06 – WW2<br /> T07 – Post‑war period<br /> <br /> X00 – Methodology<br /> X01 – Sources<br /> X02 – Transport &amp; technology<br /> X03 – Family context<br /> <br /> CHAPTER codes remain stable and short to keep asset numbering clean.<br /> <br /> == 2. PLACE Structure (Recursive, 6‑Character Codes) ==<br /> <br /> PLACE is the primary engine for narrative subdivision. <br /> It remains:<br /> <br /> * Recursive (multi‑level hierarchy)<br /> * Geographical<br /> * User‑defined<br /> * Using full 6‑character codes<br /> * The natural source of “subchapter‑like” separation<br /> <br /> PLACE captures geographical storylines such as:<br /> <br /> * WW2 in Ostende<br /> * Children in Alton<br /> * Children in Bristol<br /> * Sanas in Italy and Germany<br /> <br /> === Example PLACE Hierarchy ===<br /> <br /> EUROPE<br /> UK<br /> ALTON<br /> BRIST<br /> BELGIUM<br /> OSTEND<br /> ITALY<br /> GERMANY<br /> <br /> PLACE codes (6 chars) are used directly in asset numbering.<br /> <br /> == 3. ORGANISATION Structure (Recursive, 6‑Character Codes) ==<br /> <br /> ORGANISATION is also recursive and captures institutional storylines.<br /> <br /> It remains:<br /> <br /> * Recursive<br /> * User‑defined<br /> * 6‑character codes<br /> * Parallel to PLACE in structure and purpose<br /> <br /> === Example ORGANISATION Hierarchy ===<br /> <br /> SANAS<br /> SANAS-IT<br /> SANAS-DE<br /> <br /> This allows assets to be grouped by institutional context.<br /> <br /> == 4. Asset Numbering (Clean, Stable) ==<br /> <br /> Asset numbering uses:<br /> <br /> &lt;Chapter.Code&gt; – &lt;Place.Code OR Organisation.Code&gt; – &lt;Counter(5)&gt;<br /> <br /> Because CHAPTER is flat and fixed-length, numbering remains clean and aligned.<br /> <br /> === Examples ===<br /> <br /> T06-OSTEND-00012<br /> T00-ALTON-00013<br /> T00-BRIST-00014<br /> T00-UKPRE-00015<br /> <br /> This structure automatically groups assets by:<br /> <br /> * Chapter (narrative period)<br /> * Place (geographical storyline)<br /> * Organisation (institutional storyline)<br /> <br /> No subchapter codes are needed.<br /> <br /> == 5. Why Subchapters Are No Longer Needed ==<br /> <br /> Subchapters were originally used to subdivide narrative chapters (e.g., CH06a, CH00b). <br /> After analysis, it became clear that:<br /> <br /> * These subdivisions were geographical or institutional, not structural.<br /> * PLACE and ORGANISATION already provide natural, recursive subdivision.<br /> * Adding subchapter codes would pollute asset numbering.<br /> * CHAPTER should remain a top‑level narrative container only.<br /> <br /> Therefore:<br /> <br /> &#039;&#039;&#039;Subchapters are now expressed through PLACE and ORGANISATION, not through CHAPTER.&#039;&#039;&#039;<br /> <br /> == 6. Benefits of the Final Architecture ==<br /> <br /> * Clean, stable CHAPTER codes<br /> * Powerful recursive PLACE and ORGANISATION hierarchies<br /> * Natural narrative subdivision without extra fields<br /> * Clean asset numbering<br /> * Strong filtering for publications (Chapter + Place + Organisation + Keywords)<br /> * Easy to explain to club members<br /> * Successor‑friendly and future‑proof<br /> <br /> == 7. Status ==<br /> <br /> This structure has been validated through Excel analysis and is ready for presentation to the club members for endorsement. <br /> Once approved, it becomes the final, stable architecture for all future research, publications, and digital heritage workflows.</div>

Mngr