Training modules/Editathons/First Draft

For the live version of this training, see Training modules/dashboard/editathon

What is this page?


This page is the first draft of a training for event runners of Editathons designed to be deployed in the Programs and Events Dashboard training modules. The goal of this training, is to:

  • Synthesize the advice and documentation made by event runners over the years into a step-wise training for event runners with less or no experience.
  • Provide additional explanation to new event runners of the why of pieces of advice on pages and documentation, like English Wikipedia's "How to run an edit-a-thon" page
  • Create an English-language set of advice, that can be translated using the Translation extension so that local communities can better a) serve local language event runners and b) can modify the training to better reflect local-language editathon expectations.

As a first draft, there are a lot of issues including, but not limited to:

  • Elements that are wordy or hard to understand
  • Some of the advice may not translate well to other languages or to the context of non-English language Wikimedia communities
  • Missing pieces of advice
  • Missing illustrations or videos that could help better explain the concept in the slides

What this training does not include


This training does not include:

  • Substantial advice for work on Wikimedia projects beyond English or similar Wikipedia projects. There is room to write additional modules that evaluate the differences for editing events working on Wikisource, Wikidata, Wikimedia Commons, etc.
  • Technical "how-to"s for all of the activities related to editathons: these are best served by existing documentation elsewhere.
  • Substantial coverage of working in different fields of knowledge (medicine, art, women scientists, etc.) or different audiences (gender-focused editathons, GLAM-focused editathons, etc). This can also be created with additional modules at a later point in time.

How you can help


As a draft, we need help improving the training:

  • Please make copyediting, formatting, linking or language-simplification fixes directly to the page. Remember the audience for this training is a new contributor to the Wikimedia movement -- try to change language and ideas to be simpler and more welcoming.
  • Please provide high-level feedback on the following questions on the talk page:
    • Overall, do you think a new event-runner would be able to run an editathon after completing this training?
    • What do you think about the order and structure of the training?
    • Does the training provide too much information at any specific points?
    • Are their any gaps in the content that would prevent an effective event from being run?
  • If you think a slide or section should be substantially changed, please discuss the recommended changes on the talk page.
  • If you find a piece of advice or recommendation does not match your experience, please discuss this concern on the talk page.
  • If you would like to suggest an illustration, video or please make a recommendation on the talk page.

If you don't want to post feedback on the talk page, please email astinson wikimedia org .

Module 1: Defining your event


Slide: What is this training?


Welcome to this Editathon training!

The goal of this training is to introduce new and experienced facilitators to some of the best practices learned by the event running community for running editing events, frequently called editathons, backstage passes or editing workshops.

There are a lot of details, and a lot of opportunities for making mistakes when running these events: no editing event is ever perfect, and even the best organizers will forget some of the details that made previous events successful. Mistakes are lessons learned, and will help you better support events in the future.

This training comes in three parts: defining editing events, initial preparation for the event, and final planning and details as the event approaches.

The first two modules of this training include a series of preparation questions that can be used to help you plan an editing event.  You may want to write down the answers to your questions in a separate document or offline to help make sure that you remember to followup on challenges that you identify with those questions.

Slide: Introduction


Video: /File:Esto_es_un_editatón_de_Wikipedia.webm Caption: A video representing the 72 hour editathon at Museo Soumaya in Mexico city

Wikipedia editing events often come in different types, with different goals, for example:

  • editathons -- event focused on a particular topic, with the goal of building awareness about gaps on Wikipedia and introducing new editors to that topic
  • backstage passes -- events focused on exposing the collections, process or specialized knowledge of a cultural or research institution
  • editing workshops/trainings -- events where building editing skills among participants is more important than creating content
  • editing meetups -- events organized to support more experienced editors creating content, that are frequently scheduled at a regular time or place
  • micro-contribution events -- in person events that focus on fixing a particular type of problem or adding small repeated contributions

This training focuses largely on the more thematic content-creation focused events, frequently called "editathons," while having advice or guidance that would be appropriate for other kinds of editing events. Editathons come in many shapes and sizes, from small events that last only an hour with a few people, to 72 hour events that include dozens of contributors. These events cover all kinds of topics, including, but not limited to:

  • filling the gender gap, for example by covering women scientists or artists
  • developing representation of indigenous knowledge or languages to fill systemic bias gaps on the web
  • sharing deep knowledge from experts or institutions
  • filling gaps about local history or heritage sites

Running an editathon or other editing event requires several different things: time, a space to gather, event runners who can facilitate understanding of Wikimedia projects, and a willing audience who wants to learn how to contribute to Wikimedia projects. Facilitating these gatherings can be challenging and involve many details.

Slide: What is your goal?


Before running an event, it is important to ask why you want to run the event. Wikimedia communities frequently use contributing events to achieve a number of different goals.

A 2015 study of Editathons , found that most organizers ran this type of event to meet end goals such as:

  • Build and engage a community
  • Increase awareness of Wikimedia projects
  • Increase the diversity of information covered on Wikimedia Projects
  • Help make contribution to the Wikimedia community easier
  • Increase diversity of participants in Wikimedia projects.

