=What are we designing
As a user, I want to get summary information at a glance about my programs and events. There are three pages in the system which share a similar (though not identical) design: The multiple programs, single program and single event screens. These are the core of the system.
For more details see wiki posts [[ https://meta.wikimedia.org/wiki/Community_Tech/Tools_for_program_and_event_organizers#Sept._6,_2018:_Proposed_metrics_features%E2%80%94what_do_you_think? | Proposed metrics features—what do you think? ]] and [[ https://meta.wikimedia.org/wiki/Community_Tech/Tools_for_program_and_event_organizers#Sept._6,_2018_(continued):_New_data_and_reports_in_detail | New data and reports in detail ]].
=Design challenges / ideas
- We should probably move the participant setup and editing functionality to the Event Setup screen. But...
- We could still present a list of usernames, with links to each user's Talk page, Contributions and Sandbox (if that wiki has sandbox). That way this screen could also become an useful tool during events to help the organizer and helpers monitor contributions.
- How do the data screens relate to the reporting functions? Are the reports available from the screens, or is there a separate report-setup page users will go through before downloading that will contain the filtering interface for Worklist, Categories, Participants, Wiki and Namespace filters?
- Many or most of the metrics listed will require definition information to, for example, explain what is meant by "7-day retention." This information is currently contained in little panels popped by "info" icons, but whether that scales is unclear.
- The need for info about metrics is complicated by the new filter settings we're adding. For any display of metrics, users will need to know what filters are active. E.g., is that # of pages in all namespaces or just main? Is this # of edits to only the worklist? Etc.
- It may be useful to divide the metrics into logical groupings, to improve readability. Two main groupings that occur are "Contributions" (pages created, uploads, bytes added, etc.) vs "Impact" (pageviews, mostly, but also # of articles in which images are placed).
- Remember that some events and programs encompass multiple wikis. It appears to be a design principle now that different wikis are separated out at the Event level @Niharika, can you explain why that was done? And do you think the fact that we are offering a wiki filter will change the need to do that?
=Data for the Event Screen
Below is an edited list of Event Screen data, including both data that exists in the system now and data we propose to add. I've broken this list into three parts: "descriptive information" about the event, which will be displayed at page top to identify and describe the event; "event data", which lists the main metrics; and "Participants", which is a re-thinking of the participants list now on this page.
===__Descriptive event information__
- Event name
- Wikis involved
- Start time/date (with timezone)
- End time/date
- Length of the event (in days / hours) !![Is this needed here?]!!
- Date/time of last data update !![place near update button]!!
- Event type !![editathon, content drive, training session, etc.]!!
- Event partners !![GLAMs etc.]!!
- Event venue
- Location !![City/state/province?]!!
- Short description
===__Metrics__
- Most figures are for "# of" unless otherwise specified. E.g., [# of] participants, [# of] pages created, [# of] Commons uploads, etc.
- I've broken the event data into three categories, which may aid users in understanding the page.
**Participants**
- Participants
- % new editors !![better as a number or a %?]!!
- 7-days retention !![better as a number or a %?]!!
- Gender breakdown !![how to express? How about M/F] !!
**Contributions**
- Pages created
- Pages improved
- Edits
- Bytes added
- ~~Bytes removed~~
- Words added
- Commons uploads !![I want to change this to "Uploaded files"--but I'm waiting to make sure we can track both Commons uploads and uploads directly to wikis.]!!
- Wikidata items created
- Wikidata claims created
**Impact**
- Views to pages created
- Views to pages improved
- Views to uploaded files
- Pages with uploaded files
- New page survival rate
- Plays to uploaded audio/video