Program and Event Dashboard Feedback by Bukola James

Make use of the upcoming revert risk model to judge edits

2026-06-20 15:02:13 UTC

Track constraint violations resolved.

2026-06-20 15:03:29 UTC

Lexemes

2026-06-20 15:04:35 UTC

Please show Lexeme lables and not just the IDs

2026-06-20 15:04:35 UTC

Items created without references

Tools for easy follow-up with participants.

2026-06-20 15:06:21 UTC

Number of deleted items

2026-06-20 15:06:22 UTC

Number of edits acutally depends on tool used to edit, not a good metric in wikidata world.

2026-06-20 15:07:35 UTC

Items and Lexemes

2026-06-20 15:08:01 UTC

Separating them would be better for clarity

Is there an appropriate way, in terms of attribution of work, for an event organizer to have attendees contribute to a spreadsheet, then bulk upload that spreadsheet?

2026-06-20 15:12:15 UTC

Tracking of connecting identifiers to existing items (after proper reconciliation) is pretty important, but hard to measure.

2026-06-20 15:12:47 UTC

Editing Statistics of all Edit made on Wikidata properties

bukolajames1 — 2026-06-25 22:32:24 UTC

The dashboard has really been helpful for campaigns and events. During previous events, especially the Celtic Knot satellite events I organized for the Igbo language community, we mostly translated Wikidata properties, so that the Igbo language data can be used on Wikipedia and Wikiquote via Wikidata generated databoxes and descriptions while searching on the Igbo Wikipedia.

However, the dashboard don't show editing statistics of all edits made on Wikidata properties. I suggest that just as other mainspace items are tracked, edit on properties should be tracked as well so that several language communities can still use the dashboard to track edits instead of using other tools. Thank you for all you do.

How can users better search for and surface programs independently of campaign structures

bukolajames1 — 2026-06-25 22:35:16 UTC

I encounter challenges in discovering individual programs that are either:

not well connected to a campaign's dashboard,
placed under default campaigns like “Miscellanea,” or
difficult to locate outside structured campaign spaces.

Possible areas for improving the dashboard search

bukolajames1 — 2026-06-25 22:35:42 UTC

Some possible areas worth thinking about:

Advanced filtering/search for standalone programs
Thematic or keyword-based discovery across all programs, with a feature added during the dashboard setup process that allows organizers to indicate the subject area under which their campaign or event falls. Better visibility into “Miscellanea” or uncategorized programs
Search by tags, organizers, date ranges, or wiki focus
Improved historical discoverability for older campaigns/programs
Potential analytics/export workflows tied to search

participant level stats"

bukolajames1 — 2026-06-25 22:37:01 UTC

1)
I'd like to see a dashboard that shows me the longer term impact my event has had on someone's editing (e.g. were they a prolific editor whose editing remains unchanged after the event, a new editor who never edits after the session, an occasional editor who edits much more frequently for a month or two after the event before tailing off again etc). Atm I pitch my events at beginners but this kind of information would let me know if I'd be better off doing some follow up events or making more course like events.

As for how would I like to access or view this information - easily please! I am not good at remembering the names of tools, especially when they don't directly relate to the function it does and my bookmarks folder is already too full to be useful so there are lots of tools I've been told about repeatedly but can't retain. A nice obvious link from the dashboard would be lovely please :D

2)
I'd also add that the net words added can be a useful measure, but sometimes an editor might remove something that is out of date or incorrect and I don't think that's fully accounted for with the net approach (I could be wrong).

on "campaigns & contests" - it's much a case of "literally anything at all that would make administration easier" - I know that there are ways to do this - I'm wondering if it's actually a case of documentation and step-by-step guidance around how the dash can be used? Something that we could easily point volunteer community organisers towards, as well as ourselves.

More detailed participant-level statistics" and "Improved Wikidata integration."

bukolajames1 — 2026-06-25 22:38:52 UTC

All projects using Dashboard, and the ones that become more complex are the large-scale campaigns. I let them know that you're working on reducing the update time and on the "advanced search" option.

What Wikidata-related information would be most useful to see in the Dashboard?

bukolajames1 — 2026-06-25 22:40:25 UTC

The number of items created, improved, merged, or deleted during a campaign.
• The number of statements added, modified, or removed.
• The number of references added.
• The number of labels, descriptions, and aliases added by language.
• The number of images added through Wikimedia Commons and linked to Wikidata items.
• Statistics by property used (for example: country, instance of, located in the administrative territorial entity, coordinate location, etc.).
• Statistics related to Lexemes:
Number of lexemes created.
Number of forms added.
Number of senses added.
Contributions by language.
Contributions by lexical category (noun, verb, adjective, etc.).

What should be easier to track when reporting on Wikidata campaigns?

bukolajames1 — 2026-06-25 22:43:33 UTC

Contributions by entity type:
Items
Properties
Lexemes
• Contributions by topic (villages, cities, schools, rivers, biographies, monuments, etc.).
• Contributions by geographic area (country, region, district, department, etc.).
• Data completeness indicators.
• References and source quality.
• Multilingual contributions, including labels, descriptions, and lexicographical data.

What is currently missing in the Dashboard interface for Wikidata-focused work?

bukolajames1 — 2026-06-25 22:46:45 UTC

A dedicated Wikidata view rather than metrics primarily designed for Wikipedia.
A dedicated section for Lexeme contributions.
The ability to filter contributions by entity type (Item, Property, Lexeme).
The ability to filter contributions by language.
Visualizations showing the growth of statements, references, and lexical content over time.
Statistics on property usage.
Identification of items created without references.
Integration with the Wikidata Query Service (SPARQL) for campaign monitoring.
The ability to define target lists from Wikidata queries and automatically track completion progress.
4. How could the Dashboard better support Wikidata programs and campaign reporting?
Native integration with the Wikidata Query Service to monitor campaign targets.
Dedicated dashboards for thematic campaigns (geography, education, culture, health, open data, etc.).
Progress indicators showing how many target items have been completed or improved.
Interactive maps displaying geolocated items improved during a campaign.
Export of statistics in CSV, JSON, and other reusable formats.
Tracking contributions made through tools such as QuickStatements, OpenRefine, Cradle, and other Wikidata tools.
Dedicated metrics for Lexeme campaigns and language documentation initiatives.
Support for tracking contributions related to underrepresented and African languages.
Automated reports on lexicographical contributions, including lexemes, forms, and senses.
Wikidata campaigns are not limited to items and statements. Many communities, particularly in Africa, are actively documenting local languages through Lexemes. It is therefore important that the Dashboard provides the same level of reporting and analytics for Lexeme contributions as it does for Wikidata items.
As a contributor involved in projects related to Côte d'Ivoire localities, open data integration, and large-scale Wikidata improvement campaigns, I believe these features would significantly improve the monitoring and evaluation of Wikidata-focused programs.
Thank you for your work and for involving the community in shaping the future of the Dashboard.
Best regards,

Paul Bouaffou
Analyste-Programmeur (freelance)
Formateur en digital & Agripreneur
Consultant chez AL-FOURQANE GROUP SARL U
Support IT de Wikimedia Côte d'Ivoire