Skip to content

Main content

Nomenclatural Type Status Source Token Tool

Resolve a reviewed caller-supplied type-status vocabulary with explicit code and edition.

Loading tool…

Description

Map a source type-status token through a supplied vocabulary.

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.

Map a source type-status token through a supplied vocabulary.

When to use this tool

Use Nomenclatural Type Status Source Token when checking the stated taxonomic source, name-token, date or concept-support convention.

How to use the tool and how it works

  1. Enter token, sourceTokens, normalizedTokens, code, edition. Follow any array-alignment requirements below. 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 status, sourceKey. Use the output convention below.

Map a source type-status token through a supplied vocabulary. Require aligned source/normalized tokens, unique source tokens, nonempty code/edition and a recognized input token; return normalized status and JSON source key.1

Input fieldMeaning and unitsAccepted input
tokenTokenRequired. Text; maximum UTF-16 length 8192.
sourceTokensSource TokensRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
normalizedTokensNormalized TokensRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
codeCodeRequired. Text; maximum UTF-16 length 8192.
editionEditionRequired. Text; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
statusStatusRequired. Text; maximum UTF-16 length 8192.
sourceKeySource KeyRequired. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "token": "HT",
    "sourceTokens": [
      "HT",
      "PT"
    ],
    "normalizedTokens": [
      "holotype",
      "paratype"
    ],
    "code": "ICZN",
    "edition": "study-edition"
  },
  "output": {
    "status": "holotype",
    "sourceKey": "[\"ICZN\",\"study-edition\",\"HT\"]"
  }
}

Limitations and assumptions

  • The mapping and code labels are supplied; no nomenclatural status, valid designation or source authority is established.
  • 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

  1. Calculation and input contract: biosystematics/nomenclatural-type-status-source-token — tool.io

Similar or alternative tools