Skip to content

Main content

Food Composition Missing Vs Trace Token Tool

Distinguish explicitly supplied food-composition availability codes without replacing trace or missing quantities with zero.

Loading tool…

Description

Label a food-composition component's supplied missingness or trace state.

Dietary arithmetic depends on as-purchased versus edible mass, per-serving versus per-100-gram bases, measured versus trace states and recall periods. A recorded allergen list is not a verified allergen-free declaration. Portion counts, label intervals and mass differences use supplied assumptions rather than establishing actual intake or nutritional suitability.

Label a food-composition component's supplied missingness or trace state.

When to use this tool

Use Food Composition Missing Vs Trace Token when you already have componentId, status and need to label a food-composition component's supplied missingness or trace state.

How to use the tool and how it works

  1. Enter componentId, status. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read label. Use the output convention below.

Require componentId nonempty and status measured/trace/missing/not-applicable; append the status.1

Input fieldMeaning and unitsAccepted input
componentIdComponent IdRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
statusPreserves measured/trace/missing/not-applicable categories without a numeric imputation.Required. Text; one of "measured", "trace", "missing", "not-applicable"; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
labelLabelRequired. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "componentId": "C17",
    "status": "trace"
  },
  "output": {
    "label": "C17 [trace]"
  }
}

Limitations and assumptions

  • No numeric amount is returned or imputed. Trace and missing are not treated as measured zero, and no nutritional conclusion is made.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.

Alternative or Complementary methods

Check original food labels, composition sources, ingredient/allergen information and dietary records before combining amounts. Use a complete appropriately interpreted dietary assessment when requirements or suitable intake matter; local scaling and source labels do not make those judgments.

References

  1. Calculation and input contract: dietetics/food-composition-missing-vs-trace-token — tool.io

Similar or alternative tools