Skip to content

Main content

Metadata Source Coverage Share Tool

Calculate metadata source coverage share from explicit caller-supplied inputs.

Loading tool…

Description

Deduplicate requiredKeys, count those present in sourceKeys, and count those present in both sourceKeys and verifiedKeys.

Metadata obligations and relations apply to a declared record scope. Field presence, source coverage, cardinality, and value correctness are independent properties.

Deduplicate requiredKeys, count those present in sourceKeys, and count those present in both sourceKeys and verifiedKeys.

When to use this tool

Use Metadata Source Coverage Share when you need a narrow metadata consistency or coverage check.

How to use the tool and how it works

  1. Enter requiredKeys, sourceKeys, verifiedKeys. Keep parallel arrays aligned. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read required, covered, verifiedCovered, share, defined. Inspect defined before interpreting the associated values.

Deduplicate requiredKeys, count those present in sourceKeys, and count those present in both sourceKeys and verifiedKeys. Divide verifiedCovered by a positive required count, otherwise return zero and defined false.1

Input fieldMeaning and unitsAccepted input
requiredKeysRequired KeysRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
sourceKeysSource KeysRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
verifiedKeysVerified KeysRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
Output fieldInterpretationReturned shape
requiredRequiredRequired. Safe integer.
coveredCoveredRequired. Safe integer.
verifiedCoveredVerified CoveredRequired. Safe integer.
shareDimensionless fraction under the stated denominator policy.Required. Finite number.
definedWhether the accompanying fraction has an available nonzero denominator.Required. Boolean.
json
{
  "input": {
    "requiredKeys": [
      "a",
      "b"
    ],
    "sourceKeys": [
      "a",
      "b"
    ],
    "verifiedKeys": [
      "a"
    ]
  },
  "output": {
    "required": 2,
    "covered": 2,
    "verifiedCovered": 1,
    "share": 0.5,
    "defined": true
  }
}

Limitations and assumptions

  • Extra keys are ignored; source coverage and verification are supplied metadata, not a factual validation of field values.
  • 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

Apply the complete metadata profile and inspect field values and provenance before accepting a record.

References

  1. Calculation and input contract: information-science/metadata-source-coverage-share — tool.io

Similar or alternative tools