Cob Assayer Record Match

Compare caller-supplied expected and observed records for cob assayer record match.

Description

Cob assayer-mark reconciliation compares catalog mark labels with observed ones.

Cob assayer-mark reconciliation compares catalog mark labels with observed ones. A match needs the appropriate issue-specific catalog context.1

Compare caller-supplied expected and observed records for cob assayer record match.

When to use Cob Assayer Record Match

Use this tool to compare caller-supplied expected and observed records for cob assayer record 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 Cob Assayer Record Match and understand its results

  1. 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.
  2. Enter catalogMarks, observedMarks using the field table and calculation rules, then run the tool.
  3. Read coveragePercent, matched, missing, unexpected. The explanation below defines the units, signs, ordering and any flags or placeholder values.
  4. 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 fieldMeaningValue type; see rules belowRequirement
catalogMarksCatalog assayer markslist of stringRequired
observedMarksObserved markslist of stringRequired

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 fieldMeaningValue type
coveragePercentCoverage (%)number; minimum: 0; maximum: 100
matchedMatched itemslist of string
missingMissing itemslist of string
unexpectedUnexpected itemslist of string
json
{
  "input": {
    "catalogMarks": [
      "M",
      "oM",
      "MF"
    ],
    "observedMarks": [
      "M",
      "MF",
      "R"
    ]
  },
  "output": {
    "coveragePercent": 66.66666666666666,
    "matched": [
      "M",
      "MF"
    ],
    "missing": [
      "oM"
    ],
    "unexpected": [
      "R"
    ]
  }
}

Limitations and assumptions

The tool does not read a mark, identify an assayer or validate catalog attribution. 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 Colonial Strike Classifier: Classify caller-observed indicators for colonial strike classifier while preserving mixed and insufficient evidence. For a complementary task, use Mintmark Record Match: Compare caller-supplied expected and observed records for mintmark record match.

References

  1. Cob Assayer Record Match — tool.io

Similar or alternative tools

  • Colonial Strike Classifier

    Classify caller-observed indicators for colonial strike classifier while preserving mixed and insufficient evidence.

  • Mintmark Record Match

    Compare caller-supplied expected and observed records for mintmark record match.

Don't forget to set a bookmark for tool.io!
Privacy | Imprint | Cookies