ICT:FinalConfig - ORGANISATION

Final Configuration for the Organisation Entity

Document revision: 2026-02-17 by Mngr

The aim is to create an interface without MediaWiki clutter and well protected to avoid confusing users with unnecessary elements on the page. The Cargo template follows what has been decided in the DBML and is fully aligned with the reference entity Place.

The Organisation entity is the first entity combining: - recursiveness (parent organisation) - a foreign key to another entity (Place)

This configuration validates that recursion and foreign keys can safely coexist within the same entity model.

This configuration deliberately favors explicit behavior and robustness over visual polish or implicit framework behavior, in order to ensure long-term maintainability.

Cargo Table:

Template:Organisation

<noinclude>
Organisation data template
</noinclude>

{{#cargo_declare:
 |_table=Organisations
 |Code=Page
 |Label=String
 |Parent=Page
 |Place=Page
 |Description=Text
 |Contact=Text
 |Notes=Text
}}

{{#cargo_store:
 |Code={{FULLPAGENAME}}
 |Label={{{Label|}}}
 |Parent={{{Parent|}}}
 |Place={{{Place|}}}
 |Description={{{Description|}}}
 |Contact={{{Contact|}}}
 |Notes={{{Notes|}}}
}}

== {{{Label|}}} ==
{{DISPLAYTITLE:{{{Label}}}}}

{{#if:{{{Parent|}}}|
'''Parent organisation:''' [[{{{Parent}}}]]
}}

{{#if:{{{Place|}}}|
'''Located in:''' [[{{{Place}}}]]
}}

'''Notes:'''
{{{Notes|}}}

Once the template is created, the Cargo table must be created manually. If modifications are made to the table structure, the table must be recreated and the temporary table swapped via the Cargo administration interface.

The field Code stores the full page name (including namespace) to ensure unambiguous identification and safe use as a foreign key across entities.

Important conventions: - Field names start with a capital letter - Code is the page name and acts as the technical identifier - Label is the human-readable name and is mandatory for all entities - Parent and Place are stored as Page fields - The field name Label must not be renamed, as it is relied upon by shared JavaScript validation logic

Special lines at the bottom of the template:

== {{{Label|}}} ==
{{DISPLAYTITLE:{{{Label}}}}}

{{#if:{{{Parent|}}}|
'''Parent organisation:''' [[{{{Parent}}}]]
}}

{{#if:{{{Place|}}}|
'''Located in:''' [[{{{Place}}}]]
}}

'''Notes:'''
{{{Notes|}}}

These lines ensure that the human-readable name (Label) is consistently used as the visible page title, while the actual page name remains the stable technical identifier (Code).

This decoupling allows renaming the label without breaking Cargo relations, dashboards, or foreign keys.

Page Form:

Form:Organisation

<noinclude>
Form for creating and editing Organisation pages.
</noinclude>

{{{info
|no summary
|no preview
|no minor edit
|no watch
|no footer
}}}
''Fields marked with (*) are required.''

{{{for template|Organisation}}}

{| class="formtable"

! Code
| {{PAGENAME}}
|-

! Name (*)
| {{{field|Label}}}
|-

! Parent organisation
| {{{field|Parent
 |input type=combobox
 |values from namespace=Organisation
 |placeholder=Top level (no parent)
}}}
|-

! Located in (Place)
| {{{field|Place
 |input type=combobox
 |values from namespace=Place
 |placeholder=Select a place
}}}
|-

! Description
| {{{field|Description|input type=textarea}}}
|-

! Contact information
| {{{field|Contact|input type=textarea}}}
|-

! Notes
| {{{field|Notes|input type=textarea}}}

|}

{{{standard input|save}}}

{{{end template}}}

The first section avoids MediaWiki edit clutter.

{{{info
|no summary
|no preview
|no minor edit
|no watch
|no footer
}}}

The field Label (displayed to the user as “Name”) is mandatory for all entities. This requirement is not implemented using the Page Forms |mandatory option, as this produces unusable white error boxes in the dark Vector-2022 environment.

Instead: - the requirement is communicated via text and (*) - enforcement is handled via JavaScript at save time

Dashboard page

Dashboard:Organisation

= 🏛️ Costa Sano Research ORGANISATION Dashboard =

📖 [[Dashboard:Organisation/Help|Need Help?]]

{| class="wikitable sortable"
! Code !! Name !! Parent !! Place
{{#cargo_query:
 tables=Organisations
 |fields=_pageName,_pageTitle,Label,Parent,Place
 |where=_pageNamespace=3008
 |order by=_pageTitle
 |format=template
 |template=OrganisationRow
 |named args=yes
 |cache=no
}}
|}

Choose your organisation code corresponding to above table and respecting the naming conventions.

{{#forminput:
 form=Organisation
 |namespace=Organisation
 |button text=➕ New organisation
 |returnto=Dashboard:Organisation
}}

<div style="text-align:right; font-size:90%;">
Last updated: {{CURRENTDAY}} {{CURRENTMONTHNAME}} {{CURRENTYEAR}} – {{CURRENTTIME}} UTC
</div>

IMPORTANT: Dashboard tables are positional. The number and order of: - table headers - Cargo query fields - row template cells MUST match exactly.

Only the first column (Code) is clickable and leads to the edit form. All other columns are displayed as plain text to prevent navigation to record pages.

Row transclusion Template

Template:OrganisationRow

<includeonly>
|-
| {{#formlink:
   form=Organisation
   |target={{{_pageName}}}
   |link text={{{_pageTitle}}}
   |returnto=Dashboard:Organisation
 }}
| {{{Label}}}
| {{#if:{{{Parent|}}}|{{#titleparts:{{{Parent}}}|1}}|—}}
| {{#if:{{{Place|}}}|{{#titleparts:{{{Place}}}|1}}|—}}
</includeonly>

Parent and Place values are displayed as plain text (not links) to prevent users from navigating directly to record pages. All record editing is performed via forms accessed from the dashboard.

Javascript

The Organisation entity reuses the same shared JavaScript infrastructure as Place: - dashboard auto-purge - save-time mandatory field enforcement (Label) - no Page Forms |mandatory usage

No Organisation-specific JavaScript is required.

All Organisation pages are stored in the Organisation namespace with the page name acting as the Code.

Example:

{{Organisation
|Label=Archives Départementales du Pas-de-Calais
|Parent=
|Place=Place:ARRAS
|Description=Regional archive authority for the Pas-de-Calais department.
|Contact=Rue Ferdinand Buisson, 62000 Arras
|Notes=Primary source repository for Costa Sano research.
}}

Such pages are configuration pages and must be accessed via the dashboard, not directly.

References:

• Cargo table explanation
• Page Forms explained