Description
Count branches recorded for one identification-key couplet.
Taxonomic names, authorship strings, nomenclatural types and source-defined taxon concepts are related but distinct records. A literal token parser or source-label comparison can preserve a stated convention without resolving accepted taxonomy or establishing compliance with the applicable nomenclatural code.
Count branches recorded for one identification-key couplet.
When to use this tool
Use Key Couplet Branch Count when checking the stated taxonomic source, name-token, date or concept-support convention.
How to use the tool and how it works
- Enter coupletIds, branchLabels, requestedCouplet. Follow any array-alignment requirements below. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read distinctBranches, records. Use the output convention below.
Count branches recorded for one identification-key couplet. Require aligned coupletIds/branchLabels; return matching record count and distinct matching branch labels.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| coupletIds | Couplet Ids | Required. Array of text; maximum UTF-16 length 8192; maximum items 256. |
| branchLabels | Branch Labels | Required. Array of text; maximum UTF-16 length 8192; maximum items 256. |
| requestedCouplet | Requested Couplet | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| distinctBranches | Distinct supplied branch labels for the requested couplet; need not equal two. | Required. Safe integer. |
| records | Records | Required. Safe integer. |
{
"input": {
"coupletIds": [
"1",
"1",
"2"
],
"branchLabels": [
"a",
"b",
"a"
],
"requestedCouplet": "1"
},
"output": {
"distinctBranches": 2,
"records": 2
}
}Limitations and assumptions
- A couplet need not have exactly two branches under this input contract; key validity, taxon identification and actual wording are not checked.
- 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
Consult the original taxonomic treatment and applicable nomenclatural code, and use source-aware taxonomic resolution for accepted names, priority or type status.
References
Similar or alternative tools
- Biosystematic Key Couplet Reference Check
Check identification-key nonterminal references.
- Nomenclatural Type Status Source Token
Map a source type-status token through a supplied vocabulary.