Gecko RFQ Preparation: Names, Record References, and Open Questions
By GEKUMI
Information worth including in a gecko enquiry starts with a clear account of the name and reference you are discussing. Keep the reference as supplied, explain what it identifies where that is known, and distinguish a checked scientific-name match from a result that still needs clarification. These notes help frame a precise question without filling gaps by guesswork.
This checklist focuses on the quality of name and reference information. It is a buyer-side preparation aid, not a complete RFQ form or a statement of GEKUMI's required fields.
Explain what the reference identifies
In the Darwin Core vocabulary, organismID identifies an organism rather than the digital record describing it. That distinction is useful when preparing an enquiry: an identifier for an animal and an identifier for a record are different reference questions. The vocabulary does not establish what a particular supplier's ID means.
Before copying a reference into your message, consider checking what it points to. If its meaning is unclear, retain the original reference and ask what it identifies. Do not describe a record reference as confirmed individual-animal identity simply because it appears beside a name.
Describe the scientific-name match accurately
GBIF's taxonomy-interpretation documentation describes fuzzy matches, higher-taxon matches and unmatched names. A returned result therefore needs to be read with its match scope. A higher-taxon or fuzzy result should not be presented as an exact species identification. This is a name-matching distinction, not a finding about the particular animal in your enquiry.
Helpful details to provide are the scientific-name spelling you received, the reference used to check it and the reported match result, if you have checked one. Keep a differing spelling or unresolved result visible. If you have not checked the name, say so rather than presenting it as confirmed.
Turn missing information into a specific question
Before sending an enquiry, consider preparing a short information-to-question table. The prompts below are suggestions derived from the identity and name-matching distinctions; they are not required submission fields. Leave the value blank where you do not know it and use the question to explain what needs clarification.
| Information to review | What you can record | Question if unresolved |
|---|---|---|
| Supplied reference | The reference exactly as received | What does this reference identify? |
| Meaning of the reference | The stated relationship to an organism or digital record, where known | Is its meaning documented, or still unclear? |
| Scientific-name spelling | The supplied name without a guessed correction | Which spelling needs checking? |
| Name-check result | The source used and its reported match scope, if checked | Is this an exact species result, a fuzzy or higher-taxon result, or no match? |
| Open point | The specific connection you have not established | What information would clarify this name or reference? |
Review the notes once more before sending them. Keep the supplied information, the result of any check and the remaining question separate. That allows you to ask about a missing connection without asserting that an animal has already been identified. No specimen, buyer or completed transaction is invented in this worksheet.
Keep the checklist's scope clear
A well-labelled reference and a name-match result are information for discussion. Neither source used here establishes an animal's current availability, provenance or legal eligibility. This article supplies no conclusion about those matters and no quotation, allocation or shipment decision.
For the wider sequence of procurement stages, Review the Trade Process. To raise the name or reference question you have prepared, Contact Trade Team.
Sources and scope
- TDWG, Darwin Core Quick Reference Guide — organismID. Used for the distinction between an organism and the digital record describing it.
- GBIF, Taxonomy interpretation. Used for scientific-name match scope and issue flags.
Both sources were accessed on October 3, 2026, in America/Chicago (2026-10-04T01:52:09.942925+00:00). Their recorded publication/update dates are unknown. This source-access date is not an article publication date. These sources concern biodiversity records and name matching; their use here does not define commercial or import requirements.