Description
Classify a supplied survey code as missing, valid or unknown.
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.
Classify a supplied survey code as missing, valid or unknown.
When to use this tool
Use Neighborhood Need Survey Response Code when you already have responseCode, validCodes, missingCodes and need to classify a supplied survey code as missing, valid or unknown.
How to use the tool and how it works
- Enter responseCode, validCodes, missingCodes. Follow any array-alignment requirements below. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read classification. Use the output convention below.
Require supplied validCodes and missingCodes disjoint; test missing membership first, then valid, otherwise return unknown-code.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| responseCode | Response Code | Required. Text; maximum UTF-16 length 8192. |
| validCodes | Valid Codes | Required. Array of text; maximum UTF-16 length 8192; maximum items 256. |
| missingCodes | Missing Codes | Required. Array of text; maximum UTF-16 length 8192; maximum items 256. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| classification | Caller-defined valid/missing status or unknown; the supplied code lists must be disjoint. | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"responseCode": "NA",
"validCodes": [
"A",
"B"
],
"missingCodes": [
"NA"
]
},
"output": {
"classification": "missing"
}
}Limitations and assumptions
- Empty codes and repeated list entries are accepted if the lists remain disjoint. No response, meaning, survey design, imputation or actual need is inferred.
- 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
Similar or alternative tools
- Resident Ballot Invalid Reason Token
Preserve a supplied resident-ballot status reason and rule source.
- Meeting Language Seat Count
Sum supplied seat requests for unique language codes.