Skip to content

✨ Customers: country flag, likely affiliation suggestion and notes rules on a profile (spoke-local) #19085

Closed

Description

@clubanderson

Follow-up to #18958 and #18973. The operator asked whether Customers carries each person's country, notes, name and likely affiliation, the way the hub shows them. What exists today on the spoke:

  • Real name, organization and location, each with auto or manual provenance (✨ Customers: real name, organization and location on a profile #18973).
  • Notes: free text up to 4000 characters, shown and editable only by the owner and read-write users, withheld from a read-only user, included in export, deleted with the person on Forget. This already works; it only needs its rules stated in the docs and pinned by tests.

Missing:

  1. Country. Derive an ISO 3166 alpha-2 country from the free-text location deterministically and offline (a small bundled table: country names, aliases, ISO codes, US states, Canadian provinces, major cities; no network, no geocoder). Store it as country with auto or manual provenance like the other fields. Show a compact flag plus the ISO code as text on the row and the country name in Details (Windows renders flag emoji as letters, so the code is always text; aria-label carries the country name). Manual edit and clear are honored and never overwritten; "Auto" hands it back.
  2. Likely affiliation. A suggestion, never silent truth: "Likely: IBM" with its evidence and Accept or Dismiss. Accept writes the organization field with manual provenance; Dismiss remembers the refusal. Rules: the cleaned GitHub company text already fetched, and the domain of an email identity a person confirmed by hand (never a free-mail domain). Public GitHub organization membership is NOT used: it is not fetched today and would be a new network call.
  3. Notes rules documented and tested (bounds, visibility, export, Forget).

Constraints: no new network calls, the existing off-by-default step E switch and hourly budget are unchanged, Forget and export cover every new field, nothing is read from the hub (that is a separate issue).

Activity

  1. added
    help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
    on Nov 18, 2026
  2. hivecommons-hive commented on Nov 18, 2026

    @hivecommons-hive
    Contributor

    A hive agent asked to claim this issue, but it is covered by #19087 (@clubanderson). The claim was not recorded; the owner decides whether to proceed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions