Skip to content

Main content

Meeting Language Seat Count

Sum explicit language-channel seat requests with unique language codes without inferring attendee language needs.

Loading tool…

Description

Sum supplied seat requests for unique language codes.

Community records describe contributions, volunteer time, grants, notices, language requests and meeting participation. Person-minutes differ from elapsed task time, assigned in-kind values require a valuation basis, and a nominal seat count need not be a whole-person allocation. Supplied participation or permission flags do not verify actual access, consent or eligibility.

Sum supplied seat requests for unique language codes.

When to use this tool

Use Meeting Language Seat Count when you already have languageCodes, requestedSeats and need to sum supplied seat requests for unique language codes.

How to use the tool and how it works

  1. Enter languageCodes, requestedSeats. Follow any array-alignment requirements below. 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 totalSeats, distinctLanguages. Use the output convention below.

Require aligned arrays and unique codes; every seat request must be a nonnegative safe integer. Return total requested seats and number of codes.1

Input fieldMeaning and unitsAccepted input
languageCodesLanguage CodesRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
requestedSeatsRequested SeatsRequired. Array of safe integer; maximum items 256.
Output fieldInterpretationReturned shape
totalSeatsTotal SeatsRequired. Safe integer.
distinctLanguagesDistinct literal language codes, including any with zero requested seats; empty code can count as a category.Required. Safe integer.
json
{
  "input": {
    "languageCodes": [
      "en",
      "sw"
    ],
    "requestedSeats": [
      10,
      8
    ]
  },
  "output": {
    "totalSeats": 18,
    "distinctLanguages": 2
  }
}

Limitations and assumptions

  • Empty arrays and empty codes are accepted; zero-request languages still count. Unsafe totals are rejected; no room capacity, support need or actual provision is established.
  • 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

Review the underlying meeting, funding, service and volunteer records with the applicable project rules. Use full budgets, schedules and participation evidence when evaluating delivery or fairness; local labels and arithmetic retain only the stated assumptions.

References

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

Similar or alternative tools