Learning patterns/Using the Programs & Events Dashboard for Reporting

A learning pattern forreporting
Using the Programs & Events Dashboard for Reporting
problemThe Program & Events Dashboard is a valuable reporting tool, but implementation is sometimes inconsistent when working with a large number of organizers or events.
solutionDevelop and share a plan for using the Program & Events Dashboard before starting a new campaign.
creatorMegs
endorse
created on12:36, 30 July 2018 (UTC)
status:DRAFT

What problem does this solve?

edit

This learning pattern describes how to generate an implementation plan for using the Program & Events Dashboard for reporting. This learning pattern can be implemented by any organizational body such as Wikimedia groups like a Chapter, User Group, WikiProject, or Campaign, as well as external organizations working with Wikimedia projects like research institutes, museums or libraries, universities, or community groups

The Program & Events Dashboard captures a range of metrics for individual events or programs which are then aggregated in a Campaign. These metrics include the number and titles of articles created and edited, total edits, words added, article views, Commons uploads, and the number and names of editors contributing to the program or campaign. Thus, in addition to providing the global metrics required of WMF grantees, the Program & Events Dashboard captures data that can be used towards more nuanced metrics in line with the 2030 Movement Strategy or otherwise defined by the organization.

While the Program & Events Dashboard is a valuable reporting tool, organizers often fail to configure Programs consistently across a Campaign. This leads to data inconsistencies and loss.

What is the solution?

edit

Develop standards and workflows for implementing the Program & Events Dashboard across a Campaign.

Things to consider

edit

Get to know the Programs & Events Dashboard

The Dashboard is still under development, and features may change after this Learning Pattern is published.

Define the Campaign

  • What metrics need to be tracked as part of the Campaign?
  • What is the title of the Campaign?
  • When will the Campaign start and end?
  • What Programs will be included in the Campaign?
  • Who is responsible for generating reports from the data collected in the Program & Events Dashboard?

Create a workflow for implementing the Campaign

  • Who will create the Campaign?
  • Who will create the Programs?
  • When will the Campaign be added to the Programs?
  • How will Editors be added to the Programs?

Develop standards for Programs included in the Campaign

It’s important to develop standards at the start of any Campaign so that metrics are collected consistently. The following questions will help establish those standards.

  • Does the Campaign require a consistent means of naming Programs? If yes, what is it?
  • If a Program is co-sponsored, which sponsor is listed in the Institution field?
  • Who should be added as a facilitator?
  • Will facilitators also be added as editors?
  • Will edits across multiple project and languages be tracked, or only edits on a single wiki?
  • Will all edits be tracked, or only edits to specific articles or categories?
  • Will activity be tracked outside of the specified event times? If yes, when will activity tracking start and end?
  • Will Programs be password protected?
  • Will Programs be public or private?
  • Are there additional details the organizers wish to capture? If yes, can these be captured via the Program description field or by adding a timeline?

Write an Implementation Plan

After answering these questions, write-up the standards and workflow required in order to meet reporting needs. Then post the implementation plan online so it can be shared with partners as needed.

When to use

edit

Wikimedia NYC developed the Wikimedia NYC Program & Event Dashboard Implementation Plan to meet reporting requirements for its sAPG 2018-2019.

Endorsements

edit

See also

edit
edit
edit

References

edit