Example: A draft BBQ data structure

Editor's note: Since so many journalists are unfamiliar with the concept of a data structure, here's the beginnings of one. I wrote this out on Sunday morning for a group project that would aim to collect, preserve and interpret the barbecue folkways of South Carolina.

If you've never seen something like this before, think of it as a story that's been broken down into its component parts so that it can be endlessly reassembled, combined, deconstructed, extracted, queried, etc. Note how it uses objective statements (cloth napkins, paper napkins, roll of paper towels) as ways of answering subjective questions (What's the atmosphere like?). And see how it takes particular care to associate related media objects with the file. Even the video footage is archived as component parts for potential reassembly into different types of presentations.

A successful data structure requires a basic understanding of the subject and should become more intelligent as it grows. It also makes use of specific techniques that aren't rocket-science, yet require rational thinking. If you want a clear example of the difference between natural-language information and semantic, structured information, take a look at how we handle hours of operation here. Both approaches accomplish the same task and produce the same natural language outcome -- but only the structured approach gives you the flexibility that comes with automation.

Think this isn't a creative act? I encourage you to think of your own example and try it.

--dc

+ denotes required field (can choose N/A)
Common items (such as: BBQ, atmosphere, service, etc.) may also include a dropdown grading scale.

BASIC IDENTIFICATION

+Subject name (used as a slug / keyword for other media types)
+Name of business
.. Do we have establishing shot on file? (yes/no)
.... If yes, date (DD/MM/YYYY)
...... File name & path
+Does it have a logo? (yes/no)
.. If yes, do we have logo on file? (yes/no)
...... File name & path
...... Date acquired (DD/MM/YYYY)
+Phone number (for customers / publication)
Phone number (other)
+Owner name
.. Do we have mugshot on file? (yes/no)
.... If yes, date (DD/MM/YYYY)
...... File name & path
+Owner street address (office)
Owner mailing address (if different than street address)
+Owner e-mail
Owner personal phone (cell)
Business type (LLC, limited partnership, corporation, franchise, etc.)
+Business web site (primary)
Business web site (secondary)
+Type of business
.. Restaurant (yes/no)
.... If restaurant
...... Street address
...... GPS coordinates
...... County (counties should be assigned attributes, such as geo-region AND sauce region, etc.)
..Catering (yes/no)
.... Additional catering (must have public dining area to qualify as “additional”)
....Catering, no dining area for customers
...... If no dining area, then street address of HQ.
...... County
.. Cooking competition team (yes/no)
.... Competition team only
.... Additional cooking competition squad
+IF RESTAURANT then Days of operation (select all that apply)
..Sunday
..Monday
..Tuesday
..Wednesday
..Thursday
..Friday
..Saturday
..+(If a day is selected, require hours) Open / Close
+Also closed on (drop-down list of holidays)
+Breakfast? (yes/no)
Scheduling notes (unstructured field for describing quirks of the schedule)
+Business founded in (year drop-down menu)
+Business founded by (names)
+Employees
.. Full-time (enter number)
.. Part-time (enter number)
.. Pit bosses (enter number)
.... Names (notes field)
...... Do we have mugshot on file? (yes/no)
.... ....If yes, date (DD/MM/YYYY)
.......... File name & path
.. Date collected (DD/MM/YYYY)
Business notes field (general or interesting information that cannot be anticipated or coded)

FOOD INFO
+Cooking method (dropdown)
+If RESTAURANT, THEN: Cooked on premises? (yes/no)
+BBQ style
.. Vinegar
.. Mustard
.. Tomato (light)
.. Tomato (heavy)
.. OTHER (notes: specify)
.. Multiple (specify)
+Is sauce proprietary? (yes / no)
.. If NO, specify source (Notes field)
+Proprietary BBQ sauce options provided for diners? (yes/no)
.. If YES, select all that apply)
.... Vinegar
.... Mustard
.... Tomato (light)
.... Tomato (heavy)
.... OTHER (notes: specify)
+Non-proprietary BBQ sauce options provided for diners? (yes/no)
.. If YES, select all that apply)
.... Vinegar
.... Mustard
.... Tomato (light)
.... Tomato (heavy)
.... OTHER (notes: specify)
+Entre choices offered (select all that apply)
.. Pulled pork
.. Chopped pork
.. Sliced pork
.. Whole hog (pick your own)
.. Ribs
.... beef
.... pork
.. Brunswick stew
.. Hash
.. Chicken bog
.. Chicken
.... BBQ
.... Fried
.... Other
.. Beef (other than ribs)
.... Brisket
.... Other
.. Hamburgers
.. Fried fish
.. Seafood (includes fried fish. Don’t select fried fish if selecting seafood)
.. OTHER (Notes field, specify)
.. Specialty entre? (yes/no)
....If yes (dropdown)
.. Entre notes (unspecified, but good place to include interesting information about the entres described above)
+ Side items (select all that apply)
.. Slaw
.... Standard
.... Other
.. Beans
.... Standard
.... Other
.. Rice
.. Greens
.. Potatoes (not french fries)
.. Fries
.. Cornbread
.. Loaf bread
.. Macaroni and cheese
.. OTHER (notes: specify)
+Dessert
.. Banana pudding
.. Cobbler
.. OTHER (notes, specify)
+Beverages
.. Ice tea
.... Source (made by staff / purchased pre-made)
.... Sweet tea
.... Unsweet tea
.. Sodas (list)
..+IF RESTAURANT then alcohol license? (yes/no)
.... If YES then
...... Does it also have a bar?
...... Is beer offered on tap?
...... Are liquor / mixed drinks sold?
.... ..Is beer or wine offered with meal?
+Non-entre SPECIALTY (yes/no)
.. If YES then
.... Dropdown selection (includes OTHER)
.... Specialty notes field
.... Do we have establishing shot on file? (yes/no)
...... If yes, date (DD/MM/YYYY)
........ File name & path
+Carry Out? (yes/no)
+Phone ahead carry out? (yes/no)
.. If YES, then
.... Carry out phone number (10 digits)
.... Carry out notes (phone ahead rules? Time to prepare? Etc.)
+Sauce available by the bottle? (yes/no)
.. If YES, then is sauce available at stores? (notes: list stores)
+BEST FOOD ITEM (dropdown, includes OTHER as a category)
.. Notes about this item.
.. Do we have establishing shot on file? (yes/no)
.... If yes, date (DD/MM/YYYY)
...... File name & path
Food notes (general or interesting information on the food operation, preparation, etc.)
+Overall food grade

