Dashboard - Painel de Acompanhamento de Programas e Eventos

From Meta, a Wikimedia project coordination wiki
Jump to navigation Jump to search
This page is a translated version of the page Programs & Events Dashboard and the translation is 56% complete.

Other languages:
Deutsch • ‎English • ‎Gàidhlig • ‎Tiếng Việt • ‎dansk • ‎español • ‎euskara • ‎français • ‎italiano • ‎português do Brasil • ‎română • ‎русский • ‎українська • ‎العربية • ‎فارسی • ‎مصرى • ‎नेपाली • ‎हिन्दी • ‎বাংলা • ‎ଓଡ଼ିଆ • ‎ไทย • ‎中文 • ‎日本語 • ‎한국어

Programs & Events Dashboard

Manage and track Wikimedia programs from one place with ease.

Coolest Tool Award 2019 square logo.svg
Programs & Events Dashboard
2019 Coolest Tool Award Winner
in the category
Outreach

Program & Events Dashboard é uma ferramenta que auxilia a realização de eventos e programas educacionais em ambientes wiki.

Supondo que há um prgrama wiki, por exemplo uma atividade de edição para melhorar conteúdos em uma área do conhecimento ou um evento wiki, por exemplo um encontro de editores em um cibercafé. Para ambos casos, o dashboard é útil para:

  • Um botão de registro para os participantes informarem que fazem parte do programa.
  • Funções de acompanhamento para os organizadores avaliarem e relatarem os resultados de um programa.

O dashboard também controla os módulos de treinameto da Fundação Wikimedia, como os que lidam com assédio online e segurança dos eventos. Saiba mais sobre estes módulos.

Quem deve usar a ferramenta?

Encontre a ferramenta em https://outreachdashboard.wmflabs.org/.

São três as principais categorias de usuários da ferramenta: organizadores de programas, participantes dos programas e observadores. Organizadores podem elaborar uma página de evento e convidar qualquer pessoa com uma conta na Wikimedia para se registrar como participante do programa descrito. Organizadores convidam participantes dos prograas para se registrarem como parte do evento. Depois de se registrarem, os participantes não precisam mais retornar à página do evento. Muitos organizadores só retornam à página do evento uma vez, para coletar os resultados em um relatório depois do programa terminar. Observadores são usuários que podem ver os resultados dos programas dos quais eles não participaram.

If you would like to help with the overall organisation and administration of the tool you can now sign up to become an Admin!

Para organizadores

Organizadores preparam uma página de evento com a ferramenta. Ela permite compartilhar uma série de informações sobre o programa. Os participantes podem ver isso posteriormente.

Organizadores também têm direitos de usuário especiais para realizar ações como adicionar ou remover usuários manualmente de um programa, abrir ou fechar a inscrição no evento e gerar os relatórios de resultados.

Organizadores podem ser:

  • Educadores que incluem o uso da Wikipédia como ferramenta educacional em seus programas de ensino e desejam monitorar o progresso de seus estudantes nas edições.
  • Organizadores de eventos GLAM que desejam monitorar o carregamento de arquivos e edições.
  • Funcionários de afiliados que realizam eventos como edit-a-thons ou
  • Pessoas que querem usar o dashboard para monitorar o progresso na edição de conteúdos com um grupo de participantes.

(Provavelmente existem outros casos. Por favor, expanda a lista acima)

Para participantes

Participantes podem se registrar como parte de um programa. Muitos participantes não irão fazer mais que isto, apesar de participantes que os organizadores encorajam podem usar a página do evento como uma base para a colaboração com os colegas do programa.

Como se registrar em um programa existente é explicado nesta página.

Observadores

Organizadores, participantes e outros podem visitar o dashboard para verificar os relatórios de progresso.

Atualmente não existe nenhuma opção para produzir relatórios privados.

Guia

Instruções passo-a-passo

Para instruções passo-a-passo sobre como usar o dashboard veja orientações.

Perguntas frequentes

Por favor, veja FAQ.

Glossário de termos

É interessante usar uma linguagem comum para discutir os programas e eventos. Qualquer um que organize projetos Wikimedia pode verificar que é interessante aprender estes conceitos técnicos:

  • Dashboard é o nome desta ferramenta.
  • Programa é o termo para qualquer projeto wiki que pode ser acompanhado pelo dashboard.
  • Página de eventos é página no dashboard onde os participantes se registram nos eventos. Neste dashboard, algumas vezes a página do evento é chamada pelo termo mais geral "página do programa", porque nem todos programas incluem eventos presenciais. Aplicativos como o Facebook e meetup.com usam o termo "página de evento" e esta ferramenta cria sua wiki-equivalente.
  • O organizador é a pessoa que elabora e controla a página do evento. Esta pessoa tem permissões técnicas para controlar as páginas dos eventos que criar.
  • O facilitador é qualquer colaborador do organizador que também tem algumas permissões técnicas para controlar a página do evento. O organizador é "dono" da página do evento, mas o facilitador não.
  • Os participantes se registram na página do evento para que sua participação em um programa seja acompanhada.
  • Uma campanha é composta de programas individuais que são agrupados. Cada programa no dashboard é gerenciado por um organizador e uma campanha inclui vários programas.
  • Um organizador de campanhas é a pessoa que gerencia a categoria que agrupa os programas individuais. Esta pessoa pode também gerar relatórios coletivos incluindo todos os programas de uma campanha.
  • Um observador é qualquer pessoa que acesse os relatórios do dashboard. Observadores incluem todos os papéis acima, além de terceiros que não têm nenhum envolvimento com os programas além de ver as informações sobre o programa. Por exemplo, os funcionários da Fundação Wikimedia observam os dados, assim como instituições de pesquisa de todos os tipos. Como é rotina na comunidade da Wikimedia, a prática padrão é fazer com que a maioria dos dados estejam disponíveis publicamente.
  • An Admin is a user with advanced permissions on the dashboard. Admins can edit or delete any campaign or program, add or remove facilitators and organizers, in addition to other tools. They also provide general support to other users.

