Description
Split a numeric version suffix from a supplied accession token.
Sequence formats distinguish coordinate origins, included endpoints, allele separators and identifier grammars. A genomic interbase position differs from a base number, and a parsed optional-field value may still violate its declared type. Local token checks preserve representation without validating a complete file, sequence, reference assembly or biological interpretation.
Split a numeric version suffix from a supplied accession token.
When to use this tool
Use FASTA Accession Version Suffix when you already have accessionToken and need to split a numeric version suffix from a supplied accession token.
How to use the tool and how it works
- Enter accessionToken. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read accession, versionText, hasNumericVersion. Inspect hasNumericVersion before interpreting the associated values.
Require nonempty text without whitespace. If a final dot is followed by digits, split at that final numeric suffix; otherwise preserve the whole token and return an empty version with hasNumericVersion=false.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| accessionToken | Accession Token | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| accession | Accession | Required. Text; maximum UTF-16 length 8192. |
| versionText | Final numeric suffix preserved as text, including leading zeros; empty when no numeric suffix matched. | Required. Text; maximum UTF-16 length 8192. |
| hasNumericVersion | Has Numeric Version | Required. Boolean. |
{
"input": {
"accessionToken": "AB123456.2"
},
"output": {
"accession": "AB123456",
"versionText": "2",
"hasNumericVersion": true
}
}Limitations and assumptions
- Version digits retain leading zeros and are not converted to a number. This is a lexical convention, not validation against a database accession grammar or live version history.
- 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
Use the complete applicable file specification and a full format validator for conformance. Verify reference assembly, sequence bounds, annotation and database context before interpreting local fields or coordinate transformations.
References
Similar or alternative tools
- FASTA Header Accession Split
Split a supplied FASTA header into accession and description text.
- Protein Residue Position Label
Format a supplied protein-residue position and zero-based index.