Hi @VirginiaPoundstone, my responses are below:

• Does this relate to a current OKR?

I'm not sure if this relates to a current OKR - @CMyrick-WMF could answer that.

Contract update: Hamid Ghani's contract has been extended, with a new end date of June 30, 2024. @OSefu-WMF is now Hamid's manager.

Approved, thanks!

I'm scheduling time to follow up with Selena & others on landing on the relevance target. Needed ahead of meeting:

Approved as Omari's manager, thank you!

Per Neil: the draft framework doesn't have a default. and the recommendations aren't discoverable.

@MGerlach will consult on this. Assigning the investigatory task to @Mayakp.wiki.

Clarification per discussion with Jaime: this is related to the data that was compiled for the Equity Landscape Dashboard, but is not actually intended for the Dashboard. Instead, it's responding to the fact that we keep querying the same regional views for quarterly learning discussions, staff meetings, etc.

Approved as Neil's manager

@jbond Yes, confirmed, Hamid's contract end date is November 30, 2023. Thanks!

Removing this from the Pageview Data Loss epic, since this task also includes needs to account for other issues.

Declining this task, as our emphasis has shifted to unique devices, and the amount of work needed would be high.

Hi all, we have re-hired Hamid Ghani. I am the hiring manager. Can you please re-enable his accounts? Thank you!

Thank you for the updated 2020 vs 2023 chart, Hua!

Thank you @HXi-WMF !

@Mayakp.wiki can you update the unique devices with March data and let Hua know when that's ready?

@Iflorez can you update this with March data and let Hua know when that's ready?

Thank you @HXi-WMF!

Thank you @HXi-WMF !

Thank you @HXi-WMF ! I find the Y-axis padding to be particularly helpful here - because it gives a better sense of how new & returning change relative to each other.

Impact of this is low on high level metrics, so we would not prioritize this work from the high-level metrics perspective.

We are increasingly *also* reporting on user pageviews, because we've seen increases in automated traffic since 2022. However, we only split out automated traffic in 2020, so for longer-term historical views we still need to include automated traffic.

Thank you @HXi-WMF!

Thank you @HXi-WMF , I think these look good! Can you also provide an update for active editors - returning vs new using this format?

Adding Data-Engineering since we will work with them on the technical details.

Assigning to @Miriam as she'll be putting together the April staff meeting presentation and deciding on how to show the data.

@HXi-WMF updates to charts per our discussion:

• separate chart files into two groups: Readers (unique devices, content interactions) and Editors (active editors, active editors - returning vs new, net new content). This will make it easier to incorporate the charts into the two separate repos we have right now.
• add buffer/padding to Y axis, so that the chart's peak and trough do not extend through the full Y axis (per the draft Data visualization guidelines that Maya mentioned: "a good measure is for the line to fill two-thirds of the chart area height"
• For the data loss data: I agree with your suggestion of putting the data directly into the code as a temporary solution, rather than referencing data from Google docs. Make sure it’s well-commented.

@Volker_E After discussing this with the team, I suggest coming in to office hours to help you get the data needed from Superset. I explored the data and put together this dashboard - https://superset.wikimedia.org/superset/dashboard/403/ - so perhaps that meets your needs? The first chart shows the proportion of pageviews from IE11 out of all pageviews - and has conditional formatting to flag where that proportion is above 0.1%

We should continue to report on Wikipedia unique devices. Thank you for checking! I'll update the description to specify.

I've associated this with the ticket about improving automated detection - T280565