database - Examples of good UI for selecting multiple records -
I am currently reviewing an area of my Windows-based software and 1-> M to M -> M . As a result, I need to adjust the UI to select several related records.
There are so many ways to handle it in a normal way, but generally it is very trickling, for instance, a two-table list of all items, a list of selected items, or a list of all records and Each one has a checkbox beside it to apply.
In my case, there can be a terrible lot (in thousands of records) connected, so I would probably need to include some sort of search mechanism.
I am not looking for a difficult and fast answer. I can implement something very easy which is functional, I want to see if anyone here Whether to come up with any great UI to talk about, whether it is Web-based, Windows, Mac, Unix
Edit: Here's an example of what I'm thinking:
items are displayed as user type
- < P> You obviously start with that record, in which you want to associate with multiple items.
-
As you type searches, displays matches (no need to press on "search")
- < P> User chooses the desired record (sorting will be good, then uses "tag relevance", for example typing 'A' brings Java instead of ASP because Java has more questions than ASP, relevance in your case user's name May be)
-
The system builds relationships (in
-
If multiple records (5+) are filling input fields, they are moved to a semi-reggae area (there is no problem because it Only 5 tags will take the same question, but in your case "interesting tag" will be required)
<
Or click on the canal buttons.In this approach, "search" does not require a user's press or "add another" is not needed which are disturbed by what they are doing again, said this It's going to obstruct the car of your thoughts.
In addition, if you grab a mouse to click on the user while typing the user, then it is less efficient (I It sounds like something about it But very clearly I may be wrong)
As you see, this approach is already in your mind, but adding some features to please the user ( The danger will be if the user likes this approach and wants to see it in other parts of the system)
Comments
Post a Comment