Default scope should be the current context, not the whole collection

What it is

People issue a query from a place: a folder, a document, a section, a project. Defaulting scope to the current context means the first run is inside that place, not a sweep of the whole corpus. Global is the enlarged option, not the unexamined starting point. “Search this folder” in a digital library or drive, “search this space” on an intranet, treat the place as a constraint that has not yet been rejected.

This is not “write the current scope on the box”—that is visibility of scope. This decides which slice runs when nobody has touched a control. Visibility can be complete and the default still wrong.

Why it happens

Place is already in working memory. Walking into the “Q3 budget” folder and then opening search makes that folder the implied subject of the sentence. Defaulting to global throws away navigation cost already paid and drops people into corpus noise. Hits that are irrelevant now flood the list, the first-rank correlation thins, and people type qualifiers to rebuild the context just discarded—re-encoding interface state into the query string.

A global default also misattributes: the target sits locally but is pushed down by a hotter object from elsewhere, and people conclude it is not here. A contextual default shrinks the candidate set to the slice that agrees with the place, so scoring happens on a smaller, more homogeneous collection, and what ranks first is more like “find it here.”

Studying it

Compare “issued from a deep page, default global” with “issued from a deep page, default current collection” on completion and reformulation.

• Paradigms: the target lives in the current folder or section; the whole corpus also holds a decoy with a stronger term match; two defaults. Query logs can show how often queries issued off the root are immediately rewritten with a path qualifier.
• Independent variables: default scope (current / global), whether the current place and the target share a subtree.
• Dependent variables: whether the first query hits the in-collection target, times the query is rewritten as an explicit path, rate of picking the corpus-wide decoy.
• Methodological note: a lab that always starts from the home page cannot measure a contextual default. Launch from a place already walked into. The decoy must outscore the target on collection-wide BM25, or the harm of a global default will not show.

Where it stops holding

When people enter from a global entry (top-bar magnifier, a command palette’s “all files”), the current context is the whole app, and a global default is right. Cross-collection lookup (“which project is this person in”) has global as its first cut; a local default hides the answer. A place with no index (a display-only page, an embed) has no current collection to take; fall back to global and say so. On a shared desktop or kiosk, “current” may be the previous person’s folder; following that context leaks, and the default should fall back to the account root, not the last session’s place.

Applying it

• Search opened from a folder, section, project, or document should bind its initial scope to that node, not silently point at the whole corpus.
• Offer an explicit enlarge action (“search everything”). Do not rely on people deleting a constraint they cannot see.
• Search opened from global chrome stays global. Do not steal the scope into a document that happens to be open behind the box.
• Verify by walking into a subfolder that contains the target and typing the target’s words. First results should come from that folder. If the first row is a hotter homonym from elsewhere, the default is still global.

Related

• Within the group: G3.16.2 Nested scopes inherit: a child collection sits inside its parent · G3.16.3 Zero hits in a narrow scope should offer one-click expansion to the parent · G3.16.4 Searching several scopes at once requires one shared relevance scale · G3.16.5 Scope changes ranking; top hits from different scopes are not comparable
• Adjacent: G3.12 Search scope · G3.07 Zero-result handling · G3.01 Lookup versus browsing
• Search terms: scoped search · contextual default · collection selection