See Organization-Specific Terminology on the Selection Screen
Each organization participating in the platform uses different terminology. For example, NHF may call the peer helper role 'likeperson' while another organization uses 'frivillig' or 'støtteperson'. The terminology-aware text widget (679-terminology-aware-text-widget) and organization labels provider (006-org-labels-provider, 199-org-labels-provider) dynamically resolve label keys to organization-specific strings. On the org selection screen, the role label displayed under each organization card must reflect that organization's configured terminology, not a generic default. This requires loading org-specific label configurations before or alongside the org list.
User Story
Acceptance Criteria
- Given I belong to two organizations with different terminology configurations, When the org selection screen loads, Then each organization card displays the role label using that organization's own terminology
- Given an organization has a custom label configured for 'peer mentor', When I view that organization's card, Then the role is displayed using the custom label, not a hardcoded default
- Given terminology data is not yet loaded for an organization, When that org's card is rendered, Then a sensible fallback label is shown and the UI does not crash or show a blank role label
- Given the organization labels provider successfully loads configurations, When I select an organization, Then all subsequent screens in the session use that organization's full terminology set
Business Value
Each of the four organizations in the pilot (NHF, Blindeforbundet, HLF, Barnekreftforeningen) uses different vocabulary for peer helpers, coordinators, and activities. Displaying incorrect terminology on the very first screen users encounter after login creates immediate confusion and erodes trust in the platform. Correct terminology at the org selection step reinforces that the app understands each organization's identity and prepares the user for a contextually appropriate experience throughout their session.
Components
- Organization Labels Provider infrastructure
- Organization Labels Provider infrastructure
- Terminology-Aware Text Widget ui
- Organization Labels Notifier service
- Label Key Resolver Service service
- Terminology Sync Service service
- Terminology Repository data
- Terminology Local Cache Adapter data
- Label Key Registry infrastructure
- Terminology Riverpod Providers infrastructure
- WCAG Semantics Label Resolver infrastructure