RESTAURANT PRICING
+Date checked: (DD/MM/YYYY)
+Basic chopped sandwich (notes: specify details of sandwich)
+Basic chopped plate (notes: specify items)
+Popular chopped sandwich combo (notes: specify items)
+Popular chopped plate combo (notes: specify items)
+Quart of pork
+Bottle sauce
+Specialty food item (notes, specify)
+Glass of sweet tea to go
If available, the Delivery price (notes: specify delivery availability)

CATERING PRICING
I’m not sure how to even begin.

RESTAURANT
+Date checked (DD/MM/YYY)
+Setting
.. Urban (includes suburbs)
.. Small town commercial district
.. Rural
+Is setting in a strip shopping center?
.. Setting (notes… description)
+Have we plotted this location on a locator map? (yes/no)
.. Link
+Exterior (notes, description)
.. Do we have establishing shot on file? (yes/no)
.... If yes, date (DD/MM/YYYY)
...... File name & path
.. On-site parking?
.. Drive-thru window?
.. Outdoor dining option?
+Interior
.. Do we have establishing shot on file? (yes/no)
.... If yes, date (DD/MM/YYYY)
...... File name & path
.. Number of dining rooms (number)
.... Seating capacity of each dining room (number)
.... Dining room notes (describe)
.. Seating capacity (number)
.. Communal tables?
+Service
.. Order at line (yes/no)
.. Order at table (yes/no)
.. Servers deliver food only (yes/no)
.. Waiters (yes/no)
.. Buffet style (yes/no)
.. Family style (yes/no)
.. Tip jar? (yes/no)
.. Tip on table? (yes/no)
.. No tips policy (yes/no)
+Payment
.. All payment types
.... Select cards accepted
.. Cards, but no checks
.... Select cards accepted
.. Checks, but no cards
.... Local checks only?
.... Special check requirements?
.. Cash only
+Reservations?
.. No.
.. Recommended
.. Available, but stupid.
+Atmosphere (select all that apply)
.. Old-timey
.. Modern
.. Franchise
.. Upscale
.. Gas station
.. Honky-tonky
.. Bar/restaurant
.. Restaurant/bar
.. Joint
.. Diner
.. Roadhouse
.. Community meeting place
.. Welcoming
.. Insular, suspicious of outsiders
.. Friendly
.. Indifferent
.. Rude
.. Deliberately tacky
.. Unintentionally tacky
.. Retro
.. Rockabilly
.. Minimal
.. Elaborate
.. Features old photos, news clipping, etc., about the place & people
.. Simple menus
.. Professionally designed menus
.. No menus: order from board
.. Hand-written signs pasted up
.. Press-board signs
.. Relaxing
.. Cloth napkins
.. Paper napkins
.. Roll of paper towels
+Feels deeply authentic in its style and appearance (Should this be yes/no, or a number grade?)
.. Do we have detail shot that communicates the style of the place on file? (yes/no)
.... If yes, date (DD/MM/YYYY)
...... File name & path
.. Do we have a representative portrait shot of staff member(s) on file? (yes/no)
.... If yes, date (DD/MM/YYYY)
...... File name & path
+Overall restaurant grade.