Slide: Having realistic goals


Though editing events can have powerful impacts, experience from the Wikimedia community finds that singular Editathons or other editing events with largely new contributors:

  • Do not have a high retention rate of new contributors, unless a very deliberate effort for follow-up with participants is made. See for example, the outcomes of the 2015 report and the 2013 Report. Contributors during these events may be able to be re-engaged later for other programs or activities, especially if your event is part of a series of events.
  • Do not create very large volumes of content when compared to the productivity of experienced editors, online writing contests, or to more long-term mentoring of new contributors, like in the Education Program.

While creating a targeted, narrow content addition, edit-a-thons work best at:

  • building relationships with host institutions,
  • developing awareness about the Wikimedia Community
  • developing awareness of knowledge gaps, and
  • developing understanding of Wikimedia projects.

Slide: Preparation question: Your Goals


Throughout this training you will encounter “Preparation Questions”. These questions can be used to help you begin drafting the event plan for your event. Here is the first preparation question.

Preparation question: What are your high level goals for the event? What are the specific outcomes you hope to achieve with the event?

If you still have questions, find out more information about setting goals and targets on the Learning and Evaluation portal on Meta Wikimedia.

Slide: Partner organizations


For many Wikimedia communities, editathons offer an opportunity to collaborate with local organizations. Editathons can be hosted in partnership with many types of organizations. For example:

  • Libraries are one of the most common hosts for editathons. Libraries specialize in research, and often can support events and programs which promote research skills, local or specialized knowledge related to their collections, or promoting local community needs.
  • Other GLAMs (Galleries, Libraries, Archives and Museums) and heritage organizations: GLAMs and institutions like local historical societies, frequently support editing events in an effort to share awareness of their particular area or field of interest.
  • Universities and other research organizations that have expertise and a desire to build awareness about expert information across public platforms.
  • Government or non-governmental organizations: various types of government and non governmental organizations have knowledge that can be shared with the public with projects like Wikipedia, Wikimedia Commons and Wikidata.

Wikimedia communities all over the world organize events with ever more diversifying groups of partners. As an event organizer: make sure to innovate on who you work with, you may find surprising new partners who share your interest in promoting free, public knowledge.

Slide: Partner role and goals


Each organization type has different goals and needs from editing events. However, working with an organization for a editathon also enables a number of other opportunities:

  • Organizations can provide space and logistical support (such as ordering food or providing access to computers with internet connectivity). Very few editathons pay for space, because they use public venues or donated space.
  • Research organizations can provide sources for the volunteer editing to simplify the content creation process.
  • Promotion of events builds awareness for both the partner and the local Wikimedia community.
  • Organizations are able to work to advance public access to types of knowledge that they find important through highly visible digital platforms.

Slide: Avoiding Conflicts of interest


Note that when working with partners, you need to make sure that you find partners that share similar goals to you, so that you can develop a shared plan that meets the goals of both you and the partner.

Some partner needs will be different than your however. When evaluating, the needs of the partner its important to:

  • Avoid running events that may create a financial conflict of interest for participants, this is strictly prohibited by the Wikimedia Conflict of Interest Policy.
  • Avoid events that might be seen as promotional of the organization or partner helping host the event. Though promoting public knowledge and research relevant to an organization might be the main goal of the event, make sure not to promote just one point of view at the event.

If you are concerned that the event might engage in conflicts of interest, consider reviewing the section in the Plain and Simple Conflict of Interest Guide on types of conflict of interest

Slide: Preparation question: Partner Goals

    • Can you think of a partner that can provide support for an edit-a-thon? What type of support can they provide?
    • How do your goals and your partner’s goals compare? What is your plan to address those goals ?

Slide: Target Audience


After you have established your goals and capacities with your partner, you should next ask: who will be the participants for the editathon?

Editathon planning, resources and communications change significantly with different audiences. For example:

  • Students and university faculty may only be available during certain times of year and certain times of the week. Students may not immediately understand why they may need to get engaged, so may need to be encouraged through extra credit or other pre-communication strategies.
  • Working age volunteers may need for events to be run during weekends or non-working times like afternoons or evenings.
  • Working with professional groups, like librarians, museum staff or professional researchers, might require prior approval and support from administrators or managers at the organization.

Slide: Working with underrepresented groups


Many events focus on including underrepresented groups into Wikimedia communities. These underrepresented groups frequently face additional challenges, that you will likely have to anticipate. Here are some examples of how underrepresented groups might change your event's tactics:

  • If your goal is to encourage working-age women contributors, Art+Feminism has demonstrated that organizing child care and advertising this as part of the event, encourages more participation.
  • Working with ethnic, linguistic or cultural minorities may require making the space a deliberate safe space, where they will comfortable and welcomed through targeted communications strategies towards these groups.
  • Working with some groups may require adjusting your tactics or working with local cultural expectations, such as with indigenous communities, such as the Australian Aboriginal people, who have restrictions on how traditional knowledge is transmitted.
  • Working with senior citizens may require more helpers prepared to support other digital skills, such as using web browsers, digital library collections, and other software or hardware.

