Description
Compare voucher status only when its source is declared known.
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.
Compare voucher status only when its source is declared known.
When to use this tool
Use Voucher Type Status Source Gap when checking the stated taxonomic source, name-token, date or concept-support convention.
How to use the tool and how it works
- Enter voucherId, assertedStatus, sourceStatus, sourceKnown. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read verifiedComparison, matches, preservedId. Inspect verifiedComparison, matches before interpreting the associated values.
Compare voucher status only when its source is declared known. verifiedComparison mirrors sourceKnown, matches requires it and literal status equality, preservedId retains voucherId.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| voucherId | Voucher Id | Required. Text; maximum UTF-16 length 8192. |
| assertedStatus | Asserted Status | Required. Text; maximum UTF-16 length 8192. |
| sourceStatus | Source Status | Required. Text; maximum UTF-16 length 8192. |
| sourceKnown | Supplied assertion permitting comparison; not source authentication. | Required. Boolean. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| verifiedComparison | Verified Comparison | Required. Boolean. |
| matches | Matches | Required. Boolean. |
| preservedId | Preserved Id | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"voucherId": "V1",
"assertedStatus": "holotype",
"sourceStatus": "isotype",
"sourceKnown": true
},
"output": {
"verifiedComparison": true,
"matches": false,
"preservedId": "V1"
}
}Limitations and assumptions
- The flag does not authenticate the source or confirm actual nomenclatural type status; unknown comparison is not mismatch evidence.
- 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
- Nomenclatural Type Status Source Token
Map a source type-status token through a supplied vocabulary.
- Type Specimen Reference Depth
Return a type-specimen reference's path depth under a root policy.