Description
only when approximate is true.
Archival records often contain bounded dates, editions, and source identifiers. Arithmetic on supplied coordinates can check consistency while leaving historical interpretation and authenticity unresolved.
only when approximate is true.
When to use this tool
Use Historical Date Circa Marker when you need a precise date-span or source-record bookkeeping step.
How to use the tool and how it works
- Enter dateText, approximate. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read label. Use the output convention below.
Require nonempty dateText and prefix c. only when approximate is true.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| dateText | Supplied date text under the accepted precision and grammar above. | Required. Text; maximum UTF-16 length 8192. |
| approximate | Approximate | Required. Boolean. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| label | Formatted label for the supplied components under the convention above. | Required. Text; maximum UTF-16 length 8192. |
json
{
"input": {
"dateText": "1450",
"approximate": true
},
"output": {
"label": "c. 1450"
}
}Limitations and assumptions
- The approximation is a supplied assertion; no date parsing, historical dating, uncertainty width, or source verification occurs.
- 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 catalog and documented calendar or dating convention when historical interpretation matters.
References
Similar or alternative tools
- Catalogue Circa Date Interval Field
Validate bounded integer centralYear and nonnegative earlier/later tolerances.
- Historical Event Date Precision Token
Quote date text and append its declared precision.