Description
Build an exact facsimile page key from supplied leaf text and side token.
Digital editions separate source readings, editorial uncertainty, witness locators, image requests, identifiers and rights statements. XML character/attribute rules differ from display labels, while URI fragments and TEI pointers need their target-document context. An identifier key or formatted token does not authenticate a witness, validate an edition or authorize reuse.
Build an exact facsimile page key from supplied leaf text and side token.
When to use this tool
Use Facsimile Recto Verso Page Key when you already have facsimileId, leafText, sideToken and need to build an exact facsimile page key from supplied leaf text and side token.
How to use the tool and how it works
- Enter facsimileId, leafText, sideToken. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read token. Use the output convention below.
Enter facsimileId, leafText, sideToken using the field constraints below. Encode these values, in exactly that order, as a JSON array and return the serialized array as text in token. String values are preserved without trimming or external terminology lookup.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| facsimileId | Facsimile Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| leafText | Leaf Text | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| sideToken | Side Token | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| token | Token | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"facsimileId": "F17",
"leafText": "24",
"sideToken": "r"
},
"output": {
"token": "[\"F17\",\"24\",\"r\"]"
}
}Limitations and assumptions
- The result records supplied values without imposing a foliation system. Sources and asserted relationships are not independently authenticated.
- 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
Validate the complete XML/TEI document or IIIF request when technical conformance matters, and inspect the original witness and rights record for editorial use. Preserve uncertain readings, source order and attribution rather than treating local tokens as verified scholarly interpretations.
References
Similar or alternative tools
- Marginalia Anchor Surface Zone Key
Encode an explicit document, surface and zone marginalia anchor.
- Edition Variant Omission Witness Tag
Preserve an edition-qualified explicit witness omission assertion.