Hello Megan! Could you do data-review?

Comment on attachment 9305055 [details]
data-review-request-for-bug1797265.md

1. Is there or will there be documentation that describes the schema for the ultimate data set in a public, complete, and accurate way?
   Yes.

2. Is there a control mechanism that allows the user to turn the data collection on and off?
   Yes, users can opt out of telemetry collection.

3. If the request is for permanent data collection, is there someone who will monitor the data over time?
   Yes, this will be owned by the Search and Suggest Team.

4. Using the category system of data types on the Mozilla wiki, what collection type of data do the requested measurements fall under?
   Category 2, Interaction Data.

5. Is the data collection request for default-on or default-off?
   Default on.

6. Does the instrumentation include the addition of any new identifiers?
   No new identifiers.

7. Is the data collection covered by the existing Firefox privacy notice?
   Yes.

8. Does the data collection use a third-party collection tool?
   No.

data-review +

Not a blocker, but it would be nice if we could link the data review from the Legacy telemetry for this data here for reference.

https://hg.mozilla.org/mozilla-central/rev/a545b4ccada9
https://hg.mozilla.org/mozilla-central/rev/a1d720739071

Data Reviewers, As part of this bug we adjusted some of the values returned in the result type for the engagement event. Wanted to check in to confirm that the data returned in the result types are still considered Category 2 as it has been flagged that it might be Category 2.5. The possible values (linked below) have been expanded to represent the type of search suggestion shown to the user and are limited in granularity to the merino provider level. While never report on the individual content of the suggested just what provider they come from, some providers have a small number of destinations (ie weather). Looking for data steward feed back and happy to discuss in further detail.

Sheet with all result values from the past 30 days as of 6/13: https://docs.google.com/spreadsheets/d/1KlY4qNME912lLaGyZ2dj08KKMIhl8uemnU2PjvkNtdA/edit

In Bug #1819766, this issue was brought up and resolved since it did not result in an engagement. However the results also changed for this engagement event so I wanted to flag this for additional review.

Wil is heading out on PTO, but if there are any follow-up q's, please needinfo me until he returns.

Since this is an engagement event and not just an exposure event(see my comment in the exposure event bug regarding this), it implies a particular client-id visits a specific url, in this case the provider for the weather info. This will change the data category from Cat 2 to Category 2.5+.

This should really get a new data-review request filed so that it can be properly escalated in order to comply with Data Collection policy. I'm happy to help expedite this as much as I can from the data-stewarding side of things, but I have little control or influence on how long the escalation process takes. I just wanted to call this out so the time frame for escalation can be taken into consideration before collecting this data with the provider information in it.

ni? mreid per the comment above.