Skip to content

Main content

Public Register Folio Token Tool

Parse a positive decimal folio and unambiguous caller-supplied side suffix.

Loading tool…

Description

Accept exactly one matching suffix whose preceding tail is a positive integer without leading zero, and return folio number and side token.

Historical and public-register references combine repositories, series, titles and local identifiers. A syntactic token or hierarchy count helps organize records without authenticating the source or establishing a document's historical or legal meaning.

Accept exactly one matching suffix whose preceding tail is a positive integer without leading zero, and return folio number and side token.

When to use this tool

Use Public Register Folio Token when you need a literal archival or public-register record operation.

How to use the tool and how it works

  1. Enter token, prefix, rectoToken, versoToken. 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 folio, side. Use the output convention below.

Require nonempty prefix and distinct recto/verso suffixes, with a prefixed token. Accept exactly one matching suffix whose preceding tail is a positive integer without leading zero, and return folio number and side token.1

Input fieldMeaning and unitsAccepted input
tokenTokenRequired. Text; maximum UTF-16 length 8192.
prefixSupplied or returned literal prefix under the stated grammar.Required. Text; maximum UTF-16 length 8192.
rectoTokenRecto TokenRequired. Text; maximum UTF-16 length 8192.
versoTokenVerso TokenRequired. Text; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
folioPositive safe numeric folio index, without leading-zero spelling.Required. Safe integer.
sideSideRequired. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "token": "f12v",
    "prefix": "f",
    "rectoToken": "r",
    "versoToken": "v"
  },
  "output": {
    "folio": 12,
    "side": "v"
  }
}

Limitations and assumptions

  • Ambiguous overlapping suffix matches are rejected. Parsing does not authenticate a manuscript, resolve a catalog reference or infer its foliation convention.
  • 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 source repository's catalog and description conventions for identity and interpretation. Preserve original references and resolve language, hierarchy and identifier rules before treating a token match as an authenticated record.

References

  1. Calculation and input contract: european-studies/public-register-folio-token — tool.io

Similar or alternative tools