Submit

• Identity: restaurant name and branch address, city, state or region, and country. For economic data, identify the asset or series.
• Observation: the original value, its unit or rating scale, and the date it was observed. Separate the visit date from the date you collected the source.
• Evidence: a source URL or a clear source description, plus how you collected the data. Add a sample size if a value summarizes multiple observations.
• Limits: label estimates, unknown branches, sponsorship, and missing fields. Leave missing values blank or use null; do not change them to zero.

For a menu price, include the order total, currency, number of wing pieces, bone-in or boneless, and whether tax, tip, sides, or delivery fees are included. Send the original price; we can calculate its wing value.

Share only material you can contribute. Remove personal information, account details, and private conversation links. Source links and factual observations are more useful than copied articles or full review text.

1. Open jongos/wingmath, sign in, and fork the data repository.
2. Create a file in submissions/. Use a descriptive name such as 2026-09-15-example-wings.json. Accepted structured formats are .json, .yaml, .yml, and a plain .html data table.
3. Add the source and method in your file or a companion note. Keep one consistent set of field names and preserve original values.
4. Open a pull request explaining what you collected or corrected. Do not overwrite an older snapshot without explaining the correction.

Illustrative examples only: replace the fictional restaurant and every example value with your own evidence. The source_url must point to the actual source.

JSON

{
  "restaurant_name": "Example Wings",
  "branch_address": "123 Example Street, Atlanta, GA, US",
  "observed_at": "2026-09-15",
  "metric": "menu_order_price",
  "value": 17.50,
  "currency": "USD",
  "wing_quantity": 10,
  "wing_type": "bone-in",
  "tax_included": false,
  "source_url": "https://example.com/menu",
  "notes": "Regular order; excludes tip and delivery."
}

Use valid JSON: double quotes, numbers as numbers, and no comments or trailing commas. For multiple observations, use an array of records.

YAML

restaurant_name: Example Wings
branch_address: 123 Example Street, Atlanta, GA, US
observed_at: "2026-09-15"
metric: menu_order_price
value: 17.50
currency: USD
wing_quantity: 10
wing_type: bone-in
tax_included: false
source_url: https://example.com/menu
notes: Regular order; excludes tip and delivery.

Indent with spaces, quote dates, and use a list for multiple records. Avoid executable tags, custom objects, and secrets.

HTML data table

<table>
  <caption>Example only: menu price observations</caption>
  <thead><tr>
    <th>restaurant_name</th><th>branch_address</th>
    <th>observed_at</th><th>value</th>
    <th>currency</th><th>wing_quantity</th>
    <th>source_url</th>
  </tr></thead>
  <tbody><tr>
    <td>Example Wings</td><td>123 Example Street, Atlanta, GA, US</td>
    <td>2026-09-15</td><td>17.50</td>
    <td>USD</td><td>10</td>
    <td>https://example.com/menu</td>
  </tr></tbody>
</table>

Submit a static table with column headers and one observation per row. Include unit and scope notes in the caption or a companion file. HTML is accepted as a data format: omit scripts, forms, tracking, styling, and complete website copies.

CSV: use UTF-8, a header row, and one observation per row. Keep dates in YYYY-MM-DD format. Put units and currency in their own columns; keep blank values blank.

restaurant_name,city,state,observed_at,value,currency,wing_quantity,source_url
Example Wings,Atlanta,GA,2026-09-15,17.50,USD,10,https://example.com/menu

Excel: use .xlsx or .xls, clear tab names, a single header row per table, and no merged data cells. Include a Sources or Notes tab explaining fields, branches, units, and collection methods. Keep original values; if formulas are necessary, include their underlying inputs and saved results. Remove macros, passwords, and external data connections.

Text: upload a UTF-8 .txt file. Group each observation under a restaurant or dataset heading and label the date, location, value, units, source, and notes. Separate observations with a blank line.

Choose one file, up to 5 MiB. Include branch addresses and price scope even if the short CSV example omits them. For larger collections, split files into clearly named batches. JSON, YAML, and HTML belong in the GitHub channel.

The survey form is not available yet, and the placeholder above does not collect responses. Prepare the restaurant and exact branch, visit date, wing style and flavor, order size, price, and what you personally observed about texture, meat, sauce, and service.

Keep firsthand experience separate from recommendations you heard elsewhere. Preserve the scale for any score you report, and label complimentary meals or sponsorship. Until the survey opens, you can submit these notes as a text file.

Paste the full public video or post URL from YouTube, TikTok, Instagram, or another host. Link the individual video rather than a creator profile, playlist, search result, or private download. Check that someone else can open it.

Include the creator, restaurant and branch, recording or visit date if known, and a timestamp such as 02:15. For several relevant moments, list timestamps and what each shows in the notes. Preserve a creator’s rating scale and distinguish the upload date from the visit date.

Tell us whether the video shows a tasting, menu price, review, or historical account, and note sponsorship if disclosed. A link can be submitted without uploading or copying the video. Some platforms restrict access; an inaccessible video remains unverified rather than being treated as evidence against a restaurant.

Use a subject like WingMath data: restaurant or dataset — observation date. In the body, include the restaurant/branch or dataset, original observation and units, date, source links, collection method, and any limitations. Attach clearly named CSV, Excel, or text files, or paste public video links with timestamps. Never email passwords, private account exports, or payment details.

Document and video forms return a receipt ID after saving to the submission queue. Keep that ID for your records. Files are stored for review and are not automatically published, executed, or added to the research database’s verified datasets. GitHub pull requests are visible according to the repository’s access settings.

Review considers source access, restaurant identity, dates, units, duplicates, and whether an observation is measured or estimated. Accepted data may be included in WingMath’s open datasets with its source and limitations. No ranking position, acceptance, or review time is guaranteed. For a correction or an additional file, mention the earlier receipt ID in your notes.