Bullion Security Feature Check

Compare caller-supplied expected and observed records for bullion security feature check.

Description

Bullion security-feature reconciliation checks declared feature labels against an expected list.

Bullion security-feature reconciliation checks declared feature labels against an expected list. A matching list cannot establish that the physical features are genuine.^[1]

Compare caller-supplied expected and observed records for bullion security feature check.

When to use Bullion Security Feature Check

Use this tool to compare caller-supplied expected and observed records for bullion security feature check.

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 Bullion Security Feature Check 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 documentedFeatures, observedFeatures 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
documentedFeatures	Documented security features	list of string	Required
observedFeatures	Observed features	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": {
    "documentedFeatures": [
      "reeded edge",
      "micro-engraving",
      "radial lines"
    ],
    "observedFeatures": [
      "reeded edge",
      "radial lines",
      "privy"
    ]
  },
  "output": {
    "coveragePercent": 66.66666666666666,
    "matched": [
      "reeded edge",
      "radial lines"
    ],
    "missing": [
      "micro-engraving"
    ],
    "unexpected": [
      "privy"
    ]
  }
}

Limitations and assumptions

No mint specification, metal test, image or actual feature is verified. Full coverage does not authenticate bullion. 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 Mintmark Record Match: Compare caller-supplied expected and observed records for mintmark record match. For a complementary task, use Grading Detail Code Match: Compare caller-supplied expected and observed records for grading detail code match.

References

Bullion Security Feature Check — tool.io

Similar or alternative tools

Mintmark Record Match
Compare caller-supplied expected and observed records for mintmark record match.
Grading Detail Code Match
Compare caller-supplied expected and observed records for grading detail code match.