feat(doors): add persistent labels and groups #195

New issue

Open

opened 2026-09-30 15:26:18 +00:00 by gabogg · 0 comments

gabogg commented

2026-09-30 15:26:18 +00:00

Owner

Part of #187 — milestone: Focused operator and supervisor door operations.

Intended outcome

Let Supervisors apply clear, persistent labels to doors for finding and grouping them. Current HikCentral door names and sensor category are different concepts; labels must not overwrite hardware identity or sensor classification.

Triage questions

Does “labeling” mean one local display name, multiple tags, location/zone hierarchy, operational priority, or a combination? Which concrete filtering task should it solve first?
Who may create, rename, assign, and remove labels? Are labels shared facility-wide, controlled vocabulary, or free text?
How do labels survive HikCentral sync, door renaming, missing hardware, and manual door registration? Which stable door key owns assignments?
Should labels drive saved door lists, open-time reports, exclusions, or Operator filtering in the first milestone?

Ready-to-spec outcome

A small metadata model and edit/filter behavior, including duplicate names, stale doors, EN/ES display, and persistence across sync. Keep labels distinct from the existing SensorCategory enum.

Part of #187 — milestone: Focused operator and supervisor door operations. ## Intended outcome Let Supervisors apply clear, persistent labels to doors for finding and grouping them. Current HikCentral door names and sensor `category` are different concepts; labels must not overwrite hardware identity or sensor classification. ## Triage questions 1. Does “labeling” mean one local display name, multiple tags, location/zone hierarchy, operational priority, or a combination? Which concrete filtering task should it solve first? 2. Who may create, rename, assign, and remove labels? Are labels shared facility-wide, controlled vocabulary, or free text? 3. How do labels survive HikCentral sync, door renaming, missing hardware, and manual door registration? Which stable door key owns assignments? 4. Should labels drive saved door lists, open-time reports, exclusions, or Operator filtering in the first milestone? ## Ready-to-spec outcome A small metadata model and edit/filter behavior, including duplicate names, stale doors, EN/ES display, and persistence across sync. Keep labels distinct from the existing `SensorCategory` enum.

gabogg added this to the Focused operator and supervisor door operations milestone

2026-09-30 15:26:18 +00:00

gabogg added the

needs-triage

label

2026-09-30 15:26:18 +00:00

gabogg referenced this issue

2026-09-30 15:26:53 +00:00

epic(ui): focus Operator on doors and alarms; introduce Supervisor workspace #187

gabogg referenced this issue

2026-09-30 16:03:53 +00:00

feat(supervisor): manage existing door inventory and metadata #190