Identity Resolution

Context

• Loyalty provides member_id.

• Zeta (People Service) provides the canonical BSIN.

• All resolution is scoped within a single site_id.

Pre-requisites:

• Zeta.user_id must align with PES profileAltId.

• member_id is stored in Zeta as: unique_client_ids.loy_member_id

Core Rule

Resolve identity in this order:

1) Match on unique_client_ids.loy_member_id
2) Else match on user_id
3) Else create new Person (new BSIN)

Open Questions:

• If loy_member_id and user_id resolve to different Persons - defer to People Service merge behavior?

People service thrift calls involved

• Create new People

  • get_identity - Upsert identity using BSIN/UID/EMAIL

  • store_person - Updates person attributes

• Find people by identifier

  • get_person_by_identifier - find person by identifier

    • identifier types: BSIN/USER_ID/EMAIL

• Merge people

  • merge_identities- merge 2 people with different identifier