Skip to content

Main content

Taxon Name Year Suffix Token Tool

Split a public name/year citation token under an explicit separator; no nomenclatural validity judgment.

Loading tool…

Description

Split a name token from a year and optional one-letter suffix.

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.

Split a name token from a year and optional one-letter suffix.

When to use this tool

Use Taxon Name Year Suffix 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, separator. 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 nameToken, year, suffix. Use the output convention below.

Split a name token from a year and optional one-letter suffix. Require nonempty separator, text before its last occurrence and exactly four digits plus optional lowercase letter after it; return numeric year and suffix.1

Input fieldMeaning and unitsAccepted input
tokenTokenRequired. Text; maximum UTF-16 length 8192.
separatorSeparatorRequired. Text; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
nameTokenName TokenRequired. Text; maximum UTF-16 length 8192.
yearFour-digit lexical year including 0000 under this parser; not a validated publication history.Required. Safe integer.
suffixSuffixRequired. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "token": "Name|1901a",
    "separator": "|"
  },
  "output": {
    "nameToken": "Name",
    "year": 1901,
    "suffix": "a"
  }
}

Limitations and assumptions

  • Year zero is permitted by the lexical grammar; no publication date, author disambiguation or nomenclatural priority is verified.
  • 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/taxon-name-year-suffix-token — tool.io

Similar or alternative tools