sandbox  ·  southernculinaryatlas.com/data
| The Southern Culinary Atlas Data Suite
Platform Overview
The Culinary Atlas Data Suite is an academic tool and an indexable lockbox for our collective food memory.
20
Dishes
16 published
38
Recipes
editorial + contributed
7
Oral Histories
3 live · 4 pending
8
Contributors
2 moderators
12
Municipalities

This platform launched in beta in August 2026. Records reflect editorial seeding with some early contributions.

Dish types
Recipe source types
Dishes
Canonical dish records — editorial and community-confirmed
Always visible
Toggleable
Filters
Dish Type
Has
Dish Name Aliases Types Recipes Oral Histories Cooks Eats Knows Never Heard Appearances
Taxonomy
A numeric coding schema reminiscent of the way botanists classify plant relations, built by Justin Robinson. See more about this work in the German Soul Documentary.

About the Taxonomy

The Culinary Atlas uses a numeric coding schema to classify dishes along multiple axes: primary cooking method, macro ingredient category, preparation tradition, and more.

Each dish receives a taxonomy_codes JSON object (stored on the dishes table) with keys like main_method, macro, and prep. These codes also determine the quilt color index used for visual display in the Atlas.

The taxonomy was created for the live documentary German Soul, to research and discover connections between Soul Food, and food from Germany, West Africa, and the Caribbean. Once fully developed for this use case, the taxonomy will join the atlas in becoming a powerful resource for food scholars worldwide.

Taxonomy Structure Coming Soon
The full taxonomy web and attribute filter interface will appear here once the specification is ready for presentation, use, and feedback. This section will become a navigable web. For now, you can explore the atlas and data suite to see how we attend deeply to analytical power when building this resource.
For all atlas, data, and taxonomy-related queries, including information on where the taxonomy is and how it is being developed, please email courtney@digitalculturalcommons.com. We always welcome thoughtful engagement with our research.
Export Dataset
Fair-source · Password-protected · PII-free · Version 0.1.0
Fair-Source Data Access

The Southern Culinary Atlas is built on community trust. Contributors share recipes, oral histories, and cultural knowledge because they believe this archive will honor their stories — not exploit them.

We believe in free and fair information. We also believe in protecting this information from extraction by large corporations, advertisers, and AI training pipelines that strip context from culture. For that reason, the Atlas dataset is licensed fair-source rather than open-source, and all downloads are password-protected.

We are actively looking for collaborators and feedback-givers during this period of strong growth. If you want access to the dataset, we are happy to provide it — and we ask that you offer something to the Atlas in return. This can be:

Advising & feedback  ·  Publicity & audience  ·  Contribution solicitation
Archive or resource access/permissions  ·  Connections & networking
Technical support  ·  Fiscal support

Email courtney@digitalculturalcommons.com for access to the database.

Click anywhere to continue
Password Required
Dataset downloads are password-protected. Contact courtney@digitalculturalcommons.com to request access.
Dishes
Canonical Records · 20 rows
Canonical dish names, aliases, type classifications, recipe and oral history counts, taxonomy codes, and editorial metadata. No PII.
v0.1.0 · ~18 KB Privacy notice
🍲
Recipes
Contributed + Editorial · 38 rows
Recipe titles, linked dish IDs, ingredients, steps, provenance metadata, geographic region, dietary tags, and pseudonymized contributor IDs.
v0.1.0 · ~42 KB Privacy notice
📖
Oral Histories
Contributed · 7 rows (approved)
Story text, linked dish IDs, geographic regions, structured prompt-response fields, and pseudonymized contributor IDs.
v0.1.0 · ~28 KB Privacy notice
🗺
County Density Map
Geographic · 12 counties
County-level contribution density as GeoJSON. Compatible with QGIS, ArcGIS, Mapbox, and Leaflet.
v0.1.0 · ~88 KB Privacy notice
Full Archive Bundle
All tables · dishes + recipes + oral histories + map
Everything above in a single .zip with a README.txt, data dictionary, and citation guidance.
v0.1.0 · ~180 KB estimated Privacy notice
How to Cite This Dataset
Explorer
Choose your dependent and independent variables to pivot the dataset along any two axes.
See per
Dishes per Location
This view pivots the full dataset so researchers can examine any cross-section. Select your dependent variable (what you're counting) and independent variable (what you're grouping by), then browse the resulting table.

