Skip to content

Main content

Meeting Access Feature Count Tool

Calculate meeting access feature count from explicit caller-supplied inputs.

Loading tool…

Description

Count distinct provided and missing required meeting features.

Community projects combine participation counts, access assertions, funding bases and shared-resource policies. Local allocation or coverage arithmetic can organize those records, while equitable access, actual contribution value and valid funding rights require evidence and the applicable rules.

Count distinct provided and missing required meeting features.

When to use this tool

Use Meeting Access Feature Count when checking one explicit community-project capacity, funding, access or scheduling convention.

How to use the tool and how it works

  1. Enter required, available. 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 providedCount, missingCount. Use the output convention below.

Count distinct provided and missing required meeting features. Deduplicate required labels after partitioning by literal membership in available.1

Input fieldMeaning and unitsAccepted input
requiredRequiredRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
availableAvailableRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
Output fieldInterpretationReturned shape
providedCountProvided CountRequired. Safe integer.
missingCountMissing CountRequired. Safe integer.
json
{
  "input": {
    "required": [
      "caption",
      "ramp"
    ],
    "available": [
      "ramp"
    ]
  },
  "output": {
    "providedCount": 1,
    "missingCount": 1
  }
}

Limitations and assumptions

  • Feature presence is asserted, not usability, suitability for particular people or accessibility compliance.
  • 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

Use actual project records, participant needs and governing funding/resource rules to assess practical adequacy, fairness and eligibility.

References

  1. Calculation and input contract: community-development/meeting-access-feature-count — tool.io

Similar or alternative tools