Slide: Preparation question: Audience


Once you have identified your audience for the event, you need to work on appropriate messaging to communicate your activity, goal, and why their participation matters.

For example, if your main goal is to train and engage women to be contributors to Wikipedia, the audience might need a message focusing on activism -- one that focuses on the key role of women advancing knowledge on the internet, for example.

Preparation questions: Who is your audience? Write a message aimed at your target group that is inviting to participate.

Slide: Experienced to new contributor ratio


Before running an editing event, one of the more important questions you should ask is: Do you or your expected attendees have sufficient experience working with Wikimedia projects to support newcomers during the event? And are there enough collaborators to share the work needed to support the size of the event?

Though anyone can edit Wikipedia and other Wikimedia projects, each project and each language version of the projects have different cultures and practices. If you have some experience or training in contributing to the project, and feel comfortable guiding new editors through the process, you will likely have a successful event.

Most events that train new contributors, need sufficient experienced contributors on-hand to help guide them through questions. Community experience suggests organizers need at least one experienced contributor for every 5-10 expected new contributors. This allows experienced contributors to answer questions, and support new editors throughout the event.

Slide: Creating a support team and finding help


If you don’t have much experience yourself or would like more support, consider finding a partner or ally to be either available in-person or for online support. Typically the best tactics for finding partners will be:

  • Wikimedia outreach communities, like WikiProject Women Scientists, Art+Feminism and Black Lunch Table, have developed fairly extensive training packets and networks of support for event runners with limited experiences. Connecting with one of these communities and participating in one of their trainings will help connect you with best practices, and find a network of support.  
  • Contacting a local Wikimedia affiliate. Editathons are frequently a core program strategy for local Wikimedia affiliates.
  • Asking local professional communities that may have experience; for example, in many parts of the world, library communities will have individuals with experience teaching Wikipedia contribution through events like #1lib1ref and Art+Feminism or participating in the Wikipedia Education Program.

If you find support from others, consider splitting the activities and roles listed throughout this training among collaborators. For example, one person might focus on communications, while another person can focus on training and supporting newcomers, while another person can focus on developing on-wiki worklists or resources.

Slide: Preparation question


Preparation question: How many people do you expect to attend? Who do you expect to be your experienced helpers at the event? Have you found an organization who might be able to connect you with other experienced contributors?

Slide: End of Module 1


This is the end of the first section of the Editing Event training. After this training, you should be able to:

  • Describe your goals for an editing event.
  • Describe your audience for that event.
  • Describe if you need to find additional experienced Wikipedia editors and how you can find them.

If you don’t feel confident doing these activities, consider reviewing the training again or reaching out for support through one of the communication channels listed on theGLAM-Wiki portal.

Module 2: Planning well before the Editathon


Slide:Introduction to Module 2


Like running any event, there are several sets of planning that help smooth the running of editing events. In Module 1, you learned about defining the goal of the event, about choosing an audience, and how to find additional support. This module, Module 2, focuses on the preparations needed in the 3-8 weeks leading up to the event: clarifying venue planning, communications and editing topics. Module 3 will focus on the details that you need to examine immediately before the event proper.

Slide: Venue


One of the first activities when planning any editing event is confirming venue plans. Once you have chosen a venue and negotiated a time for the event that is appropriate for your audience, it's important to think about other elements of using the venue for the event. If working with a partner, these will likely be simpler, because your venue partner may be able to help.

Choosing a venue or promoting features of a venue that will intrigue or encourage participation from both existing Wikimedia Community members and/or a broader public. For example, the #72HorasConRodin Editathon at Museum Sumeo, found that the novelty of staying overnight in a museum helped greatly increase interest in the editathon.

Slide: Venue Challenges


Common venue planning challenges, event runners encounter include:

  • Ensuring that timing of the event and access to the venue are well documented for attendees.
    • Some partners or host organizations will have limitations on how you access the spaces, or will require leaving the event at a particular time.
    • If access to the space will be limited, make sure to create clear instructions for how to gain access for the event or if people planning to attend end up arriving late to the venue.
    • Also consider if the design of the space would prevent participation from potential participants, including people with limited mobility.
  • Providing comforts and other support for the participants:
    • Ensuring that food and drink, such as coffee, tea, and water, is available throughout the event. Food both sustains energy during the event, and provides motivation and reward for attending the event. Though not all events include food, including food greatly increases morale and energy throughout the event.
    • Deciding if you plan on including childcare at the event. Childcare is particularly important for audiences that are likely to have young families.
    • Deciding if you want to include swag or other materials that can be handed out to participants.
  • Identifying if the partner/host organization wants to provide either a presentation by one of the experts on the event topic or a “backstage pass” of the institution’s operations. These thematic opportunities allow the partner or host to share some of their mission and role in the event with participants.

Slide: Preparation question


Preparation question: Have you confirmed the details for the event venue? What comforts or amenities are you considering providing for the event? Can you promote the unique elements of the venue or the event as part of communications?

Slide: Technology


