Miller Column AntiFlood

Registered by Sergey "Shnatsel" Davidoff on 2012-10-23

Filtering miller columns work well as long as they don’t fragment content too much. For example, they don’t work well in a music player if your music library consists of cherry-picked tracks from various albums. Filtering by album often returns just one or two content items (tracks).

In more general terms, the content area is underused - it has way less than the optimal 7±2 items - and the filter column gets flooded. With a flooded filter column point-and-click navigation becomes so hard that the user is almost forced to use the keyboard-based search.

We should take measures to keep miller columns usable on such data collections.

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.