Skip to content
Astera Technology

Resolve an ambiguous nickname alias before redirecting a directory lookup

Keep multiple matches visible instead of silently selecting the first staff record.

Inspect alias membership

Fictional alias “Pat” maps S49 in site N and S50 in site S. Lookup request specifies site S; this resolves S50 under the local exact-site rule. A request with alias only remains ambiguous. The workflow does not merge staff identities or infer names from spelling similarity.

Alias disambiguation
StaffAlias/siteMatches site S request
S49Pat/NNo
S50Pat/SYes
Download editable CSV ↓

Use supplied distinguishing information

  1. List both Pat candidates
  2. Read supplied site qualifier
  3. Match exact site S
  4. Return S50 or request qualifier if absent

Do not redirect an alias-only request to whichever candidate was stored first.

How many candidates exist before and after site S qualification?

Show the worked answer

Two before qualification, one after, S50. Neither staff key changes.

Retain ambiguity until resolved

Filled administration checks
CaseAction or resultEvidence boundary
Pat onlyRequest distinguishing fieldTwo matches
Pat plus site SResolveS50One exact-site match
Download editable CSV ↓

Keep alias mappings as search aids, not replacement staff keys. The result links to the chosen staff detail record.

Related resources