Examples: recipes per dish, dishes per location, oral histories per contributor, relationships per location, media per editorial source.
Pivot engine preview — full cross-tabulation coming soon.
Methodology
How data is collected, moderated, and prepared for research use

Data Collection

The Southern Culinary Atlas collects data through three primary channels:

  • Editorial seeding — the project team contributes canonical dish records and editorial recipes as a baseline corpus, particularly for dishes with thin oral documentation.
  • Oral History Quiz — a structured eight-prompt quiz in the Interactive Suite elicits personal food memories. Responses are anchored to a self-reported county and linked to dishes where identified.
  • Open contribution — contributors may submit recipes and oral histories outside the quiz structure via a free-entry form. These follow the same moderation process.
  • Dish Scout (Dish Flash) — a gamified recognition interface generates binary dish-recognition responses (yes/no) per county, producing validation signal for existing records.

Moderation Process

Every contributed record passes through a moderation queue before publication. Moderators are community members who applied and were approved by the editorial team. The moderation process reviews:

  • Content accuracy — obvious errors or anachronisms in provenance claims
  • Geographic plausibility — contributions are anchored to a claimed county; implausible combinations are flagged
  • Cultural sensitivity — content that misrepresents or appropriates oral tradition is declined with explanation
  • PII detection — moderators are trained to catch and remove identifying information before approval

Records declined by moderators are not published and not included in exports. The moderator who approved a record and the timestamp are retained internally but are not exported.

Pseudonymization

Contributor PII is held in a separate, access-controlled database table (contributors) that is never exposed through the public-facing API or export endpoints. Every contributor is assigned a pseudo_id (a stable, non-reversible hash) which appears in exported recipe and oral history records in place of any identifying field.

The mapping between pseudo_id and real identity is held only in the admin-accessible table. No export format, endpoint, or public interface exposes this mapping. Geographic granularity in exports is county-level only — no street addresses, zip codes, or sub-county identifiers are published.

License Terms for Downloaders

Each recipe record carries a license assigned by the original contributor at time of submission. The available licenses are:

  • CC0 — public domain dedication; no attribution required
  • CC BY — attribution required; derivative works permitted
  • CC BY-NC — attribution required; non-commercial use only
  • All Rights Reserved — the contributor retains copyright; contact the editorial team for use

Oral histories default to CC BY-NC unless the contributor specifies otherwise. Dish editorial records are CC BY (the platform holds copyright). The license column is present in all recipe exports. Downloaders are responsible for respecting per-record licensing.

Limitations and Biases

Researchers using this dataset should be aware of the following:

  • Geographic skew — early data collection is concentrated in Eastern North Carolina, the Lowcountry of South Carolina, and Atlanta metro. Gulf Coast and Appalachian coverage is thin.
  • Survival bias in oral history — the quiz format privileges memories that are already narratively formed. Everyday, unremarkable foodways are underrepresented.
  • Language — the platform is English-only in V1. Spanish-language and other-language contributions are not yet supported.
  • Network recruitment — early contributors were recruited through the documentary production's existing community contacts, introducing a network homophily effect.
  • Taxonomy is editorial — dish classification is performed by the editorial team using Justin's schema. It is not crowd-sourced and reflects editorial judgment, not community consensus.
  • Sandbox data — the dataset in this release is editorial seed data. Statistically meaningful analysis should await a full contributor dataset.
For questions about data quality, methodology concerns, or collaboration inquiries, contact the editorial team at the address in the archive README.