Skip to main content

PeopleSearchStage

Which wave of a round a part is (the search in two waves). full — the search. quick — its first look, asked at the same moment as the full part of the same networks: the same query over the people whose full name carries the whole typed name, up to 50 cards in a few seconds, no refinement question. A quick part is NOT a part of the round: it requires round_key, counts nothing, claims nothing, stores no panels and no search_state, writes no history row, and is never pending. It is validated like the round's first part (a refused query is refused the same way — 400, 404, 409, 429), searches the round's fixed query once the round has one, and its cards are accounts the report has shown (a pick, a seed, "Other accounts" and confirm may name them). Its panels carry stage: quick; the client shows them while the full answer of those networks is on its way and REPLACES them with it — it never merges the two. A quick part that fails, or lands after the full answer, costs nothing. With nothing to preview (no name to search by, a phone lookup, a query the report has already answered) it answers no panels.

stringPeopleSearchStage (string)

Which wave of a round a part is (the search in two waves). full — the search. quick — its first look, asked at the same moment as the full part of the same networks: the same query over the people whose full name carries the whole typed name, up to 50 cards in a few seconds, no refinement question. A quick part is NOT a part of the round: it requires round_key, counts nothing, claims nothing, stores no panels and no search_state, writes no history row, and is never pending. It is validated like the round's first part (a refused query is refused the same way — 400, 404, 409, 429), searches the round's fixed query once the round has one, and its cards are accounts the report has shown (a pick, a seed, "Other accounts" and confirm may name them). Its panels carry stage: quick; the client shows them while the full answer of those networks is on its way and REPLACES them with it — it never merges the two. A quick part that fails, or lands after the full answer, costs nothing. With nothing to preview (no name to search by, a phone lookup, a query the report has already answered) it answers no panels.

Possible values: [quick, full]

Default value: full
PeopleSearchStage
"full"