company

Every canonical field of a company record, how one is keyed tier by tier, and the relations its fields mint, generated from spec/fields/company.json

What you'll learn

You're mapping a column or a vendor field to a company field and need the exact name, its tier, and its normalization rule.

  • every canonical field of a company, with its tier and type
  • how a company is keyed, tier by tier
  • which fields mint a relation to another type

Canonical field registry for company records (SPEC.md §4a, ADR-017). Company fields keep the company_ prefix so the same fact has the same name whether it appears on a company record or embedded on a person record. A subject type (ADR-054); the identity list is SPEC.md §4's company derivation.

Identity

A company is keyed by the first of these tiers the record has, strongest first.

TierFromKey
1company_domainthe normalized value
2company_namea SHA-256 of those, prefixed nh:

As the type file states it:

[
  {
    "field": "company_domain"
  },
  {
    "hash": [
      "company_name"
    ],
    "prefix": "nh:"
  }
]

Fields

FieldTierTypeNormalizationDescription
company_domainidentitystringdomainRegistrable domain (eTLD+1). Identity tier 1 for companies (SPEC.md §4).
company_nameidentitystringtrimCompany name. Feeds the name-hash fallback tier (SPEC.md §4).
company_websitecorestring (uri)trimWebsite URL as provided. company_domain is the comparable form.
company_linkedin_urlcorestring (uri)linkedin_urlLinkedIn company page URL.
company_employeescoreintegernoneHeadcount as an integer — never a range string.
company_industrycorestringtrimIndustry label. Value domain deferred until a second adapter forces comparability (rule of two).

Examples

FieldExample value
company_domainacme.com
company_nameAcme Corp
company_websitehttps://www.acme.com
company_linkedin_urlhttps://www.linkedin.com/company/acme-corp
company_employees120
company_industryComputer Software

Used in