Technology is the second, and perhaps more important, component of venue planning. When running Wikimedia editing events, people will require computers with internet access, otherwise participation is not possible. Before the event, it's important to ensure that the technology at the venue can support the participants. Early in your planning you should:

  • Identify if the venue has a strong enough WiFi network for supporting your size event, and that WiFi is easily accessible through a simple login process. If the WiFi requires a password, you will need to confirm the password in the weeks leading up to the event and provide participants that information during the event.
  • Identify whether participants need to bring laptops or if computers will be provided. It’s always a good idea to have several extra laptops on hand for participants to use if devices don’t work or if they don’t have personal laptops.
  • Ensure that there are sufficient power outlets for the laptop devices expected to attend.
  • Ensuring that you have some type of presentation screen (large TV screen or projector), that can be used for live demonstrations.

Slide: Preparation question


Have you confirmed with the venue that internet, plugs and computers can support the expected attendees? Do you have access to a projector?

Slide: Communications plan


Once date and time have been established with the partner, it's important to start building interest in the event, through communications. Typically these communications will be calibrated to reach two audiences: experienced Wikimedians through on-wiki communications and the more general audience that you identified in Module 1 through other communications channels.

Slide: On-Wiki communications


To include the Wikimedia community and encourage participation from local experienced editors, it's important to build an on-wiki presence for the events. Best practice is:

  • To create an on-wiki event page with the logistics . On English Wikipedia, the meetup listings and instructions can be found at: WP:Meetup . On wiki event pages provide a powerful tool for the event: you can ask experienced editors to sign up for the event, list potential editing topics or list research materials that can be used by participants.
  • Notifying your local affiliate about the event, so that they can activate local volunteers. Affiliates are listed at:
  • You may want to run a Geonotice, which places a text message in front of Wikimedia Contributors within a particular geographic region. On English Wikipedia the listing for Geonotices can be found at: Wikipedia:Geonotice

Slide: Public communications


Public communications can vary greatly by audience and goals of the program. Consider using the following:

  • Creating a public and off-wiki signup page using a Facebook Event, event, or similar event registration site. These pages help with the following:
    • New contributors to Wikimedia projects may have difficulty registering their interest on-wiki. Moreover, communicating with new contributors might be challenging if the only contact information you have is a Wikipedia User name (not all new contributors see messages on their talk pages).
    • If there is a limit on the number of participants you can support at the event (whether because of venue size or number of experienced participants), you can become aware of too much interest during the sign up process and plan accordingly. Note that on public event pages, frequently more people sign up then actually attend.
  • Doing announcement in venues appropriate to your audience:
    • Email outreach, such as newsletters of partner institution volunteers or patrons
    • Social media outreach, including targeted outreach on major platforms (Facebook, Twitter, etc) to influencers for your audience
    • Targeted flyers in the correct venues for your audience
  • Asking institutional partners to personally invite people who they think will be interested in the program. Many members of the public don’t understand what editing Wikimedia projects means: trusted staff at institutions can often encourage folks to participate, that might not take part in an edit-a-thon otherwise.

Slide: Preparation questions


Do you know which communication venues you plan to use for reaching participants? Do you have a plan for when you want to make those announcements?

Slide: Event themes


Most editing events have a theme that can appeal to your audience and encourage participation.A theme reflects the core concept of the event, and gives clear expectations to participants with regard to what they can contribute and learn by taking part of the event. Additionally, themes help people feel motivated to participate in the event. Members of the public who have never contributed to Wikimedia projects may not know why a broad call to “edit Wikipedia” is important.

Effective themes have the following characteristics:

  • Your host organization or broadly available digital research platforms have significant secondary and tertiary research about these topics (see the English Wikipedia guideilne for :Identifying reliable sources).
  • At least one of the participants supporting the event is knowledgeable about the broad topic. Having a knowledgeable person available can help participants with little understanding of the topic, navigate the right research materials and place the correct emphasis on content.
  • The topic will appeal to your expected participants. For example, Art+Feminism focuses on gender-activists, artists, and cultural heritage professionals as their audience, the theme of “Women in the arts” tends to appeal to all of these audiences.

Slide: Narrowing the focus of your them


Narrowing your broad theme, and limiting the potential scope of the contributions can help with topic identification (see subsequent slides). Common ways to narrow topics include:

  • Limiting the geographic scope of the topic, to the local region. Instead of “women artists”, you might focus on "women artists from Mexico City", if you are running an event in Mexico City.
  • Limiting the sub-discipline of the theme. Instead of the “history of Washington D.C.”, you might focus on the “economic history of Washington D.C.” or the “history of the neighborhoods of Washington D.C.”
  • Focusing on a particular event or point in time that reflects the broader theme. Instead of “French labor history”, you might focus on the “May 1968 events in France”

Once you have refined the theme, the next step is identifying articles that are appropriate for the topic. If you find that you cannot develop a list of topics based on the narrowed theme, consider modifying it.

Slide: Preparing topics


Online Wikimedia editing focuses on individuals finding pages they want to work on, and then contributing on their own time. In-person editing events work best when there is a narrow list of tasks that can be completed at the event. By preparing a list of articles that fit your theme ahead of time and pairing those articles with a handful of potential sources, you save participants from the complicated process of first picking a topic and then doing research.

