attendance-catalog

Every label the admin attendance UI renders and every option it filters on. The enum-backed lists are derived from the database enums at request time, so a value added to the schema — or a reason added to the catalogue — reaches the screen without a client release. Clients must render label and must not keep a value-to-label table of their own.

{
    "outcomes": [
        {
            "value": "string",
            "label": "string",
            "color": "string"
        }
    ],
    "methods": [
        {
            "value": "string",
            "label": "string",
            "color": "string"
        }
    ],
    "sources": [
        {
            "value": "string",
            "label": "string",
            "color": "string"
        }
    ],
    "eventTypes": [
        {
            "value": "string",
            "label": "string",
            "color": "string"
        }
    ],
    "auditActions": [
        {
            "value": "string",
            "label": "string",
            "color": "string"
        }
    ],
    "personTypes": [
        {
            "value": "string",
            "label": "string",
            "color": "string"
        }
    ],
    "reasons": [
        {
            "id": "string",
            "code": "string",
            "label": "string",
            "effect": "COUNTS_PRESENT",
            "isActive": true
        }
    ],
    "slots": [
        {
            "id": "string",
            "code": "string",
            "label": "string",
            "kind": "DAILY",
            "requiresCheckOut": true,
            "isActive": true
        }
    ],
    "zones": [
        {
            "id": "string",
            "name": "string",
            "isActive": true
        }
    ]
}