https://mwiki.costasano.club/index.php?action=history&feed=atom&title=ICT%3AMediaWiki_CleanUp_Procedure 2026-07-22T23:27:15Z Revision history for this page on the wiki MediaWiki 1.45.1 https://mwiki.costasano.club/index.php?title=ICT:MediaWiki_CleanUp_Procedure&diff=214&oldid=prev 2026-01-29T13:19:12Z

<p>Created page with &quot;= MediaWiki Cleanup &amp; Fresh Start Procedure (Cargo + Page Forms) = == Purpose == This page describes the safe procedure to remove experimental / test work before rebuilding the Costasano Heritage system using: * Cargo (data storage) * Page Forms (data entry) * Templates (schema definition) We intentionally avoid Page Schemas because it does not support: * enforced namespaces * automatic page naming * strict workflow control A clean reset prevents schema conflicts, du...&quot;</p> <p><b>New page</b></p><div>= MediaWiki Cleanup &amp; Fresh Start Procedure (Cargo + Page Forms) =<br /> <br /> == Purpose ==<br /> This page describes the safe procedure to remove experimental / test work<br /> before rebuilding the Costasano Heritage system using:<br /> <br /> * Cargo (data storage)<br /> * Page Forms (data entry)<br /> * Templates (schema definition)<br /> <br /> We intentionally avoid Page Schemas because it does not support:<br /> * enforced namespaces<br /> * automatic page naming<br /> * strict workflow control<br /> <br /> A clean reset prevents schema conflicts, duplicate forms, and long-term maintenance issues.<br /> <br /> ----<br /> <br /> == Guiding principles ==<br /> <br /> * Keep the system predictable and explicit<br /> * One template = one Cargo table<br /> * One form = one data entry workflow<br /> * No legacy or experimental artifacts in production namespaces<br /> * Delete test content aggressively<br /> <br /> If something is not part of the real system → remove it.<br /> <br /> ----<br /> <br /> == Step 0 – Backup (mandatory) ==<br /> <br /> Before deleting anything:<br /> <br /> Either:<br /> * Database dump (mysqldump), or<br /> * Special:Export XML backup<br /> <br /> Never skip this step.<br /> <br /> ----<br /> <br /> == Step 1 – Remove Page Schemas artifacts ==<br /> <br /> We no longer use Page Schemas.<br /> <br /> Delete:<br /> <br /> * Schema:* pages<br /> * Forms generated by Page Schemas<br /> * Templates generated by Page Schemas<br /> * Any helper categories or leftover scaffolding<br /> <br /> If unsure, temporarily rename with &quot;_old&quot; first.<br /> <br /> Example:<br /> Template:DigitalAsset → Template:DigitalAsset_old<br /> <br /> ----<br /> <br /> == Step 2 – Delete test content pages ==<br /> <br /> Remove all experimental pages:<br /> <br /> * DigitalAssets test pages<br /> * HeritageObjects test pages<br /> * dummy entities<br /> * sandbox objects<br /> <br /> Goal:<br /> System starts with ZERO content.<br /> <br /> This avoids mixing test data with production data later.<br /> <br /> ----<br /> <br /> == Step 3 – Delete test Forms and Templates ==<br /> <br /> Delete any temporary or experimental items:<br /> <br /> * Form:Test*<br /> * Template:Test*<br /> * old prototype templates<br /> * duplicate versions (v2, final, new, etc.)<br /> <br /> Keep names clean and canonical.<br /> <br /> Avoid:<br /> Template:DigitalAsset2<br /> Template:DigitalAsset_final<br /> Template:DigitalAsset_new<br /> <br /> Only keep:<br /> Template:DigitalAsset<br /> <br /> ----<br /> <br /> == Step 4 – Clean Cargo tables ==<br /> <br /> Cargo tables persist even if templates are deleted.<br /> <br /> Go to:<br /> Special:CargoTables<br /> <br /> Then:<br /> * delete test tables, or<br /> * recreate them later from clean templates<br /> <br /> This step is critical to avoid schema mismatches.<br /> <br /> ----<br /> <br /> == Step 5 – Delete test uploaded files ==<br /> <br /> Go to:<br /> Special:ListFiles<br /> <br /> Delete:<br /> * dummy images<br /> * sample PDFs<br /> * temporary uploads<br /> <br /> Reasons:<br /> * reduces clutter<br /> * faster backups<br /> * prevents test assets appearing in production<br /> <br /> ----<br /> <br /> == Step 6 – (Optional) Disable Page Schemas extension ==<br /> <br /> If no longer needed, disable it in LocalSettings.php:<br /> <br /> wfLoadExtension( &#039;PageSchemas&#039; );<br /> <br /> Comment out or remove.<br /> <br /> This prevents accidental reuse.<br /> <br /> ----<br /> <br /> == Rebuild order (recommended workflow) ==<br /> <br /> After cleanup, rebuild in small steps.<br /> <br /> === 1. Create templates ===<br /> Each table gets exactly one template using:<br /> <br /> #cargo_store<br /> <br /> === 2. Create Cargo tables ===<br /> Special:CargoTables → Recreate data<br /> <br /> === 3. Create Page Forms ===<br /> * set target namespace<br /> * set page name formula<br /> * hide title<br /> <br /> === 4. Test one full workflow ===<br /> Create → save → query<br /> <br /> Only then add more tables/forms.<br /> <br /> Do not build everything at once.<br /> <br /> ----<br /> <br /> == Architectural rules ==<br /> <br /> === Rule 1 – One table, one template ===<br /> Each DBML table maps to exactly one template.<br /> <br /> === Rule 2 – Use namespaces strictly ===<br /> Example:<br /> * DA: for DigitalAssets<br /> * HO: for HeritageObjects<br /> <br /> Forms must enforce namespaces automatically.<br /> <br /> === Rule 3 – Prefer Page fields over raw IDs ===<br /> Use:<br /> input type=page<br /> <br /> instead of plain text.<br /> <br /> Benefits:<br /> * autocomplete<br /> * fewer errors<br /> * clickable links<br /> <br /> === Rule 4 – Use junction tables for many-to-many ===<br /> Never embed lists manually.<br /> Always create explicit Cargo junction tables.<br /> <br /> ----<br /> <br /> == Final note ==<br /> <br /> Prototype → learn → delete → rebuild clean.<br /> <br /> A fresh start is faster and safer than trying to fix experimental scaffolding.<br /> <br /> Clarity beats cleverness.<br /> Explicit beats automatic magic.</div>

Mngr