When working with librarians or experts in the topic, they may be able to help you identify the source materials before the event, and prepare them for research (by pulling them from library shelves for instance, or collecting links to open access source materials).

Slide: Topics to avoid


There are also a handful of existing topics that you should avoid:

  • Topics with well-known or political disagreements about them. If there is widespread public disagreement about a topic, there is also probably widespread disagreement on Wikimedia projects. These kinds of topics, ranging from the Israel-Palestine Conflict to Alternative Medicine or Scientology, may accidentally expose the new contributors to aggressive editors or long-standing disputes.
  • Topics with very active recent edit histories ( for a tutorial on reading Page histories, see: This article might be currently of interest to active editors.
  • Topics about living people, especially if those people are directly affiliated with sponsor organizations or are not well-documented by reliable periodicals. Biographies of living people articles undergo additional scrutiny by other Wikimedia community members.

Avoiding high-conflict or high activity pages helps new contributors avoid creating content that might be rapidly removed from Wikipedia articles or creating content that may accidentally lead the new contributor into conflict-situations created by passionate editors.

Slide: Choosing your approach to editing articles


There are two types of Wikipedia articles that typically get used in article-writing events:

  • Existing articles: The best type of articles for Editathons are existing short or under-researched articles that can be easily expanded. This is especially true if the event runners are not experienced contributors to Wikipedia. Existing articles have already been on Wikipedia for some time, so have been reviewed by at least one or two community members as Notable (eligible for inclusion in Wikipedia). For example, in 2017 the Art+Feminism Campaign shifted to encouraging expansion of articles. Since they mostly work with new organizers and contributors, they found fewer incidences of articles being nominated for deletion or negative criticism from community members.
  • New articles: Encouraging new editors to write new articles can be challenging: new contributors don’t always know how to integrate articles into Wikipedia in ways that other editors acknowledge as quality work. Additionally, by starting with new articles, new editors have to engage in some of the more complex components of content writing (such as deciding the structure and scope of the page). Nevertheless, some editathons require starting new content, especially when the editathon is focused on a topic less covered on the projects.

When preparing suggested articles for new contributors, consider having 5-10 more articles than you expect attendees. This allows for attendees to have sufficient amount of choice among the articles, allows folks to work on different topics if they get stuck, and accounts for unexpected attendees at the event.

Slide: Focusing editathons on smaller contributions


Research from the Wikimedia Foundation on New Editors and experience from program organizers, suggest that teaching new contributors to write entire articles during in-person editing events,can be overwhelming and does not help contributors continue contributing after the event. Instead, new editors work best on smaller and less complex but repeatable contribution skills. By using these smaller contribution strategies, organizing an event will be simpler and new contributors are more likely to be retained.

There are a number of ways to contribute incrementally to Wikimedia projects, that show new contributors valuable quality-content-related skills. For example:

  • The #1lib1ref campaign encourages libraries to run editathons that only add references to existing content on Wikipedia.
  • The Smithsonian ran an event that encouraged folks to just add content to the Infoboxes on English Wikipedia.
  • After batch uploads of media files to Wikimedia Commons, some events focus on adding these images to Wikimedia pages, and adding relevant contextual information about the images.
  • Transcribing content on Wikisource is a common activity across many different language communities.
  • Contributing to Wikidata can take far less time than Wikipedia, because it does not require writing. Currently, however, introducing Wikidata and its editing interface to new volunteers may take longer than introducing Wikipedia.

Editathons or editing events focused on edits smaller than entire articles allow editathons to be run with a shorter window of time, because these kinds of contributions require less training of new contributors and the actions take less time. For example, many #1lib1ref editing events ran for less than an hour in time. We recommend new organizers work with simpler contribution strategies to become more familiar with common activities in the Wikimedia community and to simplify event organization.

Slide: Identifying existing articles for expansion


Generally when looking for articles that new contributors can work on within your theme for the event, you are looking for several characteristics:

  • Articles that are short or are missing common sections for articles of that genre (for example, Biographies missing significant information on “Early Life and Education” or articles about organizations missing significant information about their history).
  • Articles about concrete topics that don’t require expert interpretation of research to define scope. For example, articles about proper-noun people, buildings, pieces of artwork, or organizations are much easier to write than survey articles about well-studied academic fields or theories with many different interpretations. Topics with a distinct keyword that editors can use in searching for research materials helps significantly (such as a fairly unique name or title).
  • Articles that don't have many footnotes or other references. This indicates that an experienced editor hasn't likely spent significant time developing the article, reducing the potential for conflict or that contributions will be removed.

Slide: How to find existing articles


When choosing articles to work on, it might require a bit of exploring in Wikipedia. The easiest ways to find articles are:

  • Searching for topics of related interest to the editathon topic using both Wikimedia’s internal search or through external search tools like Google.
  • Investigating categories related to the topic of the editathon. For information about navigating categories, see en:w:Help:Navigating Categories
  • Finding a WikiProject which might document the topic area and examining articles listed as part of the project.  WikiProjects are listed on English Wikipedia at: . Most WikiProjects have article assessment grids that can be used to find stub and start class articles which might be appropriate for an editing event.

Pro tip: If you are comfortable with Wikidata, it is possible to use Wikidata Queries to create comprehensive worklists for campaigns. The main tool for creating these lists, can be found at: Template:Wikidata list

Slide: Identifying content gaps for editathons


Many editing events want to create new content that helps fill gaps on Wikipedia. Although writing new content increases the representation of diversity on Wikipedia, new contributors can often struggle with a) finding a suitably “notable” topic, b) creating an article from scratch that is sufficiently “wikified” to pass through initial scrutiny from other editors, or c) figuring out the correct structure for organizing the new content. We recommend that less-experienced contributors to Wikimedia projects not encourage event participants to create new articles.

