ICT:ContentTable: Difference between revisions
Appearance
No edit summary |
No edit summary |
||
| Line 40: | Line 40: | ||
|- | |- | ||
| [[ICT:VisualEditor-Admin]] | | [[ICT:VisualEditor-Admin]] | ||
| | | This page provides a one‑screen operational overview for administrators. It combines the essential health checks, the most common troubleshooting steps, and links to full documentation. | ||
|- | |- | ||
|} | |} | ||
Revision as of 20:39, 28 January 2026
| Page | Description |
|---|---|
| ICT:Architecture | This page describes the overall technical architecture of the MediaWiki installation used for heritage research and digital asset management. |
| ICT:Choosing MediaWiki | This page explains the rationale for choosing MediaWiki as the technical platform for this project, instead of Omeka-S or Zotero. It is intended for collaborators who are familiar with digital research tools but not with system architecture or MediaWiki extensions. The goal is to provide sufficient context to understand later design documents without requiring technical expertise. |
| ICT:Data Model Entity Definitions - v 3.2 | This page defines the principal conceptual entities used in the project’s data model. Its purpose is to establish a shared and explicit understanding of what each entity represents before any technical implementation is undertaken. These definitions describe meaning and responsibility, not database structure or software mechanics. |
| ICT:Data Model - v3.2 - certainties | How we deal with the treatment of uncertainty (Certainty) |
| ICT:Data Model and Media Architecture | This page documents the architectural decisions and working principles used for structuring data, relationships, and digital media in this MediaWiki installation. It reflects conclusions reached during the design phase and serves as a reference for future development and maintenance. |
| ICT:Debugging | Troubleshooting Philosophy for MediaWiki & Multi‑Layer Systems |
| ICT:Policy | This page defines rules, responsibilities, and constraints governing the system. It is normative and must be followed. |
| ICT:Rewrite Philosophy | This page explains the philosophy behind the Apache rewrite rules used on this server, so future administrators understand why the rules exist and what they protect. |
| ICT:Technical Terms for Collaborators | This page explains a small number of technical terms that appear in the project documentation. It is intended for collaborators who are not system architects and who are not expected to configure or maintain the system. The purpose of this page is to support understanding, not to teach implementation. |
| ICT:The correct Desing Philosophy | This page documents the design philosophy and lessons learned that guide the development of this MediaWiki-based research system. It exists to make implicit experience explicit, and to serve as a long-term guardrail against common project failure modes. |
| ICT:Vhost - RProxy settings | This page documents how requests flow from IIS → Apache → MediaWiki, and what must be configured to keep the wiki stable, predictable, and successor‑friendly. |
| ICT:VisualEditor | This page provides a short operational overview of how VisualEditor works on this MediaWiki installation. It is intended for day‑to‑day administrators who need a quick reference without reading the full technical documentation. |
| ICT:VisualEditor-Admin | This page provides a one‑screen operational overview for administrators. It combines the essential health checks, the most common troubleshooting steps, and links to full documentation. |
- ICT:Account protection
- ICT:Adding a New Entity/Table
- ICT:AlmaLinux update procedure
- ICT:Architecture
- ICT:Automatic IDs
- ICT:Automatic Numbering
- ICT:Cargo-Workflow
- ICT:Cargo - use of year field format
- ICT:Cargo Geo Coordinnates
- ICT:Cargo and PageForms
- ICT:Cargo and Page Forms Architecture Guide
- ICT:Choosing MediaWiki
- ICT:Conceptual Mermaid Diagram v 4.0
- ICT:ContentTable
- ICT:DA-procedure
- ICT:DBML - version 4.0
- ICT:DBML - version 4.1
- ICT:Dashboard autopurge architecture
- ICT:Dashboard help function
- ICT:Data Model Entity Definitions - v 3.2
- ICT:Data Model Entity Definitions - v 4.0
- ICT:Data Model Entity definitions
- ICT:Data Model Overview v 4.0
- ICT:Data Model and Media Architecture
- ICT:Debugging
- ICT:Development status - decisions
- ICT:Documentation and peer review
- ICT:FinaLConfig - ASSET
- ICT:FinalConfig-Chapter
- ICT:FinalConfig-Clutter and protection
- ICT:FinalConfig-Place-workdocument
- ICT:FinalConfig - ASSET - JAVASCRIPT
- ICT:FinalConfig - ASSET - automatic numbering
- ICT:FinalConfig - ASSET - automatic numbering - flowchart
- ICT:FinalConfig - AssetFileNormakizer extension
- ICT:FinalConfig - Asset - v1
- ICT:FinalConfig - Asset v2 code
- ICT:FinalConfig - Asset v2 configuration
- ICT:FinalConfig - Javascripts
- ICT:FinalConfig - ORGANISATION
- ICT:FinalConfig - PLACE
- ICT:FinalContent - ASSET - LUA
- ICT:Future Dashboard Logic
- ICT:HO-Procedure
- ICT:Hooks ClutterReduction
- ICT:Hooks – How Hooks Work in MediaWiki
- ICT:LocalSettings organisation
- ICT:LuaDebug
- ICT:LuaTest
- ICT:MediaWiki CleanUp Procedure
- ICT:MediaWiki extension Multimediaviewer
- ICT:Mermaid in VScode
- ICT:Metadata Strategy
- ICT:Multi-Tier access - UI protection
- ICT:Namespaces and Lockdown Policy v4.1
- ICT:Naming and Namespace Policy
- ICT:Numbering v 4.0
- ICT:Numbering v 4.1
- ICT:Policy
- ICT:Protection aged user interface
- ICT:Recursive structures explained
- ICT:Rewrite Philosophy
- ICT:Senior friendly interface and security
- ICT:Starting with DA
- ICT:Survivability - Future Plans
- ICT:System Strategy
- ICT:THE pattern
- ICT:THE pattern checklist
- ICT:THE pattern starter kti
- ICT:Technical Terms for Collaborators
- ICT:Template Inclusion and Transclusion Guide
- ICT:Template and Cargo Convention
- ICT:The correct Desing Philosophy
- ICT:Timeout issues
- ICT:Tracking activity
- ICT:Vhost - RProxy settings
- ICT:VisualEditor
- ICT:VisualEditor-Admin
- ICT:VisualEditor installation
- ICT:Workflow