Data dictionary · provenance + exported fields

Provenance model

Provenance is a side table, not a footnote. For each exported field in a record there is a corresponding provenance row recording the source identifier, source URL, source class, and effective value state. Values without commercial-use cleared provenance are excluded from the paid export path.

{
  "field":         "field_name",
  "value":         "...",
  "source":        "accc",
  "source_class":  "government | registry | manufacturer | aggregator | derived",
  "source_url":    "https://www.productsafety.gov.au",
  "effective":     true,
  "superseded_at": null
}

Export shape

The primary entity is recalls. The export combines the canonical entity table with active provenance from 8 sources. JSON responses and the full JSON download include nested provenance. CSV, Parquet, and SQLite are explicitly curated flat extracts and do not carry nested or separate provenance tables.

Key fields

These fields are selected from the field catalog as the main dimensions for filtering, grouping, matching, and API usage:

• -authoritySource authority code, such as cpsc, eu-safety-gate, health-canada, gov-uk-opss, accc, fr-rappelconso, tw-bsmi, or fi-tukes-historical.Notice identity
• -idUnique numeric notice identifier within RecallRadar.Notice identity
• -source_notice_refAuthority-specific reference number or ID, such as a CPSC recall number or RAPEX alert ID.Notice identity
• -is_recallTrue when the notice is a formal recall; false for alerts or warnings that stop short of recall.Recall classification
• -category_sourceCategory source value emitted by the recalls export. Use the record provenance payload to inspect source attribution when populated.Exported flat columns
• -country_of_originCountry of origin value emitted by the recalls export. Use the record provenance payload to inspect source attribution when populated.Exported flat columns
• -jurisdictionJurisdiction value emitted by the recalls export. Use the record provenance payload to inspect source attribution when populated.Exported flat columns
• -risk_levelRisk level value emitted by the recalls export. Use the record provenance payload to inspect source attribution when populated.Exported flat columns
• -summarySummary value emitted by the recalls export. Use the record provenance payload to inspect source attribution when populated.Exported flat columns
• -titleTitle value emitted by the recalls export. Use the record provenance payload to inspect source attribution when populated.Exported flat columns
• -hazard_textProse description of the hazard as stated by the issuing authority.Notice content
• -remedy_textProse description of the required consumer remedy, such as return, repair, refund, or stop use.Notice content
• -published_atDate the notice was published by the source authority.Notice identity
• -category_codeUnified product category slug from the RecallRadar taxonomy.Recall classification
• -hazard_typesHazard types value emitted by the recalls export. Use the record provenance payload to inspect source attribution when populated.Schema fields
• -languageLanguage value emitted by the recalls export. Use the record provenance payload to inspect source attribution when populated.Schema fields

Field catalog

The catalog below contains 20 documented fields from the same field model rendered on this page. Field types and descriptions come from the export contract and source registry. Nullable means unknown or not applicable; it does not mean zero, false, or inferred.

NULL policy

A missing field on a record is a missing field: not a zero, not a negative assertion, and not an imputed value. Fields that do not apply to a record are explicitly NULL. Coverage gaps are visible by design.

Audit trail

Every provenance row carries the observed value, source code, source record URL, effective state, and ingest context. Snapshot manifests and source licence notes document which upstream records were cleared for commercial use.