To help simplify the articles creation process process, screen topics ahead of time, and provide at least a handful of references for each topic to save research time among participants. To identify a topic that is likely appropriate for writing an article for in an Editathon, consider the following:

  • That the article will meet the General Notabilty Guidelines: that the topic has lasting interest and there is significant coverage in reliable secondary sources (Newspapers, Magazines, Books, Academic articles) or tertiary sources (Encyclopedias, etc). For editing events, it is a good practice to find at least 2-3 sources that editors can use to establish notability.
  • That the article can be reasonably expanded through additional research, using simple digital search techniques. By finding topics that are easily searchable, both Wikipedians and the new editors can either expand the articles or verify that the topic is in fact notable.
  • That the sources materials for the topic are easy to read by your editing-event audience, and cover various aspects of the topic. This ensures that the inexperienced editors can create content during the event about the topic that is sufficiently broad to make the article useful. Try to avoid topics that will primarily be covered in expert documentation if engaging non-expert audiences.

Make sure to create redlinks for the appropriate name for the article in the on-wiki event page. Also, its is a good idea to include external links to existing digital sources about the topic or work with librarians to pull off-wiki materials.

Slide: Preparation question


Preparation question: Have you identified enough topics to help orient contributors at your event to potential editing activities?

Slide: End of Module 2


This is the end of the second section of the Editing Event training. After this training, you should be able to:

  • Feel confident in confirming the venue plans for your event.
  • Develop a communications plan for your event
  • Identify topics relevant to the theme of your event
  • Creating a working list for event participants

If you don’t feel confident doing these activities, consider reviewing the training again or reaching out for support through one of the communication channels listed on the GLAM-Wiki portal.

Module 3: Planning leading up to the event


This module helps you anticipate the various planning leading up to the event. Consider reviewing this section of the training at least two weeks before the event, to make sure that you are prepared to run the event during the day of.

Day-of preperation mostly focuses on:

  • Ensuring attendees understand how to participate effectively
  • Tracking participation in the event
  • Maintaining a welcoming and safe space

Slide: Scheduling


As the event approaches, it's important to make sure that the draft schedule for the event is posted on-wiki for participants to plan ahead. This helps participants: a) plan ahead if they want to leave the event or show up late, b) ensure that organizers and participants share an expectation of what will happen during the event, and c) offer a point of reference throughout the day.

Here is an example schedule for a 4 hour editathon:

  • 1:00: -- Introductions and welcome to the space
  • 1:10 -- Topic introduction by expert
  • 1:20 -- Introduction to Editing Wikipedia
  • 1:50 -- Picking topics for each editor and initial questions
  • 2:00 -- Snack break
  • 2:15 -- Article writing
  • 3:30 -- Check in on what everyone has been doing
  • 3:45 -- Article Writing
  • 4:45 -- Final reflections and wrap up

Notice how the example schedule has deliberate breaks and check-in points where the organizers plan to do small evaluations of what is happening and the event effectiveness.

Also, notice how the introduction to Wikipedia editing is kept short: though Wikipedia is complex and has lots of different components, it's important to limit the amount of time spent on this portion of the event. Editathon attendees need both the time and opportunity to contribute during the event, and many will not retain all of the information introduced during the training.

Slide: Creating you dashboard event


Once your on-wiki page has been created, it is important to create an event on the Programs and Events Dashboard: see the documentation on Meta Wiki. The Programs and Events dashboard provides several important functions:

  • First, it allows for automatic collection of  global contribution metrics from participants in the event.
  • Second, it allows for rapid evaluation of the impact of volunteers on Wikipedia articles through both machine-learning based quality tools, and pageviews for content created.
  • Lastly, it allows for your event’s impact to be rolled up into other metrics collection by affiliates, community members, and the Wikimedia Foundation.

To register participants in your dashboard event, you can:

  • ask participants to sign up there in advance of the event.
  • add participants manually during the event and after it has ended.

Note: If you collect usernames in a private listing either offline or on a private webpage, its important to get consent from participants to include the user name on a public listing, in order to protect individual privacy.

Slide: Reminders before the event


