Discussed with @Tchanders today. This question depends on if we have a 'Done' button. Can not measure now. So move it to the wishlist.

Question 4: How many users are under investigation by the time the investigation ends?
answered by relevantTargetsCount

Move data analysis result to analytics ticket: https://phabricator.wikimedia.org/T265106

Guided Tour on initial page

Last week, @ifried and I discussed and decided to snapshot the watchlist event trend weekly, and separate nonbot and bot users in counting.
I created a dashboard to track the trend on each deployed wiki. So far, there are two data point on the dashboard, reflecting the trend over the last week. User is also able to slice and dice by wiki project, watchlist type ( permanent/temporary) and user type (bot/nonbot).

I have built a dashboard on Grafana to monitor the impact of the improvement.

Data timeframe:
Ran on 2020/10/14. Data timeframe is : 2020-08-26T17:07:01Z ~ 2020-10-14T18:50:56Z

@Mholloway thank you for digging in to it and clarifying the difference behind it.
@dbarratt @Niharika , given that do you agree to keep data capture as it is: not merging special:mute events to prefupdate table?

I am extracting data to answer Question 4 in ticket https://phabricator.wikimedia.org/T246951. After exploring that data, relevantTargetsCount seems related to each query action. Want to check with expert here : how to interpret relevantTargetsCount field and whether it's the field to answer Question 4?

@Nuria , Does any one in analytics team possibly know the answer to @dbarratt 's question?

Understand. There are 5 events for entire 2020, which has the same before and after.

@dbarratt I found only 2 events for the entire 2020 that the before and after are all false. The timestamps are show as below.

@ifried I have checked the data. Noticed a limitation of current data. As in 'watchlist' table and 'watchlist_expiry' table, there are no timestamps when the page was watched, it is challenging to identify which is the first watched page since deployment and track " the percentage of newly watched pages that are temporarily watched ". It seems that wl_id is generated incrementally. I could assume the first temporarily watched item (we_item field) in watchlist_expiry is the first watched page since deployment. It would miss to count a few items which were watched since deployment but did not use watch expiry. But it's the best estimation we could have with the current data.

@aezell thanks!

@Tchanders , thanks for the heads-up. I will double check the impact on existing dashboard and report.

Welcome. The manual work in the workflow still require some time. If you are familiar with Phabricator, you can create a similar ticket for #WPWP campaign. If not, you can fill in the analysis request, some member from our team will create a ticket based on the info on the request.

Analysis for below 4 requests are done. Added to Report for May 2020 .

• blocks and unblocks on editors acquired in May campaign ( 5/15/2020-6/5/2020)
• reverted edits in May campaign ( 5/15/2020-6/5/2020)
• blocks and unblocks on editors acquired in Jan campaign ( 1/15/2020-2/5/2020)
• reverted edits in Jan campaign ( 1/15/2020-2/5/2020)

Report was posted. Consider it is done.

@JFishback_WMF , thanks for the review and comment. Please find my answer here since they are the same topic.

@JFishback_WMF, thanks for the review and suggestions. Right, when I started the review conversation, the process is unclear to me. Will follow your suggestion next time.

I saw the data after 2020-09-24 19:00:00 showing up. Thanks!

Editor cohort analysis for May campaign ( 5/15/2020-6/5/2020) is posted at Report for May 2020. Feel free to comment.

@JFishback_WMF, please let me know if you have any concern.

@JFishback_WMF, please let me know if you have any concern.

The info collection is done. So close it.

Have reviewed with Niharika. It's done.

The trend of mute by preference setting increased. It increased significantly in Jun, July and August 2020. The growth is mainly from Italian Wikipedia. The growth is not from special mute because special mute is not captured in prefupdate table yet.

I documented our discussion about the expected deliveries here. Feel free to add if anything is missing.
Delivery

• editor cohort analysis for May campaign ( 5/15/2020-6/5/2020), using the same cohort definitions in Report for January 2020

Cover below 10 wikis, and any other wikis which has more than 20-30 edits or more than 2-3 editors

@Samwalton9 Thank you! Since I also need to analyze the blocks for Jan 2020 campaign, I downloaded 1/15-2/5 data from hashtag

To make it more clear, I added the description of the columns in the proposal.

To make it more clear, I added the description of the kept columns in the proposal.

The block notice tracking on mobile was enabled on Grafana in December 2018 and removed in April 2019 (https://github.com/wikimedia/mediawiki-extensions-MobileFrontend/commit/eebdabe65c067dbcfd9ddf59ab283ddcdba61b40). Previous report: https://meta.wikimedia.org/wiki/Community_health_initiative/Blocking_tools_and_improvements/Block_notices
Baseline data of block notices on mobile by wiki was retrieved at google sheet.

closed by accident. reopen.

Metrics discussion are at : https://phabricator.wikimedia.org/T246951

@Samwalton9, I am the owner of this task now. Can I schedule a meeting with you to know more about your request?

@Jhernandez I made some formatting changes on the page. Let me know if it looks better on smaller screen.

@Jhernandez thank you very much for your review and edits. And thank you for bringing up the formatting issue on smaller screen. I will adjust the format to make it more friendly to all sizes of screen. Thanks!

I have published the report to meta wiki. Feel free to comment.
Link: https://meta.wikimedia.org/wiki/Research:Emerging_Technical_Communities