Hot answers tagged search
6
Besides the obvious UI affordance of a visible search box, offering a custom Find solution gives you one big advantage over the browser-based find: control over the presentation of matches.
If most of your users are going to be looking for specific text in chronological order, a custom solution may not be necessary. However, implementing your own Find ...
5
More generally, you may see this referred to as semantic search, which tries to establish the meaning of words in a query.
Semantic search seeks to improve search accuracy by understanding searcher intent and the contextual meaning of terms as they appear in the searchable dataspace, whether on the Web or within a closed system, to generate more relevant ...
5
Don't expect users to know shortcuts. If searching within the log file will be something users will be doing often, an unobtrusive search bar that accomplished this is the best answer. Though it sounds like your users are likely to be more tech savvy than the average person, here's an article that states that only about 1 in 10 internet users even know about ...
3
I found this in a blog note. No idea if its any trustful though:
Graph Search A/B Testing
Facebook is doing some A/B testing on their Graph Search.
They are testing their Original layout, vs 2 new layouts (A & B).
A few weeks from now, we should be able to see the declared winner (if
any).
Apparently Facebook is testing your ...
3
The simple answer it that you should place an advanced search option everywhere that you have search in your app. The prime reason being consistency.
If it's available for the search on one page, but not on the next, you are going to confuse users. People think relatively, and so they associate advanced search with search. When you then leave it out, ...
3
What you are looking to do is reduce the results.
The key to this is to provide the same tools that users use for browsing in the search result, with a few tweaks to make them relevant. Avoid thinking of it as 'advanced search' as that's not the way users think - they just view it as one experience.
With the shopping sites I have worked on the common ...
3
Assuming you're using a wireframing format where you can hide dropdown elements to see what's behind them, it's fairly common to show the autocomplete form with a few letters typed and a few rows appearing below it.
Some examples from pattern libraries are:
from the Yahoo Design Pattern Library
from CollectionSpace.org
from Welie.com's Patterns in ...
3
It depends. One consensus seems to be to remove such information from intranet search results in favor of including a more human-readable location (http://www.steptwo.com.au/papers/cmb_searchresults/index.html), however other groups recommend including it as a valuable piece of contextual information (i.e., "Oh, that URL is under ...
2
Some advice in addition to the points already mentioned: if you do implement your own, don't think of it as a re-implementation. Think of it as an addition. That means:
Make sure the Ctrl+F version still works, and make sure it works well (so keep the text as basic HTML). Don't steal the ctrl+f shortcut.
Choose a fundamentally different form for the ...
2
In any case let your users know how they can search the log file. As stated before only 1 in 10 internet users know about the CTRL+F shortcut, so don't just assume everybody knows.
A visible "custom" search bar is better from a UX perspective (if it performs well), however it might not make sense for you to implement it, so instead you can make it obvious ...
2
These is a different between Auto-complete and Auto-suggest.
Auto-complete happens within the input box where you type and you can press either enter or "right-arrow-key" to accept it.
Auto-Suggest list appears as a multiple suggestion list in the form of drop-down. To make use of auto-suggest items, you have to click "down-arrow-key" or mouse click to ...
2
it depends on the requirement..
if your website/product is a search engine (Google, Bing etc) or email (Gmail, Hotmail etc), showing search results on the same page would be a good idea..
if you have a website/product where user would be able to search multiple items/products, displaying search results on a new page would be ideal. User should be able ...
1
Search Results can be shown on the same page as search criteria or a separate page. This is not an UX item. This is to be decided based on the design convenience. It should be transparent to user whether results are shown on same page or different page.
The real important UX item to note is, if the search results are shown in separate page, the search ...
1
I usually just annotate the wireframe with a note:
------------------------
| |
Search: / Search field uses |
[ enter search term ] \ autocomplete |
| |
------------------------
...
1
They call it Graph search at Facebook
At Apples it goes by the name of Unified Smart Search Field
For your concern, there is a fine article about search research at Google and their secret goal :-).
1
In theory, you should provide enough information for the user find the answer to her question, and no more. Inadequate support pages drive down customer loyalty (more details here), but complex pages encourage users to give up before finding an answer (more details here).
In practice, it’s very hard to make a support page both simple and comprehensive.
...
Only top voted, non community-wiki answers of a minimum length are eligible