As your event approaches, be prepared to remind the list of potential attendees several important details:

  • To bring laptops, if the event is not hosted in computer lab or with enough loaner devices.
  • To register Wikimedia accounts ahead of the event: many wikis have caps on how many accounts can be created at one location in one day. Each Wikipedia has a cap of 6 accounts per day per IP address (learn how other program leaders deal with this concern).
  • Reminders about logistical for the event: such as child care, access challenges, and other venue access limitations.

These reminders ensure that folks remember to participate and are prepared to do so, especially if attendees signed up well ahead of the event.

Slide: Being prepared to welcome editors


After setting up your event space, it is important to welcome participants as they enter the event. Arriving at least 30-40 minutes in advance of your event, allows you to set up the space, talk to people as they arrive early and provide them with key information as they enter the door. You may want to consider:

  • Having a sign-up list at the door, and someone ensuring that participants have created Wikimedia account. Identifying folks without accounts before the event allows you to help them with that crucial setup step before the event starts.
  • Providing a handout with key venue information (Wifi access codes, for example), key links for participating in the event (links to the meetup page or Program and Events Dashboard page, for example) and/or social media information (Hashtags, organizer handles, etc).
  • Providing a means of identifying themselves with nametags or table tents.
  • Having a slide or wiki page on the projector with key information.
  • Having food out, and directing participant attention to the food.
  • Even if most research materials identified for the event are digital, placing a couple of books, magazines to provide something for participants to browse while taking breaks.

Preparing materials for these steps well in advance will help make welcoming participants easier.

Slide: Training new editors


Because you have a limited amount of time during an editathon, and cannot expect new Wikipedia editors to walk away “knowing everything” it is important to limit what you introduce editathon trainees to during an editing event.

There are two tactics commonly used by event runners for providing these introductions: using slides or doing a live guided presentation using a lesson plan created before the event. For example slides, see the Commons category for those slides.

Event presentations typically include:

  • A welcome that sets the tone for the event. Make sure to welcome folks to the Wikimedia community, and invite them to participate.
  • Thank yous to supporters of the event.
  • Reminders about venue logistics -- including, WiFi or computers logins, fire escape and bathroom locations, including gender neutral restrooms, etc.
  • A brief training for new editors (see next slide)
  • Reminders about how to keep track of contributions through the Programs and Events Dashboard or the event page.

Slide: Training topics


When running article writing events focused on writing Wikipedia articles, it is important to introduce new editors to:

  • A high level overview of Wikipedia, including the 5 Pillars.
  • The principles behind Notability and Verifiability.
    • These concepts can be hard to explain verbally, it might be useful to use the following video: on Sourcing and Verifiability.
    • It is also important to highlight that Wikipedia summarizes the sources it cites. Some new editors may not be familiar with best practices for avoiding plagiarism or accidental copyright violations.
  • How to create a draft in User space or Draft space.
  • Using Visual editor to add the following:
    • References using the “Cite” toolbar
    • Basic formatting and structure to an article, including bolding article titles, italics, etc
  • How to develop the structure for the type of article you expect attendees to be working with, such as biographies, buildings or events.
  • The difference between Visual Editor and WikiText editor and how to switch between the two. Though most new editors do not show a preference for WikiText editor, it’s important to show folks how the WikiText editor works, because they will have to interact with it eventually in talk pages or when fixing complex formatting on pages.

Creating handouts or tailored welcome docuements with important links and a short introduction to wiki-text can help participants follow along. Examples of existing ones can be found on the Commons category for Wikipedia Reference cards.

Slide: Other knowledge to prepare


There are many other things that are likely unnecessary to teach during the initial training, unless they are part of a goal of your event. However, at many editathons, participants have questions about:

  • How to find and use templates, especially Infoboxes
  • How to engage with talk pages
  • How to illustrate Wikipedia articles with existing content on Commons or upload content to Commons
  • How to use web browsers, copy and paste functions, and other technical literacy skills.

Editathon slide decks used by other program leaders can be found at: this Commons category.

Slide: Common technical challenges


There are a number of common technical challenges that might arise during editathons, here are the main ones that can prevent editors from contributing during events:

  • Not enough editors created their accounts ahead of time, so you have to create more accounts than is allowed at your location because of the six-account limit. Consider the following:
    • Have participants sign up on other Wikimedia projects: . These accounts can be used across wikis.
    • Have participants create accounts on their smartphones. We don't recommend they edit on their smart phone, the interface isn't really good enough, but if they have mobile data it will be on a separate IP to the venue and each smartphone will have a 6 account limit. This will not work if they are connected to WiFi from their mobile phone.
    • To work around this, there is a an on-wiki set of triage opportunities at:
    • If you have a Wikipedia administrator or account creator on hand, they can create accounts via:
  • New editors can’t move pages from a draft to "Article" space (see w:en:Wikipedia:Moving a page). This is typically prevented because New User accounts have yet to receive the AutoConfirmed right (automatically issued at 10 edits and four days on English Wikipedia).
    • This is one of the important reasons for having experienced editors around: they should have an account capable of executing the move if they have made ten edits and had accounts over 4 days old.
    • Note: that English Wikipedia will be implementing ACTRIAL in September 2017, which prevents new editors from creating articles altogether in the New Article namespace. Starting new editors in another space, whether its User Sandboxes or Draft Space and then moving the content with a more experienced account is the best tactic.

