Demonstration

From Architecture to Working Demonstration

A current shared-record implementation shows how one underlying database can support multiple branded and geographically scoped surfaces — each with its own eligibility, publication status and placement.

What Is Configured Today

The Current Implementation

25 configured shared-record surfaces

One shared organization and Business Record model

Independent surface eligibility

Independent publication status

Independent placement by surface

Regional overlap across Minnesota and Wisconsin

Local/international and USA-specific information families

Specialized surfaces for reviews, happenings, savings, featured content, storefronts, promotions, advertising and activity

Example Record

One Record, Many Authorized Placements

The record below is fictional and exists only to demonstrate how eligibility and publication rules behave.

Fictional demonstration record

Northland Test Business Account

Advertising

2100 Port Terminal Drive
Duluth, Minnesota 55811

The same record may also appear on relevant specialized surfaces — reviews, happenings, savings, featured content, storefronts, promotions, advertising and activity — when it is eligible for that surface and published to it. Eligibility is never inherited automatically from another surface.

Data Flow

How a Placement Is Decided

  1. Business or organization
  2. Authoritative Business Record
  3. Location and service data
  4. Eligibility rules
  5. Publication approval
  6. Surface placement
  7. Consumer and machine-readable experiences