1911903 - Support the Fakespot product_type field

Status: RESOLVED FIXED

(Application Services :: Suggest, task)

Description

[Ben Dean-Kawamura [:bdk]]

• Ingest this field and index it using FTS5
• If a query matches against this field for a suggestion, then it should be ordered before any suggestions that don't match.

Comment 1

[Ben Dean-Kawamura [:bdk]]

To be precise:

• we're adding 2 new fields: product_type and keywords
• The matching logic should stay exactly the same, these fields will only change the ordering logic
• Define keywords_score as 1.0 if the query matches the keywords field exactly, 0.0 otherwise
• Define product_type_score as matched / term_count, where matched is the number of terms from product_type that are present in the query and term_count is the total number of terms. For example, when product_type="standing desk":
  • The query standing desk gets a product_type_score of 1.0
  • The query desk gets a product_type_score of 0.5
  • The query standing desk for my office gets a product_type_score of 1.0 (extra terms in the query are ignored)
• Matched suggestions are ordered by the tuple (keywords_score, product_type_score, score)

Comment 2

[BMO Github Automation]

Attachment: [mozilla/application-services] Bug 1911903 - Fakespot keywords and product_type fields (#6342)

Comment 3

[Drew Willcoxon :adw]

PR was merged, closing. I think it was also vendored in to m-c but I'm not sure what version -- 130 at the latest since that's the version the Fakespot experiment targeted.