Other technical challenges may arise, however they will typically not prevent individuals from contributing to Wikipedia. Having experienced editors on hand will likely allow you to avoid these challenges, or provide shortcuts or work arounds for fixing the problems. Its also helpful to have additional editing devices on hand, in case technical challenges are created by individual devices.

Slide: Keeping the space active


During the event, event runners frequently find that they don’t have enough time to edit themselves: this is okay.

Part of helping people feel engaged and successful, is maintaining morale and ensuring that folks feel supported throughout the event. It might be useful to designate which event runners will:

  • Keep an eye out for people getting “stuck” -- sometimes folks will try to triage challenges in Wikipedia or get stuck finding sources for their topic.
  • Remind folks to save often, and focus on contributing at least some information. If participants add just a few citations to a page, it provides a foundation for future editors and readers.
  • To remind folks to take breaks, eat the food, and get fresh air away from computer screens.
  • Capture the user names of participants. Even if you ask participants to record their user names, that step is frequently missed.

Slide: Maintaining a Safe Space


Another important consideration when running public events, is maintaining a safe space during the event. When working with partner organizations, they likely have strategies for maintaining a safe space, especially if they regularly host events open to the public. Make sure you understand how to take advantage of that strategy when coordinating with your partners.

On occasion, either registered attendees or members of the public will disrupt events or have inappropriate one-on-one interactions. Preparing yourself to respond to these occurrences will help ensure that all participants feel welcomed as part of the Wikimedia Community and inappropriate behaviour is curtailed.

Minimally, it is important to:

  • Be mindful of interactions among individuals at the event, and be prepared to intervene or get help from venue staff to intervene.
  • Be mindful that many members of the Wikimedia community want privacy of either their real world or digital identities. For example, if individuals ask not to be photographed or their real names used, we need to be mindful of such requests, and take action to enforce them (such as warning photographers at the event about the individuals requesting not to be photographed).
  • If you expect the event to be particularly large, it's best to designate one of the event runners to be primary person responsible for maintaining a safe space.

Slide: Planning for Safe Spaces


Maintaining safes spaces can become more challenging if you plan on running multiple events or your event will be quite large. If you do not have experience managing safe spaces or if you are running larger or more complicated events, we highly recommend:

  • affirming a "friendly space policy" as part of your events (see movement friendly space policies on meta)
  • taking the safe event training from the Wikimedia Foundation on the Programs and Events Dashboard.

Both will help you create effective proactive strategies for implementing best responses towards inappropriate behavior during events. Local organizers can set the expectations for events, that can then be enforced. Moreover, preparing a plan ahead of time, will make response to inappropriate uses during the event more effective.

Slide: After the event!


Success! You made it through your editing event! There are a lot of opportunities for overlooking things or making mistakes, but your learned from those mistakes, and all in all it was a successful event! Now for a bit more communications and tracking!

Beyond running the event , there are a few steps that you may want to use to ensure that everyone (you, your partners and the participants), get the most from the editathon:

  • Make sure to integrate any user names into the Programs and Events dashboard, so to generate metrics on the event. Note: if participants did not sign up with their user names on a public sign up page, by either signing into the Programs and Events Dashboard and registering themselves, or listing their usernames on a public event page, its important to get consent for publically associating the User ID with the event, to protect privacy.
  • Report outcomes and metrics to your participants and partners who supported the event. It may be useful, to evaluate these outcomes in light of the goals you set at the beginning of the program. Reporting outcomes can help remind folks of the impact of the event, and that you still are interested in supporting their participation in the Wikimedia Community. Also, consider continuing to monitor
  • Share impact and outcomes on easy-to-initate communication channels, like social media, on-wiki talk pages of participants in the event, and with Wikimedia affiliates in your context. Even though not everyone on those channels attended the event, finding out about its impact might encourage folks to continue participating in future events or to clean up pages created by the event.
  • Use the "Thank" button to thank participants in the event for useful edits. Additionally, consider giving barnstars or other WikiLove to those who helped train or otherwise put in unusual effort.

Additionally, consider taking these more extensive steps:

  • Uploading event photos to Wikimedia Commons in "Category:Wikimedia editathons" (or a subcategory of that).
  • Writing a blog post, report for the Signpost, and/or the GLAM newsletter talking about who attended, what got done, and how it went generally. When you share your experience with the broader Wikimedia movement: make sure that you write about what you learned, what you would do differently, and why this event mattered.
  • Send a follow up email. Invite participants to relevant future events or tell them about wikiprojects that are relevant to their interests.

Slide: End of Module 3


This is the end of the third section of the Editing Event training. After this training, you should be able to:

  • Feel confident about your ability to finalize scheduling and reminders for participants
  • Understand what might be included in an introductory presentation which teaches participants how to participate
  • Understand common tactics for maintaining a welcoming, supportive and safe space.

If you don’t feel confident doing these activities, consider reviewing the training again or reaching out for support through one of the communication channels listed on the GLAM-Wiki portal.

Guides/materials consulted/reviewed before creating this training: