Victim Offender Relationship Classifier Lookup
Exact independently verified victim/offender relationship codes registry lookup in explicit survey/statistical scheme edition, actual independent relationship evidence and context context, retaining source and as-of date. Caller supplies actual applicable records, qualifications and uncertainty; illustrative examples are not authoritative data. No complete/current catalog, eligibility, authenticity, clinical, legal, safety or compliance determination.
Description
Victim–offender relationship categories belong to a specific statistical or survey scheme.
Victim–offender relationship categories belong to a specific statistical or survey scheme.1
Independent relationship evidence and the scheme edition determine which reference applies. Use this tool to retrieve a caller-supplied reference with its source context.
When to use Victim Offender Relationship Classifier Lookup
Use this tool to retrieve a caller-supplied reference with its source context. Establish the jurisdiction or research scope, observation and event definitions, reference date, matched period and denominator basis.
How to use Victim Offender Relationship Classifier Lookup and understand its results
- Establish the jurisdiction or research scope, observation and event definitions, reference date, matched period and denominator basis.
- Enter callerVerifiedSource, callerVerifiedContext, callerVerifiedAsOfDate, callerReferenceKeys, callerReferenceTexts, queryReferenceKey, using the field meanings and rules below, then run the tool.
- Read result.matchedCallerReference, result.source, result.context, result.asOfDate. Interpret each field using the units, signs and evidence rules below.
- If input validation fails, correct the reported field and run again. Before applying a successful result, check the stated reference scope, units, assumptions and any retained unknown evidence.
| Input field | Meaning | Value type | Requirement |
|---|---|---|---|
| callerVerifiedSource | Caller verified source; caller assertion whose applicability must be independently established | string | Required |
| callerVerifiedContext | Caller verified context; caller assertion whose applicability must be independently established | string | Required |
| callerVerifiedAsOfDate | Caller verified as of date; real Gregorian YYYY-MM-DD date for the supplied record | string | Required |
| callerReferenceKeys | Caller reference keys | list of string | Required |
| callerReferenceTexts | Caller reference texts | list of string | Required |
| queryReferenceKey | Query reference key; exact key or bounded coordinate, according to the rules below | string | Required |
Supply nonblank source and context strings, each at most 256 UTF-16 units, and a real Gregorian YYYY-MM-DD as-of date in years 0001–9999. Enter nonempty aligned reference keys and texts; keys must be unique and nonblank, and texts nonblank. Select an exactly matching key, with case-sensitive matching and no trimming or normalization. The implementation returns its matched text and copies the supplied source, context and date unchanged. These verification labels are caller assertions: the tool does not fetch, verify or update a reference.
matchedText=texts[indexOfExact(queryKey,keys)]; provenance=copied caller assertions Apply the field units and exact ordering, boundary and evidence rules above.
| Output field | Meaning | Value type |
|---|---|---|
| result | Structured result containing the calculation or selected reference fields below | object |
| result.matchedCallerReference | Caller text at the exact matched reference key, returned unchanged | string |
| result.source | Caller source assertion copied unchanged | string |
| result.context | Caller applicability context copied unchanged | string |
| result.asOfDate | Caller date copied unchanged after Gregorian validation | string |
{
"input": {
"callerVerifiedSource": "independently-reviewed-source/edition",
"callerVerifiedContext": "survey/statistical scheme edition, actual independent relationship evidence and context",
"callerVerifiedAsOfDate": "2026-01-01",
"callerReferenceKeys": [
"record-a",
"record-b"
],
"callerReferenceTexts": [
"Caller independently verified victim/offender relationship codes record a",
"Caller independently verified victim/offender relationship codes record b"
],
"queryReferenceKey": "record-a"
},
"output": {
"result": {
"matchedCallerReference": "Caller independently verified victim/offender relationship codes record a",
"source": "independently-reviewed-source/edition",
"context": "survey/statistical scheme edition, actual independent relationship evidence and context",
"asOfDate": "2026-01-01"
}
}
}Limitations and assumptions
A successful lookup establishes an exact key match to supplied text. The tool does not obtain or authenticate the reference, confirm its applicability, or update its date.
Every listed input requires an explicit value. Unexpected fields, incorrect value types, nonfinite numbers and sparse numeric arrays fail validation; tool-specific bounds and alignment rules apply as described above. Extremely large inputs or outputs can also be rejected. An input error is distinct from a successful calculation that reports a false comparison or retains unknown evidence.
Alternative or Complementary methods
Use Indirect Household vs Personal Victim Classifier to examine a related aspect: Personal and household victimization are different observation levels.
Use Repeat Victimization Within Year Flag Checker where its separate inputs and scope apply: Repeat victimization requires distinct recorded events linked to the same adopted victim identifier.
References
Similar or alternative tools
- Indirect Household vs Personal Victim Classifier
Personal and household victimization are different observation levels.
- Repeat Victimization Within Year Flag Checker
Repeat victimization requires distinct recorded events linked to the same adopted victim identifier.