Difference between revisions of "Submissions:2018/Analyzing and Reporting Attendance across Multiple Events"
Jump to navigation
Jump to search
(first version of proposal) |
(adding example) |
||
| Line 17: | Line 17: | ||
;Affiliation: Wikimedia NYC |
;Affiliation: Wikimedia NYC |
||
| − | ;Abstract: Analyzing and reporting event attendance and editor retention is crucial for both WMF-grantee reporting and guiding organizations in evolving their events, but also notoriously difficult to achieve. Wikimedia NYC has prototyped a method for reporting attendances across multiple events based on Dashboard data. Key features include separate reports for total attendances as well as unique editors, identification of editors recruited in the context of events, identification of returning editors, analysis of ''coattendances'', i.e., events with an overlap in attendees as compared to a given event, and tracking editors (both established and newly recruited) across events.<br/>''Workshop only:'' While this has been useful for the chapter both internally and with reporting to WMF, there seems to be no agreed-upon standard definition of what constitutes ‘retention‘ of an editor. As a consequence, for such analysis and reporting methods to be of comparative value across organizations, some discussion and standardization would be required, which a workshop might serve to get started with. Furthermore, in a workshop setting, attendees from other organizations managing their events and attendee records in Dashboard would be able to experiment with applying the Wikimedia NYC methods to their own context.<br/>'' |
+ | ;Abstract: Analyzing and reporting event attendance and editor retention is crucial for both WMF-grantee reporting and guiding organizations in evolving their events, but also notoriously difficult to achieve. Wikimedia NYC has prototyped a method for reporting attendances across multiple events based on Dashboard data. Key features include separate reports for total attendances as well as unique editors, identification of editors recruited in the context of events, identification of returning editors, analysis of ''coattendances'', i.e., events with an overlap in attendees as compared to a given event, and tracking editors (both established and newly recruited) across events.<br/>''Workshop only:'' While this has been useful for the chapter both internally and with reporting to WMF, there seems to be no agreed-upon standard definition of what constitutes ‘retention‘ of an editor. As a consequence, for such analysis and reporting methods to be of comparative value across organizations, some discussion and standardization would be required, which a workshop might serve to get started with. Furthermore, in a workshop setting, attendees from other organizations managing their events and attendee records in Dashboard would be able to experiment with applying the Wikimedia NYC methods to their own context.<br/>''See [[#Appendix]] some examples of Wikimedia NYC metric reports generated using the proposed method.'' |
;Length of presentation: |
;Length of presentation: |
||
| Line 36: | Line 36: | ||
Note the potential thematic overlap with [[Submissions:2018/Supporting editathon and other event organizers with new tools]]. The author of this proposal would be amenable to merging the two. |
Note the potential thematic overlap with [[Submissions:2018/Supporting editathon and other event organizers with new tools]]. The author of this proposal would be amenable to merging the two. |
||
</div> |
</div> |
||
| + | |||
| + | ==Appendix== |
||
| + | ''Below are some examples of Wikimedia NYC metric reports generated using the proposed method.'' |
||
| + | |||
| + | <table style='caption-side: bottom; border:.2ex solid grey;'> |
||
| + | <tr><th colspan="2">Report scope (Dashboard campaign(s)):</th><td colspan="3"> |
||
| + | Wikimedia NYC: Simple APG 2017 - 2018</td> |
||
| + | </tr> |
||
| + | <tr><th colspan="2">Number of events</th><td>47</td></tr> |
||
| + | |||
| + | <tr><th colspan=2></th><th>all editors</th><th>new editors<sup>2</sup></th><th>returning new editors<sup>3</sup></th></tr> |
||
| + | |||
| + | <tr><th rowspan=2>event attendances</th><th>absolute numbers</th> |
||
| + | <td>987</td><td>468</td><td>27<sup>4</sup></td></tr> |
||
| + | |||
| + | <tr><th>per event, on <abbr title=average>avg.</abbr></th> |
||
| + | <td>21.0</td><td>10.0</td><td>0.6<sup>4</sup></td></tr> |
||
| + | |||
| + | <tr><th rowspan=2>unique editors<sup>1</sup></th><th>absolute numbers</th> |
||
| + | <td>818</td><td>453</td><td>12</td></tr> |
||
| + | |||
| + | <tr><th>per event, on <abbr title=average>avg.</abbr><sup>5</sup></th> |
||
| + | <td><abbr title=not applicable>n/a</abbr></td><td>9.6</td><td>0.26</td></tr> |
||
| + | |||
| + | <caption style='text-align: left; font-size: 80%;'><table> <tr><td><sup>1</sup>)</td><td>counting each editor only once, even if attending more than one event</td></tr> <tr><td><sup>2</sup>)</td><td>subset of all editors</td></tr> <tr><td><sup>3</sup>)</td><td>editors recruited within the report scope who attended more than one event; subset of new editors</td></tr> <tr><td><sup>4</sup>)</td><td>includes first attendances by new editors who would later go on to return to another event</td></tr> <tr><td><sup>5</sup>)</td><td>effectively the number of such editors recruited per event</td></tr> </table></caption></table> |
||
| + | |||
| + | |||
<!-- Do not edit the section below. --> |
<!-- Do not edit the section below. --> |
||
Revision as of 09:57, 23 August 2018
- Title
- Analyzing and Reporting Attendance across Multiple Events
- Theme (optional)
-
- Editor Recruitment & Retention
- Tech & Tools
- Type of submission
- presentation or workshop
- Author
- Loren Koenig et al.
- E-mail address
- wikimedia‹АΤ›l-koenig.com
- Wikimedia username
- BlaueBlüte
- Affiliation
- Wikimedia NYC
- Abstract
- Analyzing and reporting event attendance and editor retention is crucial for both WMF-grantee reporting and guiding organizations in evolving their events, but also notoriously difficult to achieve. Wikimedia NYC has prototyped a method for reporting attendances across multiple events based on Dashboard data. Key features include separate reports for total attendances as well as unique editors, identification of editors recruited in the context of events, identification of returning editors, analysis of coattendances, i.e., events with an overlap in attendees as compared to a given event, and tracking editors (both established and newly recruited) across events.
Workshop only: While this has been useful for the chapter both internally and with reporting to WMF, there seems to be no agreed-upon standard definition of what constitutes ‘retention‘ of an editor. As a consequence, for such analysis and reporting methods to be of comparative value across organizations, some discussion and standardization would be required, which a workshop might serve to get started with. Furthermore, in a workshop setting, attendees from other organizations managing their events and attendee records in Dashboard would be able to experiment with applying the Wikimedia NYC methods to their own context.
See #Appendix some examples of Wikimedia NYC metric reports generated using the proposed method.
- Length of presentation
-
- 15 min (presentation)
- 45 min (workshop)
- Special requests
- video projector
- Preferred room size
- 20
- Have you presented on this topic previously? If yes, where/when?
- no
- If you will be incorporating a slidedeck during your presentation, do you agree to upload it to Commons before your session, with a CC-BY-SA 4.0 license, including suitable attribution in the slidedeck for any images used?
- yes
- Will you attend WikiConference North America if your submission is not accepted?
- probably
Note the potential thematic overlap with Submissions:2018/Supporting editathon and other event organizers with new tools. The author of this proposal would be amenable to merging the two.
Appendix
Below are some examples of Wikimedia NYC metric reports generated using the proposed method.
| Report scope (Dashboard campaign(s)): | Wikimedia NYC: Simple APG 2017 - 2018 | |||
|---|---|---|---|---|
| Number of events | 47 | |||
| all editors | new editors2 | returning new editors3 | ||
| event attendances | absolute numbers | 987 | 468 | 274 |
| per event, on avg. | 21.0 | 10.0 | 0.64 | |
| unique editors1 | absolute numbers | 818 | 453 | 12 |
| per event, on avg.5 | n/a | 9.6 | 0.26 | |
| 1) | counting each editor only once, even if attending more than one event |
| 2) | subset of all editors |
| 3) | editors recruited within the report scope who attended more than one event; subset of new editors |
| 4) | includes first attendances by new editors who would later go on to return to another event |
| 5) | effectively the number of such editors recruited per event |
Interested attendees
If you are interested in attending this session, please sign with your username below. This will help reviewers to decide which sessions are of high interest. Sign with four tildes. (~~~~).
- Add your username here.