Sport Catalog Form Reference

Positions, events and statistics belong to one runtime sport type. Codes are profile/domain identifiers and should remain stable after use in recorded programme data.

Position form

Details

Sport type (required): owning runtime sport definition.
Name and Code (required): translated/display identity and stable machine identifier.
Person type (required): free profile-defined category such as player, staff or official. It is not globally limited to football roles.
Lineup group: optional grouping used for lineup ordering/filtering.
Parent position: optional hierarchy within the same sport type.
Has events (default Yes): allows event capabilities for this position.
Has statistics (default Yes): allows statistic capabilities.

Events and Statistics tabs

Existing positions expose two dual-list assignments. Move only compatible event/statistic definitions from Available to Assigned and save. These tabs do not create new definitions; use the corresponding global catalog toolbar first. Staff/official positions can legitimately have both capabilities off.

Publishing

New positions default to Published and ordering 0. Unpublishing prevents new selection but should not be treated as deleting historical use.

Event Type form

Sport type, Name, Code are required.
Person type identifies the applicable actor category.
Timeline defaults Yes and controls chronological report display.
Direction is a numeric semantic sign/order, default 0.
Affects score defaults No.
Score delta is the numeric change when the event affects score.
Score target identifies whose score changes (own_team, opponent or a profile-defined target).
Requires second person supports paired events such as substitution or assist.
Leads to suspension marks disciplinary consequences.
System event identifies records produced by system workflow rather than ordinary manual actor events.

Do not set affects_score without a score delta/target meaningful for the profile's score model. Event statistics should use matching stable codes in the profile contract.

New event types default to Published and ordering 0.

Statistic Type form

Sport type, Name, Code are required.
Statistic type defaults basic; profiles may use advanced/calculated classifications.
Scope is required and profile-defined (person, team, goalkeeper, participant or another supported scope).
Value type defaults integer; other profiles use decimal, percentage, duration and compatible values.
Calculation source defaults manual; an event-derived or calculated statistic must have a producer defined by the profile/domain logic.

New statistics default to Published and ordering 0.

Creating custom catalogs

Create/save the sport type without one or more initialization switches.
Open the empty catalog list and use Joomla's New toolbar action.
Create stable codes and publish the definitions.
Create positions, then assign their allowed event/statistic capabilities.
Create the project only after the catalog can represent its operation.

Catalog changes are installation-local. They do not edit bundled profile JSON and do not automatically become portable profile definitions.

Editing after data exists

Renaming a display label is safer than changing a code. A code may be stored in profile contracts, event/statistic payloads, templates, migrations and frontend configuration. Before changing one, audit all references and prefer creating a replacement definition while retaining the historical record.