ICT:Naming and Namespace Policy: Difference between revisions
Appearance
Created page with "= Naming & Namespace Policy = == Purpose == Defines how pages are organized and named. Namespaces enforce structure and prevent accidental mixing of content. ---- == Namespaces == Standard namespaces: * DA: → Digital Assets * HO: → Heritage Objects * P: → Persons * ORG: → Organisations * RC: → Research Chapters Each entity type has exactly one namespace. ---- == Why namespaces are mandatory == Benefits: * clear separation of content types * perm..." |
m Mngr moved page ICT:Naming & Namespace Policy to ICT:Naming and Namespace Policy without leaving a redirect |
(No difference)
| |
Latest revision as of 14:52, 29 January 2026
Naming & Namespace Policy
Purpose
Defines how pages are organized and named.
Namespaces enforce structure and prevent accidental mixing of content.
Namespaces
Standard namespaces:
- DA: → Digital Assets
- HO: → Heritage Objects
- P: → Persons
- ORG: → Organisations
- RC: → Research Chapters
Each entity type has exactly one namespace.
Why namespaces are mandatory
Benefits:
- clear separation of content types
- permission control
- safer queries
- easier navigation
- prevents naming collisions
Example:
DA:0001 HO:0001
Both can exist safely.
Page naming rules
Pages are NEVER manually named.
Forms must:
- set target namespace
- use page name formula
- hide title field
Example:
{{{info
|target namespace=DA
|page name formula={{{id}}}
|hide title=1
}}}
Users must not type titles manually.
ID policy
- IDs are stable
- IDs never change
- IDs are used as page names
- filenames are NOT page names
Good:
DA:0001
Bad:
DA:photo_final_version2.jpg
Test content
Experimental work must use:
- Test:
- Sandbox:
Never create experiments in production namespaces.