VIDEO STATUS
+Subject name (dropdown)
+Video status (dropdown)
.. Not scheduled
.. Pending (scheduled and permission)
.... Date and authorized by
.. Rejected (permission requested and rejected)
.. Shot but not edited
.... Tape filed as:
.. Shot and captured but not edited
.... File name and path
.. Web video available
.... File name and path for web video
.... File name and path for raw capture
.... Tape filed as
.. Web video posted
.... URL
.... File name and path for web video
.... File name and path for raw capture
.... Tape filed as
..Video status notes field
+Video shot by (drop down)
+Video shot on (DD/MM/YYYY)
.. Additional footage on (DD/MM/YYYY)
+Video shot with (dropdown)
+Video shot in (SD/HD)
+Raw video captured, processed an archived by (dropdown)
+Raw video checklist and archive (check all that apply)
.. Exterior establishing
.... Clip file name and path
.. Interior establishing
.... Clip file name and path
.. Pit establishing
.... Clip file name and path
.. Interview with owner
.... Clip file name and path
.. Interview with cooker
.... Clip file name and path
.. Interview with customer
.... Clip file name and path
.. Interview with locals
.... Clip file name and path
.. Notes on available footage
+Web video edited by (dropdown)
+Model releases filed and verified by (dropdown) on (DD/MM/YYYY) in: name folder

Comments

[Chris Steller]

Isn't this how Babylon fell?

[Sherri L. McLendon]

This example doesn't look too different from the methodology I might use to research any basic story, listing my question and sources before I start, then collating my data in a file. This is simply the electronic version.

You mean other journalists don't do this type of planning by rote?

Sherri L. McLendon
writer/editor

[Dan]

Sherri, I would really like to buy you a beer.

It's very much like the process a reporter goes through when working a story for print. And I think reporters are well-positioned for this kind of approach... if they can just get past their hostility toward change.

My hope in laying this out this way was that people would say "Well, that's not so exotic. That's just basic logic." Because that's all it is.

Thank you very much for being the first person to see that and comment on it.

[Andy]

It would be great if there were a wizard corresponding to various story types built into every newsroom CMS. Doing a fire story? Take 1 minute and step through this wizard. Restaurant review? Do this one. And so forth.

Suddenly, you've got a bit more structure in the newsroom, more transparency in the newsroom into the reporting process and, most importantly, a standard process for creating structured data. It's taking the piles of notebooks that clutter every reporter's desk and turning them into something of value.