Beat Source Coverage

Compare caller-supplied requirements and observations for beat source coverage.

Description

Beat-source coverage compares required source-group labels with those recorded for a reporting beat.

Beat-source coverage compares required source-group labels with those recorded for a reporting beat. It highlights absent groups in the supplied inventory.^[1]

Compare caller-supplied requirements and observations for beat source coverage.

When to use Beat Source Coverage

Use this tool to compare caller-supplied requirements and observations for beat source coverage.

Prepare the text, recorded observations, aligned figures or editorial criteria requested. Confirm what each label, count, timestamp or supplied flag represents before interpreting the result.

How to use Beat Source Coverage and understand its results

Prepare the text, recorded observations, aligned figures or editorial criteria requested. Confirm what each label, count, timestamp or supplied flag represents before interpreting the result.
Enter requiredSourceGroups, coveredSourceGroups 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
requiredSourceGroups	Required source groups	list of string	Required
coveredSourceGroups	Covered source groups	list of string	Required

Supply required and observed group labels. Enter a nonempty required list and an observed list, which may be empty. Trim and lowercase entries for comparison; blank entries are errors. Deduplicate by normalized key. Return matched/missing required labels, unexpected observed labels, and coverage. Required order is preserved; the last trimmed spelling wins for duplicate keys.

coverage%=100×matchedUnique/requiredUnique

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": {
    "requiredSourceGroups": [
      "officials",
      "residents",
      "subject experts",
      "affected groups"
    ],
    "coveredSourceGroups": [
      "officials",
      "residents",
      "affected groups"
    ]
  },
  "output": {
    "coveragePercent": 75,
    "matched": [
      "officials",
      "residents",
      "affected groups"
    ],
    "missing": [
      "subject experts"
    ],
    "unexpected": []
  }
}

Limitations and assumptions

No source quality, independence, representativeness or actual reporting is verified.

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 Roundup Source Coverage: Measure source-category coverage in a roundup. For a complementary task, use Community Source Corroboration: Check community-source and independent-corroboration counts against supplied minimums.

References

Beat Source Coverage — tool.io

Similar or alternative tools

Roundup Source Coverage
Measure source-category coverage in a roundup.
Community Source Corroboration
Check community-source and independent-corroboration counts against supplied minimums.