The existing Grant Metrics event setup screen offers a simple way to create a new event. With the expansions intended for Event Metrics, we'll be adding new data—primarily descriptive data to make the event more understandable. Also, because we plan to add a lot of metrics to the main event data screen, we will move the Categories and Participants tools from that page to Event Setup. This move is also desirable because of an important change to the way we're defining events (see below).
The goal of this design ticket is to:
- Model a clear and straightforward event-setup workflow
- Redesign the Event Settings page to incorporate the new elements and requirements described below.
Design challenges relating to significant functionality change
- Currently: Grant Metrics offers three types of "filter," all of which are required when defining an event: time period, specified wiki(s), Participant list.
- New system: When we roll out the Categories filter, we will also implement an important change to functionality (T205734): in Event Metrics, all filters will not be required, but there will be a minimum event definition, as follows: event = time period AND specified wiki(s) AND (Participants OR Category OR Worklist) In other words, users must apply at least one filter from among Participants, Categories or Worklist.
- Design challenges:
- Page challenge: It is essential that the design of this page clarify this minimal definition for users. I.e., in addition to signaling which fields are always required (See Existing Event Setup Fields, below), the page design must also clarify that the user must choose at least one of the the filters listed above.
- Workflow challenge: Currently in Grant Metrics, when the user submits an event with no wikis defined, she gets a dialog pointing at the wikis field and saying "please fill out this field." But the user IS allowed to save the event without Participants. And no indication is given that the the event is non-functional. That will remain the case for the interim design (T209107). But for our final design, we need to answer some questions: Is there any purpose to defining an event without defining the filters? What is the use case? And if there is a use case, how will we clarify for users that they must return to Settings and complete the job?
Page Elements
The following elements will populate the Event Settings page
Existing Event Setup Fields ALL REQUIRED
These fields are all already on the setup page; all are required.
- Title
- Wikis
- + Add wikis
- +All Wikipedias
- Time, with calendars and clock tools
- Time Zone
Filters ONE, MINIMUM, REQUIRED
These tools are currently on the main event data screen. They will be moved to the Settings page (and shown by default in their collapsed states). The user must choose one, minimum.
- Participants
- Categories
This is a new filter we that needs to be defined
- Worklist
New informational fields to be added ALL OPTIONAL
The fields below are all informational and optional. Their only current function is to directly add information to the main Event Summary screen (T204009). Functionality for the fields below is described in T209130
- *Description [a short, free-text field] *
- *Event type [menu]
- Content drive
- Editathon
- Hackathon
- Photo contest
- Photo drive
- Photo walk
- Ratings drive
- Training
- Wikidata drive
- Writing contest
- Other
- *Event partners [Free text field]
- *Gender breakdown (estimated)
- # of Women [number field; maximum 5 digits]
- # of Men [number field; maximum 5 digits]
- # of Other [number field; maximum 5 digits]
- [instruction text] Enter these figures directly yourself based on your own visual count or survey. This tool is provided for the convenience of organizers who wish to track participation by gender.
- *Location [Free text field to be interpreted by organizer]
