A great example would be choosing addresses in Outlook.
If you go to the "to" chooser, it has the means for a user to easily select
from your personal database of addresses, but what is added besides the
user's name is more information to make sure it is the right person. In this
case that added metadata isn't always necessary but it can certainly help.
In my situations it is often a requirement. I.e. select files. If I don't
have other metadata like folder path or taxonomy info then I can't tell the
difference between objects with the same name.
The problems that arise in a web-app are:
1. latency w/ the information
2. ability to have selection w/o checkboxes on both sides of the selection
In my case I actually pass further data at the point of selection which to
me is nutz but is at this point a weird user requirement.
> > >A problem that I have often found in web-based applications is around the >selection (multi-select) from a large data set that requires the display of >multiple layers of meta-data in order to allow the user to make a proper and
>informed selection. > Can you point to an example in desktop or web apps? I'm not sure I'm
clear on what you're asking for.