Met with Connie on 02/23 and discussed differences in Key Product Metrics vs Editors, Readers and Content dashboards
Will add documentation to Wikimedia Product/Data dictionary

I ran QA checks similar to T271455 but for data from Jan 6 to Jan 21 of the raw table (since mforns.session_length_daily (intermediate table) has data loaded from mid of Jan 5th)
The data in the intermediate table mforns.session_length_daily looks good and findings are similar to what we found earlier. Available in this Notebook.

QA checks performed for validating data between the raw table (event.mediawiki_client_session_tick) and intermediate table (mforns.session_length) is available on this Notebook

Instead of having a parent task for QA, create sub tasks for each of the tasks that move out of "Doing" and need QA . Or just assign the tasks that need QA/Review to @Mayakp.wiki

Status Update: Currently performing data-QA (added checkbox to description). Will update status this week.

Met with Jennifer on Feb 3, 2021. 1:1 document
Reached out to Ilana on Slack. Scheduled to meet her next week on Feb 9 and also attend the OCR improvement project kick off.

that worked! thank you so much everyone :)

Presented at the Tuning session on 01-28-2021 !

thanks Kate ! :)

@kzimmerman -
1] I created a new account on IRC Cloud with my staff email id. However the account is a free trial. How can I upgrade it?

I have Production access. However I am not marking it since I have to set up my new laptop and get access to all our systems on it.

Thanks @phuedx for the sample events. It would be great to see some events with new "inputLocation": "header-moved", but since @Edtadros is doing a local test we can look at it from his test results.

<Provide link to Data QA checks document once it is created>

thank you @MNeisler ! for your review :)

09/15 Meeting Notes: SearchSatisfaction Instrumentation & Data-QA

awesome, thanks @MNeisler for the feedback. :)

Moving this to Backlog, to pick up after I get back from Parental Leave (in dec)

Stretch goal for Q1.
Assigning to @cchen as I will be on parental leave starting Sep 21.

We've been able to get a few recommendations from stakeholders as a part of the Content Dataset Questionnaire.

Created QC document, updated link in description : Search Feature QC : Instrumentation QA and data checks

Currently drafting the Requirement Document : Content Data Accessibility

Requested @JTannerWMF to create Phab task template.

Hi @ppelberg, since data-QA is completed and the additional instrumentation work has been captured in T259673, I believe the scope of this task has been completed. We can go ahead and resolve it.

Updated VisualEditor/FeatureUse_data_dictionary
Added the following features:
mwUsernameCompletion

• Tagging a user in a talk page comment - using @mention or clicking an icon

Status and Scenarios tested :
Replying QC Template Post Deployment Data QA
Link to noteboks-
Data QA_Part 1_DiscussionTools
Data QA_Part 2_VEfu-new-fields

Completed Data-QA. Verdict: Data in both the schemas look good!
Here are some notes/observations.

Reviewed the QA-Instrumentation Checklist Phab Form with Kate and Jazmin.
Sent the content of the Data-QA checklist that we would like included in the Phab task template and added to Guidelines document, to Jazmin.
Next Up:

1. Present the template to Editing and Web teams
2. Document this in the QA Process documentation T228228

Checked the data in Schema:DesktopWebUIActionsTracking and everything looks good. Events from test wikis are in the schema as expected.
Results posted in this notebook.

Created and sent out Questionnaire for inputs from stakeholders on July 31.
Responses received are being added to the Use Cases section for technical translation.

@cchen and @Mayakp.wiki are reviewing articles and topics to determine accuracy of the 2 models we discussed :
Wikidata based topic dataset sample review
Outlinks based topic dataset sample review

In T258058#6331041, @Jdlrobson wrote:

@Mayakp.wiki reports that we should expect around 362 init events per sec from French Wikipedia so I think we're good to continue here with the 20% sampling rate.

Next steps

• Assuming everything is working as expected [i], @Mayakp.wiki is there any work left to be done on this task on your end (e.g. confirm the events/fields are being logged in the DB correctly)?

---

i. "Working as expected": as evidenced by all of the events in rows 182-204 being marked as Passed.

The number of events have picked up as of today. Here's the break up by day and wiki.

@alexhollender : Can you please file a task, set a priority and tag Product-Analytics ? We can triage this request tomorrow in our Board Refinement meeting.

Currently reviewing T238449 with Kate, Jazmin etc. before publishing it to Product teams.

Closing this task since we have started deploying on production test wikis.

• T255727 is complete, tested in T257909
• Donate (and other external links) T258513 : observed that they are not logged in Network tab but they are making it to the db.

Post deployment data-QA is being done in T256075

On July 23 @Edtadros helped fire many events to external links on Testwiki to check on this issue and I can confirm that all events have made it to the database.
Posted initial results here
We will be checking on the test wikis listed here T258058 in the next 2 weeks.

@Ryasmeen : I have added the events we finalized to our QC document and provided the exact section so you can find it easily.
pls feel free to reach out if you have any questions!

I have done some preliminary checks on the data and posted results here : https://github.com/wikimedia-research/Collapsible-Sidebar-Analysis/blob/master/Post%20Deployment%20Data%20QA%20for%20Collapsible%20Sidebar%20Instrumentation.ipynb

@Ryasmeen I have added a new section to the QC document and provided instructions in the Test Description of this task.
We are primarily looking at the data being stored in the 6 new fields. For that, I've added a few scenarios where you can trigger specific actions to validate them.
Please feel free to ping/chat or let me know if you have any questions.

Hi @CGlenn, thank you for opening this task and letting us know about its priority. We will triage this task during our next Board Refinement meeting on Tuesday 7/21 and provide you an update.