Tughra Marker Match

Compare caller-supplied expected and observed records for tughra marker match.

Description

Tughra-marker matching compares expected catalog labels with observed labels.

Tughra-marker matching compares expected catalog labels with observed labels. It organizes an attribution checklist without decoding the inscription itself.^[1]

Compare caller-supplied expected and observed records for tughra marker match.

When to use Tughra Marker Match

Use this tool to compare caller-supplied expected and observed records for tughra marker match.

Prepare documented records or observations for the specific coin or issue context. Enter the required labels, reference table or evidence flags and retain the supporting catalog and examination notes for interpretation.

How to use Tughra Marker Match and understand its results

Prepare documented records or observations for the specific coin or issue context. Enter the required labels, reference table or evidence flags and retain the supporting catalog and examination notes for interpretation.
Enter catalogMarkers, observedMarkers using the field table and calculation rules, then run the tool.
Read coveragePercent, matched, missing, unexpected. The explanation below defines the units, signs, ordering and any flags or placeholder values.
If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.

Input field	Meaning	Value type; see rules below	Requirement
catalogMarkers	Catalog markers	list of string	Required
observedMarkers	Observed markers	list of string	Required

Enter expected and observed lists using the field table. Trim, reject blank entries and normalize keys with en-US lowercase. Deduplicate both lists, requiring at least one distinct expected item; observations may be empty. Return matched/missing labels in expected order, unexpected labels in observed order and coverage. Last duplicate spelling is retained at its first key position.

coverage%=100 matchedDistinctExpected/distinctExpected

Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.

Output field	Meaning	Value type
coveragePercent	Coverage (%)	number; minimum: 0; maximum: 100
matched	Matched items	list of string
missing	Missing items	list of string
unexpected	Unexpected items	list of string

json

{
  "input": {
    "catalogMarkers": [
      "loop",
      "beyze",
      "tuğ"
    ],
    "observedMarkers": [
      "loop",
      "beyze",
      "unknown"
    ]
  },
  "output": {
    "coveragePercent": 66.66666666666666,
    "matched": [
      "loop",
      "beyze"
    ],
    "missing": [
      "tuğ"
    ],
    "unexpected": [
      "unknown"
    ]
  }
}

Limitations and assumptions

No script, image, ruler attribution or catalog entry is read. Case and outer whitespace are ignored, while other spelling differences remain distinct.

Numeric inputs must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Lists are limited to 100,000 entries; the rules above may require smaller limits. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors.

Alternative or Complementary methods

Use Roman Moneyer Legend Parser: Match normalized Roman Republican legend tokens against a caller-supplied abbreviation dictionary; it does not identify a moneyer from unconfigured initials. For a complementary task, use Mintmark Record Match: Compare caller-supplied expected and observed records for mintmark record match.

References

Tughra Marker Match — tool.io

Similar or alternative tools

Roman Moneyer Legend Parser
Match normalized Roman Republican legend tokens against a caller-supplied abbreviation dictionary; it does not identify a moneyer from unconfigured initials.
Mintmark Record Match
Compare caller-supplied expected and observed records for mintmark record match.