Overmintmark Omn Hub Doubling History Lookup
Bounded offline reference: Overmintmarks involve differing mintmark punches; hub doubling involves a distinct die-making mechanism. Source: Die-variety catalogue scholarship. The milestones Oмн/OMN wording is not adopted as a universal code; distinguish OMM from doubled die and machine doubling. Supported topic keys: summary, reference, limitations. No complete external corpus or live policy implied.
Description
Overmintmarks and hub doubling arise from different stages of die preparation.
Overmintmarks and hub doubling arise from different stages of die preparation.1
This lookup explains the chosen topic using a bounded stored reference.
When to use Overmintmark Omn Hub Doubling History Lookup
Use this tool to read a bounded explanation for an exact reference topic. Establish the coin issue, source edition, measurement basis and reference date where applicable.
How to use Overmintmark Omn Hub Doubling History Lookup and understand its results
- Establish the coin issue, source edition, measurement basis and reference date where applicable.
- Enter topic, using the field meanings and rules below, then run the tool.
- Read result. Inspect nested result fields where present, and review unknown records separately from known matches.
- Correct any reported input issue and run again. Before using a successful result, check the stated units, signs, reference scope and observation coverage.
| Input field | Meaning | Value type | Requirement |
|---|---|---|---|
| topic | Topic | string | Required |
Choose one exact topic token from the table. The implementation looks up the stored value and returns it in the documented output field. Matching is case-sensitive; unrecognized tokens fail. This is an offline bounded reference, not a live catalogue or independent attribution.
| Topic token | Stored value |
|---|---|
| summary | Overmintmarks involve differing mintmark punches; hub doubling involves a distinct die-making mechanism. |
| reference | Die-variety catalogue scholarship. |
| limitations | The milestones Oмн/OMN wording is not adopted as a universal code; distinguish OMM from doubled die and machine doubling. |
value=referenceTable[exactToken] Use the matching field units and the exact boundary, ordering and reference rules above.
| Output field | Meaning | Value type |
|---|---|---|
| result | Calculated observation or qualified reference | object |
| result.text | text | string |
{
"input": {
"topic": "summary"
},
"output": {
"result": {
"text": "Overmintmarks involve differing mintmark punches; hub doubling involves a distinct die-making mechanism."
}
}
}Limitations and assumptions
Coin identification, reference applicability and measurement uncertainty require separate evidence. A returned explanation or arithmetic agreement does not establish authenticity, a certified grade or a current market value. The milestones Oмн/OMN wording is not adopted as a universal code; distinguish OMM from doubled die and machine doubling.
Missing required fields, unknown fields, wrong types and violated rules return input issues. Numeric values and outputs must be finite. Extremely large composite outputs are rejected.
Alternative or Complementary methods
For a related step, use Repunched Mintmark RPM Hand Punched Era Note: A repunched mintmark reflects a mintmark-punching mechanism, which differs from other forms of apparent doubling. For a complementary comparison, use Brockage Incuse Mirror Image Error Lookup: Brockage describes a mirrored incuse impression associated with a striking mechanism.
References
Similar or alternative tools
- Repunched Mintmark RPM Hand Punched Era Note
A repunched mintmark reflects a mintmark-punching mechanism, which differs from other forms of apparent doubling.
- Brockage Incuse Mirror Image Error Lookup
Brockage describes a mirrored incuse impression associated with a striking mechanism.