Jump to content

WikiLearn - Organizer Lab V2 – Designing campaigns and other Topics for Impact projects - html: things to pay attention to on content metrics:

From Meta, a Wikimedia project coordination wiki
@metadata
sourceLanguage"en"
priorityLanguages
Empty array
allowOnlyPriorityLanguagestrue
description"html in Organizer Lab V2 – Designing campaigns and other Topics for Impact projects - Learn the skills Topics for Impact organizers need to run consistent, high-impact campaigns that invite new contributors, partners, and supporters to the movement. "
label"WikiLearn - Organizer Lab V2 – Designing campaigns and other Topics for Impact projects - html: things to pay attention to on content metrics: "
display_name" things to pay attention to on content metrics: "
content"<p><span color="#434343" face="Poppins, sans-serif" style="color: #434343; font-family: Poppins, sans-serif;"><span style="font-size: 17.3333px; white-space-collapse: preserve;">Grantees' metrics are mostly focused on the number of contents per Wikimedia project (89% capture these). 35% of grantee globally disaggregate the type of contribution, 10% are collecting data to analyse content use/quality, 5% disaggregate content targets per knowledge gap. </span></span></p> <p><span color="#434343" face="Poppins, sans-serif" style="color: #434343; font-family: Poppins, sans-serif;"><span style="font-size: 17.3333px; white-space-collapse: preserve;">If you describe or clarify the kind of impact you want to have with an event or campaign, it can help grant reviewers and you understand the impact you want to have. Here are some things to pay attention to on content metrics: </span></span></p> <table> <tbody> <tr><th><img height="50" width="50" src="/static/Wikipedia_logo.png" alt="WikipediaLogo" />  Wikipedia</th><th><img height="50" width="50" src="/static/Wikidata-logo-en.svg" alt="Wikidata Logo" />  For Wikidata</th><th><img height="35" width="35" src="/static/Commons-logo.svg.png" alt="WikiCommonsLogo" />  For Wikimedia Commons</th></tr> <tr> <td> <p>There is a huge difference between creating high quality content on a big Wikipedia like English, French or Spanish Wikipedia or on smaller Wikipedias, especially if you have diagnosed a big knowledge gap on the smaller Wikipedias. Distinguishing between which languages you are targeting, with how much content can change dramatically the impact of contributions.</p> <p>Similarly, creating new articles from scratch vs improving content on existing high pageview articles has significantly different impacts. You know, for example, that writing content on a high pageview article will have readers, but creating new content that is already missing on the wikis could have high risk but higher reward if you think it will serve a public. Describing your intended impact with the content, can further clarify if your strategy will be effective.</p> </td> <td> <p>Edits on Wikidata can come in a lot of different formats: translating Wikidata item labels and descriptions, adding statements, adding references, etc. Understanding which kind of contribution that you are prioritizing can clarify greatly what kind of impact you want to have with an activity. Simply creating new Wikidata items is not enough if they aren't well integrated into the linked data ecosystem of Wikidata.</p> </td> <td> <p>A lot of communities run photowalks or photo contests that contribute hundreds or thousands of photos, but because they are not very high quality or don't have very good descriptions, they get lost and never seen on commons. However, a really good photography workshop might only produce 50 or 100 images but be comparatively easy to use to illustrate Wikimedia articles or be easy to find from search if with enough metadata.</p> <p>When developing metrics for commons, it's important to consider various other ways of documenting success such as # of edits adding structured data or categories to files, improving the descriptions, elevating images to Featured Quality, or making it easy to find the images in multiple languages with improved captions.</p> </td> </tr> </tbody> </table> <p></p>"