Let's suppose an application that manage meetings between employees of various companies.
A meetings list is shown to any logged employee, and this one may mark himself as a participant if he's interested in the related topic.
To explain simply, I have a page listing all meetings matching some filters.
The type of filters are:
- filtering by nature of Job (engineer, manager etc.)
- only selecting the logged employee's meetings (no matter whether he's a simple participant or he is the meeting's creator) that are occurring at this time or will occur in the future.
- only selecting the logged employee's meetings that are already terminated (past meetings).
Both last filters are expected to be exclusive => both can't be selected at the same time.
If none of both filters are selected, matched meetings are those happening currently or in the future, no matter whether he's already participating.
Of course, those last filters should be combined with the job filter.
Here's a representation:
When employee selects the filter "My actual or future meetings", only those where he's marked as participant are shown":
When employee doesn't select any "My..." filter, shown meetings are those that are occurring at this time or in the future, no matter if he's marked as a participant or not:
When the employee selects "My past meetings", only finished meetings where he was a participant are shown:
I really want to keep all the natures of filters on the same page.
However, it sounds hard for any user to detect that in order to see meetings where he doesn't participate in, he should disable both "My ..." switches. It seems too implicit.
Furthermore, as by default past meetings are not displayed, I can't really consider the "My past meetings" being a filter, since it doesn't filter (reduce) the view, but adds past meetings.
Do you consider this design acceptable?
What would be a better way to represent the filter zone to increase the UX?