California DCC Data Landscape

Data Sources at a Glance

Provenance Model

Every generated page carries a standard provenance footer:

Official source

The exact URL the data was retrieved from.

Retrieval date

When the source response was captured.

Data-through date

The latest date the source reports data for.

Checksums

SHA-256 of private raw and normalized payloads recorded in the source manifest.

Generator version

scripts/dcc_ingest.py version that produced the record.

Stable entity ID

The Boris graph identity, e.g. datasets/TDTS-0001.

Definitions

Raw snapshot

Private, unpublished copy of the source response.

Normalized snapshot

Private, unpublished validated derivative of the source response.

Aggregate record

A page summarizing counts or trends, not individual entities.

Entity record

A page for one meaningful entity (laboratory, recall, contaminant, organization).

Current Sync Status

• Done — License registry fetched; payload retained privately and provenance recorded
• Done — Active testing laboratories extracted
• Done — Recall index captured across all pages
• Done — Representative recall details parsed
• Done — Contaminant index connected to recalls
• Done — Source manifest written
• Done — Schema-change and sync reports written
• Blocked — Harvest report numeric extraction: undocumented Looker Studio source
• Blocked — Sales report numeric extraction: undocumented Looker Studio source

DCC Data Caveat

Footnotes

The dashboard glossary defines reporting terms such as wet weight, packaged weight, and facility type.¹

Source & Provenance

• Official source: https://www.cannabis.ca.gov/resources/data-dashboard/
• Jurisdiction: California, United States
• Retrieval date: 2026-08-04
• Data-through date: 2026-08-04
• Source-data caveat: Source data are entered by licensees and may later be corrected or revised by the Department of Cannabis Control (DCC).
• Record status: synced
• Generator: scripts/dcc_ingest.py v0.1.0-poc (schema 1.0)
• Stable entity ID: datasets/TDTS-0004