What a view is matched against: where the dataset was read from, and which table
of it. Standard input’s - is a path no path criterion fits, so data piped in or a
frame handed over is matched by its columns alone.
Why a view’s criteria fit the open file, in the words the list annotates
rows with. The strongest reason wins: the same file beats the same columns
beats a glob.
Whether the view’s own criteria match this file: a path or pattern hit,
or every schema column the view asks for present. Distinct from the
relevance score, which also carries usage and recency and so is never zero
for a view that has been used — a ranking, not a claim of fit.
A dataset’s location as a view records it: a URL as written, a local path made
absolute and resolved. The save form offers this and matching compares with it,
so the two are spelled alike.
Whether the view’s exact path names the dataset at file_path. A URL compares as
text less any trailing slash, which is how a directory’s URL may or may not end,
and with its scheme in either case, as datui opens it.
The strongest criterion of the view’s that fits this file, or None when
none does. This is the same test criteria_match gates on, kept in one
place so the list’s “why it matches” annotation can never disagree with
what V and auto-apply do.
Whether the view’s path pattern fits file_path, as opened or as the save form
spells it: a file opened by a relative path or through a link is still under the
resolved directory its pattern was suggested from.