311 product owners want Data API builder clients to run free-text search across request summary fields. What should developers configure?
Select an answer to reveal the explanation.
Short Explanation
Free-text search on request summaries is how 311 finds “pothole on Main” without knowing the ticket number—flip searching on in the DAB entity config.
Full Explanation
311 product owners want Data API builder clients to run free-text search across request summary fields. Developers should configure DAB searching on the request summary fields so clients can perform free-text search. Searchable entity fields let municipal intake apps find requests by phrases such as location or issue text without forcing exact primary-key knowledge—improving 311 operator and resident-facing query UX while keeping access inside the API model.
Removing summary fields from entities so search is impossible fails the product requirement directly. Forcing clients to download every request row and search only on the device fails performance and privacy posture for city-scale 311 data. Disabling searching and requiring exact primary-key lookups for every inquiry fails usability when users know a description rather than an id.
Exam caveat: DAB searching configuration on the relevant fields is the answer when free-text search is requested. Client-side full downloads and PK-only access are common distractors.
Operational check: enable searching on request summary fields in DAB, issue a free-text query for a known phrase in test data, and verify matching 311 requests return. Confirm non-searchable sensitive fields remain excluded from search indexing as required by city policy.