Example use cases

Common uses in all cases are a need for program participants to register and a need to report metrics for program outcomes.

Here are some example use cases:

  • A Wiki contributor hosts an in-person meetup at a library and invites anyone to join to contribute to Wikimedia projects together. At the event, the coordinator requests that attendees register themselves by clicking a "join" button. After the event, the coordinator checks the outcome report. The report lists all users who clicked the join button along with a description of what they did, including number of Wikipedia edits, uploads of files to Commons, or whatever else on any wiki project in any language. The report also summarizes the contributions of all participants collectively. A sample report might read, "10 people joined the event. During the event the group made 60 edits to 8 English Wikipedia articles."
  • Instead of a Wikipedia meetup in a library, an analogous meetup is organized at a school with a class of students. All students register as program participants. The class engages with wiki projects over the period of the class. At the end of the class, the instructor reviews the outcome report to judge the engagement of students in the project.
  • A multi-event campaign is proposed, designating a certain month for editing a certain type of Wikipedia article. Any program organizer anywhere can host their own event, and have their event listed and celebrated along with all others in that campaign. From the perspective of individual event coordinators, they operate the dashboard like any wiki meetup. From the perspective of the campaign coordinator, all local programs in the campaign series can be grouped together to generate a collective metrics report which is a sum of all the outcomes of all events in the campaign series.
  • A staffperson at an organization is managing a partnership between their employer and Wikimedia projects, such as in a "Wikipedian in Residence" relationship or perhaps just to host events. The organization has a long-term commitment to sharing information, and so takes a long-term view of Wikipedia partnership. In this case, the organization has 1-2 experts register for a dashboard program and edit 100 Wikipedia articles in different languages, then they mostly quit contributing. After 6 months, the organization gets a report from the dashboard which describes how many people viewed the articles to which their expert contributed. The organization compares the count of wiki pageviews to the reach metrics calculated by similar dashboards for Facebook, Twitter, or any other communication platform.

Enabling automatic edits on a new wiki

As of August 2017, the Dashboard can be enabled on a wiki-by-wiki basis to make automatic edits to post program information on-wiki. This includes:

Steps to follow for community members before enabling automatic template edits in Dashboard:

1. Get community consensus

Start a community discussion to ensure community support for turning on automatic edits. Community consensus is required before editing is enabled.

Here is an example for opening the discussion:

I'm proposing to enable edits via Programs & Events Dashboard on this wiki. Once enabled, related activity for courses and other events on Programs & Events Dashboard would be reflected with wiki edits, as currently done on English Wikipedia with the Wiki Ed Dashboard. Here are the types of edits it can potentially make:

2. Create the templates

Create a local version of each of these templates:

You should localize the names of the templates, but the parameter names used by these templates should stay in English.

It would be ideal if they could be placed under a common category for future reference.

3. Open a Phabricator ticket to request edits to be enabled

Assign @Ragesoss (User:Sage (Wiki Ed)), and be sure to include:

Here is an example of a Phabricator ticket.

News and recent changes

2017-12-08
  • You can create a 'private' program, which can only be seen by that programs facilitators and by dashboard admins. Participant usernames will not appear in the user list for associated campaigns.
  • The downloadable CSV of course stats now includes retention counts, as well as per-wiki breakdowns of edit count, articles edited, and articles created.
  • For the 'ArticleScopedProgram' type, you can now track entire categories, or articles that include a specific template, instead of just tracking 'assigned' articles.
  • Outreachy intern Candela Jiménez Girón has started her project to improve the dashboard for Art+Feminism 2018
2017-12-12
  • If you are enrolled in an editathon, you can run a manual update of the statistics by just clicking in a button from the course actions. This will provide more accurate information of the last revisions that took place.
2017-12-15
  • A new message is displayed in beneath the course activity that informs the user when the last update of those statistics was performed and the average time left for the next update to happen. This will enable the user to be aware that their contributions may not appear as part of the statistics until the next update after the edition happens.
  • When browsing the revisions, only 50 of them will appear listed, together with a "See more" button that will render 50 more if they exist. This will avoid rendering of too much information for the user in the page.
