To translate botanical garden plant labels correctly, preserve the scientific taxon, the accession number that connects a living plant to its collection record, and the difference between a verified identification and a provisional one. A public label may include a family, botanical name, common name, geographic origin, collection status and cultivar designation. None of these fields is interchangeable. A fluent translation that changes a taxon or drops an accession suffix can cause visitors, staff and researchers to refer to the wrong living plant.
People searching for botanical garden plant label translation, how to read a plant label, accession number meaning, Latin plant names explained, botanical nomenclature, genus species cultivar, plant provenance and living collection records often want to decode a concise sign rather than translate prose. The correct method is to separate fixed identifiers from explanatory language, preserve names under the appropriate nomenclatural conventions, and explain what a specific garden’s database fields actually mean.
This is a world-facing guide for educators, botanical collection volunteers, translators and students. Its twenty-four worked cases are constructed learning examples, not claims about particular plants in a real garden. Different institutions use different accession formats and internal codes, so check the receiving garden’s published key before expanding a code. The canonical job of this article is interpreting labels attached to living collections, not herbaria, commercial seed packets, conservation assessments or gardening advice.
The visible problem: a garden label is a record pointer, not just a species name
Imagine a living plant marked ‘20173471*B — Potentilla erecta — Rosaceae’. A hurried translation says ‘Potentilla, rose plant, accession 2017-3471, first specimen’. That version may alter the full database key, reduce a precise species to a genus, treat a family as a common name and reverse a suffix indicating a separate individual. Even where a reader understands the general message, the translation no longer points to the same database record. Cambridge University Botanic Garden publishes an explanation of how its own labels use accession numbers and suffixes, showing why a garden-specific key must not be casually standardized.
Begin with a fixed-field ledger: copy the accession string exactly, copy the accepted printed botanical name exactly, distinguish family from common name, record any qualifier such as ‘cf.’ or ‘aff.’, and only then render explanatory prose. If a target-language audience needs more context, expand the explanation beside—not in place of—the source code. This protects the particular plant that the sign is meant to identify.
First principles: fourteen distinctions behind reliable living-collection labels
Taxon versus individual accession
A scientific name classifies a biological kind; an accession identifier links material acquired or tracked by a particular institution to its database record. Two trees with the same taxon can have distinct accessions, and one accession may comprise multiple tracked plants depending on the garden’s system.
Practical translation: Keep the number intact while translating human-readable explanations of the plant. Before publication, a reviewer should locate the same field in the accession database or the garden’s public key. The target-language sentence may be smoother than the source, but it must not introduce a second identity, new place of origin or stronger claim of certainty.
Accession identifier versus planting date
The accession prefix can encode the year material entered a collection in some gardens, but that is not automatically the date it was planted, germinated or collected in the wild. Never convert a year-like prefix into a confident statement of planting date without a confirmed local convention.
Practical translation: ‘Accessioned in 2017’ is different from ‘planted in 2017’. Before publication, a reviewer should locate the same field in the accession database or the garden’s public key. The target-language sentence may be smoother than the source, but it must not introduce a second identity, new place of origin or stronger claim of certainty.
Suffix versus footnote
An appended letter or symbol may distinguish individuals or subaccessions, or be part of a local record code. Deleting a suffix can merge two separate plant identities. Translators should retain punctuation and check whether asterisks or letters have a defined function.
Practical translation: Copy ‘A’ and ‘B’ exactly; explain their role only when documented. Before publication, a reviewer should locate the same field in the accession database or the garden’s public key. The target-language sentence may be smoother than the source, but it must not introduce a second identity, new place of origin or stronger claim of certainty.
Family versus common name
The family field groups related taxa under a botanical classification, while common names are variable and may refer to multiple unrelated plants. Translate or explain the family only with the correct botanical relationship; do not treat a family such as Rosaceae as a visitor-friendly species nickname.
Practical translation: ‘Family: Rosaceae’ and ‘common name: tormentil’ serve different purposes. Before publication, a reviewer should locate the same field in the accession database or the garden’s public key. The target-language sentence may be smoother than the source, but it must not introduce a second identity, new place of origin or stronger claim of certainty.
Genus versus species
In botanical names, a genus alone is less specific than a binomial combining genus and specific epithet. Shortening the full printed name can erase taxonomic identification even when the shortened sentence looks clearer.
Practical translation: Retain both elements and appropriate capitalization. Before publication, a reviewer should locate the same field in the accession database or the garden’s public key. The target-language sentence may be smoother than the source, but it must not introduce a second identity, new place of origin or stronger claim of certainty.
Infraspecific rank versus cultivar
Subspecies, varieties and cultivars are distinct naming situations with different conventions. Avoid interpreting a cultivar epithet as a geographic locality or an infraspecific taxonomic rank.
Practical translation: Use ‘subsp.’, ‘var.’ and quoted cultivar designations according to the source record. Before publication, a reviewer should locate the same field in the accession database or the garden’s public key. The target-language sentence may be smoother than the source, but it must not introduce a second identity, new place of origin or stronger claim of certainty.
Accepted name versus synonym
A garden may have a current accepted name and historical synonyms reflecting changing taxonomic treatment. Do not silently delete the name recorded on an older sign or present a past synonym as an unrelated species without evidence.
Practical translation: Explain ‘formerly listed as’ only when a referenced taxonomic authority supports it. Before publication, a reviewer should locate the same field in the accession database or the garden’s public key. The target-language sentence may be smoother than the source, but it must not introduce a second identity, new place of origin or stronger claim of certainty.
Identification versus determination
A provisional identification may be signalled through qualifiers or collection notes; a determined identity may have an associated determiner and date. A translator cannot remove uncertainty simply because a firm species name sounds better.
Practical translation: Keep ‘cf.’ or an equivalent explicit uncertainty note. Before publication, a reviewer should locate the same field in the accession database or the garden’s public key. The target-language sentence may be smoother than the source, but it must not introduce a second identity, new place of origin or stronger claim of certainty.
Origin versus collection locality
A native distribution range is not the same as the precise locality where a particular accession was collected. A sign saying ‘native to’ describes a broad distribution; a field label saying ‘collected in’ describes an acquisition event.
Practical translation: Keep the prepositions and provenance categories separate. Before publication, a reviewer should locate the same field in the accession database or the garden’s public key. The target-language sentence may be smoother than the source, but it must not introduce a second identity, new place of origin or stronger claim of certainty.
Wild source versus nursery source
Living plants can enter collections through field collection, exchange, cultivation or horticultural sourcing. Do not present a nursery-grown acquisition as wild-collected, or assert a rare provenance from the taxon name alone.
Practical translation: Describe source type exactly as recorded. Before publication, a reviewer should locate the same field in the accession database or the garden’s public key. The target-language sentence may be smoother than the source, but it must not introduce a second identity, new place of origin or stronger claim of certainty.
Conservation status versus cultivation status
A threatened species classification concerns a taxon under a specific assessment; an accession’s condition and display status describe a particular plant. Do not turn ‘rare in cultivation’ into ‘endangered worldwide’, or vice versa.
Practical translation: Use the named assessment and date when a conservation claim is made. Before publication, a reviewer should locate the same field in the accession database or the garden’s public key. The target-language sentence may be smoother than the source, but it must not introduce a second identity, new place of origin or stronger claim of certainty.
Scientific nomenclature versus transliteration
Botanical names use conventions that are not ordinary English sentences. Transliterating them for pronunciation is different from changing a published nomenclatural spelling. Where multilingual scripts require aids, preserve a machine-readable Latin-script scientific name beside any explanatory rendering.
Practical translation: Never translate a species epithet into an invented official taxon. Before publication, a reviewer should locate the same field in the accession database or the garden’s public key. The target-language sentence may be smoother than the source, but it must not introduce a second identity, new place of origin or stronger claim of certainty.
Public label versus database record
A garden may deliberately omit precise provenance, sensitive location or internal notes from visitor signage. Do not fill a concise public label with unapproved internal material. A translation can explain fields without exposing restricted collection data.
Practical translation: Follow the institution’s display and privacy rules. Before publication, a reviewer should locate the same field in the accession database or the garden’s public key. The target-language sentence may be smoother than the source, but it must not introduce a second identity, new place of origin or stronger claim of certainty.
Living plant versus preserved specimen
A living-collection tag identifies material under continuing care, whereas a herbarium sheet records preserved material and its collection history. The two workflows overlap in scientific naming but differ in custody, individual tracking, growth and update obligations.
Practical translation: This guide concerns living displays; use herbarium-specific guidance for dried specimens. Before publication, a reviewer should locate the same field in the accession database or the garden’s public key. The target-language sentence may be smoother than the source, but it must not introduce a second identity, new place of origin or stronger claim of certainty.
A twelve-stage method for translating plant labels and accession records
Step 1: Identify the institution
Record which botanical garden created the label. Field codes are not globally uniform; a convention documented at one garden must not be imported into another without evidence. The operational test is whether a bilingual staff member can move from either label to the same accession, the same plant taxon and the same qualified provenance. Make a record of what you translated, what you copied, what you normalized and what you deliberately left unexplained.
Step 2: Capture the entire printed label
Preserve every digit, accession suffix, scientific name, qualifier, diacritic, family and code before normalizing sentence order. Photograph or transcribe carefully where authorized. The operational test is whether a bilingual staff member can move from either label to the same accession, the same plant taxon and the same qualified provenance. Make a record of what you translated, what you copied, what you normalized and what you deliberately left unexplained.
Step 3: Separate fixed and localizable fields
Protect scientific identifiers, collection numbers and recognized nomenclatural forms from casual wording changes while translating headings and explanations naturally. The operational test is whether a bilingual staff member can move from either label to the same accession, the same plant taxon and the same qualified provenance. Make a record of what you translated, what you copied, what you normalized and what you deliberately left unexplained.
Step 4: Determine the name’s rank
Mark genus, species, subspecies, variety, hybrid designation or cultivar. A translation cannot collapse these ranks without changing which plant the record denotes. The operational test is whether a bilingual staff member can move from either label to the same accession, the same plant taxon and the same qualified provenance. Make a record of what you translated, what you copied, what you normalized and what you deliberately left unexplained.
Step 5: Check the status of the scientific name
Compare the printed name against the institution’s currently accepted name and note whether the garden shows a synonym, a working identification or an unresolved determination. The operational test is whether a bilingual staff member can move from either label to the same accession, the same plant taxon and the same qualified provenance. Make a record of what you translated, what you copied, what you normalized and what you deliberately left unexplained.
Step 6: Interpret accession codes from a local key
When a code appears to contain a year, sequence or subaccession suffix, verify the meaning from garden documentation rather than reverse-engineering from appearance. The operational test is whether a bilingual staff member can move from either label to the same accession, the same plant taxon and the same qualified provenance. Make a record of what you translated, what you copied, what you normalized and what you deliberately left unexplained.
Step 7: Distinguish provenance fields
Keep native range, cultivation source, collection site, donor, supplier and planting location in separate categories. A geographic word can have several possible relationships to the plant. The operational test is whether a bilingual staff member can move from either label to the same accession, the same plant taxon and the same qualified provenance. Make a record of what you translated, what you copied, what you normalized and what you deliberately left unexplained.
Step 8: Preserve qualifier language
Words such as possibly, provisionally identified, cultivated and thought to originate indicate evidence strength. Do not remove them to shorten a visitor sign. The operational test is whether a bilingual staff member can move from either label to the same accession, the same plant taxon and the same qualified provenance. Make a record of what you translated, what you copied, what you normalized and what you deliberately left unexplained.
Step 9: Check common names for audience fit
A common name should clarify a plant to local readers, but it may be ambiguous or region-specific. Keep the scientific name as the stable reference. The operational test is whether a bilingual staff member can move from either label to the same accession, the same plant taxon and the same qualified provenance. Make a record of what you translated, what you copied, what you normalized and what you deliberately left unexplained.
Step 10: Confirm conservation references
When red-list or threatened status appears, verify the named authority, category, date and geographic scope. Avoid transferring old or regional status to the present global population. The operational test is whether a bilingual staff member can move from either label to the same accession, the same plant taxon and the same qualified provenance. Make a record of what you translated, what you copied, what you normalized and what you deliberately left unexplained.
Step 11: Test every identifier independently
Have another editor retype the accession into the collection record or check digit by digit against the original image. Language fluency cannot catch a swapped numeral. The operational test is whether a bilingual staff member can move from either label to the same accession, the same plant taxon and the same qualified provenance. Make a record of what you translated, what you copied, what you normalized and what you deliberately left unexplained.
Step 12: Publish a source-aware visitor label
Use natural target-language prose with the original scientific name and accession intact. Credit the institution’s record, note uncertainties, and avoid revealing internal information not intended for visitors. The operational test is whether a bilingual staff member can move from either label to the same accession, the same plant taxon and the same qualified provenance. Make a record of what you translated, what you copied, what you normalized and what you deliberately left unexplained.
Twenty-four worked cases: preserving individual plant identity
These are invented teaching examples. Some imitate the structure of real records, but every numeral and combination below is a classroom placeholder unless a named institutional record is explicitly cited. Correctness means preserving the relationship among code, name, evidence and the garden’s published meaning, not endorsing a horticultural identification.
Worked case 1: Accession suffix
Source-style field: BG-2020-0042B; individual B. Misleading translation: BG-2020-0042, first plant. Faithful reader-facing version: BG-2020-0042B, the plant identified by suffix B.
The suffix is part of the record identity and should not be inferred from alphabetic order. A reviewer should compare accession code, taxonomic rank, status or event against the source record rather than judging only whether the sentence sounds natural. The exercise is complete when another reader can retrieve the same record and explain why the incorrect version would point to a different plant or a different degree of certainty.
Worked case 2: Year-like prefix
Source-style field: Accession 20191234. Misleading translation: planted in 2019. Faithful reader-facing version: plant bearing accession number 20191234.
A numeric prefix is not proof of a planting date. A reviewer should compare accession code, taxonomic rank, status or event against the source record rather than judging only whether the sentence sounds natural. The exercise is complete when another reader can retrieve the same record and explain why the incorrect version would point to a different plant or a different degree of certainty.
Worked case 3: Family line
Source-style field: FAMILY: Rosaceae. Misleading translation: rose shrub named Rosaceae. Faithful reader-facing version: botanical family: Rosaceae.
A family is a taxonomic grouping, not a species nickname. A reviewer should compare accession code, taxonomic rank, status or event against the source record rather than judging only whether the sentence sounds natural. The exercise is complete when another reader can retrieve the same record and explain why the incorrect version would point to a different plant or a different degree of certainty.
Worked case 4: Binomial spelling
Source-style field: Potentilla erecta. Misleading translation: Potentilla spp.. Faithful reader-facing version: Potentilla erecta, retaining both genus and species.
Replacing a species epithet with spp. broadens the identification. A reviewer should compare accession code, taxonomic rank, status or event against the source record rather than judging only whether the sentence sounds natural. The exercise is complete when another reader can retrieve the same record and explain why the incorrect version would point to a different plant or a different degree of certainty.
Worked case 5: Provisional ID
Source-style field: Quercus cf. robur. Misleading translation: confirmed Quercus robur. Faithful reader-facing version: oak provisionally compared with Quercus robur.
A qualifier signals a tentative identification and must not vanish. A reviewer should compare accession code, taxonomic rank, status or event against the source record rather than judging only whether the sentence sounds natural. The exercise is complete when another reader can retrieve the same record and explain why the incorrect version would point to a different plant or a different degree of certainty.
Worked case 6: Cultivar designation
Source-style field: Acer palmatum ‘Example Red’. Misleading translation: Acer palmatum var. Red. Faithful reader-facing version: Acer palmatum cultivar ‘Example Red’.
A cultivar name is not automatically a botanical variety. A reviewer should compare accession code, taxonomic rank, status or event against the source record rather than judging only whether the sentence sounds natural. The exercise is complete when another reader can retrieve the same record and explain why the incorrect version would point to a different plant or a different degree of certainty.
Worked case 7: Subspecies rank
Source-style field: Taxon subsp. minor. Misleading translation: species named Minor. Faithful reader-facing version: subspecies minor of the named species.
The infraspecific rank remains part of the name. A reviewer should compare accession code, taxonomic rank, status or event against the source record rather than judging only whether the sentence sounds natural. The exercise is complete when another reader can retrieve the same record and explain why the incorrect version would point to a different plant or a different degree of certainty.
Worked case 8: Variety rank
Source-style field: Taxon var. alba. Misleading translation: white flowering plant. Faithful reader-facing version: botanical variety alba, as recorded.
A Latin epithet may allude to colour but still functions as a name. A reviewer should compare accession code, taxonomic rank, status or event against the source record rather than judging only whether the sentence sounds natural. The exercise is complete when another reader can retrieve the same record and explain why the incorrect version would point to a different plant or a different degree of certainty.
Worked case 9: Hybrid marker
Source-style field: Genus × species hybrid notation. Misleading translation: multiplication result of two plants. Faithful reader-facing version: hybrid mark retained as part of botanical designation.
Typography can carry taxonomic meaning. A reviewer should compare accession code, taxonomic rank, status or event against the source record rather than judging only whether the sentence sounds natural. The exercise is complete when another reader can retrieve the same record and explain why the incorrect version would point to a different plant or a different degree of certainty.
Worked case 10: Common name
Source-style field: Common name: ironwood (regional). Misleading translation: official worldwide species name Ironwood. Faithful reader-facing version: regional common name ‘ironwood’.
Common names can be shared by unrelated plants in different regions. A reviewer should compare accession code, taxonomic rank, status or event against the source record rather than judging only whether the sentence sounds natural. The exercise is complete when another reader can retrieve the same record and explain why the incorrect version would point to a different plant or a different degree of certainty.
Worked case 11: Native range
Source-style field: Native range: East Asia. Misleading translation: collected in East Asia. Faithful reader-facing version: species naturally occurs in parts of East Asia.
Distribution does not establish the origin of this particular accession. A reviewer should compare accession code, taxonomic rank, status or event against the source record rather than judging only whether the sentence sounds natural. The exercise is complete when another reader can retrieve the same record and explain why the incorrect version would point to a different plant or a different degree of certainty.
Worked case 12: Field provenance
Source-style field: Collected at locality L-17. Misleading translation: native to locality L-17. Faithful reader-facing version: accession recorded as collected at locality code L-17.
Collection locality is an event in a plant’s history, not necessarily its full natural range. A reviewer should compare accession code, taxonomic rank, status or event against the source record rather than judging only whether the sentence sounds natural. The exercise is complete when another reader can retrieve the same record and explain why the incorrect version would point to a different plant or a different degree of certainty.
Worked case 13: Nursery acquisition
Source-style field: Source: nursery purchase. Misleading translation: wild collected specimen. Faithful reader-facing version: acquired from a nursery.
Cultivation source must not be upgraded into wild provenance. A reviewer should compare accession code, taxonomic rank, status or event against the source record rather than judging only whether the sentence sounds natural. The exercise is complete when another reader can retrieve the same record and explain why the incorrect version would point to a different plant or a different degree of certainty.
Worked case 14: Exchange source
Source-style field: Received through institutional exchange. Misleading translation: donated directly from wild population. Faithful reader-facing version: received from another institution through an exchange.
Origin, provider and method of acquisition are different records. A reviewer should compare accession code, taxonomic rank, status or event against the source record rather than judging only whether the sentence sounds natural. The exercise is complete when another reader can retrieve the same record and explain why the incorrect version would point to a different plant or a different degree of certainty.
Worked case 15: Planting location
Source-style field: Display bed 4C. Misleading translation: specimen group 4C. Faithful reader-facing version: currently located in display bed 4C.
Location codes can change; they should not replace the stable accession identifier. A reviewer should compare accession code, taxonomic rank, status or event against the source record rather than judging only whether the sentence sounds natural. The exercise is complete when another reader can retrieve the same record and explain why the incorrect version would point to a different plant or a different degree of certainty.
Worked case 16: Conservation label
Source-style field: Assessment: vulnerable under named list. Misleading translation: all remaining plants at this garden dying. Faithful reader-facing version: taxon classified as vulnerable under the cited assessment.
A taxon-level assessment is not a diagnosis of an individual plant. A reviewer should compare accession code, taxonomic rank, status or event against the source record rather than judging only whether the sentence sounds natural. The exercise is complete when another reader can retrieve the same record and explain why the incorrect version would point to a different plant or a different degree of certainty.
Worked case 17: Assessment date
Source-style field: Threat category, assessed 2018. Misleading translation: current 2026 official category. Faithful reader-facing version: category reported from a 2018 assessment.
Date and authority are part of the conservation statement. A reviewer should compare accession code, taxonomic rank, status or event against the source record rather than judging only whether the sentence sounds natural. The exercise is complete when another reader can retrieve the same record and explain why the incorrect version would point to a different plant or a different degree of certainty.
Worked case 18: Synonym
Source-style field: Name A, synonym Name B. Misleading translation: two different accessioned plants. Faithful reader-facing version: one taxon listed under an accepted name and a synonym.
Alternative names do not necessarily imply two different individuals. A reviewer should compare accession code, taxonomic rank, status or event against the source record rather than judging only whether the sentence sounds natural. The exercise is complete when another reader can retrieve the same record and explain why the incorrect version would point to a different plant or a different degree of certainty.
Worked case 19: Formerly labelled
Source-style field: Previously listed as Name B. Misleading translation: Name B remains official. Faithful reader-facing version: earlier garden label used Name B.
The history of a label must not be confused with current taxonomy. A reviewer should compare accession code, taxonomic rank, status or event against the source record rather than judging only whether the sentence sounds natural. The exercise is complete when another reader can retrieve the same record and explain why the incorrect version would point to a different plant or a different degree of certainty.
Worked case 20: Identification date
Source-style field: Determined by curator, 2021. Misleading translation: collected by curator in 2021. Faithful reader-facing version: plant identification reviewed by curator in 2021.
Determination and collection are distinct events. A reviewer should compare accession code, taxonomic rank, status or event against the source record rather than judging only whether the sentence sounds natural. The exercise is complete when another reader can retrieve the same record and explain why the incorrect version would point to a different plant or a different degree of certainty.
Worked case 21: Sensitive provenance
Source-style field: Locality suppressed on public sign. Misleading translation: exact coordinates provided by translator. Faithful reader-facing version: precise collection locality not displayed.
Omitting restricted data is not a licence to reconstruct it. A reviewer should compare accession code, taxonomic rank, status or event against the source record rather than judging only whether the sentence sounds natural. The exercise is complete when another reader can retrieve the same record and explain why the incorrect version would point to a different plant or a different degree of certainty.
Worked case 22: Uncertain ancestry
Source-style field: Possible hybrid origin. Misleading translation: confirmed cross of two named parents. Faithful reader-facing version: possible hybrid origin; parentage unconfirmed.
A translator must not infer pedigree from a familiar horticultural pattern. A reviewer should compare accession code, taxonomic rank, status or event against the source record rather than judging only whether the sentence sounds natural. The exercise is complete when another reader can retrieve the same record and explain why the incorrect version would point to a different plant or a different degree of certainty.
Worked case 23: Multiple plants
Source-style field: Accession includes plants A, B and C. Misleading translation: three different species. Faithful reader-facing version: three tracked individuals associated with the same accession.
Subaccessions need not be new species or unrelated accession events. A reviewer should compare accession code, taxonomic rank, status or event against the source record rather than judging only whether the sentence sounds natural. The exercise is complete when another reader can retrieve the same record and explain why the incorrect version would point to a different plant or a different degree of certainty.
Worked case 24: Record discrepancy
Source-style field: Label pending database review. Misleading translation: fully verified identity. Faithful reader-facing version: label currently under review against the garden database.
Discrepancy status is operational information, not an embarrassment to edit away. A reviewer should compare accession code, taxonomic rank, status or event against the source record rather than judging only whether the sentence sounds natural. The exercise is complete when another reader can retrieve the same record and explain why the incorrect version would point to a different plant or a different degree of certainty.
Common failure modes and the exact repair
Failure 1: A suffix disappears
Perform a byte-for-byte comparison of the accession string, including hyphens and letters. A useful counterexample is to imagine two nearby signs with the same species name but different acquisition histories. If the translated wording would make their records indistinguishable, it has lost a necessary field. Record the cause of the mistake so subsequent labels can be checked systematically.
Failure 2: A genus replaces a full species name
Keep genus and species together unless the source itself provides only genus-level identification. A useful counterexample is to imagine two nearby signs with the same species name but different acquisition histories. If the translated wording would make their records indistinguishable, it has lost a necessary field. Record the cause of the mistake so subsequent labels can be checked systematically.
Failure 3: A family becomes a common name
Label the taxonomic rank explicitly, then provide a separate familiar name if the garden supports it. A useful counterexample is to imagine two nearby signs with the same species name but different acquisition histories. If the translated wording would make their records indistinguishable, it has lost a necessary field. Record the cause of the mistake so subsequent labels can be checked systematically.
Failure 4: An accession year is described as a planting date
Identify what the garden’s code encodes and avoid inventing a horticultural timeline. A useful counterexample is to imagine two nearby signs with the same species name but different acquisition histories. If the translated wording would make their records indistinguishable, it has lost a necessary field. Record the cause of the mistake so subsequent labels can be checked systematically.
Failure 5: A nursery plant becomes wild-collected
Translate source-of-acquisition terminology without romanticizing its provenance. A useful counterexample is to imagine two nearby signs with the same species name but different acquisition histories. If the translated wording would make their records indistinguishable, it has lost a necessary field. Record the cause of the mistake so subsequent labels can be checked systematically.
Failure 6: A synonym is portrayed as another plant
Retain the relationship between accepted name and synonym as the institution records it. A useful counterexample is to imagine two nearby signs with the same species name but different acquisition histories. If the translated wording would make their records indistinguishable, it has lost a necessary field. Record the cause of the mistake so subsequent labels can be checked systematically.
Failure 7: A cultivar is mislabelled as a botanical subspecies
Keep cultivar formatting and nomenclatural distinctions intact. A useful counterexample is to imagine two nearby signs with the same species name but different acquisition histories. If the translated wording would make their records indistinguishable, it has lost a necessary field. Record the cause of the mistake so subsequent labels can be checked systematically.
Failure 8: An old threat status becomes current
Attach the cited assessment year and authority and confirm its scope. A useful counterexample is to imagine two nearby signs with the same species name but different acquisition histories. If the translated wording would make their records indistinguishable, it has lost a necessary field. Record the cause of the mistake so subsequent labels can be checked systematically.
Failure 9: A provisional determination becomes certain
Preserve qualifiers such as cf., aff., provisional or awaiting confirmation. A useful counterexample is to imagine two nearby signs with the same species name but different acquisition histories. If the translated wording would make their records indistinguishable, it has lost a necessary field. Record the cause of the mistake so subsequent labels can be checked systematically.
Failure 10: A bed location substitutes for the accession
Maintain separate stable identity and changeable physical location fields. A useful counterexample is to imagine two nearby signs with the same species name but different acquisition histories. If the translated wording would make their records indistinguishable, it has lost a necessary field. Record the cause of the mistake so subsequent labels can be checked systematically.
Failure 11: Internal locality data is exposed
Translate only the approved public record, retaining any redaction or privacy restriction. A useful counterexample is to imagine two nearby signs with the same species name but different acquisition histories. If the translated wording would make their records indistinguishable, it has lost a necessary field. Record the cause of the mistake so subsequent labels can be checked systematically.
Failure 12: A visitor-friendly common name obscures identity
Put the scientific name and accession in a form that can be cross-checked even if the local common name varies. A useful counterexample is to imagine two nearby signs with the same species name but different acquisition histories. If the translated wording would make their records indistinguishable, it has lost a necessary field. Record the cause of the mistake so subsequent labels can be checked systematically.
Guided practice: twelve exercises for accurate collection-label translation
Practice 1: Rebuild a record
Write a label using a scientific name, an accession number and a public location; then ask a second reader to retrieve each field. Evaluate your work using three independent checks: name and rank fidelity, accession-key fidelity, and factual claim fidelity. A translation can pass the language check and fail the identity check; a responsible review makes those failures visible rather than concealing them beneath smooth prose.
Practice 2: Compare two same-species plants
Give two plants the same scientific name but different accession suffixes. Produce translations that keep each individual distinct. Evaluate your work using three independent checks: name and rank fidelity, accession-key fidelity, and factual claim fidelity. A translation can pass the language check and fail the identity check; a responsible review makes those failures visible rather than concealing them beneath smooth prose.
Practice 3: Read an accession key
Consult a botanical garden’s published explanation of accession fields and explain the difference between a database identifier and a planting date. Evaluate your work using three independent checks: name and rank fidelity, accession-key fidelity, and factual claim fidelity. A translation can pass the language check and fail the identity check; a responsible review makes those failures visible rather than concealing them beneath smooth prose.
Practice 4: Preserve rank
Create five example names at genus, species, subspecies, variety and cultivar levels; mark what can and cannot be translated into ordinary vocabulary. Evaluate your work using three independent checks: name and rank fidelity, accession-key fidelity, and factual claim fidelity. A translation can pass the language check and fail the identity check; a responsible review makes those failures visible rather than concealing them beneath smooth prose.
Practice 5: Handle an uncertain determination
Convert a speculative plant identification into accessible English without presenting the suspected species as confirmed. Evaluate your work using three independent checks: name and rank fidelity, accession-key fidelity, and factual claim fidelity. A translation can pass the language check and fail the identity check; a responsible review makes those failures visible rather than concealing them beneath smooth prose.
Practice 6: Distinguish geography
Write separate phrases for native range, collection locality, supplier address and present garden bed. Evaluate your work using three independent checks: name and rank fidelity, accession-key fidelity, and factual claim fidelity. A translation can pass the language check and fail the identity check; a responsible review makes those failures visible rather than concealing them beneath smooth prose.
Practice 7: Check a taxonomic synonym
Explain ‘previously listed as’ to a visitor while preserving which name is current according to the cited institutional record. Evaluate your work using three independent checks: name and rank fidelity, accession-key fidelity, and factual claim fidelity. A translation can pass the language check and fail the identity check; a responsible review makes those failures visible rather than concealing them beneath smooth prose.
Practice 8: Conservation caution
Draft a short label that mentions a dated assessment category without making a prediction about the individual plant. Evaluate your work using three independent checks: name and rank fidelity, accession-key fidelity, and factual claim fidelity. A translation can pass the language check and fail the identity check; a responsible review makes those failures visible rather than concealing them beneath smooth prose.
Practice 9: Common-name ambiguity
Find two species sharing a regional common name and show why the binomial must remain visible. Evaluate your work using three independent checks: name and rank fidelity, accession-key fidelity, and factual claim fidelity. A translation can pass the language check and fail the identity check; a responsible review makes those failures visible rather than concealing them beneath smooth prose.
Practice 10: Two-language proof
Have one person translate field headings and another independently verify all fixed names and identifiers. Evaluate your work using three independent checks: name and rank fidelity, accession-key fidelity, and factual claim fidelity. A translation can pass the language check and fail the identity check; a responsible review makes those failures visible rather than concealing them beneath smooth prose.
Practice 11: Privacy rehearsal
Take a mock record with confidential source coordinates and make a visitor-safe version that preserves approved context. Evaluate your work using three independent checks: name and rank fidelity, accession-key fidelity, and factual claim fidelity. A translation can pass the language check and fail the identity check; a responsible review makes those failures visible rather than concealing them beneath smooth prose.
Practice 12: Transfer to another garden
Translate a label from an unfamiliar institution, checking its specific code legend instead of imposing the convention you already learned. Evaluate your work using three independent checks: name and rank fidelity, accession-key fidelity, and factual claim fidelity. A translation can pass the language check and fail the identity check; a responsible review makes those failures visible rather than concealing them beneath smooth prose.
Frequently asked questions
What is an accession number in a botanical garden?
It is an institution’s identifier connecting collected or acquired plant material to a living-collection database record. Formats vary; a number may include year, sequence and individual suffixes depending on that garden. The safest next step is to check the source institution’s local conventions rather than assume a globally uniform numbering system. Good translation keeps the public description readable while protecting the identifier that makes the collection searchable.
Does the accession number show when a tree was planted?
Not necessarily. In some institutions a prefix relates to accession year. Planting and germination can occur at different times, so check the database rather than guessing from digits. The safest next step is to check the source institution’s local conventions rather than assume a globally uniform numbering system. Good translation keeps the public description readable while protecting the identifier that makes the collection searchable.
Should scientific names be translated into the target language?
Preserve the scientific name as a stable identification, while translating explanatory headings and adding an appropriate common name separately when useful. The safest next step is to check the source institution’s local conventions rather than assume a globally uniform numbering system. Good translation keeps the public description readable while protecting the identifier that makes the collection searchable.
What is the difference between genus and species?
Genus groups related kinds; the binomial genus plus specific epithet normally denotes a more precise taxon. Dropping the epithet can change what the sign identifies. The safest next step is to check the source institution’s local conventions rather than assume a globally uniform numbering system. Good translation keeps the public description readable while protecting the identifier that makes the collection searchable.
What does ‘cf.’ mean on a specimen label?
It signals a comparison or uncertain identification in many taxonomic contexts. Translate its effect as provisional identification rather than hiding the qualifier. The safest next step is to check the source institution’s local conventions rather than assume a globally uniform numbering system. Good translation keeps the public description readable while protecting the identifier that makes the collection searchable.
Why retain cultivar quotes and ranks?
They convey that the printed name belongs to a horticultural designation, not necessarily a botanical variety or subspecies. The safest next step is to check the source institution’s local conventions rather than assume a globally uniform numbering system. Good translation keeps the public description readable while protecting the identifier that makes the collection searchable.
Can a common name replace a Latin botanical name?
No, not when precise identification is required. Common names can vary by language and region or refer to more than one taxon. The safest next step is to check the source institution’s local conventions rather than assume a globally uniform numbering system. Good translation keeps the public description readable while protecting the identifier that makes the collection searchable.
Is a botanic garden tag the same as a herbarium sheet?
Both may name taxa and provenance, but a living plant tag also connects to ongoing cultivation and individual tracking. Preserved specimen records require their own context. The safest next step is to check the source institution’s local conventions rather than assume a globally uniform numbering system. Good translation keeps the public description readable while protecting the identifier that makes the collection searchable.
Does ‘native to’ tell me where this plant was collected?
No. Native range describes where a taxon occurs naturally, while collection locality records a specific acquisition event if known. The safest next step is to check the source institution’s local conventions rather than assume a globally uniform numbering system. Good translation keeps the public description readable while protecting the identifier that makes the collection searchable.
What if a label appears inconsistent with the database?
Do not silently edit either record. Document the discrepancy, ask the responsible collection staff, and publish the approved wording. The safest next step is to check the source institution’s local conventions rather than assume a globally uniform numbering system. Good translation keeps the public description readable while protecting the identifier that makes the collection searchable.
Can I add the plant’s conservation status?
Only with an authoritative assessment, geographic scope and date. A translator should not invent a status from rarity or appearance. The safest next step is to check the source institution’s local conventions rather than assume a globally uniform numbering system. Good translation keeps the public description readable while protecting the identifier that makes the collection searchable.
How do I verify field meanings?
Start with the garden’s published label key and approved living-collection records. The Cambridge University Botanic Garden provides a clear example of how accession numbers connect labels to database records. The safest next step is to check the source institution’s local conventions rather than assume a globally uniform numbering system. Good translation keeps the public description readable while protecting the identifier that makes the collection searchable.
Contextual next routes and authoritative learning sources
The general method is covered in Translate Meaning, Not Just Words, Context, Tone and Register and Idioms and Culture. For vocabulary support, visit the Vocabulary Learning Hub and How English Works. The Top Ways to Translate Correctly index keeps each specialist lesson in a distinct route.
For related but nonidentical tasks, use the Herbarium Specimen Label Translation Guide for preserved specimens, and the Public Aquarium Species Label Guide for animal display labels. Their identity systems should not be copied uncritically into living botanical collections.
Reference sources: Cambridge University Botanic Garden: Understanding Plant Labels; Google Search Central: helpful, people-first content. Use the latest approved institutional accession guidance for the actual sign being translated; the practice records here are illustrative.
For the series-wide rules on preserving consistent specialist vocabulary, consult Terminology, Glossaries and Translation Quality Checks. That lesson owns termbase decisions and reusable translation verification; this article teaches the distinct, domain-specific application.
The final standard is simple but demanding: someone using the translated sign must be able to locate the same individual plant in the garden’s living-collection records, understand the same degree of identification certainty and distinguish the plant’s name from its provenance and care. That is a correct translation rather than a merely attractive label.