1606915 - Improve the QueryScorer for Interventions

Status: NEW

(Firefox :: Address Bar, enhancement, P3)

Description

[Harry Twyford]

The QueryScorer in the experiment is still a WIP. Mak and Drew discussed possible improvements. We must end up with a format to associate interventions to tuples of words.

Comment 1

[Drew Willcoxon :adw]

Verdi had feedback on the final version and I had questions on his feedback, but I haven't heard back yet.

Comment 2

[Marco Bonardo [:mak]]

What's the next step here, did you hear back or should we ping Verdi? Do you have a list of known improvements for the existing one?

Comment 3

[Drew Willcoxon :adw]

I haven't heard back. His point is that currently you have to type an entire phrase to match an intervention. He wants matches to happen after typing a smaller number of words in each phrase. I pressed him on what exactly the rule(s) would look like, especially since a previous version of the matcher worked similarly to that, and that's what we're stuck on. It sounds like he wants the rule to be: We match a phrase once the user types "Firefox" or "Mozilla" plus at least one non-Firefox/Mozilla word in the phrase (excluding stop words presumably).

Comment 4

[Marco Bonardo [:mak]]

Stop-words is the first thing people noticed when testing the feature: "why 'firefox slow' works but 'firefox is slow' doesn't?".
I think Verdi's idea makes sense, thus there'd be a mandatory word to match (firefox, mozilla or their alternatives like "fox fire" that we can keep hardcoded) and then we should match at least another word.
The matchers object could be something like:

{
    "en-": {
        fuzzer: "levenshtein",
        stopWords: ["the", "is", "a", "at", "on", "to", ...],
        matches: {
            "clear": ["cache", "clear", "cookie", "cookies", "history"],
            "refresh": ["slow", "hang", "crash", "crashing", "block", "blocked"],
            ...
        }
    },
    "jp-": {
        fuzzer: "none",
        ...
    }
}