Reading Botanical Names, Plant Parts, and Extract Wording on Labels

Preserve the complete botanical declaration

A botanical label row can include a common name, Latin binomial, author abbreviation, plant part, preparation, extract ratio, solvent wording, source qualifier, declared amount, and footnote. Transcribe the entire row before splitting it into fields. Preserve parentheses, order, capitalization, and words such as from, as, extract, powder, oil, or concentrate. A short ingredient name alone may discard the details needed to distinguish two package declarations.

Store the verbatim row as the primary evidence, then add structured fields for common name, scientific name as printed, plant part, preparation text, declared amount, unit, serving basis, and unresolved fragments. Do not fill missing parts from another product or a reference database. Taxonomic resources can help reviewers check spelling and accepted names, but they do not prove what material a particular package contains beyond its own evidence.

Keep common and scientific names source-aware

Common names can refer to different taxa across regions, and a species can have several common names. Record both forms when the label provides them. If an external taxonomy uses a currently accepted name different from the printed name, retain the label text and add the reference name as a separate research field with source and date. Do not silently modernize the package declaration or treat a synonym match as a product authentication.

Scientific names are often italicized in editorial presentation, but the evidence layer should preserve spelling and abbreviations exactly. Automated validation can flag binomials that appear incomplete or unusual for manual review; it should not auto-correct them. Hybrids, subspecies, varieties, fungi, algae, and non-botanical organisms may require additional taxonomy fields, so a schema should allow unresolved identity rather than forcing every row into a two-word plant template.

Treat plant part as an independent comparison field

Root, leaf, fruit, seed, flower, bark, aerial parts, whole plant, and other part terms are material components of the printed identity. Capture the label’s exact wording and do not assume that two products with the same common name use the same part. A missing part should be recorded as not stated on the reviewed row, not supplied from a typical-use reference or another listing.

A comparison can align botanical name and plant part, but it should stop when either differs or is unclear. Do not describe one part as better, stronger, or interchangeable based on the name alone. Marketplace filters often omit plant parts, and manufacturer web copy can be more detailed than package images. Display those as separate sources and mark whether the added detail is printed on the current package.

Parse preparation, ratio, and marker wording cautiously

Extract ratios, dry-equivalent statements, concentration language, solvents, and standardization or marker-compound statements can use different grammatical structures. Quote the full phrase and break out values only when their subject and basis are explicit. A ratio should remain attached to the preparation it describes. Do not multiply a declared amount by a ratio to create an equivalent quantity unless a dedicated, reviewed methodology establishes exactly what the label means.

A named marker or printed percentage is a package statement, not confirmation of the finished product’s composition. Store it separately from laboratory results and certificates. Similar percentages can use different denominators or specifications, while similar extract ratios can be described under different conventions. MIHEN should not translate these fields into relative strength or expected performance. Its safe role is to make the wording and comparison boundary visible.

Build a botanical record that exposes uncertainty

For each row, publish product version, market, serving basis, verbatim declaration, parsed names, plant part, preparation, ratio or marker wording, amount, source image, capture date, and reviewer status. Use explicit states such as scientific name printed, common name only, plant part not stated, extract basis unclear, or seller detail not found on package. Link taxonomy references without presenting them as package verification.

A second reviewer should confirm Latin spelling, decimals, colons, percentages, and parentheses. Corrections must preserve the original capture and explain whether the package changed or transcription was corrected. Provide a visible field glossary so readers can distinguish the printed common name, scientific name, plant part, preparation, and any externally referenced taxonomy. Exported comparison tables should carry those definitions too, rather than reducing the row to one normalized ingredient name. This guide does not identify unknown plant material, evaluate composition, establish equivalence, or select a preparation. It creates a careful language record that supports later evidence review without manufacturing facts the label does not contain.

• Transcribe the complete botanical row before parsing individual fields.
• Keep common and scientific names exactly as printed.
• Record plant part as a separate field and never infer a missing part.
• Attach preparation and extract-ratio wording to the subject it describes.
• Separate label marker claims from laboratory documents.
• Use taxonomy sources as references, not product authentication.
• Block comparison when identity, part, preparation, or basis differs.
• Require manual review of spelling, punctuation, ratios, and percentages.