2018-01-05
  • The campaign creator can include a Default Course Type to their campaigns so any course created from the campaign will have a determined type. It is possible to change the type of the specific course afterwards. E.g. All the users of a campaign will be by default "Edit-athons" if the user set it as Default Course Campaign for the campaign.
2018-01-17
  • The campaign creator can set a Default Passcode to a campaign so all the courses created from that campaign will have the same passcode. This passcode can be a specific one, a random one or can be set as no passcode required. It is possible to change the specific course passcode afterwards.
  • The course creator can set different start and end times for the activity and statistics gathering OR for the event that will take place.
2018-02-15
  • The campaign list from the courses is now ordered alphabetically
  • We've updated the OAuth login permissions, which now include permission to create new accounts. We will start testing a feature that uses this permission soon. If you run into any errors, please log out and log in again.
2018-02-16
  • The 'account requests' feature has been enabled. To use it, you must enable it in the 'Available Actions' section of a program you are the facilitator for.
    • A facilitator can generate new Wikipedia accounts from the program 'Editors' tab, so we'll avoid creating too many accounts from the same IP, so Wikipedia blocks the IP for the next accounts creation.
    • A participant can submit a request to create an account from the enroll link. A facilitator can then create it from the dashboard; the password will be emailed to the new editor, and they will automatically be added as a participant.
2018-05-1
  • You can view the "Alerts" for any campaign, including when articles are in danger of deletion. This works currently on English and Portuguese Wikipedias, and can be configured on request for other languages that use similar categories for proposed deletion, speedy deletion, and deletion discussions.
  • Short programs, such as 1-day editathons, now have their own fast update cycle; such programs will typically get stats updates every 5 minutes or so, and stats will automatically be refreshed when the Home tab for the program is open.
2018-06-04
  • On the 'Articles' tab, program organizers can now add multiple 'Available Articles' at once. You can paste in a list of article titles or URLs, and each of them will be added to the list for editors to choose from.
  • On the 'Uploads' tab, the layout has been improved to show larger images, and more at once. Outreachy intern Urvashi Verma is working on further image/media improvements, and we want to hear your ideas.
2018-06-19
  • The 'Article Finder' tool from GSoC intern Pratyush Singhal is live and ready for use. You can access it here, or from the 'Available Articles' section of the Articles tab if you want to use it to build a set of available articles for a program.
  • On the 'Students' tab, you can now see the count of uploads by each user.
  • For wikis that have edits enabled, you can now disable edits for an individual program. In 'Edit Details' mode, change 'Wiki edits enabled' to no.
2018-07-19
  • The 'Uploads' tab has a new switchable layout - Gallery View, List View and Tile View.
    • Under the 'List View', you can now view the credit for each upload.
    • You can also filter the uploads by their uploader.
  • On the 'Students' tab, if you click on the 'Total Uploads' of a user, you can view the uploads made by that user.
2018-10-15
  • For 'Uploads', you can click an image to see more details without leaving the Dashboard, including which pages it's used on and how many views those pages get.
  • The 'Find programs' page has a search feature to find programs by name or institution.
  • Training modules now feature links back to the translatable wiki source pages for easier editing and updates.
  • The 'Structural Completeness' charts that show changes in ORES-based article quality estimates now work for all the languages that have an ORES articlequality model.
  • User profile pages show which training modules a user has completed.
2019-01-10
  • As the first stage of Cressence's Outreachy project, the course creator lets you select a program type at the start of the course creation flow. When creating a program from a campaign, the default program type for that campaign is still maintained.
  • Translation support for training modules is more complete.
  • You can embed the live stats from a program onto a blog or other website.
2019-01-24
  • For wikis that have edits enabled, there are now fine-grained controls for each program to select which types of edits the dashboard makes.
  • Since full approval after a trial period, account creation via the Dashboard can happen through a bot account, removing the need for program organizers to get English Wikipedia account creator rights.
2019-03-05
  • Admins now have notifications for when there are requested accounts waiting for creation, which should cut down on missed requests that don't get handled during events.
2019-07-01
  • The tracked wikis for each program are now shown clearly. You can choose the wikis to track at the time you create a program, and edit them afterwards. Assigned articles are no longer used as a workaround for tracking multiple wikis.
2019-07-02
  • For wikis with an ORES article quality model, the reference counts are now tracked.
2019-08-13
  • Individual articles can now be excluded from tracking. This can be useful for editathons where you wish to exclude unrelated contributions by veteran editors who also participated in the event, and similar situations.
  • For an Article Scoped Program, you can now use a PetScan PSID as the basis for which articles are tracked.

Technical development

The Wiki Education Foundation originally developed the dashboard for the exclusive use of its own supported class programs on its website at https://dashboard.wikiedu.org/ in 2015. The tool at the time was imagined as a replacement for the 2011 mw:Extension:Education Program tool, which had proven to be costly to manage. Because of outside interest in Wiki Education's tool, the organization copied their in tool in a separate website for community use and testing. With some early help with internationalization and the 'campaign' system from Wikimedia developers, Wiki Education has been maintaining Programs & Events Dashboard for global community use since 2016.

For more documentation on technical development see also:

External links