Jump to content

ICT:Policy

From Costa Sano MediaWiki
Revision as of 16:51, 17 January 2026 by Mngr (talk | contribs) (Created page with "= Data and Content Policy = This page defines rules, responsibilities, and constraints governing the system. It is normative and must be followed. == Scope == This policy applies to: * All structured namespaces (HO:, DA:) * All Cargo tables * All file uploads * All public publications == Roles and Responsibilities == {| class="wikitable" ! Role !! Responsibility |- | Administrators || Schema changes, permissions, maintenance |- | Editors (club members) || Data ent...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Data and Content Policy

This page defines rules, responsibilities, and constraints governing the system.

It is normative and must be followed.

Scope

This policy applies to:

  • All structured namespaces (HO:, DA:)
  • All Cargo tables
  • All file uploads
  • All public publications

Roles and Responsibilities

Role Responsibility
Administrators Schema changes, permissions, maintenance
Editors (club members) Data entry, uploads, internal pages
Public users Read-only access to published content

Schema Authority

  • Cargo table pages are the single source of truth
  • Page Schemas must reflect Cargo tables
  • Direct database manipulation is forbidden

Namespace Policy

  • Main namespace is public
  • HO: and DA: are internal
  • File: uploads are restricted
  • ICT: is internal documentation

Namespaces must not be repurposed.

File Policy

  • Uploads only by authorized users
  • Internal files must not be embedded on public pages
  • Public files must be intentionally selected
  • Masters and working files remain internal

Deletion of files must be coordinated.

Digital Asset Policy

  • Every significant file must belong to a DA
  • DA pages must document provenance and relationships
  • DA pages are not public-facing content

Relationship Modeling Policy

  • Join tables are implemented as Cargo subtables
  • Relationships must not be modeled as standalone pages unless justified
  • Contextual relationships belong to the parent entity

Change Management

  • Schema changes must be documented
  • Structural changes require review
  • Ad-hoc fixes are discouraged

Enforcement

Violations of this policy may result in:

  • Page rollback
  • Schema correction
  • Permission review

Status

This policy is binding until revised.